Method and system for object prediction

• US 20060271641A1
• Filed: 05/22/2006
• Published: 11/30/2006
• Est. Priority Date: 05/26/2005
• Status: Active Grant

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Bytemobile Inc. (Cloud Software Group)
• Inventors: Koopmans, Chris, Dakhane, Kapil, Stavrakos, Nicholas, Koopmans, Fred, Monks, Jeff
• Granted Patent: US 8,856,279 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H03M 7/30 Compression speech analysis-synthesis for redundancy reduction G10L19/00; for image communication H04N; Expansion; Suppression of unnecessary data, e.g. redundancy reduction
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/5651 Reducing the amount or size of exchanged application data
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04W 8/22 Processing or transfer of terminal data, e.g. status or physical capabilities
• CPC Class Codes: H04W 8/245 from a network towards a terminal

Abstract

A method including communicating with a content server, wherein the communication includes transmitting request data to the content server and receiving first response data associated with the request data; identifying response object data within the first response data; determining whether the response object data is to be downloaded; querying the content server for second response data that corresponds to the response object data based on the determination; transmitting the first response data to a user agent; and storing the second response data, wherein the second response data can be provided to the user agent in a subsequent request.

Claims

1. A method comprising:

communicating with a content server, wherein the communication includes transmitting request data to the content server and receiving first response data associated with the request data;

identifying response object data within the first response data;

determining whether the response object data is to be downloaded;

querying the content server for second response data that corresponds to the response object data based on the determination;

transmitting the first response data to a user agent; and

storing the second response data, wherein the second response data can be provided to the user agent in a subsequent request.

2. The method of claim 1, further comprising identifying request object data within the request data.

3. The method of claim 2, further comprising determining whether the response object data matches the request object data.

4. The method of claim 3, further comprising indicating that the response object data is to be downloaded if the response object data does not match the request object data.

5. The method of claim 3, further comprising determining whether the request object data is fresh or stale if the response object data matches the request object data.

6. The method of claim 5, further comprising indicating that the response object data can be deleted if the request object data is fresh.

7. The method of claim 5, further comprising determining whether the content server verified that the request object data was fresh or stale if the request object data is stale.

8. The method of claim 7, further comprising indicating that the response object data is to be downloaded if the content server verifies that the matching request object data is stale.

9. The method of claim 7, further comprising indicating that the response object data is not to be downloaded if the content server verifies that the matching request object data is fresh.

10. The method of claim 9, further comprising updating a freshness cache so that the client device can notify the user agent that a subsequent request object data that is marked as stale is fresh.

11. The method of claim 9, further comprising updating content data from stale to fresh at a data cache of the user agent.

12. The method of claim 2, further comprising:

determining whether the response object data includes a fully qualified domain name (FQDN) different from an FQDN of the request object data;

receiving mapping data from a DNS server if the response object data includes the FQDN different from the FQDN of the request object data; and

storing mapping data at a DNS cache.

13. The method of claim 1, further comprising receiving a subsequent request data and identifying subsequent request object data from within the subsequent request data.

14. The method of claim 13, further comprising determining whether the subsequent request object data corresponds to the stored second response data.

15. The method of claim 14, further comprising transmitting the stored second response data to the user agent if the subsequent request object data corresponds to the stored second response data.

16. The method of claim 14, further comprising transmitting the subsequent request object data to the content server if the subsequent request object data does not correspond to the stored second response data.

17. The method of claim 1, wherein querying the content server includes:

constructing request data corresponding to the response object data based on the determination;

transmitting the constructed request data to the content server; and

receiving second response data, wherein the second response data is associated with the constructed request data.

18. A method comprising:

receiving request data;

identifying request object data included in the request data;

determining whether the request object data corresponds to a predicted response data; and

transmitting the predicted response data to the user agent based on the determination.

19. The method of claim 18, wherein the determining whether the request object data corresponds to a predicted response data includes matching the request object data to a predicted request data stored at the client device, wherein the predicted request data identifies the predicted response data.

20. The method of claim 18, further comprising transmitting the predicted response data to the user agent if the request object data corresponds to the predicted response data.

21. The method of claim 18, further comprising transmitting the request object data to a content server if the request object data does not correspond to the predicted response data.

22. A method comprising:

receiving optimized data associated with a request for a web page, wherein the optimized data includes first response data associated with the request and an object list providing object data;

determining whether the object data is fresh in a user agent;

transmitting the first response data to the user agent;

constructing request data corresponding to the object data based on the determination;

transmitting the constructed request data to the content server; and

receiving second response data, wherein the second response data is associated with the constructed request data; and

storing the second response data, wherein the second response data can be provided to the user agent in a subsequent request.

23. The method of claim 22, further comprising receiving subsequent request data and identifying subsequent request object data from within the subsequent request data.

24. The method of claim 23, further comprising determining whether the subsequent request object data corresponds to the stored second response data.

25. The method of claim 24, further comprising transmitting the stored second response data to the user agent if the subsequent request object data corresponds to the stored second response data.

26. The method of claim 24, further comprising transmitting the subsequent request object data to the content server if the subsequent request object data does not correspond to the stored second response data.

27. The method of claim 22, wherein separating the optimized data further includes separating the optimized data into mapping data that is stored at a DNS cache, wherein the mapping data assists in constructing the request data corresponding to the object data.

28. The method of claim 22, wherein separating the optimized data further includes separating the optimized data into freshness data of stale request object data that has been determined to be fresh, wherein the freshness data notifies the user agent that the stale request object data is fresh.

29. A method comprising:

receiving response data associated with a request for a web page;

generating an response object list that identifies the response object data within the response data;

determining whether the response object data is to be downloaded to a user agent;

updating the response object list based on the determination; and

transmitting optimized data that includes response data and the response object list, wherein the response object data within the response object list is used to construct a request that provides a predicted response data based on the determination, wherein the predicted response data can be provided to the user agent in a subsequent request.

30. The method of claim 29, further comprising providing a request object list identifying the request object data within the request data.

31. The method of claim 30, further comprising determining whether the response object data matches the request object data.

32. The method of claim 31, further comprising indicating that the response object data is to be downloaded if the response object data does not match the request object data.

33. The method of claim 31, further comprising determining whether the request object data is fresh or stale if the response object data matches the request object data.

34. The method of claim 33, further comprising indicating that the request object data can be deleted if the request object data is fresh.

35. The method of claim 33, further comprising verifying with the content server that the request object data was fresh or stale if the request object data is stale.

36. The method of claim 35, further comprising indicating that the response object data is to be downloaded if the request object data has been verified to be stale.

37. The method of claim 35, further comprising indicating that the response object data is not to be downloaded if the request object data has been verified to be fresh.

38. The method of claim 29, further comprising determining whether the response object data includes a fully qualified domain name (FQDN) different from an FQDN of a request object data, wherein the request object data is associated with the request data;

and

receiving any existing mapping data based on the determination, wherein the mapping data corresponds to the FQDN of the response object data.

39. The method of claim 38, wherein receiving mapping data from the DNS server if the response object data includes the FQDN different from the FQDN of the request object data.

40. A method comprising:

receiving response data from a content server, wherein the response data is based on request data;

identifying response object data within the response data;

determining whether the response object data includes a fully qualified domain name (FQDN) different from an FQDN of a request object data, wherein the request object data is associated with the request data;

receiving any existing mapping data based on the determination, wherein the mapping data corresponds to the FQDN of the response object data; and

storing any existing mapping data into a DNS cache, wherein the mapping data can assist in constructing predicted request data.

41. The method of claim 40, further comprising determining whether mapping data exists at the DNS cache when the mapping data of the request object data is requested.

42. The method of claim 41, further comprising constructing the predicted request data with the mapping data stored at the DNS cache if the mapping data exists at the DNS cache.

43. The method of claim 40, wherein the mapping data is an IP address of the FQDN of the response object data.

44. A system comprising

a client device configured to receive request data from a user agent and transmit the request data, wherein the request data corresponds to a request for a web page;

and

an optimization server receiving the request data, communicating with a content server, wherein the communication includes the ability to transmit the request data to the content server and receive first response data associated with the request data, generating a response object list that identifies the response object data of the first response data, and transmitting the first response data and the response object list to the client device,

wherein the client device determines whether the response object data is fresh in the user agent;

transmits the first response data to the user agent;

constructs request data that is associated with the response object data based on the determination, transmits the constructed request data to the content server, receives second response data associated with the constructed request data, and stores the second response data, wherein the second response data can be provided to the user agent in a subsequent request.

45. The system of claim 44, wherein the client device is configured to receive mapping data from the optimization server and store the mapping data, which can assist in constructing the request data that is associated with the response object data.

46. A system comprising

a client device configured to receive request data from a user agent and transmit the request data, wherein the request data corresponds to a request for a web page;

and

an optimization server receiving the request data, communicating with a content server, wherein the communication includes the ability to transmit the request data to the content server and receive first response data associated with the request data, identifying response object data of the first response data, querying the content server for second response data corresponding to the response object data, and transmitting the first response data and the second response data,

wherein the wherein the first response data is transmitted to the user agent and the second response data is stored and can be provided to the user agent in a subsequent request.

47. A method comprising:

receiving optimized data associated with a request for a web page, wherein the optimized data includes first response data associated with the request and second response data associated with embedded object data within the first response data;

transmitting the first response data to the user agent; and

storing the second response data, wherein the second response data can be provided to the user agent in a subsequent request.

48. A method comprising:

receiving response data from a content server, wherein the response data is associated with a request for a web page;

generating an response object list that identifies the response object data within the response data;

determining whether the response object data is to be downloaded to a user agent;

querying the content server for second response data that is associated with the response object data; and

transmitting optimized data that includes response data and second response data, wherein the first response data is transmitted to a user agent and the second response data is stored and can be provided to the user agent in a subsequent request.

49. A computer-readable medium encoded with a computer-implemented method, the computer-readable medium comprising:

receiving optimized data associated with a request for a web page, wherein the optimized data includes first response data associated with the request and second response data associated with embedded object data within the first response data;

transmitting the first response data to the user agent; and

storing the second response data, wherein the second response data can be provided to the user agent in a subsequent request.

50. A computer-readable medium encoded with a computer-implemented method, the computer-readable medium comprising:

receiving optimized data associated with a request for a web page, wherein the optimized data includes first response data associated with the request and an object list providing object data;

determining whether the object data is fresh in a user agent;

transmitting the first response data to the user agent;

constructing request data corresponding to the object data based on the determination;

transmitting the constructed request data to the content server; and

receiving second response data, wherein the second response data is associated with the constructed request data; and

storing the second response data, wherein the second response data can be provided to the user agent in a subsequent request.

51. A computer-readable medium encoded with a computer-implemented method, the computer-readable medium comprising:

receiving response data associated with a request for a web page;

generating an object list that identifies the object data within the response data;

determining whether the object data is to be downloaded to a user agent;

updating the object list based on the determination; and

transmitting optimized data that includes response data and the object list, wherein the object data within the object list can be used to construct a request that provides a predicted response data based on the determination, wherein the predicted response data can be provided to the user agent in a subsequent request.

52. A computer-readable medium encoded with a computer-implemented method, the computer-readable medium comprising:

receiving response data from a content server, wherein the response data is associated with a request for a web page;

generating an response object list that identifies the response object data within the response data;

determining whether the response object data is to be downloaded to a user agent;

querying the content server for second response data that is associated with the response object data; and

transmitting optimized data that includes response data and second response data, wherein the first response data is transmitted to a user agent and the second response data is stored and can be provided to the user agent in a subsequent request.