Broadcast Content Encapsulation via UDP Port Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Broadcasting content to diverse wireless devices with different CODECs requires a mechanism to identify and manage multiple versions of the same content, ensuring that each device receives the appropriate version without unnecessary data transmission.
Innovation Solution
Data streams corresponding to different versions of content are mapped to components, and these components are encapsulated in packets using protocols like UDP, with a common field in the packet header identifying the component, allowing user equipment to selectively receive and process only the desired components.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple versions of content are broadcast to support diverse wireless devices with different CODECs, then adaptability and content compatibility are improved, but transmission bandwidth consumption and system complexity increase
Solution Approach 1:
The content is segmented into multiple versions encoded with different CODECs, and each version is assigned a unique identifier. This allows the broadcast system to transmit multiple content versions simultaneously while enabling receiving devices to selectively process only the version compatible with their CODEC, thus improving adaptability without proportionally increasing bandwidth consumption for each device.
Solution Approach 2:
A universal identification mechanism is implemented that works across all content versions and device types. The identification system uses common packet header fields to carry version identifiers, enabling a single broadcast transmission to serve multiple device types with different CODECs, languages, and other variations without requiring separate dedicated transmission paths for each device category.
2Adaptability or versatility
If multiple versions of content are broadcast to support diverse wireless devices, then adaptability is improved, but device complexity for processing and identifying versions increases
Solution Approach 1:
Content versions are pre-encoded with different CODECs and pre-assigned unique identifiers before broadcast. This preliminary preparation allows receiving devices to simply filter and select based on the pre-assigned identifiers without performing complex real-time analysis, thereby reducing processing complexity at the device level while maintaining support for multiple content versions.
Solution Approach 2:
An identification field acts as an intermediary between the content version and the receiving device. Instead of requiring devices to analyze and determine compatibility through complex processing, the identifier serves as a direct indicator that mediates the selection process, simplifying device complexity while enabling adaptability to multiple content versions.
3Adaptability or versatility
If content is transmitted in multiple versions with different CODECs, then adaptability is improved, but loss of time for encoding and managing multiple versions increases
Solution Approach 1:
Multiple CODEC versions of content are encoded and prepared in advance before broadcast transmission. This preliminary encoding allows the broadcast system to have all necessary versions ready simultaneously, eliminating the need for real-time encoding decisions and reducing time loss during transmission, while still providing adaptability to diverse device CODECs.
Data Source
AI summary
Components of a transmitted service delivering multiple versions of content are mapped to streams carrying data for those multiple versions. The data streams are encapsulated into User Datagram Protocol (UDP) packets; the UDP destination port fields of the packets are given component-identifying values. A user equipment (UE) receiving the transmitted service identifies desired components based on the UDP destination port field values. The UE further encapsulates desired component UDP packets into Internet Protocol (IP) packets, and may assign component-identifying values to fields of the IP packets (e.g., the IP source address and/or IP destination address).