EP0588415A1
Expired / Lapsed
EP
⏱️ 0.0 years remaining
Peer to peer connection authorizer
Assignee: International Business Machines Corp
•
Filing: 1993-09-03
•
Granted: —
•
Expires: 2013-09-03
Abstract
Abstract A peer to peer connection authorizer is disclosed. 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 Allen Carlson
- 👤 Frederic Lawrence Huss
- 👤 Nancy Marie Schmucki
- 👤 Richard Elmer Zelenski
Bibliographic Details
Application Number
—
Jurisdiction
EP
Data Source
google_patents
Last Synchronized
2026-11-08 17:12
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: 16
Claim 1
Independent Claim
207 words
A method for communicating data, said method comprising the steps of: - requesting access to system resources, said access being requested by a first connection manager, said first connection manager residing on a first IOP; - 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 authorization token being sent as part of a first message, said first message being transmitted on a 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 said first 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; - validating said copy of said authorization token, said copy of said authorization token being validated by said second IOP connection manager; - establishing a connection between said first and said second IOPs across said bus based on the outcome of said validating step.
Claim 2
Dependent Claim
63 words
The method of claim 1 wherein said sending an authorization token step comprises at least one of the following steps: - sending a generic authorization token; - sending a reusable authorization token; - sending a single-use authorization token; - encrypting said authorization token; - sending said authorization token to a first server IOP connection manager and to a second server IOP connection manager.
Claim 3
Independent Claim
137 words
A method for communicating data between a client entity and a server entity, said method comprising the steps of: - issuing a request for data; - 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; - 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; - establishing a connection between said server entity and said client entity when said authorization token has been validated.
Claim 4
Independent Claim
73 words
The method of any of the preceding claims wherein said sending a copy of said authorization token step comprises at least one of the following steps: - encrypting said copy of said authorization token; - sending said copy of said authorization token to a first client connection manager and to a second client connection manager; - sending said copy of said authorization token to a first client entity and a second client entity.
Claim 5
Independent Claim
104 words
A method for communicating data, said method comprising the steps of: - issuing a request for data; - receiving in conjunction with said request an authorization token, said authorization token being received at a client entity, said authorization token being sent from an authorizer entity; - requesting a connection between said client 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; - establishing a connection between said client entity and said server entity based on a response received as a result of said requesting step.
Claim 6
Independent Claim
70 words
The method of any of the preceding claims wherein said establishing step comprises at least one of the following steps: - reporting the outcome of said validating step to said client IOP connection manager; - reporting the outcome of said validating step to said system authorizer; - reporting the outcome of said validating step to said client entity; - reporting the outcome of said validating step to said authorizer entity.
Claim 7
Independent Claim
94 words
A method for communicating data between a client entity and a server entity, said method comprising the steps of: - receiving in conjunction with a request for data a first authorization token, said authorization token being received at said server entity, said authorization token being sent from an authorizer entity; - validating a second authorization token, said validation being done by comparing said second authorization token with said first authorization token, said second authorization token being received as part of a request to establish a connection between said server entity and said client entity.
Claim 8
Independent Claim
59 words
The method of any of the preceding claims wherein said receiving step comprises at least one of the following steps: - encrypting said authorization token; - receiving said authorization token at a first server entity and at a second server entity; - receiving a generic authorization token; - receiving a reusable authorization token; - receiving a single-use authorization token.
Claim 9
Independent Claim
42 words
The method of any of the preceding claims wherein said validating step comprises at least one of the following steps: - encrypting said authorization token; - decrypting said authorization token; - decrypting said authorization token and said copy of said authorization token.
Claim 10
Independent Claim
216 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 connection manager residing on a first IOP; - 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 authorization token being sent as part of a first message, said first message being transmitted on a bus; - means for 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; - means for requesting a connection with said first 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; - means for establishing a connection between said first and said second IOPs across said bus based on the outcome of said validating step.
Claim 11
Dependent Claim
44 words
The apparatus of claim 36 wherein said means for sending authorization token comprises at least one of the following means: - means for sending a generic authorization token; - means for sending a reusable authorization token; - means for sending a single-use authorization token.
Claim 12
Independent Claim
145 words
An apparatus for communicating data between a client entity and a server entity, said apparatus comprising: - means for issuing a request for data; - 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; - 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 entity; - means for establishing a connection between said server entity and said client entity when said authorization token has been validated.
Claim 13
Independent Claim
109 words
An apparatus for communicating data, said apparatus comprising: - means for issuing a request for data; - means for receiving in conjunction with said request an authorization token, said authorization token being received at a client entity, said authorization token being sent from an authorizer entity; - means for requesting a connection between said client 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; - means for establishing a connection between said client entity and said server entity based on a response received as a result of said requesting step.
Claim 14
Independent Claim
67 words
The apparatus of any of the preceding claims wherein said means for establishing comprises at least one of the following means: - means for reporting the outcome of said means for validating to said client IOP connection manager; - means for reporting the outcome of said means for validating to said system authorizer; - means for reporting the outcome of said validating step to said authorizer entity;
Claim 15
Independent Claim
95 words
An apparatus for communicating data between a client entity and a server entity, said apparatus comprising: - means for receiving in conjunction with a request for data a first authorization token, said authorization token being received at said server entity, said authorization token being sent from an authorizer entity; - means for validating a second authorization token, said validation being done by comparing said second authorization token with said first authorization token, said second authorization token being received as part of a request to establish a connection between said server entity and said client entity.
Claim 16
Independent Claim
45 words
The apparatus of any of the preceding claims wherein said means for receiving comprises at least one of the following means: - means for receiving a generic authorization token; - means for receiving a reusable authorization token; - means for receiving a single-use authorization token;
References Cited (Backward Citations)
USPTO Annuity & Maintenance Windows
Maintenance schedule is calculated for granted US utility patents.