US5748892A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Method and apparatus for client managed flow control on a limited memory computer system
Assignee: Citrix Systems Inc
•
Filing: 1996-03-25
•
Granted: 1998-05-05
•
Expires: 2016-03-25
Abstract
Abstract A method and apparatus for controlling data flow on a network having a server and a non-blocking client node in which the client node may not drop requests received from the server. A process on the non-blocking client node allocates resources on the non-blocking client node and notifies the server of the allocated resources. The server then determines the resources on the non-blocking client node required to fulfill a request by an application on the server and whether sufficient resources are available on the non-blocking client node to fulfill the request by the application. If sufficient resources are available, the server then sends the request to the client node and if sufficient resources do not exist, the server waits until sufficient resources do exist to issue the request to the non-blocking client node.
Inventors
- 👤 John Richardson
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-30 20:28
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/50; G06F9/5005; G06F9/5011; G06F9/5016; H; H04; H04L; H04L9/00; H04L9/40
Claims Analysis
Total Claims: 9
Claim 1
Independent Claim
124 words
A method for flow control on a network having a server and a non-blocking client node which may not drop requests, the method comprising the steps of: allocating resources on said non-blocking client node by said non-blocking node; notifying said server of said allocated resources by said non-blocking client node; determining by said server the resources on said non-blocking client node required to fulfill a request made by an application executing on said server; determining by said server whether sufficient resources are available on said non-blocking client node to fulfill said request of said application; and sending said request of said application by said server to said non-blocking client node if sufficient resources are available on said non-blocking client node to fulfill said request.
Claim 2
Independent Claim
124 words
A method for flow control on a network having a server and a non-blocking client node which may not drop requests, the method comprising the steps of: allocating resources on said non-blocking client node by said non-blocking node; notifying said server of said allocated resources by said non-blocking client node; determining by said server the resources on said non-blocking client node required to fulfill a request made by an application executing on said server; determining by said server whether sufficient resources are available on said non-blocking client node to fulfill said request of said application; and sending said request of said application by said server to said non-blocking client node if sufficient resources are available on said non-blocking client node to fulfill said request.
Claim 3
Dependent Claim
43 words
The method for flow control of claim 1 further comprising the step of storing said notification of said allocated resources of said non-blocking client node on said server, wherein said notification comprises information relating to available allocated resources on said non-blocking client node.
Claim 4
Dependent Claim
35 words
The method for flow control of claim 2 further comprising the step of updating said notification information by said server in response to said requests from said application being sent to said non-blocking client node.
Claim 5
Dependent Claim
96 words
The method for flow control of claim 1 further comprising the steps of: determining by said server whether said request is divisible, if sufficient available resources are not available on said non-blocking client node to fulfill said request; dividing said request into subrequests if said request is divisible, the number of subrequests being chosen such that sufficient resources are available on said non-blocking client node to fulfill at least one said subrequest; and sending said subrequest capable of being fulfilled by said resources on said non-blocking client node to said non-blocking client node by said server.
Claim 6
Dependent Claim
40 words
The method for flow control of claim 2 further comprising the steps of: receiving by said server from said non-blocking client node replies to previous requests; and updating said notification stored on said server node in response to said replies.
Claim 7
Dependent Claim
88 words
A network comprising: a non-blocking client node comprising a plurality of resources, said non-blocking client node being unable to drop requests; and a server node in communication with said non-blocking client node, said server node comprising: an application process executing on said server node; a flow control process executing on said server node wherein said flow control process determines if said non-blocking client node is able to receive and service a request; and a memory comprising: resource information corresponding to available resources located on said non-blocking client node.
Claim 8
Dependent Claim
88 words
A network comprising: a non-blocking client node comprising a plurality of resources, said non-blocking client node being unable to drop requests; and a server node in communication with said non-blocking client node, said server node comprising: an application process executing on said server node; a flow control process executing on said server node wherein said flow control process determines if said non-blocking client node is able to receive and service a request; and a memory comprising: resource information corresponding to available resources located on said non-blocking client node.
Claim 9
Dependent Claim
44 words
The network of claim 6, wherein said server node sends requests from said application process to said non-blocking client node in response to resource information and updates said resource information in response to requests sent to and buffers receives from said non-blocking client node.
References Cited (Backward Citations)
US4937784A
Cited
US5367688A
Cited
US5014221A
Cited
EP0381645A2
Cited
US5341477A
Cited
US5305440A
Cited
WO1993015457A1
Cited
US5440719A
Cited
US5329619A
Cited
US5325527A
Cited
US5515508A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2001-05-04 | 2001-11-03 | 2002-05-05 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2005-05-04 | 2005-11-03 | 2006-05-05 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2009-05-04 | 2009-11-03 | 2010-05-05 | $7700.00 | Window Closed / Lapsed |