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

• US 5,850,517 A
• Filed: 08/31/1995
• Issued: 12/15/1998
• Est. Priority Date: 08/31/1995
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle Corporation
• Inventors: Shafiq, Muhammad, Harrenstien, Kenneth L., Lambert, Mark L., Verkler, Jay L., Neumann, Larry E., van der Rijn, Daniel
• Primary Examiner(s): AN, MENG AI T
• Application Number:
  US08/521,660
• Time in Patent Office: 1,202 Days
• Field of Search: 395/200.01, 395/200.03, 395/200.32, 395/200.33, 395/200.09, 395/200.06, 395/200.12, 395/200.2, 395/200.15, 370/85.13, 370/401, 370/428, 370/429, 370/463, 370/253, 370/397, 370/468, 370/384, 370/312
• US Class Current: 709/202
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/1004 Server selection for load balancing
• CPC Class Codes: H04L 67/2866 Architectures; Arrangements
• CPC Class Codes: H04L 9/40 Network security protocols

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.

Claims

1. 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.

2. 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.

3. The architecture defined in claim 2 wherein the message manager comprises a queue for storing messages prior to sending the messages to the gateway.

4. 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.

5. 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.

6. The architecture defined in claim 1 wherein the message manager comprises communications drivers and a plurality of communications hardware.

7. The architecture defined in claim 1 wherein the message interface layer comprises OLE 2.0.

8. The architecture defined in claim 1 wherein the message interface layer comprises an object-level interprogram interface.

9. 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.

10. 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.

11. The architecture defined in claim 1 wherein each of the plurality of requests is communicated as at least one self-described object.

12. 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.

13. 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.

14. 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.

15. 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.

16. The architecture defined in claim 1 wherein a gateway is linked to the agent and the client and the gateway performs automatic load balancing.

17. The architecture defined in claim 1 wherein a gateway is linked to the agent and the client and the gateway performs service-based routing.

18. 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.

19. 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.

20. The architecture defined in claim 1 wherein the communication link is a mobile communication link.