Patent US5506961A successfully refreshed from Google Patents.
US5506961A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Connection authorizer for controlling access to system resources
Assignee: International Business Machines Corp
•
Filing: 1994-10-17
•
Granted: 1996-04-09
•
Expires: 2014-10-17
Abstract
Abstract A peer to peer connection authorizer is described. The connection authorizer involves three different entities: a system authorizer mechanism, a client connection manager, and a server connection manager. The system authorizer resides on the main or primary CPU while the client and server connection managers reside on individual IOPs. To obtain information required by a user and/or an application program, the client connection manager issues a request to the system authorizer. When the system authorizer receives the request, it first verifies that the client device is who it claims to be. If the system authorizer determines that the client device should be allowed to access the requested information, it then sends a token to the server device and a copy of the same token to the client device. Upon receipt of the token copy from the system authorizer, the client connection manager packages the token copy into a message that it sends to the server device. When the server connection manager receives the message from the client device, it compares the token copy to the token it received from the system authorizer. If the tokens match, the server connection manager responds to the client device and the connection is established.
Inventors
- 👤 Brent A. Carlson
- 👤 Frederic L. Huss
- 👤 Nancy M. Schmucki
- 👤 Richard E. Zelenski
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-29 13:55
CPC Classifications
G; G06; G06F; G06F21/00; G06F21/70; G06F21/82; G06F21/85; G06F12/00; G06F12/14; G06F12/1408; G06F21/30; G06F21/31; G06F21/33; G06F21/335; G06F21/60; G06F21/606
Claims Analysis
Total Claims: 49
Claim 1
Independent Claim
241 words
A method for communicating data, said method comprising the steps of: requesting access to system resources via notification to a system authorizer, said access being requested by a first Input-Output Processor (IOP)Connection manager, said first connection manager residing on a first IOP, said first IOP being connected to a bus; sending an authorization token in response to said requesting step, said authorization token being sent from said system authorizer mechanism to a second IOP connection manager, said second IOP connection manager residing on a second IOP, said second IOP being connected to said bus, said authorization token being sent as part of a first message, said first message being transmitted on said bus; sending a copy of said authorization token from said system authorizer to said first IOP connection manager, said authorization token being sent as part of a second message, said second message being transmitted on said bus; requesting a connection with second IOP connection manager, said connection being requested by said first IOP connection manager via a third message, said third message comprising said copy of said token, said third message being transmitted via said bus; validating said copy of said authorization token, said copy of said authorization token being validated by said second IOP connection manager; and connecting said first and said second IOPs across said bus when said copy of said authorization token has been validated by said validating step and thereby permitting access to system resources.
Claim 2
Independent Claim
241 words
A method for communicating data, said method comprising the steps of: requesting access to system resources via notification to a system authorizer, said access being requested by a first Input-Output Processor (IOP)Connection manager, said first connection manager residing on a first IOP, said first IOP being connected to a bus; sending an authorization token in response to said requesting step, said authorization token being sent from said system authorizer mechanism to a second IOP connection manager, said second IOP connection manager residing on a second IOP, said second IOP being connected to said bus, said authorization token being sent as part of a first message, said first message being transmitted on said bus; sending a copy of said authorization token from said system authorizer to said first IOP connection manager, said authorization token being sent as part of a second message, said second message being transmitted on said bus; requesting a connection with second IOP connection manager, said connection being requested by said first IOP connection manager via a third message, said third message comprising said copy of said token, said third message being transmitted via said bus; validating said copy of said authorization token, said copy of said authorization token being validated by said second IOP connection manager; and connecting said first and said second IOPs across said bus when said copy of said authorization token has been validated by said validating step and thereby permitting access to system resources.
Claim 3
Dependent Claim
21 words
The method of claim 1 wherein said sending an authorization token step comprises the step of sending a generic authorization token.
Claim 4
Dependent Claim
21 words
The method of claim 1 wherein said sending an authorization token step comprises the step of sending a reusable authorization token.
Claim 5
Dependent Claim
21 words
The method of claim 1 wherein said sending an authorization token step comprises the step of sending a single-use authorization token.
Claim 6
Dependent Claim
20 words
The method of claim 1 wherein said sending an authorization token step comprises the step of encrypting said authorization token.
Claim 7
Dependent Claim
26 words
The method of claim 5 wherein said sending a copy of said authorization token step comprises the step of encrypting said copy of said authorization token.
Claim 8
Dependent Claim
24 words
The method of claim 6 wherein said validating step comprises the step of decrypting said authorization token and said copy of said authorization token.
Claim 9
Dependent Claim
26 words
The method of claim 1 wherein said connecting step comprises the step of reporting the outcome of said validating step to said client IOP connection manager.
Claim 10
Dependent Claim
24 words
The method of claim 1 wherein said establishing step comprises the step of reporting the outcome of said validating step to said system authorizer.
Claim 11
Dependent Claim
35 words
The method of claim 1 wherein said sending an authorization token step comprises the step of sending said authorization token to a first server IOP connection manager and to a second server IOP connection manager.
Claim 12
Dependent Claim
39 words
The method of claim 1 wherein said sending a copy of said authorization token step comprises the step of sending said copy of said authorization token to a first client connection manager and to a second client connection manager.
Claim 13
Dependent Claim
39 words
The method of claim 10 wherein said sending a copy of said authorization token step comprises the step of sending said copy of said authorization token to a first client connection manager and to a second client connection manager.
Claim 14
Independent Claim
153 words
A method for communicating data between an interconnected client entity and server entity, said method comprising the steps of: issuing a request for data, said request being issued by said client entity; receiving in conjunction with said request an authorization token, said authorization token being received at said server entity, said authorization token being sent from an authorizer entity, said authorizer entity being connected to said client entity and said server entity; sending a copy of said authorization token from said authorizer entity to said client entity; requesting a connection, said connection being requested via a message sent from said client entity to said server entity, said message comprising a copy of said authorization token; validating said copy of said authorization token, said copy of said authorization token being validated by said server entity; and establishing a connection between said server entity and said client entity when said authorization token has been validated.
Claim 15
Independent Claim
153 words
A method for communicating data between an interconnected client entity and server entity, said method comprising the steps of: issuing a request for data, said request being issued by said client entity; receiving in conjunction with said request an authorization token, said authorization token being received at said server entity, said authorization token being sent from an authorizer entity, said authorizer entity being connected to said client entity and said server entity; sending a copy of said authorization token from said authorizer entity to said client entity; requesting a connection, said connection being requested via a message sent from said client entity to said server entity, said message comprising a copy of said authorization token; validating said copy of said authorization token, said copy of said authorization token being validated by said server entity; and establishing a connection between said server entity and said client entity when said authorization token has been validated.
Claim 16
Dependent Claim
15 words
The method of claim 13 wherein said receiving step comprises receiving a generic authorization token.
Claim 17
Dependent Claim
18 words
The method of claim 13 wherein said receiving step comprises the step of receiving a reusable authorization token.
Claim 18
Dependent Claim
18 words
The method of claim 13 wherein said receiving step comprises the step of receiving a single-use authorization token.
Claim 19
Dependent Claim
17 words
The method of claim 13 wherein said receiving step comprises the step of encrypting said authorization token.
Claim 20
Dependent Claim
20 words
The method of claim 17 wherein said sending step comprises the step of encrypting said copy of said authorization token.
Claim 21
Dependent Claim
17 words
The method of claim 18 wherein said validating step comprises the step of decrypting said authorization token.
Claim 22
Dependent Claim
24 words
The method of claim 13 wherein said establishing step comprises the step of reporting the outcome of said validating step to said client entity.
Claim 23
Dependent Claim
24 words
The method of claim 13 wherein said establishing step comprises the step of reporting the outcome of said validating step to said authorizer entity.
Claim 24
Dependent Claim
28 words
The method of claim 13 wherein said receiving step comprises the step of receiving said authorization token at a first server entity and at a second server entity.
Claim 25
Dependent Claim
30 words
The method of claim 13 wherein said sending step comprises the step of sending said copy of said authorization token to a first client entity and a second client entity.
Claim 26
Dependent Claim
30 words
The method of claim 22 wherein said sending step comprises the step of sending said copy of said authorization token to a first client entity and a second client entity.
Claim 27
Independent Claim
151 words
A method for communicating data between an interconnected client entity and server entity, said method comprising the steps of: issuing a request for data, said request being issued by said client entity; receiving in conjunction with said request an authorization token, said authorization token being received at said client entity, said authorization token being sent from an authorizer entity, said authorizer entity being connected to said client entity and said server entity; requesting a connection between said entity and a server entity, said connection being requested via a first message sent from said client entity to said server entity, said message comprising said authorization token; receiving said first message at said server entity, validating said authorization token and responding to said request for data via a second message; and establishing a connection between said client entity and said server entity when said second message indicates that said authorization token been calibrated
Claim 28
Independent Claim
151 words
A method for communicating data between an interconnected client entity and server entity, said method comprising the steps of: issuing a request for data, said request being issued by said client entity; receiving in conjunction with said request an authorization token, said authorization token being received at said client entity, said authorization token being sent from an authorizer entity, said authorizer entity being connected to said client entity and said server entity; requesting a connection between said entity and a server entity, said connection being requested via a first message sent from said client entity to said server entity, said message comprising said authorization token; receiving said first message at said server entity, validating said authorization token and responding to said request for data via a second message; and establishing a connection between said client entity and said server entity when said second message indicates that said authorization token been calibrated
Claim 29
Dependent Claim
15 words
The method of claim 25 wherein said receiving step comprises receiving a generic authorization token.
Claim 30
Dependent Claim
18 words
The method of claim 25 wherein said receiving step comprises the step of receiving a reusable authorization token.
Claim 31
Dependent Claim
18 words
The method of claim 25 wherein said receiving step comprises the step of receiving a single-use authorization token.
Claim 32
Dependent Claim
24 words
The method of claim 25 wherein said establishing step comprises the step of reporting the outcome of said validating step to said authorizer entity.
Claim 33
Dependent Claim
17 words
The method of claim 25 wherein said validating step comprises the step of encrypting said authorization token.
Claim 34
Dependent Claim
17 words
The method of claim 25 wherein said validating step comprises the step of decrypting said authorization token.
Claim 35
Independent Claim
225 words
An apparatus for communicating data, said apparatus comprising: means for requesting access to system resources, said access being requested by a first connection manager, said first Input-Output-(IOP) connection manager residing on a first IOP, said first IOP being connected to a bus; means for sending an authorization token in response to said requesting step, said authorization token being sent from a system authorizer mechanism to a second IOP connection manager, said second IOP connection manager residing on a second IOP, said second IOP being connected to said bus said authorization token being sent as part of a first message, said first message being transmitted on said bus; means for sending a copy of said authorization token from said system authorizer to said first IOP connection mangager, said authorization token being sent as part of a second message, said second message being transmitted on said bus; means for requesting a connection with said second IOP connection manager, said connection being requested via a third message, said third message comprising said copy of said token, said third message being transmitted via said bus; means for validating said copy of said authorization token, said copy of said authorization token being validated by said second IOP connection manager; and means for connecting said first and said second IOPs across said bus based on the outcome of said validating step.
Claim 36
Independent Claim
225 words
An apparatus for communicating data, said apparatus comprising: means for requesting access to system resources, said access being requested by a first connection manager, said first Input-Output-(IOP) connection manager residing on a first IOP, said first IOP being connected to a bus; means for sending an authorization token in response to said requesting step, said authorization token being sent from a system authorizer mechanism to a second IOP connection manager, said second IOP connection manager residing on a second IOP, said second IOP being connected to said bus said authorization token being sent as part of a first message, said first message being transmitted on said bus; means for sending a copy of said authorization token from said system authorizer to said first IOP connection mangager, said authorization token being sent as part of a second message, said second message being transmitted on said bus; means for requesting a connection with said second IOP connection manager, said connection being requested via a third message, said third message comprising said copy of said token, said third message being transmitted via said bus; means for validating said copy of said authorization token, said copy of said authorization token being validated by said second IOP connection manager; and means for connecting said first and said second IOPs across said bus based on the outcome of said validating step.
Claim 37
Dependent Claim
20 words
The apparatus of claim 32 wherein said means for sending authorization token comprises means for sending a generic authorization token.
Claim 38
Dependent Claim
21 words
The apparatus of claim 32 wherein said means for sending an authorization token comprises means for sending a reusable authorization token.
Claim 39
Dependent Claim
21 words
The apparatus of claim 32 wherein said means for sending an authorization token comprises means for sending a single-use authorization token.
Claim 40
Dependent Claim
27 words
The apparatus of claim 32 wherein said means for connecting comprises means for reporting the outcome of said means for validating to said client IOP connection manager.
Claim 41
Dependent Claim
25 words
The apparatus of claim 32 wherein said means for establishing comprises means for reporting the outcome of said means for validating to said system authorizer.
Claim 42
Independent Claim
164 words
An apparatus for communicating data between an interconnected client entity and server entity, said apparatus comprising: means for issuing a request for data, said request being issued by said client entity; means for receiving in conjunction with said request an authorization token, said authorization token being received at said server entity, said authorization token being sent from a authorizer entity, said authorizer entity being connected to said client and entity and to said server entity; means for sending a copy of said authorization token from said authorizer entity to said client entity; means for requesting a connection, said connection being requested via a message sent from said client entity to said server entity, said message comprising a copy of said authorization token; means for validating said copy of said authorization token, said copy of said authorization token being validated by said server enitity; and means for establishing a connection between said server entity and said client entity when said authorization token has been validated.
Claim 43
Independent Claim
164 words
An apparatus for communicating data between an interconnected client entity and server entity, said apparatus comprising: means for issuing a request for data, said request being issued by said client entity; means for receiving in conjunction with said request an authorization token, said authorization token being received at said server entity, said authorization token being sent from a authorizer entity, said authorizer entity being connected to said client and entity and to said server entity; means for sending a copy of said authorization token from said authorizer entity to said client entity; means for requesting a connection, said connection being requested via a message sent from said client entity to said server entity, said message comprising a copy of said authorization token; means for validating said copy of said authorization token, said copy of said authorization token being validated by said server enitity; and means for establishing a connection between said server entity and said client entity when said authorization token has been validated.
Claim 44
Independent Claim
158 words
An apparatus for communicating data between an interconnected client entity and server entity, said apparatus comprising: means for issuing a request for data, said request being issued by said client entity; means for receiving in conjunction with said request an authorization token, said authorization token being received at said client entity, said authorization token being sent from an authorizer entity being connected to said client entity and to said server entity; means for requesting a connection between said client entity and said server entity, said connection being requested via a first message sent from said client entity to said server entity, said message comprising said authorization token; means for receiving said first message at said server entity, validating said authorization token and responding to said request for data via a second message; and means for establishing a connection between said client entity and said server entity when said second message indicates that said authorization token has been validated.
Claim 45
Independent Claim
158 words
An apparatus for communicating data between an interconnected client entity and server entity, said apparatus comprising: means for issuing a request for data, said request being issued by said client entity; means for receiving in conjunction with said request an authorization token, said authorization token being received at said client entity, said authorization token being sent from an authorizer entity being connected to said client entity and to said server entity; means for requesting a connection between said client entity and said server entity, said connection being requested via a first message sent from said client entity to said server entity, said message comprising said authorization token; means for receiving said first message at said server entity, validating said authorization token and responding to said request for data via a second message; and means for establishing a connection between said client entity and said server entity when said second message indicates that said authorization token has been validated.
Claim 46
Dependent Claim
18 words
The apparatus of claim 39 wherein said means for receiving comprises means for receiving a generic authorization token.
Claim 47
Dependent Claim
18 words
The apparatus of claim 39 wherein said means for receiving comprises means for receiving a reusable authorization token.
Claim 48
Dependent Claim
18 words
The apparatus of claim 39 wherein said means for receiving comprises means for receiving a single-use authorization token.
Claim 49
Dependent Claim
24 words
The apparatus of claim 39 wherein said means for establishing comprises means for reporting the outcome of said validating step to said authorizer entity.
References Cited (Backward Citations)
US4450535A
Cited
US4583088A
Cited
US4590468A
Cited
US4780871A
Cited
US4817140A
Cited
US5146575A
Cited
US5023773A
Cited
US5113499A
Cited
US5325430A
Cited
US5237614A
Cited
US5202999A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 1999-04-09 | 1999-10-09 | 2000-04-09 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2003-04-09 | 2003-10-09 | 2004-04-09 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2007-04-09 | 2007-10-09 | 2008-04-09 | $7700.00 | Window Closed / Lapsed |