Patent Description:
Streaming of live media content may be more technically challenging than non-live content streaming. Because live content is rendered at approximately the same time as it is captured, live content cannot be buffered for prolonged periods of time. The lack of extensive buffering in live content streaming may cause live content streaming to require greater network bandwidth and/or smaller network latency than non-live content streaming.

Accordingly, the need exists for new methods, systems, and media for delivery of content that are capable of satisfying the bandwidth and latency requirements of live content streaming while still being suitable for streaming non-live content.

<CIT> describes a method for managing TCP anycast requests at content delivery network nodes.

<CIT> describes a method for managing over-the-top delivery of content through a plurality of content delivery networks.

The invention relates to a method, as further defined in claim <NUM>, a computer-readable medium, as further defined in claim <NUM>, and a system, as further defined in claim <NUM>, for distributing content from a pool of content delivery networks.

The above and other objects and advantages of the invention will be apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which like reference characters refer to like parts throughout, and in which:.

This invention generally relates to systems, methods, and media for controlling delivery of content. In some embodiments, mechanisms (which can be systems, methods, media, etc.) are provided for controlling the distribution of media content that is delivered to user equipment devices by a pool of one or more content distribution networks (CDNs). In some embodiments, a count of user equipment devices that are streaming content from a particular location can be monitored and, when the count exceeds a predetermined threshold, a new content distribution network can be added to the pool.

As referred to herein, the term "media content" or "content" should be understood to mean one or more electronically consumable media assets, such as television programs, pay-per-view programs, on-demand programs (e.g., as provided in video-on-demand (VOD) systems), Internet content (e.g., streaming content, downloadable content, Webcasts, etc.), movies, films, video clips, audio, audio books, and/or any other media or multimedia and/or combination of the same. As referred to herein, the term "multimedia" should be understood to mean media content that utilizes at least two different content forms described above, for example, text, audio, images, video, or interactivity content forms. Media content may be recorded, played, displayed or accessed by user equipment devices, but can also be part of a live performance. In some embodiments, media content can include over-the-top (OTT) content. Examples of OTT content providers include YOUTUBE, NETFLIX, and HULU, which provide audio and video via IP packets. Youtube is a trademark owned by Google Inc. , Netflix is a trademark owned by Netflix Inc. , and Hulu is a trademark owned by Hulu, LLC.

Media content can be provided from any suitable source in some embodiments. In some embodiments, media content can be electronically delivered to a user's location from a remote location. For example, media content, such as a Video-On-Demand movie, can be delivered to a user's home from a cable system server. As another example, media content, such as a television program, can be delivered to a user's home from a streaming media provider over the Internet.

<FIG> shows an example <NUM> of a guidance display that can be provided as part of an interactive media guidance application in accordance with some embodiments. As illustrated, a user may be presented with display <NUM> in response to the user selecting a selectable option provided in a displayed menu (e.g., an "Internet Videos" option, a "DivXTV" option, a "Program Listings" option, etc.), pressing a dedicated button (e.g., a GUIDE button) on a user input interface or device, and/or taking any other suitable action.

As illustrated in <FIG>, guidance display <NUM> may include lists of media identifiers, such as a first list of media identifiers <NUM> that lists categories of media content, and a second list of media identifiers <NUM> that lists particular pieces of media content within a selected category that are available for presentation.

Additional media guidance data, such as additional media identifiers, may be presented in response to a user selecting a navigational icon <NUM>.

Display <NUM> may also include a media queue region <NUM> that lists one or more pieces of media content selected and queued for playback, and a video region <NUM> in which pieces of media content can be presented.

In some embodiments, information relating to a piece of media content can also be presented to a user. For example, information <NUM> can include a name of a piece of media content, a time at which the media content is available (if applicable), a source (e.g., channel, Web address, etc.) from which the media content can be obtained, a parental rating for the piece of media content, a duration of the piece of media content, a description of the piece of media content, a review or a quality rating of the piece of media content, and/or any other suitable information.

In some embodiments, pieces of media content can be played in a full sized display screen in response to a user selecting "full screen" button <NUM>.

In some embodiments, a user may be able to set settings related to the interactive media guidance application by pressing a settings button, such as settings button <NUM> of <FIG>. The settings that can be set can include any suitable settings such as channel and program favorites, programming preferences that the guidance application can utilize to make programming recommendations, display preferences, language preferences, and/or any other suitable settings.

Turning to <FIG>, an example <NUM> of architecture of hardware that can be used in accordance with some embodiments is shown. As illustrated, architecture <NUM> can include a user television equipment device <NUM>, a user computer equipment device <NUM>, a wireless user communication device <NUM>, a communications network <NUM>, a media content source <NUM>, a media guidance data source <NUM>, a media encoder <NUM>, content distribution networks (CDNs) <NUM>, <NUM>, and <NUM>, and communication paths <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>, in some embodiments.

In some embodiments, user television equipment device <NUM>, user computer equipment device <NUM>, and wireless user communication device <NUM>, which can each be referred to herein as a "user equipment device," can be any suitable devices for presenting media content, presenting an interactive media guidance application for selecting content, and/or performing any other suitable functions as described herein.

User television equipment device <NUM> can be any suitable user television equipment device or devices in some embodiments. For example, in some embodiments, user television equipment device <NUM> can include any suitable television, smart TV, set-top box, integrated receiver decoder (IRD) for handling satellite television, digital storage device, digital media receiver (DMR), digital media adapter (DMA), streaming media device, DVD player, DVD recorder, connected DVD, local media server, BLU-RAY player, BLU-RAY recorder, any other suitable user television equipment, and/or any other suitable combination of the same.

User computer equipment <NUM> can be any suitable user computer equipment in some embodiments. For example, in some embodiments, user computer equipment <NUM> can include any suitable personal computer (PC), laptop computer, tablet computer, WebTV box, personal computer television (PC/TV), PC media server, PC media center, hand-held computer, stationary telephone, non-portable gaming machine, any other suitable user computer equipment, and/or any other suitable combination of the same.

Wireless user communication device <NUM> can be any suitable wireless user communication device or devices in some embodiments. For example, in some embodiments, wireless user communication device <NUM> can include any suitable personal digital assistant (PDA), mobile telephone, portable video player, portable music player, portable gaming machine, smart phone, any other suitable wireless device, and/or any suitable combination of the same.

In some embodiments, user equipment devices may be connectable to a communications network. For example, in some embodiments, user equipment devices may be Internet-enabled allowing them to access Internet media content.

In some embodiments, communications network <NUM> may be any one or more networks including the Internet, a mobile phone network, a mobile voice network, a mobile data network (e.g., a <NUM>, <NUM>, or LTE network), a cable network, a satellite network, a public switched telephone network, a local area network, a wide area network, a wireless network (e.g., WiFi, WiMax, etc.), any other suitable type of communications network, and/or any suitable combination of communications networks.

Media content source <NUM> may include one or more types of content distribution equipment for distributing any suitable media content, including television distribution facility equipment, cable system head-end equipment, satellite distribution facility equipment, programming source equipment (e.g., equipment of television broadcasters, such as NBC, ABC, HBO, etc.), intermediate distribution facility equipment, Internet provider equipment, on-demand media server equipment, live media distribution equipment, cameras, and/or any other suitable media content provider equipment, in some embodiments. NBC is a trademark owned by the National Broadcasting Company, Inc. , ABC is a trademark owned by the American Broadcasting Companies, Inc. , and HBO is a trademark owned by the Home Box Office, Inc.

Media content source <NUM> may be operated by the originator of content (e.g., a television broadcaster, a Webcast provider, etc.) or may be operated by a party other than the originator of content (e.g., an on-demand content provider, an Internet provider of content of broadcast programs for downloading, etc.), in some embodiments.

Media content source <NUM> may be operated by cable providers, satellite providers, on-demand providers, Internet providers, providers of over-the-top content, subscription providers, rental providers, and/or any other suitable provider(s) of content, in some embodiments.

Media content source <NUM> may include a remote media server used to store different types of content (including video content selected by a user), in a location remote from any of the user equipment devices, in some embodiments. Systems and methods for remote storage of content, and providing remotely stored content to user equipment are discussed in greater detail in connection with<CIT>, which is hereby incorporated by reference herein in its entirety.

Media guidance data source <NUM> may provide any suitable media guidance data, such as names of pieces of media content, times at which the media content is available (if applicable), sources (e.g., channels, Web addresses, etc.) from which the media content can be obtained, parental ratings for the pieces of media content, durations of the pieces of media content, descriptions of the pieces of media content, reviews or quality ratings of the pieces of media content, and/or any other suitable information, in some embodiments.

Media guidance data may be provided by media guidance data source <NUM> to the user equipment devices using any suitable approach, in some embodiments. In some embodiments, for example, an interactive media guidance application may be a stand-alone interactive television program guide that receives this media guidance data from media guidance data source <NUM> via a data feed (e.g., a continuous feed or trickle feed). In some embodiments, this media guidance data may be provided to the user equipment on a television channel sideband, using an in-band digital signal, using an out-of-band digital signal, or by any other suitable data transmission technique from media guidance data source <NUM>. In some embodiments, this media guidance data may be provided to user equipment on multiple analog or digital television channels from media guidance data source <NUM>. In some embodiments, media guidance data from media guidance data source <NUM> may be provided to users' equipment using a client-server approach, wherein media guidance data source <NUM> acts as a server.

In some embodiments, media guidance data source <NUM> may manage a pool of one or more content delivery networks (CDNs) that are used to deliver content to a plurality of user equipment devices. More particularly, in some embodiments, media guidance data source <NUM> may maintain a list of the CDNs from the pool and make changes to the list as CDNs are added or removed from the pool. When a CDN is added to the pool by media guidance source <NUM>, or periodically, media guidance data source <NUM> may provide the list to media encoder <NUM>.

In some embodiments, media guidance data source <NUM> may maintain records relating to the geographic distribution of user equipment devices that are currently streaming the content. For example, media guidance data source <NUM> may maintain a record that indicates a plurality of locations along with a count of user equipment devices located at each of the locations that are currently streaming the media content. In some embodiments, any one of the locations in the record may be indicated by: an identifier of a geographic location; an identifier of a network; an identifier of a network domain; an item of information that is found in a Domain Name Service (DNS) record; and/or any other suitable identifier.

Media encoder <NUM> may receive live content from media content source <NUM> and encode fragments of the content using a media encoding algorithm. Each fragment may be of any suitable duration, such as <NUM>-<NUM> seconds. In addition, each fragment may be encoded into one or more media files. In some embodiments, each fragment may be encoded into multiple media files that have different bit encoding rates.

Media encoder <NUM> may provide the media files corresponding to each fragment of the media content to each one of the pool of CDNs that are used to deliver the media content to user equipment devices. In some embodiments, media encoder <NUM> may identify the CDNs by obtaining the list maintained by media guidance data source <NUM>. In some embodiments, the media files may be uploaded to the CDNs in the pool over a File Transfer Protocol (FTP) connection and/or any other suitable mechanism. Additionally or alternatively, in some embodiments, media encoder <NUM> may obtain a current copy of the list of CDNs before uploading media files that correspond to a fragment of the content. Doing so may cause any changes made to the pool of CDNs by media guidance data source <NUM> to take place immediately.

After the upload of a set of media files that correspond to a fragment of the media content is completed, media encoder <NUM> may provide a set of addresses to media guidance data source <NUM>. Each address in the set may be the address of one of the media files at one of the CDN's in the pool. Each address in the set may be usable to retrieve a media file from the address' respective CDN. Addresses from the set may be later communicated by media guidance data source <NUM> to user equipment devices that seek to stream the media content. The user equipment devices may use these addresses to obtain the CDNs in the pool.

Content delivery network (CDN) <NUM> may distribute content to user equipment devices <NUM>, <NUM>, and/or <NUM>. CDN <NUM> may include: load balancing servers; request servers; cache servers; storage servers; communications switches; gateways; and/or any other suitable equipment. In some embodiments, CDN <NUM> may include a cloud-based storage that includes virtualized pools of storage hosted in an Internet data center, such as the Amazon S3 storage provided by Amazon Web Services of Herndon, Virginia, USA. In some embodiments, the cloud based storage may be used to "locally" cache media content for presentation on user equipment devices <NUM>, <NUM>, and/or <NUM>. Any suitable type and/or number of equipment may be used to implement CDN <NUM>, in some embodiments.

CDN <NUM> may use an adaptive bit rate (ABR) technique in which content is encoded into fragments (e.g., <NUM>-<NUM> seconds in length) that have different bit encoding rates. Having fragments of different bit encoding rates permits CDN <NUM> to dynamically select the proper bit-rate for user equipment devices depending on the networking resources available to any of the devices. In live content streaming, the fragments may be provided to client devices in real-time or near-real time as they are generated. As noted above, the fragments may be obtained from media encoder <NUM>.

CDN <NUM> and CDN <NUM> may have similar structures to CDN <NUM>. Each CDN may include a different plurality of computing devices (e.g., load balancers, cache servers, or storage servers). Additionally or alternatively, each CDN may be implemented by using a different data center. In some embodiments, CDNs <NUM>, <NUM>, and <NUM> may have different geographic locations from one another.

In some embodiments, each of CDN <NUM>, <NUM> and <NUM> may be operated by third-party operators that deliver content on behalf of the operators of media content source <NUM> and/or media guidance data source <NUM>. Each CDN may be associated with a different price that the operator of the CDN charges for the delivery of the media content. The price may be structured in terms of: dollars per amount of data served; dollars per amount of bandwidth that is made available to serve the content; dollars per amount of bandwidth that is consumed; and/or in accordance with any other suitable pricing scheme.

Although only one each of user equipment devices <NUM>, <NUM>, and/or <NUM>, sources <NUM> and <NUM>, media encoder <NUM>, and CDNs <NUM>, <NUM>, and <NUM> are illustrated in <FIG> in order to avoid over complicating the drawing, any suitable number of each of these components can be provided in some embodiments.

Each user may utilize more than one type of user equipment device in some embodiments. In some embodiments, any of user equipment devices <NUM>, <NUM>, and <NUM> can be combined, and any of media content source, media encoder <NUM>, and media guidance data source <NUM> may be combined.

Paths <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may separately or together include one or more communications paths, such as, a satellite path, a fiber-optic path, a cable path, a path that supports Internet communications (e.g., IPTV), free-space connections (e.g., for broadcast or other wireless signals), or any other suitable wired or wireless communications path or combination of such paths, in some embodiments. Path <NUM> is drawn with dotted lines to indicate that, in the example embodiment shown in <FIG>, it can be a wireless path (although this path may be a wired path, if desired), and paths <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are drawn as solid lines to indicate they can be wired paths (although these paths may be wireless paths, if desired). In some embodiments, communication to/from user equipment devices <NUM>, <NUM>, and <NUM>, sources <NUM> and <NUM>, media encoder <NUM>, and CDNs <NUM>, <NUM>, and <NUM> may be provided by one or more of communications paths <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>, respectively, but are shown as a single path in <FIG> to avoid overcomplicating the drawing.

Although direct communications paths are not drawn between user equipment devices <NUM>, <NUM>, and <NUM>, and between sources <NUM> and <NUM>, media encoder <NUM>, and CDNs <NUM>, <NUM>, and <NUM>, these components may communicate directly with each other via communication paths, such as those described above, as well via point-to-point communication paths, such as USB cables, IEEE <NUM> cables, wireless paths (e.g., Bluetooth, infrared, IEEE <NUM>. 11x, etc.), or other communication via wired or wireless paths, in some embodiments. BLUETOOTH is a certification mark owned by Bluetooth SIG, INC. The user equipment devices <NUM>, <NUM>, and <NUM>, sources <NUM> and <NUM>, media encoder <NUM>, and CDNs <NUM>, <NUM>, and <NUM> may also communicate with each other directly through an indirect path via communications network <NUM>, in some embodiments.

In some embodiments, sources <NUM> and <NUM> and media encoder <NUM> can be implemented in any suitable hardware. For example, sources <NUM> and <NUM> and media encoder <NUM> can be implemented in any of a general purpose device such as a computer or a special purpose device such as a client, a server, a mobile terminal (e.g., a mobile phone), etc. Any of these general or special purpose devices can include any suitable components such as a hardware processor (which can be a microprocessor, a digital signal processor, a controller, etc.). Furthermore, as noted above, any of media encoder <NUM> and sources <NUM> and <NUM> may be integrated as a single device (e.g., a single computer) and/or a single distributed system.

<FIG> shows an example of hardware that can be provided in an illustrative user equipment device <NUM>, such as user television equipment device <NUM>, user computer equipment device <NUM>, and/or wireless user communication device <NUM> of <FIG>, in accordance with some embodiments. As illustrated, device <NUM> can include control circuitry <NUM> (which can include processing circuitry <NUM> and storage <NUM>), a user input interface <NUM>, a display <NUM>, speakers <NUM>, and an input/output (hereinafter "I/O") interface <NUM>, in some embodiments.

Control circuitry <NUM> may include any suitable processing circuitry such as processing circuitry <NUM>. As referred to herein, processing circuitry <NUM> can be circuitry that includes one or more microprocessors, microcontrollers, digital signal processors, programmable logic devices, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), hardware processors, etc., and may include a multi-core processor (e.g., dual-core, quad-core, hexa-core, or any suitable number of cores) or a supercomputer, in some embodiments. In some embodiments, processing circuitry may be distributed across multiple separate processors or processing units, such as, for example, multiple of the same type of processing units (e.g., two Intel Core i7 processors) or multiple different processors (e.g., an Intel Core i5 processor and an Intel Core i7 processor).

Storage <NUM> can be any suitable digital storage mechanism in some embodiments. For example, storage <NUM> can include any device for storing electronic data, program instructions, computer software, firmware, register values, etc., such as random-access memory, read-only memory, hard drives, optical drives, digital video disc (DVD) recorders, compact disc (CD) recorders, BLU-RAY disc (BD) recorders, BLU-RAY 3D disc recorders, digital video recorders (DVR, sometimes called a personal video recorder, or PVR), solid state devices, quantum storage devices, gaming consoles, gaming media, or any other suitable fixed or removable storage devices, and/or any combination of the same. Storage <NUM> may be used to store media content, media guidance data, executable instructions (e.g., programs, software, scripts, etc.) for providing an interactive media guidance application, and for any other suitable functions, and/or any other suitable data or program code, in accordance with some embodiments. Nonvolatile memory may also be used (e.g., to launch a boot-up routine and other instructions), in some embodiments. Cloud-based storage may be used to supplement storage <NUM> or instead of storage <NUM> in some embodiments.

Control circuitry <NUM> may include video generating circuitry and tuning circuitry, such as one or more analog tuners, one or more MPEG-<NUM> decoders or other digital decoding circuitry, high-definition tuners, or any other suitable tuning or video circuits or combinations of such circuits, in some embodiments. Encoding circuitry (e.g., for converting over-the-air, analog, or digital signals to MPEG signals for storage) may also be provided, in some embodiments. Control circuitry <NUM> may also include scaler circuitry for upconverting and downconverting content into the preferred output format of the user equipment <NUM>, in some embodiments. Circuitry <NUM> may also include digital-to-analog converter circuitry and analog-to-digital converter circuitry for converting between digital and analog signals. The video generating circuitry may be used for presenting media content, in some embodiments. The tuning and encoding circuitry may be used by the user equipment device to receive and to display, to play, or to record content, in some embodiments. The tuning and encoding circuitry may also be used to receive guidance data, in some embodiments. The circuitry described herein, including for example, the tuning, video generating, encoding, decoding, encrypting, decrypting, scaler, and analog/digital circuitry, may be implemented using software running on one or more general purpose or special purpose hardware processors, in some embodiments. Multiple tuners may be provided to handle simultaneous tuning functions (e.g., watch and record functions, picture-in-picture (PIP) functions, multiple-tuner recording, etc.), in some embodiments. If storage <NUM> is provided as a separate device from user equipment <NUM>, the tuning and encoding circuitry (including multiple tuners) may be associated with storage <NUM>, in some embodiments.

A user may send instructions to control circuitry <NUM> using user input interface <NUM>, in some embodiments. User input interface <NUM> may be any suitable user interface, such as a remote control, mouse, trackball, keypad, keyboard, touch screen, touchpad, stylus input, joystick, voice recognition interface, or other user input interfaces, in some embodiments.

Display <NUM> may be provided as a stand-alone device or integrated with other elements of user equipment device <NUM>, in some embodiments. Display <NUM> may be one or more of a monitor, a television, a liquid crystal display (LCD) for a mobile device, or any other suitable equipment for displaying visual images, in some embodiments. In some embodiments, display <NUM> may be HDTV-capable. In some embodiments, display <NUM> may be a 3D display.

A video card or graphics card may generate the output to display <NUM>, in some embodiments. The video card may offer various functions such as accelerated rendering of 3D scenes and 2D graphics, MPEG-<NUM>/MPEG-<NUM> decoding, TV output, or the ability to connect multiple monitors, in some embodiments. The video card may be any processing circuitry described above in relation to control circuitry <NUM>, in some embodiments. The video card may be integrated with the control circuitry <NUM> or may be integrated with display <NUM>, in some embodiments.

Speakers <NUM> may be provided as integrated with other elements of user equipment device <NUM> or may be stand-alone units, in some embodiments. The audio component of media content displayed on display <NUM> may be played through speakers <NUM>, in some embodiments. In some embodiments, the audio may be distributed to a receiver (not shown), which processes and outputs the audio via speakers <NUM>.

I/O interface <NUM> can be any suitable I/O interface <NUM> in some embodiments. For example, in some embodiments, I/O interface <NUM> can be any suitable interface for coupling control circuitry <NUM> (and specifically processing circuitry <NUM>) to one or more communications paths (e.g., paths <NUM>, <NUM>, and <NUM> described in <FIG>). More particularly, for example, I/O interface <NUM> can include a cable modem, an integrated services digital network (ISDN) modem, a digital subscriber line (DSL) modem, a telephone modem, an Ethernet card, a fiber-optic modem, a wireless modem, and/or any other suitable communications circuitry. In some embodiments, the I/O interface can be used to provide content and data from an external location to device <NUM>. For example, in some embodiments, I/O interface <NUM> can be used to provide media content (e.g., broadcast programming, on-demand programming, Internet content, content available over a local area network (LAN) or wide area network (WAN), and/or any other suitable content), media guidance data, subtitles, time codes, and/or any other suitable information or data to control circuitry <NUM> of device <NUM>. In some embodiments, I/O interface <NUM> can also be used to send and receive commands, requests, and other suitable data from and to, respectively, control circuitry <NUM>. Any suitable number of I/O interfaces <NUM> can be provided, even though only one is shown in <FIG> to avoid overcomplicating the drawing.

The processes for playing back media content, the interactive media guidance application and/or any other suitable functions as described herein may be implemented as stand-alone applications on user equipment devices in some embodiments. For example, the processes for playing back media content and/or the interactive media guidance application may be implemented as software or a set of executable instructions which may be stored in storage <NUM>, and executed by control circuitry <NUM> of a user equipment device <NUM>.

In some embodiments, the processes for playing back media content, the interactive media guidance application, and/or any other suitable functions as described herein may be implemented as client-server applications. In such client-server applications, a client application may reside on a user equipment device, and a server application may reside on a remote server, such as source <NUM> or one of CDNs <NUM>, <NUM>, and <NUM>. For example, the processes for playing back media content may be implemented partially as a client application on control circuitry <NUM> of user equipment device <NUM> and partially as a server application on media content source <NUM> or one of CDNs <NUM>, <NUM>, and <NUM>. As another example, an interactive media guidance application may be implemented partially as a client application on control circuitry <NUM> of user equipment device <NUM> and partially on a remote server (e.g., media guidance data source <NUM> or one of CDNs <NUM>, <NUM>, and <NUM>) as a server application running on control circuitry of the remote server.

<FIG> shows an example of hardware that can be provided in an illustrative server <NUM>. Server <NUM> may be part of a media guidance data source, such as media guidance data source <NUM>, and it may implement a media content delivery process, such as at least portions of content delivery process <NUM>, which is shown in <FIG>. As illustrated, server <NUM> can include control circuitry <NUM> (which can include processing circuitry <NUM> and storage <NUM>) and a network interface <NUM>.

Storage <NUM> can be any suitable digital storage mechanism in some embodiments. For example, storage <NUM> can include any device for storing electronic data, program instructions, computer software, firmware, register values, etc., such as random-access memory, read-only memory, hard drives, optical drives, digital video disc (DVD) recorders, compact disc (CD) recorders, BLU-RAY disc (BD) recorders, BLU-RAY 3D disc recorders, digital video recorders (DVR, sometimes called a personal video recorder, or PVR), solid state devices, quantum storage devices, gaming consoles, gaming media, or any other suitable fixed or removable storage devices, and/or any combination of the same. Storage <NUM> may be used to store media content, media guidance data, executable instructions (e.g., programs, software, scripts, etc.) for providing an interactive media guidance application, and for any other suitable functions, and/or any other suitable data or program code, in accordance with some embodiments. Nonvolatile memory may also be used (e.g., to launch a boot-up routine and other instructions). Cloud-based storage may be used to supplement storage <NUM> or instead of storage <NUM> in some embodiments.

Control circuitry <NUM> may include encoding circuitry for encoding media content (e.g., video or audio). Control circuitry <NUM> may also include adaptive bit streaming circuitry for encoding the media content into multiple bit rates and performing switches between the streams during normal playback based upon the streaming conditions. Control circuitry <NUM> may also include streaming circuitry for transmitting the different bit streams via network interface <NUM>.

For example, in some embodiments, interface <NUM> can be any suitable interface for coupling control circuitry <NUM> (and specifically processing circuitry <NUM>) to one or more communications networks. More particularly, for example, interface <NUM> can include a cable modem, an integrated services digital network (ISDN) modem, a digital subscriber line (DSL) modem, a telephone modem, an Ethernet card, a fiber-optic modem, a wireless modem, and/or any other suitable communications circuitry. In some embodiments, the I/O interface can be used by server <NUM> to stream content to a client device, such as device <NUM>. More particularly, in some embodiments, interface <NUM> can be used to provide media content (e.g., broadcast programming, on-demand programming, Internet content, content available over a local area network (LAN) or wide area network (WAN), and/or any other suitable content). In some embodiments, interface <NUM> can also be used to receive commands, requests, from a client device. Such requests may be for blocks (e.g., chunks) of media content that is being streamed.

<FIG> and <FIG> depict a flowchart of an example of a process <NUM> for distributing media content in accordance with some embodiments of the disclosed subject matter.

At <NUM>, one or more first records may be stored in memory or any other suitable location. The one or more first records may include identifiers for a pool of one or more content delivery networks (CDNs) that can be used to stream media content to a plurality of user equipment devices. Any suitable type of identifiers may be used in the first record(s) in some embodiments. For example, in some embodiments, an identifier of a CDN in the pool may include an identifier for a component of the CDN, such as a gateway or a load balancer. Step <NUM> may be performed by: a media guidance data source, such as media guidance data source <NUM>; processing circuitry of the media guidance data source; and/or any other suitable device or processing circuitry thereof.

At <NUM>, one or more second records may be stored in memory or any other suitable location. The second record(s) may include information relating to the geographic distribution of user equipment devices that are currently streaming media content from CDNs in the pool. In some embodiments, the record(s) may identify a set of one or more locations. In some embodiments, for each location, the record may identify a count of user equipment devices that are located at that location and are currently streaming the media content. The count may be a string, a number, or an alphanumerical string that is based on (or indicative of) a number of user equipment devices that are streaming the media content.

In some embodiments, two or more user equipment devices may be considered to be at the same location when the user equipment devices are located in the same region as each other (e.g., in the same district, in the same service area, in the same telephone service area, in the same city, or in the same state, etc.). Any suitable definition of location may be used, in some embodiments.

Additionally or alternatively, in some embodiments, two or more user equipment devices may be considered to be at the same location when the user equipment devices are part of the same network domain (or the same network; or the same portion of a network) as each other. Additionally or alternatively, in some embodiments, two user equipment devices may be considered to be at the same location when one of the user equipment devices is part of a network domain (or a network; or a portion of a network) that is associated with a network domain (or a network; or a portion of a network) the other user equipment device is part of. Thus, in some embodiments, whether two user equipment devices are located at the same location may, at least in part, depend on the topology of network(s) the two user equipment devices are part of.

Additionally or alternatively, in some embodiments, a two user equipment devices may be considered to be at the same location when a first record corresponding to one of the user equipment devices contains an item of information (e.g., a number, a word, or an alphanumerical string) that satisfies a similarity criterion with respect to another item of information that is part of a second record that corresponds to the other user equipment device. Any suitable type of records may be used, in some embodiments. For example, the first record and the second record may be Domain Name Service (DNS) records, records maintained by Internet service providers, records maintained by network administrators, records maintained by content distributors, and/or any other suitable records.

To determine whether two or more user equipment devices are at the same location, any suitable similarity criterion may be used in some embodiments. For example, in some embodiments, the similarity criterion may be one that is satisfied when the two items of information are identical. As another example, in some embodiments, the similarity criterion may be one that is satisfied when the first item of information and the second item of information are within a predetermined distance from one another in the space of items of information from their type.

Step <NUM> may be performed by: a media guidance data source, such as media guidance data source <NUM>; processing circuitry of the media guidance source and/or any other suitable device or processing circuitry thereof.

At <NUM>, a fragment of the media content may be received. The fragment may be received in any suitable manner, in some embodiments. The fragment may include any suitable media content, such as media content data that is sufficient to render (e.g., in sound and/or in image) at least a portion of the media content (e.g., <NUM>-<NUM> seconds of the media content).

At <NUM>, the fragment of the media content may be encoded to generate one or more media files that encode the fragment. The fragment may be encoded in any suitable manner, in some embodiments. For example, in some embodiments, one or more of the files may have a different encoding bit rate.

At <NUM>, one or more CDNs in the pool may be identified. The one or more of the CDNs may be identified in any suitable manner, in some embodiments. For example, in some embodiments, a first record may be obtained and used to identify the CDNs.

At <NUM>, at least some of the generated media files may be provided to the identified CDNs. The media files may be provided in any suitable manner, in some embodiments. For example, in some embodiments, at least some of the generated media files may be uploaded via a File Transfer Protocol (FTP) connection to each of the CDNs. Upon uploading any one of the media files to a given CDN, the address (e.g., Uniform Resource Locator (URL)) of that file at the CDN may be recorded. In some embodiments, the addresses (of some or all) of the media files at different CDNs may be recorded. These addresses, as is further discussed below, may be usable by user equipment devices to obtain the media files when the content is being streamed.

At <NUM>, the addresses of the media files may be provided to media guidance data source, such as media guidance data source <NUM>. The addresses may be provided in any suitable manner, in some embodiments.

Each of steps <NUM>-<NUM> may be performed by: an encoder, such as media encoder <NUM>; and/or any other suitable device.

At <NUM>, a request may be received from a user equipment device to initiate a streaming of the content to the user equipment device. The request may be received in any suitable manner in some embodiments. For example, in some embodiments, the request may be transmitted over a communications network, such as network <NUM>. In some embodiments, the request may be received at a media guidance data source, such as media guidance data source <NUM>.

At <NUM>, the location of the user equipment device may be determined. The device may be determined in any suitable manner, in some embodiments. For example, in some embodiments, determining the location, in some embodiments, may include obtaining an identifier that is indicative of the user equipment device's physical location, such as: an identifier of a network domain (or portion thereof) the device is part of; an identifier of a network (or portion thereof) the device is part of; coordinates of the device (e.g., by using a Global Positioning System (GPS) capability that is built into the device); and/or any other suitable identifier. Additionally or alternatively, in some embodiments, the location of the user equipment device may be determined by using an instance of the nslookup utility. Additionally or alternatively, in some embodiments, determining the location of the user equipment device may include retrieving a record (e.g., a DNS record, a record maintained by an Internet Service provider, and/or any other suitable type of record) that corresponds to the user equipment device and obtaining an item of information that is part of the retrieved record that is indicative of the location of the user equipment device. Any suitable item of information may be used in some embodiments. For example, in some embodiments, the item of information may include: an item of information that is indicative of a network domain (or portion thereof); an item of information that is indicative of a network (or portion thereof); an item of information that is indicative of a city; an item of information that is indicative of a physical address; an item of information that is indicative of a network address; and/or any other suitable item.

At <NUM>, a count of user equipment devices that are located at the same location as the user equipment device and are streaming the media content may be determined. This count may be determined in any suitable manner, in some embodiments. For example, in some embodiments, one of the first records may be obtained and used to identify the count. Additionally or alternatively, in some embodiments, the count may be determined based on responses to queries transmitted over a communications network to one or more devices/systems that are responsible for routing user equipment devices to CDNs (e.g., in the same manner as the device/system executing steps <NUM>-<NUM>) and receiving respective counts of user equipment devices at the location that are currently streaming the media content and have been assisted in streaming the media content by each of the CDNs.

At <NUM>, a determination may be made whether a predetermined condition is satisfied. Any suitable predetermined condition may be used, in some embodiments. For example, in some embodiments, the predetermined condition may be based on the count. For example, the predetermined condition may be one that is satisfied when the count meets (e.g., exceeds, equals, or falls below) a predetermined threshold.

Additionally or alternatively, in some embodiments, the predetermined condition may be based on a value of a quality of service metric of a communications path connecting a CDN that is used to provide media content with a user equipment device that is streaming the content. Any suitable quality of service metric may be used. For example, the quality of service metric may be latency, bandwidth, jitter, and/or any other suitable quality of service metric. Thus, in some embodiments, the predetermined criterion may be a criterion that is satisfied when the quality of service metric meets a predetermined threshold.

Additionally or alternatively, in some embodiments, the predetermined condition may be based on a plurality of quality of service metric valules, wherein each quality of service value is for a different one of a plurality of communications paths. Each communications path may be one that connects a CDN that is used to provide the media content with user equipment. Each communication path may be one that is leading to different one of a plurality of user equipment devices that are streaming the content. In some embodiments, the predetermined condition may be based on an average, median, and/or any other suitable statistical characteristic of the plurality of quality of service metric values.

When the predetermined condition is determined to be satisfied, the execution of process <NUM> proceeds to step <NUM>. Otherwise, when the predetermined condition is found to not be satisfied, the execution of process <NUM> proceeds to step <NUM>.

At <NUM>, an additional CDN that is available to stream the media content may be identified. This identification may be performed in any suitable manner, and any suitable CDN may be identified, in some embodiments. The additional CDN, in some embodiments, may include a plurality of computing devices (e.g., servers, load balancers, cache servers, and/or any suitable type of computing device). In some embodiments, the additional CDN may be implemented using a data center that is different from the data centers used to implement the CDNs in the pool. For example, the data center of the additional CDN may be at a different geographic location than the data centers of the other CDNs in the pool.

In some embodiments, the additional CDN may be selected from a plurality of available CDNs. Additionally or alternatively, the CDN may be selected based on a predetermined criterion. Any suitable criterion may be used, in some embodiments. For example, in some embodiments, the CDN may be selected based on a geographic location corresponding to the CDN (e.g., a geographic location where a data center that is used to implement the CDN is located).

As another example, in some embodiments, the CDN may be selected from the plurality of available CDNs based on a QoS metric associated with the CDN, such as latency or bandwidth. For example, in some embodiments, the QoS metric associated with the CDN may indicate one of the latency, bandwidth, or throughput for one or more communications paths between a component of the CDN (e.g., a load balancer) and a device located at a predetermined location, such as the location determined at step <NUM> and/or any other suitable location.

As yet another example, in some embodiments, the CDN may be selected from the plurality of available CDNs based on a price associated with the CDN (e.g., a price for a unit of bandwidth that is made available for serving the media content or price for a unit of bandwidth that is consumed by streaming the media content, a price for a unit of data served, etc.). For example, the CDN may be selected based on having the lowest associated price.

As yet another example, in some embodiments, the CDN may be selected from the plurality of available CDNs based on distance from CDNs in the pool. For example, the CDN may be selected based on being situated the furthest, of all CDNs in the plurality, from a given CDN in the pool. The distance between different CDNs may be based on the physical distance, the logical distance, and/or the network distance between the locations of data centers that are used to implement the CDNs.

In some embodiments, the additional CDN may be implemented using a different data center than data centers used to implement CDNs in the pool. In some embodiments, the additional CDN may include a plurality of computing devices (e.g., load balancers, cache servers, storage servers, etc.).

At <NUM>, the CDN identified at step <NUM> may be added to the pool of CDNs that are responsible for streaming the media content. The CDN may be added in any suitable manner, in some embodiments. For example, in some embodiments, adding the CDN to the pool may include adding an identifier for the CDN to one or more of the first records. Additionally or alternatively, in some embodiments, adding the identified CDN to the pool may include configuring an encoder, such as media encoder <NUM>, to start uploading media files corresponding to fragments of the media content to the CDN. Additionally or alternatively, configuring the encoder may include providing (e.g., transmitting over a communications network) an identifier for the CDN to the encoder.

At <NUM>, the user equipment device may be provided with information that may be usable by the user equipment device to begin streaming media content. Any suitable information may be provided, and this information may be provided in any suitable manner, in some embodiments. For example, the information may include an address (e.g., a URL) that is usable to retrieve a media file from a CDN from the pool. The media file may be one that corresponds to a fragment of a media stream and is uploaded to the CDN by an encoder, such media encoder <NUM>, in some embodiments. In some embodiments, in instances where the count is determined to meet the threshold at <NUM>, the address may point to an instance of the media file that is stored at the CDN identified at step <NUM>. The user equipment device may then use the streaming information to stream the media content from of the CDNs in the pool.

At <NUM>, the record indicating the geographic distribution of the user equipment devices may be updated. This record may be updated in any suitable manner, in some embodiments. For example, in some embodiments, the count determined at step <NUM> may be incremented by one (or otherwise changed) in order to reflect that the user equipment device has begun streaming the media content based on the streaming information provided at step <NUM>, in some embodiments.

Any of steps <NUM>-<NUM> may be performed by: a media guidance data source, such as media guidance data source <NUM>; processing circuitry of the media guidance data source; and/or any other suitable device or processing circuitry thereof.

In some embodiments, a functional separation may be maintained between. As noted above, steps <NUM>-<NUM> may be performed by one or more media encoders, whereas steps <NUM>-<NUM> may be performed by a media guidance data source. Thus in some embodiments, failsafe mechanism (for adding CDN's to the pools e.g., the determination whether the predetermined condition is satisfied) may be implemented at a device that is separate from any media encoders.

Although in the above example a CDN is added to a pool CDNs that are responsible for streaming the media content, in other examples, when the count meets the threshold, a server may be added to a pool of servers that are used to stream the content, in some embodiments. For example, once added, that server may begin to receive streaming resources associated with the pool as discussed with respect to step <NUM>. The address of that server may be provided to user equipment devices that seek to begin streaming the media content and the server may begin providing the media content to any devices that establish a connection with the server, in some embodiments.

It should be noted, however, that in some embodiments, adding a server to a pool of servers may be different from adding a CDN to a pool. In some embodiments, adding a new CDN to a pool of CDN may involve utilizing another data center to distribute the media content along with underlying data center infrastructure, such as load balancers and caching servers. The data center may be at a different location than other data centers in the pool and, thus, adding the CDN to the pool may provide user equipment devices located at the first location with additional network paths to stream the media content over. This in turn may prevent congestion of network paths spanning between the first location and other CDNs in the pool.

The above steps of the flow diagrams of <FIG> may be executed or performed in any order or sequence not limited to the order and sequence shown and described in the figures. Some of the above steps of the flow diagrams of <FIG> may be executed or performed substantially simultaneously where appropriate or in parallel to reduce latency and processing times. Some of the above steps of the flow diagrams of <FIG> may be omitted. Although the above embodiments of the invention are described in reference to live content streaming, the techniques disclosed herein may be used in any type of data downloading, including non-live streaming of media content.

In some embodiments, any suitable computer readable media can be used for storing instructions for performing the mechanisms and/or processes described herein. For example, in some embodiments, computer readable media can be transitory or non-transitory. For example, non-transitory computer readable media can include media such as magnetic media (such as hard disks, floppy disks, etc.), optical media (such as compact discs, digital video discs, Blu-ray discs, etc.), semiconductor media (such as flash memory, electrically programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), etc.), any suitable media that is not fleeting or devoid of any semblance of permanence during transmission, and/or any suitable tangible media. As another example, transitory computer readable media can include signals on networks, in wires, conductors, optical fibers, circuits, any suitable media that is fleeting and devoid of any semblance of permanence during transmission, and/or any suitable intangible media.

Claim 1:
A method (<NUM>) for delivery of content, the method comprising:
receiving (<NUM>) a request to stream the content, the request being received from a user equipment device, where a pool of one or more content delivery networks are responsible for streaming the content;
determining (<NUM>) a first location of the user equipment device;
determining (<NUM>) a count of user equipment devices that are located at the first location and are currently streaming the content from the pool of content delivery networks;
determining (<NUM>) whether the count meets a threshold;
responsive to determining that the count meets the threshold, adding (<NUM>) a new content delivery network to the pool of content delivery networks that are responsible for streaming the content by configuring and providing an encoder (<NUM>) with an identifier of the new content delivery network to encode the content to produce encoded content and disseminate the encoded content to the new content delivery network; and
providing (<NUM>) information to the user equipment device, wherein the user equipment device uses the provided information to begin streaming the encoded content from the new content delivery network.