Systems for monitoring and managing integrated receiver decoders

Abstract

An integrated network receiver includes a first general resource identifier (GRI) for a first channel, and an input adapted to receive first input video content from the Internet based on the first GRI. The integrated network receiver provides the first input video content of the first channel to headends connected to multiple client devices via a transmission network. The integrated network receiver updates the first GRI based on data obtained from a video address server.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 070,105, filed on August 25, 2020. Background Technology

[0003] The subject of this application relates to the monitoring and / or management of commercially integrated receiver decoder networks.

[0004] Cable television (CATV) services deliver content from a central delivery unit, often referred to as the “headend,” to a large number of customers (e.g., subscribers). This central delivery unit distributes content channels to its customers via an access network (including associated components such as nodes, amplifiers, and branch points) that comprises a hybrid fiber-coaxial (HFC) cable plant. However, modern cable television (CATV) service networks not only provide customers with media content such as television and music channels, but also a wide range of digital communication services such as internet services, video-on-demand, telephone services such as VoIP, home automation / security, and more. These digital communication services, in turn, require communication not only downstream from the headend through the HFC (which typically forms a branch network) to the customer, but also upstream from the customer to the headend, typically via the HFC network.

[0005] To this end, CATV headends have historically included a separate cable modem termination system (CMTS) for providing high speed data services, such as cable internet, voice over internet protocol, etc., to cable television customers, as well as a video headend system for providing video services, such as broadcast video and video on demand (VOD). Typically, the CMTS will include an Ethernet interface (or other more traditional high speed data interface) as well as a radio frequency (RF) interface, such that traffic from the internet can be routed (or bridged) through the CMTS over the Ethernet interface, and then onto the RF interface that connects to the cable television company's hybrid fiber coaxial (HFC) system. Downstream traffic is delivered from the CMTS to cable modems and / or set top boxes in customers' homes, while upstream traffic is delivered from cable modems and / or set top boxes in customers' homes to the CMTS. Similarly, the video headend system provides video to set top boxes, televisions with video decryption cards, or other devices capable of demodulating and decrypting incoming encrypted video services. Many modern CATV systems have combined the functionality of a CMTS with a video delivery system (e.g., EdgeQAM - quadrature amplitude modulation) in a single platform, often referred to as an integrated CMTS (e.g., integrated converged cable access platform (CCAP)) - video services are prepared and provided to the I-CCAP, which then modulates the video QAMs onto the appropriate frequencies. Still other modern CATV systems, often referred to as distributed CMTS (e.g., distributed converged cable access platform), can include a remote PHY (or R-PHY), which relocates the physical layer (PHY) of the traditional integrated CCAP to the fiber nodes of the network (R-MAC PHY relocates both the MAC and the PHY to the nodes of the network). Thus, while the core in the CCAP performs the higher layer processing, the R-PHY devices in the remote nodes convert downstream data sent from the core from digital to analog for transmission on radio frequency to cable modems and / or set top boxes, and convert upstream radio frequency data sent from cable modems and / or set top boxes from analog to digital format for transmission optically to the core. BRIEF DESCRIPTION OF DRAWINGS

[0006] For a better understanding of the present application, and to show how it can be put into effect, reference will now be made, by way of example, to the accompanying drawings in which:

[0007] Figure 1 An integrated cable modem termination system is shown.

[0008] Figure 2 A distributed cable modem termination system is shown.

[0009] Figure 3 A headend with an integrated satellite receiver is shown.

[0010] Figure 4 The headend, along with the integrated network receiver and video address server, are shown.

[0011] Figure 5 The video address server is shown. Detailed Implementation

[0012] refer to Figure 1 The integrated CMTS (e.g., an integrated converged wired access platform (CCAP)) 100 may include data 110, typically transmitted and received via the Internet (or other networks) in packetized data format. The integrated CMTS 100 may also receive downstream video 120, typically in packetized data format, from an operator's video aggregation system. For example, broadcast video is typically obtained from a satellite delivery system and pre-processed for delivery to subscribers via CCAP or a video headend system. The integrated CMTS 100 receives and processes the received data 110 and downstream video 120. The CMTS 130 may transmit downstream data 140 and downstream video 150 to a customer's cable modem and / or set-top box 160 via an RF distribution network, which may include other devices such as amplifiers and splitters. The CMTS 130 may receive upstream data 170 from a customer's cable modem and / or set-top box 160 via a network, which may include other devices such as amplifiers and splitters. The CMTS 130 may include multiple devices to achieve its required capabilities.

[0013] refer to Figure 2Due to increasing bandwidth demands, limited facility space for integrating CMTS, and power consumption considerations, it is desirable to include a Distributed Cable Modem Terminal System (D-CMTS) 200 (e.g., a Distributed Converged Cable Access Platform (CCAP)). Generally, CMTS focuses on data services, while CCAP also includes broadcast video services. D-CMTS 200 uses network packetized data to distribute some functionality of I-CMTS 100 downstream to remote locations such as fiber optic nodes. An exemplary D-CMTS 200 may include a remote PHY architecture, where the remote PHY (R-PHY) is preferably an optical node device located at the junction of fiber optic and coaxial cables. Generally, the R-PHY often comprises a PHY layer that is part of the system. D-CMTS 200 may include a D-CMTS 230 (e.g., a core) that includes data 210 typically transmitted and received via the Internet (or other networks) in packetized data format. D-CMTS 200 may also receive downstream video 220, typically in packetized data format, from a carrier video aggregation system. The D-CMTS 230 receives and processes received data 210 and downstream video 220. The remote fiber optic node 280 preferably includes a remote PHY device 290. The remote PHY device 290 can transmit downstream data 240 and downstream video 250 to a customer's cable modem and / or set-top box 260 via a network, which may include other devices such as amplifiers and splitters. The remote PHY device 290 can receive upstream data 270 from a customer's cable modem and / or set-top box 260 via a network, which may include other devices such as amplifiers and splitters. The remote PHY device 290 may include multiple devices to achieve its required capabilities. The remote PHY device 290 primarily includes PHY-related circuitry (e.g., a downstream QAM modulator, an upstream QAM demodulator), and pseudowire logic connected to the D-CMTS 230 using network packetized data. The remote PHY device 290 and the D-CMTS 230 may include data and / or video interconnects, such as downstream data, downstream video, and upstream data 295. It should be noted that in some embodiments, video traffic can reach the remote physical device directly, thereby bypassing the D-CMTS 230. In some cases, remote PHY and / or remote MAC PHY functionality can be provided at the headend.

[0014] For example, the remote PHY device 290 can convert downstream DOCSIS (i.e., Cable Data Service Interface Specification) data (e.g., DOCSIS 1.0, 1.1, 2.0, 3.0, 3.1, and 4.0, each of which is incorporated herein by reference in its entirety), video data, and out-of-band signals received from the D-CMTS 230 into analog data for transmission over an RF or analog optical system. For example, the remote PHY device 290 can convert upstream DOCSIS and out-of-band signals received from an analog medium such as an RF or linear optical system into digital data for transmission to the D-CMTS 230. It can be seen that, depending on the specific configuration, R-PHY can move all or part of the DOCSIS MAC and / or PHY layer down to the fiber optic node.

[0015] In another embodiment, the system does not need to include a CMTS, whether an integrated CMTS or a distributed CMTS, but any other type of system can be used for the headend and / or any other type of network for content distribution. For example, distribution at the headend can be performed by a set of servers providing data connectivity to clients over any type of network, including fiber optic networks, wireless networks, cellular networks, or other networks.

[0016] refer to Figure 3 Whether it's an integrated system, a distributed system, or any other type of system, the headend 300 typically includes an associated integrated satellite receiver 310 for high-density transcoding (or transmission) of video content from one or more satellites. The integrated satellite receiver 310 may include one or more active RF tuners with retuning capabilities to receive signals from satellites, and one or more network ports (e.g., Ethernet) providing network connectivity to the headend device. For example, the integrated satellite receiver 310 can transcode video content from one or more received high-definition video signals and / or one or more received standard-definition video signals from an input format to an output format.

[0017] To install and configure the integrated satellite receiver 310, it is typically mounted in a rack, powered on, and its RF satellite input ports are configured to receive signals from one or more satellites 320. For example, the ports may interconnect to Galaxy 15C-Band horizontal signals and / or Galaxy 14C-Band vertical signals and / or Galaxy 14C-Band horizontal signals. The integrated satellite receiver 310 may include Ethernet and / or ASI (Asynchronous Serial Interface) outputs connected to the headend 300. A set of frequency and modulation parameters are input to the integrated satellite receiver 310 to obtain signal lock for the satellite signals. For example, this may include input port identification, frequency, transponder number, modulation mode, and / or symbol rate. Typically, the integrated satellite receiver 310 is licensed based on its unit address from a content provider, enabling it to receive and correctly decode video signals provided from the content provider's satellite(s) 320. For example, content providers may include ABC, CBS, CW, ION, Dish, NBC, PBS, A&E, ACCN, ESPN, AHC, AMC, BBCAMERICA, BTN, Bloomberg TELEVISION, CNN, HBO, and / or BRAVO. The content, then received and transcoded (or transmitted) by the integrated satellite receiver 310, is provided to the headend 300, which in turn distributes the content to local and regional subscribers.

[0018] In most cases, once the integrated satellite receiver 310 is configured using its small and error-prone interface, the frequency and modulation parameters are unlikely to change over a considerable period (e.g., months to years). Therefore, the need to reconfigure the integrated satellite receiver 310 after its initial configuration is limited. While limited to satellite communications, the integrated satellite receiver 310 is unsuitable for internet-based video content because programming such internet-based Uniform Resource Locators and / or Uniform Resource Identifiers (collectively referred to herein as Uniform Resource Identifiers "URIs") into the integrated satellite receiver 310 is problematic, and these URIs tend to change on a more dynamic basis, making it problematic to modify the settings of the integrated satellite receiver 310 to maintain the current URI being used for each specific video stream. For example, content providers may choose to frequently change their content distribution networks depending on various factors, including network performance and cost. Moreover, in the case of multiple integrated satellite receivers 310, each integrated satellite receiver will need to modify its settings to maintain the current URI being used by that particular integrated satellite receiver for each associated specific video stream.

[0019] refer to Figure 4Whether integrated or distributed, the headend 400 of a cable television system includes an associated integrated network receiver 410 for high-density transcoding (or transmission) of video content from packet-based Internet sources (e.g., video content servers). The integrated network receiver 410 may include one or more network ports for receiving Internet-based signals, and one or more network ports (e.g., Ethernet and ASI) providing network connectivity to other devices at the headend. For example, the integrated network receiver 410 may transcode video content from one or more received high-definition video signals and / or one or more received standard-definition video signals from an input format to an output format (or another identical format), or otherwise provide transmission from an input format to an output format (or another identical format).

[0020] For installation and configuration of the integrated network receiver 410, the receiver 410 is typically rack-mounted, powered, and its network input is connected to receive signals from one or more Internet video network sources 440 (e.g., video servers). For example, the network input can receive Internet-based data from various network servers (e.g., cloud-based network servers). Some cloud-based networks may include Amazon Web Services, Google Cloud Platform, Microsoft Azure, IBM Cloud, Oracle Cloud, VMware Cloud, Dell Technologies Cloud, and / or private servers / clouds. The integrated network receiver 410 preferably queries the video address server 450 via a network connection to obtain one or more Internet Protocol (IP)-based URI addresses for serving the corresponding video source to the headend 400. Preferably, the video address server 450 provides a corresponding URI for the corresponding video content of a channel. For example, the URI may have the following format: URI = scheme:[ / / authorization] path[?query][#fragment]. Typically, authorization of the integrated network receiver 410 is obtained based on the unit address from the content provider, enabling it to receive and correctly decode video signals served over the Internet from the content provider. For example, content providers may include ABC, CBS, CW, ION, Dish, NBC, PBS, A&E, ACCN, ESPN, AHC, AMC, BBCAMERICA, BTN, Bloomberg TELEVISION, CNN, HBO, and / or BRAVO. The content, then received and transcoded (or transmitted) by the integrated network receiver 410, is provided to the headend 400, which in turn distributes the content to local and regional subscribers.

[0021] refer to Figure 5The video address server 450 includes a channel table or other data structure 500, which includes a list of one or more channels 510. Each channel 510 may include an associated URI 1 520, which is the primary network address of the video content. Each channel 510 may include an associated URI 2 530, which is the secondary network address of the video content. Additional URIs for each channel may be included if needed. When the URIs of the content are updated or otherwise modified, such as setting or otherwise changing the primary and / or secondary URIs, the content provider or other party 550 may use a network connection to update the channel table 500. The integrated network receiver 410 queries the video address server 450 to obtain the channel list (if it has not yet been obtained or defined) and obtains the associated URI 1 520 and URI 2 530 (and additional URIs, if any). The channels and URIs may be globally defined or defined for one or more integrated network receivers. The integrated network receiver 410 uses the URIs obtained from the video address server 450 to obtain the video content, which is then provided to the headend, and the headend distributes the video content to clients. If needed, the integrated network receiver 410 periodically receives an updated list of channels from the content provider, along with updated associated URIs 1 520 and URI 2 530 (and additional URIs, if any). Furthermore, the integrated network receiver and / or a group of integrated network receivers can be triggered to query for updates based on data (e.g., commands) received from the content provider and included within the content being processed.

[0022] As can be seen, content provider 550 can update the channel table 500 of video address server 450 based on its preferences, which can be done hourly, daily, weekly, or otherwise. For example, content provider 550 can determine that another network is providing higher quality of service or a cheaper service to deliver video content to integrated network receiver 410. Based on this determination, content provider 550 can update URI 1 and / or URI 2 in the channel table 500 of video address server 450. Integrated network receiver 410 uses URI 1 520 to receive video content, and if video content is unavailable based on URI 1 520, integrated network receiver 410 switches to URI 2 530 to receive video content. In this way, the system has built-in redundancy for obtaining video content from multiple sources. Additional URIs can also be used if needed. Providing a channel table 500 separate from the video content itself simplifies the identification of the desired URI for intended use, rather than the complex signaling of URIs within the video content itself. Identifying the required URI is simplified when different receivers are using different URIs for the same video content.

[0023] An integrated network receiver 410 can be installed at the headend of a cable television system. Program identifiers for channel queuing of one or more channels, or channel queuings for one or more channels (all these channels are generally referred to as channels or multiple channels), can be provided to the integrated network receiver 410. If needed, program identifiers and / or channel queuings assigned to the receiver can be obtained from a video address server 450. Based on the program identifiers and / or channel queuings, the integrated network receiver 410 is populated with mapping information between channel queuings and URIs (URI 1 520 and URI 2 530). The integrated network receiver 410 then receives content from the URI 1 520 location, and if content is not available from the URI 1 520 location, the integrated network receiver 410 receives content from the URI 2 530 location for the corresponding channel. Preferably, after activation, the integrated network receiver 410 automatically interconnects with the video address server 450 and configures itself based on information in the channel table 500 (including channel queuings). This automatic configuration may also include obtaining access to video content from content providers and authorization to decrypt the video content if necessary.

[0024] The integrated network receiver 410 can monitor network parameters of video content received at a URI. For example, the integrated network receiver 410 can determine one or more parameters (e.g., quality of service for each video stream), including latency, packet loss, bit rate, transmission delay, availability, jitter, effective throughput, errors, packet delay variations, out-of-order delivery, and so on. Furthermore, the integrated network receiver 410 can also receive pricing information from various networks. The integrated network receiver 410 can also determine parameters related to the geographic region from which the video content originates (e.g., the US West Coast and US East Coast). If needed, the integrated network receiver 410 can cascade such parameters and provide parameter information to content providers or cable TV providers, enabling them to assess the network performance of the video content. Based on the network performance of different network providers (e.g., based on their URIs), it can be determined which network provider offers better service. Based on service determination (which can be further based on pricing information), content providers can update Channel Table 500 to reflect service determination.

[0025] A set of integrated network receivers can be used to serve multiple different channels based on data obtained from a video address server. This set of integrated network receivers can operate in conjunction with a headend to provide channel queuing for Internet Protocol (IP)-based video services, with each integrated network receiver serving a different channel. The set of integrated network receivers then provides video content to the headend, which in turn distributes the video content to clients.

[0026] The video address server 450, combined with multiple integrated network receivers, can be used to efficiently switch from one set of primary URI sources to another without affecting service. For example, an integrated network receiver might have a first set of URIs, 1 and 2, where video content is provided via URI 1. The updated primary URI can be achieved by terminating the availability of video content from URI 1. Therefore, the integrated network receiver automatically switches to the secondary URI 2 to continue receiving video content. URI 1 is updated at channel table 500 and subsequently obtained by the integrated network receiver. If video content is available from the new URI 1, the integrated network receiver will then switch to obtaining video content from URI 1.

[0027] Furthermore, each functional block or feature in each of the foregoing embodiments can be implemented or executed by a circuit, which is typically an integrated circuit or multiple integrated circuits. Circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, or discrete hardware components or combinations thereof. A general-purpose processor may be a microprocessor, or the processor may be a conventional processor, controller, microcontroller, or state machine. The aforementioned general-purpose processors or each circuit may be configured by digital circuitry or by analog circuitry. Furthermore, when advancements in semiconductor technology lead to the development of technologies for manufacturing integrated circuits that replace current integrated circuits, integrated circuits manufactured using these technologies can also be used.

[0028] It should be understood that the invention is not limited to the specific embodiments described, and variations may be made therein without departing from the scope of the invention as defined in the appended claims, the scope of which is interpreted in accordance with principles of prevailing law, including the doctrine of equivalents or any other principle that extends the enforceability of the claims beyond their literal meaning. Unless the context otherwise indicates, references to the number of instances of an element in the claims (whether to one instance or more than one instance) require at least the specified number of instances of the element, but are not intended to exclude structures or methods having more instances than the instances of the element from the scope of the claims. When used in claims, the word "comprising" or its derivatives are used in a non-exclusive sense, which is not intended to exclude the presence of other elements or steps in the claimed structure or method.

Claims

1. An integrated network receiver comprising a processor, comprising: (a) the integrated network receiver comprises a first uniform resource identifier (URI) of a first channel received from a video address server based on a request of the integrated network receiver prior to receiving video content of the first channel from a first source via a transmission medium, the integrated network receiver comprises a second URI of the first channel received from the video address server based on a request of the integrated network receiver prior to receiving video content of the first channel from the first source via the transmission medium, wherein the video content of the first channel is to be simultaneously provided to a plurality of client devices by a network device such that the first channel with the first URI and the second URI corresponds to the plurality of client devices, and the integrated network receiver switches from receiving the video content based on the first URI to receiving the video content based on the second URI when the video content is not available based on the first URI, wherein the integrated network receiver further obtains authorization from a content provider of the video content prior to receiving the video content; (b) the integrated network receiver provides the video content of the first channel to the network device connected to the plurality of client devices via a transmission network, each client device is configured to receive the video content from the same first channel with the first URI and the second URI; (c) the integrated network receiver periodically receives an updated at least one of the first URI and the second URI from the video address server, the content provider provides the update of the first URI and the second URI.

2. The integrated network receiver of claim 1, wherein, the integrated network receiver switches from receiving the video content based on the second URI to receiving the video content based on the first URI when the video content is available based on the first URI.

3. The integrated network receiver of claim 1, wherein, the video content is transcoded, and the transcoded video content is provided to the network device as the video content of the first channel.

4. The integrated network receiver of claim 1, wherein, the first URI is updated on the video address server via a network connection.

5. The integrated network receiver of claim 4, wherein, the second URI is updated on the video address server via the network connection.

6. The integrated network receiver of claim 1, wherein, the integrated network receiver comprises a plurality of additional channels and a plurality of corresponding additional URIs, one of the plurality of corresponding additional URIs is associated with a respective additional channel.

7. The integrated network receiver of claim 1, further comprising monitoring network parameters related to the video content.

8. The integrated network receiver of claim 7, wherein, the network parameters comprise at least one of a quality of service of the video content, a latency of the video content, a packet loss of the video content, a bit rate of the video content, a transmission delay of the video content, an availability of the video content, a jitter of the video content, an effective throughput of the video content, an error of the video content, a packet delay variation of the video content, and an out-of-order delivery of the video content.

9. The integrated network receiver of claim 1, wherein, The integrated network receiver switches from receiving the video content based on the first URI to receiving the video content based on the second URI based on network parameters related to the video content.

Images