Patent US5862326A successfully refreshed from Google Patents.
US5862326A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Efficient request-reply protocol for a client-server model
Assignee: Cirrus Logic Inc
•
Filing: 1995-09-21
•
Granted: 1999-01-19
•
Expires: 2015-09-21
Abstract
Abstract An efficient request-reply protocol for a client-server communication and data processing model. Under the novel protocol, a client sends a Request to a server and awaits a Reply. If the Reply is not sent before expiration of a timeout period in the client, the client sends a second Request. The server provides a conditional Acknowledge if a second Request is received from the client. Thereafter, the client waits for the server to transmit a Reply without the client sending additional Requests. Under normal conditions, the inventive protocol performs as well as the best prior art protocol (the optimistic model), while under abnormal conditions, the inventive protocol performs better than the optimistic protocol and only slightly worse than the prior art pessimistic protocol. Since normal conditions should prevail for a substantially longer amount of time than abnormal conditions, the present invention provides better average performance than either prior art client-server protocol.
Inventors
- 👤 Sanjay Bapat
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-06 04:54
CPC Classifications
G; G06; G06F; G06F16/00; G06F16/10; H; H04; H04L; H04L67/00; H04L67/01; H04L67/10; H04L67/104; H04L67/1087; H04L67/1091; H04L9/00; H04L9/40
Claims Analysis
Total Claims: 7
Claim 1
Independent Claim
114 words
A method for communicating between a client and a server coupled by a network, comprising: (a) transmitting a request to perform an operation, from a client to a server over a network; (b) retransmitting the request to perform the operation, if the client does not receive a reply conveying a result of the request, from the server before a time period elapses; (c) transmitting an acknowledge signal indicating receipt of the retransmitted request by the server, from the server to the client over the network, if the server receives the retransmitted request before generating the reply; and (d) transmitting the reply from the server to the client after the server has generated the reply.
Claim 2
Independent Claim
114 words
A method for communicating between a client and a server coupled by a network, comprising: (a) transmitting a request to perform an operation, from a client to a server over a network; (b) retransmitting the request to perform the operation, if the client does not receive a reply conveying a result of the request, from the server before a time period elapses; (c) transmitting an acknowledge signal indicating receipt of the retransmitted request by the server, from the server to the client over the network, if the server receives the retransmitted request before generating the reply; and (d) transmitting the reply from the server to the client after the server has generated the reply.
Claim 3
Dependent Claim
35 words
The method according to claim 1, further comprising after step (c), (e) suspending further retransmissions of the request from the client to the server, in response to receipt by the client of the acknowledge signal.
Claim 4
Independent Claim
131 words
A method executed by a client in communicating with a server over a network, comprising: (a) transmitting a request to perform an operation to a server over a network; (b) waiting for a reply conveying a result of the request from the server; (c) retransmitting the request to the server only if the reply is not received from the server before a time period elapses; (d) waiting for the earlier arriving of the reply or an acknowledge signal indicating receipt of the retransmitted request by the server; and (e) suspending retransmissions of the request to the server, if the earlier arriving of the reply or the acknowledge signal is received from the server before the time period elapses, otherwise retransmitting the request to the server and jumping back to step (d).
Claim 5
Independent Claim
131 words
A method executed by a client in communicating with a server over a network, comprising: (a) transmitting a request to perform an operation to a server over a network; (b) waiting for a reply conveying a result of the request from the server; (c) retransmitting the request to the server only if the reply is not received from the server before a time period elapses; (d) waiting for the earlier arriving of the reply or an acknowledge signal indicating receipt of the retransmitted request by the server; and (e) suspending retransmissions of the request to the server, if the earlier arriving of the reply or the acknowledge signal is received from the server before the time period elapses, otherwise retransmitting the request to the server and jumping back to step (d).
Claim 6
Independent Claim
100 words
A method executed by a server in communicating with a client over a network, comprising: (a) receiving a request from a client over a network, and taking no action in response to the request to transmit an acknowledge signal indicating receipt of the request back to the client; (b) generating a reply conveying a result of the request; (c) transmitting an acknowledge signal to the client, if a retransmission of the request is received from the client before the reply is generated; and (b) transmitting the reply conveying the result of the request to the client, after generating the reply.
Claim 7
Independent Claim
100 words
A method executed by a server in communicating with a client over a network, comprising: (a) receiving a request from a client over a network, and taking no action in response to the request to transmit an acknowledge signal indicating receipt of the request back to the client; (b) generating a reply conveying a result of the request; (c) transmitting an acknowledge signal to the client, if a retransmission of the request is received from the client before the reply is generated; and (b) transmitting the reply conveying the result of the request to the client, after generating the reply.
References Cited (Backward Citations)
US5396613A
Cited
US5546583A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2002-01-18 | 2002-07-20 | 2003-01-19 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2006-01-18 | 2006-07-20 | 2007-01-19 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2010-01-18 | 2010-07-20 | 2011-01-19 | $7700.00 | Window Closed / Lapsed |