US5850517A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Communication link for client-server having agent which sends plurality of requests independent of client and receives information from the server independent of the server
Assignee: Oracle International Corp
•
Filing: 1995-08-31
•
Granted: 1998-12-15
•
Expires: 2015-08-31
Abstract
Abstract A client-server architecture for use with mobile clients communicating requests through wireless communications. The requests from the client and the subsequent responses by the server are transferred between the client-server connection through an intermediary agent, which operates asynchronously to the client and to the server.
Inventors
- 👤 Jay L. Verkler
- 👤 Mark L. Lambert
- 👤 Kenneth L. Harrenstien
- 👤 Muhammad Shafiq
- 👤 Larry E. Neumann
- 👤 Daniel van der Rijn
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-31 01:13
CPC Classifications
H; H04; H04L; H04L9/00; H04L9/40; H04L67/00; H04L67/2866; H04L67/01; H04L67/10; H04L67/1001; H04L67/1004
Claims Analysis
Total Claims: 21
Claim 1
Independent Claim
193 words
An architecture for client-server communication over a communication link, the architecture comprising: a client that generates a plurality of requests for information, the client including: at least one application that generates the plurality of requests when running; a message interface operating in conjunction with the at least one application to format requests into messages; a message manager operable with said at least one application to coordinate transfer of requests between the client and the agent; an agent coupled to the client through a communication link and coupled to the communication medium, the agent including: at least one handler, wherein each of the at least one handler performs at least one transaction in response to the plurality of request; and an event manager that transfers each of the plurality of requests to the at least one handler, wherein the agent sends the plurality of requests to the server on behalf of and independent of the client and receives information from the server responsive to the plurality of requests, wherein the agent sends the information to the client on behalf of and independent of the server, such that the client and the agent operate asynchronously.
Claim 2
Dependent Claim
193 words
An architecture for client-server communication over a communication link, the architecture comprising: a client that generates a plurality of requests for information, the client including: at least one application that generates the plurality of requests when running; a message interface operating in conjunction with the at least one application to format requests into messages; a message manager operable with said at least one application to coordinate transfer of requests between the client and the agent; an agent coupled to the client through a communication link and coupled to the communication medium, the agent including: at least one handler, wherein each of the at least one handler performs at least one transaction in response to the plurality of request; and an event manager that transfers each of the plurality of requests to the at least one handler, wherein the agent sends the plurality of requests to the server on behalf of and independent of the client and receives information from the server responsive to the plurality of requests, wherein the agent sends the information to the client on behalf of and independent of the server, such that the client and the agent operate asynchronously.
Claim 3
Dependent Claim
35 words
The architecture defined in claim 1 wherein a gateway is linked to the agent and the client and the message manager forwards the plurality of requests from the client to the gateway at any time.
Claim 4
Dependent Claim
24 words
The architecture defined in claim 2 wherein the message manager comprises a queue for storing messages prior to sending the messages to the gateway.
Claim 5
Dependent Claim
25 words
The architecture defined in claim 1 wherein the agent continues to operate on behalf of the client while the client is disconnected from the agent.
Claim 6
Dependent Claim
26 words
The architecture defined in claim 4 wherein the agent stores information to be forwarded to the client when the client is not available to the agent.
Claim 7
Dependent Claim
19 words
The architecture defined in claim 1 wherein the message manager comprises communications drivers and a plurality of communications hardware.
Claim 8
Dependent Claim
14 words
The architecture defined in claim 1 wherein the message interface layer comprises OLE 2.0.
Claim 9
Dependent Claim
16 words
The architecture defined in claim 1 wherein the message interface layer comprises an object-level interprogram interface.
Claim 10
Dependent Claim
30 words
The architecture defined in claim 1 wherein the message manager comprises a queue to store requests to be sent to the server while the client not communicating with the agent.
Claim 11
Dependent Claim
28 words
The architecture defined in claim 1 wherein the agent sends at least one of the plurality of requests to the server while no longer communicating with the client.
Claim 12
Dependent Claim
21 words
The architecture defined in claim 1 wherein each of the plurality of requests is communicated as at least one self-described object.
Claim 13
Dependent Claim
28 words
The architecture defined in claim 1 wherein the agent accepts unsolicited information from the server on behalf of the client and forwards the unsolicited information to the client.
Claim 14
Dependent Claim
37 words
The architecture defined in claim 1 wherein the message manager comprises a selection mechanism that allows a user to select a type of the communication link independent of at least one application programming running on the client.
Claim 15
Dependent Claim
40 words
The architecture defined in claim 1 wherein a gateway is linked to the agent and the client, the gateway maintaining a registry of agents and clients and providing system information in response to requests by the client and the agent.
Claim 16
Dependent Claim
36 words
The architecture defined in claim 1 wherein the message manager allocates buffer memory as messages are received by linking segments of memory that are a predetermined size to a buffer size necessary to store the messages.
Claim 17
Dependent Claim
24 words
The architecture defined in claim 1 wherein a gateway is linked to the agent and the client and the gateway performs automatic load balancing.
Claim 18
Dependent Claim
23 words
The architecture defined in claim 1 wherein a gateway is linked to the agent and the client and the gateway performs service-based routing.
Claim 19
Dependent Claim
39 words
The architecture defined in claim 1 wherein a gateway is linked to the agent and the client and the gateway identifies the client after the client changes locations on the communication link by rebinding the address of the client.
Claim 20
Dependent Claim
31 words
The architecture defined in claim 1 wherein a gateway is linked to the agent and the client and the gateway queues messages designated for the client or the agent when unavailable.
Claim 21
Dependent Claim
15 words
The architecture defined in claim 1 wherein the communication link is a mobile communication link.
References Cited (Backward Citations)
EP0483547A1
Cited
US5329619A
Cited
US5410543A
Cited
US5530963A
Cited
US5581596A
Cited
US5533026A
Cited
US5586121A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2001-12-14 | 2002-06-15 | 2002-12-15 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2005-12-14 | 2006-06-15 | 2006-12-15 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2009-12-14 | 2010-06-15 | 2010-12-15 | $7700.00 | Window Closed / Lapsed |