TRACKING INVALIDATION COMPLETION IN A CONTENT DELIVERY FRAMEWORK

• US 20140223003A1
• Filed: 12/03/2013
• Published: 08/07/2014
• Est. Priority Date: 12/13/2012
• Status: Abandoned Application

• 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
• Application Number:
  US14/094,868
• Publication Number:
  US 20140223003A1
• Time in Patent Office: Days
• US Class Current: 709/224
• 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 method in a content delivery framework includes, at a first service, receiving invalidation information relating to at least one resource; invalidating the at least one resource; and then, when the at least one resource has been invalidated at the first service, providing first information about the invalidating to a collector system. At a second service distinct from the first service, receiving the invalidation information relating to the at least one resource; invalidating the at least one resource at the second service; and then, when the at least one resource has been invalidated at the second service, providing second information about the invalidating at the second service to the collector system.

Claims

1. A computer-implemented method comprising:

(A) at a first service operable on a device comprising hardware including memory and at least one processor;

(A)(1) receiving invalidation information relating to at least one resource;

(A)(2) in response to said receiving in (A)(1), invalidating said at least one resource; and

then, when said at least one resource has been invalidated at said first service,

(A)(3) providing first information about said invalidating in (A)(2) to a collector system.

2. The method of claim 1 further comprising:

(B) at a second service distinct from said first service, said second service running on a second device comprising hardware including memory and at least one processor;

(B)(1) receiving said invalidation information relating to said at least one resource;

(B)(2) in response to said receiving in (B)(1), invalidating said at least one resource; and

then, when said at least one resource has been invalidated at said second service,

(B)(3) providing second information about said invalidating in (B)(2) to said collector system.

3. The method of claim 2 wherein said first resource is invalidated in (A)(2) at a first time, and wherein said second resource is invalidated in (B)(2) at a second time distinct from said first time.

4. The method of claim 2 wherein said first device is distinct from said second device.

5. The method of claim 1 wherein the first information is provided to the collector system in (A)(3) via a reducer system.

6. The method of claim 5 wherein the reducer system comprises a reducer services network.

7. The method of claim 2 wherein the first information and the second information are provided to the collector system via a reducer system comprising a reducer services network, wherein the reducer services network comprises a first reducer service and a second reducer service distinct from said first reducer service, and wherein (i) the first service provides the first information to the collector system via the first reducer service, and (ii) the second service provides the second information to the collector system via the second reducer service.

8. The method of claim 1 wherein the first information comprises first information about invalidation of the at least on resource at the first service.

9. The method of claim 8 wherein the first information about invalidation comprises a first indication about said at least one resource having been invalidated at said first service.

10. The method of claim 1 wherein said collector system comprises at least one collector service, the method further comprising:

obtaining said first information at said at least one collector service.

11. The method of claim 10 further comprising:

obtaining, at said collector service, information about said at least one resource having been invalidated on at least one other service distinct from said first service.

12. The method of claim 11 further comprising:

determining, at said collector service, whether said at least one resource has been invalidated at a plurality of services, said plurality of services comprising said first service and said at least one other service.

13. The method of claim 12 wherein said invalidation information was provided to a plurality of services, said plurality of services comprising said first service and said at least one other service the method further comprising:

determining, at said collector service, whether said at least one resource has been invalidated on at least some of said plurality of services.

14. The method of claim 12 wherein said determining comprises:

determining whether said at least one resource has been invalidated at all of said plurality of services.

15. The method of claim 1 wherein the invalidation information is received at said first service in (A)(1) as part of an invalidation manifest comprising one more invalidation commands.

16. The method of claim 15 wherein an invalidation command of said one more invalidation commands is selected from:

(i) an invalidation command that specifies a single resource; and

(ii) an invalidation command that specifies a group of resources.

17. The method of claim 16 wherein, when an invalidation command specifies a group of resources, the group is specified by a pattern.

18. The method of claim 1 wherein said invalidation information comprises an invalidation period, wherein said first resource is invalidated in (A)(2) at a first time, and wherein said first time is within said invalidation period.

19. The method of claim 3 wherein said invalidation information comprises an invalidation period, and wherein said first time is within said invalidation period and wherein the second time is within said invalidation period.

20. The method of claim 18 wherein said invalidating in (A)(2) comprises:

considering said at least one resource to be not useable based on a function of said invalidation period.

21. The method of claim 18 wherein said first time is selected based on a random value within said invalidation period.

22. The method of claim 1 wherein said invalidating in (A)(2) comprises:

(A)(2)(i) determining whether said invalidation information relates to any resources currently maintained on said first service, and, based on said determining, when said invalidation information relates to at least one resource not currently maintained on said first service, maintaining on said first service at least some of said invalidation information.

23. A computer-implemented method, the method comprising:

(A) on a device comprising hardware including memory and at least one processor, providing, to a plurality of services, invalidation information relating to at least one resource; and

then

(B) obtaining completion tracking information from a collector system, said completion information comprising an indication about invalidation of said at least one resource by at least some of said plurality of services.

24. The method of claim 23 wherein said completion tracking information comprises a completion indication about invalidation of said at least one resource by all of said plurality of services.

25. The method of claim 23 wherein the providing in (A) and the obtaining in (B) occur on different devices.

26. A computer-implemented method, the method comprising:

(A) at a collector service on a device comprising hardware including memory and at least one processor, obtaining, from each of a plurality of services, completion tracking information, the completion tracking information from each particular service of said plurality of services comprising information relating to invalidation of at least one resource by said particular service, wherein each of said plurality of services attempted to invalidate said at least one resource in response to receipt of invalidation information relating to said at least one resource and obtained by each of said plurality of services; and

(B) based on the completion tracking information obtained in (A), determining a completion status for said invalidation information.

27. The method of claim 26 wherein the completion status is based on completion tracking information obtained from all of the plurality of services.

28. The method of claim 26 wherein the collector service obtains at least some completion tracking information via a reducer services network.

29. The method of claim 26 wherein at least one of said plurality of services is a delivery service in a content delivery network.

30. A 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)(1) receive invalidation information relating to at least one resource;

(A)(2) invalidate said at least one resource; and

then, when said at least one resource has been invalidated at said service,

(A)(3) provide first information about said invalidating in (A)(2) to a collector system.

31. 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 comprising:

(A) at a first service operable on said device;

(A)(1) receiving invalidation information relating to at least one resource;

(A)(2) in response to said receiving in (A)(1), invalidating said at least one resource; and

then, when said at least one resource has been invalidated at said first service,

(A)(3) providing first information about said invalidating in (A)(2) to a collector system.