JP2010128554A - Account issuing system, allocation device, registration device, account issuing method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To flexibly control allocation of an account by a service provision server while preventing leakage of personal information that is information about a user oneself of a terminal. <P>SOLUTION: The service provision server 2 allocate an ID (Identification) to the terminal 3. An authentication server 1 transmits a password stored associatively to the ID to the terminal 3 when server identification information and the ID are transmitted from the terminal 3. The terminal 3 transmits the ID and the password to the service provision server 2. The service provision server 2 provides service to the user of the terminal 3 based on the ID and the password. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an account issuing system, an assigning device, a registration device, an account issuing method, and a program.

  In recent years, various services have been provided to terminals used by users via the Internet. At this time, a system that performs user authentication using an account (for example, a combination of an ID and a password) issued to the user in advance and provides a service to the terminal when the authentication is successful has become widespread. Yes.

  When this account is issued without specifying individual users, a plurality of accounts are issued to the same user. That is, in such a case, the same user can use a plurality of accounts.

  In addition, a service provider that provides a service may want to determine that certain accounts are managed by the same individual and that certain accounts are managed by another person in the service providing server. For example, knowing which set of accounts is managed by the same individual, knowing what the actual number of users is, and one person to obtain accurate results in polls and surveys. There is a demand to issue only one account to one individual in order to realize that only votes are cast.

  In such a case, the user is authenticated using personal information (for example, real name, biometric information, etc.) about the user himself / herself that is different for each user, and after identifying the same individual A method of assigning only one account to a user is considered.

  However, if personal information such as real name or biometric information for user authentication is leaked to an unspecified third party, the user specified by the personal information is seriously damaged. There is a risk that.

  In order to prevent personal information from leaking in this way, a technique is proposed in which the above-described user authentication is performed by a reliable third-party authentication server instead of the service providing server that provides the service. Has been.

  For example, a method may be considered in which an authentication server issues an account of the service providing server instead of the service providing server itself that provides a service to a user terminal, and the authentication server performs personal authentication using the issued account. (For example, refer to Patent Document 1).

  There is also a method in which the authentication server transmits a digital certificate that guarantees the identity of the user to the terminal of the user and then authenticates the user using the digital certificate (for example, (See Patent Document 2).

  As a technique related to a method for authenticating a user using such a digital certificate, there is an electronic signature for performing identity verification.

  However, if the electronic signature is leaked to an unspecified third party, there is a risk that the third party may be illegally infiltrated by impersonation or the like. Therefore, the electronic signature is used in cooperation with a digital certificate issued by a reliable third party.

When issuing this digital certificate by a third party, first, in the terminal used by the user, the user manages the public key and is also disclosed to a third party other than the user, and the user A private key managed only by the public key encryption method is generated. Thereafter, the user transmits the generated public key and user information about the user to the third party from the terminal, and requests the digital signature to be issued. Then, when the third party organization is able to confirm the identity of the user based on the user information or the like, the third party organization is digital data that is the data obtained by adding the electronic signature of the third party organization to the user information and the public key. A signature is generated and transmitted to the user terminal.
Japanese Patent No. 2002-183484 JP 2007-074349 A

  However, in the technology in which the authentication server assigns the account of the service providing server to the user and authenticates the user, the authentication server determines whether to assign the account to the user, not the service providing server. For this reason, there is a problem that the service provider that owns the service providing server cannot flexibly control account assignment. This makes it difficult for the service providing server to control the number of accounts assigned to each user. For example, it becomes difficult to assign one account in the service providing server to one user.

  Another problem is that the authentication server must store the personal information of the user and the server identification information for identifying the service providing server in association with each other in order to determine whether the assignment is possible. .

  In the above-described technology for authenticating the user using the user's public key, a third party other than the user is notified to notify that the user's public key belongs to the user himself / herself. It must be made public.

  Therefore, the third party uses the public key assigned by checking whether the public key is used for each of a plurality of service providing servers based on the public key. There is a problem that it becomes possible to track a person (so-called “name identification”).

  And when a user is specified by name collation, there exists a possibility that the personal information about the said user himself may leak. Therefore, there is a problem that the technology for authenticating the user using the electronic signature cannot sufficiently protect the user's privacy.

  An object of the present invention is to provide an account issuing system, an allocation device, a registration device, an authentication method, and a program that solve the above-described problems.

  In order to solve the above problems, an account issuing system according to the present invention includes a terminal used by a user, a registration device that provides services to the terminal, and an allocation device connected to the terminal and the registration device. In the account issuing system configured as described above, the allocation device stores a correspondence between a preset ID (Identification) and service necessary information necessary for receiving the service, and allocates service necessary information to the user. When the information allocation request for requesting is transmitted from the terminal, the service necessary information stored in association with the ID transmitted from the terminal together with the information allocation request is allocated to the user and transmitted to the terminal. The terminal transmits an ID allocation request for requesting allocation of the ID to a user of the terminal to the registration device, and the registration device The ID and the information allocation request transmitted from the allocation apparatus are transmitted to the allocation apparatus, the service necessary information transmitted from the allocation apparatus and the ID transmitted from the registration apparatus are transmitted to the registration apparatus, The registration device stores a correspondence between the preset ID and service necessary information, and when the ID allocation request is transmitted from the terminal, an arbitrary ID is used from the stored ID. When the ID and the service necessary information are transmitted from the terminal, the service is provided to the terminal based on the ID and the service necessary information.

  In order to solve the above-described problem, an allocation apparatus according to the present invention is an allocation apparatus connected to a terminal used by a user and a registration apparatus that provides a service to the terminal, and includes a preset ID (Identification ) And service necessary information necessary for receiving the service, and when an information allocation request for requesting allocation of service necessary information to the user is transmitted from the terminal, An information allocation unit that allocates service required information stored in association with an ID transmitted from the terminal together with the information allocation request to the user and transmits the information to the terminal.

  In order to solve the above problems, a registration apparatus according to the present invention is a registration apparatus that is connected to a terminal used by a user and an allocation apparatus connected to the terminal and provides a service to the terminal, and is set in advance. A storage unit that stores a correspondence between an ID (Identification) and necessary service information necessary for receiving the service, and an ID allocation request for requesting allocation of the ID to the user are transmitted from the terminal. An ID assigning unit that assigns an arbitrary ID from the stored information to the user and transmits it to the terminal, and when the terminal transmits the ID and the service necessary information, the ID and the ID And a service providing unit that provides the service to the terminal based on service necessary information.

  In order to solve the above problems, an account issuing method according to the present invention includes a terminal used by a user, a registration device that provides a service to the terminal, and an allocation device connected to the terminal and the registration device. An account issuing method in a configured account issuing system, wherein the assigning device stores a correspondence between a preset ID (Identification) and service required information necessary for receiving the service; A process in which the registration device stores the association between the preset ID and service necessary information, and the terminal transmits an ID assignment request for requesting the assignment of the ID to the user of the terminal to the registration device. And when the ID allocation request is transmitted from the terminal, the registration device forwards an arbitrary ID from the stored information. An ID allocation process for allocating to a user and transmitting to the terminal, an ID transmitted from the registration apparatus by the terminal, and an information allocation request for requesting allocation of service required information to the user And when the information allocation request is transmitted from the terminal, the allocation apparatus stores service necessary information stored in association with the ID transmitted from the terminal together with the information allocation request. Information allocation processing to be allocated to the user and transmitted to the terminal, and processing for the terminal to transmit service required information transmitted from the allocation device and ID transmitted from the registration device to the registration device And the registration apparatus, when the ID and the service necessary information are transmitted from the terminal, the service based on the ID and the service necessary information. Service providing processing for providing the terminal to the terminal.

  Also, a program to be executed by a computer, which receives an ID (Identification) set in advance and the service to an allocation device connected to a terminal used by a user and a registration device that provides a service to the terminal. A procedure for storing the association with the necessary service information necessary for storage in the storage unit and an information allocation request for requesting the allocation of the necessary service information to the user are transmitted from the terminal together with the information allocation request An information allocation procedure for allocating the service necessary information stored in association with the ID transmitted from the terminal to the user and transmitting the information to the terminal is executed.

  In addition, a program to be executed by a computer, which is connected to a terminal used by a user and an allocation apparatus connected to the terminal, and a ID (Identification) set in advance in a registration apparatus that provides a service to the terminal A procedure for storing a correspondence with service necessary information necessary for receiving the service in a storage unit and an ID assignment request for requesting assignment of the ID to the user is transmitted from the terminal, An ID allocation procedure for allocating an arbitrary ID from the stored information to the user and transmitting it to the terminal, and when the terminal transmits the ID and the service necessary information, the ID and the service necessary information And a service providing procedure for providing the service to the terminal.

  According to the present invention, in an account issuing system comprising a terminal used by a user, a registration device that provides a service to the terminal, and an allocation device connected to the terminal and the registration device, the allocation device Stores a correspondence between a preset ID (Identification) and service necessary information necessary for receiving the service. The registration device also stores a correspondence between a preset ID and service necessary information.

  The terminal transmits an ID allocation request for requesting ID allocation to the user of the terminal to the registration device. Then, the registration device assigns an arbitrary ID from the stored information to the user and transmits it to the terminal. Then, the terminal transmits the ID transmitted from the registration device and the information allocation request for requesting allocation of service necessary information to the user to the allocation device. When the information allocation request is transmitted from the terminal, the allocation apparatus allocates the service necessary information stored in association with the ID transmitted from the terminal to the user and transmits it to the terminal.

  Thereafter, the terminal transmits the service necessary information transmitted from the allocation device and the ID transmitted from the registration device to the registration device. Then, when the ID and the service necessary information are transmitted from the terminal, the registration device provides a service to the terminal based on the ID and the service necessary information.

  With this configuration, the registration device (for example, the service providing server) can flexibly control account assignment while preventing leakage of personal information, which is information about the terminal user itself, and It is unnecessary for the device (for example, the authentication server) to store the personal information of the user and the server identification information of the service providing server in association with each other.

(Embodiment 1)
Hereinafter, an account issuing system (including an allocation device, a registration device, an account issuing method, and a program) according to the first embodiment of the present invention will be described.

  First, the overall configuration of the account issuing system according to the first embodiment will be described.

  As shown in FIG. 1, the account issuing system includes an allocation device 1, a registration device 2, and a terminal 3.

  Each of the storage unit 14 included in the allocation device 1 and the storage unit 22 included in the registration device 2 includes an ID (Identification) for identifying each user of the terminal 3 and a service provided by the registration device 2. The association with “service required information”, which is information necessary for receiving, is stored.

  The terminal 3 transmits an “ID allocation request” for requesting ID allocation to the user of the terminal 3 to the registration device 2.

  Then, the ID assigning unit 23 of the registration device 2 assigns an arbitrary ID from among those stored in the storage unit 22 to the user and transmits it to the terminal 3.

  Thereafter, the terminal 3 transmits an “information allocation request” to the allocation apparatus 1 together with the ID transmitted from the registration apparatus 2.

  Then, the information allocating unit 18 of the allocating device 1 reads the service necessary information associated with the ID transmitted from the terminal 3 from the storage unit 14 and outputs the service necessary information and the ID to the communication unit 11. Subsequently, the communication unit 11 transmits the service necessary information and the ID to the terminal 3.

  Then, the terminal 3 transmits a “service provision request” for requesting provision of the service to the registration apparatus 2 together with the service necessary information and the ID transmitted from the allocation apparatus 1.

  Then, the registration device 2 authenticates the user by using the ID and service necessary information transmitted from the terminal 3 together with the service provision request. When the authentication is successful, the service is provided to the terminal 3.

  Examples of the terminal 3 include portable electronic devices such as a PC (Personal Computer) and a mobile phone.

  Next, the case where the above-described account issuing system of the present invention is a service providing system in which the service providing server 2 provides a service to the terminal 3 will be described.

  As shown in FIG. 2, the service providing system includes an authentication server 1, a service providing server 2 (hereinafter referred to as “service server 2”), and a terminal 3. The number of each of the authentication server 1, the service server 2, and the terminal 3 existing in the service providing system may be arbitrary.

  The authentication server 1 shown in FIG. 2 plays a role as the assignment device shown in FIG. Also, the service server 2 shown in FIG. 2 plays a role as a registration device shown in FIG. Further, the terminal 3 shown in FIG. 2 serves as the terminal 3 shown in FIG.

  Also, the form of the network NW that connects the authentication server 1, the service server 2, and the terminal 3 to each other is not particularly limited. Examples of the network NW include the Internet. Note that the communication method between the network NW and the terminal 3 is not particularly limited. For example, when the communication method is a wireless communication method, wireless communication via a general wireless communication interface may be performed. For example, when the communication method is a wired communication method, wired communication via Ethernet (registered trademark) may be performed.

  The authentication server 1 shown in FIG. 2 includes a set (hereinafter referred to as “account”) of an ID for identifying each user of the terminal 3 receiving the service provided by the service server 2 and a password PWD associated with the ID. And the account information ACT in which the ID is associated with the password PWD is stored.

  Here, the password PWD corresponds to “service required information” necessary for the terminal 3 to receive service provision from the service server 2.

  In this example, the authentication server 1 transmits each set of the generated ID and password PWD to the service server 2.

  The authentication server 1 also includes an encryption key EK1 that is a “first encryption key” for encrypting arbitrary data, and a “first decryption key for decrypting data encrypted by the encryption key EK1. "Is generated as a decryption key DK1.

  In this example, the encryption key EK1 is used for the service server 2 to encrypt arbitrary data. The service server 2 generates a temporary registration certificate TMP, which will be described later, using the encryption key EK1.

  The decryption key DK1 is used by the authentication server 1 to decrypt any data encrypted using the encryption key EK1. For example, the authentication server 1 uses the decryption key DK1 to decrypt the temporary registration certificate TMP generated by the service server 2 by encryption using the encryption key EK1.

  The authentication server 1 also has an encryption key EK2 which is a “second encryption key” for encrypting arbitrary data, and a “second key for decrypting data encrypted using the encryption key EK2. A decryption key DK2 which is a “decryption key” is generated.

  In this example, the encryption key EK2 is used for the authentication server 1 to encrypt arbitrary data. The authentication server 1 generates a member certificate PRF, which will be described later, using the encryption key EK2.

  The decryption key DK2 is used for the service server 2 to decrypt any data encrypted using the encryption key EK2. For example, the service server 2 decrypts the member certificate PRF generated by the authentication server 1 by encryption using the encryption key EK2 using the decryption key DK2.

  Also, the authentication server 1 transmits the generated encryption key EK1 and decryption key DK2 to the service server 2.

  Further, the authentication server 1 generates “member authentication information MAT” and transmits the member authentication information MAT to the terminal 3.

  The “member authentication information MAT” here is information used to determine whether or not the user of the terminal 3 is the member himself / herself, which is generated and assigned to the terminal 3 by the authentication server 1. This information is recognized only by the user of the terminal 3.

  The “member authentication information MAT” may be, for example, a set of a member ID MID and a member password MPW, or an electronic signature SGN. In this example, “member authentication information MAT” is a set of a member ID MID and a member password MPW.

  Further, the authentication server 1 authenticates the user of the terminal 3 based on the member authentication information MAT (member ID MID and member password MPW) transmitted from the terminal 3.

  When the user authentication using the member authentication information MAT is successful, the authentication server 1 decrypts the temporary registration certificate TMP transmitted from the terminal 3 together with the member authentication information MAT using the decryption key DK1. Turn into. By decrypting the temporary registration certificate TMP, the authentication server 1 acquires the ID assigned to the terminal 3 by the service server 2 and the temporary registration user ID TID.

  Here, the “temporary registration certificate TMP” refers to information generated by the service server 2 using the encryption key EK1 for identifying the user of the terminal 3.

  In the following, the temporary registration certificate TMP is a combination of the ID (for example, ID-1) assigned to the terminal 3 by the service server 2 and the temporary registration user ID TID assigned to the terminal 3 by the service server 2. Is described by taking as an example the case of information generated by the service server 2 by encryption using the encryption key EK1.

  Thereafter, the authentication server 1 compares the ID acquired by decrypting the temporary registration certificate TMP with the ID transmitted from the terminal 3 together with the temporary registration certificate TMP.

  As a result of the comparison, when the ID acquired by decryption matches the ID transmitted from the terminal 3, the authentication server 1 is a server for identifying the member ID MID assigned to the terminal 3 and the service server 2. Using the identification information SVR, a “member pseudonym ID KID” is generated.

  The “member pseudonym ID KID” is information for identifying each service server 2 having a different value for each service server 2.

  In this example, the member pseudonym ID KID is a hash value generated by applying a predetermined hash function to data obtained by combining the member ID MID and the server identification information SVR (for example, destination information of the service server 2). A case will be described as an example.

  The “server identification information SVR” is information that is transmitted from the terminal 3 to the authentication server 1 together with the temporary registration certificate TMP to identify the service server 2 that the terminal 3 has requested for temporary registration. In this example, the server identification information SVR is destination information of the service server 2 (for example, URL (Uniform Resource Locator)).

  Then, the authentication server 1 generates a “member certificate PRF” for certifying that the user of the terminal 3 is a regular member based on the member pseudonym ID KID and the temporary registration user ID TID.

  In this example, the “member certificate PRF” is a temporary registration user ID acquired by decrypting the temporary member registration ID KID generated by the authentication server 1 and the temporary registration certificate TMP transmitted from the terminal 3. This is data generated by the authentication server 1 by encrypting the data combined with the TID using the encryption key EK2.

  Thereafter, the authentication server 1 transmits the generated member certificate PRF, the ID transmitted from the terminal 3, and the password PWD associated with the ID to the terminal 3.

  The terminal 3 transfers the member certificate PRF, ID, and password PWD transmitted from the authentication server 1 to the service server 2.

  Then, the service server 2 authenticates the user of the terminal 3 based on the member certificate PRF, ID, and password PWD transmitted from the terminal 3. If the authentication is successful, the service server 2 decrypts the member certificate PRF using the decryption key DK2, and acquires the member pseudonym ID KID included in the member certificate PRF. Then, the service server 2 writes the acquired member pseudonym ID KID and the ID transmitted from the terminal 3 in association with each other in the storage unit 22.

  That is, the authentication server 1 plays a role of ensuring that the user of the terminal 3 is a regular member with respect to the service server 2 that provides the service to the terminal 3.

  The service server 2 writes each set of the ID and password PWD transmitted from the authentication server 1 in the registration identification information RGS stored in the storage unit 24.

  When the service server 2 writes the ID and the password PWD in association with each other, the registration identification information RGS stored in the service server 2 has a data structure as shown in FIG. Further, in this illustrative example, the registration identification information RGS also includes an assignment flag FG indicating whether or not an ID has already been assigned to the terminal 3.

  The service server 2 receives and stores the encryption key EK1 and the decryption key DK2 transmitted from the authentication server 1.

  Further, when a temporary registration request is transmitted from the terminal 3, the service server 2 assigns an ID that is not assigned to the terminal 3 among the IDs stored in the registration identification information RGS shown in FIG. Assign to the user of the terminal 3.

  When the service server 2 assigns an ID to a user, the service server 2 changes the assignment flag FG associated with the ID from “unassigned” to “assigned”.

  In the example shown in FIG. 3, when the service server 2 assigns ID-1 to the user and the assignment flag FG is changed, the registration identification information RGS has a data structure as shown in FIG. Yes.

  Further, when a temporary registration request is transmitted from the terminal 3, the service server 2 uses the predetermined “non-personal information” other than the personal information related to the user of the terminal 3 to set the “temporary registration user ID TID”. Generate.

  The “temporary registration user ID TID” here is information assigned to the user by the service server 2 as temporary information used to identify the user of the terminal 3.

  The temporary registration user ID TID is composed of a character string uniquely determined for each user. Even if the temporary registration user ID TID is known to an unspecified third party, The data is such that the user who is given the temporary registration user ID TID cannot be easily estimated from the temporary registration user ID TID.

  In this illustrative example, the service server 2 uses “terminal related information” (for example, a temporary registration request transmitted from the user terminal 3 in response to a temporary registration request) as the “non-personal information” other than personal information. The temporary registration user ID TID (for example, TID-1) is generated using the registration time.

  The service server 2 associates the generated temporary registration user ID TID with the ID assigned to the terminal 3 (ID-1 in the example of FIG. 4) and writes it in the registration identification information RGS.

  In the example shown in FIG. 4, when the service server 2 writes ID-1 and the temporary registration user ID TID-1 in association with each other, the registration identification information RGS has a data structure as shown in FIG. ing.

  Thereafter, the service server 2 uses the encryption key EK1 transmitted from the authentication server 1 as the data obtained by combining the assigned ID (for example, ID-1) and the temporary registration user ID TID (for example, TID-1). The temporary registration certificate TMP is generated by using and encrypting.

  Further, the service server 2 transmits the ID (for example, ID-1) assigned to the terminal 3 and the temporary registration certificate TMP to the terminal 3.

  In addition, when a member pseudonym registration request is transmitted from the terminal 3, the service server 2 determines the user of the terminal 3 based on the member certificate PRF, ID, and password PWD transmitted from the terminal 3. Authenticate.

  In this example, “first authentication”, which is user authentication using the member certificate PRF, and “second authentication”, which is user authentication using the ID and password PWD, are performed.

  When performing the “first authentication” using the member certificate PRF, first, the service server 2 decrypts the member certificate PRF transmitted from the terminal 3 using the decryption key DK2, and temporarily registers the user ID TID. And the member pseudonym ID KID are acquired.

  Then, it is determined whether or not the temporary registration user ID TID acquired by decrypting the member certificate PRF and the ID transmitted from the terminal 3 are stored in association with each other in the registration identification information RGS shown in FIG. To do.

  The first authentication is performed from the viewpoint of confirming whether the user of the terminal 3 is a user specified by the temporary registration user ID generated and assigned by the service server 2.

  Further, when performing the “second authentication” using the ID and the password PWD, the service server 2 associates the ID and the password PWD transmitted from the terminal 3 with the registration identification information RGS shown in FIG. To determine whether it is stored.

  The second authentication is performed from the viewpoint of confirming whether the pair of ID and password PWD has been issued by the authentication server 1.

  As a result of the first authentication, it is determined that the temporary registration user ID TID and the ID are stored in association with each other, and as a result of the second authentication, it is determined that the ID and the password PWD are stored in association with each other. In this case, the service server 2 associates the member pseudonym ID KID (for example, KID-1) acquired by decrypting the member certificate PRF as information for identifying the terminal 3 with the ID and registration identification. Write to information RGS.

  In the example shown in FIG. 5, when the service server 2 writes the member pseudonym IDs KID-1 and ID-1 in association with each other, the registration identification information RGS has a data structure as shown in FIG. Yes.

  In this example, the service server 2 registers the member pseudonym ID KID assigned by the authentication server 1 to the user when the member pseudonym ID KID is written in the registration identification information RGS in association with the ID. Is sent to the terminal 3 indicating that the registration has been completed.

  The terminal 3 transmits a temporary registration request for requesting temporary registration of a user who uses the terminal 3 to the service server 2. Note that when transmitting the temporary registration request, the terminal 3 also transmits information that can be communicated with the terminal 3 (for example, an e-mail address assigned to the terminal 3) to the service server 2.

  Further, the terminal 3 receives and stores the ID, which is transmitted from the service server 2, and is given to the terminal 3 by the service server 2 and the temporary registration certificate TMP.

  Further, the terminal 3 has a “membership certificate issuance request” for requesting the issuance of the member certificate PRF, the member authentication information MAT (in this example, the member ID MID and the member password MPW), and server identification information SVR (for example, , The destination information of the service server 2), and the temporary registration certificate TMP and ID (for example, ID-1) transmitted from the service server 2 to the authentication server 1 "temporary registration certificate transmission unit" It is.

  Further, the terminal 3 receives “member pseudonym registration for requesting registration of the member pseudonym ID KID in order to receive registration in the service server 2 of the member pseudonym ID KID assigned to the user of the terminal 3 by the authentication server 1. Request "is transmitted to the service server 2.

  The terminal 3 transfers the member certificate PRF, ID, and password PWD (service required information) transmitted from the authentication server 1 to the service providing server 2 when transmitting the member pseudonym registration request.

  Further, when the main registration completion notification is transmitted from the service server 2 in response to the member pseudonym registration request, the terminal 3 identifies that the identity of the user of the terminal 3 has been certified in the service server 2. The terminal 3 transmits a set of the ID assigned by the service server 2 and the password PWD transmitted from the authentication server 1 to the service server 2 and requests the service server 2 to authenticate the user.

  Thereafter, when the authentication by the service server 2 is successful, the terminal 3 receives the service provided by the service server 2.

  Next, the configuration of the authentication server 1 will be described in detail.

  As shown in FIG. 7, in addition to the communication unit 11, the storage unit 14, and the information allocation unit 18, the authentication server 1 includes an account generation unit 12, a key generation unit 13, a member authentication unit 15, and a member pseudonym ID. 1 is different from the assignment device 1 shown in FIG. 1 in that it includes a generation unit 16 and a member certificate generation unit 17.

  The communication unit 11 transmits / receives arbitrary data to / from the service server 2 or the terminal 3.

  For example, the communication unit 11 transmits the ID and password PWD output from the account generation unit 12 to the service server 2.

  In addition, the communication unit 11 transmits the encryption key EK1 and the decryption key DK2 output from the key generation unit 13 to the service server 2.

  In addition, the communication unit 11 transmits the member authentication information MAT output from the member authentication unit 15 to the terminal 3.

  In addition, the communication unit 11 transmits an information allocation request, a member certificate issuance request, member authentication information MAT, destination information (server identification information SVR) of the service server 2, ID, and temporary registration transmitted from the terminal 3. Receive the certificate TMP.

  In addition, the communication unit 11 transmits the membership certificate PRF output from the membership certificate generation unit 17 and the password PWD and ID output from the information allocation unit 18 to the terminal 3.

  The account generation unit 12 generates a set (account) of an ID for identifying each user of the terminal 3 that receives service provided by the service server 2 and a password PWD associated with the ID.

  Then, the account generation unit 12 associates the generated ID with the password PWD and writes them in the account information ACT stored in the storage unit 14.

  Further, the account generation unit 12 outputs the generated ID and password PWD to the communication unit 11.

  The key generation unit 13 includes an encryption key EK1 (first encryption key) for encrypting arbitrary data and a decryption key DK1 (first decryption key) for decrypting data encrypted by the encryption key EK1. ) And generate.

  In addition, the key generation unit 13 encrypts arbitrary data with an encryption key EK2 (second encryption key) and a decryption key DK2 (for decrypting data encrypted using the encryption key EK2). Second decryption key).

  Then, the key generation unit 13 writes the generated set of the encryption key EK1 and the decryption key DK1 and the set of the encryption key EK2 and the decryption key DK2 into the storage unit 14.

  Further, the key generation unit 13 outputs the encryption key EK1 and the decryption key DK2 to the communication unit 11.

  The storage unit 14 stores arbitrary data.

  For example, the storage unit 14 stores account information ACT that is information for associating the ID written by the account generation unit 12 with the password PWD.

  Note that the password PWD already transmitted by the communication unit 11 to the terminal 3 and the ID associated with the password PWD may be deleted from the set of ID and password PWD stored in the storage unit 14.

  In addition, the storage unit 14 stores a pair of the encryption key EK1 and the decryption key DK1 written by the key generation unit 13, and a pair of the encryption key EK2 and the decryption key DK2.

  The storage unit 14 stores member authentication information MAT written by the member authentication unit 15.

  The storage unit 14 stores member authentication information MAT for authenticating the user of the terminal 3.

  In addition, the memory | storage part 14 may further memorize | store the member information which consists of a user's personal information.

  The member authentication unit 15 generates member authentication information MAT and outputs the member authentication information MAT to the communication unit 11. Here, the member authentication information MAT may be, for example, a set of a member ID MID and a member password MPW, which is a general password, or an electronic signature SGN.

  Further, the member authentication unit 15 writes the generated member authentication information MAT into the storage unit 14. The member authentication information MAT is assigned in advance to the terminal 3 when a request for assigning the member authentication information MAT is transmitted from the terminal 3.

  Further, when the information allocation request and the member certification issuance request are transmitted from the terminal 3, the member authentication unit 15 transmits the member authentication information MAT (member ID MID and member password MPW) transmitted from the terminal 3, The terminal 3 is authenticated based on the comparison with the member authentication information MAT stored in the storage unit 14.

  The member authentication unit 15 determines that the authentication is successful when the member authentication information MAT transmitted from the terminal 3 matches the member authentication information MAT stored in the storage unit 14.

  When the authentication by the member authentication unit 15 is successful, the member pseudonym ID generation unit 16 generates a member pseudonym ID KID based on the member ID MID and the server identification information SVR (in this example, destination information of the service server 2).

  In this example, when the authentication by the member authentication unit 15 is successful, the member pseudonym ID generation unit 16 performs authentication using the ID transmitted from the terminal 3 and the temporary registration certificate TMP. If the authentication is successful, the member pseudonym ID generation unit 16 generates a member pseudonym ID KID.

  When performing authentication using the ID transmitted from the terminal 3 and the temporary registration certificate TMP, the member pseudonym ID generation unit 16 first uses the temporary registration certificate TMP transmitted from the terminal 3 together with the member authentication information MAT. Decrypt using the decryption key DK1. By the decryption, the member pseudonym ID generation unit 16 acquires the ID assigned by the service server 2 to the user of the terminal 3 and the temporary registration user ID TID.

  Thereafter, the member pseudonym ID generation unit 16 compares the ID acquired by decrypting the temporary registration certificate TMP with the ID transmitted from the terminal 3 together with the temporary registration certificate TMP.

  As a result of the comparison, when the ID acquired by the decryption matches the ID transmitted from the terminal 3, the member pseudonym ID generation unit 16 uses the member ID MID and the server identification information SVR to Generate a KID.

  In this example, the member pseudonym ID generation unit 16 uses a hash value generated by applying a predetermined hash function to data obtained by combining the member ID MID and the destination information of the service server 2 as the pseudonym of the user of the terminal 3. The member pseudonym ID KID that plays the role of is determined.

  Thereafter, the member pseudonym ID generation unit 16 outputs the determined member pseudonym ID KID and the temporary registration user ID TID acquired by decrypting the temporary registration certificate TMP to the member certificate generation unit 17.

  The member certificate generation unit 17 generates a member certificate PRF based on the member pseudonym ID KID and the temporary registration user ID TID output from the member pseudonym ID generation unit 16, and communicates the member certificate PRF. To the unit 11.

  In this example, the member certificate generation unit 17 generates a member certificate PRF by encrypting data obtained by combining the member pseudonym ID KID and the temporary registration user ID TID using the encryption key EK2. .

  When the authentication by the member authentication unit 15 is successful, the information allocation unit 18 reads the password PWD associated with the ID (for example, ID-1) transmitted from the terminal 3 from the account information ACT in the storage unit 14. put out. The password PWD is “service required information”.

  Then, the information allocation unit 18 outputs the read password PWD and the ID corresponding to the password PWD to the communication unit 11.

  Next, the configuration of the service server 2 shown in FIG. 2 will be described in detail.

  8, in addition to the communication unit 21, the storage unit 22, the ID allocation unit 23, and the service providing unit 28 illustrated in FIG. A document generation unit 25, an authentication unit 26, and a member pseudonym registration unit 27;

  The communication unit 21 transmits / receives arbitrary data to / from the authentication server 1 or the terminal 3.

  For example, the communication unit 21 receives the ID and password PWD transmitted from the authentication server 1.

  The communication unit 21 receives the encryption key EK1 and the decryption key DK2 transmitted from the authentication server 1.

  Further, the communication unit 21 receives the ID assignment request and the temporary registration request transmitted from the terminal 3.

  Further, the communication unit 21 transmits the ID output from the ID assignment unit 23 to the terminal 3.

  In addition, the communication unit 21 transmits the temporary registration certificate TMP output from the temporary registration certificate generation unit 25 to the terminal 3.

  Further, the communication unit 21 receives the member pseudonym registration request transmitted from the terminal 3.

  Further, the communication unit 21 receives the member certificate PRF and the password PWD transmitted from the terminal 3.

  In addition, the communication unit 21 transmits a main registration completion notification to the terminal 3.

  The storage unit 22 stores arbitrary data.

  For example, the storage unit 22 stores registration identification information RGS.

  As shown in FIGS. 3 to 6, the registration identification information RGS includes an ID and password PWD set to be issued to the terminal 3, an assignment flag FG indicating whether or not an ID is assigned, a member pseudonym ID KID, This is information for associating temporary registration user ID TID.

  The ID is identification information to be assigned to the terminal 3. In the example shown in FIGS. 3 to 6, ID-1 to ID-3 are associated with passwords PWD-1 to PWD-3, respectively.

  The password PWD is a password associated with the ID and is “service required information”. The password PWD is used for authentication of a user of the terminal 3 that is performed prior to service provision to the terminal 3.

  The storage unit 22 stores the encryption key EK1 and the decryption key DK2 transmitted from the authentication server 1.

  The ID assignment unit 23 writes each set of the ID and the password PWD transmitted from the authentication server 1 to the registration identification information RGS stored in the storage unit 24. When the ID assigning unit 23 writes the ID and the password PWD in association with each other, the registration identification information RGS has the data structure shown in FIG.

  In addition, when a temporary registration request and an ID allocation request of a user who uses the terminal 3 are transmitted from the terminal 3, the ID allocation unit 23 performs temporary registration of the user.

  The ID assigning unit 23 assigns an ID that is not assigned to the terminal 3 among the IDs stored in the registration identification information RGS shown in FIG. 3 to the user of the terminal 3. By this allocation, provisional registration of the user of the terminal 3 is performed.

  When assigning an ID to a user, the ID assigning unit 23 changes the assignment flag FG associated with the ID from “unassigned” to “assigned”. When the ID assignment unit 23 assigns ID-1 and changes the assignment flag FG, the registration identification information RGS has the data structure shown in FIG.

  Further, the ID assigning unit 23 outputs the ID assigned to the terminal 3 (for example, ID-1) to the communication unit 21.

  In addition, when the user of the terminal 3 is temporarily registered, the ID assigning unit 23 outputs the time (terminal related information) at which the terminal 3 is temporarily registered to the temporary registration ID generating unit 24.

  When a temporary registration request is transmitted from the terminal 3, the temporary registration ID generation unit 24 is based on “non-personal information” other than the personal information of the user himself / herself of the terminal 3 to which the ID assignment unit 23 has given an ID. A temporary registration user ID TID is generated.

  In this example, the temporary registration ID generation unit 24 uses “terminal-related information” regarding the terminal 3 as “non-personal information” (for example, by assigning an ID to the terminal 3, the ID allocation unit 23 performs temporary registration of the user. The temporary registration user ID TID (for example, TID-1) is generated.

  Further, the temporary registration ID generation unit 24 writes the generated temporary registration user ID TID and the ID assigned by the ID assignment unit 23 in association with each other in the registration identification information RGS. When the temporary registration ID generation unit 24 writes ID-1 and temporary registration user ID TID-1 in association with each other, the registration identification information RGS has the data structure shown in FIG.

  Further, the temporary registration ID generation unit 24 outputs the temporary registration user ID TID to the temporary registration certificate generation unit 25.

  The temporary registration certificate generation unit 25 encrypts the data obtained by combining the ID allocated by the ID allocation unit 23 to the terminal 3 and the temporary registration user ID TID output from the temporary registration ID generation unit 24 in the storage unit 22. The temporary registration certificate TMP is generated by encrypting with the key EK1.

  Then, the temporary registration certificate generation unit 25 outputs the temporary registration certificate TMP generated by the encryption to the communication unit 21.

  When a member pseudonym registration request is transmitted from the terminal 3, the authentication unit 26 determines whether the terminal 3 has the membership certificate PRF, the ID, and the password PWD transmitted from the terminal 3 together with the member pseudonym registration request. Authenticate users.

  In this example, the authentication unit 26 performs “first authentication” that is user authentication using the member certificate PRF and “second authentication” that is user authentication using the ID and password PWD. I do.

  When performing the “first authentication” using the member certificate PRF, the authentication unit 26 first decrypts the member certificate PRF transmitted from the terminal 3 using the decryption key DK2 in the storage unit 22, The temporary registration user ID TID and the member pseudonym ID KID are acquired.

  Then, the authentication unit 26 stores the temporary registration user ID TID acquired by decrypting the member certificate PRF and the ID transmitted from the terminal 3 in association with each other in the registration identification information RGS shown in FIG. To determine if

  When performing “second authentication” using the ID and the password PWD, the authentication unit 26 associates the ID and the password PWD transmitted from the terminal 3 with the registration identification information RGS shown in FIG. To determine whether it is stored.

  As a result of the first authentication, the authentication unit 26 determines that the temporary registration user ID TID and the ID are stored in association with each other, and as a result of the second authentication, the ID and the password PWD are stored in association with each other. If the authentication unit 26 determines that the authentication is successful, the member pseudonym registration unit 27 has transmitted from the terminal 3 the member pseudonym ID KID obtained by decrypting the member certificate PRF as information for identifying the terminal 3. It is written in the registration identification information RGS in association with the ID. In this case, the registration identification information RGS has the data structure shown in FIG.

  When the member pseudonym registration unit 27 writes the member pseudonym ID KID in the registration identification information RGS in association with the ID, the main registration of the member pseudonym ID KID assigned to the user by the authentication server 1 is completed. “Registration completion notification” indicating this may be transmitted to the terminal 3 via the communication unit 21.

  When the main registration completion notification is transmitted from the service server 2, the terminal 3 identifies that the identity of the user of the terminal 3 has been certified in the service server 2. Then, a set of the ID assigned by the service server 2 and the password PWD transmitted from the authentication server 1 is transmitted to the service server 2 to request the service server 2 for user authentication.

  After the member pseudonym registration unit 27 writes the member pseudonym ID KID in association with the ID in the registration identification information RGS, the service provision unit 28 transmits a “service provision request” from the terminal 3 together with the ID and password PWD. In this case, the user of the terminal 3 is authenticated using the ID and the password PWD.

  For example, the service providing unit 28 determines whether the ID and password PWD transmitted from the terminal 3 are stored in the registration identification information RGS in the storage unit 22 in association with the member pseudonym ID KID. As a result of the determination, if the ID and password PWD and the member pseudonym ID KID are stored in association with the registration identification information RGS, it is determined that the authentication is successful.

  When the user authentication is successful, the service is provided to the terminal 3 used by the user.

  Next, the configuration of the terminal 3 will be described in detail.

  As shown in FIG. 9, in addition to the communication unit 31, the ID allocation request unit 32, the information allocation request unit 33, and the service request unit 35 shown in FIG. Part 36.

  The communication unit 31 transmits / receives arbitrary data to / from the authentication server 1 or the service server 2.

  For example, the communication unit 31 receives member authentication information MAT transmitted from the authentication server 1.

  In addition, the communication unit 31 transmits a temporary registration request and an ID allocation request for requesting temporary registration of the user of the terminal 3 output from the ID allocation request unit 32 to the service server 2.

  When transmitting the temporary registration request, the communication unit 31 also transmits a terminal ID for uniquely identifying the terminal 3 (for example, an e-mail address assigned to the terminal 3) to the service server 2.

  The communication unit 31 receives the temporary registration certificate TMP and ID transmitted from the service server 2.

  In addition, the communication unit 31 transmits a membership certificate issuance request and an information allocation request for requesting the issuance of the membership certificate PRF output from the information allocation requesting unit 33 to the authentication server 1.

  When transmitting the membership certificate issuance request and the information allocation request, the communication unit 31 has transmitted the member authentication information MAT, the server identification information SVR (for example, the destination information of the service server 2), and the service server 2. The temporary registration certificate TMP and ID (for example, ID-1) are transmitted to the authentication server 1.

  Further, the communication unit 31 receives the member certificate PRF, ID, and password PWD transmitted from the authentication server 1.

  Further, the communication unit 31 transmits the member pseudonym registration request output from the member pseudonym registration request unit 34 to the service server 2.

  When transmitting the member pseudonym registration request, the communication unit 31 transfers the member certificate PRF, ID, and password PWD transmitted from the authentication server 1 to the service providing server 2.

  In this example, the communication unit 31 receives the main registration completion notification transmitted from the service server 2.

  The ID allocation request unit 32 communicates a temporary registration request for requesting the account allocation when an input unit (not shown) receives an input requesting ID allocation from the user. To the unit 31.

  The “temporary registration request” here is transmitted together with the “ID allocation request” for requesting ID allocation.

  When the ID allocation request unit 32 outputs the information allocation request and the temporary registration request, the ID allocation request unit 32 also outputs information communicable with the terminal 3 (for example, an e-mail address given to the terminal 3) to the communication unit 31. To do.

  The information allocation request unit 33 authenticates the issuance of the member certificate PRF for certifying that the member is a member when the temporary registration certificate TMP is transmitted from the service server 2 in response to the ID allocation request and the temporary registration request. A membership certificate issuance request for requesting the server 1 is output to the communication unit 31.

  When outputting the member certificate issuance request, the information allocation requesting unit 33 sends the member authentication information MAT, the server identification information SVR (for example, the destination information of the service server 2), and the temporary server transmitted from the service server 2. The registration certificate TMP and ID (for example, ID-1) are output to the communication unit 31.

  When the member certificate PRF is transmitted from the authentication server 1 in response to the member certificate issuance request, the member pseudonym registration request unit 34 is a service of the member pseudonym ID KID assigned to the user of the terminal 3 by the authentication server 1. In order to receive registration in the server 2, a member pseudonym registration request for requesting registration of the member pseudonym ID KID is output to the communication unit 31.

  When the member pseudonym registration request is output, the member pseudonym registration request unit 34 outputs the member certificate PRF, ID, and password PWD transmitted from the authentication server 1 to the communication unit 31.

  When the registration completion notification is transmitted from the service server 2, the service request unit 35 identifies that the identity of the user of the terminal 3 has been certified in the service server 2.

  After the identification, when receiving an input from the user to receive service provided by the service server 2, the service request unit 35 receives the ID assigned by the service server 2 and the password PWD (service assigned by the authentication server 1). Together with necessary information), a service provision request is transmitted to the service server 2. The terminal 3 receives the service provided by the service server 2 when the authentication using the ID and password PWD is successful in the service server 2.

  The storage unit 36 stores arbitrary data.

  For example, the storage unit 36 stores member authentication information MAT transmitted from the authentication server 1.

  The storage unit 36 stores the ID transmitted from the service server 2 and the temporary registration certificate TMP.

  The storage unit 36 stores the password PWD and the member certificate PRF transmitted from the authentication server 1.

  Next, in the authentication system having the above configuration, the operation in which the service server 2 registers the member pseudonym ID KID assigned by the authentication server 1 to the user of the terminal 3 will be described with reference to the sequence diagram shown in FIG. To do.

  As a premise for explanation, the authentication server 1 generates an association between the ID and the password PWD, and stores account information ACT in which the ID and the password PWD are associated with each other.

  In addition, the authentication server 1 transmits the association between the generated ID and the password PWD to the service server 2. The service server 2 stores the registration identification information RGS shown in FIG. 3 that associates the ID transmitted from the authentication server 1 with the password PWD in the storage unit 22.

  The authentication server 1 also generates and stores an encryption key EK1, a decryption key DK1, an encryption key EK2, and a decryption key DK2. Further, the authentication server 1 transmits the generated encryption key EK1 and decryption key DK2 to the service server 2. The service server 2 receives and stores the encryption key EK1 and the decryption key DK2 transmitted from the authentication server 1.

  Further, the authentication server 1 generates and stores the member authentication information MAT and transmits the member authentication information MAT to the terminal 3. The terminal 3 receives and stores the member authentication information MAT transmitted from the authentication server 1.

  As shown in FIG. 10, first, when the terminal 3 receives an input requesting ID allocation from the user, the terminal 3 makes a temporary registration request together with an ID allocation request for requesting the ID allocation. Is transmitted to the service server 2 (step S1).

  In step S1, when the terminal 3 transmits the ID assignment request and the temporary registration request, the terminal ID (for example, an e-mail address assigned to the terminal 3) that can identify the terminal 3 is also sent to the service server 2. Send.

  Then, when the temporary registration request is transmitted together with the ID allocation request from the terminal 3, the service server 2 is allocated to the terminal 3 from the IDs stored in the registration identification information RGS shown in FIG. No ID is assigned to the user of the terminal 3 (step S2).

  When the service server 2 assigns an ID to a user, the service server 2 changes the assignment flag FG associated with the ID from “unassigned” to “assigned”.

  Subsequently, the service server 2 generates “temporary registration user ID TID” using predetermined information other than personal information regarding the user of the terminal 3 (step S3).

  In this example, the service server 2 uses, as “predetermined information other than personal information”, terminal-related information related to the terminal 3 (for example, the time when the user of the terminal 3 was temporarily registered), and the temporary registration user ID A TID (eg, TID-1) is generated. Then, the service server 2 associates the generated temporary registration user ID TID with the ID assigned to the terminal 3 (for example, ID-1) and writes it in the registration identification information RGS.

  Thereafter, the service server 2 generates a temporary registration certificate TMP by encrypting data obtained by combining the assigned ID and the temporary registration user ID TID using the encryption key EK1 (step S4). Further, the service server 2 transmits the ID assigned to the terminal 3 and the temporary registration certificate TMP to the terminal 3.

  Then, the terminal 3 sends the member authentication information MAT and the server identification information SVR () together with the “information allocation request” for requesting the allocation of service necessary information and the member certificate issuance request for requesting the issuance of the member certificate PRF. For example, the destination information of the service server 2) and the temporary registration certificate TMP and ID transmitted from the service server 2 are transmitted to the authentication server 1 (step S5).

  Then, the authentication server 1 authenticates the user of the terminal 3 based on the member authentication information MAT transmitted from the terminal 3 (step S6).

  When the user authentication using the member authentication information MAT is successful, the authentication server 1 decrypts the temporary registration certificate TMP transmitted from the terminal 3 together with the member authentication information MAT using the decryption key DK1. Turn into. By decrypting the temporary registration certificate TMP, the authentication server 1 obtains only one ID that the service server 2 gives to the terminal 3 and the temporary registration user ID TID (step S7).

  Thereafter, the authentication server 1 compares the ID acquired by decrypting the temporary registration certificate TMP with the ID transmitted from the terminal 3 together with the temporary registration certificate TMP.

  As a result of the comparison, when the ID acquired by decryption matches the ID transmitted from the terminal 3, the authentication server 1 generates the member pseudonym ID KID using the member ID MID and the server identification information SVR. (Step S8). In this example, the member pseudonym ID KID is a hash value generated by applying a predetermined hash function to data obtained by combining the member ID MID and the server identification information SVR (for example, destination information of the service server 2). It is.

  Thereafter, the authentication server 1 encrypts the data obtained by combining the generated member pseudonym ID KID and temporary registration user ID TID using the encryption key EK2, thereby confirming that the user of the terminal 3 is a regular member. A member certificate PRF for proof is generated (step S9).

  If the user authentication using the member authentication information MAT in step S6 is successful, the authentication server 1 reads the password PWD stored in association with the ID transmitted from the terminal 3.

  Then, the authentication server 1 transmits the generated member certificate PRF, the ID transmitted from the terminal 3, and the password PWD associated with the ID to the terminal 3.

  Then, the terminal 3 transmits a member pseudonym registration request to the service server 2 in order to receive registration in the service server 2 of the member pseudonym ID KID assigned to the user of the terminal 3 by the authentication server 1 (step S10). . In step S 10, the terminal 3 transfers the member certificate PRF, ID, and password PWD transmitted from the authentication server 1 to the service server 2 when transmitting the member pseudonym registration request.

  Then, the service server 2 authenticates the user of the terminal 3 based on the member certificate PRF, ID, and password PWD transmitted from the terminal 3 (step S11).

  In this example, the service server 2 uses “first authentication”, which is user authentication using the member certificate PRF, and “second authentication”, which is user authentication using the ID and password PWD. To do.

  At the time of the first authentication in step S11, first, the service server 2 decrypts the member certificate PRF transmitted from the terminal 3 using the decryption key DK2, and obtains the temporary registration user ID TID and the member pseudonym ID KID. get. Then, it is determined whether or not the acquired temporary registration user ID TID and the ID transmitted from the terminal 3 are stored in association with each other in the registration identification information RGS.

  In the second authentication in step S11, the service server 2 determines whether the ID transmitted from the terminal 3 and the password PWD are stored in association with each other in the registration identification information RGS shown in FIG. To do.

  As a result of the first authentication, it is determined that the temporary registration user ID TID and the ID are stored in association with each other, and as a result of the second authentication, it is determined that the ID and the password PWD are stored in association with each other. In this case, the service server 2 associates the member pseudonym ID KID (for example, KID-1) acquired by decrypting the member certificate PRF as information for identifying the terminal 3 with the ID and registration identification. Information is written into the information RGS (step S12). In this example, the service server 2 transmits a main registration completion notification to the terminal 3 when the member pseudonym ID KID is associated with the ID and written in the registration identification information RGS.

  When the main registration completion notification is transmitted from the service server 2, the terminal 3 identifies that the identity of the user of the terminal 3 has been certified in the service server 2.

  Thereafter, the terminal 3 transmits a service provision request to the service server 2 together with the ID assigned by the service server 2 and the password PWD assigned by the authentication server 1.

  When the authentication using the ID and password PWD succeeds in the service server 2, the service server 2 provides a service to the terminal 3. The case where the authentication is successful is, for example, a case where the ID and password PWD and the member pseudonym ID KID are stored in association with the registration identification information RGS.

  Thus, in the authentication system of the first embodiment, a series of operations when the service server 2 registers the member pseudonym ID KID assigned by the authentication server 1 to the user of the terminal 3 is completed.

  As described above, according to the first embodiment of the present invention, each of the authentication server 1 and the service server 2 stores an account that is a set of an ID and a password PWD in common. Further, every time the service server 2 assigns an ID to the user of the terminal 3, the authentication server 1 generates a member certificate PRF corresponding to the ID. In the service server 2, when the authentication using the member certificate PRF or the like succeeds, the member pseudonym ID KID assigned to the user of the terminal 3 by the authentication server 1 included in the member certificate PRF. Is stored in association with the ID. When the member pseudonym ID KID and the ID are stored in association with each other in the service server 2, the user of the terminal 3 thereafter provides the service to the terminal 3 by the service server 2 using the ID and the password PWD. It can be enjoyed.

  Thus, the user can receive registration of the member pseudonym ID KID indicating that the user himself / herself is a member at the service server 2 without transmitting personal information about the user himself / herself to the service server 2. .

  In addition, it becomes unnecessary for the user of the terminal 3 to own a public key or the like that is commonly used in the plurality of service servers 2. Therefore, the protection of privacy related to the user can be improved as compared with a technique for authenticating the user using a general electronic signature.

  Further, according to the first embodiment, the authentication server 1 generates the member certificate PRF that guarantees the identity of the user. Then, the service server 2 determines whether to write the member pseudonym ID KID given to the user included in the member certificate PRF generated by the authentication server 1 in the storage unit 22.

  As a result, the service server 2 can determine whether or not an account can be assigned, and as a result, the account can be issued flexibly.

  Further, according to the first embodiment, the authentication server 1 stores the user and the service server 2 in association with each other in order to identify which user is using which service server 2 service. Is no longer necessary.

  Therefore, it is possible to avoid leakage of information regarding the user of the terminal 3 via the authentication server 1 that does not provide the service.

  Further, according to the first embodiment, the authentication server 1 assigns a different member pseudonym ID KID and member certificate PRF to each service server 2 to the same user specified by the ID. Each service server 2 authenticates the user of the terminal 3 using a member certificate PRF that is different for each service server 2.

Therefore, even when there are a plurality of service servers 2 in the authentication system, it is possible to avoid name identification from being performed on the user of the terminal 3, and the privacy of the user is infringed, or the user It is possible to make it difficult for personal information to leak.
(Embodiment 2)
Next, the case where the account issuing system of the present invention is a charging system will be described.

  When a license key for receiving service provision by a service providing server is assigned to a terminal, a device owned by a third party organization charges as a method for charging the user of the terminal with the license key fee. There is a method of charging while maintaining the anonymity of the user by acting. However, in such a billing method, there is a problem that the third party organization apparatus must store the personal information of the user and the server identification information for identifying the billing server in association with each other. is there.

  In order to avoid storing the personal information and the billing server in association with the device of the third party organization, a license key is issued from the store terminal such as an IC card reader / writer to the user. You can do it. In this case, the user of the terminal can make a payment for purchasing the license key without using the real name to the billing server.

  Hereinafter, a charging system according to the second embodiment that performs such an operation will be described.

  As shown in FIG. 11, this billing system has a store terminal 4, a billing server 5, and a terminal 6 used by a user.

  The accounting server 5 serves as the “registration device” shown in FIG. 1 having a function of providing a service to the terminal 6.

  Further, the store terminal 4 plays a role as the “allocation device” shown in FIG.

  In addition, the store terminal 4 and the billing server 5 include an ID, a license key LCK that can be purchased by the user of the terminal 6 via the store terminal 4, and a price CST to be paid to acquire the license key LCK. The correspondence with is stored.

  The “license key LCK” here is information for identifying a user who is qualified to receive the service provided by the billing server 5 (service providing server). Information ".

  In this example, the accounting server 5 stores ID information IDI as shown in FIG. 12 as an association between an ID, a license key LCK, and a price CST.

  Further, the store terminal 4 stores “key issue information PB” as shown in FIG. 13 in which a payment completion flag CM is further associated in addition to the association between the ID, the license key LCK, and the price CST.

  Here, the “settlement completion flag CM” is a flag indicating whether or not the settlement accompanying the purchase of the license key LCK is completed.

  Furthermore, in this example, before assigning the ID to the terminal 6, the accounting server 5 stores the key registration determination information KRG shown in FIG. 14A including the account used for user authentication assigned in advance to the user. is doing.

  The account here is information used to authenticate the user of the terminal 6 when receiving the service provided from the accounting server 5. Examples of the account include a general user ID and password set.

  When the ID allocation request for requesting ID allocation is transmitted from the terminal 6, the accounting server 5 transmits the account transmitted with the ID allocation request and the key registration determination information shown in FIG. Compare with account stored in KRG.

  As a result of the comparison, when the account transmitted from the terminal 6 matches the account stored in the registration determination information KRG, the accounting server 5 associates the account transmitted from the terminal 6 with the ID. It is determined whether or not the key registration determination information KRG is stored.

  If it is determined that the account transmitted from the terminal 6 is not stored in the key registration determination information KRG in association with the ID, the charging server 5 selects the ID stored in the ID information IDI shown in FIG. Is assigned to the user of the terminal 6 and transmitted to the terminal 6.

  In this case, as shown in FIG. 14B, the billing server 5 stores the ID assigned to the terminal 6 in the key registration determination information KRG in association with the account transmitted from the terminal 6.

  Further, when the accounting server 5 transmits an “information registration request” for requesting registration of a license key LCK (service required information), an account, an ID, and a license key LCK from the terminal 6, the account is stored in the key. It is determined whether or not it is stored in the registration determination information KRG.

  When the account transmitted from the terminal 6 is stored in the key registration determination information KRG, the billing server 5 uses the ID information IDI shown in FIG. 12 for the ID transmitted from the terminal 6 and the license key LCK. It is determined whether it is stored in association.

  As a result of the determination, if it is determined that the ID transmitted from the terminal 6 and the license key LCK are stored in association with the ID information IDI, the billing server 5 is as shown in FIG. The association between the account and ID transmitted from the terminal 6 and the license key LCK transmitted from the terminal 6 are stored in the key registration determination information KRG in association with each other.

  Thereafter, when the service provision request and the account for requesting the provision of service to the terminal 6 are transmitted from the terminal 6, the accounting server 5 associates the account with the license key LCK (service required information). It is determined whether or not the key registration determination information KRG is stored. As a result of the determination, when it is determined that they are stored in association with each other, the billing server 5 provides a service to the user of the terminal.

  In addition, when the terminal 6 receives an input from the user to make a payment accompanying the acquisition of the license key, the terminal 6 sends the “settlement request” (information allocation request) for requesting the execution of the payment from the charging server 5. The transmitted ID is transmitted to the store terminal 4. Further, in this illustrative example, the terminal 6 transmits money amount information MNY indicating the same amount as the price CST to the store terminal 4 by the electronic money function.

  Then, the store terminal 4 compares the amount indicated by the amount information MNY transmitted from the terminal 6 with the price CST stored in association with the ID. As a result of the comparison, if the amount is equal to or higher than the price CST, the store terminal 4 assigns a license key LCK (service required information) stored in association with the ID to the user and transmits it to the terminal 6.

  Below, the structure of the shop terminal 4 is demonstrated in detail.

  As illustrated in FIG. 15, the store terminal 4 includes an information writing unit 41, a price transmission unit 42, and a settlement unit 43 in addition to the communication unit 11, the storage unit 14, and the information allocation unit 18 illustrated in FIG. 1. And the depositing unit 44, which is different from the configuration of the allocation device 1 shown in FIG. 1.

  When the correspondence between the ID, the license key LCK, and the price CST is transmitted from the billing server 5, the information writing unit 41 further sets a settlement completion flag CM to the correspondence between the ID, the license key LCK, and the price CST. Correspondingly, the key issuance information PB shown in FIG. 13 is stored.

  When a price transmission request for requesting transmission of a price CST necessary for acquiring the license key LCK is transmitted from the terminal 6, the price transmission unit 42 associates it with the ID transmitted together with the price transmission request. The stored price CST is read from the storage unit 14 and transmitted to the terminal 6.

  When the payment request for executing the payment accompanying the acquisition of the license key LCK, the ID, the money amount information MNY, and the ID are transmitted from the terminal 6, the payment unit 43 stores them in association with the ID. It is determined whether the settlement completion flag indicates “completed” or “incomplete”.

  If the settlement completion flag indicates “incomplete” as a result of the determination, the settlement unit 43 reads the price CST stored in association with the ID from the storage unit 14 and transmits it from the terminal 6. Compared with the amount indicated by the amount information MNY.

  As a result of the comparison, when the amount indicated by the amount information MNY is equal to or greater than the read price CST, the settlement unit 43 changes the settlement completion flag CM associated with the price CST from “incomplete” to “completed”. At the same time, the depositing unit 44 is notified of the change, and the depositing information MNY is output to the depositing unit 44.

  When the amount indicated by the amount information MNY is equal to or greater than the read price CST, the settlement unit 43 notifies the information allocation unit 18 that the amount indicated by the amount information MNY is equal to or greater than the price CST. Then, the information allocating unit 18 allocates the license key LCK associated with the ID transmitted from the terminal 6 together with the payment request to the user of the terminal 6 and transmits the license key LCK to the terminal 6.

  When the payment unit 43 is notified that the payment completion flag CM has been changed from “incomplete” to “completed”, the deposit unit 44 uses the communication unit 11 for the amount information MNY output from the payment unit 43. To the billing server 5.

  Next, the configuration of the accounting server 5 will be described in detail.

  As shown in FIG. 16, the billing server 5 includes an account issuing unit 51, an authentication unit 52, in addition to the communication unit 21, the storage unit 22, the ID allocation unit 23, and the service providing unit 28 shown in FIG. 1 is different from the configuration of the registration apparatus shown in FIG. 1 in that it includes an ID information generation unit 53, a key registration unit 54, and a deposit receipt unit 55.

  When an account issuance request for requesting issuance of an account is transmitted from the terminal 6, the account issuing unit 51 generates an account, assigns the generated account to the user of the terminal 6, and transmits the account via the communication unit 21. Transmit to terminal 6. Further, when the account issuing unit 51 assigns the account AC to the user, as shown in FIG. 14A, the account issuing unit 51 determines whether to register the account AC (in the example of FIG. 14A, AC-1). Write to information KRG.

  The authentication unit 52 authenticates the user of the terminal 6 using the account AC transmitted from the terminal 6. For example, when the account AC transmitted from the terminal 6 is stored in the key registration determination information KRG, the authentication unit 52 determines that the user has been successfully authenticated.

  In this example, the authentication unit 52 includes a case where an ID allocation request and an account are transmitted from the terminal 6, a case where an account is transmitted from the terminal 6 together with an information registration request, a service provision request and an account. Are transmitted from the terminal 6, the user is authenticated using each account.

  Further, when the authentication unit 52 determines that the user authentication is successful when the ID allocation request and the account are transmitted from the terminal 6, the authentication unit 52 notifies the ID allocation unit 23 of the success of the authentication. Then, the ID assigning unit 23 assigns an ID to the user of the terminal 6 and transmits it to the terminal 6, and assigns the account AC transmitted from the terminal 6 as shown in FIG. 14 (b). Are stored in the key registration determination information KRG in association with each other.

  When the authentication unit 52 determines that the user has been successfully authenticated when the account is transmitted from the terminal 6 together with the key registration request (information registration request), the authentication unit 52 notifies the key registration unit 54 of the success of the authentication. Notice.

  Further, when the authentication unit 52 determines that the user authentication is successful when the service provision request and the account are transmitted from the terminal 6, the authentication unit 52 notifies the service provision unit 28 of the success of the authentication. Then, the service providing unit 28 provides a service to the user of the terminal 6.

  The ID information generation unit 53 generates a correspondence between the ID, the license key LCK, and the price CST and writes it as the ID information IDI in the storage unit 22, and also creates a correspondence between the ID, the license key LCK, and the price CST. 21 to the store terminal 4.

  When the authentication unit 52 is notified that the user has been successfully authenticated, the key registration unit 54 determines that the ID transmitted from the terminal 6 together with the key registration request and the license key LCK is the ID information IDI shown in FIG. It is determined whether or not it is stored in association with.

  As a result of the determination, if it is determined that the ID and the license key LCK are stored in association with the ID information IDI, the key registration unit 54 is transmitted from the terminal 6 as shown in FIG. The stored account, ID, and license key LCK are associated with each other and stored in the key registration determination information KRG. Subsequently, the key registration unit 54 transmits a registration completion notification indicating that the account, the ID, and the license key LCK transmitted from the terminal 6 are stored in association with each other to the terminal 6.

  The deposit receiving unit 55 is, for example, a database for storing the amount, and stores amount information MNY transmitted from the store terminal 4.

  Next, the configuration of the terminal 6 will be described in detail.

  As illustrated in FIG. 17, the terminal 6 includes an account issuance request unit 61, a storage unit 62, in addition to the communication unit 31, the ID allocation request unit 32, the information allocation request 33, and the service request unit 35 illustrated in FIG. 1. And the point which has the price transmission request part 63, the key registration request part 64, and the input part 65 differs from the structure of the terminal 1 shown in FIG.

  The account issuance request unit 61 transmits an account issuance request for requesting issuance of an account to the accounting server 5 using the communication unit 31.

  Further, the account issuance request unit 61 writes the account transmitted from the accounting server 5 in response to the account issuance request in the storage unit 62.

  The storage unit 62 stores arbitrary information.

  For example, the storage unit 62 stores the account written by the account issue request unit 61.

  The storage unit 62 stores the ID written by the ID allocation request unit 32.

  Further, the storage unit 62 stores the license key LCK (service required information) written by the information allocation request unit 33.

  The storage unit 62 stores balance information indicating the balance of the amount deposited by the user of the terminal 6 by the electronic money function of the terminal 6.

  In the price transmission request unit 63, the input unit 65 receives an input from the user to request transmission of a price CST necessary for obtaining the license key LCK associated with the ID transmitted from the accounting server 5. In this case, a price transmission request for requesting transmission of the price CST is transmitted to the store terminal 4 using the communication unit 31.

  In addition, the price transmission request unit 63 outputs the price CST transmitted from the store terminal 4 in response to the price transmission request to the information allocation request unit 33. Thereafter, when the input unit 65 receives an input from the user to make a settlement accompanying the acquisition of the license key LCK associated with the ID transmitted from the billing server 5, the information allocation request unit 33 receives the price. The price CST output from the transmission request unit 63 is compared with the balance indicated by the balance information stored in the storage unit 62.

  As a result of the comparison, when the balance indicated by the balance information is equal to or higher than the price CST, the information allocation request unit 33 outputs an “information allocation request” for requesting allocation of a license key and the price transmission request unit 63. The amount information MNY and ID indicating the same amount as the price CST are transmitted to the store terminal 4 using the communication unit 31. In this example, when the information allocation request unit 33 transmits the amount information MNY to the store terminal 4, the amount indicated by the amount information MNY is subtracted from the balance indicated by the balance information in the storage unit 62. The obtained value is written as balance information. Examples of the money amount information MNY include general electronic money information.

  In addition, the information allocation request unit 33 writes the license key LCK transmitted from the store terminal 4 in response to the information allocation request to the storage unit 62.

  When the input unit 65 receives an input requesting registration of the license key LCK from the user, the key registration request unit 64 receives the license in the storage unit 62 together with the key registration request for requesting registration of the license key LCK. Key LCK, account AC, and ID are transmitted to billing server 5 using communication unit 31.

  When the registration completion notification indicating that the registration of the license key LCK is completed in response to the key registration request is transmitted from the accounting server 5, the key registration request unit 64 sends the registration completion notification to the service request unit 35. Output.

  After the registration completion notification is output from the key registration request unit 64, when the input unit 65 receives an input indicating that the service provided by the charging server 5 is received, the service request unit 35 The account AC stored in the storage unit 62 together with the service provision request for requesting provision is transmitted to the billing server 5 using the communication unit 31.

  Then, the billing server 5 authenticates the user using the account AC transmitted from the terminal 6 together with the service provision request, and provides the service to the user of the terminal 6 when the authentication is successful. In this example, when performing the authentication, the authentication unit 52 of the accounting server 5 stores the account AC and the license key LCK transmitted from the terminal 6 in association with each other in the key registration determination information KRG. In this case, it is determined that the user authentication is successful.

  The input unit 65 receives input of arbitrary information from the user of the terminal 6.

  Next, in the charging system having the above-described configuration, an operation of registering the license key LCK assigned to the terminal 6 by the shop terminal 4 in the charging server 5 will be described with reference to a sequence diagram shown in FIG.

  As a premise of the following description, the accounting server 5 generates a correspondence between the ID, the license key LCK, and the price CST and stores it as the ID information IDI shown in FIG. 12, and the ID, the license key LCK, The correspondence with the price CST is transmitted to the store terminal 4. Then, the store terminal 4 stores the key issuance information PB shown in FIG. 13 by associating the ID transmitted from the accounting server 5 with the license key LCK and the price CST and the settlement completion flag CM. Yes.

  Further, the terminal 6 transmits an account issue request to the accounting server 5. Then, the accounting server 5 generates an account AC (AC-1 in this example), assigns it to the user of the terminal 6, and transmits it to the terminal 6. Further, as shown in FIG. 14A, the accounting server 5 is in a state where the assigned account AC-1 is stored in the key registration determination information KRG.

  As shown in FIG. 18, when the terminal 6 receives from the user an input requesting ID assignment to the user, first, the terminal 6 sends an ID assignment request and an account AC for requesting the ID assignment. It transmits to the accounting server 5 (step S21). In step S <b> 21, when the terminal 6 transmits the temporary registration request, the terminal 6 also transmits a terminal ID (for example, an e-mail address assigned to the terminal 6) that can identify the terminal 6 to the charging server 5.

  Then, the accounting server 5 authenticates the user of the terminal 6 using the account AC transmitted with the ID assignment request. In this example, the accounting server 5 determines that the user has been successfully authenticated when the account AC transmitted from the terminal 6 is stored in the key registration determination information KRG.

  If it is determined that the user authentication is successful, the billing server 5 determines whether the account transmitted from the terminal 6 is stored in the key registration determination information KRG in association with the ID.

  If it is determined that the account transmitted from the terminal 6 is not stored in the key registration determination information KRG in association with the ID, the charging server 5 selects the ID stored in the ID information IDI shown in FIG. Is assigned to the user of the terminal 6 and transmitted to the terminal 6 (step S22). In this case, as shown in FIG. 14B, the accounting server 5 stores the ID assigned to the terminal 6 in the key registration determination information KRG in association with the account AC transmitted from the terminal 6. .

  Thereafter, when the terminal 6 receives an input requesting transmission of the price CST necessary for obtaining the license key LCK associated with the ID transmitted from the charging server 5 from the user, the terminal CST The ID transmitted from the billing server 5 together with the price transmission request for requesting transmission of is transmitted to the store terminal 4 (step S23).

  Then, the store terminal 4 reads the price CST stored in association with the ID transmitted together with the price transmission request from the storage unit 14 and transmits it to the terminal 6 (step S24).

  Thereafter, when the terminal 6 receives an input from the user to make a payment associated with the acquisition of the license key LCK, the price CST transmitted from the store terminal 4 and the balance information stored in the storage unit 62 are obtained. Compare the balance shown.

  As a result of the comparison, if the balance indicated by the balance information is equal to or higher than the price CST, the terminal 6 sends a payment request (information allocation request) for requesting execution of payment accompanying the purchase of the license key LCK, and the store terminal 4 The money amount information MNY and ID indicating the same money amount as the price CST transmitted from is transmitted to the store terminal 4 (step S25). In this example, when the terminal 6 transmits the money amount information MNY to the shop terminal 4, the terminal 6 subtracts the money amount indicated by the money amount information MNY from the balance indicated by the balance information in the storage unit 62, and is obtained by the subtraction. Write the value as balance information.

  When the payment request, the ID, and the money amount information MNY are transmitted from the terminal 6 in step S25, the store terminal 4 sets the payment completion flag stored in association with the ID to “completed” and “incomplete”. To indicate whether or not.

  If the settlement completion flag indicates “incomplete” as a result of the determination, the store terminal 4 reads the price CST stored in association with the ID from the storage unit 14 and transmits it from the terminal 6. Compared with the amount indicated by the amount information MNY.

  As a result of the comparison, if the amount indicated by the amount information MNY is equal to or greater than the read price CST, the store terminal 4 changes the settlement completion flag CM associated with the price CST from “incomplete” to “completed”. (Step S26).

  Subsequently, the store terminal 4 uses the license key LCK associated with the ID transmitted from the terminal 6 together with the settlement request when the amount indicated by the amount information MNY is equal to or greater than the read price CST. And is transmitted to the terminal 6 (step S27).

  Furthermore, when the payment completion flag CM is changed from “incomplete” to “completed”, the shop terminal 4 transfers the amount information MNY transmitted from the terminal 6 to the billing server 5 (step S28). Then, the accounting server 5 stores the amount information MNY transferred from the store terminal 4 (step S29).

  On the other hand, the terminal 6 stores the license key LCK transmitted from the store terminal 4 in step S27 in the storage unit 62.

  Thereafter, when the terminal 6 receives an input requesting registration of the license key LCK from the user, the terminal 6 and the license key LCK and the account AC in the storage unit 62 together with a key registration request for requesting registration of the license key LCK. And ID are transmitted to the accounting server 5 (step S30).

  Then, the accounting server 5 authenticates the user of the terminal 6 using the account AC transmitted from the terminal 6 (step S31). In this example, the accounting server 5 determines that the user has been successfully authenticated when the account AC is stored in the key registration determination information KRG.

  Further, when it is determined that the user authentication is successful, the accounting server 5 associates the ID transmitted from the terminal 6 together with the key registration request and the license key LCK in the ID information IDI shown in FIG. Determine if it is remembered.

  If it is determined that the ID and the license key LCK are stored in association with the ID information IDI as a result of the determination, the billing server 5 transmits from the terminal 6 as shown in FIG. The account AC, ID, and license key LCK that have been stored are associated with each other and stored in the key registration determination information KRG (step S32).

  Subsequently, the accounting server 5 transmits a registration completion notification indicating that the account AC, the ID, and the license key LCK transmitted from the terminal 6 are stored in association with each other to the terminal 6.

  In addition, after receiving the registration completion notification transmitted from the billing server 5, the terminal 6 stores a storage unit together with a service provision request for requesting provision of a service when receiving an input to receive the service from the user. The account AC stored in 62 is transmitted to the accounting server 5.

  Then, the accounting server 5 authenticates the user using the account transmitted from the terminal 6 together with the service provision request. In this example, the billing server 5 determines that the user has been successfully authenticated when the account AC and the license key LCK transmitted from the terminal 6 are stored in association with each other in the key registration determination information KRG. . If it is determined that the authentication is successful, the accounting server 5 provides a service to the user of the terminal 6.

  Thus, in the charging system, a series of operations for registering the license key LCK assigned to the terminal 6 by the shop terminal 4 in the charging server 5 is completed.

  As described above in the second embodiment, the account issuing system of the present invention can also be applied to uses such as providing a highly anonymous billing service.

  In the present invention, the processing in the allocation device 1 is recorded on a recording medium readable by the allocation device 1 in addition to the processing realized by the dedicated hardware described above. The program recorded on the recording medium may be read by the assignment device 1 and executed. The recording medium readable by the allocating device 1 refers to a transfer medium such as a floppy disk (registered trademark), a magneto-optical disk, a DVD, and a CD, as well as an HDD built in the allocating device 1. The program recorded on the recording medium is read by, for example, the member pseudonym ID generation unit 16 and the member certificate generation unit 17 included in the assignment device 1 and is controlled by the member pseudonym ID generation unit 16 and the member certificate generation unit 17. Thus, the same processing as described above is performed.

  Here, the member pseudonym ID generation unit 16 and the member certificate generation unit 17 included in the assignment device 1 operate as a computer that executes a program read from a recording medium on which the program is recorded. Note that the above-described program can be similarly applied to the registration apparatus 2.

  As mentioned above, although this invention was demonstrated with reference to Embodiment 1-2, this invention is not limited to the said Embodiment 1-2. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention without departing from the gist of the present invention.

It is a figure which shows the structure of the account issuing system according to embodiment of this invention. It is a figure which shows the structure of the service provision system of Embodiment 1 to which the account issuing system of this invention is applied. It is a figure which shows the 1st example of the data structure of registration identification information. It is a figure which shows the 2nd example of the data structure of registration identification information. It is a figure which shows the 3rd example of the data structure of registration identification information. It is a figure which shows the 4th example of the data structure of registration identification information. It is a figure which shows the structure of the authentication server shown in FIG. It is a figure which shows the structure of the service provision server shown in FIG. It is a figure which shows the structure of the terminal shown in FIG. In the service provision system of Embodiment 1, it is a figure which shows the operation | movement sequence at the time of a service provision server registering the member pseudonym ID which the authentication server allocated with respect to the user of a terminal. It is a figure which shows the structure of the charging system of Embodiment 2 to which the account issuing system of this invention is applied. It is a figure which shows an example of the data structure of ID information. It is a figure which shows an example of the data structure of key issue information. (A) It is a figure which shows an example of the data structure of the key registration determination information after account allocation. (B) It is a figure which shows an example of the data structure of the key registration determination information after ID allocation. (C) It is a figure which shows an example of the data structure of the key registration discrimination | determination information after license key registration. It is a figure which shows the structure of the shop terminal shown in FIG. It is a figure which shows the structure of the accounting server shown in FIG. It is a figure which shows the structure of the terminal shown in FIG. It is a figure which shows the operation | movement sequence at the time of registering the license key which the shop terminal allocated to the user of the terminal in a charging system in a charging server.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Authentication server 11 Communication part 12 Account generation part 13 Key generation part 14 Storage part 15 Member authentication part 16 Member pseudonym ID generation part 17 Member certificate generation part 18 Information allocation part 2 Service provision server 21 Communication part 22 Storage part 23 ID allocation Unit 24 temporary registration ID generation unit 25 temporary registration certificate generation unit 26 authentication unit 27 member pseudonym registration unit 28 service provision unit 3 terminal 31 communication unit 32 ID allocation request unit 33 information allocation request unit 34 member pseudonym registration request unit 35 service request Unit 36 Storage unit 4 Store terminal 41 Information writing unit 42 Price transmission unit 43 Settlement unit 44 Payment unit 5 Charging server 51 Account issuing unit 52 Authentication unit 53 ID information generating unit 54 Key registration unit 55 Payment receiving unit 6 Terminal 61 Account issuing Request section 62 Storage section 63 Price transmission request section 64 Key registration request section 65 Input section

Claims (66)

In an account issuing system comprising a terminal used by a user, a registration device that provides services to the terminal, and an allocation device connected to the terminal and the registration device,
The allocation device stores a correspondence between a preset ID (Identification) and service necessary information necessary for receiving the service, and an information allocation request for requesting allocation of service necessary information to the user When transmitted from the terminal, the service allocation information stored in association with the ID transmitted from the terminal together with the information allocation request is allocated to the user and transmitted to the terminal,
The terminal transmits an ID allocation request for requesting allocation of the ID to a user of the terminal to the registration device, and transmits the ID transmitted from the registration device and the information allocation request to the allocation device. , Transmitting the service requirement information transmitted from the allocation device and the ID transmitted from the registration device to the registration device,
The registration device stores a correspondence between the preset ID and service necessary information, and when the ID allocation request is transmitted from the terminal, an arbitrary ID is used from the stored ID. An account issuing system for allocating to a user and transmitting to the terminal, and providing the service to the terminal based on the ID and the service necessary information when the ID and the service necessary information are transmitted from the terminal. In the account issuing system according to claim 1,
The allocating device allocates member authentication information used for user authentication to the user, transmits the information to the terminal in advance, and includes a member pseudonym ID for managing the user by the registration device. When a request for issuing a membership certificate for requesting the issuance of a membership certificate for proving that a user is a member is transmitted from the terminal together with the information allocation request, the request is transmitted together with the request for issuing a membership certificate. When the member pseudonym ID is generated and assigned to the user based on the member authentication information and the server identification information for uniquely identifying the registration device, the member pseudonym ID is transmitted to the terminal together with the service necessary information. Send
The terminal stores in advance the member authentication information and the server identification information transmitted from the assignment device, and the member certificate issuance request, the server identification information, and the ID transmitted from the registration device The member authentication information is transmitted to the allocation device, and when the member pseudonym ID and the service necessary information are transmitted from the allocation device, the member pseudonym ID and the service necessary information are requested to register the ID and the member pseudonym ID. To the registration device together with a member pseudonym registration request to
When the member pseudonym registration request, the member pseudonym ID, the ID, and the service necessary information are transmitted from the terminal, the registration device authenticates a user of the terminal using the ID, and the authentication If successful, the member pseudonym ID is further stored in association with the association between the ID and the required service information. In the account issuing system according to claim 2,
The assigning device generates the member pseudonym ID by applying a predetermined hash function to the member ID and the server identification information included in the member authentication information transmitted from the terminal. An account issuance system. In the account issuing system according to claim 2 or 3,
The registration device, when a temporary registration request for requesting temporary registration of the user is transmitted from the terminal together with the ID allocation request, other than personal information relating to the user himself / herself accompanying the temporary registration request A temporary registration user ID is generated based on non-personal information that is predetermined information, the temporary registration user ID and the ID assigned to the user are stored in association with each other, and the ID and the temporary registration user ID are stored. The temporary registration certificate including the association is generated and the temporary registration certificate and the assigned ID are transmitted to the terminal. The temporary registration user ID and the member pseudonym ID in the temporary registration certificate Is transmitted from the terminal together with the ID, the service necessary information, and the member pseudonym registration request, using the ID, the service necessary information, and the member certificate. The authenticating who if successful the authentication, storing in association with each member pseudonym ID and the ID included in the associative membered certificate,
The terminal transmits the temporary registration request together with the ID allocation request to the registration device by specifying the server identification information, and when the temporary registration certificate and the ID are transmitted from the registration device, The temporary registration certificate and the ID are transmitted to the allocation device together with the membership certificate issuance request, the member authentication information, the information allocation request, and the server identification information, and the membership certificate and the service necessary information are transmitted to the allocation device. Sent to the registration device together with the ID and the member pseudonym registration request, the membership certificate and the service required information.
When the temporary registration certificate, the ID, the membership certificate issuance request, the member authentication information, the information allocation request, and the server identification information are transmitted from the terminal, the allocation device generates the member pseudonym An account issuing system, wherein the membership certificate including an ID and a temporary registration user ID in the temporary registration certificate is generated, and the membership certificate is transmitted to the terminal together with the service necessary information. In the account issuing system according to claim 4,
The said registration apparatus produces | generates the said temporary registration user ID based on the terminal relevant information regarding the said terminal as said non-personal information, The account issuing system characterized by the above-mentioned. In the account issuing system according to any one of claims 2 to 5,
When the member certificate issuance request, the member authentication information, and the server identification information are transmitted from the terminal, the allocating device authenticates the user using the member authentication information, and the authentication is successful. In this case, the account issuance system is characterized in that the member pseudonym ID is generated and transmitted to the terminal together with the service necessary information. In the account issuing system according to claim 4,
The registration device, when the membership certificate, the ID, the service required information, and the member pseudonym registration request are transmitted from the terminal, the temporary registration user ID and the ID included in the membership certificate Is included in the membership certificate, and the registration device stores the association between the ID transmitted from the terminal and the required service information. An account issuance system characterized in that a member pseudonym ID and the ID are stored in association with each other. In the account issuing system according to claim 4,
The registration device generates, as the temporary registration certificate, data obtained by encrypting the ID assigned to the user and the temporary registration user ID using the first encryption key transmitted from the assignment device, Sending the temporary registration certificate to the terminal;
The assigning device generates the first encryption key and a first decryption key for decrypting data encrypted by the first encryption key, and transmits the first encryption key to the registration device. When the encrypted temporary registration certificate is transmitted from the terminal together with the membership certificate issuance request and the ID, the temporary registration certificate is decrypted using the first decryption key. An account issuing system that generates the member pseudonym ID when the acquired ID matches the ID transmitted from the terminal. In the account issuing system according to claim 8,
The assigning device generates a second encryption key and a second decryption key for decrypting data encrypted by the second encryption key, and transmits the second decryption key to the registration device. , Generating the member certificate by generating, as the member certificate, data obtained by encrypting the generated member pseudonym ID and the temporary registration user ID of the temporary registration certificate transmitted from the terminal using the second encryption key. Send it to the device,
When the member certificate encrypted using the second encryption key is transmitted from the terminal together with the ID, the service necessary information, and the member pseudonym registration request, the registration device receives the member certificate. 2. An account issuing system characterized in that a member pseudonym ID obtained by decryption using a decryption key is stored in association with the ID. In the account issuing system according to any one of claims 2 to 9,
When the ID and the service necessary information are transmitted from the terminal together with a service provision request for requesting provision of the service, the registration device transmits the ID and service necessary information transmitted from the terminal, and the member It is determined whether or not the registration device stores the association with the pseudonym ID, and when it is determined that the association is stored as a result of the determination, the service is provided to the terminal. Account issuing system. In the account issuing system according to claim 1,
The registration device
The correspondence between the ID, the service necessary information, and the price for acquiring the service necessary information is stored, and an account used for user authentication is allocated to the user and transmitted to the terminal in advance. The allocated account is stored, and when the ID allocation request is transmitted from the terminal, it is determined whether the account transmitted with the ID allocation request is stored, and the account is stored as a result of the determination. If it is determined that the ID is assigned and transmitted to the terminal, the assigned ID is stored in association with the account, and the service required information and the ID are transmitted from the terminal, It is determined whether or not the registration apparatus stores the association between the service necessary information and the ID, and as a result of the determination, the association is stored. The service requirement information transmitted from the terminal is further stored in association with the association between the ID and the account, and then the service provision request for requesting provision of the account and the service is provided. When transmitted from the terminal, it is determined whether or not the association between the account transmitted from the terminal and the service necessary information is stored, and as a result of the determination, the association is stored. Providing the service to the terminal when it is determined that
The allocating device stores an association between the ID, the service necessary information, and the price, and performs the payment associated with the acquisition of the ID and the service necessary information corresponding to the ID to provide the service necessary information. When the information allocation request for requesting the allocation and the amount information indicating the same amount as the price corresponding to the service required information paid in the settlement is transmitted from the terminal, the information corresponds to the transmitted ID The service required information stored with the information is allocated to the user and transmitted to the terminal,
The terminal stores in advance the account transmitted from the registration device, transmits the ID allocation request and the account to the registration device, and the ID is transmitted from the registration device when the ID is transmitted. And the information allocation request and the amount information are transmitted to the allocation device, and when the service necessary information is transmitted from the allocation device, it is transmitted to the registration device together with the ID, and then the account and the service provision An account issuing system for transmitting a request to the registration device. The account issuing system according to claim 11,
The allocation device is:
The correspondence between the ID, the service necessary information, and the price is further stored in association with a settlement completion flag indicating whether settlement for the price is completed, and the ID is transmitted together with the information allocation request from the terminal. Is transmitted, it is determined whether or not the settlement completion flag stored in association with the ID indicates that the settlement has been completed, and the result of the determination indicates that the settlement has been completed. If it is determined that the information is not included, the amount indicated by the amount information transmitted with the information allocation request is compared with the price stored in association with the ID transmitted with the information allocation request, and the comparison is performed. As a result, if the amount is greater than or equal to the price, the settlement completion flag stored in association with the price is changed to indicate that the settlement is completed and the service is required Account issuing system and transmits assigned a broadcast to the user to the terminal. The account issuing system according to claim 12,
When the allocation device changes the settlement completion flag to indicate that the settlement has been completed, the registration device stores the amount information used for comparison with the price stored in association with the settlement completion flag. To the device,
The registration apparatus stores the amount information transmitted from the allocation apparatus. An allocation device connected to a terminal used by a user and a registration device that provides a service to the terminal,
A storage unit for storing a correspondence between a preset ID (Identification) and necessary service information necessary for receiving the service;
When an information allocation request for requesting allocation of service necessary information to the user is transmitted from the terminal, service necessary information stored in association with the ID transmitted from the terminal together with the information allocation request is stored. An allocation apparatus comprising: an information allocation unit that allocates to the user and transmits the information to the terminal. The allocation device according to claim 14,
A member authentication unit that assigns member authentication information used for authentication of the user to the user and transmits the information to the terminal in advance;
A member certificate issuance request for requesting issuance of a member certificate for proving that the user is a member including a member pseudonym ID for managing the user in the registration device is the information allocation request. And the member pseudonym ID is generated based on the member authentication information and the server identification information for uniquely identifying the registration device transmitted together with the member certificate issuance request. An allocation apparatus, comprising: a member pseudonym ID generation unit that, when assigned to the user, transmits the member pseudonym ID to the terminal together with the service necessary information. The allocation device according to claim 15,
The member pseudonym ID generating unit generates the member pseudonym ID by applying a predetermined hash function to the member ID and the server identification information included in the member authentication information transmitted from the terminal. An assigning device characterized in that: The allocation device according to claim 15 or 16,
Correspondence between the temporary registration user ID generated based on non-personal information that is predetermined information other than personal information related to the user himself / herself accompanying the temporary registration request for requesting temporary registration of the user and the ID A temporary registration certificate including an attachment, the ID, the member certificate issuance request, the member authentication information, the information allocation request, and the server identification information are transmitted from the terminal; A membership certificate generating unit that generates the membership certificate including a temporary registration user ID in the temporary registration certificate and transmits the membership certificate to the terminal together with the service necessary information. Assigning device. The allocation device according to any one of claims 15 to 17,
When the member certification issuance request, the member authentication information, and the server identification information are transmitted from the terminal, the member authentication unit authenticates the user using the member authentication information,
The member pseudonym ID generation unit generates the member pseudonym ID and transmits it to the terminal together with the service necessary information when authentication by the member authentication unit is successful. The allocation device according to claim 17,
A key generation unit that generates a first encryption key and a first decryption key for decrypting data encrypted by the first encryption key, and transmits the first encryption key to the registration device;
The member pseudonym ID generation unit includes a temporary registration certificate obtained by encrypting an ID assigned to the user and the temporary registration user ID using the first encryption key together with the member certificate issuance request and the ID. When the temporary registration certificate is decrypted using the first decryption key when transmitted from the terminal, and the ID acquired by the decryption and the ID transmitted from the terminal match, the member pseudonym ID An allocation apparatus characterized by generating The allocation device according to claim 19,
The key generation unit generates a second encryption key and a second decryption key for decrypting data encrypted by the second encryption key, and transmits the second decryption key to the registration device. Every
The member certificate generator generates data obtained by encrypting a temporary registration user ID in the temporary registration certificate transmitted from the terminal pseudonym ID and the terminal using the second encryption key. And assigning it to the terminal. The allocation device according to claim 14,
The storage unit stores an association between the ID, the service necessary information, and a price for acquiring the service necessary information,
The information allocating unit is configured to perform the payment associated with the acquisition of the service necessary information corresponding to the ID, the information allocation request for requesting the allocation of the service necessary information, and the service necessary to be paid by the settlement. When amount information indicating the same amount as the price corresponding to the information is transmitted from the terminal, the service necessary information stored in association with the transmitted ID is allocated to the user and transmitted to the terminal. An allocating device for transmitting. The allocation device according to claim 21,
The storage unit further stores a payment completion flag indicating whether or not payment for the price is completed in association with the ID, the service necessary information, and the price,
When the ID is transmitted together with the information allocation request from the terminal, it is determined whether or not the settlement completion flag stored in association with the ID indicates that the settlement is completed, and the result of the determination When it is determined that the payment has not been completed, the amount indicated by the amount information transmitted with the information allocation request is stored in association with the ID transmitted with the information allocation request. If the amount is equal to or greater than the price as a result of the comparison, the settlement completion flag stored in association with the price is changed to indicate that the settlement has been completed. Have a payment department,
If the amount indicated by the amount information is equal to or greater than the price stored in association with the transmitted ID as a result of the comparison by the settlement unit, the information allocating unit sends the service necessary information to the user. An allocating apparatus for allocating and transmitting to the terminal. The allocation device according to claim 22,
When the settlement unit changes the settlement completion flag to indicate that the settlement has been completed, the registration device stores the amount information used for comparison with the price stored in association with the settlement completion flag. An allocation apparatus, further comprising a depositing unit that transmits to A registration device that is connected to a terminal used by a user and an allocation device connected to the terminal and provides a service to the terminal,
A storage unit for storing a correspondence between a preset ID (Identification) and necessary service information necessary for receiving the service;
An ID allocation unit that allocates an arbitrary ID from the stored information to the user and transmits the ID to the user when an ID allocation request for requesting allocation of the ID to the user is transmitted from the terminal; ,
A registration apparatus comprising: a service providing unit that provides the service to the terminal based on the ID and the service necessary information when the terminal transmits the ID and the service necessary information. The registration device according to claim 24, wherein
Request registration of member pseudonym ID for managing the user in the registration device generated based on the member authentication information used for user authentication and server identification information for uniquely identifying the registration device When the member pseudonym registration request, the member pseudonym ID, the ID, and the service necessary information are transmitted from the terminal, an authentication unit that authenticates a user of the terminal using the ID;
When authentication by the authentication unit is successful, a member that further associates the member pseudonym ID transmitted from the terminal with the association between the ID transmitted from the terminal and the service required information, and stores it in the storage unit A registration apparatus comprising a kana registration unit. The registration device according to claim 25,
When a temporary registration request for requesting temporary registration of the user is transmitted from the terminal together with the ID allocation request, the information is predetermined information other than personal information relating to the user himself / herself accompanying the temporary registration request. A temporary registration ID generating unit that generates a temporary registration user ID based on non-personal information, associates the temporary registration user ID with the ID assigned to the user, and stores the temporary registration user ID in the storage unit;
A temporary registration certificate generating unit that generates a temporary registration certificate including a correspondence between the ID and the temporary registration user ID, and transmits the temporary registration certificate and the assigned ID to the terminal; ,
The member pseudonym registration unit transmits a membership certificate including the temporary registration user ID and the member pseudonym ID in the temporary registration certificate from the terminal together with the ID, the service necessary information, and the member pseudonym registration request. When the user of the terminal is authenticated using the ID, the service necessary information, and the membership certificate, and the authentication is successful, the member pseudonym ID included in the membership certificate and A registration apparatus that stores the ID in association with each other. The registration device according to claim 26,
The temporary registration ID generation unit generates the temporary registration user ID based on terminal-related information regarding the terminal as the non-personal information. The registration device according to claim 26,
The member pseudonym registration unit, when the member certificate, the ID, the service necessary information, and the member pseudonym registration request are transmitted from the terminal, the temporary registration user ID included in the member certificate, and the When the storage unit stores the association with the ID and the storage unit stores the association between the ID transmitted from the terminal and the service necessary information, the membership certificate includes A registration apparatus for storing a member pseudonym ID included in association with the ID. The registration device according to claim 26,
The temporary registration certificate generation unit uses, as the temporary registration certificate, data obtained by encrypting an ID allocated to the user and the temporary registration user ID using a first encryption key transmitted from the allocation device. A registration apparatus that generates and transmits the temporary registration certificate to the terminal. 30. A registration device according to claim 29,
The member pseudonym registration unit transmits a member certificate obtained by encrypting the member pseudonym ID and the temporary registration user ID using a second encryption key from the terminal together with the ID, the service necessary information, and the member pseudonym registration request. The member certificate is decrypted using the second decryption key transmitted from the assigning device, and the member pseudonym ID obtained by the decryption is stored in association with the ID. Registration device to do. The registration device according to any one of claims 25 to 30,
When the ID and the service necessary information are transmitted from the terminal together with a service provision request for requesting provision of the service, the service providing unit transmits the ID and service necessary information transmitted from the terminal, and It is determined whether or not the registration apparatus stores the association with the member pseudonym ID, and when it is determined that the association is stored as a result of the determination, the service is provided to the terminal. A registration device. The registration device according to claim 24, wherein
The storage unit stores the correspondence between the ID, the service necessary information, and a price for acquiring the service necessary information,
An account issuing unit for assigning an account used for user authentication to the user and transmitting the account in advance to the terminal, and storing the assigned account in the storage unit;
An authentication unit that determines whether the account transmitted with the ID allocation request is stored when the ID allocation request is transmitted from the terminal;
A key registration unit for further associating the service required information transmitted from the terminal with the association between the ID and the account and writing the information to the storage unit;
When the authentication unit determines that the ID is stored as a result of determining whether the account transmitted with the ID allocation request is stored, the ID allocation unit allocates the ID to the terminal And writing the assigned ID in association with the account to the storage unit,
The authentication unit determines whether the storage unit stores a correspondence between the service necessary information and the ID when the service necessary information and the ID are transmitted from the terminal;
When the authentication unit determines that the key registration unit stores the association between the service necessary information and the ID, the service registration information transmitted from the terminal is associated with the association between the ID and the account. In addition, write to the storage unit in association,
The authentication unit stores an association between the account transmitted from the terminal and the service necessary information when the account and a service provision request for requesting provision of the service are transmitted from the terminal. To determine whether
The service providing unit provides the service to the terminal when the authentication unit determines that the association between the account transmitted from the terminal and the service necessary information is stored. Registration device to do. The registration device according to claim 32,
A registration apparatus, comprising: a deposit receiving unit that stores amount information indicating an amount determined by the allocation apparatus to be equal to or higher than the price transmitted from the allocation apparatus. An account issuing method in an account issuing system comprising a terminal used by a user, a registration device that provides services to the terminal, and an allocation device connected to the terminal and the registration device,
A process in which the allocation device stores a correspondence between a preset ID (Identification) and service necessary information necessary for receiving the service;
A process in which the registration device stores an association between the preset ID and service necessary information;
A process in which the terminal transmits an ID allocation request for requesting allocation of the ID to a user of the terminal to the registration device;
When the registration apparatus receives the ID allocation request from the terminal, an ID allocation process for allocating an arbitrary ID from the stored information to the user and transmitting it to the terminal;
A process in which the terminal transmits an ID transmitted from the registration device and an information allocation request for requesting allocation of service required information to the user to the allocation device;
When the allocation apparatus receives the information allocation request from the terminal, the allocation apparatus allocates service necessity information stored in association with the ID transmitted from the terminal together with the information allocation request to the user. Information allocation processing to be transmitted to the terminal;
A process in which the terminal transmits service required information transmitted from the allocation device and an ID transmitted from the registration device to the registration device;
An account issuing method comprising: a service providing process in which the registration device provides the service to the terminal based on the ID and the service necessary information when the ID and the service necessary information are transmitted from the terminal. 35. The account issuing method according to claim 34.
A member authentication process in which the assignment device assigns member authentication information to be used for user authentication to the user and transmits it to the terminal in advance;
A process in which the terminal stores in advance member authentication information transmitted from the allocation device and server identification information for uniquely identifying the registration device;
In addition to the ID transmitted from the registration device, the terminal includes a member pseudonym ID for managing the user in the registration device, and a membership certificate for certifying that the user is a member. Processing for transmitting a member certificate issuance request for requesting issuance, the server identification information, the member authentication information, and the information allocation request to the allocation device;
When the allocation device has transmitted the membership certificate issuance request from the terminal together with the information allocation request, the member is based on the member authentication information and the server identification information transmitted together with the membership certificate issuance request. A member kana ID generation process for generating a kana ID and assigning it to the user, and transmitting the member kana ID to the terminal together with the service necessary information;
When the terminal receives a member pseudonym ID and service necessary information from the allocation device, the member pseudonym registration request for requesting registration of the ID and the member pseudonym ID for the member pseudonym ID and the service necessary information Together with the process of transmitting to the registration device;
When the registration device receives the member pseudonym registration request, the member pseudonym ID, the ID, and the service necessary information from the terminal, the registration device authenticates the user of the terminal using the ID, and the authentication And a member pseudonym registration process for further storing the member pseudonym ID in association with the association between the ID and the required service information. 36. The account issuing method according to claim 35,
In the member kana ID generation process, the member kana ID is obtained by applying a predetermined hash function to the member ID and the server identification information included in the member authentication information transmitted from the terminal. An account issuing method characterized by generating. The account issuing method according to claim 35 or 36,
A process in which the terminal transmits a temporary registration request for requesting temporary registration of the user to the registration device by specifying the server identification information together with the ID allocation request;
When the temporary registration request is transmitted from the terminal together with the ID assignment request, the registration device is based on non-personal information that is predetermined information other than personal information relating to the user himself / herself accompanying the temporary registration request. A temporary registration ID generation process for generating a temporary registration user ID and storing the temporary registration user ID and the ID assigned to the user in association with each other;
Temporary registration certificate generation processing in which the registration device generates a temporary registration certificate including a correspondence between the ID and the temporary registration user ID and transmits the temporary registration certificate and the assigned ID to the terminal When,
When the terminal receives the temporary registration certificate and the ID from the registration device, the temporary registration certificate and the ID are used for the membership certificate issuance request, the member authentication information, the information allocation request, and the ID. Processing to send to the allocation device together with server identification information;
When the allocation device receives the temporary registration certificate, the ID, the membership certificate issuance request, the member authentication information, the information allocation request, and the server identification information from the terminal, the generated member pseudonym Generating a membership certificate including an ID and a temporary registration user ID in the temporary registration certificate, and transmitting the membership certificate to the terminal together with the service necessary information;
When the terminal receives the membership certificate and the service necessary information from the allocation device, the terminal transmits the membership certificate and the service necessary information together with the ID and the member pseudonym registration request to the registration device. When,
The registration device transmits a membership certificate including a temporary registration user ID and the member pseudonym ID in the temporary registration certificate from the terminal together with the ID, the service necessary information, and the member pseudonym registration request. And an authentication process for authenticating the user of the terminal using the ID, the service necessary information, and the membership certificate,
In the member pseudonym registration process, when the authentication in the authentication process is successful, the member pseudonym ID included in the member certificate and the ID are stored in association with each other. The account issuing method according to claim 37,
In the temporary registration ID generation process, the temporary registration user ID is generated based on terminal-related information regarding the terminal as the non-personal information. In the account issuing method according to any one of claims 35 to 38,
In the member authentication process, when the member certificate issuance request, the member authentication information, and the server identification information are transmitted from the terminal, the user authentication is performed using the member authentication information,
In the member pseudonym ID generation process, when the authentication by the member authentication process is successful, the member pseudonym ID is generated and transmitted to the terminal together with the service necessary information. The account issuing method according to claim 37,
In the member pseudonym registration process, when the membership certificate, the ID, the service necessary information, and the member pseudonym registration request are transmitted from the terminal, the temporary registration user ID included in the membership certificate and the When the registration device stores the association with the ID, and the registration device stores the association between the ID transmitted from the terminal and the service necessary information, the membership certificate includes A method for issuing an account, comprising: storing a member pseudonym ID included in association with the ID. The account issuing method according to claim 37,
Key generation for generating a first encryption key and a first decryption key for decrypting data encrypted by the first encryption key, and transmitting the first encryption key to the registration device Have processing,
In the temporary registration certificate generation process, data obtained by encrypting the ID assigned to the user and the temporary registration user ID using the first encryption key transmitted from the assignment device is used as the temporary registration certificate. Generate and send the temporary registration certificate to the terminal,
In the member pseudonym ID generation process, when the encrypted temporary registration certificate is transmitted from the terminal together with the membership certificate issuance request and the ID, the temporary registration certificate is decrypted using the first decryption key. And generating the member pseudonym ID when the ID acquired by the decryption and the ID transmitted from the terminal coincide with each other. The account issuing method according to claim 41,
In the key generation process, a second encryption key and a second decryption key for decrypting data encrypted by the second encryption key are generated, and the second decryption key is transmitted to the registration device. Every
In the member certificate generation process, data obtained by encrypting the temporary registration user ID in the temporary registration certificate transmitted from the terminal pseudonym ID and the terminal using the second encryption key is used as the membership certificate. Generated and sent to the terminal,
In the member pseudonym registration process, when the membership certificate encrypted using the second encryption key is transmitted from the terminal together with the ID, the service necessary information, and the member pseudonym registration request, the membership certificate is A method for issuing an account, comprising: decrypting using the second decryption key; and storing the member pseudonym ID acquired by the decryption in association with the ID. In the account issuing method according to any one of claims 35 to 42,
In the service providing process, when the ID and the service necessary information are transmitted from the terminal together with a service provision request for requesting the provision of the service, the ID and service necessary information transmitted from the terminal, It is determined whether or not the registration device stores the association with the member pseudonym ID, and when it is determined that the association is stored as a result of the determination, the service is provided to the terminal. Account issuing method. 35. The account issuing method according to claim 34.
A process in which the registration device stores an association between the ID, the service necessary information, and a price for acquiring the service necessary information;
A process in which the allocating device stores an association between the ID, the service necessary information, and the price;
An account issuance process in which the registration device allocates an account used for authentication of the user to the user and transmits the account to the terminal in advance and stores the assigned account;
A process in which the terminal stores in advance an account transmitted from the registration device;
A process in which the terminal transmits the ID allocation request and the account to the registration device;
When the terminal receives the ID from the registration device, the terminal performs an payment associated with the acquisition of the service necessary information corresponding to the ID and requests an allocation of the service necessary information. And a process for transmitting to the allocating device amount information indicating the same amount as the price corresponding to the service required information to be paid in the settlement;
When the terminal receives the service necessary information from the allocation device, the terminal transmits the service necessary information together with the ID to the registration device;
When the registration apparatus receives the service necessary information and the ID from the terminal, the registration apparatus determines whether the registration apparatus stores a correspondence between the service necessary information and the ID, and the determination As a result, if it is determined that the association is stored, a key registration process for storing the service necessary information transmitted from the terminal in association with the association between the ID and the account;
The terminal includes, after the key registration process, a process of transmitting the account and a service provision request for requesting provision of the service to the registration apparatus;
In the ID allocation process, when the ID allocation request is transmitted from the terminal, it is determined whether or not the account transmitted with the ID allocation request is stored, and as a result of the determination, the account is stored. If it is determined that the ID is assigned and transmitted to the terminal, the assigned ID is stored in association with the account,
In the information allocation process, when the ID, the information allocation request, and the amount information are transmitted from the terminal, service required information stored in association with the transmitted ID is transmitted to the user. Allocate and send to the terminal,
In the service providing process, when the account and the service providing request are transmitted from the terminal, the registration apparatus stores a correspondence between the account transmitted from the terminal and the service necessary information An account issuing method comprising: providing the service to the terminal when it is determined that the association is stored as a result of the determination. 45. The account issuing method according to claim 44,
A process in which the assigning device further stores a payment completion flag indicating whether or not payment for the price is completed in association with the ID, the service necessary information, and the price;
When the ID is transmitted together with the information allocation request from the terminal, the allocation device determines whether or not the settlement completion flag stored in association with the ID indicates that the settlement has been completed. As a result of the determination, when it is determined that the payment has not been completed, the amount indicated by the amount information transmitted with the information allocation request, and the ID transmitted with the information allocation request, Compare with the price stored in association, and if the result of the comparison is that the amount is equal to or greater than the price, the settlement completion flag stored in association with the price is confirmed to have been settled. And change payment processing as shown,
In the information allocation process, if the amount indicated by the amount information is equal to or greater than the price stored in association with the transmitted ID as a result of the comparison in the settlement processing, the service necessary information is sent to the user. An account issuing method characterized by allocating and transmitting to the terminal. The account issuing method according to claim 45,
When the allocation device has changed the settlement completion flag to indicate that the settlement is completed in the settlement process, the allocation device is used for comparison with the price stored in association with the settlement completion flag. A depositing process for transmitting money amount information to the registration device;
An account issuing method, characterized in that the registration device includes a deposit receipt process for storing money amount information transmitted from the allocation device. To an allocation device connected to a terminal used by a user and a registration device that provides a service to the terminal,
A procedure for storing a correspondence between a preset ID (Identification) and necessary service information necessary for receiving the service in the storage unit;
When an information allocation request for requesting allocation of service necessary information to the user is transmitted from the terminal, service necessary information stored in association with the ID transmitted from the terminal together with the information allocation request is stored. A program for executing an information allocation procedure to be allocated to the user and transmitted to the terminal. The program according to claim 47,
A member authentication procedure in which member authentication information used for user authentication is allocated to the user and transmitted to the terminal in advance;
A member certificate issuance request for requesting issuance of a member certificate for proving that the user is a member including a member pseudonym ID for managing the user in the registration device is the information allocation request. And the member pseudonym ID is generated based on the member authentication information and the server identification information for uniquely identifying the registration device transmitted together with the member certificate issuance request. A program for causing the allocation apparatus to further execute a member pseudonym ID generation procedure for allocating to the user and transmitting the member pseudonym ID together with the service necessary information to the terminal. 49. The program according to claim 48, wherein:
In the member kana ID generation procedure, the member kana ID is generated by applying a predetermined hash function to the member ID and the server identification information included in the member authentication information transmitted from the terminal. The program characterized by doing. The program according to claim 48 or 49,
Correspondence between the temporary registration user ID generated based on non-personal information that is predetermined information other than personal information related to the user himself / herself accompanying the temporary registration request for requesting temporary registration of the user and the ID A temporary registration certificate including an attachment, the ID, the member certificate issuance request, the member authentication information, the information allocation request, and the server identification information are transmitted from the terminal; A member certificate generation procedure for generating the membership certificate including the temporary registration user ID in the temporary registration certificate and transmitting the membership certificate to the terminal together with the service necessary information is further provided to the allocation device. A program characterized by being executed. The program according to any one of claims 48 to 50,
In the member authentication procedure, when the member certificate issuance request, the member authentication information, and the server identification information are transmitted from the terminal, the user authentication is performed using the member authentication information,
In the member pseudonym ID generation procedure, when authentication in the member authentication procedure is successful, the member pseudonym ID is generated and transmitted to the terminal together with the service necessary information. The program according to claim 50,
A key generation procedure for generating a first encryption key and a first decryption key for decrypting data encrypted by the first encryption key and transmitting the first encryption key to the registration device; To run
In the member pseudonym ID generation procedure, the temporary registration certificate obtained by encrypting the ID assigned to the user and the temporary registration user ID using the first encryption key is included in the membership certificate issuance request and the ID. When the temporary registration certificate is decrypted using the first decryption key when transmitted from the terminal, and the ID acquired by the decryption and the ID transmitted from the terminal match, the member pseudonym ID A program characterized by generating 53. The program according to claim 52,
In the key generation procedure, a second encryption key and a second decryption key for decrypting data encrypted by the second encryption key are generated, and the second decryption key is transmitted to the registration device. And
In the member certificate generation procedure, data obtained by encrypting the temporary registration user ID in the temporary registration certificate transmitted from the terminal pseudonym ID and the terminal using the second encryption key is used as the membership certificate. As a program generated and transmitted to the terminal. The program according to claim 47,
Causing the allocation device to execute a process of storing a correspondence between the ID, the service necessary information, and a price for acquiring the service necessary information in the storage unit;
In the information allocation procedure, the ID, an information allocation request for requesting allocation of the service necessary information by performing settlement associated with the acquisition of the service necessary information corresponding to the ID, and the service necessity to be paid in the settlement When amount information indicating the same amount as the price corresponding to the information is transmitted from the terminal, the service necessary information stored in association with the transmitted ID is allocated to the user and transmitted to the terminal. A program characterized by transmitting. The program according to claim 54,
A procedure for further associating a settlement completion flag indicating whether settlement with respect to the price is completed in association with the ID, the service necessary information, and the price, and storing them in the storage unit;
When the ID is transmitted together with the information allocation request from the terminal, it is determined whether or not the settlement completion flag stored in association with the ID indicates that the settlement is completed, and the result of the determination When it is determined that the payment has not been completed, the amount indicated by the amount information transmitted with the information allocation request is stored in association with the ID transmitted with the information allocation request. If the amount is equal to or greater than the price as a result of the comparison, the settlement completion flag stored in association with the price is changed to indicate that the settlement has been completed. A payment procedure is executed by the allocation device;
In the information allocation procedure, if the amount indicated by the amount information is equal to or greater than the price stored in association with the transmitted ID as a result of the comparison by the settlement procedure, the service necessary information is sent to the user. A program which is allocated and transmitted to the terminal. The program according to claim 55,
When the payment completion flag is changed to indicate that payment is completed in the payment procedure, the amount information used for comparison with the price stored in association with the payment completion flag is registered. A program for causing the allocation device to further execute a depositing procedure to be transmitted to the device. A registration device connected to a terminal used by a user and an allocation device connected to the terminal and providing a service to the terminal;
A procedure for storing a correspondence between a preset ID (Identification) and necessary service information necessary for receiving the service in the storage unit;
An ID allocation procedure for allocating an arbitrary ID from the stored information to the user and transmitting it to the terminal when an ID allocation request for requesting allocation of the ID to the user is transmitted from the terminal; ,
When the terminal transmits the ID and the service necessary information, a program for executing a service providing procedure for providing the service to the terminal based on the ID and the service necessary information. 58. The program according to claim 57, wherein
Request registration of member pseudonym ID for managing the user in the registration device generated based on the member authentication information used for user authentication and server identification information for uniquely identifying the registration device When the member pseudonym registration request, the member pseudonym ID, the ID, and the service necessary information are transmitted from the terminal, an authentication procedure for authenticating a user of the terminal using the ID;
When authentication in the authentication procedure is successful, a member that further associates the member pseudonym ID transmitted from the terminal with the association between the ID transmitted from the terminal and the service required information, and stores it in the storage unit A program that causes the registration device to further execute a kana registration procedure. 59. The program according to claim 58, wherein:
When a temporary registration request for requesting temporary registration of the user is transmitted from the terminal together with the ID allocation request, the information is predetermined information other than personal information relating to the user himself / herself accompanying the temporary registration request. A temporary registration ID generating procedure for generating a temporary registration user ID based on non-personal information and storing the temporary registration user ID and the ID assigned to the user in association with each other;
Generating a temporary registration certificate including a correspondence between the ID and the temporary registration user ID and transmitting the temporary registration certificate and the assigned ID to the terminal; Let the device perform further,
In the member pseudonym registration procedure, a membership certificate including the temporary registration user ID and the member pseudonym ID in the temporary registration certificate is transmitted from the terminal together with the ID, the service necessary information, and the member pseudonym registration request. When the user of the terminal is authenticated using the ID, the service necessary information, and the membership certificate, and the authentication is successful, the member pseudonym ID included in the membership certificate and A program characterized by storing the ID in association with each other. The program according to claim 59,
In the temporary registration ID generation procedure, the temporary registration user ID is generated based on terminal-related information regarding the terminal as the non-personal information. The program according to claim 59,
In the member pseudonym registration procedure, when the membership certificate, the ID, the service necessary information, and the member pseudonym registration request are transmitted from the terminal, the temporary registration user ID included in the membership certificate and the When the storage unit stores the association with the ID and the storage unit stores the association between the ID transmitted from the terminal and the service necessary information, the membership certificate includes A program comprising: storing a member pseudonym ID included in association with the ID. The program according to claim 59,
In the temporary registration certificate generation procedure, data obtained by encrypting the ID assigned to the user and the temporary registration user ID using the first encryption key transmitted from the assignment device is used as the temporary registration certificate. A program that generates and transmits the temporary registration certificate to the terminal. The program according to claim 62,
In the member pseudonym registration procedure, a member certificate obtained by encrypting the member pseudonym ID and the temporary registration user ID using a second encryption key is transmitted from the terminal together with the ID, the service necessary information, and the member pseudonym registration request. If so, the member certificate is decrypted using the second decryption key transmitted from the assigning device, and the member pseudonym ID obtained by the decryption is stored in the storage unit in association with the ID. A program characterized by that. The program according to any one of claims 58 to 63, wherein:
In the service provision procedure, when the ID and the service necessary information are transmitted from the terminal together with a service provision request for requesting provision of the service, the ID and the service necessary information transmitted from the terminal, It is determined whether or not the registration apparatus stores the association with the member pseudonym ID, and when it is determined that the association is stored as a result of the determination, the service is provided to the terminal. Program. 58. The program according to claim 57, wherein
A procedure for storing a correspondence between the ID, the service necessary information, and a price for acquiring the service necessary information in the storage unit;
An account issuance procedure for assigning an account used for authentication of the user to the user and transmitting the account to the terminal in advance, and storing the assigned account in the storage unit;
An authentication procedure for determining whether or not an account transmitted with the ID allocation request is stored when the ID allocation request is transmitted from the terminal;
Causing the registration apparatus to execute a key registration procedure for further associating the service necessary information transmitted from the terminal with the association between the ID and the account and writing the information to the storage unit;
In the ID allocation procedure, as a result of determining whether or not the account transmitted with the ID allocation request is stored, if the authentication procedure determines that the account is stored, the ID is allocated and the ID is allocated. Transmitting to the terminal, and writing the assigned ID in association with the account to the storage unit,
In the authentication procedure, when the service necessary information and the ID are transmitted from the terminal, it is determined whether or not the storage unit stores a correspondence between the service necessary information and the ID,
In the key registration procedure, if the authentication procedure determines that the association between the service requirement information and the ID is stored, the service requirement transmitted from the terminal to the association between the ID and the account is required. Write information to the storage unit in association with further information,
In the authentication procedure, when the account and a service provision request for requesting provision of the service are transmitted from the terminal, an association between the account transmitted from the terminal and the service necessary information is stored. To determine whether
In the service providing procedure, the service is provided to the terminal when the authentication procedure determines that the association between the account transmitted from the terminal and the service necessary information is stored. Program. The program according to claim 65,
A program for causing the lantern device to further execute a deposit receiving procedure for storing money amount information indicating an amount determined by the allocating device as being equal to or higher than the price transmitted from the allocating device.

Images