DASH File Construction for Encrypted ATSC 3.0 MMTP Playback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software-based media players, such as those equipped in televisions, are unable to play ATSC 3.0's encrypted MMTP content due to the new specification using Widevine encryption, as they are not agnostic to the MMTP protocol and cannot process media and header data in the required order.
Innovation Solution
Convert MMTP data into DASH protocol for playback, enabling the reuse of a DASH media player by constructing DASH media files that include MPU header data, fragment header data, and MPU data, while accounting for discarded Fragment Type 3 data and appending DRM data, allowing playback using a DASH player.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If software-based media players are used to play ATSC 3.0 encrypted MMTP content, then the players cannot process the content due to protocol incompatibility and encryption, but requiring multiple specialized media players increases device complexity
Solution Approach 1:
The patent introduces a proxy server as an intermediary component that sits between the ATSC 3.0 content source and the existing DASH media player. The proxy server receives encrypted MMTP content, performs decryption using Widevine DRM, converts the content to DASH protocol format, and delivers it to the player. This intermediary resolves the protocol incompatibility without requiring changes to the existing media player, thereby maintaining versatility while avoiding increased device complexity.
Solution Approach 2:
The patent changes the protocol parameter from MMTP to DASH through the proxy server's content conversion function. By transforming the content delivery protocol at the server level, the system enables existing DASH-optimized media players to handle ATSC 3.0 content without requiring the players to support multiple protocols, thus resolving the contradiction between adaptability and device complexity.
2Reliability
If MMTP protocol is used for content delivery, then the media must be delivered first followed by header data, but software players require header data before media for proper processing
Solution Approach 1:
The patent applies preliminary action by having the proxy server perform buffer management and data reordering operations before delivering content to the player. The server receives MMTP packets with media data first, then performs preliminary processing to extract and reorder header data, ensuring that complete MPUs with proper header information are assembled and delivered to the player in the correct sequence. This preliminary reordering resolves the contradiction between reliable MMTP delivery and player-friendly processing sequences.
3Ease of manufacture
If a DASH media player is used for MMTP playback, then the player cannot natively support MMTP protocol, but converting to DASH enables reuse of existing player infrastructure
Solution Approach 1:
The patent uses the proxy server as a protocol conversion intermediary that handles the complex task of transforming MMTP protocol content into DASH format. This places the protocol conversion complexity at the server level rather than requiring complex multi-protocol support in each media player device. The result is easier player implementation since players only need to support DASH, while the server handles the conversion complexity centrally.
Data Source
AI summary
Moving Picture Experts Group (MPEG) media transport protocol (MMTP) content is received from a source of content such as an ATSC 3.0 source. The MMTP content is used to construct as a Dynamic Adaptive Streaming over Hypertext Transfer Protocol (DASH) files. Constructing the file includes writing media processing units (MPU) header data, fragment header data, and MPU data. Constructing the media files also includes accounting for discarded Fragment Type 3 data in relation to a media data (MDAT) section of the DASH media files. Further, constructing the file includes appending digital rights management (DRM) data to the DASH MPD file. After the file has been constructed, a DASH software media player can play the media content using the file.