Performance enhancing proxy for high latency data links

• US 20030069925A1
• Filed: 10/09/2001
• Published: 04/10/2003
• Est. Priority Date: 10/09/2001
• Status: Abandoned Application

• Current Assignee: ViaSat Communications, Inc.
• Original Assignee: ViaSat Communications, Inc.
• Inventors: Weaver, Jeffrey Charles, Moore, Thomas Evans, Sundelin, Andrew Wilson
• Application Number:
  US09/974,664
• Publication Number:
  US 20030069925A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

A system and method for reducing the impact of high latency links for interactive applications is described. In one embodiment, a user, connected to the Internet by a satellite network, requests a web page from an origin server. The origin server generates an index page associated with the requested web page and passes that index page to an gateway PEP (performance enhancing proxy), which parses the index page to identify the objects identified therein. Next, the gateway PEP generates the requests to prefetch those identified objects and passes those requests to the origin server. These objects are then retrieved and pushed to the user. To avoid repetitive requests, the fetch requests normally generated by a web browser are blocked by a client PEP.

Claims

1. A method for managing a data transmission between an origin server and a client, the method comprising:

receiving, at a client performance enhancing proxy (PEP), a request for a data page, wherein the request is generated by the client;

receiving, at the client PEP, an index page generated according to the origin server, wherein the index page identifies a plurality of data objects contained in the requested data page;

receiving, at the client PEP, a list of data objects that are subject to a prefetch from the origin server;

providing the index page to the client;

receiving, at the client PEP, a fetch request generated by the client, wherein the fetch request is configured to request a first of the plurality of data objects identified by the index page;

blocking, at the client PEP, the fetch request so that the fetch request is not provided to the origin server;

receiving, at the client PEP, the first of the plurality of data objects, wherein the first of the plurality of data objects is being provided according to the prefetch; and

providing the received data object to the client;

wherein the received data object at least partially fills the fetch request generated by the client.

2. The method of claim 1, wherein receiving the request for the data page comprises:

receiving a request for a Web page.

3. The method of claim 1, further comprising:

providing the request for a data page to the origin server via a satellite network.

4. The method of claim 1, further comprising:

providing the request for a data page to the origin server via a wireless network.

5. The method of claim 1, wherein receiving an index page generated according to the origin server comprises:

receiving an index page generated by the origin server.

6. The method of claim 1, further comprising:

comparing the list of data objects with the index page to determine which of the plurality of data objects identified in the index page are subject to the prefetch.

7. The method of claim 1, further comprising:

storing a list of data objects available locally to the client PEP.

8. The method of claim 7, wherein the fetch request is a first fetch request, the method further comprising:

receiving, at the client PEP, a second fetch request generated by the client, wherein the second fetch request is configured to request a second of the plurality of data objects identified by the index page;

retrieving the second of the plurality of data objects from a cache; and

providing the second of the plurality of data objects to the client PEP;

wherein an identifier for the second of the plurality of data objects is included in the list of data objects available locally to the client.

9. The method of claim 8, further comprising;

receiving, at the client PEP, freshness information related to the second of the plurality of data objects; and

providing the second of the plurality of data objects to the client PEP responsive to the freshness information indicating that the second of the plurality of data objects is fresh.

10. A method for managing a data transmission between an origin server and a client, the method comprising:

receiving an index page identifying a plurality of data objects contained in a data page;

receiving a list of data objects identifying a first data object included in the plurality of data objects, the first data object subject to a prefetch through the origin server;

receiving a fetch request generated by the client, wherein the fetch request is configured to request the first of the plurality of data objects; and

blocking the fetch request such that the fetch request is not provided to the origin server.

11. The method of claim 10, wherein receiving the index page comprises:

receiving the index page from the origin server.

12. The method of claim 10, further comprising:

comparing the list of data objects with the index page to determine which of the plurality of data objects identified in the index page are not subject to the prefetch.

13. The method of claim 12, wherein the fetch request is a first fetch request and wherein the method further comprises:

receiving a second fetch request, wherein the second fetch request is for one of the plurality of data objects determined not to be subject to the prefetch; and

providing the second fetch request to the origin server.

14. The method of claim 13, further comprising:

receiving the data object corresponding to the second fetch request; and

providing the data object corresponding to the second fetch request to the client.

15. The method of claim 10, further comprising:

storing a list of data objects available locally to the client.

16. The method of claim 15, wherein the fetch request is a first fetch request, the method further comprising:

receiving a second fetch request generated by the client, wherein the second fetch request is configured to request a second of the plurality of data objects;

retrieving the second of the plurality of data objects from a local storage device; and

providing the second of the plurality of data objects to the client;

wherein an identifier for the second of the plurality of data objects is included in the list of data objects available locally to the client.

17. The method of claim 16, further comprising;

receiving freshness information related to the second of the plurality of data objects; and

providing the second of the plurality of data objects to the client responsive to the freshness information indicating that the second of the plurality of data objects is fresh.

18. A system method for managing a data transmission, the system comprising:

a satellite modem configured to transfer information between an origin server and a client; and

a client-side PEP coupled to the satellite modem, the client side PEP configured to intercept a data page fetch request generated by the client and to block the data page fetch request, thereby preventing the data page fetch request from being sent between the client and the origin server.

19. The system of claim 18, further comprising:

a satellite dish coupled to the satellite modem.

20. The system of claim 18, wherein the satellite modem and the client-side PEP are integrated.

21. The system of claim 18, further comprising:

a browser;

wherein the client-side PEP and the browser are integrated.

22. The system of claim 18, further comprising:

a multipoint distribution system coupled to the client-side PEP;

wherein a plurality of users are connectable to the mulitpoint distribution system.

23. The system of claim 22, wherein the multipoint distribution system comprises one of:

a multichannel, multipoint distribution system (MMDS) and a local multipoint distribution system (LMDS).

24. The system of claim 18, further comprising:

a satellite network coupled to the satellite modem, the satellite network configured to transmit data to the satellite modem.

25. The system of claim 24, wherein the satellite network comprises:

a gateway satellite dish; and

a data transmission satellite.

26. The system of claim 18, wherein the client comprises:

a browser.

27. The system of claim 18, further comprising:

a local storage device configured to store a plurality of fetched data objects.

28. A system for managing a data transmission between an origin server and a client, the system comprising:

at least a first processor device;

at least a first memory device coupled to the at least a first processor device;

a plurality of instructions stored on the at least a first memory device, the plurality of instructions configured to cause the at least a first processor to;

process a request for a data page, wherein the request is generated by the client;

process an index page generated according to the origin server, wherein the index page identifies a plurality of data objects contained in the requested data page;

process a list of data objects that are subject to a prefetch through the origin server;

provide the index page to the client;

process a fetch request generated by the client, wherein the fetch request is configured to request a first of the plurality of data objects identified by the index page;

block the fetch request such that the fetch request is not provided to the origin server;

process the first of the plurality of data objects identified by the index page, wherein the first of the plurality of data objects is being provided by the origin server according to the prefetch; and

provide the received data object to the client.

29. The system of claim 28, wherein the plurality of instructions are further configured to cause the at least a first processor to:

provide the request to the origin server via a satellite network.

30. The system of claim 28, wherein the plurality of instructions are further configured to cause the at least a first processor to:

compare the list of data objects with the index page to determine which of the plurality of data objects identified in the index page are subject to the prefetch.

31. The system of claim 30, wherein the plurality of instructions are further configured to cause the at least a first processor to:

process a second fetch request, wherein the second fetch request is for a second of the plurality of data objects subject to the prefetch; and

provide the second fetch request to the origin server.

32. The system of claim 31, wherein the plurality of instructions are further configured to cause the at least a first processor to:

process the data object corresponding to the second prefetch request; and

provide the data object corresponding to the second prefetch request to the client.

33. The system of claim 28, wherein the plurality of instructions are further configured to cause the at least a first processor to:

store a list of data objects available locally to the client.

34. The system of claim 33, wherein the fetch request is a first fetch request and wherein the plurality of instructions are further configured to cause the at least a first processor to:

process a second fetch request generated by the client, wherein the second fetch request is configured to request a second of the plurality of data objects;

retrieve the second of the plurality of data objects from a local storage device; and

provide the second of the plurality of data objects to the client;

wherein an identifier for the second of the plurality of data objects is included in the list of data objects available locally to the client.

35. The system of claim 33, wherein the plurality of instructions are further configured to cause the at least a first processor to:

receive freshness information related to the second of the plurality of data objects; and

provide the second of the plurality of data objects to the client responsive to the freshness information indicating that the second of the plurality of data objects is fresh.

36. A system for managing a data transmission between an origin server and a client, the system comprising:

means for receiving an index page identifying a plurality of data objects contained in a data page;

means for receiving a list of data objects identifying a first data object included in the plurality of data objects, the first data object subject to a prefetch through the origin server;

means for receiving a fetch request generated by the client, wherein the fetch request is configured to request the first of the plurality of data objects; and

means for blocking the fetch request such that the fetch request is not provided to the origin server.