Proximity as an aid to caching and secondary serving of data

• US 7,761,572 B1
• Filed: 07/30/2004
• Issued: 07/20/2010
• Est. Priority Date: 04/01/1999
• Status: Expired due to Term

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Auerbach, Karl G.
• Primary Examiner(s): Najjar; Saleh
• Assistant Examiner(s): NGUYEN, THUONG
• Application Number:
  US10/902,971
• Time in Patent Office: 2,181 Days
• Field of Search: 709203-239, 709/200, 709/271, 709/226, 709/235, 370238-408, 370/235, 395200-404
• US Class Current: 709/226
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/023 using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 4/029 Location-based management or tracking services

Abstract

A proximity-based content control method “propagates” or positions content based upon “proximity” between various nodes on a network. The nodes between which the content is propagated include content libraries, servers, and clients. In one case, the relative proximities of two content servers to a particular client or group of clients determines which of these servers serves client requests. In another case, the method employs anticipatory loading of content from a library to a server based upon the server'"'"'s proximity to a given client-base. Yet another application involves adding or removing server capacity to a network based upon proximity to clients. Another application applies proximity affects to cache release algorithms. A “content control system” calculates proximity dynamically and automatically decides whether to move content based upon the proximity calculation.

Claims

1. A method of loading content to a server in anticipation of a need for the content by network clients, the method comprising:

determining the location of at least one client not currently requesting the content but that is likely to request the content;

determining a first proximity between the at least one client and a first server not currently storing but configured to store and serve the content;

determining a second proximity between the at least one client and a second server not currently storing but configured to store and serve the content; and

based upon the relative values of the first and second proximities, loading the content into one of the first server or the second server from a third entity.

2. The method of claim 1, wherein the first and second proximities are determined dynamically by a content control system.

3. The method as recited in claim 1, wherein determining the location comprises:

determining the location where clients are expected to subscribe to a service making the content available.

4. The method as recited in claim 1, wherein determining the location comprises:

determining the location that is to receive a service making the content available.

5. The method as recited in claim 1, wherein determining the location is not performed using an activity schedule of the at least one client.

6. The method as recited in claim 1, wherein the at least one client includes a plurality of clients, and wherein the location is associated with the plurality of clients.

7. The method as recited in claim 1, wherein the location is a current location of the at least one client.

8. The method as recited in claim 1, wherein determining the location comprises:

ascertaining that a service making the content available will be provided at the location.

9. A method of loading content to a server in anticipation of need by network clients, the method comprising:

(a) determining the location of a client or group of clients that will require access to the content;

(b) identifying a first server currently storing the content and serving the client'"'"'s requirements for access to the content;

(c) identifying a second server that does not currently store said content but that is configured to store and serve the content;

(d) determining a first proximity between the first server and the client or group of clients;

(e) determining a second proximity between the second server and the client or group of clients, wherein at least one of the first or second proximities is determined by at least one of the following factors, the factors weighted based on the type of content to be loaded;

congestion, noise and loss on a network segment, or charges incurred to send; and

(f) if the relative values of the first and second proximities meet a defined constraint, loading the content to the second server from a third entity.

10. The method of claim 9, wherein (d) includes determining whether the server and the client or group of clients are on the same sub-network.

11. A method of loading content to a server in anticipation of a need for the content by network clients, the method comprising:

(a) determining the location of a client or group of clients that are likely to access the content;

(b) determining the relative proximities of (i) the client or group of clients to a first server not currently storing but configured to store and serve the content and (ii) the client or group of clients and a second server not currently storing but configured to store and serve the content; and

(c) based upon the relative proximities, loading the content into one of the first server or the second server from a third entity.

12. The method of claim 11, wherein the first and second proximities are determined dynamically by a content control system.

13. A method of selecting a server to fill a client request for content, the method comprising:

(a) determining that one or more clients needs or will need to receive the content;

(b) determining a first proximity between the one or more clients and a first server configured to supply the content;

(c) determining a second proximity between the one or more clients and a second server configured to supply the content; and

(d) based upon the relative values of the first and second proximities, choosing one of the first or second servers to receive the content from a third entity in order to be able to fill future client requests for the content, wherein at least one of the first or second proximities is determined by at least one of the following factors;

congestion, noise and loss on a network segment, or charges incurred to send.

14. The method of claim 13, wherein the first and second proximities are determined dynamically by a content control system.

15. The method of claim 13, wherein the content is provided by the server that is most proximate to the one or more of clients.

16. The method of claim 13, wherein the content is multimedia content.

17. The method of claim 13, wherein at least one of the first and second proximities is determined by a combination of at least two of the following factors:

bandwidth, number of hops, congestion, noise and loss on a network segment, and charges incurred to send.

18. The method of claim 13, wherein the first proximity is determined by a considering whether the first server and the one or more clients are on the same sub-network.

19. The method of claim 18, wherein content is provided by the first server when the first server and the one or more clients are on the same sub-network and the second server and the one or more clients are not on the same sub-network.

20. A method of loading content to a server in anticipation of a need for the content by network clients, the method comprising:

predicting that at least one client is likely to request the content, wherein the at least one client is not currently requesting the content;

determining a first proximity between the at least one client and a first server not currently storing but configured to store and serve the content;

determining a second proximity between the at least one client and a second server not currently storing but configured to store and serve the content; and

based upon the relative values of the first and second proximities, loading the content into one of the first server or the second server from a third entity.

21. The method as recited in claim 20, wherein predicting is not performed based upon scheduled activities of the at least one client.

22. The method as recited in claim 20, wherein predicting is performed based upon a location of the at least one client.

23. The method as recited in claim 22, wherein a service making the content available will be provided at the location.