Gateway architecture for data communication bandwidth-constrained and charge-by-use networks

• US 6,115,384 A
• Filed: 06/20/1996
• Issued: 09/05/2000
• Est. Priority Date: 06/20/1996
• Status: Expired due to Term

• Current Assignee: Venturi Wireless Incorporated
• Original Assignee: Fourelle Systems Incorporated
• Inventors: Parzych, Matthew J.
• Primary Examiner(s): Patel, Ajit
• Application Number:
  US08/667,002
• Time in Patent Office: 1,538 Days
• Field of Search: 370/398, 370/465, 370/466, 370/467, 370/477, 370/401, 370/402, 370/351, 370/352-356, 370/395
• US Class Current: 370/401
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A gateway architecture for data communication over bandwidth-constrained and charge-by-use networks (10) uses a C_-- Gate application (14) located between a client application (12) and a bandwidth-constrained network (22), and an S_-- Gate application (20) located between the bandwidth-constrained network (22) and an Internet server (26), to send and receive data in an efficient manner across the bandwidth-constrained network (22) by converting the native protocols of the client application (12) and the Internet server (26) to a bandwidth-efficient protocol. The C_-- Gate application (14) and S_-- Gate application (20) also act to reconvert data packets from the bandwidth-efficient protocol back to the native transport protocols for data communication to the Internet server (26) and the client application (12).

Claims

1. A method for effecting data communications between a remote node and a host, comprising the steps of:

exchanging data in a first exchanging step between a client application at said remote node using the TCP/IP communications protocol which is resident on said remote node and a first proxy or gateway, wherein said first exchanging step further comprises the step of compressing said data;

converting said TCP/IP communications protocol resident on said remote node into a bandwidth-efficient protocol prior to transmission of said data communications from said first proxy or gateway to said host;

reconverting said bandwidth-efficient protocol back to said TCP/IP communications protocol at a second proxy or gateway; and

exchanging data in a second exchanging step between said second proxy or gateway and an application at said host in said TCP/IP communications protocol which is resident on said host, wherein said second exchanging step further comprises the step of decompressing said data.

2. The method of claim 1, wherein said host is an Internet.

3. The method of claim 1, wherein said host is an intranet.

4. The method of claim 1, wherein said standard communications protocol is Transmission Control Protocol/Internet Protocol.

5. The method of claim 1, wherein the step of reconverting said bandwidth-efficient protocol back to said standard communications protocol further comprises the step of interpreting data communications.

6. A gateway architecture for data communication over network between a remote node and a host, comprising:

a first proxy or gateway located between a client application and said network, wherein said first proxy or gateway receives requests and gathers information from said client application using the TCP/IP communications protocol which is resident on said remote node, and wherein said information is first compressed and then converted to a bandwidth-efficient protocol prior to communication over said network; and

a second proxy or gateway located between said network and said host, wherein said second proxy or gateway receives requests from said first proxy or gateway, and wherein said second proxy or gateway sends and receives messages to and from said host in said TCP/IP communications protocol resident on said host, wherein said information is first reconverted from said bandwidth-efficient protocol back to said TCP/IP protocol and then decompressed after receipt over said network;

wherein said first proxy or gateway sends and receives messages to and from said second proxy or gateway over said network using an efficient transport mechanism other than TCP/IP.

7. The gateway architecture of claim 6, wherein said client application operates as though said server is located between said client application and said bandwidth-constrained network.

8. The gateway architecture of claim 6, wherein said first proxy or gateway extracts data from said requests and said information from said client application.

9. The gateway architecture of claim 6, wherein said second proxy or gateway stores information regarding said client application.

10. The gateway architecture of claim 9, wherein said second proxy or gateway combines said information regarding said client application with said requests.

12. The method of claim 10, wherein said network is an Internet.

13. The method of claim 10, wherein said network is an intranet.

14. The method of claim 10, wherein said standard communications protocol is Transmission Control Protocol/Internet Protocol.

15. The method of claim 10, further comprising the step of:

reconverting said bandwidth-efficient protocol back to said standard communications protocol; and

interpreting data communications.

11. A method for effecting data communications between a host and a remote node, comprising the steps of:

converting the TCP/IP communications protocol which is resident on said host into a bandwidth-efficient protocol with a first proxy or gateway prior to transmission over a network to said remote node, wherein data for said data communication are compressed prior to said converting step; and

reconverting said bandwidth-efficient protocol back to said TCP/IP communications protocol with a second proxy or gateway at said remote node, wherein said data for said data communication are decompressed after said reconverting step.

16. A gateway architecture for data communication over a network between a remote node and a host, comprising:

a client application located on said remote node, said client application using the tCP/IP protocol;

a first proxy or gateway located between said client application and said network, wherein said first proxy or gateway converts said TCP/IP protocol of said client application to a bandwidth-efficient protocol for data communication over said network, wherein data for said data communication are compressed prior to said conversion; and

a second proxy or gateway located between said network and said host, wherein said second proxy or gateway reconverts said bandwidth-efficient protocol back to said TCP/IP protocol for data communication to said host, wherein said data for said data communication are decompressed after said reconversion.

17. The gateway architecture of claim 16, wherein said client application operates as though said host is located between said client application and said network.

18. The gateway architecture of claim 16, wherein said first proxy or gateway intercepts data before data communication occurs from said client application to said host over said network.

19. The gateway architecture of claim 16, wherein said second proxy or gateway stores information regarding said client application.

20. The gateway architecture of claim 19, wherein said second proxy or gateway combines said information regarding said client application with said data communication between said client application and said host.