JP2007304752A - Authentication system, authentication computer and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a safe and convenient personal authentication system. <P>SOLUTION: The personal authentication system comprises a plurality of client computers and an authentication computer connected to the plurality of computers. The authentication computer assigns, upon receipt of an authentication request from the client computer, a telephone number receivable by the authentication computer to the client computer that is the transmission source of the received authentication request. The authentication computer specifies, upon receipt of dialing, a transmitter telephone number of the dialing and an incoming telephone number, specifies a user corresponding to the specified transmitter telephone number in reference to user information, specifies a client computer corresponding to the specified incoming telephone number in reference to authentication telephone number correspondence information, and determines that the authentication is requested by the specified user in the authentication request received from the specified client computer. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

The present invention relates to an authentication system, an authentication computer, and a program.

Conventionally, a combination of a user ID and a password is known as personal authentication for providing a service by specifying a user. For example, a person who logs in to a WEB site via the Internet inputs a user ID and a password according to a WEB screen displayed on a personal computer to be operated, and transmits an authentication request to the WEB server. In addition, when a user of a financial institution withdraws a deposit at the ATM of the financial institution, a cash card is inserted into the ATM, a personal identification number is input, and an authentication request is transmitted to the authentication server. The user ID in this case is a cash card.

However, the user of the WEB site has the trouble of inputting the user ID and password according to the screen of the WEB site. In addition, this authentication method is widely used, and has been adopted in WEB sites for Internet banking and various electronic commerce. For this reason, the user ID and password which one person should manage are increasing. If the user of the WEB site forgets the user ID or password, it is necessary to inquire the user of the user ID or password to the site operator, and the user cannot enjoy the convenience of the WEB site. Further, impersonation in which a person who is not an original user gives up a user ID and a password and performs a transaction has become a social problem. Phishing and spyware are known as means for giving up the user ID and password. Phishing is an act of providing a pseudo site that looks just like a regular WEB site, allowing the original user to input a user ID and password, and giving up the user ID and password. Spyware is software that is installed without the knowledge of the user of the personal computer, and is software that reads various user IDs and passwords input by the user and notifies the server of the eavesdropper via the Internet. When a transaction by impersonation is established by Internet banking or electronic commerce, not only the original user but also the operator of the WEB site will be seriously damaged due to loss of site reliability and compensation problems.

When a user of a financial institution withdraws a deposit at the ATM of the financial institution, it is troublesome to insert a cash card into the ATM and input a personal identification number. Further, when a personal identification number is voyeurized by a voyeur camera and a cash card is stolen, a deposit is withdrawn by an impersonating user. Banks as well as depositors are severely damaged by the loss of reliability and compensation issues.

Patent Document 1 discloses a personal authentication method for authenticating a user by inputting a user ID and a password to the WEB site and dialing a specific telephone number when the user of the WEB site is authenticated.

Patent Document 2 discloses a personal authentication method for authenticating a user by inputting a telephone number as a user ID into the WEB site and dialing a specific telephone number when the user of the WEB site is authenticated. Yes.
Patent Publication 2002-229951 Patent Publication No. 2004-213440

According to the technique of Patent Document 1, impersonation can be prevented even when a user ID and a password are complied for using a caller telephone number. Further, according to the technique of Patent Document 2, impersonation can be prevented even when a spoofed telephone number is input to a WEB site in order to use a caller telephone number. However, with the techniques of Patent Document 1 and Patent Document 2, it is impossible to accurately grasp the correspondence between the user who dialed with the caller telephone number notification and the computer operated by the user. Therefore, the techniques of Patent Document 1 and Patent Document 2 cannot provide authentication with high safety and convenience. For example, in the techniques of Patent Document 1 and Patent Document 2, a person who is not an original user may impersonate the legitimate user by inputting the user ID of the legitimate user many times. Specifically, if a legitimate user authenticates by dialing a specific telephone number and then redials the specific telephone number by mistake, the person who is not the original user is authenticated as a legitimate user. Will be.

The present invention has been made in view of the above-described problems, and an object thereof is to provide a personal authentication system with high safety and convenience.

An authentication system comprising: a plurality of client computers including a processor, a memory and an interface; and an authentication computer connected to the plurality of computers via a network and including a processor, a memory and an interface, wherein the authentication computer is a user Is stored in the user information indicating the correspondence between the user and the telephone number of the user, and when the authentication request is received from the client computer, the authentication computer is assigned to any of the plurality of client computers among the telephone numbers that can be received. A telephone number that is not yet assigned is assigned to the client computer that is the sender of the received authentication request, and the correspondence between the client computer that is the sender of the received authentication request and the telephone number assigned to the client computer is used for authentication. Store in phone number correspondence information and dial When an incoming call is received, the caller telephone number and the incoming telephone number of the received dial are specified, the user corresponding to the specified caller telephone number is specified with reference to the user information, and the authentication telephone number is supported. With reference to the information, a client computer corresponding to the specified incoming telephone number is specified, and in the authentication request received from the specified client computer, it is determined that authentication is requested by the specified user. An authentication system characterized by that.

An authentication system comprising: a plurality of client computers including a processor, a memory, and an interface; and an authentication computer connected to the plurality of computers via a network and including a processor, a memory, and an interface. , Storing user information indicating correspondence between the user and the user's telephone number, and receiving an authentication request from the client computer, any of the previously received authentication requests among the telephone numbers that can be received by the authentication computer. Is assigned to the received authentication request, the correspondence between the received authentication request and the telephone number assigned to the authentication request is stored in the authentication phone number correspondence information, and a dial is received. Then, the caller telephone number of the incoming dial and the incoming telephone number are specified. Referring to the user information, the user corresponding to the identified caller telephone number is identified, and the authentication request corresponding to the identified incoming telephone number is identified by referring to the authentication telephone number correspondence information The authentication system is characterized in that the specified authentication request determines that authentication is requested by the specified user.

An authentication system comprising: a plurality of client computers including a processor, a memory, and an interface; and an authentication computer connected to the plurality of computers via a network and including a processor, a memory, and an interface. , Storing user information indicating correspondence between the user and the user's telephone number, and assigning the client computer and the authentication computer to the client computer so as not to overlap with other client computers among the telephone numbers that can be received by the authentication computer Is stored in the authentication phone number correspondence information, and when an authentication request is received from the client computer and a dial is received, the caller phone number and the incoming phone number of the incoming dial are specified. And referring to the user information, the identified outgoing call The user corresponding to the telephone number is identified, the client computer corresponding to the identified incoming telephone number is identified with reference to the authentication telephone number correspondence information, and the authentication request received from the identified client computer is An authentication system for determining that authentication is requested by the specified user.

According to the exemplary embodiment of the present invention, the safety and convenience of the personal authentication system can be improved.

Embodiments of the present invention will be described with reference to the drawings. Note that a general-purpose embodiment of the present invention will be described as the first embodiment. Next, as the second embodiment, a specific embodiment in which the first embodiment is used for a WEB site will be described. Next, as the third embodiment, a specific embodiment for easily introducing the second embodiment into an existing WEB server will be described. Next, as the fourth embodiment, a specific embodiment in which the third embodiment is used for Internet credit card settlement will be described. Next, as a fifth embodiment, a specific embodiment in which the first embodiment is used for an ATM of a financial institution will be described. Next, as a sixth embodiment, a specific embodiment in which the first embodiment is used for credit card payment at a store will be described. Next, as the seventh embodiment, a specific embodiment in which the first embodiment is used for connection to an in-house intranet will be described. Next, as an eighth embodiment, a specific embodiment in which the first embodiment is used for connecting a thin client to a centralized server will be described. Next, a specific embodiment in which the first embodiment is used for public wireless LAN connection will be described as a ninth embodiment. Next, as a tenth embodiment, a general-purpose embodiment using a client ID that is an identifier of a client device instead of an authentication request ID will be described.

(First embodiment)
FIG. 1 is a schematic configuration diagram of a personal authentication system according to the first embodiment. The personal authentication system shown in FIG. 1 includes a client device 10, a mobile phone 60, a fixed phone 80, and a dial authentication device 4. The client device 10 is connected to the network 9. The network 9 may be the Internet or an internal network. Details of the client device 10 will be described with reference to FIG. The mobile phone 60 and the fixed phone 80 are telephones that send a dial accompanied by a caller phone number notification when operated by a user. The caller telephone number does not necessarily have to be a number, and may be a character as employed in ISDN (Integrated Services Digital Network) or SIP (Session Initiation Protocol). The mobile phone 60 and the fixed phone 80 are connected to the public switched telephone network 2. The cellular phone 60 and the fixed phone 80 may be IP phones. In this case, the public switched telephone line network 2 is the Internet. The dial authentication device 4 is connected to the client device 10 via the network 9. Specifically, the dial authentication device 4 is connected to the client device 10 via at least one of the Internet and an internal network. The dial authentication device 4 is connected to a mobile phone 60 and a fixed phone 80 via the public switched telephone line network 2. Details of the dial authentication device 4 will be described with reference to FIG. For the sake of clarity, the authentication process for one client apparatus 10 will be described in the personal authentication system of the first embodiment. In practice, the dial authentication device 4 authenticates a plurality of client devices 10 via the network 9. In FIG. 1, five client devices 10 are illustrated, but any number of personal authentication systems may be provided. In FIG. 1, two mobile phones 60 and fixed phones 80 are shown, but any number may be provided. The dial authentication device 4 can receive authentication requests from a plurality of client devices 10.

FIG. 2 is a block diagram of a configuration of the client device 10 included in the personal authentication system according to the first embodiment. The client device 10 is physically a computer system including a transmission / reception unit 11, a central processing unit 12, a main storage device 13, an auxiliary storage device 14, an input device (not shown), a display device (not shown), and the like. . The transmission / reception unit 11 is an interface that is connected to the network 9 and transmits / receives data to / from an external device (dial authentication device 4). The central processing unit 12 is, for example, a CPU. The central processing unit 12 performs various processes by executing programs stored in the main storage device 13. The main storage device 13 is a memory, for example. The main storage device 13 stores programs executed by the central processing unit 12, information required by the central processing unit 12, and the like. The auxiliary storage device 14 is, for example, a hard disk. The auxiliary storage device 14 stores various information. The input device is, for example, a mouse, a keyboard, or a touch panel. Various information is input to the input device from the user. The display device is a display. On the display device, information instructed to be displayed by the central processing unit 12 is displayed. The client device 10 may take any form as long as it includes the transmission / reception unit 11, the central processing unit 12, and the main storage device 13. For example, the client device 10 is a personal computer, a server, a mobile phone, an ATM, or the like.

The client device 10 transmits an authentication request to the dial authentication device 4 in response to a user operation. The client device 10 receives the authentication telephone number and the authentication request ID from the dial authentication device 4. Details of the authentication request ID and the authentication telephone number will be described later.

The client device 10 transmits an authentication result request including the authentication request ID to the dial authentication device 4. Note that the client device 10 may transmit an authentication result request in response to a user operation, or may transmit an authentication result request at regular intervals.

The client device 10 receives the authentication result from the dial authentication device 4.

The cellular phone 60 or the fixed phone 80 transmits a dial with a caller phone number notification to the authentication phone number.

FIG. 3 is a block diagram of the configuration of the dial authentication device 4 provided in the personal authentication system of the first embodiment. The dial authentication device 4 is physically a computer system including a transmission / reception unit 31, a central processing unit 32, a main storage device 33, an auxiliary storage device 34, an input device (not shown), a display device (not shown), and the like. is there. The transmission / reception unit 31 is an interface that is connected to the network 9 and transmits / receives data to / from an external device (client device 10). The central processing unit 32 is, for example, a CPU. The central processing unit 32 performs various processes by executing programs stored in the main storage device 33. The main storage device 33 is, for example, a memory. The main storage device 33 stores programs executed by the central processing unit 32, information required by the central processing unit 32, and the like. The auxiliary storage device 34 is, for example, a hard disk. The auxiliary storage device 34 stores various information. The input device is, for example, a mouse, a keyboard, or a touch panel. Various information is input to the input device from the administrator. The display device is a display. The display device displays information instructed to be displayed by the central processing unit 32. The dial authentication device 4 may be in any form as long as it includes the transmission / reception unit 31, the central processing unit 32, and the main storage device 33. For example, the dial authentication device 4 is a personal computer or a server.

FIG. 4 is a functional block diagram of the dial authentication device 4 according to the first embodiment. The auxiliary storage device of the dial authentication device 4 stores the authentication program 400 of the first embodiment. When the authentication program 400 of the first embodiment is executed, the main memory of the dial authentication device 4 includes a main module 431, an authentication request reception module 4321, an authentication result request reception module 4322, an authentication request ID generation module 433, An authentication telephone number selection module 434, an authentication telephone number transmission module 435, a dial incoming module 436, a telephone number reading module 437, an authentication module 438, and an authentication result transmission module 439 are stored.

The main module 431 includes an authentication request reception module 4321, an authentication result request reception module 4322, an authentication request ID generation module 433, an authentication telephone number selection module 434, an authentication telephone number transmission module 435, a dial incoming module 436, and a telephone number reading module. 437, the authentication module 438 and the authentication result transmission module 439 are integrated.

The authentication request receiving module 4321 receives an authentication request from the client device 10. Upon receiving the authentication request, the authentication request receiving module 4321 requests the authentication request ID generation module 433 to generate an authentication request ID.

The authentication result request reception module 4322 receives an authentication result request from the client device 10. Upon receiving the authentication result request, the authentication result request receiving module 4322 requests the authentication module 438 for authentication.

The authentication request ID generation module 433 generates an authentication request ID. The authentication request ID is a unique identifier of the authentication request. If the dial authentication device 4 receives authentication requests from a plurality of client devices 10 at the same time, a different authentication request ID is assigned to each received authentication request. Further, during processing of the first authentication request, the dial authentication device 4 may receive the second authentication request from the client device 10 that is the transmission source of the first authentication request being processed. In this case, the dial authentication device 4 assigns an authentication request ID different from the first authentication request to the second authentication request. Thereby, the dial authentication device 4 can process a plurality of authentication requests transmitted from the same client device 10 simultaneously. The authentication request ID generation module 433 generates an authentication request ID based on a random number, an application ID, an authentication request ID generation time, and the like. The application ID is a unique identifier of the authentication program 400 installed in the dial authentication device 4. The application ID is generally known as a license key and will not be described in detail. As a method for generating the authentication request ID, other methods may be used as long as the purpose is achieved. Subsequently, the authentication request ID generation module 433 delivers the generated authentication request ID to the authentication telephone number selection module 434.

The authentication telephone number selection module 434 accepts the authentication request ID from the authentication request ID generation module 433. The authentication telephone number selection module 434 selects one telephone number from the authentication telephone number table 443. Details of the authentication telephone number table 443 will be described with reference to FIG. Then, the authentication telephone number selection module 434 assigns the selected telephone number as the authentication telephone number to the accepted authentication request ID. Further, the authentication telephone number selection module 434 stores the accepted authentication request ID and the selected authentication telephone number in association with each other. The correspondence between the authentication request ID and the authentication telephone number is managed by an authentication telephone number correspondence table 441 stored in the auxiliary storage device of the dial authentication device 4. Details of the authentication telephone number correspondence table 441 will be described with reference to FIG. Thereby, the dial authentication device 4 can uniquely identify the authentication request ID corresponding to the authentication telephone number.

FIG. 5 is a configuration diagram of the authentication telephone number table 443 stored in the auxiliary storage device of the dial authentication device 4. The authentication telephone number table 443 includes an authentication telephone number 4431 and an allocation flag 4432. The authentication telephone number 4431 is a telephone number that is a candidate for the authentication telephone number. In the authentication telephone number 4431, all telephone numbers that can be dialed by the dial authentication device 4 are stored in advance. That is, the telephone number 4431 for authentication stores all the telephone numbers assigned to the dial authentication device 4 by the operator operating the public switched telephone line network 2. The assignment flag 4432 indicates whether or not the authentication telephone number 4431 is assigned to any of the authentication requests. Specifically, when the authentication telephone number 4431 is assigned to any authentication request, “1” is stored in the assignment flag 4432. On the other hand, if the authentication telephone number 4431 is not assigned to any authentication request, “0” is stored in the assignment flag 4432.

FIG. 6 is a configuration diagram of the authentication telephone number correspondence table 441 stored in the auxiliary storage device of the dial authentication device 4. The authentication telephone number correspondence table 441 includes an authentication request ID 4411, an authentication telephone number 4412, and a user telephone number 4413. The authentication request ID 4411 is a unique identifier of the authentication request. The authentication request ID 4411 stores an authentication request ID generated by the authentication request ID generation module 433. The authentication telephone number 4412 is a telephone number assigned to the authentication request identified by the authentication request ID 4411 of the record. Note that the telephone number selected by the authentication telephone number selection module 434 is stored in the authentication telephone number 4412. The user telephone number 4413 is the telephone number of the user who requests authentication. Note that the user telephone number 4413 stores the caller telephone number of the dial transmitted from the mobile phone 60 or the fixed telephone 80. In the present embodiment, the user's telephone number is also used as the user's unique identifier.

Here, a method for selecting an authentication telephone number by the authentication telephone number selection module 434 will be described. The authentication request ID must be uniquely specified by the authentication telephone number. In order to achieve this object, the authentication telephone number selection module 434 does not select a telephone number already assigned to the authentication request ID from the authentication telephone number table 443. The authentication telephone number selection module 434 selects a record in which “0” is stored in the allocation flag 4432 of the authentication telephone number table 443 from the authentication telephone number table 443. Next, the authentication telephone number selection module 434 extracts the authentication telephone number 4431 from the selected record. Further, the authentication telephone number selection module 434 stores “1” in the allocation flag 4432 of the selected record. Then, the authentication telephone number selection module 434 assigns the extracted authentication telephone number 4431 to the authentication request. The authentication telephone number selection module 434 cancels the assignment of the authentication telephone number when a predetermined time elapses after the authentication telephone number 4431 is assigned. Further, when the authentication telephone number selection module 434 completes the authentication for the authentication request, the authentication telephone number selection module 434 cancels the assignment of the authentication telephone number for the authentication request. Note that the authentication telephone number selection module 434 may cancel the allocation of the authentication telephone number at another opportunity. Specifically, the authentication telephone number selection module 434 selects, from the authentication telephone number correspondence table 441, a record in which the authentication telephone number to be deallocated and the authentication telephone number 4412 in the authentication telephone number correspondence table 441 match. To do. The authentication telephone number selection module 434 deletes the selected record from the authentication telephone number correspondence table 441. That is, the authentication telephone number selection module 434 deletes the correspondence between the authentication telephone number to be deallocated and the file ID. Next, the authentication telephone number selection module 434 selects, from the authentication telephone number table 443, a record in which the authentication telephone number to be unassigned matches the authentication telephone number 4431 of the authentication telephone number table 443. Next, the authentication telephone number selection module 434 cancels the assignment of the authentication telephone number by storing “0” in the assignment flag 4432 of the selected record. Then, the authentication telephone number selection module 434 can reassign the phone number that has been unassigned to a different authentication request ID as an authentication telephone number. However, the dial authentication device 4 cannot authenticate more users than the number of telephone numbers assigned by the operator of the public switched telephone network within a predetermined time. This is because if all the telephone numbers that can be received by the dial authentication device 4 have already been assigned to the authentication request ID, the authentication telephone number selection module 434 can assign the telephone number to the newly accepted authentication request ID. It is not possible. Therefore, it is preferable that telephone numbers that can be received by the dial authentication device 4 are prepared in advance according to the service provision scale. Note that the authentication telephone number selection module 434 may select the authentication telephone number using another method.

Returning now to FIG. The authentication telephone number selection module 434 delivers the selected authentication telephone number and the accepted authentication request ID to the authentication telephone number transmission module 435.

The authentication telephone number transmission module 435 accepts the authentication telephone number and the authentication request ID from the authentication telephone number selection module 434. The authentication telephone number transmission module 435 transmits the authentication telephone number received from the authentication telephone number selection module 434 to the client device 10.

The dial incoming module 436 receives a dial transmitted from the mobile phone 60 or the fixed phone 80. The dial incoming module 436 may or may not place the dial in a call state. Even if the dial incoming module 436 does not place the dial in a call state, the telephone number reading module 437 can acquire the caller telephone number and the incoming telephone number. Note that the dial incoming module 436 may send a voice message indicating that the dial has been accepted when the dial is placed in a call state.

The telephone number reading module 437 acquires the caller telephone number from the dial received by the dial incoming module 436. Further, the telephone number reading module 437 acquires the incoming telephone number from the port where the dial is received. The method for obtaining the caller telephone number and the incoming telephone number of the telephone number reading module 437 is mounted on a normal CTI server, and thus the description thereof is omitted. Subsequently, the telephone number reading module 437 selects, from the authentication telephone number correspondence table 441, a record in which the acquired incoming telephone number matches the authentication telephone number 4412 of the authentication telephone number correspondence table 441. Next, the telephone number reading module 437 stores the acquired caller telephone number in the user telephone number 4413 of the selected record.

The authentication module 438 accepts an authentication result request including the authentication request ID from the authentication result request reception module 4322. Subsequently, the authentication module 438 acquires an authentication request ID from the authentication result request. Next, the authentication module 438 selects, from the authentication telephone number correspondence table 441, a record in which the acquired authentication request ID matches the authentication request ID 4411 of the authentication telephone number correspondence table 441. Subsequently, the authentication module 438 extracts the user telephone number 4413 from the selected record. If the user telephone number 4413 cannot be extracted, the authentication module 438 determines that authentication is not possible.

Next, the authentication module 438 selects from the user management table 442 a record in which the extracted user telephone number 4413 matches the telephone number 4422 of the user management table 442. Details of the user management table 442 will be described with reference to FIG. The authentication module 438 determines that authentication is not possible when a record having the same user telephone number cannot be selected. On the other hand, the authentication module 438 determines that authentication is possible when a record having the same user telephone number can be selected. The authentication module 438 then passes the authentication result to the authentication result transmission module 439 as an authentication result. As a result, the authentication module 438 can specify the user who issued the authentication request. Specifically, the authentication module 438 extracts the user ID 4421 from the selected record. Then, the authentication module 438 specifies that the issuer of the authentication request identified by the acquired authentication request ID is a user identified by the extracted user ID 4421.

FIG. 7 is a configuration diagram of the user management table 442 stored in the auxiliary storage device of the dial authentication device 4 according to the first embodiment. The user management table 442 includes a user ID 4421 and a telephone number 4422. The user ID is a unique identifier of a user who is authenticated by the dial authentication device 4 of the first embodiment. The telephone number 4422 is the telephone number of the user identified by the user ID 4421. Note that the user management table 442 may hold other information unique to the user. The user-specific information includes, for example, at least one of a user name, password, credit card number, cash card number, user biometric information, schedule table, operation history, and deposit balance. That is, in the user management table 442, user-specific information is managed corresponding to the user ID 4421.

The user of the dial authentication device 4 according to the first embodiment registers the user ID 4421 and the telephone number 4422 in the user management table 442 in advance by a predetermined method. Note that when the telephone number 4422 is used as the user ID, the user ID 4421 can be omitted.

The authentication result transmission module 439 transmits the authentication result determined by the authentication module 438 to the client device 10. When the authentication module 438 determines that authentication is possible, the authentication result transmission module 439 may transmit an authentication result accompanied with user-specific information corresponding to the user ID 4421.

Next, processing of the personal authentication method of the first embodiment will be described with reference to the drawings. FIG. 8 is a sequence diagram of processing of the personal authentication method of the first embodiment.

Client apparatus 10 transmits an authentication request to dial authentication apparatus 4 via network 9 in response to a user operation (ST211).

Then, authentication request receiving module 4321 receives an authentication request from client device 10 (ST212). Next, the authentication request receiving module 4321 requests the authentication request ID generation module 433 to generate an authentication request ID.

Upon receiving a request for generating an authentication request ID, authentication request ID generation module 433 generates an authentication request ID (ST213). Next, the authentication request ID generation module 433 delivers the generated authentication request ID to the authentication telephone number selection module 434.

The authentication telephone number selection module 434 accepts the authentication request ID from the authentication request ID generation module 433. Next, the authentication telephone number selection module 434 selects one authentication telephone number from the authentication telephone numbers 4431 in the authentication telephone number table 443 (ST214). Next, the authentication telephone number selection module 434 generates a new record in the authentication telephone number correspondence table 441. Next, the authentication telephone number selection module 434 stores the authentication request ID accepted from the authentication request ID generation module 433 in the authentication request ID 4411 of the created new record. Next, authentication telephone number selection module 434 stores the selected authentication telephone number in authentication telephone number 4412 of the created new record (ST215). Next, the authentication telephone number selection module 434 delivers the selected authentication telephone number and the accepted authentication request ID to the authentication telephone number transmission module 435.

The authentication telephone number transmission module 435 accepts the authentication telephone number and the authentication request ID from the authentication telephone number selection module 434. Next, the authentication telephone number transmission module 435 transmits the accepted authentication telephone number and authentication request ID to the client device 10 via the network 9 (ST216).

Client device 10 receives the authentication telephone number and authentication request ID from dial authentication device 4 (ST217). Next, the client device 10 displays the received authentication telephone number on the display device.

The cellular phone 60 transmits a dial including the caller telephone number to the authentication telephone number via the public switched telephone line network 2 in response to a user operation (ST218).

Then, dial incoming module 436 accepts an incoming dial call from mobile phone 60 (ST219).

The telephone number reading module 437 acquires the caller telephone number and the incoming telephone number from the dial received by the dial incoming module 436. Next, the telephone number reading module 437 selects, from the authentication telephone number correspondence table 441, a record in which the acquired incoming telephone number matches the authentication telephone number 4412 of the authentication telephone number correspondence table 441. Next, the telephone number reading module 437 stores the acquired caller telephone number in the user telephone number 4413 of the selected record (ST220).

On the other hand, the client device 10 transmits an authentication result request including the authentication request ID to the dial authentication device 4 via the network 9 (ST221).

Then, the authentication result request receiving module 4322 receives an authentication result request from the client device 10 (ST222). Upon receiving the authentication result request, the authentication result request receiving module 4322 requests the authentication module 438 for authentication.

When receiving the authentication request, the authentication module 438 acquires the authentication request ID from the authentication result request received by the authentication result request receiving module 4322. Next, the authentication module 438 selects, from the authentication telephone number correspondence table 441, a record in which the acquired authentication request ID matches the authentication request ID 4411 of the authentication telephone number correspondence table 441. Subsequently, the authentication module 438 extracts the user telephone number 4413 from the selected record. If the user telephone number 4413 cannot be extracted, the authentication module 438 determines that authentication is not possible. If it is determined that authentication is not possible, the authentication module 438 passes authentication impossible to the authentication result transmission module 439 as an authentication result. On the other hand, when the user telephone number 4413 can be extracted, the authentication module 438 selects from the user management table 442 a record in which the extracted user telephone number 4413 matches the telephone number 4422 of the user management table 442 (FIG. 7). . The authentication module 438 determines that authentication is not possible when a record with a matching telephone number cannot be extracted. If it is determined that authentication is not possible, the authentication module 438 passes authentication impossible to the authentication result transmission module 439 as an authentication result. In the first embodiment, the authentication module 438 determines that a user who is not registered in the user management table 442 in advance cannot be authenticated. However, the authentication module 438 may authenticate a user who is not registered in the user management table 442 as a new user. In this case, the authentication module 438 generates a new user ID when a record with a matching telephone number cannot be extracted from the user management table 442. At this time, the authentication module 438 generates user IDs so as not to overlap with all user IDs 4421 included in the user management table 442. Next, the authentication module 438 creates a new record in the user management table 442. Next, the authentication module 438 stores the generated user ID in the user ID 4421 of the generated new record. Further, the authentication module 438 stores the extracted user telephone number 4413 in the telephone number 4422 of the generated new record. As a result, the authentication module 438 associates the generated user ID with the caller telephone number acquired from the dial and stores them in the user management table 442. Then, the authentication module 438 authorizes the user corresponding to the caller telephone number acquired from the dial as a new user. Note that the authentication module 438 may receive information specific to the registered user from the client device 10. Then, the authentication module 438 stores the received unique information of the user in the newly generated record. Note that the user-specific information may be included in the authentication request, may be included in the authentication result request, or may be transmitted alone.

On the other hand, the authentication module 438 determines that authentication is possible when a record having a matching telephone number can be extracted. Then, authentication module 438 delivers authentication result to authentication result transmission module 439 as an authentication result (ST223). As a result, the authentication module 438 can specify the user who issued the authentication request. Specifically, the authentication module 438 extracts the user ID 4421 from the selected record. Then, the authentication module 438 specifies that the issuer of the authentication request identified by the acquired authentication request ID is a user identified by the extracted user ID 4421. Note that the authentication module 438 may include user-specific information corresponding to the extracted user ID 4421 in the authentication result.

The authentication result transmission module 439 accepts the authentication result from the authentication module 438. Next, the authentication result transmission module 439 transmits the accepted authentication result to the client device 10 via the network 9 (ST224).

Then, the client device 10 receives the authentication result from the dial authentication device 4 (ST225).

As described above, the user of the client device 10 can receive personal authentication without entering a user ID and password. Therefore, there is no risk that the user ID and password are given up. In the present embodiment, the user of the client device 10 does not need to manage the user ID and password. Thus, the trouble of inputting the user ID and password can be omitted. Furthermore, the user cannot receive personal authentication without both the client device 10 and the mobile phone 60. As a result, another person who has acquired only the client device 10 can impersonate the user of the client device 10 and cannot be authenticated. That is, even if the client device 10 is lost, information leakage can be prevented. As described above, according to the present embodiment, the management of the user ID and password is unnecessary, the trouble of inputting the user ID and password is eliminated, and the risk of giving up the user ID and password is eliminated. A highly personal authentication system can be provided. Further, the dial authentication device 4 accurately grasps the correspondence between the user who dials with the caller telephone number notification and the computer operated by the user. Therefore, there is no possibility that a person who is not the original user will impersonate the legitimate user by repeatedly inputting the legitimate user's user ID and the like. According to the present embodiment, it is possible to provide a personal authentication system with high safety and convenience.

In the above embodiment, the dial authentication device 4 is configured by a single device, but may be configured by a plurality of devices depending on the scale of the service to be provided. In this case, the devices constituting the dial authentication device 4 are connected to each other via an appropriate data transfer path. Further, the dial authentication device 4 may be composed of a plurality of devices according to functions. For example, the dial authentication device 4 includes an apparatus that selects an authentication telephone number and receives a dial, and an apparatus that receives an authentication request and an authentication result request and transmits the authentication telephone number and the authentication result. . Also in this case, the devices constituting the dial authentication device 4 are connected to each other via an appropriate data transfer path. Information including the authentication telephone number and the telephone number of the dial addressed to the authentication telephone number is delivered between the devices via the data transfer path.

Here, the maximum feature of this embodiment will be described. As described above, the cellular phone 60 transmits a dial accompanied by the caller telephone number to the authentication telephone number. Then, the dial authentication device 4 receives an incoming call. The dial authentication device 4 specifies a user who is to be authenticated based on the dialer telephone number of the accepted dial. Also, the dial authentication device 4 specifies an authentication request ID that is a unique identifier of the authentication result request based on the telephone number that received the dial. That is, the dial authentication device 4 can specify the correspondence between the authentication request and the user who requests authentication based on the authentication request. Next, the client device 10 transmits an authentication result request to the dial authentication device 4. Then, the dial authentication device 4 receives the authentication result request. The dial authentication device 4 can identify the client device operated by the identified user based on the authentication request ID included in the received authentication result request. Thus, in the present embodiment, the dial authentication device 4 can realize authentication even though the user ID is not included in the authentication request. In the authentication method using the user ID and password, the user ID and password are included in the authentication request. On the other hand, the dial authentication device 4 according to the present embodiment specifies a user to be authenticated by dialing. And the dial authentication apparatus 4 specifies the client apparatus operated by the specified user. As a result, the dial authentication device 4 can perform authentication even if the user ID is not included in the authentication request.

In the above embodiment, the authentication telephone number transmission module 435 transmits the authentication telephone number selected by the authentication telephone number selection module 434 and the authentication request ID generated by the authentication request ID generation module 433 to the client device 10. However, the authentication telephone number transmission module 435 may transmit only the authentication telephone number to the client device 10. In this case, the authentication request ID 4411 in the authentication telephone number correspondence table 441 can be omitted. Then, the client device 10 transmits an authentication result request including an authentication telephone number to the dial authentication device 4 instead of the authentication request ID. That is, the authentication telephone number is also used as an identifier for identifying the authentication request. Then, the authentication module 438 acquires an authentication telephone number from the authentication result request. Next, the authentication module 438 selects, from the authentication telephone number correspondence table 441, a record in which the acquired authentication telephone number matches the authentication telephone number 4412 of the authentication telephone number correspondence table 441. Then, the authentication module 438 extracts the user telephone number 4413 from the selected record.

Moreover, in this Embodiment, the mobile telephone 60 transmits the dial with a caller telephone number. However, when the client device 10 is equipped with an IP phone function, a dial with a caller telephone number may be transmitted. Accordingly, the user can be authenticated by the telephone number assigned to the client device 10.

Here, a modification of the first embodiment of the present invention will be described. When the dial authentication device 4 according to the first embodiment receives the authentication result request from the client device 10, whether or not the user telephone number 4413 extracted from the authentication telephone number correspondence table 441 is stored in the user management table 442. It was confirmed. However, the dial authentication device 4 may confirm whether or not the acquired caller telephone number is stored in the user management table 442 when the dial is received. In this case, the authentication telephone number correspondence table 441 includes a confirmation result flag. The confirmation result flag indicates whether or not the dial authentication device 4 has confirmed that the dialer telephone number is stored in the user management table 442. Specifically, “0” is stored in advance in the confirmation result flag. When the dial authentication device 4 confirms that the caller telephone number of the accepted dial is stored in the user management table 442, the dial authentication device 4 stores “1” in the confirmation result flag. When receiving the authentication result request from the client device 10, the dial authentication device 4 refers to the authentication telephone number correspondence table 441 instead of referring to the user management table 442. Specifically, if “1” is stored in the confirmation result flag of the authentication telephone number correspondence table 441, the dial authentication device 4 determines that authentication is possible. On the other hand, if “0” is stored in the confirmation result flag of the authentication telephone number correspondence table 441, the dial authentication device 4 determines that the authentication is impossible.

Note that the user of the present embodiment may be a computer instead of a person. For example, the computer may be authenticated as a user. By the way, since the security against impersonation of the present invention depends on the strength against impersonation of the caller telephone number, the impersonation of the caller telephone number will be described.

The caller telephone number is transmitted not from the mobile phone 60 but from the exchange of the public switched telephone line network 2. The mobile phone 60 issues an instruction to notify the dialing recipient of the caller telephone number, accompanying the dialing. Therefore, it is difficult to forge the caller telephone number by operating the mobile phone 60.

Here, authentication in the present invention will be described. Authentication in the present invention includes not only a general concept but also authentication in a broad sense. Specifically, the authentication in the present invention is verification of whether or not the user has the right to use the service provided by the personal authentication system. The personal authentication system of the present invention can identify a user who uses a client device and provide a service corresponding to each identified user. Therefore, the authentication request in the present invention is a request for verifying whether the user has the right to use the service provided by the personal authentication system. A specific example of authentication according to this embodiment will be described. For example, the authentication request is a request for logging in to the WEB page. In this case, the dial authentication device 4 may be a WEB server or an authentication-dedicated device that receives an authentication request from the WEB server. The authentication request is a request for credit card settlement on the WEB page. In this case, the dial authentication device 4 may be a WEB server that performs credit card payment, or may be a dedicated authentication device that receives an authentication request from the WEB server. The authentication request is a request for withdrawal of a deposit, repayment of a borrowing or borrowing of a borrowing in an ATM. In this case, the client device 10 is an ATM. Further, the dial authentication device 4 is a management server that manages settlement in ATM. The authentication request is a request for credit card payment at the store. In this case, the client device 10 is a reader device that reads credit card information. Further, the dial authentication device 4 is a management server that manages payment of a credit card in the reader device. The authentication request is a request for debit card settlement. In this case, the client device 10 is a reader device that reads information of the debit card. Furthermore, the dial authentication device 4 is a management server that manages settlement of debit cards in the reader device. The authentication request is a request for borrowing after payment with the public utility fee. In this case, the client device 10 is an ATM. Furthermore, the dial authentication device 4 is a management server that manages borrowing in the ATM. The authentication request is a request for payment of unpaid utility bills. In this case, the client device 10 is an information terminal installed in a convenience store or the like. Furthermore, the dial authentication device 4 is a management server that manages the information terminal. The authentication request is a request for connection to the in-house intranet. In this case, the dial authentication device 4 is a management server that manages an intranet in the company. The authentication request is a request for connection to a server by a thin client (THIN CLIENT). In this case, the dial authentication device 4 is a management server that manages the connection between the thin client device and the server. The authentication request is a request for connection to a wireless LAN access point. In this case, the dial authentication device 4 is a management server that manages the connection between the client device 10 and the access point. Although the authentication request of the present embodiment does not include the user ID and password, the dial authentication device 4 can perform authentication processing. The dial authentication device 4 may improve safety by executing a conventional authentication process in combination with the authentication process of the present embodiment. For example, the dial authentication device 4 may authenticate by collating the unique information of the user together with the authentication process of the present embodiment. The user specific information includes, for example, at least one of a user name, a password, a credit card number, a cash card number, a user's biometric information, an email address, a telephone number, a schedule table, an operation history, and a deposit balance. However, the unique information of the user is preferably other than the phone number of the mobile phone 60. This is because the Service-to-Self who wants to be authenticated by impersonation knows the telephone number of the mobile phone 60 and therefore does not increase the security of the authentication system of the present embodiment. Next, a specific example of an authentication method for verifying user-specific information will be described. Specifically, the dial authentication device 4 may perform authentication by collating at least one of a user ID and a password. In this case, the dial authentication device 4 stores the correspondence between the user ID and the user's unique information in advance. On the other hand, a user who wants to receive authentication inputs user-specific information to the client device 10. The input here includes not only the operation of a keyboard or the like but also the reading of a card by a card reader. That is, any client device 10 may be used as long as it can acquire user-specific information. The input timing of the user's unique information may be any time. The client device 10 transmits the input user-specific information to the dial authentication device 4. The client device 10 may transmit the input user-specific information in the authentication request, may be transmitted in the authentication result request, or may be transmitted alone. The dial authentication device 4 receives user-specific information from the client device 10. The authentication module 438 of the dial authentication device 4 stores the user-specific information stored corresponding to the user ID of the user specified as the authentication request issuer in step ST223 of the personal authentication method processing (FIG. 8). Identify. Next, the authentication module 438 of the dial authentication device 4 determines whether or not the specified user's unique information matches the user's unique information received from the client device 10. Then, the dial authentication device 4 determines that authentication is possible when the unique information of the two users matches. On the other hand, the dial authentication device 4 determines that authentication is not possible when the unique information of the two users does not match.

(Second Embodiment)
Although the personal authentication system of the second embodiment will be described below, the same reference numerals are used for portions that overlap with the personal authentication system of the first embodiment, and description thereof is omitted.

In the second embodiment, the management of the user ID and password by the user of the WEB site is not required, the labor of inputting the user ID and password is omitted, and the risk of compromising the user ID and password by phishing or spyware is eliminated. An object is to provide a safe and convenient WEB site personal authentication system. In addition, the correspondence between the user who dials with the caller telephone number notification and the computer operated by the user is accurately grasped, and the person who is not the original WEB site user can obtain the user ID of the user of the legitimate WEB site. It is an object of the present invention to provide a personal authentication system with high safety and convenience that does not have the possibility of impersonating the legitimate user by inputting many times.

FIG. 9 is a schematic configuration diagram of a personal authentication system according to the second embodiment. The personal authentication system shown in FIG. 9 includes a client device 9110, a mobile phone 9160, a fixed telephone 9180, and a dial authentication WEB device 914. The client device 9110 is a computer operated by a user who is going to be authenticated. The client device 9110 is connected to the network 9. In the second embodiment, the network 9 is the Internet. Further, the configuration of the client device 9110 is the same as that of the client device 10 (FIG. 2) provided in the personal authentication system of the first embodiment, and a description thereof will be omitted. The client device 9110 may take any form as long as it includes a transmission / reception unit, a central processing unit, and a main storage device. The mobile phone 9160 is a telephone that transmits a dial accompanied by a caller telephone number notification when operated by a user. The caller telephone number does not necessarily have to be a number, and may be a character as employed in ISDN (Integrated Services Digital Network) or SIP (Session Initiation Protocol). The mobile phone 9160 is connected to the public switched telephone line network 2. The mobile phone 9160 may be an IP phone. In this case, the public switched telephone line network 2 is the Internet. The dial authentication WEB device 914 is connected to the client device 9110 via the network 9. The dial authentication WEB device 914 is connected to the mobile phone 9160 and the fixed phone 9180 via the public switched telephone line network 2. The dial authentication WEB device 914 has a WEB server function and a dial incoming server function. Since the configuration of the dial authentication WEB device 914 is the same as that of the dial authentication device 4 (FIG. 3) provided in the personal authentication system of the first embodiment, the description thereof is omitted. For the sake of clarity, the authentication process for one client device 9110 will be described in the personal authentication system of the second embodiment. In practice, the dial authentication WEB apparatus 914 performs authentication for a plurality of client apparatuses 10 via the network 9. In FIG. 9, three client devices 9110 are illustrated, but any number of personal authentication systems may be provided. Further, although four mobile phones 9160 are illustrated, any number may be provided in the personal authentication system. In addition, although two fixed telephones 9180 are illustrated, any number of personal authentication systems may be provided. However, the mobile phone 9160 also functions as the client device 9110 if it has a WEB browser function.

The function of the client device 9110 is the same as that of the client device 10 provided in the personal authentication system of the first embodiment, and a description thereof will be omitted. The client device 9110 transmits an authentication request and an authentication result request to the dial authentication WEB device 914 by HTTP. Also, the client device 9110 receives the authentication telephone number and the authentication result from the dial authentication WEB device 914 by HTTP.

FIG. 10 is a functional block diagram of the dial authentication WEB apparatus 914 according to the second embodiment. The auxiliary storage device of the dial authentication WEB device 914 stores the authentication program 91400 of the second embodiment. When the authentication program 91400 of the second embodiment is executed, a main module 431, an authentication request reception module 4321, an authentication result request reception module 4322, and an authentication request ID generation module 433 are included in the main storage device of the dial authentication WEB apparatus 914. , An authentication telephone number selection module 434, an authentication telephone number transmission module 91435, a dial incoming module 436, a telephone number reading module 437, an authentication module 438, and an authentication result transmission module 91439 are stored.

The authentication telephone number transmission module 91435 has the same function as the authentication telephone number transmission module 435 provided in the dial authentication device 4 of the second embodiment. The authentication result transmission module 91439 has the same function as the authentication result transmission module 439 provided in the dial authentication device 4 of the second embodiment. The other modules are the same as those provided in the dial authentication device 4 of the personal authentication system of the second embodiment, and thus description thereof is omitted.

The authentication telephone number transmission module 91435 generates a WEB page including the authentication telephone number in addition to the function of the authentication telephone number transmission module 435. The authentication telephone number transmission module 91435 transmits the generated WEB page and the authentication request ID accepted from the authentication request ID generation module 433 to the client device 9110.

The WEB page (not shown) generated by the authentication telephone number transmission module 91435 includes an authentication telephone number and an authentication result request button, and is displayed on the client device 9110. The authentication result request button accepts an instruction to send an authentication result request from the user. That is, when the authentication result request button is operated by the user, the client device 9110 transmits an authentication result request to the dial authentication WEB device 914. Note that the WEB page generated by the authentication telephone number transmission module 91435 may not include the authentication request button. In this case, the client apparatus 9110 transmits an authentication result request to the dial authentication WEB apparatus 914 at regular intervals without triggering a user operation.

The authentication result transmission module 91439 generates a WEB page including the authentication result of the authentication module 438 in addition to the function of the authentication result transmission module 439. The authentication result transmission module 91439 transmits the generated WEB page to the client device 9110 as an authentication result. If the authentication result can be authenticated, the WEB page generated by the authentication result transmission module 91439 may include user-specific information corresponding to the user ID. The user-specific information includes, for example, at least one of a user name, password, credit card number, cash card number, user biometric information, schedule table, operation history, and deposit balance.

Next, the personal authentication method of the second embodiment will be described with reference to the drawings. FIG. 11 is a sequence diagram of processing of the personal authentication method according to the second embodiment. The personal authentication method of the second embodiment (FIG. 11) is compared with the personal authentication method of the second embodiment (FIG. 8). The personal authentication method of the second embodiment includes ST91216 instead of ST216. Also, the personal authentication method of the second embodiment includes ST91224 instead of ST224. The processing of the personal authentication method of the second embodiment is the same as the processing sequence (FIG. 8) of the personal authentication method of the second embodiment, except for ST91216 and ST91224. Therefore, description of steps other than ST91216 and ST91224 is omitted.

ST91216 will be described. The authentication telephone number transmission module 91435 accepts the authentication telephone number selected by the authentication telephone number selection module 434 and the authentication request ID generated by the authentication request ID generation module 433 from the authentication telephone number selection module 434. Next, the authentication telephone number transmission module 91435 generates a WEB page including the accepted authentication telephone number. Next, the authentication telephone number transmission module 91435 transmits the generated WEB page and the accepted authentication request ID to the client device 9110 via the network 9 (ST91216).

Next, ST91224 will be described. The authentication result transmission module 91439 accepts the authentication result from the authentication module 438. Next, the authentication result transmission module 91439 generates a WEB page including the accepted authentication result. Next, the authentication result transmission module 91439 transmits the generated WEB page to the client apparatus 9110 via the network 9 (ST91224). Note that the authentication result transmission module 91439 may generate a WEB page including user-specific information corresponding to the user ID, and transmit the generated WEB page.

As described above, the user of the client device 9110 can receive personal authentication without entering a user ID and password. Therefore, there is no risk that the user ID and password are given up. Further, the user of the client device 9110 does not need to manage the user ID and password. In this way, this embodiment makes it unnecessary to manage the user ID and password by the user of the WEB site. Further, it is possible to save the user from entering the user ID and password. Furthermore, there is no risk of the user ID and password being given up due to phishing or spyware. Furthermore, the user cannot receive personal authentication without both the client device 9110 and the mobile phone 9160. As a result, another person who has acquired only the client device 10 can impersonate the user of the client device 10 and cannot be authenticated. That is, even if the client device 10 is lost, information leakage can be prevented. As described above, according to the present embodiment, the management of the user ID and password by the user of the WEB site is unnecessary, the labor of inputting the user ID and password is omitted, and the risk of compromising the user ID and password by phishing or spyware Therefore, it is possible to provide a safe and convenient web site personal authentication system that eliminates the need for security. Also, the dial authentication WEB device 914 accurately grasps the correspondence between the user who dials with the caller telephone number notification and the computer operated by the user. Therefore, there is no possibility that a person who is not the original user will impersonate the legitimate user by repeatedly inputting the legitimate user's user ID and the like. According to the present embodiment, it is possible to provide a personal authentication system with high safety and convenience.

Note that the mobile phone 9160 may function as both the mobile phone 9160 and the client device 9110 when the WEB browser function is installed. Further, when the client device 9110 has an IP phone function, it may function as both the mobile phone 9160 and the client device 9110.

Further, a session ID may be used instead of the authentication request ID. The session ID is an identifier for identifying communication between the WEB server and the WEB browser. The session ID is managed by a URL parameter, a cookie, a HIDDEN tag, or the like. The generation and management of the session ID is a function of a normal WEB server and a normal WEB browser. Therefore, detailed description of the session ID is omitted.

(Third embodiment)
In the following, the personal authentication system of the third embodiment will be described. However, the same reference numerals are used for portions that overlap the personal authentication system of the first embodiment or the personal authentication system of the second embodiment. Omitted.

The dial authentication WEB apparatus 914 provided in the personal authentication system of the third embodiment includes an authentication function and a WEB page transmission function including user-specific information. At this time, in order to change the conventional WEB server to have the function of the dial authentication WEB apparatus 914, it is essential to change the program of the WEB server. In addition, in order to change the conventional WEB server to have the function of the dial authentication WEB apparatus 914, it is necessary to receive a dial. On the other hand, in the third embodiment, an embodiment in which the personal authentication method of the present invention can be easily introduced to a conventional WEB server will be described. A conventional WEB server provided in the personal authentication system of the third embodiment is referred to as an introduction WEB server 5.

FIG. 12 is a schematic configuration diagram of a personal authentication system according to the third embodiment. The personal authentication system shown in FIG. 12 includes a plurality of client devices 10, a plurality of mobile phones 60, a plurality of fixed phones 80, an introduction WEB server 5, and a dial authentication dedicated WEB device 954. The client device 10 is a computer operated by a user who is going to be authenticated. The client device 10 is connected to the network 9. In the present embodiment, the network 9 is the Internet. Since the configuration of the client device 10 is the same as that of the client device 10 (FIG. 2) provided in the personal authentication system of the first embodiment, the description thereof is omitted. The mobile phone 60 is operated by a user who is going to be authenticated. The cellular phone 60 and the landline phone 80 are dialed with a caller phone number notification when operated by a user. The cellular phone 60 and the fixed phone 80 may be IP phones. In this case, the public switched telephone line network 2 is the Internet. When the mobile phone 60 operates as the client device 10, a WEB browser is installed. In this case, the mobile phone 60 is connected to the network 9. The introduction WEB server 5 is connected to the client device 10 and the mobile phone 60 via the network 9. The introduction WEB server 5 is a conventional WEB server. For example, the introduction WEB server 5 receives a login from the user of the client device 10. Then, the introduction WEB server 5 transmits a WEB page including user-specific information to the client device 10. Specifically, the introduction WEB server 5 transmits a member WEB page corresponding to the user ID. The dial authentication dedicated WEB device 954 is connected to the client device 10 and the mobile phone 60 via the network 9. The dial authentication dedicated WEB device 954 is connected to the mobile phone 60 and the fixed phone 80 via the public switched telephone line network 2. The dial authentication dedicated WEB device 954 has a WEB server function. The configuration of the dial authentication dedicated WEB device 954 is the same as that of the dial authentication device 4 (FIG. 3) provided in the personal authentication system of the first embodiment, and a description thereof will be omitted. For the sake of clarity, in the personal authentication system of the third embodiment, authentication processing of one client device 10 and one introduction WEB server 5 will be described. In FIG. 12, three client devices 10 are illustrated, but any number of personal authentication systems may be provided. Further, although five mobile phones 60 are illustrated, any number of personal authentication systems may be provided. In addition, although two fixed telephones 80 are illustrated, any number of personal authentication systems may be provided. Further, although one introduction web server 5 is illustrated, any number of personal authentication systems may be provided.

For the sake of clarity, in the description of the personal authentication system of the third embodiment, it is assumed that the domain “dunyu.jp” is assigned to the introduction WEB server 5. Further, it is assumed that the domain “ninsho.jp” is assigned to the dial authentication dedicated WEB device 954.

Since the functional configuration of the client device 10 is the same as that of the client device 10 provided in the personal authentication system of the first embodiment, the description thereof is omitted. The client device 10 transmits an authentication request to the dial authentication dedicated WEB device 954, not to the introduction WEB server 5. Thereafter, the client device 10 receives the authentication telephone number and the authentication request ID from the dial authentication dedicated WEB device 954. Further, the client device 10 transmits an authentication result request including the authentication request ID to the dial authentication dedicated WEB device 954.

The client device 10 has the following functions in addition to the functions of the client device 10 provided in the personal authentication system of the first embodiment. The client device 10 transmits a request for a login WEB page to the introduction WEB server 5 in response to a user operation. In addition, the client device 10 transmits a request for a member WEB page to the introduction WEB server 5 based on information included in the WEB page indicating the authentication result received from the dial authentication dedicated WEB device 954.

The introduction WEB server 5 receives the request for the login WEB page transmitted by the client device 10 and transmits the login WEB page. The WEB page includes authentication site information. The authentication site information is information that prompts the client apparatus 10 to transmit an authentication request to the dial authentication dedicated WEB apparatus 954. The authentication site information includes a return URL. The return URL is a URL to which the client apparatus 10 transmits a request for a member WEB page after the authentication by the dial authentication dedicated WEB apparatus 954 is completed. Here, an example of authentication site information is shown. For example, the authentication site information is “<SCRIPT SRC = 'http: //www.ninsho.jp/index.php? Rurl = http: //www.dunyu.jp/member.php' >> </ SCRIPT>". is there. The URL after “rurl =” is the return URL. Further, for example, the authentication site information is “<A HREF='http://www.ninsho.jp/index.php?rurl=http://www.dunyu.jp/member.php'> Click here for authentication < / A> ". The URL after “rurl =” is the return URL. The authentication site information may be other information as long as the purpose is achieved.

The introduction WEB server 5 receives a request for a member WEB page from the client device 10. The introduction WEB server 5 extracts the user's telephone number from the received request for the member WEB page. The introduction WEB server 5 generates a WEB page including user-specific information corresponding to the extracted telephone number. The introduction WEB server 5 transmits the generated WEB page to the client apparatus 10 as a member WEB page.

The function of the dial authentication dedicated WEB device 954 is mainly the same as that of the dial authentication WEB device 914 provided in the personal authentication system of the second embodiment. The functions of the dial authentication dedicated WEB device 954 include the following functions in addition to the functions of the dial authentication WEB device 914 provided in the personal authentication system of the second embodiment. The dial authentication dedicated WEB device 954 extracts the return URL from the authentication request received from the client device 10. Further, the dial authentication dedicated WEB device 954 stores the extracted return URL in association with the generated authentication request ID in the authentication telephone number correspondence table 441. Therefore, the authentication telephone number correspondence table 441 includes a return URL (not shown). Also, the dial authentication dedicated WEB device 954 generates a WEB page including the return URL and the user's telephone number as a result of the authentication. The example of the source code contained in the produced | generated WEB page is shown. For example, the source code is “<meta http-equiv =“ Refresh ”content =“ 0; url = http: // www. dounyu. jp / member. php? usrtel = 09014812122 & auth = 1 ″> ”. The URL after “url =” is the return URL. The numeric string after “userel =” is the telephone number of the user. The value after “auth =” is the result of authentication. For example, “1” can be authenticated, and “0” cannot be authenticated. However, “auth =” is not necessarily included. For example, the source code is “<A HREF =“ http: // www. dounyu. jp / member. php? usrtel = 09014812122 & auth = 1 "> Membership page is here </A>". The URL after “url =” is the return URL. The numeric string after “userel =” is the telephone number of the user. The value after “auth =” is the result of authentication. For example, “1” can be authenticated, and “0” cannot be authenticated. However, “auth =” is not necessarily included. The source code included in the WEB page may be other as long as the purpose is achieved.

Next, a personal authentication method according to the third embodiment will be described with reference to the drawings. FIG. 13 is a sequence diagram of processing of the personal authentication method of the third embodiment. The personal authentication method of the third embodiment (FIG. 13) is compared with the personal authentication method of the second embodiment (FIG. 11). The personal authentication method of the third embodiment includes ST95212 instead of ST212. Also, the personal authentication method of the third embodiment includes ST95215 instead of ST215. Further, the personal authentication method of the third embodiment includes ST95224 instead of ST224. The personal authentication method of the third embodiment includes ST95209, ST95210, ST95226, ST95227, and ST95228. Processing of the personal authentication method of the third embodiment is the same as that of the personal authentication method of the second embodiment (FIG. 11) except for ST95209, ST95210, ST95212, ST95215, ST95224, ST95226, ST95227, and ST95228. Therefore, description of steps other than ST95209, ST95210, ST95212, ST95215, ST95224, ST95226, ST95227, and ST95228 is omitted.

ST95209 will be described. Client apparatus 10 transmits a request for a login WEB page to introduction WEB server 5 via network 9 (ST95209).

ST95210 will be described. The introduction WEB server 5 receives a request for a login WEB page from the client device 10. Next, the introduction WEB server 5 transmits a login WEB page including authentication site information to the client device 10 via the network 9 (ST95210).

ST95212 will be described. The authentication request receiving module provided in the dial authentication dedicated WEB device 954 receives the authentication request from the client device 10. Next, the authentication request receiving module extracts a return URL included in the received authentication request. Next, the authentication request receiving module requests the authentication request ID generation module to generate an authentication request ID (ST95212).

ST95215 will be described. The authentication telephone number selection module generates a new record in the authentication telephone number correspondence table 441. Next, the authentication telephone number selection module stores the authentication request ID accepted from the authentication request ID generation module in the authentication request ID 4411 of the created new record. Next, the authentication telephone number selection module stores the selected authentication telephone number in the authentication telephone number 4412 of the created new record. Next, authentication telephone number selection module 434 stores the return URL extracted by the authentication request receiving module in the return URL of the created new record (ST95215).

ST95224 will be described. The authentication result transmission module accepts an authentication result from the authentication module. Next, the authentication result transmitting module extracts the return URL and the user's telephone number from the authentication telephone number correspondence table 441 based on the authentication request ID extracted by the authentication result request receiving module. The authentication result transmission module generates a WEB page including the return URL and the user's telephone number as a result of the authentication. Next, the authentication result transmission module transmits the generated WEB page as a result of authentication to the client device 10 via the network 9 (ST95224).

ST95226 will be described. The client device 10 receives the WEB page transmitted as a result of the authentication from the dial authentication dedicated WEB device 954. Next, based on the received WEB page, the client apparatus 10 transmits a member WEB page request to the introduction WEB server 5 via the network 9 (ST95226). The request for the member WEB page transmitted by the client device 10 includes the telephone number of the user. For example, a request for a member's WEB page is a URL “http://www.dunyu.jp/member.php?usrtel=09014812122&auth=1”. The numeric string after “userel =” is the telephone number of the user.

ST95227 will be described. The introduction WEB server 5 receives a request for a member WEB page from the client device 10. Next, the introduction WEB server 5 extracts the user's telephone number from the received request for the member WEB page. Next, the introduction WEB server 5 identifies the user based on the extracted telephone number. Next, the introduction WEB server 5 generates a member WEB page corresponding to the identified user. Next, the dial authentication dedicated WEB device 954 transmits the generated member WEB page to the client device 10 via the network 9 (ST95227).

ST95228 will be described. The client device 10 receives a member WEB page from the introduction WEB server 5 via the network 9. Next, the client device 10 displays the received member WEB page on the display device (ST95228).

An outline of processing of the personal authentication method of the third embodiment will be described. The client device 10 requests a login WEB page from the introduction WEB server 5 in response to a user operation (ST95209). The introduction WEB server 5 transmits the requested login WEB page to the client device 10 (ST95210). Based on the authentication site information included in the login WEB page, client apparatus 10 transmits an authentication request to dial authentication dedicated WEB apparatus 954 (ST211). The dial authentication dedicated WEB device 954 receives the authentication request. Next, dial authentication dedicated WEB device 954 extracts the return URL from the received authentication request (ST95212). Next, the dial authentication dedicated WEB device 954 generates an authentication request ID (ST213). Next, dial authentication dedicated WEB device 954 selects an authentication telephone number (ST214). Next, the dial authentication dedicated WEB apparatus 954 stores the authentication request ID, the authentication telephone number, and the return URL in association with each other in the authentication telephone number correspondence table 441 (ST95215). Next, the dial authentication dedicated WEB device 954 transmits the generated authentication request ID and the selected authentication telephone number to the client device 10 (ST91216). The client device 10 receives the authentication request ID and the authentication telephone number (ST217). Next, the client device 10 displays the received authentication telephone number on the display device. Next, cellular phone 60 transmits a dial including a caller telephone number notification to the authentication telephone number in response to a user operation (ST218). Dial authentication dedicated WEB device 954 accepts an incoming dial call from mobile phone 60 (ST219). Next, the dial authentication dedicated WEB device 954 acquires the caller telephone number from the received dial. Also, the dial authentication dedicated WEB device 954 acquires the incoming telephone number from the accepted dial. Next, the dial authentication dedicated WEB device 954 associates the authentication request ID corresponding to the acquired incoming telephone number with the acquired caller telephone number, and stores them in the authentication telephone number correspondence table 441 (ST220). . On the other hand, the client apparatus 10 transmits an authentication result request to the dial authentication dedicated WEB apparatus 954 (ST221). Dial authentication dedicated WEB device 954 receives the authentication result request from client device 10 (ST222). The dial authentication dedicated WEB device 954 extracts an authentication request ID from the received authentication result request. Next, the dial authentication dedicated WEB device 954 extracts the user telephone number 4413 corresponding to the extracted authentication request ID from the authentication telephone number correspondence table 441. Next, the dial authentication dedicated WEB apparatus 954 determines whether or not the extracted user telephone number 4413 is stored in the telephone number 4422 of the user management table 442 (ST223). When the user telephone number 4413 is stored in the user management table 442, the dial authentication dedicated WEB device 954 determines that authentication is possible. On the other hand, when the user telephone number 4413 is not stored in the user management table 442, the dial authentication dedicated WEB device 954 determines that the authentication is impossible. Next, dial authentication dedicated WEB device 954 transmits the result of authentication to client device 10 (ST95224). The client device 10 receives the authentication result (ST225). Next, based on the received authentication result, the client device 10 transmits a member web page request to the introduction web server 5 (ST95226). The introduction WEB server 5 receives a request for a member WEB page from the client device 10. Next, the introduction WEB server 5 extracts the user's telephone number from the received request for the member WEB page. Next, the introduction WEB server 5 transmits a member WEB page corresponding to the extracted telephone number to the client device 10 (ST95227). Note that the member WEB page includes user-specific information corresponding to the user of the extracted telephone number. The client device 10 receives a member WEB page from the introduction WEB server 5. Next, the client device 10 displays the received member WEB page on the display device (ST95228).

As described above, the introduction WEB server 5 which is a conventional WEB server can introduce the personal authentication method of the present invention only by including the authentication site information in the login WEB page transmitted to the client device 10.

In the embodiment described above, the dial authentication dedicated WEB device 954 stores the user management table 442. However, the dial authentication dedicated WEB device 954 does not necessarily need to store the user management table 442. In this case, the introduction WEB server 5 stores the user management table 442. In this case, in step ST223, the dial authentication dedicated WEB apparatus 954 does not determine whether or not the extracted user telephone number 4413 is stored in the telephone number 4422 of the user management table 442. Instead, the introduction WEB server 5 determines whether or not the telephone number included in the request for the member WEB page received from the client device 10 is stored in the user management table 442.

In the embodiment described above, the introduction WEB server 5 trusts the telephone number included in the request for the member WEB page received from the client device 10 and transmits the member WEB page. However, the telephone number included in the request for the member's WEB page may be forged. Therefore, the introduction WEB server 5 may confirm that the link source is the dial authentication dedicated WEB device 954 by referring to the referer.

Here, a modification of the third embodiment of the present invention will be described. In the third embodiment, the dial authentication dedicated WEB device 954 generates an authentication request ID. However, the introduction WEB server 5 may generate an authentication request ID instead of the dial authentication dedicated WEB device 954. In this case, the introduction WEB server 5 stores the generated authentication request ID. Next, the introduction WEB server 5 transmits authentication site information including the generated authentication request ID to the client device 10. The client device 10 extracts the authentication request ID from the received authentication site information. Next, the client device 10 transmits an authentication request including the extracted authentication request ID to the dial authentication dedicated WEB device 954. The dial authentication dedicated WEB apparatus 954 stores the authentication request ID received from the client apparatus 10 and the authentication telephone number in the authentication telephone number correspondence table 441 in association with each other instead of generating the authentication request ID. The dial authentication dedicated WEB device 954 transmits a WEB page including the authentication request ID stored in the authentication telephone number correspondence table 441 to the client device 10 as a result of the authentication. The client device 10 receives the authentication result from the dial authentication dedicated WEB device 954. Next, the client device 10 transmits a request for a member WEB page to the introduction WEB server 5 based on the received authentication result. Here, the client device 10 transmits a request for the member WEB page including the authentication request ID to the introduction WEB server 5. The introduction WEB server 5 receives a request for a member WEB page from the client device 10. Next, the introduction WEB server 5 extracts the authentication request ID from the received request for the member WEB page. Next, the introduction WEB server 5 determines whether or not the extracted authentication request ID is stored. When the introduced authentication request ID is stored, the introduction WEB server transmits a member WEB page to the client device 10. On the other hand, when the extracted authentication request ID is not stored, the introduction WEB server 5 determines that the received request for the member WEB page is camouflaged. Therefore, the introduction WEB server 5 does not transmit a member WEB page. When the dial authentication dedicated WEB device 954 is connected to a plurality of introduction WEB servers 5, each introduction WEB server 5 generates a unique authentication request ID without a personal authentication system. For example, the introduction WEB server 5 generates an authentication request ID including a unique identifier of the introduction WEB server 5, thereby generating a unique authentication request ID within the personal authentication system.

(Fourth embodiment)
Although the personal authentication system of the fourth embodiment will be described below, the same reference numerals are used for portions that overlap with the personal authentication system of the third embodiment, and description thereof is omitted.

In electronic commerce on the Internet, a credit card is often used as a settlement means. In the fourth embodiment, an example in which the personal authentication system of the third embodiment is applied to credit card settlement on the Internet will be described.

Since the schematic configuration diagram of the personal authentication system of the fourth embodiment is the same as the schematic configuration diagram (FIG. 12) of the personal authentication system of the third embodiment, detailed description thereof is omitted. The client device 10 is operated by a user who intends to execute a credit card payment. The mobile phone 60 is operated by a user who intends to execute credit card payment. The introduction WEB server 5 is a WEB server that provides electronic commerce such as article sales or service sales. The dial authentication dedicated WEB device 954 is a WEB device that processes credit card credit examination and billing. The user management table 442 of the dial authentication dedicated WEB device 954 includes a credit card number (not shown). The credit card number included in the user management table 442 is a user's credit card number. The user management table 442 stores a credit card number and a telephone number of a user who owns the credit card in association with each other. Further, the authentication telephone number correspondence table 441 of the dial authentication dedicated WEB device 954 includes a settlement amount (not shown). The settlement amount included in the authentication telephone number correspondence table 441 is an amount to be settled with a credit card.

The outline of the process of the personal authentication method of the fourth embodiment will be described. The introduction WEB server 5 determines the payment amount with the user's operation. The settlement amount determination method may be a method adopted in a conventional electronic commerce site. The client device 10 transmits a request for a settlement WEB page to the introduction WEB server 5 instead of a request for a login WEB page in response to a user operation. The introduction WEB server 5 receives a request for a payment WEB page. Then, the introduction WEB server 5 generates the requested payment WEB page. Next, the introduction WEB server 5 transmits the generated payment WEB page to the client device 10. The payment WEB page generated by the introduction WEB server 5 includes authentication site information. The authentication site information includes the settlement amount as well as the return URL. The client device 10 receives the payment WEB page. Next, the client device 10 transmits an authentication request to the dial authentication dedicated WEB device 954 based on the authentication site information included in the received payment WEB page. The dial authentication dedicated WEB device 954 receives the authentication request. Next, the dial authentication dedicated WEB device 954 extracts the return URL and the payment amount from the received authentication request. Next, the dial authentication dedicated WEB device 954 generates an authentication request ID. Next, the dial authentication dedicated WEB device 954 selects an authentication telephone number. Next, the dial authentication dedicated WEB device 954 stores the generated authentication request ID, the selected authentication telephone number, the extracted return URL, and the extracted settlement amount in association with the authentication telephone number correspondence table 441. Next, the dial authentication dedicated WEB device 954 transmits the generated authentication request ID and the selected authentication telephone number to the client device 10. The client device 10 receives the authentication request ID and the authentication telephone number. Next, the cellular phone 60 sends a dial including a caller phone number notification to the authentication phone number in response to a user operation. As a result, the cellular phone 60 transmits a dial accompanied by a caller telephone number notification to the dial authentication dedicated WEB device 954. The dial authentication dedicated WEB device 954 receives an incoming dial call from the mobile phone 60. Next, the dial authentication dedicated WEB device 954 acquires the caller telephone number and the incoming telephone number from the received dial. Next, the dial authentication dedicated WEB device 954 stores the authentication request ID corresponding to the acquired incoming telephone number in association with the acquired caller telephone number in the authentication telephone number correspondence table 441. On the other hand, the client device 10 transmits an authentication result request to the dial authentication dedicated WEB device 954. The dial authentication dedicated WEB device 954 receives the authentication result request from the client device 10. The dial authentication dedicated WEB device 954 extracts the authentication request ID from the received authentication result request. Next, the dial authentication dedicated WEB device 954 extracts the telephone number and settlement amount corresponding to the extracted authentication request ID from the authentication telephone number correspondence table 441. Next, the dial authentication dedicated WEB device 954 extracts a credit card number corresponding to the extracted telephone number from the user management table 442. Next, the dial authentication dedicated WEB device 954 performs a credit examination by determining whether or not the extracted payment amount can be used with the extracted credit card number. The credit screening here is the same as the credit screening when using a conventional credit card. The dial authentication dedicated WEB device 954 charges the payment amount to the credit card when the credit examination is good. Note that the dial authentication-dedicated WEB device 954 may request the device that performs the credit screening process and the charging process exclusively for the credit screening process and the charging process. When the dial authentication dedicated WEB device 954 completes the accounting process, it determines that the authentication result is authentic. The dial authentication dedicated WEB device 954 transmits the authentication result to the client device 10. Based on the received authentication result, the client device 10 transmits a request for the ending WEB page to the introduction WEB server 5. The introduction WEB server 5 receives a request for a WEB page for completion of payment from the client device 10. Next, the introduction WEB server 5 extracts the user's telephone number from the received WEB page request. Next, the introduction WEB server 5 transmits to the client device 10 a payment-finished WEB page corresponding to the extracted telephone number. The payment-finished WEB page includes user-specific information corresponding to the extracted telephone number.

As described above, the personal authentication system of the third embodiment can be applied to a credit card settlement. In the fourth embodiment, the credit card settlement has been described. However, the settlement means may be any means as long as it is a means for settlement through authentication. For example, the settlement means includes “Edy” (trademark), “Jay debit” (trademark), “mobile phone payment service” (trademark), and the like. “Edy” (trademark) is electronic money that can be used at a store or the Internet. “J Debit” (trademark) is a deposit account debiting settlement service that can be used at stores or the Internet. “Mobile Phone Payment Service” (trademark) is a postpaid payment service available on the Internet in which the payment amount is added to the charge for the mobile phone fee.

Here, a modification of the personal authentication system of the fourth embodiment will be described. The dial authentication dedicated WEB device 954 provided in the personal authentication system of the fourth embodiment specifies the credit card number based on the caller telephone number of the dial that has accepted the incoming call. For this reason, if the dialer's telephone number is forged, it will be settled by the impersonating user. In order to prevent impersonation settlement, the user inputs a credit card number into the client device 10. The client device 10 transmits the input credit card number to the dial authentication dedicated WEB device 954. The client device 10 may transmit the input credit card number included in the authentication request or the authentication confirmation request. The dial authentication dedicated WEB device 954 receives the credit card number from the client device 10. Then, the dial authentication dedicated WEB device 954 stores the received credit card number. The outline of the modification is as follows. The introduction WEB server 5 transmits a payment WEB page including a credit card number input field to the client device 10. The user of the client device 10 inputs a credit card number in the input field of the payment WEB page. The input here includes not only the operation of a keyboard or the like but also the reading of a card by a card reader. That is, any client device 10 may be used as long as it can obtain a credit number. The client device 10 transmits an authentication request including the input credit card number to the dial authentication dedicated WEB device 954. The dial authentication dedicated WEB device 954 receives the authentication request from the client device 10. Next, the dial authentication dedicated WEB device 954 extracts a credit card number from the received authentication request. Next, the dial authentication dedicated WEB device 954 associates the extracted credit card number with the authentication request ID and stores them in the authentication telephone number correspondence table 441. On the other hand, as described above, the dial authentication dedicated WEB device 954 receives the authentication result request from the client device 10. Then, the dial authentication dedicated WEB device 954 extracts the credit card number corresponding to the authentication request ID included in the received authentication result request from the user management table 442. As a result, the dial authentication dedicated WEB device 954 extracts the credit card number used for settlement from the user management table 442. Next, the dial authentication dedicated WEB apparatus 954 collates the extracted credit card number with the credit card number stored in the authentication telephone number correspondence table 441. Only when both the credit card numbers match, the dial authentication dedicated WEB device 954 performs credit examination on the credit card and charges. Moreover, it may be as follows. The dial authentication dedicated WEB device 954 receives the authentication request from the client device 10. Then, the dial authentication dedicated WEB device 954 transmits a WEB page including the authentication telephone number to the client device 10. The WEB page including the authentication telephone number further includes a credit card number input field. The user of the client device 10 inputs the credit card number in the credit card number input field on the WEB page including the authentication telephone number. The client device 10 transmits an authentication result request including the input credit card number to the dial authentication dedicated WEB device 954. As described above, the dial authentication dedicated WEB device 954 receives the authentication result request from the client device 10. Then, the dial authentication dedicated WEB device 954 extracts the credit card number corresponding to the authentication request ID included in the received authentication result request from the user management table 442. As a result, the dial authentication dedicated WEB device 954 extracts the credit card number used for settlement from the user management table 442. The dial authentication dedicated WEB device 954 collates the extracted credit card number with the credit card included in the authentication result request. Only when the two credit card numbers match, the dial authentication dedicated WEB device 954 performs credit examination on the credit card number and charges it. In the modification of the fourth embodiment, impersonation may be prevented by allowing the user to input other information such as a password instead of allowing the user to input a credit card number.

(Fifth embodiment)
In the following, the personal authentication system of the fifth embodiment will be described. However, the same reference numerals are used for portions that overlap with the personal authentication system of the first embodiment, and the description thereof is omitted.

In the fifth embodiment, a financial institution user eliminates the trouble of inserting a cash card into an ATM, entering a personal identification number, and eliminates the risk of the personal identification number being voyeurized. It is an object to provide an authentication system. In addition, the correspondence between the user who dials with the caller telephone number notification and the computer operated by the user is accurately grasped, and the person who is not the original WEB site user can obtain the user ID of the user of the legitimate WEB site. It is an object of the present invention to provide a personal authentication system with high safety and convenience that does not have the possibility of impersonating the legitimate user by inputting many times.

FIG. 14 is a schematic configuration diagram of a personal authentication system according to the fifth embodiment. The personal authentication system shown in FIG. 14 includes a plurality of ATM (AUTOMATIC TELLER MACHINE) 9210, a plurality of mobile phones 60, and an ATM dial authentication device 934. The ATM 9210 is operated by a user who is authenticated and wants to withdraw or withdraw cash. The ATM 9210 is connected to the network 9. Details of the ATM 9210 will be described with reference to FIG. The cellular phone 60 is a telephone that transmits a dial accompanied by a caller telephone number notification when operated by a user. The mobile phone 60 may be an IP phone. In this case, the public switched telephone line network 2 is the Internet. The ATM dial authentication device 934 is connected to the ATM 9210 via the network 9. In the fifth embodiment, the network 9 is an internal network. The network 9 may include a relay device that aggregates authentication devices installed in a plurality of financial institutions. The ATM dial authentication device 934 is connected to the mobile phone 60 through the public switched telephone network 2. Since the configuration of the ATM dial authentication device 934 is the same as that of the dial authentication device 4 (FIG. 3) provided in the personal authentication system of the first embodiment, the description thereof is omitted. In FIG. 14, three ATM 9210s are shown, but any number of personal authentication systems may be provided. In addition, although three mobile phones 60 are illustrated, any number of personal authentication systems may be provided.

FIG. 15 is a block diagram of a configuration of an ATM 9210 provided in the personal authentication system of the fifth embodiment. The ATM 9210 physically includes a transmission / reception unit 11, a central processing unit 12, a main storage device 13, an auxiliary storage device 14, an input device (not shown), a display device (not shown), a cash handling unit 15, and the like. The transmission / reception unit 11 is an interface which is connected to the network 9 and transmits / receives data to / from an external device (ATM dial authentication device 934). The central processing unit 12 is, for example, a CPU. The central processing unit 12 performs various processes by executing programs stored in the main storage device 13. The main storage device 13 is a memory, for example. The main storage device 13 stores programs executed by the central processing unit 12, information required by the central processing unit 12, and the like. The auxiliary storage device 14 is, for example, a hard disk. The auxiliary storage device 14 stores various information. The input device is, for example, a keyboard or a touch panel. Various information is input to the input device from the user. The display device is a display. On the display device, information instructed to be displayed by the central processing unit 12 is displayed. The cash handling unit 15 physically manages banknotes and money. Further, the cash handling unit 15 deposits and withdraws banknotes and money. The cash handling unit 15 may be provided in an ATM of a general financial institution.

Since the functions of the ATM 9210 provided in the personal authentication system of the fifth embodiment are the same as those of the client device 10 provided in the personal authentication system of the first embodiment except for the cash handling unit 15, the description thereof will be omitted.

The mobile phone 60 sends a dial with a caller phone number notification to the authentication phone number.

The functional configuration of the ATM dial authentication device 934 of the fifth embodiment is the same as the function (FIG. 4) of the dial authentication device 4 provided in the personal authentication system of the first embodiment, and thus description thereof is omitted.

The user management table 442 stored in the auxiliary storage device of the ATM dial authentication device 934 stores user-specific information corresponding to the user ID. The user-specific information in the present embodiment is account information of a financial institution. The account information of the financial institution includes an account number, a deposit balance, a borrowing balance, a borrowable balance, and the like. However, the user-specific information does not necessarily have to be managed by the user management table 442, and any method may be used as long as it is managed in correspondence with the user ID. The management method of the user's unique information is left to the implementer of the present invention according to the type of service and the scale of the user. Part of the user's unique information corresponding to the user ID is included in the authentication result transmitted from the ATM dial authentication device 934 to the ATM 9210.

Next, a personal authentication method according to the fifth embodiment will be described. The processing of the personal authentication method of the fifth embodiment is the same as that of the personal authentication method of the second embodiment (FIG. 8), and thus description thereof is omitted. However, here, characteristic steps of the personal authentication method of the fifth embodiment will be described.

ST224 in the fifth embodiment will be described. The authentication result transmission module 439 of the ATM dial authentication device 934 transmits the authentication result to the ATM 9210 via the network 9. The authentication result includes unique information of the user such as an account number corresponding to the user ID, a deposit balance, a borrowing balance, and a borrowable balance.

Subsequent to ST224, the ATM 9210 displays the authentication result received from the ATM dial authentication device 934 and the user's unique information on the display device. The user of the ATM 9210 performs subsequent operations based on the displayed information. Subsequent operations are, for example, withdrawal of deposits, repayment of borrowings or borrowing of borrowings.

By the way, a general ATM can accept various operations such as withdrawal of deposits, repayment of borrowings and borrowing of borrowings. Therefore, prior to ST 211, ATM 9210 accepts the type of operation from the user. The ATM 9210 includes the type of operation requested by the user in the authentication request transmitted to the ATM dial authentication device 934. The ATM dial authentication device 934 extracts the type of operation requested by the user of the ATM 9210 from the authentication request received from the ATM 9210. Then, the ATM dial authentication device 934 determines user-specific information to be included in the authentication result based on the extracted operation type.

The following procedure may also be used. A general ATM can accept various operations such as withdrawal of deposits, repayment of borrowings and borrowing of borrowings. Here, the ATM dial authentication device 934 stores operations that can be received from the user of the ATM 9210 in advance corresponding to the user ID. In this case, the ATM 9210 does not accept the type of operation from the user before sending the authentication request. First, the ATM 9210 is authenticated by the personal authentication method of the fifth embodiment. The ATM dial authentication device 934 includes an acceptable operation corresponding to the authenticated user ID in the authentication result and transmits it to the ATM 9210. The ATM 9210 displays the result of authentication received from the ATM dial authentication device 934 and acceptable operations on the display device. The user of the ATM 9210 selects an operation from among the types of operations displayed on the ATM 9210 display device. The ATM 9210 then performs the selected type of operation.

As described above, according to the present embodiment, a user of a financial institution eliminates the trouble of inserting a cash card into an ATM and inputting a personal identification number, and eliminates the risk of the personal identification number being voyeurized. A highly personal authentication system can be provided. Further, the ATM dial authentication device 934 accurately grasps the correspondence between the user who dials with the caller telephone number notification and the ATM operated by the user. Therefore, there is no possibility that a person who is not the original user will impersonate the legitimate user by repeatedly inputting the legitimate user's user ID and the like. According to the present embodiment, it is possible to provide a personal authentication system with high safety and convenience.

Note that the personal authentication method of the fifth embodiment may be combined with a conventional personal authentication method using a cash card and a personal identification number. Thus, even if the cash card and the password are stolen, the deposit is not withdrawn by the impersonating user unless dialed by the user's telephone number. The personal authentication method of the fifth embodiment may be combined with personal authentication using either a cash card or a personal identification number.

Here, a modification of the fifth embodiment of the present invention will be described. In the fifth embodiment, the ATM dial authentication device 934 generates an authentication request ID and transmits it to the ATM 9210. However, in a modified example, the ATM 9210 may transmit an authentication request including its own ATM_ID to the ATM dial authentication device 934. ATM_ID is a unique identifier of ATM 9210. Then, the ATM dial authentication device 934 extracts ATM_ID from the authentication request. Then, the ATM dial authentication device 934 stores the extracted ATM_ID and the authentication telephone number in association with each other. In this case, the authentication telephone number correspondence table 441 includes ATM_ID instead of the authentication request ID 4411. Note that the ATM 9210 does not transmit a different authentication request to the ATM dial authentication device 934 before the processing for one authentication request is completed. Therefore, there is a one-to-one correspondence between ATM_ID and authentication telephone number. When the ATM dial authentication device 934 receives a dial from the mobile phone 60, the ATM dial authentication device 934 acquires the caller telephone number and the incoming telephone number of the dial. Next, the ATM dial authentication device 934 extracts the ATM_ID corresponding to the acquired incoming telephone number from the authentication telephone number correspondence table 441. Then, the ATM dial authentication device 934 transmits the authentication result to the ATM 9210 identified by the extracted ATM_ID. That is, the ATM dial authentication device 934 can transmit the authentication result without receiving an authentication result request from the ATM 9210.

Here, an application example of the fifth embodiment of the present invention will be described. An ATM dial authentication device 934 provided in the personal authentication system of the application example of the fifth embodiment also serves as a device for calculating a utility bill. In this case, the ATM dial authentication device 934 calculates a utility bill, issues a bill, and manages the payment status. For example, the public charges are telephone charges, mobile phone charges, electricity charges, gas charges, water charges, and the like. The ATM dial authentication device 934 stores the telephone number of the mobile phone 60 and the identifier of the user who receives the utility bill service in association with each other. The ATM dial authentication device 934 accepts a request for payment of a utility bill from a user of the ATM 9210. When the ATM dial authentication device 934 authenticates the user of the ATM 9210 as described above, the ATM dial authentication device 934 accepts from the ATM 9210 payment of the unpaid utility fee of the user of the mobile phone 60. Also, the ATM dial authentication device 934 receives a loan loan request from a user of the ATM 9210. When the ATM dial authentication device 934 authenticates the user of ATM 9210 as described above, the loan is lent out from ATM 9210. Note that the ATM dial authentication device 934 charges the loan together with the utility bill.

  In the fifth embodiment of the present invention, a non-overlapping authentication telephone number may be assigned in advance to each of all ATM 9210s. In this case, the correspondence between the ATM 9210 and the authentication telephone number is unchanged, and is stored in advance in the authentication telephone number correspondence table 441 or the like. Then, the ATM dial authentication device 934 can specify the ATM 9210 that is the transmission source of the user authentication request based on the incoming telephone number.

(Sixth embodiment)
The personal authentication system of the sixth embodiment will be described below, but the same reference numerals are used for the same portions as those of the personal authentication system of the first embodiment and the personal authentication system of the fifth embodiment. Omitted.

As a personal authentication system of the sixth embodiment, a specific embodiment in which the personal authentication system of the first embodiment is used for credit card payment at a store will be described. Conventionally, in a store credit card settlement, in order to prevent the use of impersonation, a store salesperson visually compares the signature of the usage slip with the signature on the back of the credit card. However, visual verification is not sufficient as an anti-spoofing measure. In the personal authentication system according to the sixth embodiment, an example in which a caller telephone number of a telephone is used instead of signature verification will be described.

FIG. 16 is a schematic configuration diagram of a personal authentication system according to the sixth embodiment. The personal authentication system shown in FIG. 16 includes a plurality of reader devices 9310, a plurality of mobile phones 60, a plurality of fixed phones 80, and a dial authentication device 4. The reader device 9310 is connected to the network 9. The reader device 9310 will be described in detail with reference to FIG. In a store, a store salesperson usually operates the reader device 9310. However, the user who is authenticated in the personal authentication system of the sixth embodiment is a credit card holder. Therefore, in order to simplify the description, in the description of this embodiment, the user of the reader device 9310 is assumed to be a credit card holder. The mobile phone 60 and the fixed phone 80 are telephones that send a dial accompanied by a caller phone number notification when operated by a user. The cellular phone 60 and the fixed phone 80 may be IP phones. In this case, the public switched telephone line network 2 is the Internet. The dial authentication device 4 is connected to the reader device 9310 via the network 9. The dial authentication device 4 is connected to a mobile phone 60 and a fixed phone 80 via the public switched telephone line network 2. For the sake of clarity, in the personal authentication system of the sixth embodiment, processing of one reader device 9310 and one mobile phone 60 will be described. In practice, the dial authentication device 4 authenticates a plurality of reader devices 9310 via the network 9. That is, the dial authentication device 4 can receive an authentication request and an authentication result request from the plurality of reader devices 9310. In practice, the dial authentication device 4 is connected to a plurality of mobile phones 60 via the public switched telephone network 2. In FIG. 16, three reader devices 9310 are shown, but any number of personal authentication systems may be provided. In FIG. 16, two mobile phones 60 and fixed phones 80 are shown, but any number of mobile phones 60 and fixed phones 80 may be provided in the personal authentication system.

FIG. 17 is a block diagram of a configuration of the reader device 9310 provided in the personal authentication system of the thirteenth embodiment. The reader device 9310 physically includes a transmission / reception unit 11, a central processing unit 12, a main storage device 13, an auxiliary storage device 14, an input device (not shown), a display device (not shown), a card information reading unit 16, and the like. Prepare. The transmission / reception unit 11 is an interface that is connected to the network 9 and transmits / receives data to / from an external device (dial authentication device 4). The central processing unit 12 is, for example, a CPU. The central processing unit 12 performs various processes by executing programs stored in the main storage device 13. The main storage device 13 is a memory, for example. The main storage device 13 stores programs executed by the central processing unit 12, information required by the central processing unit 12, and the like. The auxiliary storage device 14 is, for example, a hard disk. The auxiliary storage device 14 stores various information. The input device is, for example, a keyboard or a touch panel. Various information is input to the input device from the user. The display device is a display. On the display device, information instructed to be displayed by the central processing unit 12 is displayed. The card information reading unit 16 reads information stored in a credit card. The card information reading unit 16 provided in a general credit card card reader is sufficient. Note that the reader device 9310 does not necessarily include the auxiliary storage device 14.

The function of the reader device 9310 provided in the personal authentication system of the sixth embodiment is mainly the same as that of the client device 10 provided in the personal authentication system of the first embodiment. The reader device 9310 provided in the personal authentication system of the sixth embodiment has the following functions in addition to the functions of the client device 10 provided in the personal authentication system of the first embodiment. The reader device 9310 receives a credit card number and a settlement amount by a user operation. The reader device 9310 includes the accepted credit card number and settlement amount in the authentication request transmitted to the dial authentication device 4.

The function of the dial authentication device 4 provided in the personal authentication system of the sixth embodiment is mainly the same as that of the dial authentication device 4 provided in the personal authentication system of the first embodiment. The dial authentication device 4 provided in the personal authentication system of the sixth embodiment has the following functions in addition to the functions of the dial authentication device 4 provided in the personal authentication system of the first embodiment. The dial authentication device 4 of the sixth embodiment processes credit card credit examination and billing. The user management table 442 of the dial authentication device 4 includes a credit card number (not shown). The credit card number included in the user management table 442 is a credit card number owned by the user. That is, in the user management table 442, the credit card number and the user's telephone number are stored in advance in association with each other. The authentication telephone number correspondence table 441 of the dial authentication device 4 includes a settlement amount (not shown) and a credit card number (not shown). The settlement amount included in the authentication telephone number correspondence table 441 is an amount to be settled with a credit card. The credit card number included in the authentication telephone number correspondence table 441 is the number of the credit card that is about to be used for settlement.

Next, an outline of processing of the personal authentication method of the sixth embodiment will be described. The sequence diagram of the personal authentication method of the sixth embodiment is mainly the same as FIG. 8 which is the sequence diagram of the personal authentication method of the first embodiment. The reader device 9310 receives a payment amount in response to a user operation. Further, the card information reading unit 16 of the reader device 9310 reads the credit card number by the user's card operation. Next, reader apparatus 9310 transmits the accepted payment amount and the read credit card number to dial authentication apparatus 4 (ST211). Dial authentication apparatus 4 receives the authentication request (ST212). Next, the dial authentication device 4 extracts the payment amount and the credit card number from the received authentication request. Next, the dial authentication device 4 generates an authentication request ID (ST213). Next, dial authentication apparatus 4 selects an authentication telephone number (ST214). Next, dial authentication apparatus 4 stores the generated authentication request ID, the selected authentication telephone number, the extracted payment amount, and the extracted credit card number in association with authentication telephone number correspondence table 441 (ST215). Next, dial authentication device 4 transmits the generated authentication request ID and the selected authentication telephone number to reader device 9310 (ST216). Reader apparatus 9310 receives the authentication request ID and the authentication telephone number (ST217). Next, the reader device 9310 displays the received authentication telephone number on the display device. Note that the reader device 9310 may print the paper on which the authentication telephone number is written without displaying the authentication telephone number. That is, the reader device 9310 may use any method as long as it can notify the user of the authentication telephone number. The cellular phone 60 sends a dial including the caller phone number notification to the authentication phone number in response to the user's operation (ST218). Dial authentication apparatus 4 accepts an incoming dial call from mobile phone 60 (ST219). Next, the dial authentication device 4 acquires the caller telephone number and the incoming telephone number from the received dial. Next, the dial authentication device 4 stores the acquired caller telephone number in the authentication telephone number correspondence table 441 in association with the authentication request ID based on the acquired incoming telephone number (ST220). Specifically, the dial authentication device 4 selects from the authentication telephone number correspondence table 441 a record in which the acquired incoming telephone number matches the authentication telephone number 4412 of the authentication telephone number correspondence table 441. Next, the dial authentication device 4 stores the acquired caller telephone number in the user telephone number 4413 of the selected record. On the other hand, reader apparatus 9310 transmits an authentication result request to dial authentication apparatus 4 (ST221). Dial authentication apparatus 4 receives an authentication result request from reader apparatus 9310 (ST222). The dial authentication device 4 extracts an authentication request ID from the received authentication result request. Next, the dial authentication device 4 selects from the authentication telephone number correspondence table 441 a record in which the extracted authentication request ID matches the authentication request ID 4411 of the authentication telephone number correspondence table 441. Next, the dial authentication device 4 extracts the user telephone number 4413, the payment amount, and the credit card number from the selected record (ST223). Next, the dial authentication device 4 selects from the user management table 442 a record in which the extracted user telephone number 4413 matches the telephone number 4422 of the user management table 442. Next, the dial authentication device 4 extracts a credit card number from the selected record. Next, the dial authentication device 4 collates the credit card number extracted from the authentication telephone number correspondence table 441 with the credit card number extracted from the user management table 442. If the two extracted credit card numbers do not match, the dial authentication device 4 determines that authentication is not possible. On the other hand, if the two extracted credit card numbers match, the dial authentication device 4 performs a credit examination to determine whether or not the extracted payment amount can be used. Credit screening is the same as that performed when using a conventional credit card. If the credit check is satisfactory, the dial authentication device 4 charges the payment amount to the credit card. Note that the dial authentication device 4 may request a dedicated device for credit examination and billing processing. In this case, the dial authentication device 4 is connected via a network to a dedicated device that performs credit examination and billing. When the billing process is completed, the dial authentication device 4 determines that authentication is possible. Dial authentication device 4 transmits the result of authentication to reader device 9310 (ST224). The reader device 9310 receives the authentication result (ST225). Next, the reader device 9310 displays the authentication result on the display device.

As described above, in the personal authentication system of the sixth embodiment, the caller telephone number of the telephone can be used instead of the signature verification in the credit card settlement at the store. In the sixth embodiment, the credit card settlement has been described. However, the settlement means is not limited to a credit card as long as it is a means for making a settlement through authentication. For example, the settlement means is “Jay Debit” (trademark).

In the above-described embodiment, the authentication request transmitted by the reader device 9310 includes a credit card number. However, it may be as follows. The reader device 9310 may include the credit number in the authentication result request instead of the authentication request. In this case, the authentication telephone number correspondence table 441 of the dial authentication device 4 may not include a credit card number. The reader device 9310 transmits an authentication result request to the dial authentication device 4. The dial authentication device 4 receives an authentication result request from the reader device 9310. Next, the dial authentication device 4 extracts an authentication request ID from the received authentication result request. Next, the dial authentication device 4 selects from the authentication telephone number correspondence table 441 a record in which the extracted authentication request ID matches the authentication request ID 4411 of the authentication telephone number correspondence table 441. Next, the dial authentication device 4 extracts the user telephone number 4413 and the payment amount from the selected record. Next, the dial authentication device 4 selects from the user management table 442 a record in which the extracted user telephone number 4413 matches the telephone number 4422 of the user management table 442. Next, the dial authentication device 4 extracts a credit card number from the selected record. Next, the dial authentication device 4 collates the credit number extracted from the user management table 442 with the credit card included in the authentication result request. If the two credit card numbers match, the dial authentication device 4 performs a credit check and charges.

Here, a modification of the sixth embodiment of the present invention will be described. In the personal authentication system of the sixth embodiment, the reader device 9310 reads information on a credit card. However, in the modified example of the sixth embodiment, an example will be described in which credit card settlement can be executed without the reader device 9310 reading credit card information. That is, even if the user does not physically hold a credit card, credit card payment can be made at the store.

The authentication request transmitted by the reader device 9310 provided in the modification of the sixth embodiment does not include a credit card number. Further, the authentication telephone number correspondence table 441 of the dial authentication device 4 provided in the modification of the sixth embodiment does not include a credit card number.

The outline of the process of the modified example of the sixth embodiment will be described. The reader device 9310 transmits an authentication request to the dial authentication device 4 in response to a user operation. The dial authentication device 4 receives the authentication request. Next, the dial authentication device 4 extracts the payment amount from the received authentication request. Next, the dial authentication device 4 generates an authentication request ID. Next, the dial authentication device 4 selects an authentication telephone number. Next, the dial authentication device 4 stores the generated authentication request ID, the selected authentication telephone number, and the extracted settlement amount in association with the authentication telephone number correspondence table 441. Next, the dial authentication device 4 transmits the generated authentication request ID and the selected authentication telephone number to the reader device 9310. The reader device 9310 receives the authentication request ID and the authentication telephone number. Next, the reader device 9310 displays the received authentication telephone number on the display device. The mobile phone 60 sends a dial including a caller phone number notification to the authentication phone number in response to a user operation. Then, the dial authentication device 4 receives an incoming dial call from the mobile phone 60. Next, the dial authentication device 4 acquires the caller telephone number and the incoming telephone number from the received dial. Next, the dial authentication device 4 stores the acquired caller telephone number in the authentication telephone number correspondence table 441 in association with the authentication request ID based on the acquired incoming telephone number. On the other hand, the reader device 9310 transmits an authentication result request to the dial authentication device 4. The dial authentication device 4 receives an authentication result request from the reader device 9310. The dial authentication device 4 extracts an authentication request ID from the received authentication result request. Next, the dial authentication device 4 selects from the authentication telephone number correspondence table 441 a record in which the extracted authentication request ID matches the authentication request ID 4411 of the authentication telephone number correspondence table 441. Next, the dial authentication device 4 extracts the user telephone number 4413 and the payment amount from the selected record. Next, the dial authentication device 4 selects from the user management table 442 a record in which the extracted user telephone number 4413 matches the telephone number 4422 of the user management table 442. Next, the dial authentication device 4 extracts a credit card number from the selected record. Next, the dial authentication device 4 performs a credit examination on the extracted credit card number. The credit examination is a credit examination when using a conventional credit card. If the credit examination is satisfactory, the dial authentication device 4 charges the payment amount to the credit card. Note that the dial authentication device 4 may request a dedicated device for credit examination and billing processing. In this case, the dial authentication device 4 is connected via a network to a dedicated device that performs credit examination and billing. When the billing process is completed, the dial authentication device 4 determines that authentication is possible. The dial authentication device 4 transmits the authentication result to the reader device 9310. The reader device 9310 receives the authentication result. Next, the reader device 9310 displays the authentication result on the display device.

As described above, in the modification of the sixth embodiment, the user does not physically hold a credit card at the store. The user can make a credit card payment only by holding the mobile phone 60.

Here, an application example of the sixth embodiment of the present invention will be described. The dial authentication device 4 provided in the personal authentication system of the application example of the sixth embodiment also serves as a device for calculating a utility bill. That is, the dial authentication device 4 calculates a utility bill, issues a bill, and manages the payment status. For example, the public charges are telephone charges, mobile phone charges, electricity charges, gas charges, water charges, and the like. In the sixth embodiment, the user management table 442 of the dial authentication device 4 stores the correspondence between the phone number of the mobile phone 60 and the credit card number. In the application example of the modification of the sixth embodiment, the user management table 442 of the dial authentication device 4 stores the correspondence between the telephone number of the mobile phone 60 and the identifier of the user who receives the utility bill service. The dial authentication device 4 adds the payment amount at the store to the public bill instead of charging the credit card. As described above, the user of the reader device 9310 can complete payment at the store only by holding the mobile phone 60.

(Seventh embodiment)
In the following, an example in which a personal computer and a PDA are connected to an in-house intranet in the personal authentication system of the first embodiment will be described as the personal authentication system of the seventh embodiment. The same code | symbol is used for the location which overlaps with the personal authentication system of 1st Embodiment.

Many companies set up an internal intranet to encourage employees to communicate information while keeping internal information confidential. An employee connects a portable terminal such as a personal computer or a PDA to a company intranet by means of communication means such as dial-up or VPN for the purpose of browsing or updating company information from a destination or sending and receiving e-mail. Conventionally, an employee inputs a user ID and a password and connects to an in-house intranet. The user of the portable terminal receives authentication using the authentication method of the first embodiment, and connects the portable terminal to the in-house intranet. In this case, the client device 10 is a portable terminal that is about to be connected to an in-house intranet. The dial authentication device 4 is a management server that manages an in-house intranet. Employees can connect to the corporate intranet without entering a user ID and password. A user who intends to connect a portable terminal to an in-house intranet cannot receive personal authentication without both the portable terminal and the mobile phone 60. As a result, another person who has acquired only the portable terminal can not be authenticated by impersonating the user of the portable terminal. That is, even if the portable terminal is lost, information leakage can be prevented.

(Eighth embodiment)
The following describes an example in which a thin client device is connected to an in-house server in the personal authentication system of the first embodiment as the personal authentication system of the eighth embodiment. The same code | symbol is used for the location which overlaps with the personal authentication system of 1st Embodiment.

The thin client device is a personal computer having a minimum auxiliary storage device. Companies have introduced a thin client system in order to prevent information leakage due to theft or loss of personal computers. The auxiliary storage device of the thin client device does not store sufficient in-house data and applications. In-house data and applications are stored by the central server. The employee operates the thin client device to connect to the central server, and browses and updates data. Conventionally, an employee inputs a user ID and a password and connects to a centralized server. The user of the thin client device receives authentication using the authentication method of the first embodiment, and connects the thin client device to the in-house intranet. In this case, the client device 10 is a thin client device connected to the central server. The dial authentication device 4 is a management server that manages the connection between the thin client device and the server. The management server may be included in the central server. The employee can connect the thin client device to the central server without entering the user ID and password. A user who wants to connect a thin client device to an in-house intranet cannot receive personal authentication without both the thin client device and the mobile phone 60. As a result, another person who has acquired only the thin client device can impersonate the user of the thin client device and cannot be authenticated. That is, even if the thin client device is lost, information leakage can be prevented.

(Ninth embodiment)
In the following, an example of connecting a personal computer and a PDA to a public wireless LAN in the personal authentication system of the first embodiment will be described as the personal authentication system of the ninth embodiment. The same code | symbol is used for the location which overlaps with the personal authentication system of 1st Embodiment.

Public wireless LANs that connect to the Internet at the destination are widespread. Conventionally, a user of a public wireless LAN inputs a user ID and a password, and connects a portable terminal such as a personal computer and a PDA (PERSONAL DIGITAL ASSISTANCE) to an access point of the public wireless LAN. The user of the public wireless LAN is authenticated using the authentication method of the first embodiment, and connects the portable terminal to the access point. In this case, the client device 10 is a portable terminal to be connected to the access point. The dial authentication device 4 is a management server that manages the connection between the portable terminal and the access point. A public wireless LAN user can connect to an access point without entering a user ID and password. A user who wants to connect to the public wireless LAN cannot receive personal authentication without both the portable terminal and the mobile phone 60. As a result, another person who has acquired only the portable terminal can impersonate the user of the portable terminal and cannot connect to the public wireless LAN.

(Tenth embodiment)
Although the personal authentication system of the tenth embodiment will be described below, the same reference numerals are used for portions that overlap with the personal authentication system of the first embodiment, and description thereof is omitted.

The personal authentication system of the tenth embodiment uses a client ID that is an identifier of the client device 10 instead of the authentication request ID. Note that the personal authentication system of the tenth embodiment can be applied to any of the first to ninth personal authentication systems. Here, the case where it applies to the authentication system of 1st Embodiment is demonstrated.

The personal authentication system of the tenth embodiment is the same as the personal authentication system (FIG. 1) of the first embodiment except for the authentication telephone number correspondence table (FIG. 6) stored in the dial authentication device 4. is there.

FIG. 18 is a configuration diagram of the authentication telephone number correspondence table 20441 stored in the auxiliary storage device of the dial authentication device 4 according to the tenth embodiment. The authentication telephone number correspondence table 20441 includes a client ID 204411, an authentication telephone number 4412, and a user telephone number 4413. Since the authentication telephone number 4412 and the user telephone number are the same as those included in the authentication telephone number correspondence table (FIG. 6) of the first embodiment, the description thereof is omitted. The client ID 204411 is a unique identifier of the client device 10 provided in the personal authentication system. The client ID 204411 stores a client ID included in the authentication request transmitted from the client device 10.

Next, processing of the personal authentication system of the tenth embodiment will be described. Note that the description of the same processing as in the first embodiment is omitted. The client device 10 transmits an authentication request including its own client ID. Then, the dial authentication device 4 assigns an authentication telephone number to the client ID included in the received authentication request. Next, the dial authentication device 4 stores the correspondence between the client ID included in the received authentication request and the authentication telephone number assigned to the client ID in the authentication telephone number correspondence table 20441. Specifically, the dial authentication device 4 selects one authentication telephone number from the authentication telephone numbers 4431 in the authentication telephone number table 443. Next, the authentication telephone number selection module 434 generates a new record in the authentication telephone number correspondence table 20441. Next, the dial authentication device 4 stores the client ID included in the received authentication request in the client ID 204411 of the created new record. Further, the dial authentication device 4 stores the selected authentication telephone number in the authentication telephone number 4412 of the created new record.

Next, the dial authentication device 4 transmits the selected authentication telephone number to the client device 10 via the network 9. The client device 10 receives the authentication telephone number from the dial authentication device 4. Next, the client device 10 displays the received authentication telephone number on the display device.

The cellular phone 60 transmits a dial including the caller telephone number to the authentication telephone number via the public switched telephone line network 2 in response to a user operation. Then, the dial authentication device 4 accepts an incoming dial call from the mobile phone 60. Next, the dial authentication device 4 acquires the caller telephone number and the incoming telephone number from the received dial. Next, the dial authentication device 4 selects from the authentication telephone number correspondence table 20441 a record in which the acquired incoming telephone number matches the authentication telephone number 4412 of the authentication telephone number correspondence table 20441. Next, the dial authentication device 4 extracts the client ID 204411 from the selected record. Next, the dial authentication device 4 selects from the user management table 442 a record in which the acquired caller telephone number matches the telephone number 4422 of the user management table 442. Next, the dial authentication device 4 extracts the user ID 4421 from the selected record. The dial authentication device 4 determines that the authentication request transmitted from the client device 10 identified by the extracted client ID 204411 is from the user identified by the extracted user ID 4421. Therefore, the dial authentication device 4 determines whether to authenticate the user identified by the extracted user ID 4421. The dial authentication device 4 transmits the authentication result to the client device 10 identified by the extracted client ID 204411. In this case, the dial authentication device 4 can transmit the authentication result to the client device 10 without receiving the authentication result request.

Moreover, it may be as follows. Dial authentication device 4 accepts an incoming dial call from mobile phone 60. Next, the dial authentication device 4 acquires the caller telephone number and the incoming telephone number from the received dial. Next, the dial authentication device 4 selects from the authentication telephone number correspondence table 20441 a record in which the acquired incoming telephone number matches the authentication telephone number 4412 of the authentication telephone number correspondence table 20441. Next, the dial authentication device 4 stores the acquired caller telephone number in the user telephone number 4413 of the selected record.

On the other hand, the client device 10 transmits an authentication result request including its own client ID to the dial authentication device 4. The dial authentication device 4 selects from the authentication telephone number correspondence table 20441 a record in which the client ID included in the authentication result request matches the client ID 204411 of the authentication telephone number correspondence table 20441. Next, the dial authentication device 4 extracts the user telephone number 4413 from the selected record. And the dial authentication apparatus 4 determines an authentication result based on the extracted user telephone number 4413 similarly to 1st Embodiment. Specifically, if the user telephone number 4413 cannot be extracted, the dial authentication device 4 determines that authentication is not possible. On the other hand, when the user telephone number 4413 can be extracted, the dial authentication device 4 selects from the user management table 442 a record in which the extracted user telephone number 4413 matches the telephone number 4422 of the user management table 442 (FIG. 7). To do. The dial authentication device 4 determines that authentication is not possible when a record with a matching telephone number cannot be extracted. On the other hand, the dial authentication device 4 determines that authentication is possible when a record having a matching telephone number can be extracted. As a result, the dial authentication device 4 can identify the user who issued the authentication request. Specifically, the dial authentication device 4 extracts the user ID 4421 from the selected record. Then, the dial authentication device 4 specifies that the issuer of the authentication request transmitted from the client device 10 identified by the client ID included in the authentication result request is the user identified by the extracted user ID 4421. Note that the dial authentication device 4 may include user-specific information corresponding to the extracted user ID 4421 in the authentication result. The dial authentication device 4 transmits the authentication result to the client device 10 identified by the client ID included in the authentication result request via the network 9. The other processes in the tenth embodiment are the same as those in the first embodiment. Therefore, description of the same processing is omitted.

Further, in the tenth embodiment of the present invention, non-overlapping authentication telephone numbers may be assigned in advance to all the client apparatuses 10. In this case, the correspondence between the client device 10 and the authentication telephone number is unchanged, and is stored in advance in the authentication telephone number correspondence table 20441 or the like. Then, the dial authentication device 4 can identify the client device 10 that is the transmission source of the user authentication request based on the incoming telephone number.

It is a figure which shows schematic structure of the personal authentication system of 1st Embodiment. 2 is a block diagram of a configuration of a client device 10. FIG. 3 is a block diagram of a configuration of a dial authentication device 4. FIG. 3 is a functional block diagram of a dial authentication device 4. FIG. 4 is a configuration diagram of an authentication telephone number table 443 stored in an auxiliary storage device 34 of the dial authentication device 4. FIG. 4 is a configuration diagram of an authentication telephone number correspondence table 441 stored in an auxiliary storage device 34 of the dial authentication device 4. FIG. 4 is a configuration diagram of a user management table 442 stored in an auxiliary storage device 34 of the dial authentication device 4. FIG. It is a sequence diagram of a process of the personal authentication method of the first embodiment. It is a schematic block diagram of the personal authentication system of 2nd Embodiment. It is a functional block diagram of the dial authentication WEB apparatus 914. It is a sequence diagram of a process of the personal authentication method of the second embodiment. It is a schematic block diagram of the personal authentication system of 3rd Embodiment. It is a sequence diagram of a process of the personal authentication method of the third embodiment. It is a schematic block diagram of the personal authentication system of 5th Embodiment. It is a block diagram of a structure of ATM9210. It is a schematic block diagram of the personal authentication system of 6th Embodiment. 3 is a block diagram of a configuration of a reader device 9310. FIG. It is a block diagram of the authentication telephone number corresponding | compatible table 20441 memorize | stored in the auxiliary storage device 34 of the dial authentication apparatus 4 of 10th Embodiment.

Explanation of symbols

2 Public Switched Telephone Line Network 4 Dial Authentication Device 5 Introduced WEB Server 9 Network 10 Client Device 11 Transmission / Reception Unit 12 Central Processing Unit 13 Main Storage Device 14 Auxiliary Storage Device 15 Cash Handling Unit 16 Card Information Reading Unit 20441 Authentication Phone Number Correspondence Table 204411 Client ID
31 Transmission / Reception Unit 32 Central Processing Unit 33 Main Storage Unit 34 Auxiliary Storage Unit 400 Authentication Program 431 Main Module 433 Authentication Request ID Generation Module 434 Authentication Phone Number Selection Module 435 Authentication Phone Number Transmission Module 436 Dial Incoming Module 437 Phone Number Reading Module 438 Authentication module 439 Authentication result transmission module 441 Authentication telephone number correspondence table 442 User management table 443 Authentication telephone number table 4321 Authentication request reception module 4322 Authentication result request reception module 4411 Authentication request ID
4412 Authentication phone number 4413 User phone number 4421 User ID
4422 Telephone number 4431 Authentication telephone number 4432 Allocation flag 60 Mobile phone 80 Fixed telephone 9110 Client device 914 Dial authentication WEB device 91400 Authentication program 91435 Authentication telephone number transmission module 91439 Authentication result transmission module 9160 Mobile phone 9180 Fixed telephone 9210 ATM
934 ATM Dial Authentication Device 9310 Reader Device 954 Dial Authentication WEB Device

Claims (41)

An authentication system comprising: a plurality of client computers including a processor, a memory, and an interface; and an authentication computer that is connected to the plurality of client computers via a network and includes a processor, a memory, and an interface.
The authentication computer is
Storing user information indicating correspondence between the user and the telephone number of the user;
Upon receiving an authentication request from the client computer, a telephone number that is not assigned to any of the plurality of client computers among telephone numbers that can be received by the authentication computer is a client that is a transmission source of the received authentication request Assigned to the calculator,
Storing the correspondence between the client computer that is the transmission source of the received authentication request and the telephone number assigned to the client computer in the authentication telephone number correspondence information;
When a dial is received, the caller telephone number and the incoming telephone number of the incoming dial are specified,
With reference to the user information, a user corresponding to the specified caller telephone number is specified,
With reference to the authentication telephone number correspondence information, a client computer corresponding to the identified incoming telephone number is identified,
An authentication system, wherein an authentication request received from the specified client computer determines that authentication is requested by the specified user. An authentication system comprising: a plurality of client computers including a processor, a memory, and an interface; and an authentication computer that is connected to the plurality of client computers via a network and includes a processor, a memory, and an interface.
The authentication computer is
Storing user information indicating correspondence between the user and the user's telephone number;
When receiving an authentication request from the client computer, among the phone numbers that can be received by the authentication computer, a phone number that is not assigned to any of the previously received authentication requests is assigned to the received authentication request,
Storing the correspondence between the received authentication request and the telephone number assigned to the authentication request in the authentication telephone number correspondence information;
When a dial is received, the caller telephone number and the incoming telephone number of the incoming dial are specified,
With reference to the user information, a user corresponding to the specified caller telephone number is specified,
Referring to the authentication telephone number correspondence information, an authentication request corresponding to the specified incoming telephone number is identified,
An authentication system, wherein the specified authentication request determines that authentication is requested by the specified user. An authentication system comprising: a plurality of client computers comprising a processor, a memory and an interface; and an authentication computer connected to the plurality of client computers via a network and comprising a processor, a memory and an interface,
The authentication computer is
Storing user information indicating correspondence between the user and the user's telephone number;
The correspondence between the client computer and a telephone number assigned to the client computer so as not to overlap with other client computers among the telephone numbers that can be received by the authentication computer is stored in the authentication telephone number correspondence information. ,
Receiving an authentication request from the client computer;
When a dial is received, the caller telephone number and the incoming telephone number of the incoming dial are specified,
With reference to the user information, a user corresponding to the specified caller telephone number is specified,
With reference to the authentication telephone number correspondence information, a client computer corresponding to the identified incoming telephone number is identified,
An authentication system, wherein an authentication request received from the specified client computer determines that authentication is requested by the specified user. The authentication computer is
When a certain amount of time has passed since the phone number was assigned, the phone number will be unassigned,
The authentication system according to claim 1 or 2, wherein the telephone number that has been deallocated is reassigned. The authentication computer transmits the assigned telephone number to a client computer that is a transmission source of the authentication request,
The authentication system according to any one of claims 1 to 3, wherein the client computer outputs a telephone number received from the authentication computer. The client computer sends an authentication result request including the telephone number received from the authentication computer to the authentication computer;
When the authentication computer receives the authentication result request from the client computer, the authentication computer extracts a telephone number from the received authentication result request,
Determining whether the extracted telephone number is a dialed incoming telephone number;
When receiving the dial, referring to at least one of the user information and the authentication telephone number correspondence information, determine the result of the received authentication request,
6. The authentication system according to claim 5, wherein the determination result is transmitted to a client computer that is a transmission source of the received authentication result request.   If the authentication computer cannot identify the user corresponding to the identified caller telephone number with reference to the user information, the authentication computer determines that the result of the authentication request received from the identified client computer is unauthenticated. The authentication system according to claim 1 or 3, wherein   If the authentication computer cannot identify a user corresponding to the identified caller telephone number with reference to the user information, the authentication computer determines that the result of the identified authentication request is unauthenticated. The authentication system according to claim 2.   If the authentication computer cannot identify a user corresponding to the specified caller telephone number with reference to the user information, the authentication computer uses the specified caller telephone number as a new user telephone number in the user information. The authentication system according to claim 1, wherein the authentication system is stored. The authentication computer is
Refer to at least one of the user information and the authentication telephone number correspondence information, determine the result of the received authentication request,
The authentication system according to claim 1, wherein the determination result is transmitted to the identified client computer. The authentication computer is
Refer to at least one of the user information and the authentication telephone number correspondence information, determine the result of the received authentication request,
The authentication system according to claim 2, wherein the determination result is transmitted to a client computer that is a transmission source of the specified authentication request. The authentication computer is
When an authentication result request including an identifier of the client computer that is the transmission source of the authentication request is received from the client computer, the identifier of the client computer is extracted from the received authentication result request,
Referring to at least one of the user information and the authentication telephone number correspondence information to determine the result of the authentication request received from the client computer identified by the extracted identifier;
4. The authentication system according to claim 1, wherein the determined result is transmitted to a client computer that is a transmission source of the received authentication result request. The authentication computer is
When an authentication request is received from the client computer, an identifier of the received authentication request is generated,
Sending the generated authentication request identifier to the client computer;
Receiving an authentication result request including an identifier of the authentication request from the client computer;
Extract the authentication request identifier from the received authentication result request,
Referring to at least one of the user information and the authentication telephone number correspondence information to determine a result of the authentication request identified by the extracted identifier;
The authentication system according to claim 2, wherein the determination result is transmitted to a client computer that is a transmission source of the received authentication result request. The user information further includes a correspondence between the user and information unique to the user,
The authentication computer is
Referring to the user information to identify unique information corresponding to the identified user;
Receiving user-specific information from the client computer;
4. The method according to claim 1, wherein when the specified unique information matches the received unique information, the result of the received authentication request is determined to be authentic. 5. Authentication system.   15. The authentication system according to claim 14, wherein the unique information of the user includes at least one of a user identifier, a personal identification number, a card number owned by the user, and a user's biometric information. And a WEB computer for transmitting a WEB page to the client computer.
The authentication system according to claim 1 or 2, wherein the authentication computer processes an authentication request for the client computer to access the WEB computer. The user information further includes correspondence between the user and the user's credit card,
The authentication computer is
Refer to at least one of the user information and the authentication telephone number correspondence information, determine the result of the received authentication request,
When it is determined that the received authentication request result can be authenticated, the credit card corresponding to the identified user is identified with reference to the user information,
Perform credit examination for the identified credit card,
The authentication system according to any one of claims 1 to 3, wherein the credit card is permitted to be settled if the credit examination result is good. The user information further includes a correspondence between the user and the user's account,
The authentication computer is
Refer to at least one of the user information and the authentication telephone number correspondence information, determine a result of the received authentication request, and determine that the received authentication request can be authenticated, refer to the user information, Identify an account corresponding to the identified user;
The authentication system according to claim 1, wherein a transaction for the specified account is executed.   4. The authentication system according to claim 1, wherein the client computer is any one of a personal computer, a reader device that reads card information, and an ATM.   The authentication system according to claim 1, wherein the authentication computer is a WEB server. An authentication computer connected to a plurality of client computers via a network and comprising a processor, a memory and an interface,
The processor is
Storing user information indicating correspondence between the user and the user's telephone number;
When an authentication request is received from the client computer, a telephone number that is not assigned to any of the plurality of client computers among telephone numbers that can be received by the authentication computer is a client that is a transmission source of the received authentication request Assigned to the calculator,
Storing the correspondence between the client computer that is the transmission source of the received authentication request and the telephone number assigned to the client computer in the authentication telephone number correspondence information;
When a dial is received, the caller telephone number and the incoming telephone number of the incoming dial are specified,
With reference to the user information, a user corresponding to the specified caller telephone number is specified,
With reference to the authentication telephone number correspondence information, a client computer corresponding to the identified incoming telephone number is identified,
An authentication computer, wherein an authentication request received from the specified client computer determines that authentication is requested by the specified user. An authentication computer connected to a plurality of client computers via a network and comprising a processor, a memory and an interface,
The processor is
Storing user information indicating correspondence between the user and the user's telephone number;
When receiving an authentication request from the client computer, among the phone numbers that can be received by the authentication computer, a phone number that is not assigned to any of the previously received authentication requests is assigned to the received authentication request,
Storing the correspondence between the received authentication request and the telephone number assigned to the authentication request in the authentication telephone number correspondence information;
When a dial is received, the caller telephone number and the incoming telephone number of the incoming dial are specified,
With reference to the user information, a user corresponding to the specified caller telephone number is specified,
Referring to the authentication telephone number correspondence information, an authentication request corresponding to the specified incoming telephone number is identified,
In the specified authentication request, it is determined that authentication is requested by the specified user. An authentication computer connected to a plurality of client computers via a network and comprising a processor, a memory and an interface,
The processor is
Storing user information indicating correspondence between the user and the user's telephone number;
The correspondence between the client computer and the telephone number that can be received by the authentication computer and the telephone number assigned to the client computer so as not to overlap with other client computers is stored in the authentication telephone number correspondence information. ,
Receiving an authentication request from the client computer;
When a dial is received, the caller telephone number and the incoming telephone number of the incoming dial are specified,
With reference to the user information, a user corresponding to the specified caller telephone number is specified,
With reference to the authentication telephone number correspondence information, a client computer corresponding to the identified incoming telephone number is identified,
An authentication computer, wherein an authentication request received from the specified client computer determines that authentication is requested by the specified user. The processor is
When a certain amount of time has passed since the phone number was assigned, the phone number will be unassigned,
23. The authentication computer according to claim 21, wherein the telephone number that has been deallocated is reassigned. The processor transmits the assigned telephone number to a client computer that is a transmission source of the authentication request;
24. The authentication computer according to claim 21, wherein the client computer is instructed to output the transmitted telephone number. The processor receives an authentication result request including the transmitted telephone number from the client computer,
Extract the phone number from the received authentication result request,
Determining whether the extracted telephone number is a dialed incoming telephone number;
When receiving the dial, referring to at least one of the user information and the authentication telephone number correspondence information, determine the result of the received authentication request,
26. The authentication computer according to claim 25, wherein the determined result is transmitted to a client computer that is a transmission source of the received authentication result request.   The processor determines that the result of the authentication request received from the specified client computer is not authenticable when the user corresponding to the specified caller telephone number cannot be specified with reference to the user information. 24. The authentication computer according to claim 21 or 23.   The processor determines that the result of the specified authentication request is unauthenticated when the user corresponding to the specified caller telephone number cannot be specified with reference to the user information. Item 23. The authentication computer according to Item 22.   When the processor cannot identify a user corresponding to the identified caller telephone number with reference to the user information, the processor stores the identified caller telephone number as a new user telephone number in the user information. The authentication computer according to any one of claims 21 to 23, wherein: The processor is
Refer to at least one of the user information and the authentication telephone number correspondence information, determine the result of the received authentication request,
The authentication computer according to claim 21 or 23, wherein the determination result is transmitted to the identified client computer. The processor is
Refer to at least one of the user information and the authentication telephone number correspondence information, determine the result of the received authentication request,
The authentication computer according to claim 22, wherein the determination result is transmitted to a client computer that is a transmission source of the specified authentication request. The processor is
When an authentication result request including an identifier of the client computer that is the transmission source of the authentication request is received from the client computer, the identifier of the client computer is extracted from the received authentication result request,
Referring to at least one of the user information and the authentication telephone number correspondence information to determine the result of the authentication request received from the client computer identified by the extracted identifier;
24. The authentication computer according to claim 21, wherein the determined result is transmitted to a client computer that is a transmission source of the received authentication result request. The processor is
When an authentication request is received from the client computer, an identifier of the received authentication request is generated,
Sending the generated authentication request identifier to the client computer;
Receiving an authentication result request including an identifier of the authentication request from the client computer;
Extract the authentication request identifier from the received authentication result request,
Referring to at least one of the user information and the authentication telephone number correspondence information to determine a result of the authentication request identified by the extracted identifier;
The authentication computer according to claim 22, wherein the determination result is transmitted to a client computer that is a transmission source of the received authentication result request. The user information further includes a correspondence between the user and information unique to the user,
The processor is
Referring to the user information to identify unique information corresponding to the identified user;
Receiving user-specific information from the client computer;
24. When the specified unique information matches the received unique information, the result of the received authentication request is determined to be authenticable. 24. Authentication calculator.   35. The authentication computer according to claim 34, wherein the unique information of the user includes at least one of a user identifier, a personal identification number, a card number owned by the user, and user biometric information. And connected to a WEB computer that transmits a WEB page to the client computer,
The authentication computer according to claim 21 or 22, wherein the processor processes an authentication request for the client computer to access the WEB computer. The user information further includes correspondence between the user and the user's credit card,
The processor is
Refer to at least one of the user information and the authentication telephone number correspondence information, determine the result of the received authentication request,
When it is determined that the received authentication request result can be authenticated, the credit card corresponding to the identified user is identified with reference to the user information,
Perform credit examination for the identified credit card,
The authentication computer according to any one of claims 21 to 23, wherein if the result of the credit examination is good, the credit card settlement is permitted. The user information further includes a correspondence between the user and the user's account,
The processor is
Refer to at least one of the user information and the authentication telephone number correspondence information, determine a result of the received authentication request, and determine that the received authentication request can be authenticated, refer to the user information, Identify an account corresponding to the identified user;
The authentication computer according to claim 21 or 22, wherein a transaction for the specified account is executed. A program connected to a plurality of client computers via a network and executed by an authentication computer having a processor, a memory and an interface,
Storing user information indicating correspondence between the user and the telephone number of the user;
When an authentication request is received from the client computer, a telephone number that is not assigned to any of the plurality of client computers among telephone numbers that can be received by the authentication computer is a client that is a transmission source of the received authentication request Assigning it to a calculator,
Storing the correspondence between the client computer that is the transmission source of the received authentication request and the telephone number assigned to the client computer in the authentication telephone number correspondence information;
When a dial is received, a step of identifying a caller telephone number and an incoming telephone number of the received dial;
Identifying the user corresponding to the identified caller telephone number with reference to the user information;
Identifying a client computer corresponding to the specified incoming telephone number with reference to the authentication telephone number correspondence information;
And determining in the authentication request received from the specified client computer that authentication is requested by the specified user. A program connected to a plurality of client computers via a network and executed by an authentication computer having a processor, a memory and an interface,
Storing user information indicating correspondence between the user and the telephone number of the user;
When receiving an authentication request from the client computer, among the phone numbers that can be received by the authentication computer, assigning to the received authentication request a phone number that is not assigned to any of the previously received authentication requests;
Storing the correspondence between the received authentication request and the telephone number assigned to the authentication request in authentication telephone number correspondence information;
When a dial is received, a step of identifying a caller telephone number and an incoming telephone number of the received dial;
Identifying the user corresponding to the identified caller telephone number with reference to the user information;
Identifying an authentication request corresponding to the specified incoming telephone number with reference to the authentication telephone number correspondence information;
Determining in the specified authentication request that authentication is requested by the specified user. A program connected to a plurality of client computers via a network and executed by an authentication computer having a processor, a memory and an interface,
Storing user information indicating correspondence between the user and the telephone number of the user;
The correspondence between the client computer and the telephone number assigned to the client computer so as not to overlap with other client computers among the telephone numbers that can be received by the authentication computer is stored in the authentication telephone number correspondence information. Steps,
Receiving an authentication request from the client computer;
When a dial is received, a step of identifying a caller telephone number and an incoming telephone number of the received dial;
Identifying the user corresponding to the identified caller telephone number with reference to the user information;
Identifying a client computer corresponding to the specified incoming telephone number with reference to the authentication telephone number correspondence information;
And determining in the authentication request received from the specified client computer that authentication is requested by the specified user.

Images