Caching in Mobile Networks

• US 20140237071A1
• Filed: 09/30/2011
• Published: 08/21/2014
• Est. Priority Date: 09/28/2011
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Friman, Erik, Arvidsson, ke, Westberg, Lars
• Granted Patent: US 9,703,752 B2
• Time in Patent Office: Days
• US Class Current: 709/216
• CPC Class Codes: G06F 15/17331 Distributed shared memory [DSM], e.g. remote direct memory access [RDMA]
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics

Abstract

There is described a method for optimising the distribution of data objects between caches in a cache domain of a resource limited network. User requests for data objects are received at caches in the cache domain. A notification is sent from each cache at which a request is received to a cache manager. The notification reports the user request and identifies the requested data object. At the cache manager, object information including the request frequency of each requested data object and the locations of the caches at which the requests were received is collated and stored. At the cache manager, objects for distribution within the cache domain are identified on the basis of the object information. Instructions are sent from the cache manager to the caches to distribute data objects stored in those caches between themselves. The objects are classified into classes according to popularity, the classes including a high popularity class comprising objects which should be distributed to all caches in the cache domain, a medium popularity class comprising objects which should be distributed to a subset of the caches in the cache domain, and a low popularity class comprising objects which should not be distributed.

Claims

1-23. -23. (canceled)

24. A cache manager for controlling distribution of content stored in caches in a cache domain in a packet data network, the cache manager comprising:

an object monitor configured to receive notifications from caches in the cache domain about data objects requested at those caches;

an object database configured to collate and store object information about the requested data objects, the object information including information about the caches at which the data objects have been requested and frequency with which the requests have been made;

an object distributor configured to;

identify objects for distribution on the basis of the object information and instruct the caches in the cache domain to distribute data objects stored in those caches between themselves;

wherein the object information includes a popularity parameter for each object, and the object distributor is configured to classify the objects into one of at least three classes, the classes including;

a high popularity class comprising objects which should be distributed to all caches in the cache domain;

a medium popularity class comprising objects which should be distributed to one or more subsets of the caches in the cache domain; and

a low popularity class comprising objects which should not be distributed.

25. The cache manager of claim 24, further comprising:

a topology monitor configured to retrieve topology information about the topology of the cache domain;

a topology database configured to store the topology information;

wherein the topology information includes data relating to one or more of the following;

a topology structure of the cache domain;

bandwidth limitations of links between elements in the topology structure;

storage capabilities of the caches;

location of caches in the topology structure;

current loads sustained by the links between elements in the topology structure; and

transport types for data within the cache domain;

wherein the object distributor is configured to make use of the topology information in the determination of how the objects should be distributed between the caches.

26. The cache manager of claim 25:

wherein the topology information includes a daily load profile for each cache in the cache domain, the daily load profile indicating periods of high load and low load for that cache;

wherein the object distributor is configured to allocate objects in the medium popularity class to caches in such a way that, at all times of the day, each object is stored on at least one cache in a low load period.

27. The cache manager of claim 25, wherein the object distributor is configured to instruct the caches to distribute objects within the medium popularity class in such a way that more popular objects are distributed to a relatively high number of caches and less popular objects are distributed to a relatively low number of caches.

28. The cache manager of claim 27, wherein the more popular objects in the medium popularity class are distributed to many caches relatively close to users and less popular objects are distributed to a few caches relatively central in the network.

29. The cache manager of claim 24, wherein the cache manager is configured to control the distribution of the data objects between caches in the cache domain so that the cache domain functions as a large virtual cache.

30. The cache manager of claim 24, wherein the packet data network is a mobile network.

31. The cache manager of claim 24, wherein the cache manager is a discrete entity and includes a communications system for communicating with elements in the packet data network.

32. The cache manager of claim 31, wherein the cache manager is associated with one of the caches in the cache domain.

33. The cache manager of claim 24, wherein functionality of the cache manager is distributed among network elements in the cache domain.

34. A method for optimizing distribution of data objects between caches in a cache domain of a resource limited network, the method comprising:

receiving user requests for data objects at caches in the cache domain;

sending a notification from the cache at which a request is received to a cache manager, the notification reporting the user request and identifying the requested data object;

at the cache manager, collating and storing object information including the request frequency of each requested data object and the locations of the caches at which the requests were received;

at the cache manager, identifying objects for distribution within the cache domain on the basis of the object information;

sending instructions from the cache manager to the caches to distribute data objects stored in those caches between themselves; and

distributing the data objects between the caches by an object distributor;

wherein the object information includes a popularity parameter for the object, and the object distributor is configured to classify the object into one of at least three classes, the classes including;

a high popularity class comprising objects which should be distributed to all caches in the cache domain;

a medium popularity class comprising objects which should be distributed to one or more subsets of the caches in the cache domain; and

a low popularity class comprising objects which should not be distributed.

35. The method of claim 34, wherein the objects are distributed using transmission capacity of the network that would otherwise be unused.

36. The method of claim 34, wherein the cache manager takes into account at least one of the following when identifying the data objects for distribution:

topology of the network;

priority of the requested data objects;

frequency of requests for particular data objects.

37. The method of claim 34, wherein the cache manager:

takes into account a daily load profile of each cache in the cache domain, the daily load profile indicating periods of high load and low load for that cache;

allocates objects in the medium popularity class to caches in such a way that, at all times of the day, the object is stored on at least one cache in a low load period.

38. The method of claim 34, further comprising distributing objects within the medium popularity class in such a way that more popular objects are distributed to a relatively high number of caches and less popular objects are distributed to a relatively low number of caches.

39. The method of claim 38, wherein the more popular objects in the medium popularity class are distributed to many caches relatively close to users and less popular objects are distributed to a few caches relatively central in the network.

40. The method of claim 34, wherein the caches are associated with or part of Radio Network Controllers, Radio Base Stations, or other Radio Access Network nodes.

41. The method of claim 34, wherein the data objects are distributed between the caches during off-peak periods.

42. The method of claim 34, wherein functionality of the cache manager is distributed between network elements in the cache domain.

43. The method of claim 34, further comprising:

at each cache, forming a distribution queue of objects to be distributed to other caches;

placing most-recently-used or most-frequently-used objects at a head of the distribution queue.

44. The method of claim 34, further comprising sending messages including object popularity statistics from the caches to the cache controller.

45. A computer program product stored in a non-transitory computer readable medium for controlling a cache manager in a resource limited network, the computer program product comprising software instructions which, when run on the cache manager, causes the cache manager to:

retrieve notifications from caches in a cache domain controlled by the cache manager, the notifications including details of data objects recently requested at those caches;

collate and store object information about the requested data objects, the object information including the location and popularity of requested data objects;

identify objects for distribution on the basis of the object information;

instruct the caches in the network to distribute data objects stored in those caches between themselves;

wherein the object information includes a popularity parameter for each object, and the objects are classified into one of at least three classes, the classes including;

a high popularity class comprising objects which should be distributed to all caches in the cache domain;

a medium popularity class comprising objects which should be distributed to one or more subsets of the caches in the cache domain; and

a low popularity class comprising objects which should not be distributed.