SYSTEM FOR MONITORING AND MANAGING DECODERS WITH INTEGRATED RECEIVER

Abstract

An integrated network receiver includes a first universal resource identifier (URI) for a first channel and an input suitable for receiving first incoming video content from the internet based on that URI. The integrated network receiver provides the first incoming video content for the first channel to a headend connected to multiple client devices via a broadcast network. The integrated network receiver updates the URI based on data obtained from a video address server.

Description

SYSTEM FOR MONITORING AND MANAGING DECODERS WITH RECEIVER INTEGRATED LCPznn / pznz / e / YiAi CROSS REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. provisional patent application no. 63 / 070,105 filed on August 25, 2020. BACKGROUND The subject of this request relates to the monitoring and / or management of a network of commercial integrated receiver decoders. Cable television (CATV) services provide content to large groups of customers (e.g., subscribers) from a central delivery unit, typically called a "headend," which distributes content channels to its customers via an access network comprising a hybrid fiber-coaxial (HFC) cable plant, including associated components (nodes, amplifiers, and taps). However, modern cable television (CATV) service networks not only provide multimedia content, such as television and music channels, but also a range of digital communication services, including internet access, video on demand, telephone services such as Voice over Paper (VoP), home automation / security, and more.These digital communication services, in turn, require not only downstream communication from the headend, via HFC, which typically forms a branch network to a customer, but also upstream communication from a customer to the headend, typically via the HFC network. To this end, CATV headends have historically included a separate cable modem termination system (CMTS), used to provide high-speed data services such as cable internet, voice over internet protocol, etc., to cable customers, and a video headend system, used to provide video services such as broadcast video and video on demand (VOD). A CMTS typically includes both Ethernet interfaces (or other more traditional high-speed data interfaces) and radio frequency (RF) interfaces so that traffic from the internet can be routed (or connected) via the Ethernet interface, through the CMTS, and then to the RF interfaces that are connected to the cable company's hybrid fiber-coaxial (HFC) system.Downstream traffic is delivered from the CMTS to a cable modem and / or set-top box in a customer's home, while upstream traffic is delivered from a cable modem and / or set-top box in a customer's home to the CMTS. Similarly, the video headend system delivers video to a set-top box, TV with a video decryption card, or other device capable of demodulating and decrypting incoming encrypted video services. Many modern CATV systems have combined the functionality of the CMTS with the video delivery system (e.g., EdgeQAM - quadrature amplitude modulation) into a single platform, generally called an integrated CMTS (e.g., integrated converged cable access platform (CCAP)). Video services are prepared and delivered to the CCAP, where QAM then modulates the video at the appropriate frequencies.Still other modern CATV systems, generally referred to as distributed CMTS (e.g., distributed converged cable access platform), may include a remote PHY (or R-PHY) that relocates the physical layer (PHY) of a traditional embedded CCAP by pushing it to the fiber nodes of the network (RMAC PHY relocates MAC and PHY to the network nodes). Therefore, while the core in the CCAP performs the upper-layer processing, the R-PHY device at the remote node converts the downstream data sent from the digital core to analog for transmission over radio frequency to the cable modems and / or set-top boxes, and converts the upstream data sent from the cable modems and / or set-top boxes from analog to digital for optical transmission to the core. BRIEF DESCRIPTION OF THE FIGURES For a better understanding of the invention, and to show how it can be carried out, reference will now be made, by way of example, to the accompanying figures, in which: Figure 1 illustrates an integrated cable modem termination system. Figure 2 illustrates a Distributed Cable Modem Termination System. Figure 3 illustrates a headend along with an integrated satellite receiver. Figure 4 illustrates a header along with an integrated network receiver and video address server. Figure 5 illustrates a video address server. DETAILED DESCRIPTION OF THE INVENTION With reference to Figure 1, an integrated CMTS (e.g., Converged Cable Access Platform (CCAP)) 100 may include data 110 that is sent and received over the Internet (or another network), typically in the form of packet data. The integrated CMTS 100 may also receive downstream video 120, typically in the form of packet data, from an operator's video aggregation system. For example, broadcast video is usually obtained from a satellite delivery system and pre-processed for delivery to the subscriber via the CCAP or 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 can receive upstream data 170 from a customer's cable modem and / or set-top box 160 via a network, which may include other devices. LCPznn / pznz / e / YiAi such as amplifiers and dividers. The CMTS 130 can include multiple devices to achieve its desired capabilities. With reference to Figure 2, due to increased bandwidth demands, limited space in facilities for integrated CMTSs, and power consumption considerations, it is desirable to include a Distributed Cable Modem Termination System (D-CMTS) 200 (e.g., Distributed Converged Cable Access Platform (CCAP)). Generally, the CMTS focuses on data services, while the CCAP also includes video streaming services. The D-CMTS 200 distributes a portion of the downstream functionality of the 1-CMTS 100 to a remote location, such as a fiber node, using packet-based data. An illustrative D-CMTS 200 might include a remote PHY architecture, where a remote PHY (R-PHY) is preferably an optical node device located at the fiber-coaxial junction. Generally, the R-PHY often includes the PHY layers of a portion of the system.The D-CMTS 200 may include a D-CMTS 230 (for example, a core) that carries data 210 sent and received over the Internet (or another network), typically in packet form. The D-CMTS 200 may also receive downstream video 220, typically in packet form, from a carrier's video aggregation system. The D-CMTS 230 receives and processes the received data 210 and downstream video 220. A remote fiber 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 over 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 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 include multiple devices to achieve its desired capabilities. It primarily comprises PHY-related circuitry, such as downlink QAM modulators and uplink QAM demodulators, along with pseudo-cable logic for connecting to the D-CMTS 230 using packet-based network data. The remote PHY device 290 and the D-CMTS 230 may include data and / or video interconnects, such as downlink data, downlink video, and uplink data. In some configurations, video traffic can be routed directly to the remote physical device, bypassing the D-CMTS 230. In some cases, remote PHY and / or remote MAC functionality may be provided at the headend. As an example, the remote PHY 290 device can downconvert downstream DOCSIS data (i.e., Wired Data Service Interface Specifications) (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 to analog for transmission over RF or analog optical signals. As an example, the remote PHY 290 device can also upstream DOCSIS and out-of-band signals received from a medium LCPznn / pznz / e / YiAi analog, such as RF or linear optical, to digital for transmission to the D-CMTS 230. As can be seen, depending on the particular configuration, the R-PHY can move all or a portion of the DOCSIS MAC and / or PHY layers to the fiber node. In another scenario, the system doesn't need to include a CMTS, whether an integrated or distributed CMTS, but can use any other type of system for the headend and / or any other type of network for content distribution. For example, headend distribution can be handled by a set of servers that provide data connectivity to clients through any type of network, including a fiber optic network, a wireless network, a cellular network, or any other means. With reference to Figure 3, the 300 headend, whether an integrated system, a distributed system, or any other type of system, often includes an associated integrated satellite receiver 310 for high-density transcoding (or passing) of video content from one or more satellites. The integrated satellite receiver 310 may include one or more active radio frequency tuners capable of retuning to receive satellite signals and one or more network ports, such as Ethernet, providing network connections to the headend devices. For example, the integrated satellite receiver 310 can transcode the video content of 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. To install and configure the Integrated Satellite Receiver 310, it is typically rack-mounted, powered on, and its RF satellite input ports are configured to receive signals from one or more satellites. For example, the ports might be wired to a Galaxy 15 C-band horizontal signal and / or a Galaxy 14 C-band vertical signal and / or a Galaxy 14 C-band horizontal signal. The Integrated Satellite Receiver 310 may include Ethernet and / or ASI (Asynchronous Serial Interface) outputs that connect to the headend. A set of frequency and modulation parameters is entered into the Integrated Satellite Receiver 310 to lock the satellite signals. For example, this might include an input port ID, a frequency, a transponder number, a modulation mode, and / or a symbol rate.Typically, authorization for the integrated satellite receiver 310 is obtained based on a content provider's integrated satellite receiver 310 unit address so that it can properly receive and decode the content provider's video signals delivered from the 320 satellite(s). Examples of content providers may include ABC, CBS, CW, ION, Dish, NBC, PBS, A&E, ACCN, ESPN, AHC, AMC, BBC America, BTN, Bloomberg Television, CNN, HBO, and / or Bravo. The content received and transcoded (or transferred) by the integrated satellite receiver 310 is then provided to the 300 headend, which in turn distributes the content to local and regional subscribers. LCPznn / pznz / e / YiAi In most cases, after configuring the 310 integrated satellite receiver using its small and error-prone interface, the frequency and modulation parameters are unlikely to change for a substantial period of time, such as several months to several years. Consequently, there is little need to reconfigure the 310 integrated satellite receiver after its initial setup.Being limited to satellite communications, the Integrated Satellite Receiver 310 is not suitable for Internet-based video content because it is problematic to program such an Internet-based Uniform Resource Locator and / or Uniform Resource Identifier (generally referred to collectively in this description as a Uniform Resource Identifier “URI”) into the Integrated Satellite Receiver 310, and URIs tend to change more dynamically, making it difficult to modify the Integrated Satellite Receiver 310's configuration to maintain the current URI being used for each particular video stream. For example, content providers may choose to change content distribution networks frequently, depending on a variety of factors, including network performance and costs.Furthermore, in the case of multiple 310 integrated satellite receivers, each would need to have its configuration modified to maintain the current URI used for that particular integrated satellite receiver for each particular associated video stream. With reference to Figure 4, the 400 headend of a cable system, whether an integrated or distributed system, includes an associated integrated network receiver 410 for high-density transcoding (or passing) of video content from a packet-based Internet network source, such as a video content server. The integrated network receiver 410 may include one or more network ports for receiving Internet-based signals, and one or more network ports, such as Ethernet and ASI, that provide network connections to other headend devices. For example, the integrated network receiver 410 may transcode the video content of one or more received high-definition video signals and / or one or more received standard-definition video signals, or otherwise provide a pass-through from an input format to an output format (or otherwise to the same format). To install and configure the 410 Integrated Network Receiver, the receiver is typically rack-mounted, powered on, and its network inputs are connected to receive signals from one or more Internet video network sources, such as video servers. For example, the network inputs can receive Internet-based data from various network servers, such as cloud-based network servers. Examples of cloud-based networks include Amazon Web Services, Google Cloud Platform, Microsoft Azure, IBM Cloud, Oracle Cloud, VMware Cloud, Dell Technologies Cloud, and / or private servers / clouds. The 410 Integrated Network Receiver preferably queries a video address server over a network connection to obtain one or more URI addresses based on the [Protocol / Resource / etc.]. LCPznn / Fznz / e / YiAi Internet access is provided to the respective video sources for the 400 header. Preferably, the 450 video address server provides a corresponding URI for each video content channel. For example, the URI might be in the following format: URI = scheme:[ / / authority]path[?query][#fragment]. Typically, the 410 integrated network receiver is authorized based on a content provider's 410 integrated network receiver address so that it can properly receive and decode the content provider's video signals delivered over the internet. Examples of content providers include ABC, CBS, CW, ION, Dish, NBC, PBS, A&E, ACCN, ESPN, AHC, AMC, BBC America, BTN, Bloomberg Television, CNN, HBO, and / or Bravo.The content received and transcoded (or transferred) by the integrated network receiver 410 is then provided to the 400 headend, which in turn distributes the content to local and regional subscribers. With reference to Figure 5, the video address server 450 includes a channel table or other data structure 500 that includes a list of one or more channels 510. Each of the channels 510 can include an associated URI 1 520, which is a primary network address for the video content. Each of the channels 510 can include an associated URI 2 530, which is a secondary network address for the video content. Additional URIs can be included for each channel if desired. A content provider or otherwise 550 can update the channel table 500 by using a network connection when the URIs for the content are updated or otherwise modified, such as by configuring or otherwise changing the primary and / or secondary URIs.The integrated network receiver 410 queries the video address server 450 and obtains the channel list (if it has not already been obtained or defined) and obtains the associated URI 1 520 and URI 2 530 (and any additional URIs if available). Channels and URIs can be defined globally or for one or more integrated network receivers. The integrated network receiver 410 uses the URIs obtained from the video address server 450 to obtain video content, which is then provided to the headend, and the headend distributes the video content to clients. The integrated network receiver 410 periodically receives an updated channel list, if desired, along with the updated associated URI 1 520 and URI 2 530 (and any additional URIs if available), from the content provider.Additionally, an integrated network receiver and / or a group of integrated network receivers can be activated to query data-based updates (e.g., commands) received from the provided content, included within the content being processed. As can be seen, content provider 550 can update the channel table 500 of the video address server 450, which can occur hourly, daily, weekly, or in any other way depending on the content provider's preferences. For example, content provider 550 might determine that another network is providing a higher quality of service or, conversely, that another network is providing a less expensive service, for the LCPznn / pznz / e / YiAi delivers video content to the integrated network receiver 410. Based on this determination, the content provider 550 can update URI 1 and / or URI 2 in the channel table 500 of the video address server 450. The integrated network receiver 410 uses URI 1 520 to receive the video content, and if the video content is not available based on URI 1 520, then the integrated network receiver 410 switches to URI 2 530 to receive the video content. In this way, the system has a built-in redundancy function for obtaining video content from multiple sources. Other URIs can be used if desired. Providing a channel table 500 that is separate from the video content itself simplifies the identification of the desired URIs to be used, instead of complicated in-band URI signaling with the video content.Simplifying the identification of desired URIs when different receivers use different URIs for the same video content. The Integrated Network Receiver 410 can be installed at the headend of a cable system. The Integrated Network Receiver 410 can be supplied with program IDs for a channel line of one or more channels, or alternatively, the channel line of one or more channels (all of which are generally referred to as a channel or channels). The program ID and / or channel alignment assigned to the receiver can be obtained from the Video Address Server 450, if desired. Based on the program ID and / or channel alignment, the Integrated Network Receiver 410 is populated with mapping information between the channel alignment and the URIs (URI 1 520 and URI 2 530). The Integrated Network Receiver 410 then receives content from the URI 1 520 locations, and if content is not available from the URI 1 520 locations, the Integrated Network Receiver 410 receives content from the URI 2 530 locations, for the respective channels.Preferably, after activating the integrated network receiver 410, it automatically interfaces with the video address server 450 and configures itself based on the information in the channel table 500, which includes the channel lineup. This automatic configuration may also include obtaining authorization from a content provider to receive video content and decrypting the video content if necessary. The 410 Integrated Network Receiver can monitor the network parameters of the video content received at the URIs. For example, the 410 Integrated Network Receiver can determine one or more parameters, such as Quality of Service (QoS) for each video stream, latency for each video stream, packet loss for each video stream, bit rate for each video stream, transmission delay for each video stream, availability for each video stream, jitter for each video stream, usable throughput for each video stream, errors for each video stream, packet delay variation for each video stream, and out-of-service delivery. LCPznn / pznz / e / YiAi for each video stream, etc. Furthermore, the Integrated Network Receiver 410 can also receive pricing information for various networks. The Integrated Network Receiver 410 can also determine parameters related to the geographic regions from which the video content originates, such as the US West Coast and the US East Coast. The Integrated Network Receiver 410 can concatenate these parameters, if desired, and provide parameter information to the content provider or cable provider so they can evaluate network performance for video content. Based on the network performance of different network providers, such as based on their URIs, it can be determined which network provider offers superior service.Based on service determinations, which may also be based on pricing information, the content provider may update the 500 channel table to reflect the service determinations. A set of integrated network receivers can be used to provide services for multiple different channels based on data obtained from the video address server. This set of integrated network receivers can operate collectively with a headend to provide a channel line for Internet Protocol-based video services, with each integrated network receiver providing different channels. The integrated network receivers supply video content to the headend, which in turn distributes the video content to clients. The 450 video address server, in combination with integrated network receivers, can be used to efficiently transition from one set of primary source URIs to another without disrupting service. For example, an integrated network receiver might have an initial set of URIs 1 and 2, with video content delivered via URI 1. An updated primary URI can be obtained when video content becomes unavailable from URI 1. As a result, the integrated network receiver automatically switches to the secondary URI 2 to continue receiving video content. URI 1 is updated in the 500 channel table, which the integrated network receiver then obtains. The integrated network receiver will subsequently switch to obtaining video content from URI 1 if video content becomes available from the new URI 1. Furthermore, each functional block or several features in each of the aforementioned modes can be implemented or executed by a circuit, which is typically an integrated circuit or a plurality of integrated circuits. The circuits designed to execute the functions described herein may comprise a general-purpose processor, a digital signal processor (DSP), an application-specific or general-purpose integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, or a LCPznn / pznz / e / YiAi microcontroller or a state machine. The general-purpose processor or each circuit described above can be configured using a digital circuit or an analog circuit. Furthermore, when a manufacturing technology for integrated circuits emerges that replaces traditional integrated circuits due to advancements in semiconductor technology, integrated circuits using this technology can also be used. It will be appreciated that the invention is not limited to the particular embodiment described, and that variations may be made thereon without departing from the scope of the invention as defined in the appended claims, as interpreted in accordance with the principles of applicable law, including the doctrine of equivalents or any other principle that extends the enforceable scope of a claim beyond its literal scope. Unless the context indicates otherwise, a reference in a claim to the number of instances of an element, whether a reference to one instance or more than one instance, requires at least the stated number of instances of the element, but is not intended to exclude from the scope of the claim a structure or method having more instances of that element than stated.The word “comprises” or a derivative thereof, when used in a claim, is used in a non-exclusive sense that is not intended to exclude the presence of other elements or steps in a claimed structure or method.

Claims

1. An integrated network receiver including a processor comprising: (a) said integrated network receiver including a first universal resource identifier for a first channel, said integrated network receiver including an input suitable for receiving a first input video content from the Internet based on said first universal resource identifier; (b) said integrated network receiver providing said first input video content for said first channel to a headend connected to a plurality of client devices via a transmission network; (c) said integrated network receiver updating said first universal resource identifier based on data obtained from a video address server.

2. The integrated network receiver of claim 1, wherein said integrated network receiver includes a second universal resource identifier for said first channel.

3. The integrated network receiver of claim 2, wherein said integrated network receiver switches from receiving said first input video content based on said first universal resource identifier to said second universal resource identifier when said video content is not available based on said first universal resource identifier.

4. The integrated network receiver of claim 3, wherein said integrated network receiver updates said second universal resource identifier based on data obtained from said video address server.

5. The integrated network receiver of claim 4 wherein said integrated network receiver switching from receiving said first input video content based on said second universal resource identifier to said first universal resource identifier when said video content is available based on said first universal resource identifier.

6. The integrated network receiver of claim 1, wherein said first input video content is transcoded and said first transcoded input video content is provided as said first input video content for said first channel to said headend.

7. The integrated network receiver of claim 1, wherein said data obtained from said video address server is via a network connection.

8. The integrated network receiver of claim 1, wherein said first LCPznn / pznz / e / YiAi universal resource identifier is updated on said video address server via a network connection.

9. The integrated network receiver of claim 4, wherein said second universal resource identifier is updated on said video address server via a network connection.

10. The integrated network receiver of claim 1, wherein said integrated network receiver includes a plurality of additional channels and a plurality of corresponding additional universal resource identifiers, one of which is associated with a respective additional channel.

11. The integrated network receiver of claim 1, further comprising monitoring network parameters related to said first input video content.

12. The integrated network receiver of claim 11, wherein said network parameters include at least one of the following: quality of service for said first input video content, latency for said first input video content, packet loss for said first input video content, bit rate for said first input video content, transmission delay for said first input video content, availability for said first input video content, jitter for said first input video content, usable throughput for said first input video content, errors in said first input video content, packet delay variation for said first input video content, and out-of-service delivery for said first input video content.

13. The integrated network receiver of claim 2, wherein said integrated network receiver switches from receiving said first input video content based on said first universal resource identifier to said second universal resource identifier based on network parameters related to said first input video content.

14. An integrated network receiver including a processor comprising: (a) said integrated network receiver including a first universal resource identifier for a first channel, said integrated network receiver including an input suitable for receiving a first input video content from a first network-based source based on said first universal resource identifier; (b) said integrated network receiver providing said first input video content for said first channel to a headend connected to a plurality of client devices via a transmission network; (c) said integrated network receiver updating said first universal resource identifier based on data obtained from a video address server.

15. The integrated network receiver of claim 1, wherein said integrated network receiver includes a second universal resource identifier for said first channel.

16. The integrated network receiver of claim 15, wherein said integrated network receiver switching from receiving said first input video content based on said LCPznn / pznz / e / YiAi first universal resource identifier to said second universal resource identifier when said video content is not available based on said first universal resource identifier.

17. The integrated network receiver of claim 16, wherein said integrated network receiver updates said second universal resource identifier based on data obtained from said video address server.

18. The integrated network receiver of claim 17, wherein said integrated network receiver switches from receiving said first input video content based on said second universal resource identifier to said first universal resource identifier when said video content is available based on said first universal resource identifier.

19. The integrated network receiver of claim 14, wherein said first input video content is transcoded and said first input video content is provided as said first input video content for said first channel to said headend.

Images