Maximum receive capacity specifying query processing client/server system replying up to the capacity and sending the remainder upon subsequent request

• US 5,754,771 A
• Filed: 02/12/1996
• Issued: 05/19/1998
• Est. Priority Date: 02/12/1996
• Status: Expired due to Term

• Current Assignee: Sybase Incorporated (SAP SE)
• Original Assignee: Sybase Incorporated (SAP SE)
• Inventors: Van Couvering, David W., Epperson, Dirk
• Primary Examiner(s): Kim, Kenneth S.
• Application Number:
  US08/598,594
• Time in Patent Office: 827 Days
• Field of Search: 348/7, 348/10, 370/235, 370/236, 395/200.13, 395/200.09, 395/849, 395/853, 395/854, 395/200.33, 395/200.49
• US Class Current: 709/203
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/2871 Implementation details of single intermediate entities
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

An Interactive Television (ITV) Client/Server system comprises one or more Clients (e.g., set top boxes or "STBs") connected to a Server module, via a Broadband Communication Network, is described. The system provides a generic mechanism for deciding how much or how little data is to be sent in response to a request from a Client. Specifically, each Client is allowed to describe ahead of time how much memory (approximately or exactly) it is allowing for the query result. This is communicated by the Client as part of the query itself. Regardless of what other activity the Client undertakes, the server maintains the context of the original query, until the Client terminates the connection. In a similar manner, when other simultaneous queries are open, the context is maintained for each query until the connection is dropped (or the query terminates). The Client can ask for more data (i.e., rows) on any open query. To optimize operation of the environment, requests from the Clients (i.e., queries) are de-multiplexed down to a set of worker threads, available at the server, which carry out the actual work of query processing. Because of this approach, a request for more data from a Client (i.e., set top box) can "land" on any worker thread. This gives queries the ability to "jump" from one thread of execution to another. In this manner, a finite number of threads may be employed to service a large query pool, with maximum throughput.

Claims

1. In a client/server system comprising at least one client connected via a network to a server, a method for sending information from the server to a particular client, the method comprising:

receiving a request from the particular client for information of interest, said request specifying a maximum amount of information that can be received by said particular client at one time;

while the maximum amount of the information that can be received by said particular client has not been reached, retrieving some amount of the information for sending to the particular client;

if the maximum amount of the information that can be received by said particular client has been reached while more of the information remains for said request, storing data describing a context for the request, said context storing information at the server describing said request for information of interest to the particular client, the maximum amount of information that can be received by said particular client at one time, and how much information has already been retrieved by the particular client, for facilitating processing of subsequent requests by the particular client for retrieving additional portions of the information of interest which have yet to be retrieved by the particular client; and

sending to the client the information retrieved in response to said request and any subsequent requests.

2. The method of claim 1, wherein said request comprises a query specifying a query condition.

3. The method of claim 2, wherein said query is an SQL query.

4. The method of claim 1, wherein said particular client is a set top box.

5. The method of claim 1, wherein said information of interest comprises particular rows from a database table stored on the server.

6. The method of claim 1, wherein said maximum amount of information is specified as a maximum number of rows that said particular client can receive.

7. The method of claim 1, wherein said maximum amount of information is specified as a maximum number of bytes that said particular client can receive.

8. The method of claim 1, wherein said data describing the context for the request comprises a query object characterizing a query in process, said query object including information sufficient to characterize said request specifying the information of interest to the particular client.

9. The method of claim 8, wherein said query object comprises a database query and information describing how much information has been sent to the particular client.

10. The method of claim 8, wherein said query object is maintained on a thread of execution separate from a worker thread of execution employed for processing the request.

11. The method of claim 1, further comprising:

receiving another request for more information, and repeating the retrieving step.

12. The method of claim 1, wherein said particular client is a set top box and said request comprises a request for a listing of services available to a user of the system.

13. The method of claim 1, wherein said maximum amount of information comprises about 25 to 300 rows of information from a database table.

14. The method of claim 1, wherein said information of interest comprises rows of information taken from a plurality of database tables.

15. The method of claim 1, wherein said context for the request is preserved by a separately executing thread.

16. The method of claim 15, wherein said request comprises a query and wherein said separately executing thread "sleeps" during periods of time when the query remains open yet information is not being currently sent to the particular client.

17. In a database system comprising at least one client connected via a network to at least one server, a method for processing a query from a particular client, said query specifying fetching of data records, the method comprising:

receiving an initial request comprising a query from the particular client for fetching data records, said query specifying a query condition which data records must meet in order to be fetched, said client able to receive a maximum number of data records at one time;

fetching data records meeting said query condition;

sending to the particular client an initial set of data records from said fetched data records, said initial set having a number of data records equal to or less than said maximum number of data records;

suspending processing of the query until a subsequent request for more data records satisfying the query is received from the particular client, said suspending step maintaining information describing the query in process;

receiving such a subsequent request from the particular client for more data records; and

sending to the particular client a subsequent set of data records from said fetched data records, said subsequent set having a number of data records equal to or less than said maximum number of data records.

18. The method of claim 17, wherein said query comprises an SQL statement.

19. The method of claim 17, wherein said data records are stored in a database table of a particular server.

20. The method of claim 17, wherein said data records are derived from a plurality of database tables.

21. The method of claim 17, wherein said maximum number of data records specified by the particular client is determined based on memory available at the particular client.

22. The method of claim 21, wherein said memory available at the particular client comprises memory ranging from four megabytes to eight megabytes of random-access memory.

23. The method of claim 17, wherein said initial request for more data records comprises an SQL statement.

24. The method of claim 17, wherein said maximum number of data records numbers about 25 to 300 data records.

25. The method of claim 17, wherein said information describing said query includes information describing the query condition, information describing a connection between said particular client and a particular server, and information describing how many data records had been sent to said particular client.

26. The method of claim 17, wherein said suspending step includes suspending execution of a thread which holds said information describing said query.

27. The method of claim 26, wherein said thread which holds said information describing said query is separate from a thread employed for processing said query.

28. The method of claim 27, wherein said thread employed for processing said query condition executes processing for another query, upon suspending execution of the thread which holds said information describing said query.

29. The method of claim 17, further comprising sending a command from the particular client to the particular server for terminating processing of the query.

30. The method of claim 29, wherein said command to terminate processing of said query can be sent by the particular client at any time during query processing.