MULTI-LEVEL PEERING IN A CONTENT DELIVERY FRAMEWORK

• US 20150180725A1
• Filed: 12/22/2014
• Published: 06/25/2015
• Est. Priority Date: 12/13/2012
• Status: Active Grant

• Current Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Original Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Inventors: Varney, Lewis Robert, Lipstone, Laurence R., Crowder, William, Swart, Andrew, Newton, Christopher
• Granted Patent: US 10,135,697 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 12/0808 with cache invalidating means G06F12/0815 takes precedence
• CPC Class Codes: G06F 15/173 using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
• CPC Class Codes: G06F 15/177 Initialisation or configuration control processor initialisation G06F9/4405
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine
• CPC Class Codes: G06F 9/5083 Techniques for rebalancing the load in a distributed system
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/0823 characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for optimising operational conditions of wireless networks H04W24/02
• CPC Class Codes: H04L 41/0869 Validating the configuration within one network element
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/50 Network service management, e.g. ensuring proper service fulfilment according to agreements
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 41/509 wherein the managed service relates to media content delivery, e.g. audio, video or TV
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/83 based on usage prediction
• CPC Class Codes: H04L 61/10 of different types
• CPC Class Codes: H04L 61/2503 : Translation of Internet protocol [IP] addresses
• CPC Class Codes: H04L 61/4511 : using domain name system [DNS]
• CPC Class Codes: H04L 61/4535 : using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers
• CPC Class Codes: H04L 61/58 : Caching of addresses or names
• CPC Class Codes: H04L 65/403 : Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 65/60 : Network streaming of media packets
• CPC Class Codes: H04L 67/01 : Protocols
• CPC Class Codes: H04L 67/06 : specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1078 : Resource delivery mechanisms
• CPC Class Codes: H04L 67/2885 : Hierarchically arranged intermediate devices, e.g. for hierarchical caching
• CPC Class Codes: H04L 67/289 : Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/55 : Push-based network services
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5682 : Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 67/60 : Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70
• CPC Class Codes: H04L 69/03 : Protocol definition or specification protocol conformance testing H04L1/244

Abstract

A computer-implemented method is operable in a network comprising multiple delivery service endpoints running on a plurality of devices where each of the delivery service endpoints is constructed and adapted to deliver resources. A plurality of the delivery service endpoints comprise a group, wherein each node in the group has at least one kind of responsibility relating to delivery of resources. The method includes receiving a request at a node; and, based on what kind of responsibility the node has for said request, attempting to process the request outside the group.

Claims

1. A computer-implemented method, operable in a network comprising multiple delivery service endpoints running on a plurality of devices, each of said delivery service endpoints constructed and adapted to deliver resources, a plurality of said multiple delivery service endpoints comprising a group, wherein each node in said group has at least one kind of responsibility relating to delivery of resources, the method comprising:

(A) receiving a request at a node in the group; and

(B) based on what kind of responsibility said node has for said request, attempting to process the request outside the group.

2. The method of claim 1 wherein said attempting to process the request in (B) comprises one of:

(B)(1) proxying the request outside the group; and

(B)(2) redirecting the request outside the group.

3. The method of claim 1 wherein the request relates to a particular resource and wherein said attempting to process the request in (B) comprises:

(B)(2) attempting to obtain the particular resource from outside the group.

4. The method of claim 1 wherein the attempting to process the request outside the group in (B) comprises attempting to process the request using a second node.

5. The method of claim 4 wherein the second node comprises a remote fill target.

6. The method of claim 1 wherein the said attempting to process the request outside the group in (B) targets a subcluster outside the group.

7. The method of claim 1 wherein the group comprises one or more subclusters.

8. The method of claim 7 wherein the one or more subclusters comprise a first supercluster.

9. The method of claim 8 wherein the said attempting to process the request outside the group in (B) targets a second supercluster distinct from said first supercluster, and

10. The method of claim 1 wherein the group comprises a peer group of said multiple delivery service endpoints.

11. The method of claim 10 wherein said peer group comprises a super-cluster of said plurality of nodes of said multiple delivery service endpoints.

12. The method of claim 1, wherein the request relates to a particular resource and wherein said attempting to process in (B) is based on at least one kind responsibility said node has for requests relating to said particular resource.

13. The method of claim 12 wherein the kind of responsibility the node has for the particular resource is defined in a policy associated with the particular resource.

14. The method of claim 13 wherein the policy is defined for a group of resources.

15. The method of claim 14 wherein the group of resources comprises a property.

16. The method of claim 13 wherein the policy is based on one or more of:

thresholds for popularity, cacheability, and resource size.

17. The method of claim 1 wherein the group comprises a first cluster and wherein the attempting to process the request outside the group in (B) comprises attempting to process the request at a peer cluster distinct from the first cluster.

18. The method of claim 1 wherein the kind of responsibility that said node has is taken from a discrete set of responsibilities comprising of:

non-responsible, cache-responsible, and fill-responsible.

19. The method of claim 1 wherein the request relates to a particular resource and wherein said attempting to process in (B) is also based on a resource type of said particular resource.

20. The method of claim 1 wherein, when no node in said group has responsibility for said request, said attempting to process said request in (B) comprises:

(B)(1) redirecting the request to a second node outside the group.

21. The method of claim 1 wherein the request relates to a particular resource and wherein, when no node in said group has responsibility for said request, said attempting to process said request in (B) comprises:

(B)(2) proxying the request to a second node outside the group.

22. The method of claim 1 wherein the request relates to a particular resource and wherein, when said node is fill-responsible for said request, and said particular resource is not in a cache of said node, said attempting to process said request in (B) comprises:

(B)(3) attempting to obtain the resource from a second node outside the group.

23. A device, operable in a network comprising multiple delivery service endpoints running on a plurality of devices, each of said delivery service endpoints constructed and adapted to deliver resources, a plurality of said multiple delivery service endpoints comprising a group, wherein each node in said group has at least one kind of responsibility relating to delivery of resources,

the device comprising:

(a) hardware including memory and at least one processor, and

(b) a service running on said hardware, wherein said service is configured to;

(A) receive a request at a node; and

(B) based on what kind of responsibility said node has for said request, attempt to process the request outside the group.

24. A system comprising a device according to claim 23.

25. A computer program product having computer readable instructions stored on non-transitory computer readable media, the computer readable instructions including instructions for implementing a computer-implemented method, said method operable on a device comprising hardware including memory and at least one processor and running a service on said hardware, said method operable in a network comprising multiple delivery service endpoints running on a plurality of devices, each of said delivery service endpoints constructed and adapted to deliver resources, a plurality of said multiple delivery service endpoints comprising a group, wherein each node in said group has at least one kind of responsibility relating to delivery of resources,

said method comprising:

(A) receiving a request at a node; and

(B) based on what kind of responsibility said node has for said request, attempting to process the request outside the group.