Information processing program, information processing device, and information processing method

Abstract

To improve a satisfaction of a user using a service application while ensuring a certain security level.SOLUTION: An information processing apparatus (40) includes an acquisition unit that acquires an issuance request to request an issuance of a token and / or an electronic certificate used in a first application provided by a first business operator to a second application provided by a second business operator, a verification unit that verifies an identity of a user of the first application and a user of the second application in response to the issuance request, and a provision unit that provides the token and / or the electronic certificate issued by the first business operator to the second application based on a verification result of the identity.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to an information processing program, an information processing device, and an information processing method. [Background technology]

[0002] Conventionally, a technology is known in which a token is issued to a payment application (hereinafter, referred to as a "payment app") installed on a device, and the token is used to make a payment in the payment app. For example, Patent Document 1 describes that a token is issued to a payment app installed on a user's device, and a store terminal reads a payment code generated based on the token, thereby making a payment based on the payment app.

[0003] There is also known a technology that uses an authentication application (hereinafter referred to as "authentication app") installed on a device to authenticate a device or a user. In order to ensure a certain level of security, such payment apps and / or authentication apps (hereinafter referred to as "payment / authentication apps") are generally used for dedicated purposes. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 6986176 Summary of the Invention [Problem to be solved by the invention]

[0005] Various applications, including but not limited to payment / authentication applications, are installed on a user's device. For example, applications optimized for various services, such as online services that provide virtual reality (VR) space or metaverse space, are becoming more widely used. In order to improve the satisfaction of users who use such service apps (e.g., building experiences in VR space or metaverse space), it is expected that a payment function and / or authentication function will be required when the service app provides a service.

[0006] However, if an attempt is made to link a service app with a payment / authentication app in order to improve the satisfaction of users who use the service app, there is a risk that a certain level of security required of the payment / authentication app cannot be guaranteed.

[0007] The present disclosure has been made in consideration of the above-mentioned circumstances, and one of its objectives is to provide an information processing program, an information processing system, and an information processing method that can improve the satisfaction of users who use service apps while ensuring a certain level of security. [Means for solving the problem]

[0008] An information processing program according to one embodiment of the present disclosure causes a computer to function as an acquisition unit that acquires an issuance request requesting that a token and / or electronic certificate used in a first application provided by a first operator be issued to a second application provided by a second operator, a verification unit that verifies the identity of a user of the first application and a user of the second application in response to the issuance request, and a provision unit that provides the token and / or the electronic certificate issued by the first operator to the second application based on a result of the identity verification.

[0009] An information processing device according to another aspect of the present disclosure includes an acquisition unit that acquires an issuance request requesting that a token and / or electronic certificate used in a first application provided by a first operator be issued to a second application provided by a second operator, a verification unit that verifies the identity of a user of the first application and a user of the second application in response to the issuance request, and a provision unit that provides the token and / or the electronic certificate issued by the first operator to the second application based on a result of the identity verification.

[0010] An information processing method of an information processing device according to another aspect of the present disclosure includes the steps of obtaining an issuance request requesting that a token and / or an electronic certificate used in a first application provided by a first operator be issued to a second application provided by a second operator, verifying the identity of a user of the first application and a user of the second application in response to the issuance request, and providing the token and / or the electronic certificate issued by the first operator to the second application based on a result of the identity verification. Effect of the Invention

[0011] According to one aspect of the present disclosure, it is possible to improve the satisfaction of users who use service applications while ensuring a certain level of security. [Brief description of the drawings]

[0012] [Figure 1] 1 is a diagram showing a schematic configuration of an information processing system 1 according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram illustrating an example of a collaboration model according to the embodiment. [Diagram 3] 1 is a diagram illustrating an example of a physical configuration of each device in an information processing system 1 according to the present embodiment. [Figure 4] 1 is a diagram illustrating an example of a functional configuration of an information processing system 1 according to an embodiment of the present invention. [Diagram 5]FIG. 4 is a diagram illustrating an example of the operation of the information processing system 1 according to the present embodiment. [Figure 6] FIG. 11 is a diagram showing another example of the operation of the information processing system 1 according to the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, an information processing system according to an embodiment of the present invention will be described in detail with reference to the drawings. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

[0014] In the following description, the first application and the second application are respectively a payment / authentication app and a service app, but this is merely an example and is not limited thereto. The first business is a payment business and / or an authentication business, and the second business is a service business, but this is merely an example and is not limited thereto. As an example of the first confirmation information regarding the user of the first application, confirmation information regarding the user of the payment / authentication app is shown, but is not limited thereto. As an example of the second confirmation information regarding the user of the second application, confirmation information regarding the user of the service app is shown, but is not limited thereto.

[0015] (overview) 1 is a diagram showing an overview of an information processing system according to the present embodiment. As shown in FIG. 1, the information processing system 1 includes a terminal 10, a payment / authentication business device 20, a service business device 30, an inter-application cooperation device 40, and a network 50.

[0016] The terminal 10 is a terminal in which a payment / authentication app and / or a service app are installed and used by a user. The terminal 10 is, for example, a smartphone, a tablet, a personal computer, a game console, VR (Virtual Reality) goggles, a VR headset, etc. The payment / authentication app and / or the service app are installed in the terminal 10. The payment / authentication app and the service app may be installed in different terminals 10 or may be installed in the same terminal 10.

[0017] The payment / authentication business operator device 20 is an information processing device of a payment business operator and / or authentication business operator, and provides a payment / authentication app. The payment business operator is, for example, a credit card company, a financial institution, etc. The authentication business operator is, for example, a credit card company, a financial institution, an authentication agency, etc. The payment / authentication business operator device 20 is not limited to one information processing device, and may be composed of multiple information processing devices.

[0018] The payment / authentication app is an application that has a payment function and / or a user authentication function. For example, a payment is performed by a payment service provider based on a token issued by the payment / authentication service provider device 20 to the payment / authentication app. Also, authentication by an authentication service provider may be performed based on a digital certificate issued by the payment / authentication service provider device 20 to the payment / authentication app.

[0019] The service provider device 30 is an information processing device of a service provider, and provides a service application. The service provider is, for example, a game company, a company providing a VR space, a company providing a metaverse space, etc. The service provider device 30 is not limited to one information processing device, and may be composed of multiple information processing devices.

[0020] Service apps are applications optimized for various services, such as online services that provide VR spaces and metaverse spaces.

[0021] The inter-application cooperation device 40 is an information processing device used for cooperation between a payment / authentication application and a service application. The inter-application cooperation device 40 provides a token and / or an electronic certificate (hereinafter referred to as "token / certificate") issued by a payment / authentication business operator to the service application. The inter-application cooperation device 40 is not limited to one information processing device, and may be configured by a plurality of information processing devices.

[0022] The inter-application cooperation device 40 has an interface with a payment / authentication application installed in the terminal 10 (hereinafter referred to as a "payment / authentication application I / F"), and an interface with a service application installed in the terminal 10 (hereinafter referred to as a "service application I / F"). The payment / authentication application I / F and the service application I / F are, for example, APIs (Application Programming Interfaces) and may be used for calling functions, providing SDKs (Software Development Kits), etc.

[0023] The network 50 is a wireless and / or wired network, and connects at least two of the terminal 10, the payment / authentication company device 20, the service provider device 30, and the inter-application cooperation device 40.

[0024] Furthermore, the inter-application cooperation device 40 has a connection interface with the payment / authentication provider device 20 (hereinafter referred to as the "payment / authentication provider I / F") and a connection interface with the service provider device 30 (hereinafter referred to as the "service provider I / F"). The inter-application cooperation device 40 transmits and receives data to and from the payment / authentication provider device 20 via the payment / authentication provider I / F, and transmits and receives data to and from the service provider device 30 via the service provider I / F. The payment / authentication provider I / F and the service provider I / F may be, for example, an API.

[0025] Fig. 2 is a diagram showing an example of a linkage model according to the present embodiment. In Fig. 2, the payment / authentication application and the service application are installed in the same terminal 10, but this is not limiting and they may be installed in different terminals 10. The order of steps S101 and S102 may be interchanged.

[0026] In the collaboration model shown in FIG. 2, when a service provided by a service app to a user requires payment and / or authentication, the inter-application collaboration device 40 verifies the identity of the user of the payment / authentication app and the user of the service app in response to a token / certificate issuance request from either the payment / authentication app or the service app, and provides the service app with a token / certificate issued by the payment / authentication business based on the verification result of the identity.

[0027] 2, in response to a token / certificate issuance request from either the payment / authentication app or the service app to the service app, a user verification process is performed between the payment / authentication business device 20, the payment / authentication app, and the user via the inter-application cooperation device 40. In the verification process, the inter-application cooperation device 40 acquires verification information related to the user of the payment / authentication app (hereinafter referred to as "payment / authentication user verification information").

[0028] In step S102, in response to the issuance request, a user verification process is performed between the service provider device 30, the service app, and the user via the inter-application cooperation device 40. In the verification process, the inter-application cooperation device 40 obtains verification information related to the user of the service app (hereinafter, referred to as "service user verification information") from the service provider device 30.

[0029] Here, the user verification process in step S101 is a process for verifying that the user is a legitimate user of the payment / authentication application. Also, the user verification process in step S102 is a process for verifying that the user is a legitimate user of the service application. The user verification process in steps S101 and S102 may be (1) a high level (hereinafter referred to as "high level") identity verification required by the Act on Prevention of Transfer of Criminal Proceeds, and / or (2) identity verification at a level lower than the high level identity verification. In the (1) high level identity verification, for example, identity verification may be performed using at least two of knowledge information (for example, a password, a PIN code, or a secret question, etc.), possession information (for example, SIM card information, a hard token, or an IC card, etc.), and biometric information (for example, a face, a fingerprint, a vein, a voiceprint, etc.). Note that the high level identity verification may be called identity authentication. In the (2) low level identity verification, for example, identity verification using knowledge information may be performed. Alternatively, the method may be a method of simply verifying the identity of a user by comparing user information in a customer database held by a service provider, financial institution, payment provider, public institution, or other provider with information provided by the user, and verifying the identity of the user if the information matches. For example, a low level of identity verification may be performed between the payment / authentication provider device 20 and the payment / authentication app, and a high level of identity verification (identification) may be performed between the payment / authentication app and the user. Similarly, a low level of identity verification may be performed between the service provider device 30 and the service app, and a high level of identity verification (identification) may be performed between the service app and the user.

[0030] In step S103, the inter-application cooperation device 40 verifies the identity of the user of the payment / authentication application and the user of the service application based on the payment / authentication user identification information acquired in step S101 and the service user identification information acquired in step S102. If the identity of the user of the payment / authentication application and the user of the service application is verified, in step S104, the inter-application cooperation device 40 provides the token / certificate issued by the payment / authentication business device 20 to the service application.

[0031] In step S105, a service is provided to the user by the service app that has acquired the token / certificate issued by the payment / authentication service provider device 20. In order to provide the service to the user, the service app may perform a process related to payment between the service app and the payment / authentication service provider device 20, using the acquired token. The service app may also perform a process related to authentication between the service app and the payment / authentication service provider device 20, using the acquired digital certificate.

[0032] In this manner, in the information processing system 1 according to the present embodiment, when the use of a payment function and / or authentication function is required when a service is provided by a service app, the identity of the user of the payment / authentication app and the user of the service app is verified, and then a token / certificate for the payment / authentication app is issued to the service app from the payment / authentication business device 20. Therefore, while ensuring a certain level of security, it is possible to link the token / certificate between the payment / authentication app and the service app, thereby improving the satisfaction of the user who uses the service app.

[0033] (composition) Next, the physical configuration and functional configuration of the information processing system 1 according to this embodiment will be described. <Physical configuration> 3 is a diagram showing an example of a physical configuration of each device in the information processing system 1 according to this embodiment. Each device in the information processing system 1 (e.g., the terminal 10, the payment / authentication company device 20, the service provider device 30, and the inter-application cooperation device 40) includes a processor 101, a storage unit 102, a transmission / reception unit 103, and an input / output unit 104.

[0034] The processor 101 is, for example, a CPU (Central Processing Unit) and controls each device in the information processing system 1. The processor 101 may execute various processes described in this embodiment by reading and executing a program from the storage unit 102. Each device in the information processing system 1 may be configured with one or more processors 101. Furthermore, each of the devices may be called a computer.

[0035] The storage unit 102 is configured with, for example, storage such as a memory, a hard disk drive (HDD) and / or a solid state drive (SSD), etc. The storage unit 102 may store various information necessary for the processor 101 to execute processing (for example, a program executed by the processor 101, etc.).

[0036] The transmitting / receiving unit 103 is a device that performs communication via the network 50, and may include, for example, a network card, a communication module, a chip, an antenna, etc. The transmitting / receiving unit 103 may include a transmitting unit that transmits various information via the network 50 and / or a receiving unit that receives various information via the network 50.

[0037] The input / output unit 104 includes an input unit such as a keyboard, a touch panel, a mouse, and / or a microphone, an output unit such as a display and / or a speaker, and an imaging unit such as a camera. The input unit accepts input of various information from a user. The output unit may include a display unit that displays various information for the user.

[0038] The physical configuration described above is merely an example. Each device in the information processing system 1 may omit some of the hardware shown in Fig. 3, or may include hardware not shown in Fig. 3. Furthermore, the hardware shown in Fig. 3 may be configured by one or more chips.

[0039] <Functional configuration> FIG. 4 is a diagram showing an example of a functional configuration of the terminal 10 and the inter-application cooperation device 40 according to the present embodiment. <Device> As shown in Fig. 4, terminal 10 includes a payment / authentication application unit 11 that performs various processes provided by a payment / authentication application and a service application unit 12 that performs various processes provided by a service application. The function of payment / authentication application unit 11 is realized by processor 101 of terminal 10 executing a program of a payment / authentication application stored in storage unit 102 of terminal 10. Furthermore, the function of service application unit 12 is realized by processor 101 of terminal 10 executing a program of a service application stored in storage unit 102 of terminal 10. Note that when the payment / authentication application and the service application are installed on different terminals 10, each terminal 10 may include either the payment / authentication application unit 11 or the service application unit 12.

[0040] 4, payment / authentication application unit 11 includes issuance request unit 111 and user confirmation unit 112. Note that issuance request unit 111 may be omitted when issuance request unit 121 is provided in service application unit 12, which will be described later.

[0041] The issuance request unit 111 may request the inter-application cooperation device 40 to issue, to the service application unit 12, a token / certificate used in the payment / authentication application unit 11. For example, in response to reception of an input from a user by the input / output unit 104, the issuance request unit 111 may cause the transmission / reception unit 103 to transmit an issuance request for the token / certificate to the inter-application cooperation device 40.

[0042] Here, the issuance request may include at least one of information on the payment / authentication app (hereinafter referred to as "payment / authentication app information"), information on the service app to which the token / certificate is to be issued (hereinafter referred to as "service app information"), and information on the token / certificate (hereinafter referred to as "token / certificate information"). The issuance request may also include identification information of the user of the payment / authentication app (hereinafter referred to as "payment / authentication user ID").

[0043] The payment / authentication app information may include, for example, at least one of identification information of the payment / authentication app (hereinafter referred to as the "payment / authentication app ID") and identification information of the payment / authentication business that provides the payment / authentication app (hereinafter referred to as the "payment / authentication business ID").

[0044] Furthermore, the service application information may include, for example, at least one of identification information of the service application (hereinafter referred to as a "service application ID") and identification information of a service provider that provides the service application (hereinafter referred to as a "service provider ID").

[0045] The token / certificate information may include at least one of token identification information (hereinafter referred to as "token ID"), digital certificate identification information (hereinafter referred to as "certificate ID"), and type information. The type information may indicate whether issuance of a token or a digital certificate is requested, or may indicate that issuance of both a token and a digital certificate is requested.

[0046] The user confirmation unit 112 performs a process of confirming the user of the payment / authentication app. Specifically, the user confirmation unit 112 performs a process of confirming the user of the payment / authentication app between the payment / authentication service provider device 20 in response to a confirmation request from the inter-application cooperation device 40. For example, the user confirmation unit 112 may perform a process of confirming the user of the payment / authentication app between the payment / authentication service provider device 20 in the confirmation process.

[0047] On the other hand, service application unit 12 includes issuance request unit 121, user confirmation unit 122, acquisition unit 123, and service unit 124. Note that when issuance request unit 111 is provided in payment / authentication application unit 11, issuance request unit 121 may be omitted.

[0048] The issuance request unit 121 may request the inter-application cooperation device 40 to issue a token / certificate used in the payment / authentication application unit 11 to the service application unit 12. For example, the issuance request unit 121 may cause the transmission / reception unit 103 to transmit an issuance request for the token / certificate to the inter-application cooperation device 40 in response to reception of an input from a user by the input / output unit 104. The issuance request is as described for the issuance request unit 111. The issuance request by the issuance request unit 121 may include identification information of a user of the service application (hereinafter referred to as a "service user ID").

[0049] The user confirmation unit 122 performs a process of confirming the user of the service app. Specifically, the user confirmation unit 122 performs a process of confirming the user of the service app with the service provider device 30 in response to a confirmation request from the inter-application cooperation device 40. For example, the user confirmation unit 122 may perform a process of confirming the user of the service app with the service provider device 30 in the confirmation process.

[0050] The acquisition unit 123 acquires the token / certificate issued by the payment / authentication business operator device 20 in response to an issuance request from the issuance request unit 111 or the issuance request unit 121. Specifically, the acquisition unit 123 may acquire the token / certificate received from the inter-application cooperation device 40 by the transmission / reception unit 103.

[0051] The service unit 124 provides a service to the user. Specifically, the service unit 124 provides the service to the user by using the token / certificate acquired by the acquisition unit 123. For example, in order to provide the service, the service unit 124 may perform a process related to payment with the payment / authentication provider device 20 by using the token acquired by the acquisition unit 123. In addition, in order to provide the service, the service unit 124 may perform a process related to authentication with the payment / authentication provider device 20 by using the electronic certificate acquired by the acquisition unit 123.

[0052] <Inter-app linking device> 4, the inter-application cooperation device 40 includes an acquisition unit 41, a user confirmation unit 42, a verification unit 43, and a provision unit 44. Note that the processor 101 of the inter-application cooperation device 40 executes a program stored in the storage unit 102 of the inter-application cooperation device 40, thereby realizing at least some functions of the acquisition unit 41, the user confirmation unit 42, the verification unit 43, and the provision unit 44, which will be described later.

[0053] The acquisition unit 41 acquires an issuance request requesting that a token / certificate used in a payment / authentication application provided by the payment / authentication business device 20 be issued to a service application provided by the service provider device 30. Specifically, the acquisition unit 41 acquires the issuance request from the terminal 10 received by the transmission / reception unit 103 of the inter-application cooperation device 40. The issuance request may be one requested by either the issuance request unit 111 or the issuance request unit 121.

[0054] The user confirmation unit 42 performs a process of confirming the user of the payment / authentication app and the user of the service app installed in the terminal 10 in response to the issuance request acquired by the acquisition unit 41. Specifically, the user confirmation unit 42 may acquire payment / authentication user confirmation information from the payment / authentication business device 20 in the process of confirming the user of the payment / authentication app. The user confirmation unit 42 may also acquire service user confirmation information from the service provider device 30 in the process of confirming the user of the service app.

[0055] Here, the payment / authentication user confirmation information may include at least one of the confirmation result of the user of the payment / authentication app and the attribute information of the user. The user attribute information may include at least one of the user's name, phone number, email address, date of birth, postal code, gender, age, and if the user is a corporation, the company name, trade name, and representative name, etc. Furthermore, the service user confirmation information may include at least one of the confirmation result of the user of the service app and the attribute information of the user.

[0056] The user confirmation unit 42 determines the connection destination payment / authentication service provider device 20 based on the payment / authentication application information (e.g., payment / authentication application ID or payment / authentication service provider ID) included in the issuance request. The user confirmation unit 42 may transmit a request for confirmation processing of the user of the payment / authentication application (hereinafter referred to as a "payment / authentication user confirmation request") to the payment / authentication service provider device 20 via the transmission / reception unit 103, and receive payment / authentication user confirmation information from the payment / authentication service provider device 20 via the transmission / reception unit 103 in response to the payment / authentication user confirmation request.

[0057] When the issuance request acquired by the acquisition unit 41 includes the payment / authentication user ID (i.e., when the payment / authentication user ID is linked), the user confirmation unit 42 may include the payment / authentication user ID in a payment / authentication user confirmation request to the payment / authentication business. Based on the payment / authentication user ID, the payment / authentication business device 20 may perform a process of confirming the user of the payment / authentication app.

[0058] On the other hand, if the issuance request acquired by acquisition unit 41 does not include the payment / authentication user ID (i.e., if the payment / authentication user ID is not linked), user confirmation unit 42 may acquire the payment / authentication user ID from payment / authentication application unit 11 of terminal 10, and include the payment / authentication user ID in a payment / authentication user confirmation request to payment / authentication service provider device 20. Based on the payment / authentication user ID, payment / authentication service provider device 20 may perform a process of confirming the user of the payment / authentication application.

[0059] Furthermore, the user confirmation unit 42 determines the service provider device 30 to which the connection is to be made based on the service app information (e.g., a service app ID or a service provider ID) included in the issuance request. The user confirmation unit 42 may transmit a request for confirmation processing of the user of the service app (hereinafter referred to as a "service user confirmation request") to the service provider device 30 via the transmission / reception unit 103, and may receive service user confirmation information from the service provider device 30 via the transmission / reception unit 103 in response to the service user confirmation request.

[0060] When the service user ID is included in the issuance request acquired by the acquisition unit 41 (i.e., when the service user ID is linked), the user confirmation unit 42 may include the service user ID in a service user confirmation request to the service provider. Based on the service user ID, the service provider device 30 may perform a process of confirming the user of the service app.

[0061] On the other hand, if the issuance request acquired by the acquisition unit 41 does not include the service user ID (i.e., if the service user ID is not linked), the user confirmation unit 42 may acquire the service user ID from the service application unit 12 of the terminal 10, and include the service user ID in the service user confirmation request to the service provider device 30. Based on the service user ID, the service provider device 30 may perform a process of confirming the user of the service app.

[0062] The verification unit 43 verifies the identity of the user of the payment / authentication app and the user of the service app in response to the issuance request acquired by the acquisition unit 41. Specifically, the verification unit 43 may verify the identity based on the payment / authentication user confirmation information acquired by the user confirmation unit 42 (e.g., at least one of the confirmation result of the user of the payment / authentication app and attribute information of the user) and the service user confirmation information (e.g., at least one of the confirmation result of the user of the service app and attribute information of the user).

[0063] For example, the verification unit 43 may verify the identity of the user of the payment / authentication application and the user of the service application by comparing the verification result of the user of the payment / authentication application and the verification result of the user of the service application. When the user verified by the payment / authentication business device 20 and the user verified by the service business device match, the verification unit 43 may determine that the user of the payment / authentication application and the user of the service application are the same.

[0064] Furthermore, the verification unit 43 may verify the identity of the user of the payment / authentication application and the user of the service application by comparing attribute information of the user of the payment / authentication application and attribute information of the user of the service application. When the user indicated by the attribute information acquired from the payment / authentication business device 20 and the user indicated by the attribute information acquired from the service business device match, the verification unit 43 may determine that the user of the payment / authentication application and the user of the service application are the same.

[0065] When the user of the payment / authentication application and the user of the service application are not the same, the verification unit 43 may transmit error information to the application that requested the issuance of the token / certificate (payment / authentication application unit 11 or service application unit 12) via the transmission / reception unit 103. Based on the error information, the terminal 10 may notify the user of the application that requested the issuance of the token / certificate that the issuance process of the token / certificate has been stopped. For example, the terminal 10 may output information indicating the stop of the issuance process to the input / output unit 104 (for example, display on a display unit). Furthermore, the error information may be transmitted to the payment / authentication business device 20 and / or the service provider device 30.

[0066] When the user of the payment / authentication application and the user of the service application are the same, the verification unit 43 may instruct the provision unit 44 to provide the token / certificate to the service application.

[0067] The providing unit 44 provides the service application with a token / certificate issued by a payment / authentication business operator, based on the result of the verification by the verifying unit 43 of the identity of the user of the payment / authentication application and the user of the service application.

[0068] Specifically, when the identity of the payment / authentication application user and the service application user is verified by verification unit 43, providing unit 44 transmits a token / certificate issuance request to payment / authentication business device 20 via transmission / reception unit 103. The issuance request transmitted to the payment / authentication business may be based on at least one of the payment / authentication application information, the service app information, and the token / certificate information included in the issuance request from payment / authentication application unit 11 or service application unit 12 (it may include at least one of the payment / authentication application information, the service app information, and the token / certificate information).

[0069] For example, the providing unit 44 may transmit an issuance request for either a token or an electronic certificate, or an issuance request for both a token and an electronic certificate to the payment / authentication provider device 20 based on type information included in the issuance request from the payment / authentication application unit 11 or the service application unit 12.

[0070] (operation) The operation of information processing system 1 according to this embodiment will be described with reference to Figures 5 and 6. Note that, in Figures 5 and 6, the payment / authentication application and the service application are installed on the same terminal 10, but this is not limiting and they may be installed on different terminals 10. That is, in Figures 5 and 6, the same terminal 10 is equipped with both the payment / authentication application unit 11 and the service application unit 12, but this is not limiting and it goes without saying that the same operation can be performed in the case where one terminal 10 is equipped with the payment / authentication application unit 11 and the other terminal 10 is equipped with the service application unit 12.

[0071] Fig. 5 is a diagram showing an example of the operation of the information processing system 1 according to this embodiment. Fig. 5 illustrates a case in which the payment / authentication application unit 11 of the terminal 10 accepts a token / certificate issuance request for the service application unit 12 of the terminal 10.

[0072] 5 may be omitted, or a step not shown may be added, or the order of at least two steps may be changed and / or performed in parallel. For example, steps S203 to S205 and steps S206 to S208 in FIG. 5 may be performed in parallel, or steps S206 to S208 may be performed before steps S203 to S205.

[0073] In step S201, payment / authentication application unit 11 accepts a token / certificate issuance request input by the user via input / output unit 104 to service application unit 12.

[0074] In step S202, payment / authentication application unit 11 transmits the issuance request acquired in step S201 to inter-application cooperation device 40 via transmission / reception unit 103.

[0075] In step S203, in response to the issuance request received in step S202, the inter-application cooperation device 40 transmits the payment / authentication user confirmation request to the payment / authentication business device 20. As described above, the payment / authentication user confirmation request may include a payment / authentication user ID, which may be included in the issuance request in step S202, or may be acquired from the payment / authentication application unit 11 in response to a request (not shown) from the inter-application cooperation device 40.

[0076] In step S204, the payment / authentication service provider device 20 performs a process of verifying the user of the payment / authentication application with the payment / authentication application unit 11 in response to the payment / authentication user verification request from the inter-application cooperation device 40. Specifically, the payment / authentication service provider device 20 may perform a process of verifying the user with the payment / authentication application unit 11 based on the payment / authentication user ID included in the authentication / payment user verification request. For example, the payment / authentication service provider device 20 may obtain attribute information of a user identified by the payment / authentication user ID and transmit the attribute information to the terminal 10. The payment / authentication application unit 11 matches the attribute information with information about the user input to the payment / authentication application unit 11 (hereinafter referred to as "user information"). The user information may be, for example, at least one of knowledge information (e.g., user ID, password), biometric information (e.g., captured image of the user, fingerprint, etc.) and possession information (e.g., SIM card number stored in the terminal 10) input to the payment / authentication application. The user information may be input on an input screen that payment / authentication application unit 11 causes to be displayed on the display unit, may be captured by an imaging unit activated by payment / authentication application unit 11, or may be acquired via payment / authentication application unit 11. If payment / authentication application unit 11 matches the attribute information with the user information, this operation may proceed to step S205, and if the matching results do not match, this operation may end.

[0077] In step S205, the inter-application cooperation device 40 receives payment / authentication user confirmation information based on the result of the confirmation process in step S204 from the payment / authentication business device 20. The payment / authentication user confirmation information may include at least one of the confirmation result of the user in step S204 and attribute information of the user.

[0078] In step S206, in response to the issuance request received in step S202, the inter-application cooperation device 40 transmits the above-mentioned service user confirmation request to the service provider device 30. As described above, the service user confirmation request may include a service user ID, and the service user ID may be included in the issuance request of step S202, or may be acquired from the service application unit 12 in response to a request (not shown) from the inter-application cooperation device 40.

[0079] In step S207, the service provider device 30 performs a process of verifying the user of the service app with the service application unit 12 in response to the service user verification request from the inter-application cooperation device 40. Specifically, the service provider device 30 may perform a process of verifying the user with the service application unit 12 based on the service user ID included in the service user verification request. For example, the service provider device 30 may acquire attribute information of the user identified by the service user ID and transmit the attribute information to the terminal 10. The service application unit 12 matches the attribute information with the user information input to the service application unit 12. The user information may be at least one of knowledge information (e.g., user ID, password), biometric information (e.g., captured image of the user, fingerprint, etc.), and possession information (e.g., SIM card number stored in the terminal 10) input to the service app. The user information may be input on an input screen that the service application unit 12 causes to be displayed on the display unit, may be captured by an imaging unit activated by the service application unit 12, or may be acquired through the service application unit 12. If the service application unit 12 finds a match between the attribute information and the user information, the operation proceeds to step S208, and if the match does not find a match between the attribute information and the user information, the operation may end.

[0080] In step S208, the inter-application cooperation device 40 receives service user confirmation information based on the result of the confirmation process in step S207 from the service provider device 30. The service user confirmation information may include at least one of the confirmation result of the user in step S207 and attribute information of the user.

[0081] In step S209, the inter-application cooperation device 40 verifies the identity of the user of the payment / authentication application and the user of the service application, based on the payment / authentication user confirmation information received in step S205 and the service user confirmation information received in step S208. For example, when positive confirmation results are input by the user in steps S204 and S207 and the users match, the inter-application cooperation device 40 may determine that the user of the payment / authentication application and the user of the service application are the same.

[0082] In step S210, when the identity of the payment / authentication application user and the service application user is verified, inter-application cooperation device 40 transmits a token / certificate issuance request to payment / authentication business device 20. The issuance request in step S210 may be based on at least one of the payment / authentication application information, service application information, and token / certificate information included in the issuance request in step S202 (and may include at least one of the payment / authentication application information, service application information, and token / certificate information). For example, the issuance request in step S210 may request issuance of either a token or a digital certificate, or both a token and a digital certificate, based on type information included in the issuance request in step S202.

[0083] In step S211, the inter-application cooperation device 40 receives the token / certificate transmitted by the payment / authentication business device 20 in response to the issuance request in step S210.

[0084] In step S212, the inter-application cooperation device 40 provides the token / certificate received from the payment / authentication business device 20 in step S211 to the service application unit 12. The service application unit 12 receives the token / certificate via the transmission / reception unit 103.

[0085] In step S213, the service application unit 12 provides a service to the user by using the token / certificate provided by the inter-application cooperation device 40 in step S212. For example, the service application unit 12 may provide the user with a service requiring payment by performing a process related to payment with the payment / authentication provider device 20 by using the provided token. Also, the service application unit 12 may provide the user with a service requiring authentication by performing a process related to authentication with the payment / authentication provider device 20 by using the provided electronic certificate.

[0086] Fig. 6 is a diagram showing another example of the operation of the information processing system 1 according to the present embodiment. Fig. 6 illustrates a case where the service application unit 12 of the terminal 10 accepts a request for issuing a token / certificate for a payment / authentication application for itself. Note that Fig. 6 mainly describes the differences from Fig. 5, and the description of the similar points will not be repeated.

[0087] As shown in FIG. 6, in step S301, the service application unit 12 accepts a request, input by the user via the input / output unit 104, for the service application unit 12 to issue a token / certificate for the payment / authentication application.

[0088] In step S302, the service application unit 12 transmits the issuance request acquired in step S301 to the inter-application cooperation device 40 via the transmission / reception unit 103. Steps S303 to S313 are similar to steps S203 to S213 in FIG.

[0089] As described above, in the information processing system 1 according to the present embodiment, when the use of a payment function and / or authentication function is required when a service is provided by a service app, the identity of the user of the payment / authentication app and the user of the service app is verified, and then a token / certificate for the payment / authentication app is issued to the service app from the payment / authentication business device 20. Therefore, while ensuring a certain level of security, it is possible to link the token / certificate between the payment / authentication app and the service app, thereby contributing to the satisfaction of the user who uses the service app.

[0090] (Other embodiments) The above-described embodiments are intended to facilitate understanding of the present invention, and are not intended to limit the present invention. The elements of the embodiments, as well as their arrangements, materials, conditions, shapes, sizes, etc., are not limited to those shown as examples and can be changed as appropriate. In addition, configurations shown in different embodiments can be partially substituted or combined with each other. [Explanation of symbols]

[0091] 1...information processing system, 10...terminal, 20...payment / authentication business device, 30...service business device, 40...inter-application cooperation device, 50...network, 11...authentication application unit, 12...service application unit, 41...acquisition unit, 42...user confirmation unit, 43...verification unit, 44...providing unit, 111...issuance request unit, 112...user confirmation unit, 121...issuance request unit, 122...user confirmation unit, 123...acquisition unit, 124...service unit, 101...processor, 102...storage unit, 103...transmission / reception unit, 104...input / output unit,

Claims

1. Computer, an acquisition unit that acquires an issuance request for requesting that a token and / or a digital certificate used in a first application provided by a first business be issued to a second application provided by a second business; a verification unit that verifies the identity of the user of the first application and the user of the second application in response to the issuance request; a providing unit that receives the token and / or the electronic certificate from a first business operator device that is an information processing device of the first business operator based on a result of the verification of the identity, and provides the token and / or the electronic certificate to the second application, the token and / or the electronic certificate being issued by the first business operator device, based on the result of the verification of the identity; An information processing program that functions as a

2. a user confirmation unit that, in response to the issuance request, acquires first confirmation information related to a user of the first application from the first business operator device, and acquires second confirmation information related to the user of the second application from a second business operator device that is an information processing device of the second business operator; The verification unit verifies the identity based on the first confirmation information and the second confirmation information. The information processing program according to claim 1.

3. the providing unit, when the identity is verified by the verifying unit, requests the first business operator device to issue the token and / or the electronic certificate, receives the token and / or the electronic certificate issued by the first business operator device in response to the request from the first business operator device, and provides the token and / or the electronic certificate to the second application.

3. The information processing program according to claim 2.

4. The acquisition unit acquires the issuance request from the first application or the second application.

4. The information processing program according to claim 1.

5. an acquisition unit that acquires an issuance request for requesting that a token and / or a digital certificate used in a first application provided by a first business be issued to a second application provided by a second business; a verification unit that verifies the identity of the user of the first application and the user of the second application in response to the issuance request; a providing unit that receives the token and / or the electronic certificate from a first business operator device that is an information processing device of the first business operator based on a result of the verification of the identity, and provides the token and / or the electronic certificate to the second application, the token and / or the electronic certificate being issued by the first business operator device, based on the result of the verification of the identity; An information processing device comprising:

6. obtaining an issuance request for issuing a token and / or a digital certificate for use in a first application provided by a first business operator to a second application provided by a second business operator; In response to the issuance request, verifying the identity of the first application user and the second application user; receiving, based on a result of the verification of the identity, the token and / or the electronic certificate issued by a first business device, which is an information processing device of the first business device, from the first business device and providing the token and / or the electronic certificate to the second application; The information processing method of the information processing device having the above configuration.

Images