Extended Channel Flow Initiation Protocol for Cable Broadcast Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current broadcast receiver systems face inefficiencies in data transmission between cable broadcast receivers and cable cards over extended channels, particularly in supporting various service types and managing flow connections effectively.
Innovation Solution
The implementation of a method and data structure that allows for the efficient initiation and management of flows over extended channels by receiving requests, checking channel support, and responding with necessary information, including service types, transaction sequences, and IP addresses, using specific application protocol data units (APDUs) to facilitate communication between cable broadcast receivers and cable cards.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a traditional data transmission method is used between cable broadcast receiver and cable card, then the system can maintain simple structure, but the data transmission efficiency is low and cannot effectively support various service types
Solution Approach 1:
The patent segments the data transmission process into distinct phases: flow initiation request, channel capability checking, and flow establishment confirmation. This is achieved through dividing the communication into separate APDU (Application Protocol Data Unit) exchanges between the cable broadcast receiver and cable card, allowing each phase to be handled independently and efficiently
Solution Approach 2:
The patent introduces an intermediary protocol layer (extended channel protocol) that mediates between the cable broadcast receiver and cable card. This protocol includes standardized message formats for flow initiation requests, channel capability checks, and flow establishment confirmations, enabling efficient data transmission without requiring complex direct integration between components
2Adaptability or versatility
If the system supports multiple service types (MPEG sections, IP Unicast, IP Multicast), then the adaptability increases, but the implementation complexity increases
Solution Approach 1:
The patent implements a universal flow initiation protocol that can handle multiple service types (MPEG sections, IP Unicast, IP Multicast) through a single standardized interface. The extended channel protocol defines universal message structures that accommodate different service types without requiring separate specialized protocols for each service
Solution Approach 2:
The patent uses parameter-based service type identification where different service types are distinguished by specific parameters within the standardized protocol messages. For example, service type indicators and channel capability flags allow the same protocol structure to adapt to different service requirements by changing relevant parameters rather than requiring different protocol structures
3Reliability
If flow initiation includes comprehensive checking of channel support, then the reliability of flow establishment increases, but the communication time increases
Solution Approach 1:
The patent performs preliminary channel capability checking during the flow initiation phase, before actual data transmission begins. The cable broadcast receiver sends a flow initiation request that includes pre-assessed channel capability information, allowing the cable card to verify support for the requested service type in advance, ensuring reliable flow establishment without delaying subsequent data transmission
Solution Approach 2:
The patent implements an optimized flow initiation sequence that skips unnecessary verification steps when channel capabilities are already known or pre-configured. The protocol allows for streamlined confirmation messages when the cable card can immediately verify channel support without requiring extensive back-and-forth capability negotiation, reducing communication overhead while maintaining reliability
Data Source
AI summary
A method included a receiving a request that includes information that defines a service type and information that can identify the request for this service type, wherein the request is required in order to initiate a flow over an extended channel; checking whether the extended channel can support the flow of the requested service type; and responding to the request, wherein the response includes information of the service type and information on whether the external channel can support the flow of the requested service type.