Patent US6092178A successfully refreshed from Google Patents.
US6092178A
Expired / Lapsed
US
⏱️ 0.0 years remaining
System for responding to a resource request
Assignee: Oracle America Inc
•
Filing: 1998-09-03
•
Granted: 2000-07-18
•
Expires: 2018-09-03
Abstract
Abstract A trigger is provided in association with a network naming service, such as DNS (Domain Name Service), that handles client requests for an application. The trigger comprises a set of executable instructions referenced by a resource record associated with an identifier of the application. In response to a client request concerning the application, the resource record is retrieved and the instructions are executed. In one implementation of a trigger, a DNS server provides load balancing among a plurality of servers within a network name space (e.g., domain or sub-domain) offering an application program (or replicated service) that is known by a virtual server name. A policy is selected for choosing a preferred server from the plurality of servers according to a specified status or operational characteristic of the application instances, such as the least-loaded instance of the application or the instance with the fastest response time. The policy is encapsulated within multiple levels of objects or modules distributed among the plurality of servers and the DNS server. The objects collect and assemble the servers' status and operational characteristics. The information collected by the objects is analyzed to select the server that best satisfies the selected policy. A client request for the application is received by the DNS server, which retrieves a resource record corresponding to the virtual server name. Within the record is the name of a trigger. The trigger is executed to select, or retrieve an identity of, a server to which the client request is to be directed.
Inventors
- 👤 Anita Jindal
- 👤 Swee Boon Lim
- 👤 Sanjay Radia
- 👤 Whei-Ling Chang
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-24 21:21
CPC Classifications
H; H04; H04L; H04L67/00; H04L67/01; H04L67/10; H04L67/1001; H04L67/1004; H04L67/1008; H04L61/00; H04L61/45; H04L61/4505; H04L61/4511; H04L67/101; H04L67/1038
Claims Analysis
Total Claims: 33
Claim 1
Independent Claim
76 words
A method of handling a resource request, comprising: receiving a resource request at a network server from a client computer system, said resource request including a first identity of a network entity; searching a database for a resource record associated with said network entity; retrieving an identifier of a series of executable instructions from said resource record; and executing said series of instructions to facilitate providing the requested resource to said client by said network entity.
Claim 2
Independent Claim
76 words
A method of handling a resource request, comprising: receiving a resource request at a network server from a client computer system, said resource request including a first identity of a network entity; searching a database for a resource record associated with said network entity; retrieving an identifier of a series of executable instructions from said resource record; and executing said series of instructions to facilitate providing the requested resource to said client by said network entity.
Claim 3
Dependent Claim
12 words
The method of claim 1, wherein said network entity is an application.
Claim 4
Dependent Claim
15 words
The method of claim 1, wherein said network entity is a server operating an application.
Claim 5
Dependent Claim
29 words
The method of claim 1, wherein said network server is a DNS server and said receiving a resource request comprises receiving a request concerning access to said network entity.
Claim 6
Dependent Claim
15 words
The method of claim 4, further comprising identifying a means for accessing said network entity.
Claim 7
Dependent Claim
11 words
The method of claim 5, wherein said means comprises an address.
Claim 8
Dependent Claim
17 words
The method of claim 5, wherein said identifying comprises retrieving a second identity of said network entity.
Claim 9
Dependent Claim
19 words
The method of claim 7, wherein said first identity comprises a name and said second identity comprises an address.
Claim 10
Dependent Claim
29 words
The method of claim 5, wherein said identifying comprises: analyzing information concerning a set of network entities; and selecting said network entity on the basis of an operational characteristic.
Claim 11
Dependent Claim
13 words
The method of claim 9, wherein said resource request includes said operational characteristic.
Claim 12
Independent Claim
156 words
A method of load-balancing requests for an application received at a central server among a set of servers, wherein each server in the set of servers operates an instance of the application, comprising: receiving a client request concerning access to the application; retrieving a resource record associated with the application, said resource record referencing a trigger, wherein said trigger comprises a series of executable instructions; executing said trigger to determine an identity of a preferred server from the set of servers, said preferred server operating an instance of the application to be accessed by said client; identifying a first factor for selecting said preferred server, said first factor comprising an operational characteristic of the application; receiving a first status of said first factor for a first instance of the application operating on a first server; and receiving a second status of said first factor for a second instance of the application operating on a second server.
Claim 13
Independent Claim
156 words
A method of load-balancing requests for an application received at a central server among a set of servers, wherein each server in the set of servers operates an instance of the application, comprising: receiving a client request concerning access to the application; retrieving a resource record associated with the application, said resource record referencing a trigger, wherein said trigger comprises a series of executable instructions; executing said trigger to determine an identity of a preferred server from the set of servers, said preferred server operating an instance of the application to be accessed by said client; identifying a first factor for selecting said preferred server, said first factor comprising an operational characteristic of the application; receiving a first status of said first factor for a first instance of the application operating on a first server; and receiving a second status of said first factor for a second instance of the application operating on a second server.
Claim 14
Dependent Claim
28 words
The method of claim 11, further comprising: examining said first status and said second status to select a preferred server; and storing an identity of said preferred server.
Claim 15
Dependent Claim
70 words
The method of claim 11, further comprising: executing a first status object to determine a first status of said first factor for a first instance of the application, wherein said first status object resides on a first server; and executing a second status object to determine a second status of said first factor for a second instance of the application, wherein said second status object resides on a second server.
Claim 16
Dependent Claim
21 words
The method of claim 11, wherein said receiving a first status comprises collecting data concerning a first instance of the application.
Claim 17
Dependent Claim
32 words
The method of claim 13, further comprising: receiving said first status by a first server monitor object; and receiving said first status at the central server from said first server monitor object.
Claim 18
Dependent Claim
27 words
The method of claim 11, wherein said executing said trigger to determine an identity of a preferred server comprises retrieving a stored identity of a preferred server.
Claim 19
Dependent Claim
32 words
The method of claim 11, wherein said executing a trigger to determine an identity of a preferred server comprises examining said first status and said second status to select a preferred server.
Claim 20
Independent Claim
51 words
A method of handling a client request at a central server, comprising: receiving a client request, said request comprising an identifier of an application; retrieving a resource record associated with said application, said resource record comprising a trigger; and executing said trigger; wherein said trigger comprises a series of executable instructions.
Claim 21
Independent Claim
51 words
A method of handling a client request at a central server, comprising: receiving a client request, said request comprising an identifier of an application; retrieving a resource record associated with said application, said resource record comprising a trigger; and executing said trigger; wherein said trigger comprises a series of executable instructions.
Claim 22
Dependent Claim
26 words
The method of claim 18, wherein the server is a DNS server, further comprising searching a DNS database for a resource record associated with said application.
Claim 23
Dependent Claim
43 words
The method of claim 19, wherein: said receiving a client request comprises receiving a request for an identifier of a server offering an application; and wherein said trigger comprises a series of instructions for determining an identifier of a server offering an application.
Claim 24
Independent Claim
126 words
An apparatus for balancing requests for an application among multiple servers operating multiple instances of the application, wherein the requests are received at a central server, comprising: a trigger for executing a series of instructions in response to a request for the application from a client computer system; a first server for operating a first instance of the application; a second server for operating a second instance of the application; a first status module for determining a first status of said first instance; a second status module for determining a second status of said second instance; an analysis module for examining said first status and said second status and selecting one of said first server and said second server for receiving said request for the application.
Claim 25
Independent Claim
126 words
An apparatus for balancing requests for an application among multiple servers operating multiple instances of the application, wherein the requests are received at a central server, comprising: a trigger for executing a series of instructions in response to a request for the application from a client computer system; a first server for operating a first instance of the application; a second server for operating a second instance of the application; a first status module for determining a first status of said first instance; a second status module for determining a second status of said second instance; an analysis module for examining said first status and said second status and selecting one of said first server and said second server for receiving said request for the application.
Claim 26
Dependent Claim
25 words
The apparatus of claim 21, wherein said trigger comprises an identifier of said series of instructions and said series of instructions comprises said analysis module.
Claim 27
Dependent Claim
15 words
The apparatus of claim 21, wherein said first status module resides on said first server.
Claim 28
Dependent Claim
89 words
A computer readable storage medium storing instructions that, when executed by a computer, cause the computer to perform a method for handling a resource request, the method comprising: receiving a resource request at a network server from a client computer system, said resource request including a first identity of a network entity; searching a database for a resource record associated with said network entity; retrieving an identifier of a series of executable instructions from said resource record; and executing said series of instructions in response to said resource request.
Claim 29
Dependent Claim
89 words
A computer readable storage medium storing instructions that, when executed by a computer, cause the computer to perform a method for handling a resource request, the method comprising: receiving a resource request at a network server from a client computer system, said resource request including a first identity of a network entity; searching a database for a resource record associated with said network entity; retrieving an identifier of a series of executable instructions from said resource record; and executing said series of instructions in response to said resource request.
Claim 30
Dependent Claim
78 words
A computer readable storage medium containing a data structure for storing a trigger, said data structure comprising: an index portion for storing an identifier of a network entity; an identifier of a trigger, said trigger comprising a series of executable instructions; and a type portion for identifying the data structure as comprising said trigger; wherein said data structure is retrieved and said trigger executed in response to a client request for a resource offered by said network entity.
Claim 31
Dependent Claim
78 words
A computer readable storage medium containing a data structure for storing a trigger, said data structure comprising: an index portion for storing an identifier of a network entity; an identifier of a trigger, said trigger comprising a series of executable instructions; and a type portion for identifying the data structure as comprising said trigger; wherein said data structure is retrieved and said trigger executed in response to a client request for a resource offered by said network entity.
Claim 32
Dependent Claim
38 words
The method of claim 9, wherein said operational characteristic is one of: a response time of said network entity, a load on said network entity, a distance to said network entity and a throughput of said network entity.
Claim 33
Dependent Claim
23 words
The method of claim 1, wherein said requested resource is available on said network entity but is not available on said network server.
References Cited (Backward Citations)
US5506999A
Cited
US5371852A
Cited
US5459837A
Cited
US5583994A
Cited
US5881238A
Cited
US5915095A
Cited
US5742598A
Cited
US5894556A
Cited
US5937165A
Cited
WO1998026559A1
Cited
US5938732A
Cited
US6038599A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2003-07-18 | 2004-01-17 | 2004-07-18 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-07-18 | 2008-01-17 | 2008-07-18 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-07-18 | 2012-01-17 | 2012-07-18 | $7700.00 | Window Closed / Lapsed |