Multicast Notifier for Set-Top Box Channel Data Distribution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multimedia distribution systems face scalability and latency issues due to the use of HTTP for .nsc file retrieval, which is inefficient for broadcast TV solutions and introduces channel changing latency, especially when many set-top boxes (STBs) change channels simultaneously.
Innovation Solution
A method for delivering broadcast channels over a broadband network using a multicast protocol, where .nsc files are stored locally on subscriber terminals, and a multicast notifier provides the necessary information for accessing new channels, allowing STBs to join the appropriate multicast group and retrieve channel data without relying on remote servers for each channel change.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If HTTP protocol is used for .nsc file retrieval, then file access is simple and standardized, but scalability deteriorates and latency increases when many STBs change channels simultaneously
Solution Approach 1:
The patent creates local copies of .nsc files on STB devices and distributes them via multicast. Instead of every STB retrieving .nsc files individually from the server via HTTP, the system copies these configuration files to local storage on each STB, eliminating repeated server access and enabling simultaneous channel changes without server bottlenecking.
Solution Approach 2:
The patent combines .nsc file distribution with the multicast video stream delivery mechanism. By integrating the configuration file distribution into the existing multicast infrastructure, the system efficiently delivers both video content and associated metadata (.nsc files) through the same network pathway, reducing overhead and improving scalability.
2Ease of operation
If HTTP protocol is used for .nsc file retrieval, then individual file access is straightforward, but channel changing latency increases especially when many STBs change channels simultaneously
Solution Approach 1:
The patent performs preliminary distribution of .nsc files to STB local storage in advance, so that when channel changes occur, the files are already available locally rather than needing to be retrieved from the server at the moment of channel change. This pre-positioning of data eliminates retrieval latency during actual channel switching operations.
Solution Approach 2:
By copying .nsc files to local storage on each STB device, the system eliminates network latency associated with real-time file retrieval during channel changes. The local copies enable instant access to channel configuration data, significantly reducing the time required for channel switching operations.
3Extent of automation
If remote server access is used for each channel change, then centralized control is maintained, but system performance deteriorates due to frequent server requests
Solution Approach 1:
The patent enables STB devices to serve themselves by storing .nsc files locally and autonomously retrieving channel data from multicast groups without requiring centralized server mediation for each channel change. The STBs independently join multicast groups and receive channel data directly, reducing server load while maintaining system coordination through the multicast protocol.
Data Source
AI summary
For offering entertainment services by video streaming content to users, a video encoder creates the required .nsc file for each broadcast channel. This .nsc file is retrieved and stored on a server which notifies each set-top box in the field, via a multicast notifier of the availability of the new service. This notifier contains the multicast address and port to where the .nsc files are being streamed. Once the set-top box retrieves this notification, it attempts to join the dedicated multicast stream, download the .nsc files and store them locally in memory on the set-top box. When a user selects a broadcast channel from their lineup, the set-top box will access the local file to obtain the proper information about that particular ASF stream; hence, it will not have to do an HTTP retrieval.