WO2009113154A1 - Id managing system and id managing method - Google Patents

Abstract

A main ID managing device manages a main ID, an auxiliary ID managing device ID for specifying an auxiliary ID managing device, an allocation management ID for specifying a correspondence relation of the auxiliary ID and the main ID, and individual information of a user specified by the main ID (information on a bank account or a credit number of a user, which are used for settlement processing service, and a name and an address, which are used for physical distribution service, for example) by associating them with one another. The auxiliary ID managing device correspondingly manages the auxiliary ID, the main ID managing device ID for specifying the main ID managing device and the allocation management ID.

Description

ID management system and ID management method

The present invention relates to an ID management system and an ID management method for managing a primary ID and a secondary ID issued in response to a request from a user.

2. Description of the Related Art Conventionally, there is a technique for managing service user information for the purpose of providing a service via a network (see, for example, Patent Document 1).

In addition, the service user may have a large number of IDs for each use, such as a company employee ID, a supermarket customer ID, and an insurance contractor ID. In such a case, there is a case where it is necessary to manage that a large number of IDs different for each application are held by the same person.

For example, in a case where a student makes a student insurance contract using a student ID and is issued an insurance policyholder ID, the student ID and policyholder ID are owned by the same person. It may be necessary to manage something. Therefore, conventionally, for example, an ID management device provided in an insurance company that needs to manage that a student ID and a contractor ID are held by the same person is contracted with the student ID. The correspondence with the person ID is associated and managed.

JP 2005-50330 A

However, conventionally, since different types of IDs having different uses are associated and managed in one apparatus, there is a problem that the correspondence between different types of IDs having different uses may be exposed.

As described above, if the correspondence between different types of IDs with different uses is exposed, there is a problem that various information corresponding to the different types of IDs are made public by the same person. . For example, when the correspondence between the student ID and the contractor ID has been exposed, the academic achievement that is the information corresponding to the student ID is the same as the non-payment of premium information that is the information corresponding to the contractor ID. It becomes public as a person's.

Accordingly, the present invention has been made to solve the above-described problems of the prior art, and an ID management system and an ID that can prevent the correspondence between different types of IDs having different uses from being exposed. The purpose is to provide a management method.

In order to solve the above-described problems and achieve the object, the present invention provides a user terminal used by a user, a main ID management device that manages a main ID for identifying the user for the first use, An ID management system including a secondary ID management device for managing a secondary ID for identifying a user for the second use, wherein the primary ID management device includes a primary ID and the secondary ID management. A secondary ID management device ID for specifying a device, and a primary ID management means for managing an association management ID for specifying a correspondence relationship between the secondary ID and the primary ID in association with each other; The sub-ID management means for managing the sub ID, the main ID management device ID for specifying the main ID management device, and the allocation management ID in association with each other is a requirement.

Further, according to the present invention, in the above invention, the sub ID management means manages the main ID management device ID and the allocation management ID that are different for each main ID management device in association with the sub ID. To do.

Also, in the present invention, in the above invention, the secondary ID management device requests a secondary ID generation means for generating a secondary ID and a login by a primary ID when receiving a secondary ID issue request from the user terminal. The main ID to be associated with the sub-ID generated by the sub-ID generation means is whether or not the user of the user terminal that is the user and the user of the user terminal that is the transmission source of the sub-ID issue request is the same person. The same person confirmation means for confirming in cooperation with the managing main ID management device, the user terminal user who requests the login request, and the user terminal user who is the transmission source of the sub ID issue request are the same person. Is confirmed by the same person confirmation unit, the correspondence between the sub ID generated by the sub ID generation unit and the main ID to be associated with the sub ID An allocation management ID generating unit that generates an allocation management ID to be indicated; and an allocation management that transmits the allocation management ID generated by the allocation management ID generating unit to a main ID management device that manages a main ID to be associated with the sub ID An ID transmission unit, a sub ID generated by the sub ID generation unit, a main ID management device ID for specifying a main ID management device that manages a main ID to be associated with the sub ID, and the allocation management ID A sub-ID allocation management information recording unit that records the allocation management ID generated by the generating unit in association with each other; and when the recording by the sub-ID allocation management information recording unit is completed, the transmission source of the sub-ID issue request A sub-ID transmission unit that transmits the sub-ID generated by the sub-ID generation unit to the user terminal, wherein the main ID management device An allocation management ID receiving means for receiving an allocation management ID from the D management apparatus; an allocation management ID received by the allocation management ID receiving means; and a sub-ID management apparatus that is a transmission source of the allocation management ID It is a requirement that the apparatus further includes a main ID assignment management information recording unit that records the sub ID management device ID and the main ID that has requested login in association with each other.

The present invention also issues and manages a primary ID for identifying a user for the first use, and issues and manages a sub-ID for identifying the user for the second use. An ID management method, wherein a primary ID management device that manages a primary ID includes a primary ID, a secondary ID management device ID for specifying a secondary ID management device that manages a secondary ID, a secondary ID, and a primary ID. The secondary ID management device that manages the secondary ID includes a primary ID management step that causes the primary ID management device to manage the primary ID management device in association with the allocation management ID for specifying the correspondence relationship. The secondary ID management device manages the secondary ID and the primary ID. It is a requirement to include a sub-ID management step in which a main ID management device ID for specifying an ID management device and an allocation management ID are associated with each other and managed by the sub-ID management device.

Further, in the present invention, the present invention requires that the sub ID management step manages a different main ID management device ID and allocation management ID for each main ID management device in association with the sub ID. To do.

The secondary ID management device, when receiving a secondary ID issue request from a user terminal used by a user, a secondary ID generation step of generating a secondary ID, a user of a user terminal requesting login by a primary ID, Cooperation with the main ID management apparatus that manages the main ID to be associated with the sub ID generated by the sub ID generation step, as to whether or not the user of the user terminal that is the transmission source of the sub ID issue request is the same person The same person confirmation step confirms that the user of the user terminal that requests the login request and the user of the user terminal that is the transmission source of the sub ID issue request are the same person. If confirmed, it indicates the correspondence between the sub ID generated in the sub ID generation step and the main ID to be associated with the sub ID. An allocation management ID generating step for generating an allocation management ID, and an allocation management ID for transmitting the allocation management ID generated by the allocation management ID generation step to a main ID management device that manages a main ID to be associated with the sub ID. A transmission step, a sub ID generated by the sub ID generation step, a main ID management device ID for specifying a main ID management device that manages a main ID to be associated with the sub ID, and the allocation management ID generation When the recording by the sub ID allocation management information recording step for recording the allocation management ID associated with the step in association with each other and the recording by the sub ID allocation management information recording step are completed, the transmission source of the sub ID issue request is A sub-ID transmission step of transmitting the sub-ID generated by the sub-ID generation step to a certain user terminal. The primary ID management device includes an allocation management ID receiving step for receiving an allocation management ID from the secondary ID management device, an allocation management ID received by the allocation management ID receiving step, and a transmission source of the allocation management ID. It is a requirement that it further includes a main ID assignment management information recording step of recording a sub ID management device ID for specifying a certain sub ID management device in association with a main ID that has requested login.

According to the present invention, there is an effect that it is possible to prevent the correspondence between different kinds of IDs having different uses from being exposed.

In addition, according to the present invention, the anonymity of the primary ID and the secondary ID is maintained, and the secondary ID can be issued on the condition that the primary ID exists.

FIG. 1 is a diagram for explaining the outline and features of the ID management system according to the first embodiment. FIG. 2 is a diagram illustrating a system configuration of the ID management system according to the first embodiment. FIG. 3 is a block diagram illustrating the configuration of the main ID management apparatus according to the first embodiment. FIG. 4 is a diagram illustrating a configuration example of the main ID management information and the sub ID management information according to the first embodiment. FIG. 5 is a block diagram illustrating the configuration of the secondary ID management apparatus according to the first embodiment. FIG. 6 is a diagram illustrating a process flow of the ID management system according to the first embodiment. FIG. 7 is a block diagram illustrating the configuration of the secondary ID management apparatus according to the second embodiment. FIG. 8 is a diagram illustrating a process flow of the ID management system according to the second embodiment. FIG. 9 is a diagram illustrating a process flow of the ID management system according to the second embodiment. FIG. 10 is a diagram for explaining the features of the ID management system according to the third embodiment. FIG. 11 is a diagram illustrating a system configuration of the ID management system according to the third embodiment. FIG. 12 is a diagram illustrating a configuration example of main ID management information and sub ID management information according to the third embodiment. FIG. 13 is a diagram illustrating a process flow of the ID management system according to the third embodiment. FIG. 14 is a diagram illustrating a process flow of the ID management system according to the third embodiment. FIG. 15 is a diagram illustrating a process flow of the ID management system according to the third embodiment. FIG. 16 is a diagram illustrating an overview of an ID management system according to the fourth embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Main ID management apparatus 110 Storage part 111 Main ID management information 120 Control part 121 Data transmission / reception part 122 Owner confirmation part 123 Data registration part 200 Sub ID management apparatus 210 Storage part 211 Sub ID management information 220 Control part 221 Data transmission / reception part 222 Sub ID generation unit 223 Identity verification data generation unit 224 Allocation management ID generation unit 225 Data registration unit 226 Main ID authentication request unit 300 User terminal

Hereinafter, an embodiment for carrying out an ID management system and an ID management method according to the present invention will be described in detail with reference to the accompanying drawings. In the following, Example 1 will be described as an embodiment of the ID management system according to the present invention, and then other embodiments included in the ID management system according to the present invention will be described in other examples.

[Outline and Features of ID Management System (Example 1)]
First, the outline and characteristics of the ID management system according to the first embodiment will be described with reference to FIG. FIG. 1 is a diagram for explaining the outline and features of the ID management system according to the first embodiment.

The ID management system according to the first embodiment outlines the management of the primary ID and the secondary ID issued in response to a request from the user, but the correspondence between different types of IDs with different uses is exposed. The main feature is to prevent.

That is, as shown in FIG. 1, the ID management system according to the first embodiment includes a user terminal used by a user and a main ID management device that manages a main ID that issues a main ID for uniquely identifying the user. And a sub-ID management device that issues a sub-ID for uniquely identifying a virtual person used by the user on the network.

The main ID management device uses the main ID, the sub ID management device ID for specifying the sub ID management device, the allocation management ID for specifying the correspondence between the sub ID and the main ID, and the main ID. Personal information (for example, user bank account information and credit number information for use in a payment processing service, name and address for use in a logistics service, etc.) is managed in association with each other.

Also, the secondary ID management device manages the secondary ID, the primary ID management device ID for specifying the primary ID management device, and the allocation management ID in association with each other.

In this way, information managed on the main ID management apparatus side is exposed by managing the main ID and the sub ID in association with the allocation management ID without directly managing them in association with each other. Even so, the correspondence between the primary ID and the secondary ID is not revealed.

That is, the ID management system according to the first embodiment can prevent the correspondence between different types of IDs having different uses from being exposed, like the main feature described above.

[Configuration of ID management system (Example 1)]
Next, the configuration of the ID management system according to the first embodiment will be described with reference to FIGS. FIG. 2 is a diagram illustrating a system configuration of the ID management system according to the first embodiment. FIG. 3 is a block diagram illustrating the configuration of the main ID management apparatus according to the first embodiment. FIG. 4 is a diagram illustrating a configuration example of the main ID management information and the sub ID management information according to the first embodiment. FIG. 5 is a block diagram illustrating the configuration of the secondary ID management apparatus according to the first embodiment.

As illustrated in FIG. 2, the ID management system according to the first embodiment includes a user terminal 300 used by a user, and a main ID management device 100 that manages a main ID that issues a main ID for uniquely identifying the user. And a sub ID management device 200 that issues a sub ID for uniquely identifying a virtual person used by the user on the network. Further, the user terminal 300, the main ID management device 100, and the sub ID management device 200 are connected to each other so that they can communicate with each other via a network, and the main ID management device 100 and the sub ID management device 200 are connected to each other. They are connected so that they can communicate with each other via a network.

As shown in FIG. 3, the main ID management device 100 includes a storage unit 110 and a control unit 120.

The storage unit 110 is a storage unit that stores data and programs necessary for various processes performed by the control unit 120. In particular, the storage unit 110 includes main ID management information 111 that is closely related to the present invention. The main ID management information 111 corresponds to “main ID management means” described in the claims.

As shown in FIG. 4, the main ID management information 111 includes a main ID issued in advance for uniquely identifying a user and a main ID for authenticating the user of the user terminal 300 that has logged in using the main ID. Authentication data (for example, a password), a sub ID management device ID for specifying the sub ID management device 200 connected in a communicable state, and a sub ID issued to the user by the sub ID management device 200 An allocation management ID for specifying the correspondence relationship with the main ID (link relationship between the sub-ID and the main ID), and personal information (for example, a payment processing service) of the user specified by the main ID (not shown) Information on the bank account of the user, information on credit numbers, and name and address for use in logistics services).

The control unit 120 has a predetermined control program, a program defining various processing procedures, and an internal memory for storing necessary data, and executes various processes using these, and is particularly suitable for the present invention. As closely related, a data transmission / reception unit 121, an owner confirmation unit 122, and a data registration unit 123 are provided.

The data transmission / reception unit 121 is a processing unit that performs transmission / reception of data between the user terminal 300 and the sub-ID management device 200. Specifically, the data transmission / reception unit 121 receives the main ID and the main ID password when accepting login from the user terminal 300.

Further, the data transmitting / receiving unit 121 receives a request for assigning a main ID to a sub ID from the user terminal 300 and also receives an assignment management ID from the sub ID management device 200. This assignment processing request includes data for identity verification.

In addition, when the data transmission / reception unit 121 receives a request for assigning a main ID to a sub-ID from the user terminal 300, the authentication result of the main ID by the owner confirmation unit 122, which will be described later, and the personal identification data included in the assignment processing request The allocation management ID issuance request combined with the above is transmitted to the secondary ID management device 200. Furthermore, when the registration by the data registration unit 123 described later is completed, the data transmission / reception unit 121 transmits a main ID assignment process completion notification to the user terminal 300.

The owner confirmation unit 122 is a processing unit that authenticates the main ID when a login by the main ID is accepted. Specifically, the owner confirmation unit 122 confirms whether or not the main ID acquired at the time of login is already registered in the main ID management information 111. When the main ID is already registered, the owner confirmation unit 122 acquires the main ID password stored in the main ID management information 111 in association with the main ID, and logs in the main ID at the time of login. Compared with the main ID password received together with the ID, authentication is performed as to whether or not the owner is a valid owner of the main ID.

The data registration unit 123 is a processing unit that registers assignment management IDs and the like. Specifically, when the data management unit 121 receives the allocation management ID from the data transmission / reception unit 121, the data registration unit 123 identifies the allocation management ID and the secondary ID management device 200 that is the transmission source of the allocation management ID. The ID management device ID and the main ID acquired at the time of login reception are stored in the main ID management information 111 in association with each other.

As shown in FIG. 5, the secondary ID management device 200 includes a storage unit 210 and a control unit 220.

The storage unit 210 is a storage unit that stores data and programs necessary for various processes performed by the control unit 220. In particular, the storage unit 210 includes sub-ID management information 211 that is closely related to the present invention. The secondary ID management information 211 corresponds to “secondary ID management means” recited in the claims.

As shown in FIG. 4, the sub ID management information 211 includes a sub ID issued to uniquely identify a virtual person used by the user on the network, and the user terminal 300 that logs in using the sub ID. By sub-ID authentication data (for example, password) for authenticating a user, a main ID management device ID for specifying the main ID management device 100 connected in a communicable state, and the sub-ID management device 200 An allocation management ID for specifying the correspondence between the sub ID issued to the user and the main ID (link relationship between the sub ID and the main ID) is stored.

The correspondence between the primary ID and the secondary ID will be briefly described. As shown in FIG. 4, for example, the primary ID “aaaaaa” in the primary ID management information is changed to the secondary ID “FJS” in the secondary ID management information, It is associated with the allocation management ID “8h49i”.

The control unit 220 has a predetermined control program, a program defining various processing procedures, and an internal memory for storing necessary data, and performs various processing using these, and is particularly suitable for the present invention. As closely related, a data transmission / reception unit 221, a sub ID generation unit 222, an identity verification data generation unit 223, an allocation management ID generation unit 224, and a data registration unit 225 are provided.

The data transmission / reception unit 221 is a processing unit that transmits and receives data between the user terminal 300 and the main ID management device 100. Specifically, a sub ID issue request, a personal identification data issue request, and a sub ID transmission request are received from the user terminal 300, and a sub ID and a sub ID password generated by a sub ID generation unit 222, which will be described later, The identity verification data generated by the identity verification data generation unit 223 is transmitted to the user terminal 300.

Further, the data transmission / reception unit 221 receives an allocation management ID issue request from the main ID management device 100 and transmits an allocation management ID to the main ID management device 100.

The secondary ID generation unit 222 is a processing unit that generates a secondary ID. Specifically, when the data transmission / reception unit 221 receives a sub ID issue request from the user terminal 300, it generates a sub ID and a sub ID password.

The personal identification data generation unit 223 is a processing unit that generates personal identification data. Specifically, when the data transmission / reception unit 221 receives a personal identification data issuance request from the user terminal 300, personal identification data is generated.

The allocation management ID generation unit 224 is a processing unit that generates an allocation management ID for specifying the correspondence between the sub ID and the main ID (the link relationship between the sub ID and the main ID). Specifically, when the data transmission / reception unit 221 receives an allocation management ID issuance request from the main ID management device 100, the authentication result included in the allocation management ID issuance request proves the right owner of the main ID. When the personal identification data included in the allocation management ID issuance request matches the personal identification data transmitted to the user terminal 300, an allocation management ID is generated.

The data registration unit 225 is a processing unit that registers a sub ID, an allocation management ID, and the like. Specifically, in order to identify the secondary ID generated by the secondary ID generation unit 222, the allocation management ID generated by the allocation management ID generation unit 224, and the main ID management device 100 that is the transmission destination of the allocation management ID. Are stored in the secondary ID management information 211 in association with each other.

[Processing of ID management system (Example 1)]
Subsequently, processing of the ID management system according to the first embodiment will be described with reference to FIG. FIG. 6 is a diagram illustrating a process flow of the ID management system according to the first embodiment.

As shown in the figure, when the user terminal 300 transmits a sub ID issue request to the sub ID management apparatus 200 (step S601), the sub ID management apparatus 200 generates a sub ID and a sub ID password (step S602). ) And stored in the sub ID management information 211 (step S603).

Next, when the user terminal 300 receives and acquires the input of the main ID, the main ID password, and the main ID management device ID from the user (step S604), the user terminal 300 transmits a request for issuing personal identification data to the sub ID management device 200. (Step S605).

The secondary ID management device 200 generates identity verification data (step S606), and transmits the generated identity verification data to the user terminal 300 (step S607).

When the user terminal 300 receives the personal identification data from the secondary ID management device 200, the user terminal 300 attempts to log in to the main ID management device 100 using the main ID and the main ID password received from the user (step S608).

When the main ID management device 100 accepts the login from the user terminal 300, the main ID management device 100 checks whether or not the main ID acquired at the time of login is already registered in the main ID management information 111 (step S609). When the main ID is already registered, the main ID management device 100 acquires the main ID password stored in the main ID management information 111 in association with the main ID, and logs in the main ID at the time of login. Compared with the main ID password received together with the ID, authentication is performed as to whether or not the owner is a valid owner of the main ID (step S610).

The user terminal 300 transmits a request for assigning the main ID to the sub ID following the login to the main ID management apparatus 100 (step S611). When the main ID management device 100 receives the request for assigning the main ID to the sub-ID from the user terminal 300, the assignment management ID issuance request that combines the authentication result of the main ID and the personal identification data included in the assignment processing request. Is transmitted to the secondary ID management device 200 (step S612).

When the secondary ID management device 200 receives the allocation management ID issuance request from the main ID management device 100, the authentication result included in the allocation management ID issuance request proves the right owner of the main ID and the allocation management. It is confirmed whether or not the identity confirmation data included in the ID issuance request matches the identity confirmation data transmitted to the user terminal 300 (step S613). Then, the secondary ID management device 200 generates an allocation management ID when the personal identification data included in the allocation management ID issuance request matches the personal identification data transmitted to the user terminal 300 (step S614). .

Next, the secondary ID management device 200 identifies the allocation management ID and the primary ID management device 100 that is the transmission destination of the allocation management ID in association with the secondary ID that has been generated and registered in the secondary ID management information 211. The main ID management device ID is stored (step S615), and the allocation management ID is transmitted to the main ID management device 100 (step S616).

The primary ID management device 100 is acquired at the time of log-in reception, the allocation management ID received from the secondary ID management device 200, the secondary ID management device ID for identifying the secondary ID management device 200 that is the transmission source of the allocation management ID. The main ID is stored in the main ID management information 111 in association with each other (step S617), and a main ID assignment process completion notification is transmitted to the user terminal 300 (step S618).

When the user terminal 300 receives the main ID assignment processing completion notification from the main ID management device 100, the user terminal 300 transmits a sub ID transmission request to the sub ID management device 200 (step S619). The secondary ID management device 200 transmits the secondary ID and the secondary ID password to the user terminal 300 (step S620). The user terminal 300 notifies the user of the sub ID and the sub ID password received from the sub ID management device 200 (step S621).

[Effects of Example 1]
As described above, according to the first embodiment, the main ID management device 100 has a correspondence between the main ID, the sub ID management device ID for specifying the sub ID management device 200, and the sub ID and the main ID. The sub-ID management device 200 manages the sub-ID and the main ID management device 100 in association with the assignment management ID for specifying the ID and the personal information of the user specified by the main ID in association with each other. The ID management device ID and the allocation management ID are managed in association with each other. As described above, the main ID management apparatus 100 and the sub ID management apparatus 200 are distributed and managed, and the main ID, the sub ID, and the allocation management ID are associated with each other, thereby informing the main ID management apparatus 100 of the sub ID. In addition, necessary information can be exchanged between the devices based on the assigned management ID without notifying the secondary ID management device 200 of the primary ID, and it is assumed that the primary ID management device 100 or the secondary ID management device 200 Even if any one of the managed information is exposed, it is possible to prevent the correspondence between the primary ID and the secondary ID from being exposed.

Further, according to the first embodiment, when the main ID management device 100 authenticates that the main ID of the user who logs in to the main ID management device 100 is the main ID of a valid user, the secondary ID management device 200 Since the sub ID is provided and assigned to the main ID in response to a request from the user, the anonymity of the main ID and the sub ID can be maintained and the sub ID can be issued on condition that the main ID exists. There is an effect. In addition, when a problem occurs in providing a service using the sub-ID, there is an effect that the responsibility corresponding to the user corresponding to the main ID can be pursued as necessary.

The issuing procedure of the sub ID of the ID management system according to the present invention is not limited to the issuing procedure (see FIG. 6) described in the first embodiment. Therefore, in the following second embodiment, another form of the sub ID issuing procedure will be described.

[Configuration of ID management system (second embodiment)]
First, the configuration of the ID management system according to the second embodiment will be described with reference to FIG. FIG. 7 is a block diagram illustrating the configuration of the secondary ID management apparatus according to the second embodiment. The configuration of the ID management system according to the second embodiment is basically the same as that of the ID management system according to the first embodiment, but differs in the points described below.

That is, when the owner confirmation unit 122 of the main ID management device 100 accepts login from the sub ID management device 200, the encryption main ID acquired at the time of login is a secret key corresponding to the public key used for encryption. The main ID is obtained by decryption, and it is confirmed whether or not this main ID is already registered in the main ID management information 111.

Next, when the main ID is already registered, the owner confirmation unit 122 of the main ID management device 100 stores the main ID password stored in the main ID management information 111 in association with the main ID. And authenticate whether or not it is a legitimate owner of the main ID by comparing the main ID password obtained by decrypting the encrypted main ID password received with the encryption main ID at the time of login with a secret key. Do.

Then, the data transmission / reception unit 121 of the main ID management device 100 transmits an allocation management ID issuance request including the authentication result of the main ID by the owner confirmation unit 122 to the sub ID management device 200. In addition, when the registration by the data registration unit 123 is completed, the data transmission / reception unit 121 of the main ID management apparatus 100 transmits a main ID assignment process completion notification to the sub ID management apparatus 200.

Further, as shown in FIG. 7, the main ID authentication request unit 226 of the sub ID management device 200 uses the data transmission / reception unit 221 to transfer the sub ID to the sub ID together with the main ID management device ID, the encryption main ID, and the encryption main ID password. When the main ID assignment processing request is received from the user terminal 300, login to the main ID management device 100 is attempted using the encryption main ID and the encryption main ID password.

When the allocation management ID generation unit 224 of the secondary ID management device 200 receives the allocation management ID issuance request from the main ID management device 100, the authentication result included in the allocation management ID issuance request proves the right owner of the main ID. If it is, an allocation management ID is generated.

When the data transmission / reception unit 221 of the secondary ID management device 200 receives the main ID assignment processing completion notification from the main ID management device 100, it transfers the main ID assignment processing completion notification to the user terminal 300.

Further, the process described below can be added to the process described above to configure the ID management system according to the second embodiment.

That is, the owner confirmation unit 122 of the main ID management device 100 generates confirmation data (challenge data) and transmits it to the sub ID management device 200 when the main ID is already registered.

When the owner confirmation unit 122 of the main ID management device 100 receives the encryption confirmation data from the sub ID management device 200, the owner confirmation unit 122 associates the main ID management information 111 with the main ID that has been confirmed as being registered first. Obtain the stored main ID password, compare the encryption confirmation data created by encrypting the confirmation data using the main ID password, and the encryption confirmation data received from the secondary ID management device 200, Authentication is performed as to whether or not the owner of the main ID is valid.

Also, the main ID authentication request unit 226 of the secondary ID management device 200 receives a request for assigning a primary ID to the secondary ID from the user terminal 300 together with the primary ID management device ID and the encryption main ID by the data transmission / reception unit 221. Then, login to the main ID management device 100 is attempted using the encryption main ID.

When the data transmission / reception unit 221 of the secondary ID management device 200 receives the confirmation data from the main ID management device 100, the data transmission / reception unit 221 transfers the received confirmation data to the user terminal 300 and receives the encryption confirmation data from the user terminal 300. The confirmation data is transferred to the main ID management device 100.

[Processing of ID management system (second embodiment)]
Hereinafter, processing of the ID management system according to the second embodiment will be described with reference to FIGS. 8 and 9. 8 and 9 are diagrams illustrating a process flow of the ID management system according to the second embodiment.

First, the processing of the ID management system according to the second embodiment will be described with reference to FIG. Steps S804 to S815, steps S819, and S820 shown in FIG. 8 are different from the processing of the ID management system according to the first embodiment.

That is, when the user terminal 300 receives input of the main ID, the main ID password, and the main ID management device ID from the user (step S804), the user terminal 300 acquires the public key of the main ID management device 100 (step S805). The main ID is encrypted using the key to create an encrypted main ID (step S806).

Similarly, the user terminal 300 encrypts the main ID password using the public key of the main ID management device 100 to create an encrypted main ID password (step S807), and the main ID management device ID, encryption main ID, and encryption Along with the main ID password, a request for assigning the main ID to the sub ID is transmitted to the sub ID management apparatus 200 (step S808).

When the secondary ID management device 200 receives a request for assigning the primary ID to the secondary ID together with the primary ID management device ID, the cryptographic primary ID, and the cryptographic primary ID password from the user terminal 300, the secondary ID management device 200 uses the cryptographic primary ID and the cryptographic primary ID. A login to the main ID management device 100 is attempted using the password (step S809).

When receiving the login from the secondary ID management device 200, the main ID management device 100 acquires the main ID by decrypting the encryption main ID acquired at the time of login with the private key corresponding to the public key used for encryption. (Step S810), it is confirmed whether or not the main ID is already registered in the main ID management information 111 (Step S811).

Next, when the main ID is already registered, the main ID management device 100 decrypts the encryption main ID password received together with the encryption main ID at the time of login with the secret key, and obtains the main ID password. Whether it is a legitimate owner of the main ID as compared with the main ID password stored in the main ID management information 111 in association with the main ID acquired (step S812) and confirmed as registered No authentication is performed (step S813).

Then, the main ID management device 100 transmits an allocation management ID issue request including the authentication result of the main ID to the sub ID management device 200 (step S814).

When the secondary ID management device 200 receives the allocation management ID issuance request from the main ID management device 100, if the authentication result included in the allocation management ID issuance request proves the legitimate owner of the main ID, An allocation management ID is generated (step S815).

When the registration of the main ID, the allocation management ID, and the like is completed, the main ID management apparatus 100 transmits a main ID allocation process completion notification to the secondary ID management apparatus 200 (step S819).

Upon receiving the main ID assignment process completion notification from the main ID management apparatus 100, the secondary ID management apparatus 200 transfers the main ID assignment process completion notice to the user terminal 300 (step S820).

Further, the processing of the ID management system shown in FIG. 9 is different from the processing described above with reference to FIG. 8 in the points described below.

That is, the user terminal 300 encrypts the main ID using the public key of the main ID management device 100 to create an encrypted main ID (step S906), and sends the sub ID to the sub ID together with the main ID management device ID and the encryption main ID. The main ID assignment processing request is transmitted to the sub ID management device 200 (step S907).

When the secondary ID management device 200 receives a request for assigning a primary ID to the secondary ID together with the primary ID management device ID and the encryption main ID from the user terminal 300, the secondary ID management device 200 attempts to log in to the primary ID management device 100 using the encryption main ID. (Step S908).

When the main ID is already registered, the main ID management device 100 generates confirmation data (challenge data) and transmits it to the sub ID management device 200 (step S912).

When the sub ID management device 200 receives the confirmation data from the main ID management device 100, the sub ID management device 200 transfers the received confirmation data to the user terminal 300 (step S913).

When the user terminal 300 receives the confirmation data from the secondary ID management apparatus 200, the user terminal 300 encrypts the confirmation data using the main ID password and creates encrypted confirmation data (step S914). Then, the user terminal 300 transmits the encryption confirmation data to the sub ID management device 200 (step S915). When receiving the encryption confirmation data from the user terminal 300, the secondary ID management device 200 transfers the received encryption confirmation data to the main ID management device 100 (step S916).

When the primary ID management device 100 receives the encryption confirmation data from the secondary ID management device 200, the primary ID password stored in the primary ID management information 111 in association with the primary ID that has been previously confirmed as registered. And the encryption confirmation data created by encrypting the confirmation data using the main ID password is compared with the encryption confirmation data received from the sub-ID management device 200, and the authorized owner of the main ID Authentication of whether or not there is is performed (step S917).

In the above-described embodiment, the case where information of a single primary ID management device is managed in the secondary ID management information has been described. However, the present invention is not limited to this and is separately provided for each type of personal information of the user. Information of a plurality of main ID management devices that hold the personal information may be managed respectively. Thus, in the following third embodiment, the features, configuration, and processing of the ID management system according to the third embodiment will be described in order.

[Characteristics of ID management system (Example 3)]
First, the features of the ID management system according to the third embodiment will be described with reference to FIG. FIG. 10 is a diagram for explaining the features of the ID management system according to the third embodiment.

The ID management system according to the third embodiment outlines the management of the main ID and the sub ID issued in response to a request from the user, as in the above-described embodiment, but for each type of personal information of the user. The main feature is that each piece of information of a plurality of main ID management devices having separate personal information is managed.

Specifically, as shown in FIG. 10, in response to one of the user's personal information (for example, money-related information used for settlement processing such as account information and non-life insurance information) and a request from the user The main ID management device A (main ID management device ID: 0020) that manages the issued main ID (for example, “aaaaaa”) in association with each other, and a user that is different from the one managed by the main ID management device A A main ID management apparatus B (for example, information that supports logistics such as address and family register information) and a main ID (for example, “kx010”) issued in response to a request from the user are associated with each other. For each of the primary ID management device ID: 3350), the secondary ID management device S manages information.

That is, the secondary ID management device S has a secondary ID (for example, “FJS”) issued in response to a request from the user and a primary ID (for example, “aaaaaa”) issued by the primary ID management device A to the user. When the main ID management device B is issued by being assigned to a main ID (for example, “kx010”) issued to the user, the main ID management device ID “0020” and the assignment of the main ID management device A The management ID “8h49i”, the main ID management device ID “3350” and the allocation management ID “00230” of the main ID management device B are managed together.

In this way, by managing by assigning a plurality of main IDs to one sub-ID, in the process executed by receiving login from the user by the sub-ID, the main information managing personal information associated with the process is managed. It is possible to exchange with the ID management device individually.

[Configuration of ID management system (Example 3)]
Next, the configuration of the ID management system according to the third embodiment will be described with reference to FIGS. 11 and 12. FIG. 11 is a diagram illustrating a system configuration of the ID management system according to the third embodiment. FIG. 12 is a diagram illustrating a configuration example of main ID management information and sub ID management information according to the third embodiment. The ID management system according to the third embodiment has basically the same configuration as the above-described embodiment, but differs in the points described below.

That is, as illustrated in FIG. 11, the ID management system according to the third embodiment includes a user terminal 300 used by a user and a plurality of main IDs that manage a main ID that issues a main ID for uniquely identifying the user. The management apparatus 100 includes a secondary ID management apparatus 200 that issues a secondary ID for uniquely identifying a virtual person used by a user on the network. In addition, the user terminal 300, each main ID management device 100, and the sub ID management device 200 are connected to each other so that they can communicate with each other via a network, and each main ID management device 100 and each sub ID management device 200 are connected. Are connected to each other so that they can communicate with each other via a network.

In addition, as shown in FIG. 12, the sub ID management information 211 includes a sub ID issued to uniquely identify a virtual person used by the user on the network, and a user terminal that logs in using the sub ID. Sub ID authentication data (for example, a password) for authenticating 300 users, a main ID management device ID for identifying each main ID management device 100 connected in a communicable state, and sub ID management The apparatus 200 is configured to store an allocation management ID for specifying a correspondence relationship (link relationship between the sub ID and the main ID) between the sub ID issued to the user by the device 200 and the main ID.

[Processing of ID management system (Example 3)]
Subsequently, processing of the ID management system according to the third embodiment will be described with reference to FIGS. FIGS. 13 to 15 are flowcharts illustrating the processing flow of the ID management system according to the third embodiment.

First, an embodiment of processing of the ID management system according to the third embodiment will be described with reference to FIG. The process shown in FIG. 13 differs from the process described with reference to FIG. 6 in the above embodiment in the following points.

That is, when the user terminal 300 receives the assignment processing completion notification from the main ID management device 100 (see A in FIG. 13), it confirms whether or not acquisition of all the main IDs to be assigned to the sub-IDs has been completed. (Step S1304).

If all the main IDs have been acquired as a result of the confirmation (Yes in step S1305, see B in FIG. 13), the user terminal 300 transmits a sub ID transmission request to the sub ID management device 200. (Step S1321), the process flows in the same manner as the process described in the above embodiment (see FIG. 6).

On the other hand, if all the main IDs have not been acquired as a result of the confirmation (No at step S1305), the main ID, the main ID password and the main ID management device ID of the next main ID management device 100 are input. After being received and acquired from the user (step S1306), an identity verification data issuance request is transmitted to the secondary ID management device 200 (step S1307), and the process is the same as the process described in the above embodiment (see FIG. 6). Flowing.

Next, an embodiment of processing of the ID management system according to the third embodiment will be described with reference to FIG. The process shown in FIG. 14 differs from the process described with reference to FIG. 8 in the above embodiment in the following points.

That is, when the user terminal 300 receives the allocation process completion notification from the secondary ID management device 200 (see A in FIG. 14), it confirms whether or not acquisition of all the primary IDs to be allocated to the secondary ID has been completed. (Step S1404).

If all the main IDs have been acquired as a result of the confirmation (Yes in step S1405, see B in FIG. 13), the user terminal 300 transmits a sub ID transmission request to the sub ID management device 200. (Step S1423), the process flows in the same manner as the process described in the above embodiment (see FIG. 8).

On the other hand, if all the main IDs have not been acquired as a result of the confirmation (No at step S1404), the next main ID, main ID password, and main ID management device ID are input. After receiving and acquiring from the user (step S1406), the public key of the main ID management apparatus 100 is acquired (step S1407), and the main ID is encrypted using this public key to create an encrypted main ID (step S1408). The process flows in the same manner as the process described in the above embodiment (see FIG. 8).

Subsequently, an embodiment of processing of the ID management system according to the third embodiment will be described with reference to FIG. The process shown in FIG. 15 differs from the process described with reference to FIG. 9 in the above embodiment in the following points.

That is, when the user terminal 300 receives the allocation process completion notification from the secondary ID management device 200 (see A in FIG. 15), it confirms whether or not acquisition of all the primary IDs to be allocated to the secondary ID has been completed. (Step S1504).

If all the main IDs have been acquired as a result of the confirmation (Yes at step S1505, see FIG. 15B), the user terminal 300 sends a sub ID transmission request to the sub ID management device 200. (Step S1527), the process flows in the same manner as the process described in the above embodiment (see FIG. 9).

On the other hand, if acquisition of all the main IDs is not completed as a result of the confirmation (No at step S1505), input of the main ID, main ID password, and main ID management device ID of the next main ID management device 100 is performed. After receiving and acquiring from the user (step S1506), the public key of the main ID management apparatus 100 is acquired (step S1507), and the main ID is encrypted using this public key to create an encrypted main ID (step S1508). The process flows in the same manner as the process described in the above embodiment (see FIG. 9).

In the following embodiment 4, as described in the above embodiment with reference to FIG. 16, after the main ID and the sub ID are managed in each device, the ID management when the user actually uses the service is performed. An overview of system processing will be described. FIG. 16 is a diagram illustrating an overview of an ID management system according to the fourth embodiment.

As shown in the figure, the ID management system according to the fourth embodiment includes a user terminal X, a user terminal Y, a real person management apparatus A (corresponding to the main ID management apparatus described in the above embodiment), virtual person management. A device (corresponding to the sub ID management device described in the above embodiment), a real person management device B (corresponding to the main ID management device described in the above embodiment), and a plurality of service providing devices (job search site, SNS (Social Networking Service), shopping site).

The user terminal X is connected in a communicable state with the real person management apparatus A, the virtual person management apparatus, and each service providing apparatus, and the user terminal Y is connected to the real person management apparatus B, the virtual person management apparatus, and each service providing apparatus. Connected in a communicable state.

The user X of the user terminal X obtains the real person ID (corresponding to the main ID) “XX” from the real person management apparatus A, and the virtual person ID (sub ID) that is a virtual personality when using the service from the virtual person management apparatus. Equivalent to) “x11” is acquired. The user Y of the user terminal Y acquires the real person ID “YY” from the real person management apparatus B and also acquires the virtual person ID “y22” from the virtual person management apparatus.

The real person management apparatus A associates the personal information of the user X, the real person ID “XX” issued to the user X, and the real person ID “XX” and the virtual person ID managed by the virtual person management apparatus. The allocation management ID “10kx” is managed in association with each other. The real person management apparatus B associates the personal information of the user Y, the real person ID “YY” issued to the user Y, and the real person ID “YY” with the virtual person ID managed by the virtual person management apparatus. Are associated with the management ID “yh2k”.

The virtual person management apparatus issues a virtual person ID “x11” issued to the user X, and an assignment management ID “10 kx” for associating the virtual person ID “x11” with the real person ID managed by the real person management apparatus A. , And the real person management apparatus ID for specifying the real person management apparatus A that manages the real person ID associated with the virtual person ID “x11” is managed in association with the virtual person ID “y22” issued to the user Y. ”, The allocation management ID“ yh2k ”for associating the virtual person ID“ y22 ”with the real person ID managed by the real person management apparatus B, and the real person ID associated with the virtual person ID“ y22 ”. The real person management apparatus ID for identifying the real person management apparatus B to be managed is associated and managed.

Then, the user X and the user Y use the virtual person ID “x11” and the virtual person ID “y22” acquired from the virtual person management apparatus to access and operate each service providing apparatus. In addition, the user X and the user Y can use the virtual person ID to act on the service providing apparatus without disclosing personal information.

In the following, as an example of processing at the time of service use by the service providing apparatus, each of the user X and the user Y accesses the service providing apparatus (SNS) using the virtual person ID, and the virtual person ID “x11” and the virtual person An outline of processing when the virtual person ID “y22” who is the user Y meets the person ID “y22” and transmits the mail to the virtual person ID “x11” which is the user X will be described.

User Y transmits the mail and the mail transmission request to the virtual person management apparatus in order to request the transmission of the mail having the virtual person ID “y22” as the sender and the virtual person ID “x11” as the destination.

When receiving the mail transmission request from the user terminal Y, the virtual person management apparatus manages the real person ID associated with the virtual person ID “x11” that is the destination of the mail from the managed information. A real person management device ID for identifying A, a virtual person ID “x11”, and an assignment management ID “10 kx” for associating the real person ID managed by the real person management device A are acquired, The real person management apparatus A corresponding to the real person management apparatus ID is requested to send the mail received from the user Y to the user corresponding to the assignment management ID “10 kx”.

When the real person management apparatus A receives the mail transmission request from the virtual person management apparatus, the real person management apparatus A acquires the mail address of the user X corresponding to the assignment management ID “10 kx” that is the destination of the mail from the managed information. , Forward the mail to this mail address. In this way, mail can be exchanged between the virtual person ID “x11” and the virtual person ID “y22” that are met on the service providing device (SNS) while keeping private information confidential.

Further, as another example of processing at the time of service use by the service providing apparatus, the service providing apparatus (shopping site) performs an article sales transaction between the virtual person ID “x11” and the virtual person “y22”. An outline of the processing when sending the price from “y22” to “x11” will be described.

In this case, the user Y transmits the price and the remittance request to the virtual person management apparatus in order to request the remittance of the price with “y22” as the remittance source and “x11” as the remittance destination.

The virtual person management apparatus, like the above-described mail transfer example, from the managed information, the real person management apparatus A and the allocation management ID “10 kx” of the real person management apparatus A corresponding to the remittance destination “x11”. And requests the real person management apparatus A to remit money from the user Y to the user corresponding to the allocation management ID “10 kx”.

The real person management apparatus A acquires the account number of the user X corresponding to the allocation management ID “10 kx” as the remittance destination from the information managed as in the mail transfer example described above, and this account number Send money to.

As described above, the real person ID and the virtual person ID are linked by the allocation management ID, and the real person ID, the personal information, and the virtual person ID are managed in a distributed manner, and exchange of information necessary when using the service While maintaining the function to perform the management, even if one of the information managed by the real person management apparatus and the virtual person management apparatus leaks, the correspondence relationship between the virtual person and the real person can be prevented from being exposed to the outside. Therefore, it is possible to prevent the personal information of the user who uses the service from being identified using the virtual person ID and leaked to the outside.

Now, various examples have been described as one embodiment for carrying out the present invention, but the present invention may be implemented in various different forms other than the above-described examples. Therefore, in the following, another example will be described as an embodiment for carrying out the present invention.

(1) Device Configuration etc. For example, each component of the main ID management device 100 shown in FIG. 3 and the sub ID management device shown in FIG. 5 is functionally conceptual, and is not necessarily physically configured as shown. You don't need to be. That is, the specific form of distribution / integration of the main ID management device 100 and the sub ID management device 200 is not limited to the illustrated one, and the data transmission / reception unit 121 and the owner confirmation unit 122 of the main ID management device 100 shown in FIG. And the data registration unit 123, and the data transmission / reception unit 221, the sub ID generation unit 222, the personal identification data generation unit 223, and the allocation management ID generation unit 224 of the sub ID management device 200 shown in FIG. For example, all or a part of them may be integrated and functionally or physically distributed and integrated in arbitrary units according to various loads and usage conditions.

Furthermore, each processing function (FIGS. 6, 8, and 13, 13 to 15) performed in the main ID management device 100 and the sub ID management device 200 is entirely or arbitrarily part of the CPU and the It can be realized by a program that is analyzed and executed by the CPU.

The computer functioning as the primary ID management device 100 and the secondary ID management device 200 reads out and executes a program recorded in a predetermined recording medium, thereby executing each processing function similar to the above-described embodiment (FIGS. 6 and 6). 8 and FIG. 9 and FIGS. 13 to 15). Here, the predetermined recording medium includes the main ID management apparatus 100 in addition to “portable physical medium” such as a flexible disk (FD), a CD-ROM, an MO disk, a DVD disk, a magneto-optical disk, and an IC card. And a hard disk drive (HDD) provided inside and outside the computer functioning as the sub-ID management device 200, a “fixed physical medium” such as RAM and ROM, a public line connected via a modem, and the like It can be read by a computer functioning as the primary ID management device 100 and the secondary ID management device 200 such as a “communication medium” that holds the program in a short time when transmitting the program, such as a LAN / WAN to which a computer system and server are connected. Including all types of recording media for recording various programs

That is, the program referred to in the other embodiments is recorded on a recording medium such as the above-mentioned “portable physical medium”, “fixed physical medium”, and “communication medium” in a computer-readable manner. The computer functioning as the primary ID management device 100 and the secondary ID management device 200 reads out the program from such a recording medium and executes it to execute each processing function similar to the above-described embodiment (FIGS. 6, 8, and FIG. 9 and FIGS. 13 to 15). Note that the program in this other embodiment is not limited to being executed by a computer functioning as the primary ID management device 100 and the secondary ID management device 200, but is executed by another computer system or server. The present invention can be similarly applied to the case where the programs are executed in cooperation with each other.

(2) ID management method Moreover, the following ID management method is implement | achieved by the ID management system demonstrated in said Example.

For example, the secondary ID management device 200 receives a secondary ID issue request from a user terminal used by the user, a secondary ID generation step for generating a secondary ID, and a user of the user terminal that requests login by the primary ID, The main ID management device that manages the main ID to be associated with the sub ID generated by the sub ID generation step as to whether or not the user of the user terminal that is the transmission source of the sub ID issuance request is the same person The same person confirmation step that confirms in cooperation with the user, the user of the user terminal that requests the login request, and the user of the user terminal that is the transmission source of the sub ID issue request are the same person When confirmed by the step, the pair of the sub ID generated by the sub ID generation step and the main ID to be associated with the sub ID An allocation management ID generation step for generating an allocation management ID indicating a relationship, and the allocation management ID generated by the allocation management ID generation step are transmitted to a main ID management device that manages a main ID to be associated with the sub ID. An assignment management ID transmission step; a sub ID generated by the sub ID generation step; a main ID management device ID for specifying a main ID management device that manages a main ID to be associated with the sub ID; When the sub ID allocation management information recording step for recording the allocation management ID generated in association with the management ID generation step in association with the sub ID allocation management information recording step is completed, A sub ID transmission step of transmitting the sub ID generated by the sub ID generation step to the user terminal as the transmission source; The main ID management device further includes an allocation management ID receiving step for receiving an allocation management ID from the sub ID management device, an allocation management ID received by the allocation management ID receiving step, and transmission of the allocation management ID An ID management method including a main ID assignment management information recording step of recording a sub ID management device ID for specifying the original sub ID management device in association with a main ID that has requested login is realized. To do.

In the above embodiment, the manager of the main ID management device 100 and the manager of the sub-ID management device 200 exchange allocation management IDs according to a request from the user by mail or the like. The management apparatus 100 pre-registers the main ID, the allocation management ID, and personal information in association with each other, the sub-ID management apparatus 200 associates the sub-ID and the allocation management ID in advance with registration management, and has static information. After that, the primary ID management device 100 and the secondary ID management device 200 may be caused to execute processing accompanying a service request to the service providing device.

As described above, the ID management system and the ID management method according to the present invention are useful for managing the primary ID and the secondary ID issued in response to a request from the user, and in particular, between different types of IDs having different uses. It is suitable for preventing the correspondence relationship from being exposed.

Claims (6)

1. A user terminal used by a user, a main ID management device that manages a main ID for identifying the user for the first use, and a sub ID for identifying the user for the second use An ID management system including a sub-ID management device,
   The main ID management device associates a main ID, a sub ID management device ID for specifying the sub ID management device, and an allocation management ID for specifying a correspondence relationship between the sub ID and the main ID. A main ID management means for managing,
   The secondary ID management device includes secondary ID management means for managing a secondary ID, a primary ID management device ID for specifying the primary ID management device, and an allocation management ID in association with each other. ID management system.
2. The ID management system according to claim 1, wherein the secondary ID management means manages a primary ID management device ID and an allocation management ID that are different for each primary ID management device in association with the secondary ID.
3. The secondary ID management device
   A sub ID generating means for generating a sub ID when a sub ID issuance request is received from the user terminal;
   The sub-ID generated by the sub-ID generation means determines whether or not the user of the user terminal that requests login by the main ID and the user of the user terminal that is the transmission source of the sub-ID issue request are the same person. The same person confirmation means for confirming in cooperation with a main ID management device that manages a main ID to be associated;
   When the same person confirmation means confirms that the user of the user terminal requesting the login request and the user of the user terminal that is the transmission source of the sub ID issue request are the sub ID, An allocation management ID generating unit that generates an allocation management ID indicating a correspondence relationship between the sub ID generated by the generating unit and the main ID to be associated with the sub ID;
   An allocation management ID transmission unit that transmits the allocation management ID generated by the allocation management ID generation unit to a main ID management device that manages a main ID to be associated with the sub-ID;
   The sub ID generated by the sub ID generation means, the main ID management apparatus ID for specifying the main ID management apparatus that manages the main ID to be associated with the sub ID, and the allocation management ID generation means Sub ID allocation management information recording means for recording the allocation management ID in association with each other;
   Sub-ID transmission for transmitting the sub-ID generated by the sub-ID generation unit to the user terminal that is the transmission source of the sub-ID issue request when the recording by the sub-ID allocation management information recording unit is completed Means,
   Further comprising
   The main ID management device
   An allocation management ID receiving means for receiving an allocation management ID from the secondary ID management device;
   The allocation management ID received by the allocation management ID receiving means, the secondary ID management device ID for identifying the secondary ID management device that is the transmission source of the allocation management ID, and the main ID that requested the login are associated with each other 2. The ID management system according to claim 1, further comprising main ID allocation management information recording means for recording.
4. An ID management method for issuing and managing a primary ID for identifying a user for a first use, and issuing and managing a sub ID for identifying a user for a second use ,
   The main ID management device that manages the main ID is for specifying the correspondence between the main ID, the sub ID management device ID for specifying the sub ID management device that manages the sub ID, and the sub ID and the main ID. Including a main ID management step for causing the main ID management device to manage the association with the allocation management ID,
   The secondary ID management device that manages the secondary ID manages the secondary ID, the primary ID management device ID for specifying the primary ID management device that manages the primary ID, and the allocation management ID in association with each other and manages the secondary ID management device. An ID management method characterized by including a sub-ID management step.
5. 5. The ID management method according to claim 4, wherein the sub ID management step manages a main ID management device ID and an allocation management ID that are different for each main ID management device in association with the sub ID.
6. The secondary ID management device
   A sub ID generation step for generating a sub ID when a sub ID issuance request is received from a user terminal used by the user;
   Whether the user of the user terminal that requests login by the main ID and the user of the user terminal that is the transmission source of the sub ID issue request are the same person, the sub ID generated by the sub ID generation step The same person confirmation step of confirming in cooperation with a main ID management device that manages a main ID to be associated;
   When it is confirmed by the same person confirmation step that the user of the user terminal that requests the login request and the user of the user terminal that is the transmission source of the sub ID issue request are the same person ID, An allocation management ID generation step for generating an allocation management ID indicating a correspondence relationship between the sub-ID generated by the generation step and the main ID to be associated with the sub-ID;
   An allocation management ID transmission step of transmitting the allocation management ID generated by the allocation management ID generation step to a main ID management device that manages a main ID to be associated with the sub-ID;
   The sub ID generated by the sub ID generation step, the main ID management device ID for specifying the main ID management device that manages the main ID to be associated with the sub ID, and the allocation management ID generation step A sub ID assignment management information recording step for recording the assigned management ID in association with each other;
   Sub-ID transmission for transmitting the sub-ID generated by the sub-ID generation step to the user terminal that is the transmission source of the sub-ID issue request when the recording by the sub-ID allocation management information recording step is completed Steps,
   Further including
   The main ID management device
   An allocation management ID receiving step of receiving an allocation management ID from the secondary ID management device;
   The allocation management ID received in the allocation management ID receiving step is associated with the secondary ID management device ID for specifying the secondary ID management device that is the transmission source of the allocation management ID, and the main ID that requested the login. Main ID assignment management information recording step for recording,
   The ID management method according to claim 4, further comprising:

Images