Abstract: Aspects of the present disclosure provide techniques for improved cache localization. Network path data received from a plurality of routing advertisements for a communication network is aggregated, the communication network comprising a plurality of content delivery network (CDN) caches. Link utilization for a plurality of links in the communication network relating to the plurality of CDN caches is determined, and a connectivity table reflecting, for each of a plurality of routes in the communication network, one or more characteristics of the routes is generated. Communication between a requesting client and a first CDN cache, of the plurality of CDN caches, is routed based on the connectivity table and the determined link utilization.

Abstract: Techniques relating to caching a content object are disclosed. These techniques include transmitting, from a requestor to a first server, a revalidation request relating to a content object, and receiving, at the requestor from the first server, a response to the revalidation request indicating that the content object is not modified. The response is received at the requestor based on the first server determining that metadata describing one or more characteristics of the content object is stored in a cache associated with the first server and that the content object is not stored in the cache, and in response determining whether to retrieve content object data from any server based on analyzing a metric relating to retrieving the content object.

Abstract: Techniques relating to caching a content object are disclosed. These techniques include transmitting, from a requestor to a first server, a revalidation request relating to a content object, and receiving, at the requestor from the first server, a response to the revalidation request indicating that the content object is not modified. The response is received at the requestor based on the first server determining that metadata describing one or more characteristics of the content object is stored in a cache associated with the first server and that the content object is not stored in the cache, and in response determining whether to retrieve content object data from any server based on analyzing a metric relating to retrieving the content object.

Abstract: Embodiments herein describe a CDN where anycast routing is used to identify a load balancer for selecting a cache in the CDN to use to deliver a requested object to a user. In one embodiment, the user performs a DNS lookup to identify an anycast IP address for a plurality of load balancers in the CDN. The user can then initiate anycast routing using the anycast IP address to automatically identify a load balancer. Once the identified balancer selects the cache, the load balancer can close the anycast connection with the user device and use a redirect to provide the user device with a unicast path to the selected cache. The user device can then establish a unicast connection with the cache to retrieve (e.g., stream) the object.

Abstract: Techniques relating to caching a content object are disclosed. These techniques include transmitting, from a requestor to a first server, a revalidation request relating to a content object, and receiving, at the requestor from the first server, a response to the revalidation request indicating that the content object is not modified. The response is received at the requestor based on the first server determining that metadata describing one or more characteristics of the content object is stored in a cache associated with the first server and that the content object is not stored in the cache, and in response determining whether to retrieve content object data from any server based on analyzing a metric relating to retrieving the content object.

Abstract: Techniques relating to caching a content object are disclosed. These techniques include receiving, at a first server from a requestor, a revalidation request relating to a content object. The techniques further include determining that metadata describing one or more characteristics of the content object is stored in a cache associated with the first server and that the content object is not stored in the cache, and in response: determining, at the first server, whether to retrieve content object data from any server based on analyzing a metric relating to retrieving the content object, and transmitting from the first server to the requestor, based on analyzing the metadata, a response to the revalidation request indicating that the content object is not modified.

Abstract: The embodiments herein describe a CDN that uses revalidation to force edge servers to refresh their cached objects (i.e., download new copies of the objects from the origin data center). Revalidation can be used by edge servers to determine whether an object currently cached at the edge servers has been updated or changed in the origin data center. The embodiments herein leverage revalidation to perform a forced refresh to force the edge servers to refresh their cached object, regardless whether those cached objects match the objects stored in the origin data center. A forced refresh can be used when there is a network connection that may have caused the cached objects to become corrupted. Moreover, the forced refresh can be performed in batches so as not to overwhelm the network and computing resources in the CDN.

Abstract: Embodiments herein describe a CDN where anycast routing is used to identify a load balancer for selecting a cache in the CDN to use to deliver a requested object to a user. In one embodiment, the user performs a DNS lookup to identify an anycast IP address for a plurality of load balancers in the CDN. The user can then initiate anycast routing using the anycast IP address to automatically identify a load balancer. Once the identified balancer selects the cache, the load balancer can close the anycast connection with the user device and use a redirect to provide the user device with a unicast path to the selected cache. The user device can then establish a unicast connection with the cache to retrieve (e.g., stream) the object.

Abstract: Embodiments herein describe a CDN where anycast routing is used to identify a load balancer for selecting a cache in the CDN to use to deliver a requested object to a user. In one embodiment, the user performs a DNS lookup to identify an anycast IP address for a plurality of load balancers in the CDN. The user can then initiate anycast routing using the anycast IP address to automatically identify the closest load balancer. Once the identified balancer selects the cache, the load balancer can close the anycast connection with the user device and use an HTTP redirect to provide the user device with a unicast path to the selected cache. The user device can then establish a unicast connection with the cache to retrieve (e.g., stream) the object.

Abstract: The embodiments herein describe a CDN that uses revalidation to force edge servers to refresh their cached objects (i.e., download new copies of the objects from the origin data center). Revalidation can be used by edge servers to determine whether an object currently cached at the edge servers has been updated or changed in the origin data center. The embodiments herein leverage revalidation to perform a forced refresh to force the edge servers to refresh their cached object, regardless whether those cached objects match the objects stored in the origin data center. A forced refresh can be used when there is a network connection that may have caused the cached objects to become corrupted. Moreover, the forced refresh can be performed in batches so as not to overwhelm the network and computing resources in the CDN.

Abstract: Techniques relating to caching a content object are disclosed. A first server receives a revalidation request, relating to a content object, from a requestor. It is determined that metadata, relating to the content object, is stored in a cache associated with the first server. In response, the first server determines not to retrieve the content object from a second server. The content object is not stored in the cache. A response to the revalidation request, indicating that the content object is not modified, is transmitted from the first server to the requestor, based on analyzing the metadata.

Abstract: A method is performed at a mobile core, including assigning a first cache servicing a client device in response to a first request for a media content item based at least in part on a first IP address of the client device associated with a first edge location. The method further includes providing a first portion of the media content item from the first cache. The method additionally includes triggering a plurality of caches at edge locations proximate to the first edge location to retrieve a second portion of the media content item. The method also includes receiving a continuation request from the client device with a second IP address associated with a second edge location. The method further includes selecting a second cache from the plurality of caches based at least in part on the second IP address and continuing providing the media content item from the second cache.

Abstract: The embodiments herein describe a CDN that uses revalidation to force edge servers to refresh their cached objects (i.e., download new copies of the objects from the origin data center). Revalidation can be used by edge servers to determine whether an object currently cached at the edge servers has been updated or changed in the origin data center. The embodiments herein leverage revalidation to perform a forced refresh to force the edge servers to refresh their cached object, regardless whether those cached objects match the objects stored in the origin data center. A forced refresh can be used when there is a network connection that may have caused the cached objects to become corrupted. Moreover, the forced refresh can be performed in batches so as not to overwhelm the network and computing resources in the CDN.

Abstract: Techniques for improved media streaming are provided. A request for a variant list for streaming media content is received from a requesting entity, where the request includes a predefined flag. A set of predefined rules corresponding to the predefined flag is identified. The variant list is pruned based on the set of predefined rules, and the pruned variant list is transmitted to the requesting entity.

Abstract: Techniques relating to caching a content object are disclosed. A first server receives a revalidation request, relating to a content object, from a requestor. It is determined that metadata, relating to the content object, is stored in a cache associated with the first server. In response, the first server determines not to retrieve the content object from a second server. The content object is not stored in the cache. A response to the revalidation request, indicating that the content object is not modified, is transmitted from the first server to the requestor, based on analyzing the metadata.

Abstract: Techniques for improved media streaming are provided. A request for a variant list for streaming media content is received from a requesting entity, where the request includes a predefined flag. A set of predefined rules corresponding to the predefined flag is identified. The variant list is pruned based on the set of predefined rules, and the pruned variant list is transmitted to the requesting entity.

Abstract: A method is performed at a mobile core, including assigning a first cache servicing a client device in response to a first request for a media content item based at least in part on a first IP address of the client device associated with a first edge location. The method further includes providing a first portion of the media content item from the first cache. The method additionally includes triggering a plurality of caches at edge locations proximate to the first edge location to retrieve a second portion of the media content item. The method also includes receiving a continuation request from the client device with a second IP address associated with a second edge location. The method further includes selecting a second cache from the plurality of caches based at least in part on the second IP address and continuing providing the media content item from the second cache.

Abstract: A method is performed at a mobile core, including assigning a first cache servicing a client device in response to a first request for a media content item based at least in part on a first IP address of the client device associated with a first edge location. The method further includes providing a first portion of the media content item from the first cache. The method additionally includes triggering a plurality of caches at edge locations proximate to the first edge location to retrieve a second portion of the media content item. The method also includes receiving a continuation request from the client device with a second IP address associated with a second edge location. The method further includes selecting a second cache from the plurality of caches based at least in part on the second IP address and continuing providing the media content item from the second cache.

Abstract: A method is performed at a mobile core, including assigning a first cache servicing a client device in response to a first request for a media content item based at least in part on a first IP address of the client device associated with a first edge location. The method further includes providing a first portion of the media content item from the first cache. The method additionally includes triggering a plurality of caches at edge locations proximate to the first edge location to retrieve a second portion of the media content item. The method also includes receiving a continuation request from the client device with a second IP address associated with a second edge location. The method further includes selecting a second cache from the plurality of caches based at least in part on the second IP address and continuing providing the media content item from the second cache.

Abstract: A system can include a reconciliation engine configured to evaluate metadata in a given manifest file of a plurality of manifest files generated for redundant copies of a given media asset. The metadata describes a condition of a given chunk of media content in one of the redundant copies of the given media asset. The system can also include a manifest modification function configured to modify the given manifest file for the given chunk of media content in response to the reconciliation engine detecting that the given chunk of media content is damaged based on the evaluation of the metadata associated with the given chunk of media content in the given manifest file.