PERFORMANCE ENHANCING PROXY

• US 20090172801A1
• Filed: 12/28/2007
• Published: 07/02/2009
• Est. Priority Date: 12/28/2007
• Status: Active Grant

• Current Assignee: Dish Technologies LLC (Echostar Corporation)
• Original Assignee: Echostar Technologies Corporation (Echostar Corporation)
• Inventors: Hansen, Tom, Selvamani, Kiruthika, Yakemovic, John, Friedrich, Alisson, Taylor, Thomas Steven
• Granted Patent: US 8,966,011 B2
• Time in Patent Office: Days
• US Class Current: 726/12
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• CPC Class Codes: H04L 69/165 Combined use of TCP and UDP protocols; selection criteria therefor

Abstract

One embodiment of the present invention may take the form of a method and a system for performance enhancing proxy (PEP). A PEP system may include a configuration of software components and hardware devices to increase the performance of a two-way satellite broadband service. The PEP system may include one or more embodiments to reduce the time necessary for users to transmit and receive data provided through a communication network.

Claims

1. A method of communicating a client proxy comprising:

requesting a plurality of unidirectional connections between the client proxy and a hub proxy, the plurality of unidirectional connections include a first transmission link to transmit a first data signal to a hub proxy and a second transmission link to receive a second data signal from the hub proxy until at least at least one of the client proxy and the hub proxy is offline;

acknowledging an establishment of the plurality of unidirectional connections; and

transmitting a data request signal to the hub proxy.

2. The method of claim 1 wherein the operation of establishing comprises establishing the first and second transmission links across a satellite communications network.

3. The method of claim 1, wherein the operation of transmitting the data request signal comprises:

receiving a first data request associated with a webpage from a client;

transmitting the first request to the hub proxy across the first transmission link; and

receiving a response message from the hub proxy across the second transmission link.

4. The method of claim 1, further comprising:

receiving a data response based on the data request;

receiving a prefetched response based on the data response; and

storing the prefetched response.

5. The method of claim 4, further comprising transmitting the prefetched response, to a client, when a second request associated with data of the at least one prefeteched response is received.

6. The method of claim 1, further comprising receiving a complied list of most frequently requested domain names and/or Internet protocol addresses via the second transmission link.

7. The method of claim 1, wherein the data request includes a request for an Internet protocol address associated with the webpage.

8. The method of claim 7, further comprising transmitting an internally generated spoof Internet protocol address in response to receiving a first data signal from a client.

9. A method of operating a hub proxy comprising:

receiving a data request from a first user in order to transmit the data request to an internet server;

receiving a data response based on the data request;

determining whether the data response includes an indicator that identify additional data needed to complete the data request; and

prefetching data associated with the indicator identified in response therein.

10. The method of claim 9, wherein the operation of receiving the data request comprises receiving the data request associated with a webpage.

11. The method of claim 9, further comprising transmitting prefetched additional data to the user.

12. The method of claim 11, further comprising receiving the data request over a satellite communication network.

13. The method of claim 10, further comprising:

receiving a plurality of domain name requests associated with a plurality of webpages from a plurality of client proxies; and

generating a complied list of most frequently requested domain names and/or Internet protocol addresses based on the plurality of domain name requests.

14. The method of claim 9, further comprising ignoring a second data request from the client proxy if the second data request is associated with prefetched data.

15. The method of claim 9, wherein the operation of receiving the data request comprises:

receiving a unique identification associated with the first request; and

extracting the unique identification from the first request.

16. The method of claim 15, wherein the unique identification comprises a uniform resource locator (URL) address of the webpage, port number, and source IP address of the client proxy.

17. The method of claim 12 further comprising receiving a second data request from a second user.

18. The method of claim 17, further comprising generating a complied list of most frequently requested domain names and/or Internet protocol addresses by the first user and the second user.

20. The method of claim 19, further comprising transmitting the complied list to the first user and the second user.

21. A method of operating a client proxy comprising:

receiving a data request associated with contents of a webpage from a user;

determining whether the data message includes identification associated with a previously transmitted data request; and

storing unidentified data in a data store until a data request is received by a user.

22. The method of claim 21 further comprising generating the unique identification associated with the data request.

23. The method of claim 22 further comprising determining whether the unidentified data is data associated with the data request based on at least one of a uniform resource locator (URL) address of the webpage and an Internet Protocol address.