Transport Frame Metadata Blocks for Backward-Compatible Codec Support
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing media container formats, such as ADTS, impose limitations on the amount and type of data that can be stored in the header block, leading to inadequate representation of newer codecs and playback errors, particularly when streaming media content to diverse client devices.
Innovation Solution
Appending one or more metadata blocks to the payload of transport frames, including extended metadata fields that are not compatible with the header block, allowing advanced codecs to be utilized while maintaining backward compatibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the header block of ADTS frames is used to store metadata for codec configuration, then backward compatibility with legacy audio codecs is maintained, but the amount and type of data that can be stored is restricted, leading to inadequate representation of newer codecs
Solution Approach 1:
The patent segments the metadata storage into two parts: the traditional header block for basic codec information and a new metadata block for extended codec parameters. This segmentation allows the header block to maintain its backward compatibility while the metadata block provides additional storage capacity for newer codec requirements.
Solution Approach 2:
The patent nests the metadata block within the payload portion of the ADTS frame structure. The metadata block is embedded as a nested element that contains extended codec parameters, allowing it to coexist with the traditional header block structure while providing additional functionality.
2Adaptability or versatility
If the profile field in the header block is limited to two bits, then the header block structure remains simple and backward compatible, but only four distinct Audio Object Types can be represented, which is insufficient for current and future codecs
Solution Approach 1:
The patent extracts the extended codec parameter information from the constrained header block structure and places it in a separate metadata block. This extraction allows the profile field to remain simple and backward compatible while the metadata block accommodates the expanded number of Audio Object Types and newer codec parameters.
Solution Approach 2:
The metadata block acts as an intermediary structure that bridges the gap between the simple two-bit profile field in the header block and the need to represent many more Audio Object Types. It provides a translation layer that enables extended codec support without modifying the traditional header block structure.
3Adaptability or versatility
If container formats like ADTS are designed for legacy audio codecs, then wide client device compatibility is achieved, but the formats do not provide sufficient support for evolving media encoding formats
Solution Approach 1:
The patent prepares the ADTS frame structure in advance to accommodate future codec requirements by adding the metadata block capability. This preliminary action allows the format to evolve and support new codecs without requiring fundamental structural changes, preventing information loss as codecs evolve.
Solution Approach 2:
The patent makes the ADTS frame structure multi-functional by enabling it to carry both traditional header block information and extended metadata block information. This universality allows the same container format to support both legacy and evolving audio codecs, preventing information loss across different codec generations.
Data Source
AI summary
In various embodiments a computer-implemented method for transmitting frames of media content to a client device. The method includes generating a frame for a portion of media content, generating a header for the frame based on the portion of the media content, and generating one or more metadata blocks for the frame corresponding to a media encoding format, where the one or more metadata blocks include metadata incompatible with the header. The method further includes incorporating the header into a header portion of the frame, incorporating the portion of media content and the one or more metadata blocks into a payload portion of the frame, and transmitting the frame to a client device for playback.