Distributed access control system

• US 7,945,670 B2
• Filed: 01/31/2003
• Issued: 05/17/2011
• Est. Priority Date: 01/31/2002
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Nakamura, Hiroaki, Nakamura, Taiga
• Primary Examiner(s): Bruckart; Benjamin R
• Application Number:
  US10/357,038
• Publication Number:
  US 20030163522A1
• Time in Patent Office: 3,028 Days
• Field of Search: 340/5.7, 709217-219, 709/226, 707/104.1
• US Class Current: 709/226
• CPC Class Codes: G07C 9/27 with central registration
• CPC Class Codes: H04L 2463/101 applying security measures for digital rights management data processing systems or methods, specially adapted for commerce, e.g. marketing, shopping, billing, auctions or e-commerce G06Q30/00
• CPC Class Codes: H04L 63/104 Grouping of entities

Abstract

An entrance and exit management system for controlling the entrance and exit at a plurality of management points according to the present invention includes a server connected to a network and managing right information generated from a request for a certain service, a ranking device for generating ranking with respect to the right information and generating sub-right information in response to the ranking, further included is an inquiry information device being responsive to the right information, local servers being connected to the server through the network and placed at the management points, the local server being allowed to make mutual transmissions, and entrance and exit managing means for reading information related to the right information. The means for managing entrance and exit being connected to the local server. Ranking is determined with respect to the relation between the local server and the right information. The server transmits to local servers the sub-right information and the inquiry information having the relation to the ranking of the local servers.

Claims

1. A system for determining whether to allow at least one token to pass through at least one control point, said system comprising:

a plurality of distributed components, each of the distributed components being associated with a given control point and operative;

to store at least a subset of data associated with each token which may be allowed to pass through the control point; and

to determine whether to allow a given token, which may be allowed to pass through the control point, to pass through the control point based at least in part on at least a portion of the data stored by the distributed components; and

a master server operative to determine the subset of data associated with each token to be stored on each of the distributed components associated with a control point through which the token may be allowed to pass;

wherein, for a given token, at least one member of at least a primary subset of the distributed components associated with at least one control point through which the given token may be allowed to pass stores a different subset of the data associated with that token than at least one member of at least a secondary subset of the distributed components associated with at least one control point through which the given token may be allowed to pass.

2. The system of claim 1, wherein at least one member of at least the secondary subset of the distributed components associated with at least one control point through which a given token may be allowed to pass stores a subset of the data associated with the given token that is stored by at least one member of at least the primary subset of the distributed components associated with at least one control point through which the given token may be allowed to pass.

3. The system of claim 1, wherein at least one member of at least the primary subset of the distributed components associated with at least one control point through which a given token may be allowed to pass stores substantially all of the data associated with the given token.

4. The system of claim 1, wherein at least one member of at least the secondary subset of the distributed components associated with at least one control point through which a given token may be allowed to pass requests data from at least one member of at least the primary subset of the distributed components associated with at least one control point through which the given token may be allowed to pass to determine whether the given token is allowed to pass through at least the given control point associated with the at least one member of at least the secondary subset of the distributed components.

5. The system of claim 1, wherein the master server determines the subset of the data associated with a given token to be stored on a given one of the distributed components associated with at least one control point through which the given token may be allowed to pass based at least in part on a probability that the given token will attempt to pass through the at least one control point associated with the given distributed component.

6. The system of claim 1, wherein a given token is not allowed to pass through a control point associated with at least one of the distributed components which contains no data associated with the given token.

7. The system of claim 1, wherein at least one of the distributed components determines whether to allow a given token which may be allowed to pass through at least one control point to pass through the at least one control point based at least in part on at least a portion of a transmission from the master server.

8. The system of claim 1, wherein the master server is further operative to transmit updated data associated with at least one token to the distributed components associated with a control point through which the token may be allowed to pass based at least in part on input received from at least one of (i) an external data source and (ii) at least one of the distributed components.

9. A method for determining whether to allow at least one token to pass through at least one control point, said method comprising the steps of:

for each control point through which a given token may be allowed to pass, determining a subset of data associated with each token which may be allowed to pass through the control point to be stored on at least one of a plurality of distributed components associated with at least the control point; and

determining whether to allow the given token which may be allowed to pass through the control point based at least in part on at least a portion of the data stored by the at least one distributed component associated with the control point;

wherein, for the given token, members of at least a primary subset of the distributed components associated with at least one control point through the which the given token may be allowed to pass stores a different subset of the data associated with that token than members of at least a secondary subset of the distributed components associated with at least one control point through which the given token may be allowed to pass.

10. The method of claim 9, wherein at least one member of at least the secondary subset of the distributed components associated with at least one control point through which a given token may be allowed to pass stores a subset of the data associated with the given token that is stored by at least one member of at least the primary subset of the distributed components associated with at least one control point through which the given token may be allowed to pass.

11. The method of claim 9, wherein at least one member of at least the primary subset of the distributed components associated with at least one control point through which a given token may be allowed to pass stores substantially all of the data associated with the given token.

12. The method of claim 9, wherein at least one member of at least the secondary subset of the distributed components associated with at least one control point through which a given token may be allowed to pass requests data from at least one member of at least the primary subset of the distributed components associated with at least one control point through which the given token may be allowed to pass to determine whether the given token is allowed to pass through at least the given control point associated with the at least one member of at least the secondary subset.

13. The method of claim 9, wherein the master server determines the subset of the data associated with a given token to be stored on a given one of the distributed components associated with at least one control point through which the given token may be allowed to pass based at least in part on a probability that the given token will attempt to pass through the at least one control point associated with the given distributed component.

14. The method of claim 9, wherein a token is not allowed to pass through a control point associated with at least one of the distributed components which contains no data associated with that token.

15. The method of claim 9, wherein the at least one of the distributed components determines whether to allow a given token which may be allowed to pass through at least one control point to pass through the at least one control point based at least in part on at least a portion of a transmission from the master server.

16. The method of claim 9, wherein the master server is further adapted for transmitting updated data associated with at least a given token to the distributed components associated with a control point through which the given token may be allowed to pass based at least in part on input received from at least one of (i) an external data source and (ii) at least one of the distributed components.

17. An article of manufacture for determining whether to allow at least one token to pass through at least one control point, comprising a non-transitory machine readable storage medium containing one or more programs which when executed implement the steps of:

for each control point through which a given token may be allowed to pass, determining a subset of data associated with each token which may be allowed to pass through the control point to be stored on at least one of a plurality of distributed components associated with at least the control point; and

determining whether to allow the given token which may be allowed to pass through the control point based at least in part on at least a portion of the data stored by the at least one distributed component associated with the control point;

wherein, for the given token, members of at least a primary subset of the distributed components associated with at least one control point through the which the given token may be allowed to pass stores a different subset of the data associated with that token than members of at least a secondary subset of the distributed components associated with at least one control point through which the given token may be allowed to pass.

18. The article of claim 17, wherein at least one member of at least the secondary subset of the distributed components associated with at least one control point through which a given token may be allowed to pass stores a subset of the data associated with the given token that is stored by at least one member of at least the primary subset of the distributed components associated with at least one control point through which the given token may be allowed to pass.

19. The article of claim 17, wherein at least one member of at least the primary subset of the distributed components associated with at least one control point through which a given token may be allowed to pass stores substantially all of the data associated with the given token.

20. The article of claim 17, wherein at least one member of the at least the secondary subset of the distributed components associated with at least one control point through which a given token may be allowed to pass requests data from at least one member of at least the primary subset of the distributed components associated with at least one control point through which the given token may be allowed to pass to determine whether the given token is allowed to pass through at least the given control point associated with the at least one member of at least the secondary subset.

21. The article of claim 17, wherein the master server determines the subset of the data associated with a given token to be stored on a given one of the distributed components associated with at least one control point through which the given token may be allowed to pass based at least in part on a probability that the given token will attempt to pass through the at least one control point associated with the given distributed component.

22. The article of claim 17, wherein a given token is not allowed to pass through a control point associated with at least one of the distributed components which contains no data associated with the given token.

23. The article of claim 17, wherein the at least one of the distributed components determines whether to allow a given token which may be allowed to pass through at least one control point to pass through the at least one control point based at least in part on at least a portion of a transmission from the master server.

24. The article of claim 17, wherein the master server is further operative to transmit updated data associated with at least one token to the distributed components associated with a control point through which the token may be allowed to pass based at least in part on input received from at least one of (i) an external data source and (ii) at least one of the distributed components.