JP2013097441A - Distribution id management method and distribution id management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable interconversion of identifiers that can obtain a different value due to date and time, and a domain even though associated with the same management object and to enable scale-out after suppressing a data amount to be managed.SOLUTION: A data management device 3 of a distribution ID management system manages data including an identifier, a domain and date and time by using two types of keys: an index key (combination of identifier and domain) and a sub route key (combination of route key and domain). When receiving an ID conversion request from a client device 1, a gateway device 2 determines a data management device 3(3A) for retrieving a route key by using an index key. Then, the data management device 3(3A) determines a data management device 3(3D) for retrieving an identifier of a conversion destination by using a sub route key, acquires the identifier of the conversion destination from the data management device 3(3D), and returns the identifier to the client device 1.

Description

  The present invention relates to a distributed ID management method and a distributed ID management system.

  When managing articles, people, or data related to them in an information system, management is often automated and efficient by using a code that can uniquely identify a management target, that is, an ID (Identification). . For example, books have a universal number called ISBN (International Standard Book Number), and using that number makes it possible to specify only one book in the world. ing. Also, in some countries / regions, by assigning identifiers such as taxpayer IDs or resident numbers to individuals in the country / region, the relationship between the data associated with each individual and the individual can be uniquely identified. And the efficient operation of tax and social security systems.

  In general, an identifier assigned to a management target (article or person) can take a different value depending on a range to be used (hereinafter referred to as “domain”) and time. For example, for a certain management object, the management object managed with the identifier “0” at the factory A as of March 2009 is changed to the identifier “a” at the factory B as of June 2010. There may be situations managed by In this case, if it is understood that both identifiers point to the same management target and both identifiers can be converted to each other as necessary, efficient management across time and domains is possible. Become. In order to maintain the consistency of the management system, the identifier update (for example, the identifier at the factory A is updated to “9” after September 2011) can be grasped and reflected in the mutual conversion. Is desirable.

  In order to realize the mutual conversion and update processing as described above, a database in which values (identifiers) are associated with each point in the three-dimensional space (managed object, domain, time) is constructed, and data registration / conversion / It is necessary to provide an update interface. This database is relatively easy to implement using a relational database if the number of managed objects, the number of domains, and the update frequency of identifiers are known in advance. Using a relational database may not always be optimal because it is difficult to determine size and hardware performance requirements. Under these circumstances, a distributed data management system that can satisfy the required capacity and performance requirements (scaling out) simply by adding one or more devices after the service is started is used. There are many.

  As an example of a distributed data management system that can be scaled out, a method that applies a method called consistent hashing (consistent hash method) is known (see, for example, Patent Document 1).

JP 2010-74604 A

  However, in the technique described in Patent Document 1, distributed management of data is realized based on a data name (key), but based on information (date / time / domain / identifier etc.) included in the distributed data. It does not have a function to identify efficiently. For example, as described above, with respect to a certain management target (article or person), as of March 2009, the management target managed with the identifier “0” at the factory A is as of June 2010. In a situation where the factory B manages the identifier “a”, the conversion source identifier (for example, “0”), the conversion source domain (for example, the A factory), and the conversion source date and time (for example, (March 2009), the conversion destination domain (for example, factory B), the conversion destination date and time (for example, June 2010), and the conversion destination identifier (in this case, “a”) When realizing a process that obtains the conversion source ID, conversion source domain, conversion source date and time, conversion destination domain, conversion destination date and time as a data name (key), a method of storing the conversion destination ID in the data Is possible by using. However, when such a configuration is adopted, there is a problem that the amount of data to be stored in the data management system and the amount of data that needs to be rewritten when the ID is updated increase. In addition, when the time interval is wide, for example, in units of months or days, it is relatively easy to construct the data name as described above, but when the interval is small, for example, in minutes or seconds In such a case, there is a problem that the amount of data to be managed becomes enormous.

  The present invention has been made in view of such a background, and the present invention enables and manages mutual conversion between identifiers that are associated with the same management target but can take different values depending on the date and domain. It is an object of the present invention to provide a distributed ID management method and a distributed ID management system that can be scaled out while suppressing the amount of data to be processed.

  The data management apparatus in the distributed ID management system of the present invention uses two types of keys, an index key (a set of identifier and domain) and a sub-root key (a set of root key and domain), for data including an identifier, a domain, and a date and time. Manage. Then, when receiving the ID conversion request from the client device, the gateway device uses the index key to determine the data management device that holds the route key from among the plurality of data management devices. Then, the data management device uses the sub-root key to determine another data management device that holds the conversion destination identifier, acquires the conversion destination identifier from the other data management device, and passes through the gateway device. Then, a message including the identifier of the conversion destination is transmitted to the client device.

  According to the present invention, although it is associated with the same management target, it is possible to perform mutual conversion between identifiers that can take different values depending on the date and time and domain, and it is possible to scale out while suppressing the amount of data to be managed A distributed ID management method and a distributed ID management system can be provided.

It is a figure for demonstrating the example of a whole structure of the distributed ID management system which concerns on this embodiment. It is a functional block diagram which shows the structural example of the client apparatus which concerns on this embodiment. It is a functional block diagram which shows the structural example of the gateway apparatus which concerns on this embodiment. It is a figure for demonstrating the determination process of the node used as the data distribution destination which the node determination part which concerns on this embodiment performs. FIG. 4A is a diagram illustrating an example of a data configuration of node information stored in the node information storage area according to the present embodiment. FIG. 4B is a diagram for explaining the data distribution destination determination process by the node determination unit according to the present embodiment. It is a functional block diagram which shows the structural example of the data management apparatus which concerns on this embodiment. It is a hardware block diagram of each apparatus (a client apparatus, a gateway apparatus, a data management apparatus) which concerns on this embodiment. It is a sequence diagram which shows the flow of the whole ID registration process which the distributed ID management system which concerns on this embodiment performs. It is a figure which shows the example of a message transmitted / received by the ID registration process which the data management system which concerns on this embodiment performs. It is a figure which shows the example of the index and route information which are memorize | stored in the data storage area of the data management apparatus which concerns on this embodiment. It is a flowchart which shows the flow of a process of the gateway apparatus in the ID registration process which concerns on this embodiment. It is a flowchart which shows the flow of the node determination process which concerns on this embodiment. It is a flowchart which shows the flow of a process of the charge node (data management apparatus A) in the ID registration process which concerns on this embodiment. It is a flowchart which shows the flow of a process of the charge node (data management apparatus A) in the ID registration process which concerns on this embodiment. It is a flowchart which shows the flow of a process of the data management apparatus in the index preservation | save process which concerns on this embodiment. It is a flowchart which shows the flow of a process of the data management apparatus in the route information preservation | save process which concerns on this embodiment. It is a sequence diagram which shows the whole flow of the ID conversion process which the distributed ID management system which concerns on this embodiment performs. It is a figure which shows the example of a message transmitted / received by the ID conversion process which the data management system which concerns on this embodiment performs. It is a flowchart which shows the flow of a process of the gateway apparatus in the ID conversion process which concerns on this embodiment. It is a flowchart which shows the flow of a process of the data management apparatus A in the ID conversion process which concerns on this embodiment. It is a flowchart which shows the flow of a process of the data management apparatus D in the ID acquisition process which concerns on this embodiment. It is a sequence diagram which shows the whole flow of the ID update process which the distributed ID management system which concerns on this embodiment performs. It is a figure which shows the example of a message transmitted / received by the ID update process which the data management system which concerns on this embodiment performs. It is a figure which shows the example of the index and route information which are memorize | stored in the data storage area after ID update process of the data management apparatus which concerns on this embodiment. It is a flowchart which shows the flow of a process of the gateway apparatus in the ID update process which concerns on this embodiment. It is a flowchart which shows the flow of a process of the data management apparatus A in the ID update process which concerns on this embodiment. It is a flowchart which shows the flow of a process of the data management apparatus A in the ID update process which concerns on this embodiment. It is a flowchart which shows the flow of the route information update process of the data management apparatus B in the ID update process which concerns on this embodiment. It is a sequence diagram which shows the whole flow of ID conversion process (1) after the ID update process which the distributed ID management system which concerns on this embodiment performs. It is a figure which shows the example of a message transmitted / received by ID conversion process (1) after ID update process which the data management system which concerns on this embodiment performs. It is a sequence diagram which shows the whole flow (2) of the ID conversion process after the ID update process which the distributed ID management system which concerns on this embodiment performs. It is a figure which shows the example of a message transmitted / received by ID conversion process (2) after ID update process which the data management system which concerns on this embodiment performs. It is a sequence diagram which shows the whole flow of the ID conversion process (failure example) after the ID update process which the distributed ID management system which concerns on this embodiment performs. It is a figure which shows the example of a message transmitted / received by ID conversion process (failure example) after ID update process which the data management system which concerns on this embodiment performs.

First, the configuration of the distributed ID management system 5 according to the present embodiment will be described.
FIG. 1 is a diagram for explaining an example of the overall configuration of a distributed ID management system 5 according to the present embodiment.

  As shown in FIG. 1, a distributed ID management system 5 according to the present embodiment includes a gateway device 2 connected to a client device 1 and a plurality of data management devices connected to the gateway device 2 via a communication network 4. 3 (3A, 3B, 3C, 3D, 3E,...). The number of data management devices 3 is not limited to five as shown in FIG. Each data management device 3 (3A, 3B, 3C, 3D, 3E,...) Is connected to be communicable via a communication network 4.

  The client device 1 sends to the distributed ID management system 5 (gateway device 2) an ID registration request message 10 (see FIG. 8A), an ID conversion request message 40 (see FIG. 17A), It is an apparatus that transmits an update request message 60 (see FIG. 22A) and receives the result. The gateway device 2 receives each message from the client device 1, distributes and transmits the message to the data management device 3 in charge of the message, and returns the processing result from the data management device 3 to the client device 1. Device. The data management device 3 is a device that performs data registration, conversion, update, and the like in accordance with a message acquired from the gateway device 2. Next, the detailed configuration of each device will be described.

≪Client device≫
FIG. 2 is a functional block diagram illustrating a configuration example of the client device 1 according to the present embodiment. As illustrated in FIG. 2, the client device 1 includes a control unit 110, an input / output unit 130, a transmission / reception unit 140, and a storage unit 150.

  The control unit 110 includes an ID registration request unit 111, an ID conversion request unit 112, and an ID update request unit 113.

  The ID registration request unit 111 generates an ID registration request message 10 (see FIG. 8A) to be described later, and transmits the ID registration request message 10 to the gateway device 2 via the transmission / reception unit 140. Further, the ID registration request unit 111 receives the ID registration response message 11 (see FIG. 8B) via the transmission / reception unit 140.

  The ID conversion request unit 112 generates an ID conversion request message 40 (see FIG. 17A) to be described later, and transmits the ID conversion request message 40 to the gateway device 2 via the transmission / reception unit 140. Further, the ID conversion request unit 112 receives the ID conversion response message 41 (see FIG. 17B) via the transmission / reception unit 140.

  The ID update request unit 113 generates an ID update request message 60 (see FIG. 22A) to be described later, and transmits the ID update request message 60 to the gateway device 2 via the transmission / reception unit 140. Further, the ID update request unit 113 receives the ID update response message 61 (see FIG. 22B) via the transmission / reception unit 140.

  The input / output unit 130 is connected to input means such as a keyboard and mouse (not shown) and output means such as a monitor, receives input information from the user via the input means, and receives the input information and processing results from the monitor and the like. Processing to output to the output means is performed.

  The transmission / reception unit 140 controls information transmitted / received via a network or a communication path such as a protocol stack that enables TCP / IP (Transmission Control Protocol / Internet Protocol) communication, a module that enables inter-process communication, and the like. I do.

  The storage unit 150 includes the gateway information storage area 100. The gateway information storage area 100 is an area for storing connection information (for example, a combination of an IP address and a port number) of the gateway device 2 that is a transmission destination of the ID registration request message 10, the ID conversion request message 40, and the ID update request message 60. It is. This connection information may be registered statically in advance, or a connection destination may be dynamically determined and stored based on information from the gateway device 2 or another device.

≪Gateway device≫
FIG. 3 is a functional block diagram illustrating a configuration example of the gateway device 2 according to the present embodiment. As shown in FIG. 3, the gateway device 2 includes a control unit 210, an input / output unit 230, a transmission / reception unit 240, and a storage unit 250.

  The control unit 210 includes a node management unit 211, a node determination unit 212, an ID registration transfer unit 213, an ID conversion transfer unit 214, and an ID update transfer unit 215.

  The node management unit 211 communicates with a node management unit 311 to be described later on the data management device 3 to synchronize connection information (for example, a combination of an IP address and a port number) of nodes in the node information storage area 200 to be described later. I do. Specifically, the node management unit 211 adds the connection information in the node information storage area 200 when a new data management device 3 is added, and deletes a data management device 3. Deletes the connection information of the data management device 3.

  When the node determination unit 212 obtains a search key from another processing unit, the node determination unit 212 determines a node (data management device 3) that the search key is responsible for based on the node information stored in the node information storage area 200. A process of returning the connection information of the node to the requested processing unit is performed. Hereinafter, the process performed by the node determination unit 212 will be specifically described.

  FIG. 4A is a diagram illustrating an example of a data configuration of node information stored in the node information storage area 200 according to the present embodiment. FIG. 4B is a diagram for explaining the data distribution destination determination process by the node determination unit 212 according to the present embodiment.

  As shown in FIG. 4A, the node information in the node information storage area 200 includes, for each data management device 3, a node ID, a node name, connection information (for example, a set of an IP address and a port number), and the like. Is remembered. The node ID is a hash value obtained by the node determination unit 212 introducing, for example, connection information into a predetermined hash function, and is on the ring (closed hash space) 400 illustrated in FIG. Is associated with a value. The node information in the node information storage area 200 is periodically transmitted between the gateway device 2 and all the data management devices 3 by the node management unit 211 of the gateway device 2 and the node management unit 311 of the data management device 3. The same node information is shared by synchronizing with each other.

As illustrated in FIG. 4B, for example, when “0 @ D0” is acquired as a search key, the node determination unit 212 introduces the search key into the hash function H and calculates a hash value. Then, the node determination unit 212 determines the data management device A having “3050”, which is the closest node ID (hash value), larger than the calculated hash value (“2133” in FIG. 4B). It is determined as a node to which the search key data is distributed.
At this time, the node determination unit 212 has a node having a node ID (hash value) having a value next to the node determined as the distribution destination (in this case, for example, the data management device 3B having the node ID “5988”). Is further selected (and one or more nodes may be selected so as to include the next closest node ID), thereby increasing the reliability of the system by making the destination of each message described later redundant. Is also possible.

  Returning to FIG. 3, the ID registration transfer unit 213 combines the identifier (for example, “0”) and the domain (for example, “D0”) of the received ID registration request message 10 (see FIG. 8A). An index key (for example, “0 @ D0”) is generated as a value and output to the node determination unit 212. Then, the ID registration transfer unit 213 transmits the ID registration request message 10 via the transmission / reception unit 240 to the data management device 3 that is the responsible node determined by the node determination unit 212. Here, the responsible node refers to a node (data management apparatus 3) that stores an index, which will be described later, using an index key obtained by combining the first identifier of the ID registration request message 10 and the domain as a key. Further, the ID registration transfer unit 213 receives the ID registration response message 11 (see FIG. 8B) from the responsible node via the transmission / reception unit 240 and transmits the ID registration response message 11 to the client device 1.

  The ID conversion transfer unit 214 indexes the conversion source identifier (for example, “0”) of the received ID conversion request message 40 (see FIG. 17A) and the conversion source domain (for example, “D0”) as a combined value. A key (for example, “0 @ D0”) is generated and output to the node determination unit 212. Then, the ID conversion / transfer unit 214 sends an ID conversion request to the data management device 3 serving as the index node (the node that stores the index, details will be described later) determined by the node determination unit 212 via the transmission / reception unit 240. A message 40 is transmitted. Further, the ID conversion transfer unit 214 receives the ID conversion response message 41 (see FIG. 17B) from the index node via the transmission / reception unit 240 and transmits the ID conversion response message 41 to the client device 1.

  The ID update transfer unit 215 indexes the update target identifier (for example, “0”) and the update target domain (for example, “D0”) of the received ID update request message 60 (see FIG. 22A) as an index. A key (for example, “0 @ D0”) is generated and output to the node determination unit 212. Then, the ID update transfer unit 215 transmits the ID update request message 60 to the data management device 3 serving as the index node determined by the node determination unit 212 via the transmission / reception unit 240. Further, the ID update transfer unit 215 receives the ID update response message 61 (see FIG. 22B) from the index node via the transmission / reception unit 240 and transmits it to the client device 1.

  The input / output unit 230 is connected to input means such as a keyboard and mouse (not shown) and output means such as a monitor, receives input information from the user via the input means, and receives the input information and processing results from the monitor and the like. Processing to output to the output means is performed.

  The transmission / reception unit 240 controls information transmitted / received via a network or a communication path, such as a protocol stack that enables TCP / IP communication and a module that enables inter-process communication.

  The storage unit 250 includes the node information storage area 200 (see FIG. 4A).

  In the present embodiment, the gateway device 2 is handled as a device independent of the client device 1 and the data management device 3, but the present invention is not limited to such an aspect. By implementing each function constituting the gateway device 2 in the client device 1 or the data management device 3, it is also possible to realize the distributed ID management system 5 without the gateway device 2.

≪Data management device≫
FIG. 5 is a functional block diagram illustrating a configuration example of the data management apparatus 3 according to the present embodiment.
As shown in FIG. 5, the data management device 3 includes a control unit 310, an input / output unit 330, a transmission / reception unit 340, and a storage unit 350.

  In addition, the control unit 310 includes a node management unit 311, a node determination unit 312, a root key generation unit 313, an ID registration processing unit 314, an ID conversion processing unit 315, an ID update processing unit 316, and an ID acquisition process. A unit 317, an index registration processing unit 318, a route information registration processing unit 319, a route information update processing unit 320, and a data management unit 321.

  Since the processes of the node management unit 311 and the node determination unit 312 are the same as those of the node management unit 211 and the node determination unit 212 of the gateway device 2, the description thereof is omitted.

  The root key generation unit 313 generates a root key (for example, “R0”) using a pseudo random number generator or the like. Here, the root key refers to an identifier for uniquely specifying a management target in the distributed ID management system 5.

The ID registration processing unit 314 controls the overall ID registration processing. This will be specifically described below.
The ID registration processing unit 314 generates a value obtained by combining the identifier and the domain (for example, “0 @ D0”) as an index key, and outputs the generated value to the node determination unit 312. Then, the ID registration processing unit 314 transmits the index registration request message 30 (see FIG. 8E described later) to the data management device 3 that is the index node determined by the node determination unit 312 via the transmission / reception unit 340. To do.
Further, the ID registration processing unit 314 generates a value (for example, “R0 @ D0”) obtained by combining a root key (for example, “R0”) and a domain (for example, “D0”) as a sub-root key, and The data is output to the determination unit 312. Then, the ID registration processing unit 314 sends a route information registration request message 20 (see FIG. 8C described later) to the data management device 3 that is the root node determined by the node determination unit 312 via the transmission / reception unit 340. Send. Here, the root node refers to a node (data management apparatus 3) that stores route information to be described later using a sub-root key as a key. When receiving the route information registration response message 21 (see FIG. 8D described later) from the root node, the ID registration processing unit 314 generates an ID registration response message 11 (see FIG. 8B described later). To the gateway device 2.

The ID conversion processing unit 315 controls the overall ID conversion processing. This will be specifically described below.
The ID conversion processing unit 315 combines a conversion source identifier (for example, “0”) and a conversion source domain (for example, “D0”) from the ID conversion request message 40 (see FIG. 17A) (for example, , “0 @ D0”), an index key is generated. Then, the ID conversion processing unit 315 outputs the generated index key (“0 @ D0”) and the conversion source date and time (for example, “T1”) to the data management unit 321, so that The root key (for example, “R0”) is obtained from the index of the.
The ID conversion processing unit 315 generates a sub-root key as a value (for example, “R0 @ D1”) obtained by combining the acquired root key (“R0”) and the conversion destination domain (for example, “D1”), and a node determination unit An ID acquisition request message 50 (see FIG. 17C described later) is transmitted to the data management device 3 that is the root node determined by 312.
Further, the ID conversion processing unit 315 receives an ID acquisition response message 51 (see FIG. 17D described later) from the root node via the transmission / reception unit 340. Then, the ID conversion processing unit 315 generates an ID conversion response message 41 (see FIG. 17B) including the ID (identifier) acquired from the ID acquisition response message 51, and the gateway device via the transmission / reception unit 340 2 to send.

The ID update processing unit 316 controls the overall ID update processing. This will be specifically described below.
The ID update processing unit 316 combines the update target identifier (for example, “0”) and the update target domain (for example, “D0”) from the ID update request message 60 (see FIG. 22A) (for example, , “0 @ D0”), an index key is generated. Then, the ID update processing unit 316 outputs the generated index key (“0 @ D0”) and the update target date (for example, “T1”) to the data management unit 321, thereby generating a root key (for example, "R0") is acquired.
Further, the ID update processing unit 316 updates the revocation date / time (“∞”) of the row to the update date / time (for example, “T2”) via the data management unit 321.
Next, the ID update processing unit 316 generates a sub-root key as a value (for example, “R0 @ D0”) obtained by combining the root key (“R0”) and the update target domain (“D0”), and the node determination unit A route information update request message 70 (see FIG. 22C described later) is transmitted to the data management device 3 that is the root node determined by 312.
The ID update processing unit 316 receives a route information update response message 71 (see FIG. 22D described later) from the route node via the transmission / reception unit 340.
Further, the ID update processing unit 316 generates an index key as a value (for example, “9 @ D0”) obtained by combining the post-update identifier (for example, “9”) and the update target domain (“D0”), and the node The index registration request message 30 (see FIG. 22 (e)) is transmitted to the data management apparatus 3 that is the index node determined by the determination unit 312.
Then, the ID update processing unit 316 receives the index registration response message 31 (see FIG. 22F) from the index node via the transmission / reception unit 340. Subsequently, the ID update processing unit 316 generates an ID update response message 61 (see FIG. 22B) and transmits it to the gateway device 2 via the transmission / reception unit 340.

  The ID acquisition processing unit 317 acquires the sub-root key (for example, “R0 @ D1”) and the conversion date / time (for example, “T1”) from the ID acquisition request message 50 (see FIG. 17C), By outputting the data to the data management unit 321, an identifier (for example, “a”) as a conversion destination is acquired. Then, the ID acquisition processing unit 317 generates an ID acquisition response message 51 (see FIG. 17D) including the identifier (“a”) that is the conversion destination, and performs data management of the request source via the transmission / reception unit 340. Transmit to device 3.

  The index registration processing unit 318 performs index registration processing based on the received index registration request message 30 (see FIG. 8E), and an index registration response message 31 (including “success”). 8 (f)) is generated and transmitted to the requesting data management apparatus 3 via the transmission / reception unit 340.

  The route information registration processing unit 319 performs route information registration processing based on the received route information registration request message 20 (for example, see FIG. 8C), and includes a route including the processing result (for example, “success”). An information registration response message 21 (see FIG. 8D) is generated and transmitted to the requesting data management apparatus 3 via the transmission / reception unit 340.

  The route information update processing unit 320 performs route information update processing based on the received route information update request message 70 (see FIG. 22C), and updates the route information including the processing result (for example, “success”). A response message 71 (see FIG. 22D) is generated and transmitted to the requesting data management apparatus 3 via the transmission / reception unit 340.

  In response to a request from another processing unit, the data management unit 321 creates, searches, updates, deletes data in the data storage area 300, and the like.

  The input / output unit 330 is connected to input means such as a keyboard and mouse (not shown) and output means such as a monitor, receives input information from the user via the input means, and receives the input information and processing results from the monitor and the like. Processing to output to the output means is performed.

  The transmission / reception unit 340 controls information transmitted / received via a network or a communication path, such as a protocol stack that enables TCP / IP communication and a module that enables inter-process communication.

The storage unit 350 includes the node information storage area 200 (see FIG. 4A) and the data storage area 300 described above.
The data storage area 300 is an area in which four sets of data of key, registration date / time, expiration date / time, and value are stored as an index or route information. Details will be described later.

≪Hardware configuration≫
FIG. 6 is a hardware configuration diagram of each device (client device 1, gateway device 2, data management device 3) according to the present embodiment.

As shown in FIG. 6, each device according to the present embodiment is realized by a general computer 1000.
The computer 1000 includes a CPU 1001, a memory 1002, an external storage device 1003 such as a hard disk, a transmission / reception device 1004 such as a NIC (Network Interface Card) for connection to a communication network, an output device 1005 such as a monitor, a keyboard, An input device 1006 such as a mouse and a reading device 1007 that reads information from a portable storage medium 1008 such as a CD-ROM or DVD-ROM are configured.

  The storage area in the storage unit of each device can be realized by the CPU 1001 using the memory 1002 or the external storage device 1003. Each control unit can be realized by the CPU 1001 by loading a predetermined program stored in the external storage device 1003 into the memory 1002. The predetermined program may be acquired from the storage medium 1008 via the reading device 1007, or downloaded to the external storage device 1003 from the network via the transmission / reception device 1004, loaded into the memory 1002, and executed by the CPU 1001. You may do it. Alternatively, the program may be directly loaded into the memory 1002 from the storage medium 1008 via the reading device 1007 or from the network via the transmission / reception device 1004 and executed by the CPU 1001.

≪Distributed ID management method≫
Next, a distributed ID management method by the distributed ID management system 5 according to the present embodiment will be described. Specifically, (1) ID registration processing, (2) ID conversion processing, and (3) ID update processing by the distributed ID management system 5 will be described.
(1) In the ID registration process, registration information including “identifier”, “domain”, and “registration date / time” included in the ID registration request message 10 (see FIG. 8A) acquired from the client device 1 is sent to the gateway device 2. Thus, the data is stored in the data management device 3 in a distributed manner in the storage format of index and route information.
(2) The ID conversion process includes “conversion source identifier”, “conversion source domain”, “conversion source date / time”, and “conversion destination domain” included in the ID conversion request message 40 (see FIG. 17A) acquired from the client device 1. This is a process of converting “conversion source identifier” to “conversion destination identifier” using the parameter of “conversion destination date and time”, that is, searching for “conversion destination identifier”.
(3) In the ID update process, based on the ID update request message 60 (see FIG. 22A) acquired from the client device 1, identifiers after “update date and time” in a certain “update target domain” have been registered so far. This is a process for updating the “update target identifier” to the “updated identifier” which is a new identifier.
Hereinafter, each process will be described in detail.

<ID registration process>
First, referring to FIG. 7 to FIG. 15, when the client device 1 requests the gateway device 2 to register ID (ID registration request), the ID registration processing executed by the gateway device 2 and the data management device 3. Will be described.

  Here, as an example of the ID registration process requested by the client apparatus 1, the identifier “0” in the date “T0” of the domain “D0” and the identifier “a” in the date “T0” of the domain “D1” are the same management. A process for registering in the distributed ID management system 5 as an identifier indicating a target will be described as an example.

(Overall flow of ID registration process)
FIG. 7 is a sequence diagram showing the overall flow of ID registration processing performed by the distributed ID management system 5 according to the present embodiment.

  First, the client device 1 transmits an ID registration request message 10 to the gateway device 2 (step S101).

FIG. 8A is a diagram illustrating an ID registration request message 10. As shown in FIG. 8A, the ID registration request message 10 indicates one registration information with three parameters of “identifier”, “domain”, and “registration date and time”, and reference numeral 10-1 denotes the ID registration. The request indicates that the identifier “0” in the registration date “T0” of the domain “D0” is included. Reference numeral 10-2 indicates that the ID registration request is an identifier “a” in the registration date “T0” of the domain “D1”. "Indicates that it contains. In the ID registration process requested by the ID registration request message 10, the identifier “0” in the registration date “T0” of the domain “D0” and the identifier “a” in the registration date “T0” of the domain “D1” A process of registering identifiers indicating the same management target is performed.
In this example, two examples of registration information that is a set of “identifier”, “domain”, and “registration date” will be described. However, the registration information is not limited to two sets, and three or more sets of registration information are registered. Information may be registered at the same time.
Further, in the diagrams shown in FIG. 7 and subsequent figures, for example, the information of the identifier “0” of the domain “D0” in the date and time “T0” is expressed as [0 @ D0: T0].

  Returning to FIG. 7, next, the gateway apparatus 2 performs a determination process of a responsible node (step S102). Here, the responsible node is the head index key of the received ID registration request message 10 (here, “0 @ D0” as a value obtained by combining the head identifier “0” and the domain “D0”) as the key. This refers to a node (data management device 3) that stores an index to be described later. The node determination unit 212 of the gateway device 2 determines the responsible node by the consistent hash method using the index key “0 @ D0” as a key. Here, it is assumed that the node determination unit 212 determines the data management device 3A as the responsible node.

  Subsequently, the gateway device 2 transmits the ID registration request message 10 to the data management device 3A determined as the responsible node (step S103).

  Upon receiving the ID registration request message 10, the data management device 3A performs a root key generation process (step S104). For example, the distributed key management system 5 uses the same management target indicated by the identifier “0” in the date “T0” of the domain “D0” and the identifier “a” in the date “T0” of the domain “D1”. It points to an identifier for uniquely identifying within. Here, for example, the root key generation unit 313 of the data management apparatus 3A generates “R0” as the root key using a pseudo random number generator or the like.

Next, the data management device 3A performs index storage (registration) processing (step S105). Here, the index includes an index key (a combined value of an identifier and a domain. For example, “0 @ D0”), a registration date (for example, “T0”), and a root key (for example, “R0”). It refers to information (for example, see FIG. 9A described later).
Specifically, first, the data management device 3A determines an index node (data management device 3) that stores an index relating to the identifier “0” and the domain “D0”. The index node determination process is executed by the node determination unit 312 in the same manner as the assigned node determination process using the index key (“0 @ D0”) as a search key. Then, the node determination unit 312 determines the data management device 3A itself as an index node using the consistent hash method. Then, the data management device 3A performs an index saving process on its own data storage area 300A (300).

  FIG. 9A shows an example of the data storage area 300A of the data management apparatus 3A in which the index is stored (registered). The index stored in the data storage area 300A includes an index key “0 @ D0” as a key, “T0” as a registration date, and an expiration date (“0 @ D0” has not yet been revoked). ) “∞” and root key “R0” as value are stored.

  Returning to FIG. 7, next, the data management device 3 </ b> A performs a root node determination process for the domain “D 0” (step S 106). Here, the root node refers to a node (data management apparatus 3) that stores root information to be described later using a sub-root key (a combined value of a root key and a domain. For example, “R0 @ D0”) as a key. In this root node determination process, the node determination unit 312 determines a root node by a consistent hash method using the sub-root key as a search key. Here, for example, it is assumed that the data management device 3B is determined as a root node as a node corresponding to the sub-root key “R0 @ D0”.

  Subsequently, the data management device 3A transmits a route information registration request message 20a (20) to the data management device 3B determined as the root node (step S107).

  FIG. 8C is a diagram illustrating a route information registration request message 20. As shown in FIG. 8C, the route information registration request message 20 includes parameters of “sub-root key”, “identifier”, and “registration date”. In the route information registration request message 20a (20) illustrated in FIG. 8C, the route key “R0” and the identifier “0” in the registration date “T0” of the domain “D0” are associated and managed. It is what is requested.

  Returning to FIG. 7, the data management apparatus 3B that has received the route information registration request message 20a (20) performs a route information storage (registration) process (step S108). Here, the route information includes a sub-root key (a combined value of a root key and a domain. For example, “R0 @ D0”), a registration date (for example, “T0”), and an identifier (for example, “0”). It refers to the information that it contains.

  FIG. 9B shows an example of the data storage area 300B of the data management device 3B in which route information is stored (registered). The route information stored in the data storage area 300B includes a sub-root key “R0 @ D0” as a key, “T0” as a registration date, and an expiration date (“R0 @ D0” has not yet been revoked). “)” And “0” as a value are stored.

  Returning to FIG. 7, the data management device 3B transmits the route information registration response message 21a (21) to the data management device 3A (step S109). As shown in FIG. 8D, the route information registration response message 21 is composed of parameters indicating processing results. Here, it is assumed that “success” indicating that the route information registration processing is successful is added as the route information registration response message 21a.

  Next, the data management device 3A performs an index node determination process for the identifier “a” and the domain “D1” (step S110). Here, for example, the data management device 3C that is a node corresponding to the index key “a @ D1” is determined by the node determination unit 312 as an index node.

  Subsequently, the data management device 3A transmits the index registration request message 30a (30) to the data management device 3C determined as the index node (step S111).

  FIG. 8E illustrates the index registration request message 30. As shown in FIG. 8E, the index registration request message 30 includes parameters of “index key”, “root key”, and “registration date”. The index registration request message 30a (30) illustrated in FIG. 8E requests to manage the root key “R0” and the identifier “a” in the registration date “T0” of the domain “D1” in association with each other. To do.

  Returning to FIG. 7, the data management apparatus 3C that has received the index registration request message 30a (30) performs an index storage (registration) process (step S112).

  FIG. 9C shows an example of the data storage area 300C of the data management device 3C in which the index is saved (registered). In the index stored in the data storage area 300C, an index key “a @ D1” as a key, “T0” as a registration date / time, and “a @ D1” as an expiration date / time have not yet been revoked. ) “∞” and root key “R0” as value are stored.

  Returning to FIG. 7, the data management device 3C transmits an index registration response message 31a (31) to the data management device 3A (step S113). As shown in FIG. 8F, the index registration response message 31 is composed of parameters indicating processing results. Here, it is assumed that “success” indicating that the index registration processing is successful is added as the index registration response message 31a (31).

  Returning to FIG. 7, the data management device 3A performs a root node determination process for the domain “D1” (step S114). Here, it is assumed that the node determination unit 312 has determined the data management device 3D as a root node as a node corresponding to the sub-root key “R0 @ D1”.

  Subsequently, the data management device 3A transmits a route information registration request message 20b (20) to the data management device 3D determined as the root node (step S115).

  As shown in FIG. 8G, the route information registration request message 20b includes a sub-root key “R0 @ D1”, an identifier “a”, and a registration date and time “T0”. This route information registration request message 20b requests to manage the route key “R0” in association with the identifier “a” in the registration date “T0” of the domain “D1”.

  Returning to FIG. 7, the data management device 3D that has received the route information registration request message 20b (20) performs a route information storage (registration) process (step S116).

  FIG. 9D shows an example of the data storage area 300D of the data management device 3D in which route information is saved (registered). The route information stored in the data storage area 300D includes a sub-root key “R0 @ D1” as a key, “T0” as a registration date, and an expiration date (“R0 @ D1” indicates that it has not yet been revoked). ) “∞” and identifier “a” as value are stored.

  Returning to FIG. 7, the data management device 3D transmits the route information registration response message 21b (21) to the data management device 3A (step S117). As shown in FIG. 8H, the route information registration response message 21b is attached with “success” indicating that the route information registration processing is successful.

  Returning to FIG. 7, the data management device 3A that has received the route information registration response message 21b (21) transmits the ID registration response message 11 to the gateway device 2 (step S118). As shown in FIG. 8B, “success” indicating that the ID registration processing is successful is attached to the ID registration response message 11.

  Returning to FIG. 7, the gateway device 2 transmits the ID registration response message 11 to the client device 1 (step S119), and ends the process.

  By this ID registration processing, indexes and route information as shown in FIGS. 9A to 9D are stored in the data storage area 300 of each data management device 3. These pieces of information can be regarded as a virtual representation of the conversion table at the date “T0” as shown in FIG. For example, in the data in the first row of FIG. 9E, the identifier “0” is stored in the column of the domain “D0”, and the identifier “a” is stored in the column of the domain “D1”. In the date and time “T0”, a management target indicates that the identifier is “0” in the domain “D0”, and the identifier “a” in the domain “D1”.

  Next, processing performed by the gateway device 2 and the data management device 3 in this ID registration processing will be described in more detail.

(Processing of gateway device in ID registration processing)
First, the processing of the gateway device 2 in the ID registration processing of FIG. 7 will be described in detail. FIG. 10 is a flowchart showing a process flow of the gateway device 2 in the ID registration process according to the present embodiment.

  First, the transmission / reception unit 240 of the gateway device 2 receives the ID registration request message 10 (see FIG. 8A) from the client device 1, and outputs the received ID registration request message 10 to the ID registration transfer unit 213 (step). S121).

  The ID registration transfer unit 213 generates an index key “0 @ D0” as a value obtained by combining the first identifier (“0”) and the domain (“D0”) of the received ID registration request message 10, and the node determination unit 212. (Step S122).

  The node determination unit 212 determines a responsible node by the consistent hash method, acquires connection information of the determined responsible node from the node information storage area 200 in the storage unit 250, and outputs it to the ID registration transfer unit 213 ( Step S123).

  The ID registration transfer unit 213 transmits the ID registration request message 10 (see FIG. 8A) to the responsible node via the transmission / reception unit 240 (step S124).

  Then, the ID registration transfer unit 213 receives the ID registration response message 11 (see FIG. 8B) from the responsible node via the transmission / reception unit 240 (step S125).

  Subsequently, the ID registration transfer unit 213 transmits the ID registration response message 11 to the client device 1 via the transmission / reception unit 240 and ends the process (step S126).

(Node decision processing by the node decision unit)
Next, node determination processing by the node determination units 212 and 312 will be described (see FIG. 4 as appropriate). FIG. 11 is a flowchart showing the flow of the node determination process according to the present embodiment. The node determination units 212 and 312 exist in both the gateway device 2 and the data management device 3, and perform the same processing. The same information is also stored in both the gateway device 2 and the data management device 3 in the node information storage area 200 referred to by the node determination units 212 and 312.

  First, the node determination units 212 and 312 are called with a search key (here, “q”) as an input (step S131).

  Next, the node determination units 212 and 312 calculate the hash value H (q) of the search key q based on the hash function H (step S132).

  Subsequently, the node determination units 212 and 312 refer to the ring (closed hash space in FIG. 4B) 400 based on the node information in the node information storage area 200, and the value larger than the hash value H (q) is the most. A node having a close hash value (node ID) is determined as a node to which data relating to the search key q is distributed (step S133).

  Then, the node determination units 212 and 312 acquire the connection information of the determined nodes with reference to the node information storage area 200, output them to the caller, and finish the processing (step S134).

(Process of responsible node in ID registration process)
Next, the processing of the data management device 3A, which is the responsible node, in the ID registration processing of FIG. 7 will be described in detail. 12 and 13 are flowcharts showing the processing flow of the node in charge (data management apparatus 3A) in the ID registration processing according to the present embodiment.

  As shown in FIG. 12, first, the transmission / reception unit 340 of the data management device 3 (here, the data management device 3A), which is the responsible node, sends an ID registration request message 10 (see FIG. 8A) from the gateway device 2. The received ID registration request message 10 is output to the ID registration processing unit 314 (step S141).

  Next, the root key generation unit 313 generates a root key (here, “r”) (step S142). For example, as in step S104 of FIG. 7, the root key generation unit 313 of the data management device 3A generates “R0” as the root key r using a pseudo random number generator or the like.

  Subsequently, the ID registration processing unit 314 determines whether or not a set of an identifier, a domain, and a registration date / time exists in the ID registration request message 10 (step S143). The ID registration processing unit 314 proceeds to step S152 in FIG. 13 when there is no set of identifier, domain, and registration date / time (step S143 → No). On the other hand, if a set of identifier, domain, and registration date / time exists (step S143 → Yes), one of the set of identifier, domain, registration date / time is selected, and the process proceeds to the next step S144.

  In step S144, the ID registration processing unit 314 generates a value obtained by combining the identifier and the domain (for example, “0 @ D0”) for the selected set of information as an index key, and outputs the generated value to the node determination unit 312. .

  Next, the node determination unit 312 determines a node to be an index node by a consistent hash method, acquires connection information of the determined index node from the node information storage area 200 in the storage unit 350, and performs ID registration processing The data is output to the unit 314 (step S145).

  Then, the ID registration processing unit 314 transmits the index registration request message 30 (see FIG. 8E) including the index key, root key, and registration date and time parameters to the index node via the transmission / reception unit 340 ( Step S146).

  Subsequently, the ID registration processing unit 314 receives the index registration response message 31 (see FIG. 8F) from the index node (step S147).

  Moving to FIG. 13, the ID registration processing unit 314 generates a value obtained by combining the root key and the domain (for example, “R0 @ D0”) as a sub-root key, and outputs the generated value to the node determination unit 312 (step S148).

  Next, the node determination unit 312 determines a root node by a consistent hash method, acquires connection information of the determined root node from the node information storage area 200 in the storage unit 350, and sends it to the ID registration processing unit 314. Output (step S149).

  Subsequently, the ID registration processing unit 314 sends the route information registration request message 20 (see FIGS. 8C and 8G) including the parameters of the sub route key, the identifier, and the registration date / time to the route node via the transmission / reception unit 340. (Step S150).

  Then, the ID registration processing unit 314 receives the route information registration response message 21 (see FIGS. 8D and 8H) from the root node (step S151).

  Returning to step S143 in FIG. 12, the ID registration processing unit 314 proceeds to step S152 in FIG. 13 when there is no set of identifier, domain, and registration date / time (step S143 → No). Then, the ID registration processing unit 314 determines whether all the processes have been successful (step S152). For example, the ID registration processing unit 314 determines whether or not a correct response to the request message has been made within a predetermined time. When all the processes are successful (step S152 → Yes), the ID registration processing unit 314 sends the ID registration response message 11 (see FIG. 8B) to the gateway device 2 via the transmission / reception unit 340. Then, the process ends (step S153). On the other hand, when all the processes are not successful (step S152 → No), the ID registration processing unit 314 transmits an error message to the gateway device 2 via the transmission / reception unit 340 and ends the process (step S154). ).

(Index saving process)
Next, an index storage (registration) process of the data management apparatus 3 (here, the data management apparatus 3C) performed in step S112 of the ID registration process of FIG. 7 will be described in detail. FIG. 14 is a flowchart showing a process flow of the data management apparatus 3 in the index storing process according to the present embodiment.

  First, when the transmission / reception unit 340 receives the index registration request message 30 from another data management apparatus 3, the transmission / reception unit 340 outputs the received index registration request message 30 (see FIG. 8E) to the index registration processing unit 318 (step S31). S161).

  Next, the index registration processing unit 318 receives an index key (here “k”), a root key (here “r”), a registration date and time (here “t”) from the index registration request message 30. Is output to the data management unit 321 (step S162).

  The data management unit 321 adds, to the index of its own data storage area 300, a row with the index key “k” as the key, the registration date and time “t”, the expiration date and time “∞”, and the root key “r” as the value. (Step S163).

  Then, the index registration processing unit 318 generates an index registration response message 31 (see FIG. 8F) including “success” indicating that the index has been saved, and transmits the request source data via the transmission / reception unit 340. It transmits to the management apparatus 3 and complete | finishes a process (step S164).

(Route information saving process)
Next, the route information storage (registration) processing of the data management device 3 (here, the data management devices 3B and 3D) performed in steps S108 and S116 of the ID registration processing of FIG. 7 will be described in detail. FIG. 15 is a flowchart showing a process flow of the data management apparatus 3 in the route information storage process according to the present embodiment.

  First, when the transmission / reception unit 340 receives the route information registration request message 20 (see FIGS. 8C and 8G) from the other data management device 3, the received route information registration request message 20 is transmitted to the route information registration processing unit. It outputs to 319 (step S171).

  Next, the route information registration processing unit 319 receives, from the route information registration request message 20, a sub route key (here, “s”), an identifier (here, “i”), a registration date (here, “t”). And output to the data management unit 321 (step S172).

  The data management unit 321 adds, to the route information of its own data storage area 300, a row with the sub-root key “s” as the key, the registration date and time “t”, the expiration date and time “∞”, and the identifier “i” as the value. (Step S173).

  Then, the route information registration processing unit 319 generates a route information registration response message 21 (see FIGS. 8D and 8H) indicating that the route information has been saved, and transmits the request source via the transmission / reception unit 340. It transmits to the data management apparatus 3, and a process is complete | finished (step S174).

  In this way, the distributed ID management system 5 according to the present embodiment transmits the registration information included in the ID registration request message 10 (see FIG. 8A) acquired from the client device 1 via the gateway device 2. Thus, the data can be stored in the data management apparatus 3 in a distributed manner by the storage format of index and route information.

  In this example, as shown in FIG. 8A, the registration information that is a set of “identifier”, “domain”, and “registration date” is the first registration information (reference numeral 10-1) and the second registration information. The case where two sets of registration information (reference numeral 10-2) are registered has been described as an example. However, the present invention is not limited to two sets of registration information. If there are two or more sets, for example, the third registration information, the fourth registration information, and the fifth registration information are used. It is also possible to register in each data management device 3 by the ID registration processing according to the present embodiment including the i (i-th) registration information.

In this case, the node determination unit 312 of the first data management device 3 (3A) that has received the ID registration request message 10 including i pieces of registration information from the gateway device 2 is the i-th (i-th: i is 1). As the data management apparatus 3 that calculates a hash value by applying a hash function to the i-th index key generated by the ID registration processing unit 314 for the registration information of the above integer), and refers to the node ID of the node information, The registration destination of the i-th index can be determined for the (2 × i−1) -th data management device 3. Further, the node determination unit 312 of the first data management device 3 (3A) applies a hash function to the i (i-th) sub-root key generated by the ID registration processing unit 314 for the i-th (i-th) registration information. Then, the hash value is calculated, and the registration destination of the i-th route information is determined as the (2 × i) -th data management device 3 as the data management device 3 determined by referring to the node ID of the node information. it can.
That is, even if the distributed ID management system 5 according to the present embodiment receives the ID registration request message 10 including i pieces of registration information, the i pieces of registration information are converted into indexes and route information. The data can be distributed and stored in a plurality of data management apparatuses 3.

<ID conversion process>
Next, referring to FIGS. 16 to 20, when the client apparatus 1 requests the gateway apparatus 2 to convert ID (ID conversion request) after the ID registration processing illustrated in FIG. 7 is performed. Next, ID conversion processing executed by the gateway device 2 and the data management device 3 will be described.

  Here, as an example of the ID conversion process requested by the client apparatus 1, the process of converting the identifier “0” of the date “T1” of the domain “D0” into the identifier of the same date “T1” of the domain “D1” (that is, The process of searching for an identifier in the same date and time “T1” of the domain “D1” corresponding to the identifier “0” in the date and time “T1” of the domain “D0” will be described. Here, “T1” indicates a date and time that is in the future than “T0”.

(Overall flow of ID conversion process)
FIG. 16 is a sequence diagram showing the overall flow of ID conversion processing performed by the distributed ID management system 5 according to the present embodiment.

  First, the client device 1 transmits an ID conversion request message 40a (40) to the gateway device 2 (step S201).

  FIG. 17A is a diagram illustrating an ID conversion request message 40. As shown in FIG. 17A, the ID conversion request message 40 includes parameters of “conversion source identifier”, “conversion source domain”, “conversion source date / time”, “conversion destination domain”, and “conversion destination date / time”. Consists of. The ID conversion request message 40a (40) illustrated in FIG. 17A includes an identifier (conversion source identifier) “0” of the date and time (conversion source date and time) “T1” of the domain (conversion source domain) “D0” as the conversion source. A process of converting “to” an identifier in the same date and time (conversion destination date and time) “T1” of the domain (conversion destination domain) “D1” (searching for an identifier to be converted) is requested.

  Returning to FIG. 16, the gateway device 2 that has received the ID conversion request message 40a (40) performs an index node determination process (step S202). This index node determination process is performed by the node determination unit 212 using the consistent hash method with the index key as a search key. Here, for example, the data management device 3A that is a node corresponding to the index key “0 @ D0” is determined as the index node.

  Subsequently, the gateway device 2 transmits the ID conversion request message 40a (40) to the data management device 3A determined as the index node (step S203).

  The data management device 3A that has received the ID conversion request message 40a (40) performs a root key acquisition process (step S204). The root key is acquired by searching the index (see FIG. 9A) in the data storage area 300A using the index key (“0 @ D0”) as a key, and the conversion source date / time T1 is between the registration date / time and the expiration date / time. From the included line. Here, “R0” is acquired as the root key from the index shown in FIG.

  Next, the data management device 3A performs a root node determination process (step S205). Here, the data management device 3D is determined as the root node as a node corresponding to the sub-root key “R0 @ D1”.

  Subsequently, the data management device 3A transmits an ID acquisition request message 50a (50) to the data management device 3D determined as the root node (step S206).

  FIG. 17C is a diagram illustrating an ID acquisition request message 50. As shown in FIG. 17C, the ID acquisition request message 50 includes parameters of “sub-root key” and “conversion destination date / time”. The ID acquisition request message 50a (50) illustrated in FIG. 17 (c) is a request for acquisition of an identifier associated with the sub-root key “R0 @ D1” that is valid for the conversion destination date and time “T1”. Indicates.

  Returning to FIG. 16, the data management device 3D that has received the ID acquisition request message 50a (50) performs an ID (identifier) acquisition process (step S207). The ID (identifier) is obtained by searching the route information (see FIG. 9D) in the data storage area 300D using the sub-root key “R0 @ D1” as a key, and the conversion date / time T1 is the registration date / time and expiration date. It is done from the lines that are included in the time. Here, “a” is acquired as the identifier from the route information shown in FIG.

  Next, the data management device 3D generates an ID acquisition response message 51a (51) and transmits it to the data management device 3A (step S208). As shown in FIG. 17D, the ID acquisition response message 51a includes the identifier (conversion destination identifier) “a” acquired as a result of the ID conversion process.

  Subsequently, the data management device 3A generates an ID conversion response message 41a (41) and transmits it to the gateway device 2 (step S209). As shown in FIG. 17B, the ID conversion response message 41a includes the identifier (conversion destination identifier) “a” acquired as a result of the ID conversion processing.

  Then, the gateway device 2 transmits an ID conversion response message 41a (41) to the client device 1 and ends the process (step S210).

  Next, processing performed by the gateway device 2 and the data management device 3 in this ID conversion processing will be described in more detail.

(Processing of gateway device in ID conversion processing)
First, details of the processing of the gateway device 2 in the ID conversion processing of FIG. 16 will be described. FIG. 18 is a flowchart showing a process flow of the gateway device 2 in the ID conversion process according to the present embodiment.

  First, the transmission / reception unit 240 of the gateway device 2 receives the ID conversion request message 40 (see FIG. 17A) from the client device 1, and outputs the received ID conversion request message 40 to the ID conversion transfer unit 214 (step). S221).

  The ID conversion transfer unit 214 generates an index key “0 @ D0” as a value obtained by combining the conversion source identifier “0” and the conversion source domain “D0” of the received ID conversion request message 40 and outputs the index key “0 @ D0” to the node determination unit 212. (Step S222).

  The node determination unit 212 determines a node to be an index node by a consistent hash method, acquires connection information of the determined index node from the node information storage area 200 in the storage unit 250, and sends it to the ID conversion transfer unit 214. Output (step S223).

  The ID conversion transfer unit 214 transmits the ID conversion request message 40 to the determined index node via the transmission / reception unit 240 (step S224).

  Then, the ID conversion transfer unit 214 receives the ID conversion response message 41 (see FIG. 17B) from the index node via the transmission / reception unit 240 (step S225).

  Subsequently, the ID conversion transfer unit 214 transmits the ID conversion response message 41 to the client device 1 via the transmission / reception unit 240 and ends the processing (step S226).

(Processing of data management device in ID conversion processing)
Next, the processing of the data management device 3 (here, the data management device 3A) in the ID conversion processing of FIG. 16 will be described in detail. FIG. 19 is a flowchart showing a process flow of the data management apparatus 3 (3A) in the ID conversion process according to the present embodiment.

  First, the transmission / reception unit 340 of the data management device 3 (here, the data management device 3A) receives the ID conversion request message 40 (see FIG. 17A) from the gateway device 2 and outputs it to the ID conversion processing unit 315. (Step S231).

  Next, the ID conversion processing unit 315 includes the conversion source identifier (here, “i”), the conversion source domain (here, “d”), the conversion date and time included in the ID conversion request message 40. (Here, “t”), a conversion destination domain (here, “d ′”), and a conversion destination date and time (here, “t ′”) are acquired. The ID conversion processing unit 315 generates an index key as a value (i @ d) obtained by combining the conversion source identifier i and the conversion source domain d. Specifically, the ID conversion processing unit 315 generates an index key “0 @ D0”. Then, the ID conversion processing unit 315 outputs the generated index key (i @ d) and the conversion source date / time t to the data management unit 321 (step S232).

  Subsequently, the data management unit 321 calculates the condition [key = i @ d and registration date ≦ t <revocation date / time from the index stored in the data storage region 300 (here, the data storage region 300A in FIG. 9A). ] Is satisfied (step S233).

  Then, the data management unit 321 determines whether or not there is a row that satisfies the condition (step S234), and when there is no row that satisfies the condition (step S234 → No), the data management unit 321 proceeds to step S242. On the other hand, if there is a row that satisfies the condition (step S234 → Yes), the data management unit 321 proceeds to the next step S235.

  In step S <b> 235, the data management unit 321 acquires a root key (“r”) from the value value of the row that satisfies the condition, and outputs the root key (“r”) to the ID conversion processing unit 315. Here, the data management unit 321 acquires “R0” as the root key from the index shown in FIG. 9A and outputs it to the ID conversion processing unit 315.

  Next, the ID conversion processing unit 315 generates a sub-root key as a value (r @ d ′) obtained by combining the root key r and the conversion destination domain d ′. Here, the ID conversion processing unit 315 generates a sub-root key “R0 @ D1”. Then, the ID conversion processing unit 315 outputs the generated sub-root key (r @ d ′) to the node determination unit 312 (step S236).

  Subsequently, the node determination unit 312 determines a node to be a root node by the consistent hash method, acquires connection information of the determined root node from the node information storage area 200 in the storage unit 350, and performs ID conversion processing The data is output to the unit 315 (step S237).

  The ID conversion processing unit 315 generates an ID acquisition request message 50 (see FIG. 17C) including the sub-root key (r @ d ′) and the conversion destination date and time t ′, and transmits the root node via the transmission / reception unit 340. (Step S238).

  Then, the ID conversion processing unit 315 receives an ID acquisition response message 51 (see FIG. 17D) including the conversion destination ID (identifier) from the root node via the transmission / reception unit 340 (step S239).

  The ID conversion processing unit 315 determines whether or not the ID (identifier) has been successfully acquired (step S240). If the ID conversion processing unit 315 has not succeeded (step S240 → No), the process proceeds to step S242. On the other hand, if the ID conversion processing unit 315 succeeds in acquiring the ID (identifier) (step S240 → Yes), the process proceeds to the next step S241.

  In step S241, the ID conversion processing unit 315 generates an ID conversion response message 41 (see FIG. 17B) including the ID (identifier) acquired from the ID acquisition response message 51, and via the transmission / reception unit 340, The data is transmitted to the gateway device 2 and the processing is finished.

  If there is no row that satisfies the condition in step S234 (step S234 → No), or if ID (identifier) acquisition has not been successful in step S240 (step S240 → No), the ID conversion processing unit 315 However, an error message is generated and transmitted to the gateway device 2 via the transmission / reception unit 340, and the process ends (step S242).

(ID acquisition process)
Next, the ID acquisition process performed in step S207 of the ID conversion process in FIG. 16 will be described in detail. FIG. 20 is a flowchart showing a processing flow of the data management device 3 (here, the data management device 3D) in the ID acquisition processing according to the present embodiment.

  First, when the transmission / reception unit 340 receives an ID acquisition request message 50 (see FIG. 17C) from another data management device 3, the transmission / reception unit 340 outputs the received ID acquisition request message 50 to the ID acquisition processing unit 317 (step S31). S251).

  Next, the ID acquisition processing unit 317 acquires the sub-root key (r @ d) and the conversion date and time t ′ from the ID acquisition request message 50, and outputs them to the data management unit 321 (step S252).

  Subsequently, the data management unit 321 satisfies the condition [key = r @ d and registration date / time ≦ t ′ <revocation date / time] from the route information stored in the data storage region 300 (here, the data storage region 300D). Is searched (step S253).

  Then, the data management unit 321 determines whether or not there is a row that satisfies the condition (step S254), and if there is no row that satisfies the condition (step S254 → No), the process proceeds to step S257. On the other hand, if there is a row that satisfies the condition (step S254 → Yes), the data management unit 321 proceeds to the next step S255.

  In step S <b> 255, the data management unit 321 acquires the identifier i from the value value of the row that satisfies the condition, and outputs the identifier i to the ID acquisition processing unit 317. Here, the data management unit 321 acquires “a” as the conversion destination identifier (conversion destination identifier) i from the route information shown in FIG. 9D, and outputs it to the ID acquisition processing unit 317.

  Next, the ID acquisition processing unit 317 generates an ID acquisition response message 51 (see FIG. 17D) including the conversion destination identifier i (here, “a”), and sends the request source via the transmission / reception unit 340. Is transmitted to the data management apparatus 3 and the process is terminated (step S256).

  In step S254, when there is no row that satisfies the condition (step S254 → No), the ID acquisition processing unit 317 generates an error message and sends the request source data management device 3 via the transmission / reception unit 340. To finish the process (step S257).

  By doing in this way, the distributed ID management system 5 according to the present embodiment allows the “conversion source identifier” “conversion source domain” included in the ID conversion request message 40 (see FIG. 17A) acquired from the client device 1. "Conversion source date", "Conversion destination domain", "Conversion destination date" can be used to convert "Conversion source identifier" to "Conversion destination identifier", that is, "Conversion destination identifier" can be searched. .

<ID update processing>
Next, referring to FIG. 21 to FIG. 27, when the client device 1 requests the gateway device 2 to update the ID (ID update request) after the ID registration processing shown in FIG. 7 is performed. Next, ID update processing executed by the gateway device 2 and the data management device 3 will be described.

  Here, as an example of ID update processing requested by the client device 1, the identifier (update target identifier) “0” in the date (update target date) “T1” of the domain (update target domain) “D0” is set to the date (update). The process of replacing (updating) with the identifier (updated identifier) “9” after “date and time” “T2” will be described. Here, “T2” indicates a future date and time than “T1”.

(Overall flow of ID update processing)
FIG. 21 is a sequence diagram showing an overall flow of ID update processing performed by the distributed ID management system 5 according to the present embodiment.

  First, the client device 1 transmits an ID update request message 60 to the gateway device 2 (step S301).

  FIG. 22A is a diagram illustrating an ID update request message 60. As shown in FIG. 22A, the ID update request message 60 includes parameters of “update target identifier”, “update target domain”, “update target date / time”, “updated identifier”, and “update date / time”. Composed. The ID update request message 60 illustrated in FIG. 22A includes the date (date of update) “T1” of the domain (update target domain) “D0” and the date (date of update) “0” as the update source. (Update date / time) After “T2”, a request to replace (update) the identifier (updated identifier) “9” is requested.

  Returning to FIG. 21, the gateway device 2 that has received the ID update request message 60 performs an index node determination process (step S302). This index node determination process is performed by the node determination unit 212 using the consistent hash method with the index key as a search key. Here, for example, the data management device 3A that is a node corresponding to the index key “0 @ D0” is determined as the index node.

  Subsequently, the gateway device 2 transmits an ID update request message 60 to the data management device 3A determined as the index node (step S303).

  The data management device 3A that has received the ID update request message 60 performs a root key acquisition process (step S304). The root key is acquired by searching the index (see FIG. 9A) in the data storage area 300A using the index key (“0 @ D0”) as a key, and the update target date and time “T1” is the registration date and expiration date. It is done from the line included in the time. Here, “R0” is acquired as the root key from the index shown in FIG.

  Next, the data management apparatus 3A performs an index revocation process (step S305). This index revocation process is performed by updating the revocation date and time of the row for which the root key “R0” has been acquired from the index in step S304.

  FIG. 23A shows an example of the data storage area 300A of the data management device 3A after the index revocation processing. Here, in the row corresponding to the index “0 @ D0”, the expiration date / time is updated from “∞” to “T2”.

  Returning to FIG. 21, next, the data management device 3A performs a process of determining a route node to be updated (step S306). Here, the node determination unit 312 determines the data management device 3B as a root node as a node corresponding to the sub-root key “R0 @ D0”.

  Subsequently, the data management apparatus 3A transmits a route information update request message 70 to the data management apparatus 3B determined as the root node (step S307).

  FIG. 22C is a diagram illustrating a route information update request message 70. As shown in FIG. 22C, the route information update request message 70 includes parameters of “sub-root key”, “updated identifier”, and “update date / time”. The route information update request message 70 shown in FIG. 22C is updated so that “9” is used as the identifier (updated identifier) associated with the sub route key “R0 @ D0” after the date (update date) “T2”. It is required to do.

  Returning to FIG. 21, the data management device 3B that has received the route information update request message 70 performs a route information update process (step S308).

  FIG. 23B shows an example of the data storage area 300B of the data management device 3B after updating the route information. Here, in the row corresponding to the sub-root key “R0 @ D0”, the expiration date / time is updated from “∞” to “T2” which is the update date / time in the row of the registration date / time “T0”. In addition, a new line of the sub-root key “R0 @ D0” is added, the sub-root key “R0 @ D0” as the key, the updated date and time “T2” as the registration date and time, “∞” as the revocation date and the identifier (after the update) Identifier) "9" is stored.

  Returning to FIG. 21, the data management device 3B transmits the route information update response message 71 (see FIG. 22D) to the data management device 3A (step S309). As shown in FIG. 22D, the route information update response message 71 is given “success” indicating that the route information update processing has been successful.

  Next, the data management device 3A performs an index node determination process (step S310). Here, for example, the data management device 3E that is a node corresponding to the index key “9 @ D0” is determined as the index node.

  Subsequently, the data management device 3A transmits the index registration request message 30b (30) to the data management device 3E determined as the index node (step S311).

  FIG. 22 (e) is a diagram illustrating an index registration request message 30. The index registration request message 30b illustrated in FIG. 22E is a request for managing the root key “R0” in association with the identifier “9” in the registration date “T2” of the domain “D0”. is there.

  Returning to FIG. 21, the data management device 3E that has received the index registration request message 30b performs an index storage process (step S312).

  FIG. 23 (e) shows an example of the data storage area 300E of the data management device 3E in which the index is stored. In the index stored in the data storage area 300E, an index key “9 @ D0” as a key, “T2” as a registration date / time, and “9 @ D0” as an expiration date / time have not yet been revoked. ) “∞” and root key “R0” as value are stored.

  Returning to FIG. 21, the data management device 3E generates an index registration response message 31b (31) and transmits it to the data management device 3A (step S313). As shown in FIG. 22 (f), the index registration response message 31 b is given “success” indicating that the index registration process has been successful.

  The data management device 3A that has received the index registration response message 31b generates an ID update response message 61 and transmits it to the gateway device 2 (step S314). As shown in FIG. 22B, “success” indicating that the ID update processing has been successful is added to the ID update response message 61.

  Then, the gateway device 2 transmits an ID update response message 61 to the client device 1 (step S315), and ends the process.

  By this ID update processing, values as shown in FIGS. 23A to 23E are stored in the data storage area 300 of each data management device 3. These values can be regarded as a virtual implementation of the conversion table at the date “T2” as shown in FIG. For example, in the data in the first row of FIG. 23F, the identifier “9” is stored in the column of the domain “D0” and the identifier “a” is stored in the column of the domain “D1”. It indicates that at a date and time “T2”, a certain management target has the identifier “9” in the domain “D0” and the identifier “a” in the domain “D1”.

  Next, processing performed by the gateway device 2 and the data management device 3 in this ID update processing will be described in more detail.

(Processing of gateway device in ID update processing)
Next, details of the processing of the gateway device 2 in the ID update processing of FIG. 21 will be described.
FIG. 24 is a flowchart showing a process flow of the gateway device 2 in the ID update process according to the present embodiment.

  First, the transmission / reception unit 240 of the gateway device 2 receives the ID update request message 60 (see FIG. 22A) from the client device 1, and outputs the received ID update request message 60 to the ID update transfer unit 215 (step). S321).

  The ID update transfer unit 215 generates an index key “0 @ D0” as a value obtained by combining the update target identifier “0” and the update target domain “D0” of the received ID update request message 60, and outputs the index key “0 @ D0” to the node determination unit 212 (Step S322).

  The node determination unit 212 determines a node to be an index node by a consistent hash method, acquires connection information of the determined index node from the node information storage area 200 in the storage unit 250, and sends it to the ID update transfer unit 215. Output (step S323).

  The ID update transfer unit 215 transmits the ID update request message 60 to the determined index node via the transmission / reception unit 240 (step S324).

  Then, the ID update transfer unit 215 receives the ID update response message 61 (see FIG. 22B) from the index node via the transmission / reception unit 240 (step S325).

  Subsequently, the ID update transfer unit 215 transmits the ID update response message 61 to the client device 1 via the transmission / reception unit 240 and ends the process (step S326).

(Process of data management device in ID update process)
Next, details of the processing of the data management device 3 (here, the data management device 3A) in the ID update processing of FIG. 21 will be described. 25 and 26 are flowcharts showing the flow of processing of the data management device 3 (3A) in the ID update processing according to the present embodiment.

  In FIG. 25, first, the transmission / reception unit 340 of the data management device 3 (here, the data management device 3A) receives the ID update request message 60 (see FIG. 22A) from the gateway device 2, and receives the ID update processing unit. It outputs to 316 (step S331).

  Next, the ID update processing unit 316 includes an update target identifier (here, “i”), an update target domain (here, “d”), and update target date / time included in the ID update request message 60. (Here, “t”), an identifier after update (here, “i ′”), and update date (here, “t ′”) are acquired. The ID update processing unit 316 generates an index key as a value (i @ d) obtained by combining the update target identifier i and the update target domain d. Here, the ID update processing unit 316 generates an index key “0 @ D0”. Then, the ID update processing unit 316 outputs the generated index key (i @ d) and the update target date / time t to the data management unit 321 (step S332).

  Subsequently, the data management unit 321 searches for a row satisfying the condition [key = i @ d and registration date ≦ t <revocation date] from the index stored in the data storage area 300 (in this case, the data storage area 300A). (Step S333).

  Then, the data management unit 321 determines whether or not there is a row that satisfies the condition (step S334), and if there is no row that satisfies the condition (step S334 → No), the process proceeds to step S347 in FIG. . On the other hand, if there is a row that satisfies the condition (step S334 → Yes), the data management unit 321 proceeds to the next step S335.

  In step S335, the data management unit 321 acquires the root key (“r”) from the value value of the row that satisfies the condition, and outputs the root key (“r”) to the ID update processing unit 316. Here, the data management unit 321 acquires “R0” as the root key from the index shown in FIG. 9A and outputs it to the ID update processing unit 316.

  Next, the ID update processing unit 316 updates the invalidation date / time of the row from “∞” to the update date / time t ′ via the data management unit 321 (step S336).

  Subsequently, the ID update processing unit 316 generates a sub-root key as a value (r @ d) obtained by combining the root key r and the update target domain d. Here, the ID update processing unit 316 generates a sub-root key “R0 @ D0”. Then, the ID update processing unit 316 outputs the generated sub-root key (r @ d) to the node determination unit 312 (step S337).

  Then, the node determination unit 312 determines a node to be a root node by a consistent hash method, acquires connection information of the determined root node from the node information storage area 200 in the storage unit 350, and an ID update processing unit It outputs to 316 (step S338).

  The ID update processing unit 316 generates a route information update request message 70 (see FIG. 22C) including the sub-root key (r @ d), the post-update identifier i ′, and the update date and time t ′. To the root node (step S339).

  Then, the ID update processing unit 316 receives the route information update response message 71 (see FIG. 22D) from the route node via the transmission / reception unit 340 (step S340).

  Moving to FIG. 26, the ID update processing unit 316 generates an index key as a value (i ′ @ d) obtained by combining the post-update identifier i ′ and the update target domain d. Here, the ID update processing unit 316 generates the index key “9 @ D0”. Then, the ID update processing unit 316 outputs the generated index key “9 @ D0” to the node determination unit 312 (step S341).

  Next, the node determination unit 312 determines a node to be an index node by a consistent hash method, acquires connection information of the determined index node from the node information storage area 200 in the storage unit 350, and performs ID update processing The data is output to the unit 316 (step S342).

  Then, the ID update processing unit 316 generates an index registration request message 30b (see FIG. 22E) via the index registration processing unit 318, and transmits it to the index node (step S343). The index registration request message 30b includes information on the index key “9 @ D0”, the root key “R0”, and the registration date and time “T2”.

  Subsequently, the ID update processing unit 316 receives the index registration response message 31b (see FIG. 22F) from the index node via the receiving unit 340 (step S344).

  Next, the ID update processing unit 316 determines whether or not all the processes related to the ID update process have succeeded (step S345), and if there is any process that has not succeeded (step S345 → No). The process proceeds to step S347. On the other hand, when all the processes are successful (step S345 → Yes), the ID update processing unit 316 proceeds to the next step S346.

  In step S346, the ID update processing unit 316 transmits the ID update response message 61 (see FIG. 22B) to the gateway device 2 via the transmission / reception unit 340, and ends the process.

  In addition, when there is no row that satisfies the condition in step S334 in FIG. 25 (step S334 → No), or there is a process that has not succeeded in step S345 in FIG. 26 (step S345 → No). The ID update processing unit 316 transmits an error message to the gateway device 2 and ends the process (step S347).

(Route information update process)
Next, the route information update processing of the data management device 3 (here, the data management device 3B) performed in step S308 of the ID update processing of FIG. 21 will be described in detail. FIG. 27 is a flowchart showing a flow of route information update processing of the data management device 3 (3B) in the ID update processing according to the present embodiment.

  First, when the transmission / reception unit 340 receives a route information update request message 70 (see FIG. 22C) from another data management device 3, the received route information update request message 70 is output to the route information update processing unit 320. (Step S351).

  Next, the route information update processing unit 320 obtains the sub route key (r @ d), the post-update identifier (i ′), and the update date / time (t ′) from the route information update request message 70, and performs data management. The data is output to the unit 321 (step S352).

  Subsequently, the data management unit 321 satisfies the condition [key = r @ d and registration date / time ≦ t ′ <revocation date / time] from the route information stored in the data storage region 300 (here, the data storage region 300B). Is searched (step S353).

  Then, the data management unit 321 determines whether or not there is a row that satisfies the condition (step S354), and if there is no row that satisfies the condition (step S354 → No), the process proceeds to step S358. On the other hand, if there is a row that satisfies the condition (step S354 → Yes), the data management unit 321 proceeds to the next step S355.

  In step S355, the route information update processing unit 320 updates the expiration date and time of the row satisfying the condition from “∞” to the update date and time t ′ via the data management unit 321.

  Next, the data management unit 321 adds the sub-root key (r @ d) as the key, the update date / time (t ′) as the registration date / time, “∞” as the expiration date / time, and the post-update identifier as value in the route information of the data storage area 300 A line that becomes (i ′) is added (step S356).

  Then, the route information update processing unit 320 generates a route information update response message 71 (see FIG. 22 (d)) indicating that the route information has been updated, and the request source data management device via the transmission / reception unit 340. 3 to finish the process (step S357).

  In step S354, if there is no row satisfying the condition (step S354 → No), the route information update processing unit 320 generates an error message and sends the request source data management device 3 via the transmission / reception unit 340. To finish the process (step S358).

  By doing in this way, the distributed ID management system 5 according to the present embodiment, based on the ID update request message 60 (see FIG. 22A) acquired from the client device 1, "update" in a certain "update target domain" The identifier after “date and time” can be updated from the “update target identifier” registered so far to the “updated identifier” which is a new identifier.

≪Specific example of ID conversion process after ID update process≫
Next, in the distributed ID management system 5 according to the present embodiment, three examples of ID conversion processing after the ID update processing shown in FIG. 21 is performed will be described. The first example and the second example show an example in which the ID conversion process after the ID update process is normally performed, and the third example is an example in which the ID conversion process fails because an illegal ID conversion process request is received. Show. These are examples for explaining that the ID conversion process can be normally executed even after the ID update process.

<ID conversion processing after ID update processing (1)>
First, referring to FIG. 28 and FIG. 29, when the client device 1 requests the gateway device 2 to convert ID (ID conversion request) after the ID update processing is performed, The ID conversion process (1) executed by the data management device 3 will be described.

  Here, as an example of the ID conversion process requested by the client apparatus 1, the identifier (conversion source identifier) “9” in the date (conversion source date) “T3” of the domain (conversion source domain) “D0” is converted into the domain (conversion Destination domain) Processing to convert to an identifier (conversion destination identifier) in the same date (conversion destination date) “T3” of “D1” (that is, a domain corresponding to the identifier “9” in the date “T3” of the domain “D0”) The process of searching for an identifier at the same date “T3” of “D1” will be described. Here, “T3” indicates a future date and time than “T2”.

(Overall flow of ID conversion process)
FIG. 28 is a sequence diagram showing the overall flow of the ID conversion process (1) after the ID update process performed by the distributed ID management system 5 according to the present embodiment. Here, the ID update processing shown in FIG. 21 has already been performed, and the data shown in FIG. 23 is stored in the data storage area 300 of each data management device 3 (3A, 3B, 3C, 3D, 3E). Explain that it is.

  First, the client device 1 transmits an ID conversion request message 40b (40) to the gateway device 2 (step S401).

  FIG. 29A is a diagram illustrating an ID conversion request message 40b (40). The ID conversion request message 40b (40) shown in FIG. 29A includes an identifier (conversion source identifier) “9” in the date (conversion source date) “T3” of the domain (conversion source domain) “D0” as the conversion source. Is converted to the identifier (conversion destination identifier) in the same date (conversion destination date and time) “T3” of the domain (domain after conversion) “D1”.

  Returning to FIG. 28, the gateway device 2 that has received the ID conversion request message 40b performs an index node determination process (step S402). This index node determination process is performed by the node determination unit 212 using the consistent hash method with the index key as a search key. Here, for example, the data management device 3E that is a node corresponding to the index key “9 @ D0” is determined as the index node.

  Subsequently, the gateway device 2 transmits the ID conversion request message 40b (40) to the data management device 3E determined as the index node (step S403).

  The data management device 3E that has received the ID conversion request message 40b (40) performs a root key acquisition process (step S404). The root key is acquired by searching the data storage area 300E (see FIG. 23E) using the index key “9 @ D0” as a key, and the conversion source date and time “T3” is included between the registration date and the expiration date and time. Done from line. Here, “R0” is acquired as the root key from the index shown in FIG.

  Next, the data management device 3E performs a root node determination process (step S405). Here, the data management device 3D is determined as the root node as a node corresponding to the sub-root key “R0 @ D1”.

  Subsequently, the data management device 3E transmits an ID acquisition request message 50b (50) to the data management device 3D determined as the root node (step S406).

  FIG. 29C is a diagram illustrating an ID acquisition request message 50b (50). As shown in FIG. 29 (c), the ID acquisition request message 50b (50) is a request for acquiring an effective identifier at the conversion destination date and time "T3" among the identifiers associated with the sub-root key "R0 @ D1". Indicates that there is.

  Returning to FIG. 28, the data management device 3D that has received the ID acquisition request message 50b (50) performs an ID (identifier) acquisition process (step S407). The ID (identifier) is acquired by searching the data storage area 300D (see FIG. 23D) using the sub-root key “R0 @ D1” as a key, and the conversion date / time “T3” is between the registration date / time and the expiration date / time. It is done from a line that is included in Here, “a” is obtained as the identifier (conversion destination identifier) from the route information shown in FIG.

  Next, the data management device 3D transmits an ID acquisition response message 51b (51) to the data management device 3E (step S408). As shown in FIG. 29D, the ID acquisition response message 51b includes an identifier (conversion destination identifier) “a” acquired as a result of the ID conversion processing.

  Subsequently, the data management device 3E transmits an ID conversion response message 41b (41) to the gateway device 2 (step S409). As shown in FIG. 29B, the ID conversion response message 41b (41) includes the identifier (conversion destination identifier) “a” acquired as a result of the ID conversion processing.

  Then, the gateway device 2 transmits an ID conversion response message 41b (41) to the client device 1 and ends the process (step S410).

  In this way, after the ID update process is performed, when the client apparatus 1 makes an ID conversion request to the gateway apparatus 2, a conversion destination identifier is obtained as a correct conversion result reflecting the result of the ID update process. be able to.

<ID conversion process after ID update process (2)>
Next, referring to FIG. 30 and FIG. 31, when the client apparatus 1 requests the gateway apparatus 2 to convert the ID (ID conversion request) after the ID update process is performed, the gateway apparatus 2 ID conversion processing (2) executed by the data management device 3 will be described.

  Here, as an example of the ID conversion process requested by the client apparatus 1, the identifier (conversion source identifier) “a” in the date (conversion source date) “T3” of the domain (conversion source domain) “D1” is converted into the domain (conversion Destination domain) Processing to convert to the identifier (conversion destination identifier) in the same date (conversion destination date) “T3” of “D0” (that is, the domain corresponding to the identifier “a” in the date “T3” of the domain “D1”) The process of searching for an identifier of “D0” at the same date and time “T3” will be described. Here, “T3” indicates a future date and time than “T2”.

(Overall flow of ID conversion process)
FIG. 30 is a sequence diagram showing an overall flow (2) of the ID conversion process after the ID update process performed by the distributed ID management system 5 according to the present embodiment. Here, the ID update processing shown in FIG. 21 has already been performed, and the data shown in FIG. 23 is stored in the data storage area 300 of each data management device 3 (3A, 3B, 3C, 3D, 3E). Explain that it is.

  First, the client device 1 transmits an ID conversion request message 40c (40) to the gateway device 2 (step S501).

  FIG. 31A is a diagram illustrating an ID conversion request message 40c (40). The ID conversion request message 40c (40) shown in FIG. 31A includes an identifier (conversion source identifier) “a” in the date and time (conversion source date and time) “T3” of the domain (conversion source domain) “D1” as the conversion source. Is converted to an identifier (conversion destination identifier) in the same date (conversion destination date) “T3” of the domain (domain after conversion) “D0”.

  Referring back to FIG. 30, the gateway device 2 that has received the ID conversion request message 40c (40) performs an index node determination process (step S502). This index node determination process is performed by the node determination unit 212 using the consistent hash method with the index key as a search key. Here, for example, the data management device 3C that is a node corresponding to the index key “a @ D1” is determined as the index node.

  Subsequently, the gateway device 2 transmits the ID conversion request message 40c (40) to the data management device 3C determined as the index node (step S503).

  The data management device 3C that has received the ID conversion request message 40c (40) performs a root key acquisition process (step S504). The root key is acquired by searching the data storage area 300C (see FIG. 23C) using the index key “a @ D1” as a key, and the conversion source date / time “T3” is included between the registration date / time and the expiration date / time. Done from line. Here, “R0” is acquired as the root key from the index shown in FIG.

  Next, the data management device 3C performs a root node determination process (step S505). Here, the data management device 3B is determined as the root node as a node corresponding to the sub-root key “R0 @ D0”.

  Subsequently, the data management device 3C transmits an ID acquisition request message 50c (50) to the data management device 3B determined as the root node (step S506).

  FIG. 31C illustrates an ID acquisition request message 50c (50). As shown in FIG. 31 (c), the ID acquisition request message 50c (50) is a request for acquisition of a valid one for the conversion destination date and time "T3" among the identifiers associated with the sub-root key "R0 @ D0". Indicates that there is.

  Returning to FIG. 30, the data management apparatus 3B that has received the ID acquisition request message 50c (50) performs an ID (identifier) acquisition process (step S507). The ID (identifier) is acquired by searching the data storage area 300B (see FIG. 23B) using the sub-root key “R0 @ D0” as a key, and the conversion date / time “T3” is between the registration date / time and the expiration date / time. It is done from a line that is included in Here, “9” is acquired as the identifier (conversion destination identifier) from the route information shown in FIG.

  Next, the data management device 3B transmits an ID acquisition response message 51c (51) to the data management device 3C (step S508). As shown in FIG. 31D, the ID acquisition response message 51c (51) includes an identifier (conversion destination identifier) “9” acquired as a result of the ID conversion process.

  Subsequently, the data management device 3C transmits an ID conversion response message 41c (41) to the gateway device 2 (step S509). As shown in FIG. 31B, the ID conversion response message 41c (41) includes an identifier (conversion destination identifier) “9” acquired as a result of the ID conversion processing.

  Then, the gateway device 2 transmits an ID conversion response message 41c to the client device 1 and ends the process (step S510).

  In this way, after the ID update process is performed, when the client apparatus 1 makes an ID conversion request to the gateway apparatus 2, a conversion destination identifier is obtained as a correct conversion result reflecting the result of the ID update process. be able to.

<ID conversion processing after ID update processing (failure example)>
Next, referring to FIG. 32 and FIG. 33, when the client apparatus 1 requests the gateway apparatus 2 to convert the ID (ID conversion request) after the ID update process is performed, the gateway apparatus 2. ID conversion processing (failure example) executed by the data management device 3 will be described.

  Here, as an example of the ID conversion process requested by the client device 1, the identifier (conversion source identifier) “0” in the date (conversion source date) “T3” of the domain (conversion source domain) “D0” is changed to the domain (conversion). Destination domain) Processing to convert to the identifier (conversion destination identifier) in the same date (conversion destination date) “T3” of “D1” (that is, the domain corresponding to the identifier “0” in the date “T3” of the domain “D0”) The process of searching for an identifier at the same date “T3” of “D1” will be described. Here, “T3” indicates a future date and time than “T2”.

  Further, here, the ID update process shown in FIG. 21 has already been performed, and the data shown in FIG. 23 is stored in the data storage area 300 of each data management device 3 (3A, 3B, 3C, 3D, 3E). As a result of this ID update processing, the identifier of the date “T3” of the domain “D0” is not “0” but updated to “9”. The ID conversion process fails. A processing example in that case is shown.

(Overall flow of ID conversion processing (failure example))
FIG. 32 is a sequence diagram showing the overall flow of the ID conversion process (failure example) after the ID update process performed by the distributed ID management system 5 according to the present embodiment.

  First, the client device 1 transmits an ID conversion request message 40d (40) to the gateway device 2 (step S601).

  FIG. 33A is a diagram illustrating an ID conversion request message 40d (40). The ID conversion request message 40d shown in FIG. 33A includes an identifier (conversion source identifier) “0” in the date (conversion source date) “T3” of the conversion source domain (conversion source domain) “D0”. (Post-conversion domain) Requests processing for conversion to the identifier (conversion destination identifier) in the same date and time (conversion destination date and time) “T3” of “D1”.

  Returning to FIG. 32, the gateway device 2 that has received the ID conversion request message 40d (40) performs an index node determination process (step S602). This index node determination process is performed by the node determination unit 212 using the consistent hash method with the index key as a search key. Here, for example, the data management device 3A that is a node corresponding to the index key “0 @ D0” is determined as the index node.

  Subsequently, the gateway device 2 transmits the ID conversion request message 40d (40) to the data management device 3A determined as the index node (step S603).

  The data management device 3A that has received the ID conversion request message 40d (40) performs a root key acquisition process (step S604). The root key is acquired by searching the data storage area 300A (see FIG. 23A) using the index key (“0 @ D0”) as a key, and the conversion source date / time “T3” is between the registration date / time and the expiration date / time. From the included line. Here, based on the index shown in FIG. 23A, since there is no row in which the conversion source date / time T3 is included between the registration date / time T0 and the expiration date / time T2, the acquisition of the root key fails.

  Next, the data management device 3A transmits an ID conversion response message 41d (41) to the gateway device 2 (step S605). As shown in FIG. 33B, the ID conversion response message 41d (41) includes “null” indicating that the result of the ID conversion process does not exist. The message may include not only “null” but also more detailed error contents.

  Then, the gateway device 2 transmits an ID conversion response message 41d (41) to the client device 1 and ends the process (step S606).

  In this way, when the client apparatus 1 requests the gateway apparatus 2 to convert the ID after the ID update process is performed, an error is returned for the conversion process using the nonexistent identifier. It was shown that

  As described above, according to the distributed ID management method and the distributed ID management system according to the present embodiment, identifiers that are associated with management targets and that can be changed for each domain or date / time are managed. In the system, identifiers are distributed and arranged in each data management device 3, and identifier conversion processing and update processing in which a domain and a date / time are specified can be performed. In addition, by arranging a plurality of data management devices 3 having the same function and distributing the index and route information to each data management device 3, it is possible to easily scale out while suppressing the amount of data to be managed. can do.

DESCRIPTION OF SYMBOLS 1 Client apparatus 2 Gateway apparatus 3 Data management apparatus 4 Communication network 5 Distributed ID management system 10 ID registration request message 11 ID registration response message 20 Route information registration request message 21 Route information registration response message 30 Index registration request message 31 Index registration response message 40 ID conversion request message 41 ID conversion response message 50 ID acquisition request message 51 ID acquisition response message 60 ID update request message 61 ID update response message 70 Route information update request message 71 Route information update response message 100 Gateway information storage area 110, 210 , 310 Control unit 111 ID registration request unit 112 ID conversion request unit 113 ID update request unit 130, 230, 33 Input / output unit 140, 240, 340 Transmit / receive unit 150, 250, 350 Storage unit 200 Node information storage area 211, 311 Node management unit 212, 312 Node determination unit 213 ID registration transfer unit 214 ID conversion transfer unit 215 ID update transfer unit 300 Data storage area 313 Root key generation unit 314 ID registration processing unit 315 ID conversion processing unit 316 ID update processing unit 317 ID acquisition processing unit 318 Index registration processing unit 319 Route information registration processing unit 320 Route information update processing unit 321 Data management unit

Claims (12)

A gateway device that receives a request message from a client device and distributes the received request message to one of a plurality of data management devices; receives the distributed request message; and performs processing indicated in the request message A distributed ID management method of a distributed ID management system comprising the plurality of data management devices to be executed,
The gateway device is
A storage unit for storing connection information indicating addresses of the data management devices;
As the request message, an identifier for identifying a management target, a domain indicating a range in which the identifier is used, and an ID registration request message for requesting storage of registration information indicating a registration date and time are received,
A first data management device that generates an index key that combines the identifier and the domain included in the ID registration request message and stores an index as the registration information is configured based on the generated index key. Determined from the data management device
Sending the ID registration request message to the determined first data management device with reference to the connection information,
The first data management device includes:
Generating a root key that is an identifier for uniquely identifying the management target in the distributed ID management system;
The index key combining the identifier and the domain included in the ID registration request message is generated, and the generated index key and the registration date and time are associated with the root key as the index. Save it in the memory,
Based on the generated sub-root key, a second data management device that generates a sub-root key obtained by combining the domain and the root key included in the ID registration request message and stores route information as the registration information. Determined from the plurality of data management devices;
A route information registration request message including the sub-root key, the registration date and time, and the identifier is transmitted to the determined second data management device;
The second data management device includes:
The distributed ID management method, wherein the sub-root key and the registration date / time included in the route information registration request message are stored in its own storage unit as information corresponding to the identifier as the route information. After the distributed ID management system completes registration of the index and the route information based on the ID registration request message,
The gateway device is
The request message includes (1) a conversion source identifier, a conversion source domain, a conversion source date and time, and (2) a conversion destination domain and a conversion destination date and time, and an ID conversion request that requests a search for the identifier that is the conversion destination Receive the message,
Generating the index key obtained by combining the conversion source identifier of the ID conversion request message and the conversion source domain, and determining the first data management device that stores the index based on the generated index key;
Sending the ID conversion request message to the first data management device with reference to the connection information;
The first data management device includes:
Generating the index key obtained by combining the conversion source identifier and the conversion source domain included in the ID conversion request message, referring to the index using the generated index key and the conversion source date and time as a key, and the route Get the key
The sub-root key obtained by combining the conversion destination domain and the root key included in the ID conversion request message is generated, and the second data management device that stores the route information is determined based on the generated sub-root key. And
An ID acquisition request message including the sub-root key and the conversion destination date and time is transmitted to the determined second data management device;
The second data management device includes:
2. The distributed ID according to claim 1, wherein the identifier that is the conversion destination is acquired by referring to the route information using the sub-root key and the conversion destination date and time included in the ID acquisition request message as keys. Management method. After the distributed ID management system completes registration of the index and the route information based on the ID registration request message,
The gateway device is
The request message includes (1) an update target identifier, an update target domain, an update target date and time, and (2) an after-update identifier and an update date and time, and is the identifier at the update target date and time of the update target domain Receiving an ID update request message requesting to update the update target identifier to the post-update identifier after the update date and time;
Generating the index key obtained by combining the update target identifier of the ID update request message and the update target domain, and determining the first data management device that stores the index based on the generated index key;
Sending the ID update request message to the first data management device with reference to the connection information;
The first data management device includes:
Generate the index key that combines the update target identifier and the update target domain included in the ID update request message, and use the generated index key and the update target date and time as a key to retrieve the index from its storage unit Extract, obtain the root key, register the update date and time as the expiration date of the extracted index,
The sub-root key obtained by combining the update target domain included in the ID update request message and the root key is generated, and the second data management device that stores the route information is determined based on the generated sub-root key. And
A route information update request message including the sub-root key, the update date and time, and the post-update identifier is transmitted to the determined second data management device;
Generating a new index key obtained by combining the post-update identifier and the update target domain included in the ID update request message, and storing the new index based on the generated new index key Determining the data management device;
An index registration request message including the new index key, the update date and time, and the acquired root key is transmitted to the determined third data management device;
The second data management device includes:
Using the sub-root key and the update date / time included in the route information update request message as keys, extract the route information from its own storage unit, and register the update date / time as the expiration date / time of the extracted route information,
The sub-root key and the update date / time included in the route information update request message are stored in its own storage unit as new route information that is associated with the updated identifier,
The third data management device includes:
The new index key and the update date / time included in the index registration request message are stored in its own storage unit with the information associated with the root key as the new index. The distributed ID management method described. A gateway device that receives a request message from a client device and distributes the received request message to one of a plurality of data management devices; receives the distributed request message; and performs processing indicated in the request message A distributed ID management method of a distributed ID management system comprising the plurality of data management devices to be executed,
Each of the plurality of data management devices is communicably connected,
The gateway device and the plurality of data management devices store node information in which connection information indicating addresses of the data management devices and node IDs indicating hash values corresponding to the data management devices are stored. Each has a storage unit,
The gateway device is
As the request message, (1) a first (i = 1) identifier for identifying a management target, a first (i = 1) domain indicating a range in which the first identifier is used, and a registration date and time (2) a second (i = 2) identifier that is another identifier indicating the same management target as the management target indicated by the first identifier, At least a second (i = 2) domain indicating a range in which the second identifier is used, and second (i = 2) registration information indicating a registration date and time, and (i) the first identifier The i th (where i is an integer of 3 or more) identifier indicating the same management target as the management target shown in FIG. 1, the i th (where i is 3 or more) indicating the range in which the i th identifier is used (Integer) domain and the i-th registration (where i is an integer of 3 or more) indicating the registration date and time. Receiving an ID registration request message requesting the information, the registration processing of information which can include,
Generating an index key that combines the first identifier, which is the first identifier of the ID registration request message, and the first domain;
Calculating a hash value by applying a hash function to the generated index key, referring to the node ID of the node information, and determining a first data management device as a distribution destination;
Transmitting the ID registration request message to the determined first data management device with reference to the connection information of the node information; and
The first data management device includes:
Receiving the ID registration request message;
Generating a root key that is an identifier for uniquely identifying the management target in the distributed ID management system;
Based on the ID registration request message, an i-th (i = 1 or greater integer) index key combining an i-th (i = 1 or greater integer) identifier and an i-th (i = 1 or greater integer) domain is Generating step;
A hash function is calculated by applying a hash function to the generated i-th index key, and a registration destination of an i-th index that is an index including the i-th index key is referred to by referring to the node ID of the node information. Determining (2 × i−1) as the data management device;
Generating an index registration request message including the i-th index key, the registration date and time, and the root key, and sending the index registration request message to the (2 × i−1) data management device;
Generating an i-th sub-root key that combines the i-th domain and the root key;
A hash value is calculated by applying a hash function to the generated i-th sub-root key, and a registration destination of i-th route information that is route information including the i-th sub-root key with reference to the node ID of the node information Determining the (2 × i) th data management device;
Generating a route information registration request message including the i-th sub-root key, the registration date and time and the i-th identifier, and transmitting the route information registration request message to the (2 × i) data management device,
The (2 × i−1) th data management device is:
Receiving the index registration request message;
Registering the i-th index, which is information in which the i-th index key and registration date and time are associated with the root key, in the storage unit based on the index registration request message;
The (2 × i) data management device is:
Receiving the route information registration request message;
Performing, based on the route information registration request message, registering the i-th route information, which is information in which the i-th sub-root key and registration date and time are associated with the i-th identifier, in its storage unit. A distributed ID management method characterized by the above. After the distributed ID management system completes registration of the index and the route information based on the ID registration request message,
The gateway device is
As the request message, (1) a first identifier as a conversion source, a first domain as a conversion source, a conversion source date and time as a conversion source date and time, and (2) a second domain as a conversion destination, Receiving an ID conversion request message that includes a conversion destination date and time that is a conversion destination date and that requests a search for a second identifier that is a conversion destination;
Generating the index key obtained by combining the first identifier of the ID conversion request message and the first domain;
Calculating a hash value by applying a hash function to the generated index key, referring to the node ID of the node information, and determining the data management device that is the registration destination of the index;
Transmitting the ID conversion request message to the determined data management device with reference to the connection information of the node information; and
The data management device that is the registration destination of the index is:
Receiving the ID conversion request message;
Based on the ID conversion request message, generates the index key that combines the first identifier and the first domain, refers to the index registered in its storage unit, and generates the index key and Obtaining the root key using the conversion source date and time as a key;
Generating the sub-root key obtained by combining the acquired root key and the second domain included in the ID conversion request message;
Calculating a hash value by applying a hash function to the generated sub-root key, referring to the node ID of the node information, and determining the data management device that is a registration destination of the route information;
Generating an ID acquisition request message including the conversion destination date and time contained in the sub-root key and the ID conversion request message, and transmitting to the determined data management device,
The data management device that is the registration destination of the route information is:
Receiving the ID acquisition request message;
Referring to the route information registered in its own storage unit, obtaining the second identifier as the conversion destination using the sub-root key and the conversion date and time included in the ID acquisition request message as keys,
Generating an ID acquisition response message including the second identifier to be the conversion destination, and transmitting the ID acquisition response message to the data management device that is the registration destination of the index, and
The data management device that is the registration destination of the index is:
Receiving an ID acquisition response message including the second identifier as the conversion destination;
The distributed ID according to claim 4, wherein an ID conversion response message including the second identifier as the conversion destination is generated and transmitted to the client via the gateway device. Management method. After the distributed ID management system completes registration of the index and the route information based on the ID registration request message,
The gateway device is
The request message includes (1) an update target identifier, an update target domain, an update target date and time, and (2) an after-update identifier and an update date and time, and is the identifier at the update target date and time of the update target domain Receiving an ID update request message for requesting an update target identifier to be updated to the post-update identifier after the update date and time;
Generating the index key that combines the update target identifier of the ID update request message and the update target domain;
Calculating a hash value by applying a hash function to the generated index key, referring to the node ID of the node information, and determining the data management device that is the registration destination of the index;
Transmitting the ID update request message with reference to the connection information to the determined data management device, and
The data management device that is the registration destination of the index is:
Receiving the ID update request message;
Generate the index key that combines the update target identifier and the update target domain included in the ID update request message, and use the generated index key and the update target date and time as a key to retrieve the index from its storage unit Extracting, obtaining the root key, and registering the update date and time as an expiration date and time of the extracted index;
Generating the sub-root key obtained by combining the update target domain and the root key included in the ID update request message;
Calculating a hash value by applying a hash function to the generated sub-root key, referring to the node ID of the node information, and determining the data management device that is a registration destination of the route information;
Transmitting a route information update request message including the sub route key, the update date and time, and the updated identifier to the determined data management device;
Generating a new index key that combines the post-update identifier and the update target domain included in the ID update request message;
Calculating a hash value by applying a hash function to the generated new index key, referring to the node ID of the node information, and determining a data management apparatus that is a registration destination of the new index;
Transmitting the second index registration request message including the new index key, the update date and time, and the acquired root key to the determined data management device;
The data management device that is the registration destination of the route information is:
Receiving the route information update request message;
Extracting the route information from its own storage unit using the sub-root key and the update date / time included in the route information update request message as keys, and registering the update date / time as an expiration date / time of the extracted route information;
Registering the sub-root key and the update date / time included in the route information update request message with the information associated with the post-update identifier as new route information in its own storage unit, and
The data management device that is the registration destination of the new index is:
Receiving the second index registration request message;
Registering the new index key and the update date / time included in the second index registration request message in its own storage unit with the information associated with the root key as the new index. The distributed ID management method according to claim 4, wherein: A gateway device that receives a request message from a client device and distributes the received request message to one of a plurality of data management devices; receives the distributed request message; and performs processing indicated in the request message A distributed ID management system comprising the plurality of data management devices to be executed,
The gateway device is
A storage unit for storing connection information indicating addresses of the data management devices;
As the request message, an identifier for identifying a management target, a transmission / reception unit that receives an ID registration request message for requesting storage of registration information indicating a domain and a registration date and time indicating a range in which the identifier is used;
An index key that combines the identifier and the domain included in the ID registration request message is generated, and the first data management device that stores the index as the registration information is referred to the connection information, and the ID An ID registration transfer unit that transmits a registration request message;
A node determination unit that determines the first data management device from the plurality of data management devices based on the index key generated by the ID registration transfer unit;
The first data management device includes:
A root key generation unit that generates a root key that is an identifier for uniquely identifying the management target in the distributed ID management system;
The index key combining the identifier and the domain included in the ID registration request message is generated, and the generated index key and the registration date and time are associated with the root key as the index. Save it in the memory,
A sub-root key obtained by combining the domain and the root key included in the ID registration request message is generated, and the sub-root key and the registration date and time are stored in a second data management device that stores route information as the registration information. An ID registration processing unit that transmits a route information registration request message including the identifier;
A node determination unit that determines the second data management device from the plurality of data management devices based on the sub-root key generated by the ID registration processing unit;
The second data management device includes:
A route information registration processing unit that stores the sub-root key and the registration date / time included in the route information registration request message in the storage unit as information corresponding to the identifier as the route information. A distributed ID management system. The gateway device further includes an ID conversion transfer unit,
The transmission / reception unit of the gateway device includes:
The request message includes (1) a conversion source identifier, a conversion source domain, a conversion source date and time, and (2) a conversion destination domain and a conversion destination date and time, and an ID conversion request that requests a search for the identifier that is the conversion destination Receive the message,
The ID conversion transfer unit
The first data management device that generates the index key obtained by combining the conversion source identifier and the conversion source domain of the ID conversion request message and stores the index is based on the generated index key. Through the decision part
Sending the ID conversion request message to the determined first data management device with reference to the connection information;
The first data management device further includes an ID conversion processing unit,
The ID conversion processing unit
Generating the index key obtained by combining the conversion source identifier and the conversion source domain included in the ID conversion request message, referring to the index using the generated index key and the conversion source date and time as a key, and the route Get the key
Based on the generated sub-root key, the second data management device that generates the sub-root key that combines the conversion-target domain included in the ID conversion request message and the root key, and stores the route information. Determined through the node determination unit,
An ID acquisition request message including the sub-root key and the conversion destination date and time is transmitted to the determined second data management device;
The second data management device further includes an ID acquisition processing unit,
The ID acquisition processing unit
The distributed ID management according to claim 7, wherein the identifier to be the conversion destination is acquired by referring to the route information using the sub-root key and the conversion destination date and time included in the ID acquisition request message as keys. system. The gateway device further includes an ID update transfer unit,
The transmission / reception unit of the gateway device includes:
The request message includes (1) an update target identifier, an update target domain, an update target date and time, and (2) an after-update identifier and an update date and time, and is the identifier at the update target date and time of the update target domain Receiving an ID update request message requesting to update the update target identifier to the post-update identifier after the update date and time;
The ID update transfer unit
Generating the index key obtained by combining the update target identifier of the ID update request message and the update target domain, and determining the first data management device that stores the index based on the generated index key;
Sending the ID update request message to the first data management device with reference to the connection information;
The first data management device further includes an ID update processing unit,
The ID update processing unit
Generate the index key that combines the update target identifier and the update target domain included in the ID update request message, and use the generated index key and the update target date and time as a key to retrieve the index from its storage unit Extract, obtain the root key, register the update date and time as the expiration date of the extracted index,
The sub-root key obtained by combining the update target domain included in the ID update request message and the root key is generated, and the second data management device that stores the route information is determined based on the generated sub-root key. And
A route information update request message including the sub-root key, the update date and time, and the post-update identifier is transmitted to the determined second data management device;
Generating a new index key obtained by combining the post-update identifier and the update target domain included in the ID update request message, and storing the new index based on the generated new index key Determining the data management device;
An index registration request message including the new index key, the update date and time, and the acquired root key is transmitted to the determined third data management device;
The second data management device further includes a route information update processing unit,
The route information update processing unit
Using the sub-root key and the update date / time included in the route information update request message as keys, extract the route information from its own storage unit, and register the update date / time as the expiration date / time of the extracted route information,
The sub-root key and the update date / time included in the route information update request message are stored in its own storage unit as new route information that is associated with the updated identifier,
The third data management device includes an index registration processing unit,
The index registration processing unit
8. The new index key and the update date / time included in the index registration request message are stored in its own storage unit with the information associated with the root key as the new index. The distributed ID management system described. A gateway device that receives a request message from a client device and distributes the received request message to one of a plurality of data management devices; receives the distributed request message; and performs processing indicated in the request message A distributed ID management system comprising the plurality of data management devices to be executed,
Each of the plurality of data management devices is communicably connected,
The gateway device and the plurality of data management devices store node information in which connection information indicating addresses of the data management devices and node IDs indicating hash values corresponding to the data management devices are stored. Each has a storage unit,
The gateway device is
As the request message, (1) a first (i = 1) identifier for identifying a management target, a first (i = 1) domain indicating a range in which the first identifier is used, and a registration date and time (2) a second (i = 2) identifier that is another identifier indicating the same management target as the management target indicated by the first identifier, At least a second (i = 2) domain indicating a range in which the second identifier is used, and second (i = 2) registration information indicating a registration date and time, and (i) the first identifier The i th (where i is an integer of 3 or more) identifier indicating the same management target as the management target shown in FIG. 1, the i th (where i is 3 or more) indicating the range in which the i th identifier is used (Integer) domain and the i-th registration (where i is an integer of 3 or more) indicating the registration date and time. A transceiver for receiving an ID registration request message for requesting information and the registration processing of information, which may include,
First data that generates an index key that combines the first identifier that is the first identifier of the ID registration request message and the first domain, and that is a distribution destination determined by the node determination unit of the gateway device An ID registration transfer unit that sends the ID registration request message to the management device with reference to the connection information of the node information;
The first data management device calculates a hash value by applying a hash function to the index key generated by the ID registration transfer unit, refers to the node ID of the node information, and becomes the distribution destination The node determination unit for determining the first data management device;
The first data management device includes:
A transmission / reception unit for receiving the ID registration request message;
A root key generation unit that generates a root key that is an identifier for uniquely identifying the management target in the distributed ID management system;
Based on the ID registration request message, an i-th (i = 1 or greater integer) index key combining an i-th (i = 1 or greater integer) identifier and an i-th (i = 1 or greater integer) domain is Generate and
An index registration request message including the i-th index key, the registration date and time, and the root key is generated, and the (2 × i−1) -th registration destination of the i-th index that is the index including the i-th index key. To the data management device,
Generating an i-th sub-root key obtained by combining the i-th domain and the root key;
A route information registration request message including the i-th sub-root key, the registration date and time, and the i-th identifier is generated, and the registration destination of the i-th route information that is the route information including the i-th sub-root key is (2 × an ID registration processing unit to be transmitted to the data management device of i);
A hash function is calculated by applying a hash function to the i-th index key generated by the ID registration processing unit, and the registration destination of the i-th index is referred to as the second (2) with reference to the node ID of the node information. Xi-1) is determined as the data management device,
The hash value is calculated by applying a hash function to the i-th sub-root key generated by the ID registration processing unit, and the registration destination of the i-th route information is referred to by referring to the node ID of the node information. A node determining unit that determines the data management device of 2 × i),
The (2 × i−1) th data management device is:
A transmission / reception unit for receiving the index registration request message;
An index registration processing unit that registers the i-th index, which is information in which the i-th index key and registration date and time are associated with the root key, based on the index registration request message in its own storage unit;
The (2 × i) data management device is:
A transmission / reception unit for receiving the route information registration request message;
A route information registration processing unit for registering the i-th route information, which is information in which the i-th sub-root key and registration date and time are associated with the i-th identifier, based on the route information registration request message; A distributed ID management system comprising: The gateway device further includes an ID conversion transfer unit,
The transmission / reception unit of the gateway device,
As the request message, (1) a first identifier as a conversion source, a first domain as a conversion source, a conversion source date and time as a conversion source date and time, and (2) a second domain as a conversion destination, An ID conversion request message that includes a conversion destination date and time that is a conversion destination date and that requests a search for a second identifier that is a conversion destination;
The ID conversion transfer unit
Generating the index key obtained by combining the first identifier of the ID conversion request message and the first domain;
A hash value is calculated by applying a hash function to the generated index key via the node determination unit, and the data management apparatus that is the registration destination of the index is referred to by referring to the node ID of the node information Decide
Sending the ID conversion request message to the data management device, which is the registration destination of the determined index, with reference to the connection information of the node information;
The data management device that is the registration destination of the index further includes an ID conversion processing unit,
The ID conversion processing unit
Based on the received ID conversion request message, generates the index key that combines the first identifier and the first domain, refers to the index registered in its storage unit, and generates the index Using the key and the conversion source date and time as a key, obtain the root key,
Generating the sub-root key obtained by combining the acquired root key and the second domain included in the ID conversion request message;
The data management device which is a registration destination of the route information by calculating a hash value by applying a hash function to the generated sub-root key via the node determination unit and referring to the node ID of the node information Decide
Generate an ID acquisition request message including the conversion destination date and time included in the sub-root key and the ID conversion request message, and transmit the ID acquisition request message to the data management device that is the registration destination of the determined route information.
The data management device that is the registration destination of the route information further includes an ID acquisition processing unit,
The ID acquisition processing unit
With reference to the route information registered in its own storage unit, using the sub-root key and the conversion destination date and time included in the received ID acquisition request message as a key, the second identifier as the conversion destination is acquired,
Generating an ID acquisition response message including the second identifier as the conversion destination, and transmitting the ID acquisition response message to the data management device as the registration destination of the index;
The ID conversion processing unit of the data management device, which is the registration destination of the index,
The ID conversion response message including the second identifier serving as the conversion destination is generated based on the received ID acquisition response message, and is transmitted to the client via the gateway device. The distributed ID management system described. The gateway device further includes an ID update transfer unit,
The transmission / reception unit of the gateway device,
The request message includes (1) an update target identifier, an update target domain, an update target date and time, and (2) an after-update identifier and an update date and time, and is the identifier at the update target date and time of the update target domain Receiving an ID update request message requesting to update the update target identifier to the post-update identifier after the update date and time;
The ID update transfer unit
Generating the index key that combines the update target identifier of the ID update request message and the update target domain;
A hash value is calculated by applying a hash function to the generated index key via the node determination unit, and the data management apparatus that is the registration destination of the index is referred to by referring to the node ID of the node information Decide
Sending the ID update request message to the determined data management device with reference to the connection information;
The data management device that is the registration destination of the index further includes an ID update processing unit,
The ID update processing unit
Generate the index key that combines the update target identifier and the update target domain included in the ID update request message, and use the generated index key and the update target date and time as a key to retrieve the index from its storage unit Extract, obtain the root key, register the update date and time as the expiration date of the extracted index,
Generating the sub-root key that combines the update target domain and the root key included in the ID update request message;
Apply a hash function to the generated sub-root key to calculate a hash value, refer to the node ID of the node information, determine the data management device that is the registration destination of the route information,
A route information update request message including the sub route key, the update date and time, and the updated identifier is transmitted to the determined data management device;
Generating a new index key that combines the post-update identifier and the update target domain included in the ID update request message;
Apply a hash function to the generated new index key to calculate a hash value, refer to the node ID of the node information, determine a data management device that is a new index registration destination,
A second index registration request message including the new index key, the update date and time, and the acquired root key is transmitted to the determined data management device;
The data management device that is the registration destination of the route information further includes a route information update processing unit,
The route information update processing unit
Using the sub-root key and the update date / time included in the route information update request message as keys, extract the route information from its own storage unit, and register the update date / time as the expiration date / time of the extracted route information,
Registering the sub-root key and the update date / time included in the route information update request message as information on the updated identifier in the storage unit thereof as new route information,
The data management device that is the registration destination of the new index includes an index registration processing unit,
The index registration processing unit
The new index key and the update date / time included in the second index registration request message are registered in its own storage unit with information associated with the root key as the new index. Item 11. The distributed ID management system according to Item 10.

Images