WO2018207781A1

WO2018207781A1 - Information processing system

Info

Publication number: WO2018207781A1
Application number: PCT/JP2018/017801
Authority: WO
Inventors: 大河　克好
Original assignee: 合同会社Ｆｏｍ研究所
Priority date: 2017-05-08
Filing date: 2018-05-08
Publication date: 2018-11-15
Also published as: JP2020112839A

Abstract

The purpose of the present invention is to provide a technology which enables, in a payment process performed by a digital method, reduction of such risks as breach of personal information. A service code acquisition unit 102 of a user terminal 2 acquires an authentication service code generated in a storefront terminal 1. A C-OTID generation unit 104 generates a C-OTID indicating that the user terminal 2 is a legitimate terminal whereto a given service is applicable. A user terminal information generation unit 106 generates user terminal information. A user authentication unit 203 of an authentication server 3 acquires the user terminal information transmitted from the user terminal 2 and carries out authentication of a user. On the basis of the result of the authentication of the user, a user parameter conversion unit 204 generates a user parameter indicating the result of the authentication of the user. An authentication server information transmission control unit 205 transmits to a payment server the authentication service code and user parameter as authentication server information to be executed by the storefront terminal, payment server, user terminal, and authentication server.

Description

Information processing system

The present invention relates to an information processing system.

Conventionally, for example, an electronic settlement method using a credit card or the like has been widely used.
Such an electronic settlement method is very convenient for the user, but risks such as leakage of personal information and unauthorized settlement are inherent. Therefore, how to secure such security by eliminating such risks in the electronic settlement method is a big issue.
In this regard, for example, a technique for preventing unauthorized use of a credit card has been proposed (see, for example, Patent Document 1).

Japanese Patent Laying-Open No. 2015-152952

However, according to the prior art including the technique of Patent Document 1 described above, for example, it is not possible to avoid the process of transmitting the user's personal information to the terminal of a store that performs settlement.
That is, since the user's personal information is always transmitted to the store terminal once, the user's personal information is inevitably stored in the store terminal.
Therefore, the personal information of the user stored in the terminal of the store may be abused by employees of the store, or the personal information may be leaked from the store terminal.

This invention is made in view of such a situation, and it aims at reducing the risk of personal information leakage etc. in the settlement process by an electronic method.

In order to achieve the above object, an information processing system according to one embodiment of the present invention includes:
A request source device managed by a service request source that requests settlement as an authentication service;
A user terminal managed by a user executing the authentication service;
An authentication server for authenticating the user;
A payment server for executing a payment process for the user;
In an information processing system including
The user terminal is
Service code acquisition means for acquiring an authentication service code used as a general authentication code for the user to execute the authentication service from the request source device;
First authenticator generating means for generating a first one-time authenticator indicating that the user terminal is authentic;
First transmission information generation for generating an encrypted password by encrypting the input password, and generating first transmission information including the encrypted password, the authentication service code, and the first one-time authenticator Means,
First transmission control means for performing control to transmit the first transmission information to the authentication server;
With
The authentication server is
First reception control means for performing control to receive the first transmission information from the user terminal;
Based on the password obtained by decrypting the encrypted password included in the first transmission information and the first one-time authenticator included in the first transmission information, a user parameter indicating the authentication result of the user is generated. User authentication means for
Second transmission control means for performing control to transmit the second transmission information including the authentication service code included in the first transmission information and the user parameter to the settlement server;
Is provided.

The information processing apparatus and program of one embodiment of the present invention are also provided as an apparatus and program corresponding to the information processing system of one embodiment of the present invention.

According to the present invention, it is possible to reduce risks such as leakage of personal information in settlement processing by an electronic method.

It is a figure which shows the structure of the information processing system which concerns on 1st Embodiment of this invention. It is a block diagram which shows an example of the hardware constitutions of a user terminal among the information processing systems of FIG. It is a block diagram which shows an example of the hardware constitutions of an authentication server among the information processing systems of FIG. It is a functional block diagram which shows an example of a functional structure for performing a payment assistance process among the functional structures of the user terminal of FIG. 2, and the authentication server of FIG. It is a figure which shows the outline | summary of the flow of the payment assistance process performed by the user terminal, authentication server, etc. of FIG. FIG. 5 is an arrow chart showing a flow of settlement support processing executed by the user terminal and the authentication server in FIG. 4. FIG. 7 is a flowchart for explaining a detailed flow of a series of processes mainly executed in the user terminal of FIG. 2 among the settlement support processes of FIGS. 5 and 6. 7 is a flowchart for explaining a detailed flow of a series of processing mainly executed by the authentication server of FIG. 3 in the settlement support processing of FIG. 5 and FIG. 6. 7 is a flowchart for explaining a detailed flow of a series of processes mainly executed in the settlement server of FIG. 1 among the settlement support processes of FIGS. 5 and 6. 5 and 6 is a series of processes mainly executed by the store terminal, the payment server, and the user terminal of FIG. 2 in the process P4-4, the process P4-2, and the process. It is a flowchart explaining the detailed flow of the process after P4-1. It is an example of the composition of the information processing system concerning a 2nd embodiment of the present invention, and is a figure showing the 2nd embodiment of the present invention. It is a functional block diagram which shows an example of a functional structure of the shop terminal of FIG. 11, a payment server, a user terminal, and an authentication server, and is a figure which shows an example different from the example of FIG. It is a figure which shows the outline | summary of the flow of the payment assistance process performed by the shop terminal of FIG. 12, a payment server, a user terminal, and an authentication server. It is an arrow chart which shows the flow of the payment assistance process performed by the shop terminal of FIG. 12, a payment server, a user terminal, and an authentication server, and is a figure which shows an example different from the example of FIG. FIG. 15 is a flowchart for explaining a detailed flow of a series of processing mainly executed in the user terminal of FIG. 11 among the settlement support processing of FIG. 13 and FIG. 14, and is a diagram showing an example different from FIG. . FIG. 15 is a flowchart for explaining a detailed flow of a series of processes mainly executed in the authentication server of FIG. 11 among the settlement support processes of FIG. 13 and FIG. 14, and is a diagram showing an example different from FIG. . FIG. 15 is a flowchart for explaining a detailed flow of a series of processing mainly executed in the user terminal of FIG. 11 among the settlement support processing of FIG. 13 and FIG. 14, and is a diagram showing an example different from FIG. . It is a flowchart explaining the flow of the payment result display process performed by the shop terminal of FIG. 12, a payment server, and a user terminal, and is a figure which shows an example different from FIG. It is a figure which shows the structure of the information processing system which concerns on 3rd Embodiment of this invention.

[First embodiment]
Hereinafter, a first embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram showing an overview of an information processing system according to the first embodiment of the present invention.

The information processing system shown in FIG. 1 includes a store terminal 1, a user terminal 2, an authentication server 3, and a settlement server 4.
The store terminal 1, the user terminal 2, the authentication server 3, and the settlement server 4 are connected to each other via a predetermined network N such as the Internet.
In addition, about the number of each of the shop terminal 1, the user terminal 2, the authentication server 3, and the payment server 4, any number of 1 or more may be sufficient.

The store terminal 1 is managed in a store that provides products or services (hereinafter referred to as “product etc.”) to the user, and generates an authentication service code.
The store is a trader or the like that provides a product or the like to the user on condition that the user pays for the payment.
The authentication service code refers to a general-purpose authentication code for a user to execute a payment service for a product or the like (hereinafter referred to as “this service”).

The user terminal 2 is operated by the user and has the authentication server 3 authenticate that the apparatus is an application target of the service, and requests the payment service 3 to execute the service (execution of payment). .
That is, the user operates the user terminal 2 to execute this service (execution of settlement) and receives provision of goods and the like from the store.

As described above, the authentication server 3 authenticates whether or not the user terminal 2 is legitimate as a device to which this service is applied, and notifies the settlement server 4 of the result of the authentication.
The settlement server 4 is managed by various settlement parties such as a credit company and executes this service (execution of settlement) based on the authentication result transmitted from the authentication server 3.

FIG. 2 is a block diagram showing an example of the hardware configuration of the user terminal 2 in the information processing system of FIG.

The user terminal 2 is configured with a smartphone or the like.
The user terminal 2 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a bus 14, an input / output interface 15, a touch operation input unit 16, a display A unit 17, an input unit 18, a storage unit 19, a communication unit 20, and a drive 21 are provided.

The CPU 11 executes various processes according to a program recorded in the ROM 12 or a program loaded from the storage unit 19 to the RAM 13.
The RAM 13 appropriately stores data necessary for the CPU 11 to execute various processes.

The CPU 11, ROM 12 and RAM 13 are connected to each other via a bus 14. An input / output interface 15 is also connected to the bus 14. A touch operation input unit 16, a display unit 17, an input unit 18, a storage unit 19, a communication unit 20, and a drive 21 are connected to the input / output interface 15.

The touch operation input unit 16 includes, for example, a capacitance type or resistive film type (pressure sensitive) position input sensor stacked on the display surface of the display unit 17, and detects the coordinates of the position where the touch operation is performed.
Here, the touch operation refers to an operation of contacting or approaching an object with respect to the touch operation input unit 16. The object that contacts or approaches the touch operation input unit 16 is, for example, a user's finger or a touch pen. For example, in the present embodiment, the user inputs a password by a touch operation.
The display unit 17 is configured by a display such as a liquid crystal display, and displays various images such as an image showing a settlement result.
Thus, in this embodiment, the touch operation input unit 16 and the display unit 17 constitute a touch panel.

The input unit 18 is configured by various hardware and the like, and inputs various information according to a user's instruction operation.
The memory | storage part 19 is comprised by DRAM (Dynamic Random Access Memory) etc., and memorize | stores various data.
The communication unit 20 controls communication with other devices (such as the authentication server 3 and the settlement server 4 in the example of FIG. 1) via the network N including the Internet.

The drive 21 is provided as necessary. A removable medium 22 made of a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is appropriately attached to the drive 21. The program read from the removable medium 22 by the drive 21 is installed in the storage unit 19 as necessary. The removable medium 22 can also store various data stored in the storage unit 19 in the same manner as the storage unit 19.

FIG. 3 is a block diagram showing an example of the hardware configuration of the authentication server in the information processing system of FIG.

The authentication server 3 includes a CPU 31, a ROM 32, a RAM 33, a bus 34, an input / output interface 35, an output unit 36, an input unit 37, a storage unit 38, a communication unit 39, and a drive 40. Yes.
Since the configuration of the authentication server 3 is the same as the configuration excluding the touch panel of the user terminal 2 in FIG. 2, the description thereof is omitted here.
Further, since the store terminal 1 and the settlement server 4 in FIG. 1 are the same as the configuration of the authentication server 3, the description thereof is omitted here.

Various kinds of processing such as payment support processing can be executed by cooperation of various hardware and software of the store terminal 1, user terminal 2, authentication server 3, and payment server 4. The payment support process refers to various processes such as user authentication for supporting the payment process when the store provides products to the user.
4 is a functional block diagram illustrating an example of a functional configuration for executing the settlement support process among the functional configurations of the user terminal of FIG. 2 and the authentication server of FIG.

As shown in FIG. 4, in the CPU 11 of the user terminal 2, the upper request unit 101, service code acquisition unit 102, PW input unit 103, C-OTID generation unit 104, PW encryption unit 105, user The terminal information generation unit 106, the user terminal information transmission control unit 107, the server authentication unit 108, the authentication seed update unit 109, the settlement result acquisition unit 110, and the presentation unit 111 function.

The upper request unit 101 executes an upper request to the settlement server 4. Here, the upper request means requesting the settlement server 4 to receive the settlement result.

The service code acquisition unit 102 acquires an authentication service code generated at the store terminal 1.
Here, the method for acquiring the authentication service code is not particularly limited.
For example, a QR code (registered trademark) indicating an authentication service code is displayed on a display unit (not shown) of the store terminal 1, and a display unit (not shown) of the user terminal 2 includes the QR code (registered trademark). You may employ | adopt the method of acquiring an authentication service code by imaging.
Further, for example, a method of acquiring the authentication service code from the store terminal 1 using near field communication such as NFC (Near Field Communication) (registered trademark) may be adopted.
The user terminal 2 transmits this authentication service code to the settlement server 4 via the authentication server 3 as information for specifying a store for settlement. Thereby, since transmission / reception of the user's personal information at the time of payment becomes unnecessary between the user terminal 2 and the store terminal 1, the possibility that personal information at the time of payment leaks from the store terminal 1 is reduced.

The PW input unit 103 accepts input of a password from the user via the touch panel.

The C-OTID generation unit 104 updates the one-time ID, for example, at the time of execution of the previous settlement as an authenticator indicating to the authentication server 3 that the user terminal 2 is legitimate as a device to which this service is applied. Generated based on the authentication seed and the common encryption key.
As will be described later, since the authentication server 3 also generates a one-time ID, the one-time ID generated by the C-OTID generation unit 104 is hereinafter referred to as “C-OTID” to be distinguished from this. .

The PW encryption unit 105 generates an encrypted password by encrypting the password received by the PW input unit 103 by a predetermined method.

The user terminal information generation unit 106 receives the encrypted password generated by the PW encryption unit 105, the authentication service code acquired by the service code acquisition unit 102, and the C-OTID generated by the C-OTID generation unit 104. The information to be included is generated as user terminal information.

The user terminal information transmission control unit 107 executes control for transmitting the user terminal information generated by the user terminal information generation unit 106 to the authentication server 3 via the communication unit 20.

In this way, user terminal information (particularly C-OTID and encrypted password) transmitted from the user terminal 2 to the authentication server 3 is used in the authentication server 3 for various processes such as user authentication.
In the authentication server 3, an S-OTID described later is generated and transmitted to the user terminal 2.
Therefore, the server authentication unit 108 acquires the S-OTID and the updated authentication seed information via the communication unit 20, and authenticates the authentication server 3 based on the acquired S-OTID.
The authentication seed update unit 109 updates the authentication seed based on the result authenticated by the server authentication unit 108.

The settlement result acquisition unit 110 receives the upper request from the upper request unit 101 described above, and acquires the result of the settlement process transmitted from the settlement server 4 via the communication unit 20. The presentation unit 111 presents the result of the payment process acquired by the payment result acquisition unit 110 to the user by causing the display unit 17 to display the result.

Next, a functional configuration provided in the authentication server 3 will be described.
In the authentication server 3, a user terminal information acquisition unit 201, a decryption unit 202, a user authentication unit 203, a user parameter conversion unit 204, an authentication server information transmission control unit 205, and an S-OTID generation update unit 206 are provided. Function.
A UPDB (user parameter database) 301 is provided in one area of the storage unit 38 of the authentication server 3.

The user terminal information acquisition unit 201 acquires user terminal information transmitted from the user terminal 2 via the communication unit 39.
The decryption unit 202 decrypts the password described above from the encrypted password included in the user terminal information acquired by the user terminal information acquisition unit 201.

Based on the password decrypted by the decryption unit 202 and the C-OTID included in the user terminal information acquired by the user terminal information acquisition unit 201, the user authentication unit 203 can apply the service to the user terminal 2. Is authenticated (hereinafter, referred to as “user authentication” as appropriate).

The user parameter conversion unit 204 generates a parameter indicating the result of user authentication by the user authentication unit 203 as a user parameter and stores it in the UPDB 301.
The form of the user parameter is not particularly limited as long as it indicates the result of user authentication. Specific examples of user parameters employed in the present embodiment will be described later with reference to FIGS.

The authentication server information transmission control unit 205 uses information including the authentication service code and the user parameters generated by the user parameter conversion unit 204 among the user terminal information acquired by the user terminal information acquisition unit 201 as authentication server information. Then, control for transmitting to the settlement server 4 via the communication unit 39 is executed.

When the settlement server 4 receives the authentication server information, the settlement server 4 recognizes the user authentication result based on the user parameter in the authentication server information.
The settlement server 4 executes a predetermined settlement process when the user authentication is successful, executes a predetermined error process when the user authentication is unsuccessful, and a settlement result indicating the execution contents Is transmitted to each of the store terminal 1 and the user terminal 2.
Here, the payment process refers to a series of processes related to the execution of this service, that is, a series of processes until a user who purchases a product or the like at a store makes a payment to pay for the product or the like.

The S-OTID generation / update unit 206 of the authentication server 3 generates a one-time ID as an authenticator indicating that the authentication server 3 is authentic based on the authentication seed and the common encryption key updated at the previous settlement. . Then, the S-OTID generation / updating unit 206 executes control for transmitting the generated S-OTID to the user terminal 2 via the communication unit 39.
As described above, since the user terminal 2 also generates a one-time ID, the one-time ID generated by the S-OTID generation / updating unit 206 is hereinafter referred to as “S-OTID” to be distinguished from this. . The S-OTID is an authenticator indicating that the authentication server 3 is authentic.
That is, in this embodiment, mutual authentication in which the user terminal 2 authenticates the authentication server 3 as well as the authentication server 3 is adopted. Therefore, the S-OTID is generated by the S-OTID generation / update unit 206 and transmitted to the user terminal 2.

Further, two one-time IDs, C-OTID and S-OTID, are generated using authentication seeds created (updated) in advance. Therefore, an authentication mechanism using an authentication seed will be briefly described.
In the first embodiment, a common authentication seed and common encryption key are used for one or more services.
Specifically, for example, the C-OTID generation unit 104 of the user terminal 2 copies an authentication seed and a common encryption key common to one or more services to the operation stack on the RAM 13, and uses the copied authentication seed as the copied authentication seed. Based on this, a C-OTID is generated and transmitted to the authentication server 3. In addition, the C-OTID generation unit 104 updates the authentication seed at the same time.
The user authentication unit 203 of the authentication server 3 authenticates the validity of the user terminal 2 based on the C-OTID transmitted from the user terminal 2.
On the other hand, the S-OTID generation / update unit 206 of the authentication server 3 generates an S-OTID based on the previously updated authentication seed and the common encryption key, and transmits the S-OTID to the user terminal 2. In addition, the S-OTID generation / update unit 206 simultaneously updates the authentication seed.
The server authentication unit 108 of the user terminal 2 determines the validity of the authentication server 3 based on the S-OTID transmitted from the authentication server 3.

The functional configuration for executing the settlement support process by the user terminal 2 and the authentication server 3 has been described above with reference to FIG. Next, the flow of the settlement support process executed by the user terminal 2 and the authentication server 3 will be described with reference to FIGS.

FIG. 5 is a diagram showing an outline of the flow of the settlement support process executed by the user terminal and the authentication server in FIG.
FIG. 6 is an arrow chart showing the flow of a payment support process executed by the user terminal and the authentication server shown in FIG.

In step Sa0-1, store terminal 1 generates an authentication service code.
In step Sa0-2, the service code acquisition unit 102 of the user terminal 2 acquires the authentication service code generated in the store terminal 1.

In step Sa1, the upper request unit 101 executes an upper request to the settlement server 4. That is, the upper request unit 101 requests the payment server 4 to receive a payment result.

In step Sa2, the PW input unit 103 receives a password input from the user via the touch operation input unit 16. Then, the PW encryption unit 105 generates an encrypted password by encrypting the password.

In step Sa3, the C-OTID generating unit 104 generates a C-OTID based on the previously updated authentication seed and common encryption key.

In step Sa4, the user terminal information generation unit 106 receives user terminal information including the encrypted password generated in step Sa2, the authentication service code acquired in step Sa0, and the C-OTID generated in step Sa3. Generate.

In step Sa5, the user terminal information transmission control unit 107 transmits the user terminal information generated in step Sa4 to the authentication server 3.

In step Sa6, the user authentication unit 203 performs user authentication (client authentication) based on the password and C-OTID included in the user terminal information transmitted from the user terminal 2 in step Sa5.

In step Sa7, the decryption unit 202 of the authentication server 3 decrypts the encrypted password included in the user terminal information transmitted from the user terminal 2 in step Sa5 into the above-described password.

In step Sa8, the S-OTID generation / update unit 206 generates an S-OTID based on the authentication seed and the common encryption key updated in step Sa3 of the previous settlement support process, and updates the authentication seed.

In step Sa9-1, the authentication server information transmission control unit 205 transmits the authentication server side information including the S-OTID generated in step Sa8 and the updated authentication seed information to the user terminal 2.

In step Sa9-2, the server authentication unit 108 of the user terminal 2 acquires the authentication server side information transmitted in step Sa9-1, that is, S-OTID and the like. The server authentication unit 108 authenticates the authentication server 3 based on the acquired S-OTID.

In step Sa9-3, the authentication seed update unit 109 updates the authentication seed based on the result authenticated by the server authentication unit 108.

In step Sa10, the user parameter conversion unit 204 generates a user parameter indicating the authentication result of the user performed in step Sa7.

In step Sa11, the authentication server information transmission control unit 205 obtains authentication server information including the authentication service code included in the user terminal information transmitted from the user terminal 2 in step Sa5 and the user parameter generated in step Sa10. It transmits to the settlement server 4.

In step Sa12, the settlement server 4 executes settlement processing or error processing based on the authentication server information transmitted from the authentication server 3 in step Sa11, that is, the authentication service code and the user parameter.

In step Sa13-1, the settlement server 4 transmits the result of the settlement process or error process executed in step Sa12 (hereinafter referred to as “settlement result”) to the store terminal 1.
In step Sa13-2, the store terminal 1 acquires the settlement result transmitted from the settlement server 4 in step Sa13-1, and the store terminal 1 displays the acquired settlement result.

In step Sa14, the settlement server 4 transmits the settlement result executed in step Sa12 to the user terminal 2.
In step Sa15, the payment result acquisition unit 110 of the user terminal 2 acquires the payment result transmitted from the payment server 4 in step Sa14. Then, the presentation unit 111 displays the settlement result on the display unit 17.

By realizing such payment support processing, when payment processing is performed in the payment server 4, the user terminal 2 does not need to perform any communication other than acquisition of the authentication service code with the store terminal 1. There is no possibility that the personal information of the user is transmitted to the store terminal 1.
Therefore, personal information of the user is not stored in the store terminal 1, so that it is never abused by store employees or leaked from the store terminal 1 as in the past.
In this way, it is possible to reduce the risk of personal information leakage and the like in the settlement process using an electronic method.
Further details of the settlement support process capable of producing such an effect will be described below with reference to FIGS.

FIG. 7 is a flowchart for explaining a detailed flow of a series of processes mainly executed in the user terminal 2 of FIG. 2 in the settlement support process of FIG.

In step Sa0-1, the store terminal 1 generates or receives an authentication service code. The subsequent processing of the store terminal 1 will be described later with reference to FIG. 10 as processing P4-1.
In step Sa0-2, the service code acquisition unit 102 of the user terminal 2 acquires the authentication service code generated by the store terminal 1 in step Sa0-1. As described above, the method for acquiring the authentication service code is not particularly limited.

When the authentication service code is acquired in step Sa0-2, in step Sa1, the upper request unit 101 executes an upper request to the payment server 4, that is, a request for receiving a payment result. Note that the reception process of the settlement server 4 for this higher order request is executed as process P4-4-1, and the process of step Sa14 in FIG. 10 is executed as the response process. The process of step Sa14 will be described later with reference to FIG.

In step Sa <b> 2, the PW input unit 103 receives a password input from the user via the touch operation input unit 16. Then, the PW encryption unit 105 encrypts the password received in step Sa2 to generate an encrypted password.
In step Sa3, the C-OTID generating unit 104 generates a C-OTID.
In step Sa4, the user terminal information generation unit 106 generates an authentication server transmission packet.
That is, the user terminal information generation unit 106 includes the encrypted password generated in step Sa2, the authentication service code acquired by the service code acquisition unit 102 in step Sa0-2, and the C-OTID generated in step Sa3. The user terminal information including is generated.
This user terminal information is composed of a plurality of packets in this embodiment. This packet corresponds to the above-described authentication server transmission packet.

In step Sa5, the user terminal information transmission control unit 107 transmits the authentication server transmission packet generated in step Sa4 to the authentication server 3.
As processing of the user terminal 2 thereafter, processing P4-2 is executed. The process P4-2 will be described later with reference to FIG.

When the authentication server transmission packet is transmitted to the authentication server 3 in step Sa4, the authentication server 3 executes process P2-3.
Therefore, the process P2-3 in the authentication server 3 will be described below with reference to FIG.
FIG. 8 is a flowchart for explaining a detailed flow of a series of processing mainly executed by the authentication server 3 of FIG. 3 in the settlement support processing of FIG.

In step Sa6, the user authentication unit 203 of the authentication server 3 performs the client authentication (user authentication) based on the C-OTID transmitted from the user terminal 2, that is, the normal operation to which the user terminal 2 is the application target of this service. Authenticate that it is a terminal.

In step Sa7, the decryption unit 202 of the authentication server 3 decrypts the encrypted password included in the user terminal information transmitted from the user terminal 2 into the above-described password.

In step SP3-1, the user authentication unit 203 determines whether or not the C-OTID used in the client authentication in step Sa6 is generated by a legitimate terminal.
If the C-OTID is not generated by a legitimate terminal, NO is determined in step SP3-1, and the process proceeds to step Sa10-3. The processing after step Sa10-3 will be described later.
On the other hand, if the C-OTID is generated by a legitimate terminal, it is determined as YES in Step SP3-1, and the process proceeds to Step Sa8.

In step Sa8, the S-OTID generation / update unit 206 generates an S-OTID based on the previously updated authentication seed and the common encryption key, and updates the authentication seed.

In step Sa <b> 9, the authentication server information transmission control unit 205 transmits an authentication packet to the user terminal 2.
That is, the authentication server information transmission control unit 205 transmits the authentication server side information including the S-OTID generated in step Sa8 and the updated authentication seed information to the user terminal 2. This authentication server side information is composed of a plurality of packets in this embodiment. This packet corresponds to the authentication packet described above.
Note that when the authentication server information transmission control unit 205 transmits the authentication server information to the user terminal 2, the user terminal 2 executes the process P4-2. The process P4-2 will be described later with reference to FIG.

In step SP3-2, the user parameter conversion unit 204 determines whether or not the password decrypted in step Sa7 is input from a legitimate terminal.

If the password is entered at a legitimate terminal, it is determined as YES in step SP3-2, and the process proceeds to step Sa10-1.
In step Sa10-1, the user parameter conversion unit 204 generates the C-OTID used in the client authentication in step Sa6 at the legitimate terminal, and the password decrypted in step Sa7 is the legitimate terminal. An arbitrary user parameter is generated from the C-OTID to indicate a case where it has been input.

On the other hand, if the acquired password is not entered at the legitimate terminal, it is determined as NO in step SP3-2, and the process proceeds to step Sa10-2.
In step Sa10-2, the user parameter conversion unit 204 generates the C-OTID used in the client authentication in step Sa6 at the legitimate terminal, and the password decrypted in step Sa7 is the legitimate terminal. “-2” is generated as a user parameter to indicate a case where it has not been input.

As described above, if the C-OTID used in the client authentication in step Sa6 is not generated by a legitimate terminal, it is determined NO in step SP3-1, and the process proceeds to step Sa10-3. move on.
In step Sa10-3, the user parameter conversion unit 204 generates “−1” as the user parameter when the C-OTID used in the client authentication in step Sa6 is not generated by a legitimate terminal.

That is, when the user parameter is “−2” or “−1”, the user authentication (client authentication) in the authentication server 3 is NG, and the user parameter notifies the NG code. .
As described above, when any one of steps Sa10-1 to 10-3 (step S10 in FIGS. 5 and 6) is executed and a user parameter is generated, the process proceeds to step Sa11. .

In step Sa11, the authentication server information transmission control unit 205 selects one of the authentication service code included in the user terminal information transmitted from the user terminal 2 in step Sa5 (FIG. 7) and steps Sa10-1 to 10-3. Authentication server information including the user parameters generated in this step is transmitted to the settlement server 4 as a packet.

When the authentication server information is transmitted to the settlement server 4, the settlement server 4 executes the process P3-4 in FIG.
FIG. 9 is a flow chart for explaining a detailed flow of processes after process P3-4, which is a series of processes mainly executed in the settlement server 4 of FIG. 1 in the settlement support process of FIG. The process shown in FIG. 9 corresponds to the process of step Sa12 in FIGS.

In step SP4-0, the settlement server 4 receives the authentication server information packet transmitted from the authentication server 3 in step Sa11 as a settlement packet.

In step SP4-1, the settlement server 4 determines the user parameter included in the authentication server information.

When the settlement server 4 extracts the user parameter “−1” in step SP4-1, the processing proceeds to step SP4-2.
In step SP4-2, the settlement server 4 generates a settlement result “settlement result NG” indicating that the settlement process has not been completed normally and a reason code “−1” indicating the reason.

When the settlement server 4 extracts the user parameter “−2” in step SP4-1, the settlement server 4 advances the processing to step SP4-3.
In step SP4-3, the settlement server 4 generates a settlement result “settlement result NG” indicating that the settlement process has not been completed normally and a reason code “−2” indicating the reason.

If the settlement server 4 extracts other user parameters in step SP4-1, that is, if a user parameter indicating that the user authentication is successful is extracted, the process proceeds to step SP4-4.
In step SP4-4, the settlement server 4 executes a settlement process based on the user parameters.

In step SP4-5, the settlement server 4 determines whether or not the settlement process executed in step SP4-4 is OK.

If the settlement server 4 determines that the settlement process is NG, the settlement server 4 advances the process to step SP4-6.
In step SP4-6, the settlement server 4 generates a settlement result “settlement result NG” indicating that the settlement process has not been completed normally and a reason code “−3” indicating the reason.

On the other hand, when the settlement server 4 determines that the settlement process is OK, the process proceeds to step SP4-7.
In step SP4-7, the settlement server 4 generates a settlement result “settlement result OK” indicating that the settlement process has been normally completed.

In this way, when a settlement result or the like is generated in any of steps SP4-2, SP4-3, SP4-6, and SP4-7, the process proceeds to process P4-4.
Therefore, the process P4-4 in the settlement server 4, the process P4-2 in the user terminal 2 and the process P4-1 in the store terminal 1 will be described below with reference to FIG.

FIG. 10 is a series of processes executed mainly by the store terminal 1, the payment server 4 of FIG. 1, and the user terminal 2 of FIG. 2 among the payment support processes of FIG. -2 is a flowchart for explaining the detailed flow of processes after process P4-1.

First, the processing after P4-4 performed by the settlement server 4 will be described with the settlement server 4 serving as the center of processing as a center.
In step SP4-8, the settlement server 4 generates a settlement result packet for the shop terminal.
That is, the settlement server 4 uses the authentication service code transmitted from the authentication server 3 in step Sa11 and the settlement result generated in any of the above steps SP4-2, SP4-3, SP4-6, SP4-7. (And a reason code in the case of NG) generate settlement server information for store terminals in a packet. This packet is a settlement result packet for store terminals.

In step Sa13, the payment server 4 transmits the payment server side information for the store terminal generated in step SP4-8 to the store terminal 1.
In step Sa13-2, the shop terminal 1 acquires the payment server information for the shop terminal transmitted from the payment server 4 in step Sa13 and displays it.

In step SP4-9, the payment server 4 generates a payment result packet for the user terminal.
That is, as in step SP4-8, the settlement server 4 sends the authentication service code transmitted from the authentication server 3 in step Sa11 and the above-described steps SP4-2, SP4-3, SP4-6, and SP4-7. The payment server information for the user terminal including the payment result (and reason code in the case of NG) generated by any of the packets is generated in a packet. This packet is a payment result packet for the user terminal.

In step Sa14, on the condition that the upper request has been transmitted from the user terminal 2 (Process P4-4-1), the settlement server 4 uses the user server 2 for the payment server information for the user terminal generated in step SP4-8. Send to.
In step Sa15, the payment result acquisition unit 110 of the user terminal 2 acquires the user terminal payment server information (payment result) transmitted from the payment server 4 in step Sa14. The presentation unit 111 displays it.

In the user terminal 2, the following processing is also executed before Step Sa15.
That is, in step Sa9-2, the server authentication unit 108 of the user terminal 2 receives the S-OTID authentication packet transmitted from the authentication server 3.
That is, the server authentication unit 108 acquires the S-OTID transmitted from the authentication server 3 in step Sa9-1 and the updated authentication seed for each packet.

In step SP3-3, the server authentication unit 108 determines whether or not the S-OTID acquired in step Sa9-1 is OK.
When the acquired S-OTID is NG, it is determined as NO in Step SP3-3, and the process on the user terminal 2 side ends.
On the other hand, if the acquired S-OTID is OK, YES is determined in step SP3-3, and the process proceeds to step Sa9-3.
In step Sa9-3, the authentication seed update unit 109 updates the authentication seed.

Here, in the above-described first embodiment, a series of settlement support processing is realized by adopting an information processing system including the store terminal 1, the user terminal 2, the authentication server 3, and the settlement server 4.
However, in order to realize such a settlement support process, it is not always necessary to adopt an information processing system including the store terminal 1, the user terminal 2, the authentication server 3, and the settlement server 4. For example, the provision of products and the like is performed not only at an actual store but also at an EC site such as an online shop.
Accordingly, as another embodiment of the information processing system to which the present invention is applied, that is, as a second embodiment, an information processing system including an EC site, a user terminal 2, an authentication server 3, and a settlement server 4 may be adopted. Good.
By adopting the second embodiment, the provider of this service can provide a wider range of settlement services.
A server that manages such an EC site is hereinafter referred to as a “service server”. The service server is managed by a merchant operating the EC site and issues an authentication service code.

Here, the hardware configurations of the user terminal 2 and the authentication server 3 in the second embodiment are the same as those in the first embodiment shown in FIGS. 2 and 3 respectively. In addition, the hardware configuration of the service server 5 newly employed in the second embodiment is the same as the hardware configuration of the authentication server 3 described above.

FIG. 11 is an example of a configuration of an information processing system according to the second embodiment of the present invention, and is a diagram illustrating the second embodiment of the present invention.
The information processing system shown in FIG. 11 includes a user terminal 2, an authentication server 3, a settlement server 4, and a service server 5.
The user terminal 2, the authentication server 3, the settlement server 4, and the service server 5 are connected to each other via a predetermined network N such as the Internet.
The number of user terminals 2, authentication server 3, settlement server 4, and service server 5 may be any number greater than or equal to one.

In the second embodiment of the present invention, the payment support process is executed by the information processing system shown in FIG.
Here, FIGS. 12 to 18 are a functional block diagram, a schematic diagram, an arrow chart, and a flowchart according to the second embodiment of the present invention. Since these are basically the same except that the service server 5 is employed instead of the store terminal 1, the description other than this point is omitted here.

That is, unlike the first embodiment, in the second embodiment, as shown in FIG. 13, the user terminal 2 is connected to the upper application software (hereinafter referred to as “upper host software”) for communicating with the service server 5 in order to provide products and the like. Called "app"). Further, the user terminal 2 has an authentication module for communicating with the authentication server 3 without communicating with the service server 5 as communication for executing user authentication or the like.

In step Sb 0-1, the service code acquisition unit 102 of the upper application of the user terminal 2 makes an access (service access) for requesting a settlement service for providing products etc. to the service server 5.
In step Sb0-2, the service server 5 generates an authentication service code. In step Sb0-3, the service server 5 transmits an authentication service code to the user terminal 2. The service code acquisition unit 102 of the upper application of the user terminal 2 receives the authentication service code.

In the second embodiment, as indicated by a dotted line in FIG. 13, the upper request unit 101 of the upper application does not execute the upper request to the settlement server 4 as in the first embodiment, Then, the reception of the settlement result is requested (step Sb1).

In step Sb <b> 2, the PW input unit 103 of the upper application receives a password input from the user via the touch operation input unit 16.
In step Sb3-0, the upper application transmits the authentication service code and the password to the authentication module.
Accordingly, in step Sb3-2, the PW encryption unit 105 of the authentication module generates an encrypted password by encrypting the password.

In step Sb3-1, the C-OTID generating unit 104 of the authentication module generates a C-OTID based on the previously updated authentication seed and common encryption key.

In step Sb4, the user terminal information generation unit 106 of the authentication module performs the encrypted password generated in step Sb3-2, the authentication service code acquired in step Sb0-3, and the C generated in step Sb3-1. User terminal information including the OTID (authentication server transmission packet generated in step Sb3-3 in FIG. 15) is transmitted to the authentication server 3.

Since the subsequent processing of the authentication server 3 and the settlement processing of the settlement server 4 are executed in the same manner as in the first embodiment, their description is omitted here.

Similar to the first embodiment, in step Sb9-1, the authentication server 3 transmits S-OTID (an authentication packet in FIG. 16) to the user terminal 2.
In step Sb13-1, the server authentication unit 108 of the authentication module of the user terminal 2 authenticates the authentication server 3 based on the S-OTID.
In step Sb13-2, the authentication seed update unit 109 of the authentication module updates the authentication seed based on the result authenticated by the server authentication unit 108.

On the other hand, the settlement server 4 transmits the settlement result to the service server 5 in step Sb17.
Here, unlike the first embodiment, in the second embodiment, the settlement server 4 does not transmit the settlement result to the user terminal 2.
That is, in the second embodiment, the service server 5 receives the above-described result request from the user terminal 2 and transmits the settlement result acquired from the settlement server 4 to the user terminal 2 in step Sb18.
In step Sb19, the payment result acquisition unit 110 of the upper application of the user terminal 2 acquires the payment result transmitted from the service server 5 in step Sb18. Then, the presentation unit 111 of the upper application displays the settlement result on the display unit 17.

Also in the second embodiment, when the payment server 4 performs a payment process by realizing such a payment support process, the user terminal 2 acquires an authentication service code and a payment result with the service server 5. Since there is no need to perform any other communication, there is no possibility that the personal information of the user is transmitted to the service server 5.
For this reason, since the personal information of the user is not stored in the service server 5, it is never abused by a person who manages the EC site or the personal information is not leaked from the EC site 5 as in the past.
As described above, in the second embodiment, as in the first embodiment, it is possible to reduce the risk of personal information leakage or the like in the settlement process using an electronic method.

Furthermore, in the first embodiment and the second embodiment described above, a series of settlement support processing is realized by adopting an information processing system constituted by various hardware.
However, in order to realize such a settlement support process, it is not always necessary to adopt the information processing system described in the first embodiment and the second embodiment.
For example, the present invention includes a so-called shoplifting prevention system that prevents the unpaid product from being taken out when the user purchases the product after performing the above-described settlement support process at a store that provides the product. It can be applied to an information processing system.

FIG. 19 is a diagram showing an example of the configuration of an information processing system according to the third embodiment of the present invention.
The information processing system shown in FIG. 19 includes a store terminal 1, a user terminal 2, an authentication server 3, a settlement server 4, and a gate device 6.
The store terminal 1, the user terminal 2, the authentication server 3, the payment server 4, and the gate device 6 are connected to each other via a predetermined network N.
In addition, about the number of each of the shop terminal 1, the user terminal 2, the authentication server 3, the payment server 4, and the gate apparatus 6, any number of 1 or more may be sufficient.
The gate device 6 is, for example, an information processing device integrated with a gate for preventing unsettled products installed at a store entrance and the like, and is provided by a provider of this service or products, etc. It is managed by a person.

In the example of FIG. 19, it is assumed that the above-described settlement support process is performed when a user purchases a product A, a product B, and a product C (hereinafter referred to as “product A to C”). In the example of FIG. 19, each of the products A to C can directly communicate with the user terminal 2 by an arbitrary communication method such as NFC (Near Field Communication) or Bluetooth (registered trademark). It is assumed that tags are attached respectively.

When the user terminal 2 wishes to purchase the products A to C from the user, as described above, the authenticator indicating to the authentication server 3 that the user terminal 2 is legitimate as a device to which this service is applied. As a one-time ID, that is, C-OTID.
The user terminal 2 generates an encrypted password by encrypting the password received by the user input by a predetermined method.
The user terminal 2 transmits information including the encrypted password and C-OTID and the authentication service code obtained from the store terminal 1 to the authentication server 3 as user terminal information.

When the authentication server 3 acquires the user terminal information transmitted from the user terminal 2, the authentication server 3 decrypts the above password from the encrypted password included in the user terminal information.
Based on the decrypted password and the C-OTID included in the user terminal information, the authentication server 3 performs authentication that the user terminal 2 is a regular terminal to which this service is applied, that is, user authentication.
The authentication server 3 transmits information including a user parameter indicating the result of user authentication and an authentication service code included in the user terminal information to the settlement server 4 as authentication server information.

Furthermore, in the third embodiment, the authentication server 3 generates an ID (hereinafter referred to as “G-ID”) for allowing the user who has performed user authentication to pass through the gate, and the gate device 6, the user terminal 2, To each of the.
Here, it is sufficient that the G-ID is generated by the authentication server 3 that has performed user authentication, and it is not necessary to match the above-described C-OTID, service code, etc., and any G-ID can be adopted. The G-ID transmission timing may be any timing as long as it is before the user passes through the gate. For example, as described above, the authentication server 3 generates an S-OTID and transmits it to the user terminal 2. However, the G-ID may also be transmitted to the user terminal 2 at the transmission timing of this S-OTID. Needless to say, it is not necessary to match the S-OTID and the G-ID.

The user terminal 2 uses the G-ID transmitted from the authentication server 3 and information (hereinafter referred to as “product identification information”) that can identify each product transmitted from the tags of the products A to C. Generate linked information (hereinafter referred to as “linked information”).
Here, three pieces of association information may be generated individually for each of the products A to C, or one piece of information may be generated for a group of products A to C (a unit of settlement). Hereinafter, for convenience of explanation, it is assumed that one piece of linking information is generated for a group of products A to C (a unit of settlement).
The gate device 6 holds the G-ID transmitted from the authentication server 3.

On the other hand, when the settlement server 4 receives the authentication server information transmitted from the authentication server 3, the settlement server 4 recognizes the user authentication result based on the user parameter in the authentication server information.
The settlement server 4 executes a predetermined settlement process when the user authentication is successful, and transmits a settlement result indicating the execution content to each of the store terminal 1 and the user terminal 2.

When the user terminal 2 acquires the result of the payment process transmitted from the payment server 4, the user terminal 2 displays the result of the payment process on the display unit 17 and presents it to the user.

When the store terminal 1 acquires the result of the payment process transmitted from the payment server 4, the shop terminal 1 shows information indicating the result of the payment process and the products (products A to C in this example) that are the objects of the payment process. Are transmitted to the gate device 6. The gate device 6 holds this information in association with the above-mentioned G-ID.

Thereafter, when the user holding the user terminal 2 passes through the store gate, the gate terminal 6 directly communicates with the user terminal 2 by an arbitrary communication method such as NFC (Near Field Communication) or Bluetooth (registered trademark). Communication is performed to obtain linking information, and the user passes through the gate based on whether or not the G-ID included in the linking information matches the G-ID held by the own device. Decide whether or not to allow it.
In other words, as shown in the lower right example in FIG. 19, when the products A to C do not have the link information (that is, “G-ID” is not linked), or the products A to C are linked. Even if it has attachment information (that is, “G-ID” is associated), if it is a different G-ID, the gate device 6 prohibits the user from passing through the gate. Execute the process. Furthermore, the gate device 6 allows the user to pass through the gate not only when the G-ID but also the result of the payment processing transmitted from the payment server 4 via the store terminal 1 is a failure result. Execute the process that prohibits.
The process for prohibiting the user from passing through the gate can employ various processes such as sounding a buzzer, shutting off the gate, and notifying the store terminal 1.

Also in the third embodiment, since the settlement support process of the first embodiment can be realized as it is, there is no possibility that the user's personal information is transmitted to the store side (the store terminal 1 or the gate device 6).
Further, unlike the conventional shoplifting prevention system, there is no need for the store clerk to attach or remove the tag attached to the product or the like.
As described above, by adopting the third embodiment, the provider of this service provides a wider range of settlement services that can easily prevent users from taking unsettled products out of the store, for example. It is possible to achieve the effect of being able to.

The G-ID is generated based on user authentication using the C-OTID in the third embodiment. However, the G-ID is not particularly limited to this, and the information that can identify the user terminal 2 and the user can be identified. It may be generated based on user authentication using information (for example, biometric information). That is, the process of permitting the passage of the gate using the G-ID is premised on the settlement support process, but this settlement support process is not particularly limited to the process of the first embodiment or the second embodiment described above, It is sufficient if user authentication is performed. That is, it is sufficient that the G-ID is generated based on the user authentication performed in the payment support process.

The first to third embodiments of the present invention have been described above. However, the present invention is not limited to the above-described first to third embodiments, and modifications within a range that can achieve the object of the present invention. Improvements and the like are included in the present invention.

For example, the authentication service code in the above-described embodiment can be used in the following applications.
That is, the authentication service code can be used for various services such as service login, access authentication (monitoring / control, etc.), access right (voting / questionnaire, etc.), in addition to the settlement of the above-described embodiment.
That is, the authentication service code is information issued by the service. In order to prevent unauthorized authentication from being executed by the authentication service code, authentication information is checked by the authentication server and the user terminal.
Specifically, the following information is set in the authentication service code.
That is, for example, the target of the service (who, what), the content of the service (what, in principle, service login, payment, etc.), the recipient (to whom) the authentication result is received, the time limit (until, usually the service) Information such as a random number (request code) for each service is set.
That is, the authentication service code is read by the user terminal (authentication client) and notified to the authentication server.
Then, the authentication server notifies user information to a specified who (who) of the authentication service code, and a specified who (who) notifies a Result (result) to the specified who (who).
This Result (result), for example, notifies the user ID, password, payment code, payment amount, time stamp, payment service, etc. For example, if the specified who (to whom) is not specified, from the authentication server The Result (result) is notified to the authentication service code issuer.

Further, for example, the authentication service code in the above-described embodiment has been described as being notified by a QR code (registered trademark), but is not particularly limited thereto.
For example, communication means such as NFC (Near Field Radio Communication) (registered trademark), Bluetooth (registered trademark), and optical communication can be used.

Further, for example, in the above-described embodiment, various authenticators (for example, C-OTID and S-OTID) are described as one-time IDs.
This one-time ID is a genuine random number or a pseudo-random number, and the authentication server 3 and the user terminal 2 update their seeds based on this. For this reason, the communication performed between the user terminal 2 and the authentication server 3 employs a communication using a common encryption key in the above-described embodiment in order to prevent analogy of a one-time ID due to eavesdropping. However, the present invention is not particularly limited to the above-described embodiment, and communication performed between the user terminal 2 and the authentication server 3 can be performed in so-called plain text.
Further, for example, the authentication with the one-time ID itself is not particularly limited, and other authentication techniques such as a fixed password can be used.

For example, in the above-described embodiment, the password input by the user is encrypted, and the encrypted password obtained as a result is included in the user terminal information and transmitted from the user terminal 2 to the authentication server 3. Then, in the authentication server 3, the above password is decrypted from the encrypted password included in the user terminal information, and the user authentication is performed based on the decrypted password and the C-OTID included in the user terminal information. .
However, the encryption of the password is not particularly essential, and the encryption may be omitted. However, it goes without saying that encryption increases security.
Furthermore, a password is not particularly required as information included in the user terminal information, and an identifier for identifying the user is sufficient.

For example, the series of processes described above can be executed by hardware or can be executed by software.
In other words, the functional configurations of FIGS. 4 and 12 are merely examples, and are not particularly limited.
That is, it is sufficient that the information processing system has a function capable of executing the above-described series of processing as a whole, and what functional blocks are used to realize this function are particularly shown in the examples of FIGS. It is not limited. Further, the location of the functional block is not particularly limited to that shown in FIGS. 4 and 12, and may be arbitrary.
In addition, one functional block may be constituted by hardware alone, software alone, or a combination thereof.

For example, when a series of processing is executed by software, a program constituting the software is installed in a computer or the like from a network or a recording medium.
The computer may be a computer incorporated in dedicated hardware.
Further, the computer may be a computer that can execute various functions by installing various programs, for example, a server, a smartphone, a personal computer, or various devices.

In addition, for example, the recording medium including such a program is not only constituted by a removable medium (not shown) distributed separately from the apparatus main body in order to provide the program to the user, but is also incorporated in the apparatus main body in advance. And a recording medium provided to the user.

In the present specification, the step of describing the program recorded on the recording medium is not limited to the processing performed in time series along the order, but is not necessarily performed in time series, either in parallel or individually. The process to be executed is also included.
Further, in the present specification, the term “system” means an overall apparatus configured by a plurality of devices, a plurality of means, and the like.

In other words, the information processing system to which the present invention is applied can take various embodiments having the following configurations.
That is, an information processing system to which the present invention is applied is
A request source device (for example, the store terminal 1 in FIG. 1 or the service server 5 in FIG. 11) managed by a service request source that requests settlement as an authentication service;
A user terminal managed by a user who executes the authentication service (for example, the user terminal 2 in FIG. 1 or FIG. 11);
An authentication server for authenticating the user (for example, the authentication server 3 in FIG. 1 or FIG. 11);
A payment server (for example, the payment server 4 in FIG. 1 or FIG. 11) that executes a payment process for the user;
In an information processing system including
The user terminal is
Service code acquisition means (for example, the service code acquisition unit 102 in FIG. 4 or FIG. 12) that acquires an authentication service code used as a general authentication code for the user to execute the authentication service from the request source device;
First authenticator generation means (for example, C-OTID generator 104 in FIG. 4 or FIG. 12) for generating a first one-time authenticator (C-OTID) indicating that the user terminal is authentic;
First transmission information generating means for generating first transmission information including an identifier for identifying the user, the authentication service code, and the first one-time authenticator (for example, user terminal information generation in FIG. 4 or FIG. 12) Part 106),
First transmission control means (for example, user terminal information transmission control unit 107 in FIG. 4 or FIG. 12) for performing control to transmit the first transmission information to the authentication server;
With
The authentication server is
First reception control means (user terminal information acquisition unit 201 in FIG. 4 or FIG. 12) for performing control to receive the first transmission information from the user terminal;
User authentication means for generating a user parameter indicating the user authentication result based on the identifier included in the first transmission information and the first one-time authenticator included in the first transmission information (for example, FIG. 4 or the user authentication unit 203) of FIG.
Second transmission control means for performing control to transmit the second transmission information including the authentication service code included in the first transmission information and the user parameter to the settlement server (the authentication server information in FIG. 4 or FIG. 12). Transmission control unit 205),
It is enough to have

As a result, the store to be settled can be specified by the authentication service code described above, and the individual at the time of settlement between the user terminal and the request source device (for example, the store terminal 1 in FIG. 1 or the service server 5 in FIG. 11). Transmission / reception of information becomes unnecessary. Therefore, it is possible to reduce risks such as leakage of personal information in the settlement process by an electronic method.

Furthermore, the first transmission information generating means includes
As the identifier for identifying the user, an encrypted password is generated by encrypting the input password, and includes the encrypted password, the authentication service code, and the first one-time authenticator. Generating first transmission information;
The user authentication means, based on the password obtained by decrypting the encrypted password included in the first transmission information, and the first one-time authenticator included in the first transmission information, the user authentication result The user parameter indicating can be generated.
Thereby, since eavesdropping at the time of communication of the identifier for identifying the user can be suppressed, security is further improved.

Further, the authentication server includes:
Based on the previously updated authentication seed, a second one-time authenticator (S-OTID) indicating that the authentication server is authentic is generated, and second authenticator generation means (for example, FIG. 4 or the generation function of the S-OTID generation / update unit 206 in FIG.
Third transmission control means (for example, the transmission control function of the S-OTID generation / updating unit 206 in FIG. 4 or FIG. 12) for controlling the transmission of the second one-time authenticator (S-OTID) to the user terminal;
Further comprising
The first authenticator generating means of the user terminal generates the first one-time authenticator (C-OTID) based on the previously updated authentication seed,
The user terminal authenticates the authentication server based on the second one-time authenticator and also updates server authentication means for updating the authentication seed (for example, the server authentication unit 108 in FIG. 4 or FIG. 12);
It is enough to have more.

Thereby, since mutual authentication between the user terminal and the request source device can be performed more accurately, it is possible to further reduce risks such as leakage of personal information in settlement processing by an electronic method.

Further, the payment server recognizes the authentication result of the user based on the user parameter, executes the payment process when the user authentication is successful, and the user authentication has failed. In this case, a predetermined error process is executed, and at least the settlement result indicating the execution content is notified to the request source device.
The user terminal is
Acquisition means for acquiring the payment result from the payment server or the request source device (for example, the payment result acquisition unit 110 in FIG. 4 or FIG. 12);
Presenting means for presenting the acquired settlement result to the user (for example, the presentation unit 111 in FIG. 4 or 12);
It is enough to have more.

According to the above-described configuration, the result of the payment process (payment process result) executed by the payment server is transmitted to the user terminal and the request source apparatus. The user terminal can present the settlement processing result to the user.
Thereby, the user can grasp | ascertain correctly whether the payment above-mentioned payment assistance process was completed normally.

1 store terminal 2 user terminal 3 authentication server 4 settlement server 5 service server 11 CPU
31 CPU
DESCRIPTION OF SYMBOLS 101 Upper request | requirement part 102 Service code acquisition part 103 PW input part 104 C-OTID generation part 105 PW encryption part 106 User terminal information generation part 107 User terminal information transmission control part 108 Server authentication part 109 Authentication seed update part 110 Settlement result acquisition Unit 111 presentation unit 201 user terminal information acquisition unit 202 decryption unit 203 user authentication unit 204 user parameter conversion unit 205 authentication server information transmission control unit 206 S-OTID generation update unit 301 UPDB

Claims

A request source device managed by a service request source that requests settlement as an authentication service;
A user terminal managed by a user executing the authentication service;
An authentication server for authenticating the user;
A payment server for executing a payment process for the user;
In an information processing system including
The user terminal is
Service code acquisition means for acquiring an authentication service code used as a general authentication code for the user to execute the authentication service from the request source device;
First authenticator generating means for generating a first one-time authenticator indicating that the user terminal is authentic;
First transmission information generating means for generating first transmission information including an identifier for identifying the user, the authentication service code, and the first one-time authenticator;
First transmission control means for performing control to transmit the first transmission information to the authentication server;
With
The authentication server is
First reception control means for performing control to receive the first transmission information from the user terminal;
User authentication means for generating a user parameter indicating an authentication result of the user based on the identifier included in the first transmission information and the first one-time authenticator included in the first transmission information;
Second transmission control means for performing control to transmit the second transmission information including the authentication service code included in the first transmission information and the user parameter to the settlement server;
Comprising
Information processing system.
The first transmission information generating means includes
As the identifier for identifying the user, an encrypted password is generated by encrypting the input password, and includes the encrypted password, the authentication service code, and the first one-time authenticator. Generating first transmission information;
The user authentication means, based on the password obtained by decrypting the encrypted password included in the first transmission information, and the first one-time authenticator included in the first transmission information, the user authentication result Generating the user parameter indicating:
The information processing system according to claim 1.
The authentication server is
A second authenticator generating means for generating a second one-time authenticator indicating that the authentication server is authentic based on the authentication seed updated last time, and updating the authentication seed;
Third transmission control means for performing control to transmit the second one-time authenticator to the user terminal;
Further comprising
The first authenticator generating means of the user terminal generates the first one-time authenticator based on the authentication seed updated last time,
The user terminal further includes server authentication means for authenticating the authentication server based on the second one-time authenticator and updating the authentication seed.
The information processing system according to claim 1 or 2.
The payment server recognizes the authentication result of the user based on the user parameter, executes the payment process when the user authentication is successful, and when the user authentication fails. Executes predetermined error processing, notifies at least the requesting device of a settlement result indicating the execution content,
The user terminal is
Obtaining means for obtaining the settlement result from the settlement server or the request source device;
Presenting means for presenting the acquired settlement result to the user;
Further comprising
The information processing system according to any one of claims 1 to 3.