Granted patent
Resilient content distribution network
- Number
- 12363395
- Published
- 2025-07-15
- Filed
- 2023-05-15
- Assignee
- Disney Enterprises, Inc.
- Inventors
- Strein; Michael J. et al.
- CPC
- H04N21/64322; H04N21/2187; H04N21/2665
- Verdict
- Set aside CDN infrastructure, plumbing
- Source
- Google Patents · FreePatentsOnline
Abstract
In one implementation, a content distribution network includes a first plurality of communication paths for Internet Protocol (IP) signals, a router providing a second plurality of communication paths for non-IP signals, and a plurality of signal sources and a plurality of signal destinations. Each signal source is linked to a respective one signal destination by a respective first communication path of the first plurality of communication paths. Each of one or more of the signal sources designated as a protected source is further linked to the respective one signal destination by a second communication path of the second plurality of communication paths. The content distribution network distributes content in one of a first mode in which the first communication path and the second communication path carry the same content contemporaneously, or a second mode in which only the second communication path carries that content.
Background
BACKGROUND (1) Resiliency in Internet Protocol (IP) content distribution networks is usually achieved through established network topologies that provide protection, such as a mesh network or the use of red/blue redundant networks. Additionally, to protect the Broadcast Controller (BC), the system that controls the flow management of the network (bandwidth management through spines, leaves, and ports), the BC is often placed in a virtual machine (VM) stack where the process can be seamlessly migrated in case of failure. However, one key failure point still lies in the fact that the BC communicates with the network via the Network Control (NC) module specific to the network switches used in the topology of the network. At present, NC modules cannot communicate with more than one BC at any time, rendering this service a single point of failure. If the connection between the NC module and the BC is somehow severed, the BC no longer has control of the network. This can happen not only in failure scenarios, but also in maintenance or upgrade scenarios where the BC needs service. (2) Severance of the connection between the NC module and the network BC typically severs the connections between all sources of communication signals served by the network and their intended destinations. Depending upon the purpose supported by a particular network, those sources and destinations may be of more or less critical importance. For example, in a media production scenario, only some fraction of