Remediation of the impact of detected synchronized data requests in a content delivery network

US10154074B1 · US · B1

Patent metadata
FieldValue
Publication numberUS-10154074-B1
Application numberUS-201614987299-A
CountryUS
Kind codeB1
Filing dateJan 4, 2016
Priority dateNov 15, 2006
Publication dateDec 11, 2018
Grant dateDec 11, 2018

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Managing synchronized data requests is disclosed. Examples of synchronized data requests include viewer-induced synchronization, failure-induced synchronization, and player-induced synchronization. Information indicative of a potential occurrence of an amount of synchronized requests for audiovisual content that has a potential to have a detrimental impact on one or more components within a content delivery network is obtained. Subsequent to obtaining the information, one or more remediation actions are automatically caused to occur.

First claim

Opening claim text (preview).

What is claimed is: 1. A system, comprising: one or more hardware processors configured to: determine a load threshold beyond which a component in a content delivery environment will degrade; collect, from a set of remote clients, quality information associated with receipt of audiovisual content; detect, based at least in part on an evaluation of at least a portion of the quality information collected from the set of remote clients, a potential occurrence of an amount of synchronized requests for the audiovisual content that has a potential to cause the load threshold for the component to be exceeded; and in response to detecting, based at least in part on the evaluation of the at least portion of the quality information collected from the set of remote clients, the potential occurrence of the amount of synchronized requests for the audiovisual content that has the potential to cause the load threshold for the component to be exceeded, prevent the load threshold from being violated at least in part by performing one or more remediation actions, wherein performing the one or more remediation actions comprises modifying, for a remote client, at least one of a protocol with which the remote client obtains audiovisual content, a source from which the remote client obtains audiovisual content, a retry rate, and a bitrate at which the remote client obtains audiovisual content; and a physical memory coupled to the one or more hardware processors and configured to provide the one or more hardware processors with instructions. 2. The system of claim 1 wherein the detecting is based at least in part on load information associated with the component. 3. The system of claim 1 wherein the load threshold is determined based at least in part on capacity information associated with the component. 4. The system of claim 1 wherein the determined load threshold includes one of a maximum number of concurrent connections, an available amount of bandwidth, and a rate at which new connections can be accepted. 5. The system of claim 1 wherein the detecting includes analyzing at least one of real-time performance and load data to determine whether one or more performance metrics are indicative of degradation. 6. The system of claim 5 wherein the one or more performance metrics includes at least one of buffering quality, connection failures, connection interruptions, time taken to setup a connection, and time taken to start streaming. 7. The system of claim 1 wherein the one or more hardware processors are further configured to collect at least one of peak concurrent viewer information, join information, join failure information, connection interruption information, and bitrate switching information. 8. The system of claim 1 wherein the detecting is based at least in part on historical information and wherein the one or more remediation actions are performed based at least in part on a prediction using the historical information. 9. The system of claim 8 wherein the historical information is associated with at least one of client patterns and load patterns associated with the component. 10. The system of claim 1 wherein the detecting is based at least in part on information received from a server within a content delivery network. 11. The system of claim 10 wherein the server comprises an authentication server. 12. The system of claim 1 wherein the synchronized requests comprise at least one of viewer-induced requests, failure-induced requests, and player-induced requests. 13. The system of claim 1 wherein at least one of the remediation actions treat premium clients preferentially from non-premium clients. 14. The system of claim 1 wherein at least one of the remediation actions treat clients with longer engagements preferentially over clients with shorter engagements. 15. The system of claim 1 wherein at least one of the remediation actions treat clients having longer wait times preferentially over clients having shorter wait times. 16. The system of claim 1 wherein performing the one or more remediation actions comprises sending a command to a client. 17. The system of claim 1 wherein performing the one or more remediation actions comprises instructing the remote client to perform at least one of changing a protocol with which it obtains content, switching a source from which it obtains content, reducing a retry rate, and reducing a bitrate. 18. A method, comprising: determining a load threshold beyond which a component in a content delivery environment will degrade; collecting, from a set of remote clients, quality information associated with receipt of audiovisual content; detecting, based at least in part on an evaluation of at least a portion of the quality information collected from the set of remote clients, and using one or more hardware processors, a potential occurrence of an amount of synchronized requests for the audiovisual content that has a potential to cause the load threshold for the component to be exceeded; and in response to detecting, based at least in part on the evaluation of the at least portion of the quality information collected from the set of remote clients, the potential occurrence of the amount of synchronized requests for the audiovisual content that has the potential to cause the load threshold for the component to be exceeded, preventing the load threshold from being violated at least in part by performing one or more remediation actions, wherein performing the one or more remediation actions comprises modifying, for a remote client, at least one of a protocol with which the remote client obtains audiovisual content, a source from which the remote client obtains audiovisual content, a retry rate, and a bitrate at which the remote client obtains audiovisual content. 19. A computer program product embodied in a non-transitory computer readable storage medium and comprising computer instructions for: determining a load threshold beyond which a component in a content delivery environment will degrade; collecting, from a set of remote clients, quality information associated with receipt of audiovisual content; detecting, based at least in part on an evaluation of at least a portion of the quality information collected from the set of remote clients, a potential occurrence of an amount of synchronized requests for audiovisual content that has a potential to cause the load threshold for the component to be exceeded; and in response to detecting, based at least in part on the evaluation of the at least portion of the quality information collected from the set of remote clients, the potential occurrence of the amount of synchronized requests for the audiovisual content that has the potential to cause the load threshold for the component to be exceeded, preventing the load threshold from being violated at least in part by performing one or more remediation actions, wherein performing the one or more remediation actions comprises modifying, for a remote client, at least one of a protocol with which the remote client obtains audiovisual content, a source from which the remote client obtains audiovisual content, a retry rate, and a bitrate at which the remote client obtains audiovisual content. 20. The method of claim 18 wherein the detecting is based at least in part on load information associated with the component. 21. The method of claim 18 wherein the load threshold is determined based at least in part on capacity information associated with the component.

Assignees

Inventors

Classifications

  • Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually · CPC title

  • Electricity · mapped topic

  • Electricity · mapped topic

  • Processing captured monitoring data, e.g. for logfile generation · CPC title

  • based on parameters of servers, e.g. available memory or workload (monitoring of computer activity G06F11/30) · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10154074B1 cover?
Managing synchronized data requests is disclosed. Examples of synchronized data requests include viewer-induced synchronization, failure-induced synchronization, and player-induced synchronization. Information indicative of a potential occurrence of an amount of synchronized requests for audiovisual content that has a potential to have a detrimental impact on one or more components within a con…
Who is the assignee on this patent?
Conviva Inc
What technology area does this patent fall under?
Primary CPC classification H04L65/4084. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Dec 11 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (B1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).