ID issuing system and ID issuing server used therein

• US 20090294532A1
• Filed: 05/29/2009
• Published: 12/03/2009
• Est. Priority Date: 05/29/2008
• Status: Abandoned Application

• Current Assignee: Seiko Epson Corporation (Seiko Group)
• Original Assignee: Seiko Epson Corporation (Seiko Group)
• Inventors: Matsunaga, Kosuke, Togashi, Koki, Ichimura, Minoru, Tokonami, Eiichi
• Application Number:
  US12/455,251
• Publication Number:
  US 20090294532A1
• Time in Patent Office: Days
• US Class Current: 235/385
• CPC Class Codes: G06Q 10/00 Administration; Management

Abstract

An ID issuing system that issues an ID in response to a request from a client includes: a plurality of ID issuing servers that execute issuance of the ID; and a history management device that manages the ID, which is issued by each of the plurality of ID issuing servers, by a history table. Either an issued state or a reserved state, which is a reserved but non-issued state, is registered as a status of an issuance history of the ID in the history table. Each of the plurality of ID issuing servers includes: a unit that registers an issuance history, in which the status is a reserved state, as an issuance history of an issue-wanted ID in the history table through the history management device before issuing the issue-wanted ID to the client in response to a request of the issue-wanted ID from the client; a unit that checks whether or not another issuance history different from the issuance history of the registered issue-wanted ID, which corresponds to the same ID as the issue-wanted ID, exists among issuance histories registered in the history table through the history management device regardless of the status; a unit that issues the issue-wanted ID and changes the status of the issuance history of the issue-wanted ID to an issued state through the history management device when another issuance history corresponding to the same ID as the issue-wanted ID does not exist; and a unit that stops issuing the issue-wanted ID when another issuance history corresponding to the same ID as the issue-wanted ID exists.

Claims

1. An ID issuing system that issues an ID in response to a request from a client, comprising:

a plurality of ID issuing servers that execute issuance of the ID; and

a history management device that manages the ID, which is issued by each of the plurality of ID issuing servers, by a history table,

wherein either an issued state or a reserved state, which is a reserved but non-issued state, is registered as a status of an issuance history of the ID in the history table, and

each of the plurality of ID issuing servers includes;

a unit that registers an issuance history, in which the status is a reserved state, as an issuance history of an issue-wanted ID in the history table through the history management device before issuing the issue-wanted ID to the client in response to a request of the issue-wanted ID from the client;

a unit that checks whether or not another issuance history different from the issuance history of the registered issue-wanted ID, which corresponds to the same ID as the issue-wanted ID, exists among issuance histories registered in the history table through the history management device regardless of the status;

a unit that issues the issue-wanted ID and changes the status of the issuance history of the issue-wanted ID to an issued state through the history management device when another issuance history corresponding to the same ID as the issue-wanted ID does not exist; and

a unit that stops issuing the issue-wanted ID when another issuance history corresponding to the same ID as the issue-wanted ID exists.

2. The ID issuing system according to claim 1,

wherein registration of the issuance history of the issue-wanted ID into the history table is executed using, as table management keys, processing date and time acquired by reception of the request from the client and a processing ID for distinguishing issuance histories of the same processing date and time.

3. The ID issuing system according to claim 2,

wherein checking of another issuance history corresponding to the same ID as the issue-wanted ID is executed by checking whether or not there is an issuance history with the same table management keys.

4. The ID issuing system according to claim 3,

wherein checking of another issuance history corresponding to the same ID as the issue-wanted ID is executed by checking whether or not there is an issuance history, in which the same ID as the issue-wanted ID is included and the status is a reserved state, among existing issuance histories when the issuance histories with the same table management keys exist.

5. The ID issuing system according to claim 4,

wherein checking of another issuance history corresponding to the same ID as the issue-wanted ID is executed by checking whether or not an issuance history corresponding to the same ID as the issue-wanted ID exists among issuance histories with different table management keys when there is no issuance history in which the status is a reserved state.

6. The ID issuing system according to claim 3,

wherein checking of another issuance history corresponding to the same ID as the issue-wanted ID is executed by checking whether or not an issuance history corresponding to the same ID as the issue-wanted ID exists among issuance histories with different table management keys when there is no issuance history with the same table management keys.

7. The ID issuing system according to claim 5,

wherein in checking of another issuance history corresponding to the same ID as the issue-wanted ID, an issuance history with processing date and time, which is older than processing date and time of the issuance history of the issue-wanted ID by a predetermined amount, among issuance histories in which the status is a reserved state is excluded from objects to be checked.

8. An ID issuing server that issues an ID in response to a request from a client using a history table in which either an issued state or a reserved state, which is a reserved but non-issued state, is registered as a status of an issuance history of an ID, comprising:

a unit that registers an issuance history, in which the status is a reserved state, as an issuance history of an issue-wanted ID in the history table before issuing the issue-wanted ID to the client in response to a request of the issue-wanted ID from the client;

a unit that checks whether or not another issuance history different from the issuance history of the registered issue-wanted ID, which corresponds to the same ID as the issue-wanted ID, exists among issuance histories registered in the history table regardless of the status;

a unit that issues the issue-wanted ID and changes the status of the issuance history of the issue-wanted ID to an issued state when another issuance history corresponding to the same ID as the issue-wanted ID does not exist; and

a unit that stops issuing the issue-wanted ID when another issuance history corresponding to the same ID as the issue-wanted ID exists.

9. A method of issuing a specific ID in response to a request from a client using a history table in which either an issued state or a reserved state, which is a reserved but non-issued state, is registered as a status of an issuance history of an ID, comprising:

registering an issuance history, in which the status is a reserved state, as an issuance history of an issue-wanted ID in the history table before issuing the issue-wanted ID to the client in response to a request from the client;

checking whether or not another issuance history different from the issuance history of the registered issue-wanted ID, which corresponds to the same ID as the issue-wanted ID, exists among issuance histories registered in the history table regardless of the status;

issuing the issue-wanted ID and changing the status of the issuance history of the issue-wanted ID to an issued state when another issuance history corresponding to the same ID as the issue-wanted ID does not exist; and

stopping issuing the issue-wanted ID when another issuance history corresponding to the same ID as the issue-wanted ID exists.