Non Real-Time Broadcast Receiver Error Handling via Return Channel
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing digital broadcast systems face challenges in providing non real-time services without errors, particularly due to limitations in two-way communication schemes like IPTV, which suffer from degraded data rates and quality of service issues, especially for high-definition video, and are unable to handle channel changes or errors effectively.
Innovation Solution
A non real-time broadcast receiving system that includes a decoder, service content manager, memory, file checker, retransmission request signal generator, and return channel transmitter to identify and retransmit error portions of content, using protocols like FLUTE and FEC, allowing for error-free content delivery through a return channel network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If two-way communication schemes like IPTV are used to provide non real-time services, then user interaction and service flexibility are improved, but data rate and quality of service are degraded
Solution Approach 1:
The system segments the communication path into a broadcast channel for content delivery and a return channel for error reporting and retransmission requests. This segmentation allows the broadcast channel to maintain high data rates while the return channel handles error management, thus preserving quality of service without sacrificing service flexibility.
Solution Approach 2:
The patent introduces a file delivery table and error indication mechanism as an intermediary between the broadcast content and the receiver. This intermediary enables the system to identify and request retransmission of only erroneous portions without requiring full two-way communication for all data transfer, maintaining both flexibility and reliability.
2Adaptability or versatility
If multicasting or unicasting is used for two-way broadcast service, then user-specific content delivery is improved, but the maximum number of users and coverage are reduced
Solution Approach 1:
The system segments content delivery into a broadcast component that serves multiple users simultaneously and a return channel component that handles user-specific error reporting. This allows one-to-many content distribution while maintaining individualized error management for each user.
Solution Approach 2:
The broadcast channel serves a universal function of delivering content to multiple users simultaneously, while the return channel provides a universal error handling mechanism that works for all users. This multi-functional approach enables both mass coverage and user-specific service.
3Quantity of substance
If broadcast scheme is used for digital broadcast, then coverage and number of users are improved, but error handling and retransmission capability are reduced
Solution Approach 1:
The system segments the communication function into broadcast content delivery (for coverage) and return channel error reporting (for reliability). This segmentation allows the system to maintain broad coverage through broadcast while adding error handling capability through the return channel.
Solution Approach 2:
The patent implements a feedback mechanism where receivers report errors through the return channel and request retransmission of specific erroneous portions. This feedback loop enables the broadcast system to handle errors effectively while maintaining its coverage advantage.
4Productivity
If FLUTE protocol is used for content file download, then content delivery efficiency is improved, but error detection and retransmission require additional complexity
Solution Approach 1:
The system segments error detection and retransmission into separate, standardized procedures that operate independently of the main FLUTE content delivery process. This segmentation maintains content delivery efficiency while managing error handling complexity through modular, protocol-based approaches.
Data Source
AI summary
Disclosed herein is a non real-time broadcast receiving system. The system includes: a non real-time service decoder dividing received non real-time service content into a transmission block according to a protocol; a service content manager monitoring whether the receive of the non real-time service content stops and acknowledging a schedule regarding whether a portion with errors in the non real-time service content is retransmitted; a memory storing a portion without errors in the non real-time service content; a file checker checking whether errors are produced during the receive of the non real-time service contents and determining whether the portion with errors in the non real-time service content is retransmitted; a retransmission request signal generator generating a retransmission request signal; a return channel transmitter transmitting the retransmission request signal; and a return channel receiver receiving data corresponding the portion with error.