AVS1-P2 Bitstream Version Signaling for Decoder Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing AVS1-P2 bitstream decoding systems face challenges in handling different versions of the bitstream, particularly due to non-compliance issues between reference models like AVS1-P2 Rm52j_r1 and AVS1-P2, which can lead to incorrect derivation processes and decoding errors.
Innovation Solution
Inserting decoding version information, such as a decoding version identifier, into the AVS1-P2 bitstream during encoding or transcoding, allowing the video decoder to parse and determine the correct decoding version, ensuring compatibility with either AVS1-P2 Rm52j_r1 or AVS1-P2 specifications, and using a default version when specific information is absent.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single decoder is designed to handle multiple AVS1-P2 bitstream versions, then the decoder's versatility is improved, but the complexity of the decoding logic increases due to version detection and conditional processing
Solution Approach 1:
The patent applies preliminary action by inserting version identification information into the bitstream during encoding. This allows the decoder to detect the bitstream version in advance through parsing the user data sequence, rather than requiring complex conditional logic to handle multiple versions. The version ID is determined before the main decoding process, simplifying the decoder's control flow.
Solution Approach 2:
The patent uses version identification information as an intermediary element between the encoder and decoder. This intermediary data structure (containing version ID and syntax flag) mediates the interaction between different bitstream versions and the decoder, allowing the system to handle multiple versions without requiring the decoder to have complex version-specific logic for each case.
2Manufacturing precision
If version-specific decoding processes are implemented for different AVS1-P2 specifications, then the manufacturing precision of decoding is improved, but the difficulty of detecting and measuring the correct version increases
Solution Approach 1:
The patent applies the color changes principle by using distinct version identification markers (similar to color codes) in the bitstream. Different AVS1-P2 versions are identified by specific version ID values and syntax flag combinations in the user data sequence, making version detection straightforward through pattern recognition rather than complex analysis. The decoder can quickly identify the version by detecting these distinctive markers.
Solution Approach 2:
The version identification information is prepared in advance during encoding and placed in a predetermined location (user data sequence in the bitstream). This preliminary placement of version information allows the decoder to detect the version easily by parsing to this known location, rather than requiring complex version detection algorithms during the decoding process.
3Reliability
If decoding version information is inserted into the bitstream, then the reliability of cross-version compatibility is improved, but the quantity of data in the bitstream increases
Solution Approach 1:
The patent applies the nested doll principle by embedding the version identification information within the existing user data sequence structure of the AVS1-P2 bitstream. Rather than adding a separate data structure, the version ID and syntax flag are nested within the user data that already exists in the bitstream format. This minimizes the additional data volume while ensuring version information is reliably transmitted.
Data Source
AI summary
Aspects of a method and system for signaling and decoding AVS1-P2 bitstreams of different versions are provided. A sequence user data indicating decoding version information such as a decoding version identifier, for example, may inserted into an AVS1-P2 bitstream. The decoding version information may be, for example, AVS1-P2 Rm52j_r1 or AVS1-P2. The AVS1-P2 bitstream may be decoded based on the decoding version information. The sequence user data may be inserted in the AVS1-P2 bitstream during AVS encoding or during AVS1-P2 bitstream transcoding. Upon receiving the AVS1-P2 bitstream, the sequence user data may be detected and extracted to determine the decoding version information. The received encoded AVS1-P2 bitstream may be decoded based on the decoding version information. When no specific decoding version information can be decided, default decoder version information may be used by the video decoder.