CONTENT DELIVERY FOR CLIENT SERVER PROTOCOLS WITH USER AFFINITIES USING CONNECTION END-POINT PROXIES

• US 20100088370A1
• Filed: 12/07/2009
• Published: 04/08/2010
• Est. Priority Date: 08/12/2003
• Status: Active Grant

• Current Assignee: Riverbed Technology, LLC (Riverbed Technology Incorporated)
• Original Assignee: Riverbed Technology Incorporated
• Inventors: Wu, David Tze-Si, McCanne, Steven
• Granted Patent: US 8,635,346 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 43/12 Network monitoring probes
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/20 Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel

Abstract

In a network supporting transactions between clients and servers over a network path having operating characteristics to overcome, data is transported to overcome the operating characteristics using user affinities and dynamic user location information to selectively preload data, or representations, signatures, segments, etc. of data, in order to overcome the one or more operating characteristic. Examples of operating characteristics to overcome include bandwidth limitations, errors and latency. The dynamic location information can be stored in data structures accessible by agents of a data server and the data structures are populated based on user activities with respect to proxies associated with user locations, or the dynamic location information can be obtained implicitly as proxies maintain connections after termination by clients and the use of those maintained connections for preloading of data for the users associated with those clients. The data being preloaded can be protocol-specific data or protocol-independent data.

Claims

1. In a network supporting transactions between clients and servers,

wherein a client is a host that requests a transaction and a server is a host that issues responses responsive to client requests and wherein packets between a client and a server travel over a network path comprising one or more hops and having one or more operating characteristic to overcome, a method of transporting data to overcome the one or more operating characteristic comprising:

identifying user affinity for a data object, wherein user affinity of the data object indicates which user or users might be associated with the data object such that a user having user affinity to the data object is more likely to request the data object than a user not having user affinity to the data object;

dynamically identifying user locations, wherein a user location represents an association between a user and preload node, wherein a preload node is a network location wherein preloaded data can be stored to overcome at least one of the one or more operating characteristics;

transporting particular data having a specified user affinity, in advance of a client request on behalf of a particular user having a user affinity for the particular data, from a server to a preload node identified as a user location for the particular user,

wherein identifying the user affinity is performed at or near the server using the data object, wherein the data object is not received from the client or the particular user.

2. The method of claim 1, wherein the one or more operating characteristics are selected from bandwidth usage, error rate and latency.

3. The method of claim 1, wherein the data objects comprise one or more of an e-mail object, a dataset, a file, or a portion of a database.

4. The method of claim 1, wherein the user affinity of a data object is to a single user.

5. The method of claim 1, wherein the user affinity of a data object is to a plurality of users.

6. The method of claim 1, wherein identifying user affinity comprises:

determining which users access which data objects; and

assigning user affinity to those data objects according to which users access those data objects.

7. The method of claim 1, wherein dynamically identifying user locations comprises:

determining which users access the network using particular clients;

determining the preload nodes associated with those particular clients; and

populating a user location database with records associating those users with the preload nodes, thereby identifying user locations.

8. The method of claim 1, wherein each preload node is a proxy.

9. The method of claim 1, wherein each preload node includes a data cache.

10. The method of claim 1, wherein each preload node includes a proxy and a segment store.

11. The method of claim 1, wherein identifying the user affinity for the data object is performed at a data center, wherein the user affinity is based on an intended recipient of the data object, and wherein identifying the user affinity for the data object includes inspecting, with a content delivery agent of the data center, the data object to determine the intended recipient, and

wherein the particular data having the specified user affinity is transported in advance of any client request to the data center for the particular data and is transported from a server of the data center to the preload node.

12. The method of claim 11, wherein the data center includes the user location database.

13. The method of claim 11, wherein the dynamic user location is determined from previous interactions of the particular user with the data center.

14. In a network supporting clients, servers and proxies, wherein a client is a host that transmits requests to a server, a server is a host that issues responses responsive to client requests, and a proxy is a host that acts as a protocol intermediary between one or more clients and one or more servers, and wherein packets between a client and a server travel over a network path comprising one or more hops and having one or more operating characteristic to overcome, a method of transporting data to overcome the one or more operating characteristic, the method comprising:

determining a preferred proxy for one or more users by detecting a proxy used by the one or more users;

storing an association between the one or more users and the preferred proxy, wherein the association is stored at least when the one or more users are not currently using the preferred proxy;

detecting either a newly available data object stored on a server or a modification to an existing data object stored on a server;

identifying user affinity for the detected data object, wherein user affinity of the data object indicates which user or users might be associated with the data object such that a user having user affinity to the data object is more likely to requested data object then a user and not having user affinity to the data object;

identifying a preferred proxy for the user or users with user affinity associated with the detected data object, wherein the preferred proxy is determined from the stored association; and

transporting the detected data object, in advance of a client request on behalf of a particular user having a user affinity for the detected data object, from a server to the preferred proxy.

15. The method of claim 14, wherein the data objects comprise one or more of an e-mail object, a dataset, a file, or a portion of a database.

16. The method of claim 14, wherein identifying user affinity comprises:

determining which users access which data objects; and

assigning user affinity to those data objects according to which users access those data objects.

17. The method of claim 14, wherein the transporting is performed when the one or more users are not currently using the preferred proxy