US 12,192,529 B2Grant
Picture timing information signaling in coded video
Issue Date:2025-01-07
•20 Claims
•18 Drawing Sheets
Abstract
Examples of video encoding methods and apparatus and video decoding methods and apparatus are described. An example method of video processing includes performing a conversion between a video and a bitstream of the video comprising one or more output layer sets according to a rule, wherein the rule specifies that a supplemental enhancement information (SEI) network abstraction layer (NAL) unit that includes a scalable-nested SEI message carrying picture timing information is not included due to use of a same picture timing in all output layer sets in the bitstream.
Metadata
Assignee
- Bytedance Inc.
Inventor
- Ye-kui Wang
Application Information
Application Number:US 18/078,662
Filing Date:2022-12-09
Priority Date:2020-06-09
Art Unit:2482
Classifications
IPC:
H04N19/70H04N19/136H04N19/169H04N19/184H04N19/30H04N19/433H04N19/46
Patent Drawings (18 sheets)
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of International Patent Application No. PCT/US2021/036487, filed on Jun. 8, 2021, which claims the priority to and benefits of U.S. Provisional Patent Application No. 63/036,808, filed on Jun. 9, 2020. All the aforementioned patent applications are hereby incorporated by reference in their entireties.
TECHNICAL FIELD
[0002] This patent document relates to image and video coding and decoding.
BACKGROUND
[0003] Digital video accounts for the largest bandwidth use on the internet and other digital communication networks. As the number of connected user devices capable of receiving and displaying video increases, it is expected that the bandwidth demand for digital video usage will continue to grow.
SUMMARY
[0004] The present document discloses techniques that can be used by video encoders and decoders to perform video encoding or decoding.
[0005] In one example aspect, a video processing method is disclosed. The method includes performing a conversion between a video and a bitstream of the video, wherein the bitstream includes one or more output layer sets comprising one or more video layers according to a format rule, wherein the format rule specifies that a non-scalable-nested supplemental enhancement information, SEI, message that includes information regarding hypothetical reference decoder, HRD, is applicable to all output layer sets that include same video layers as the bitstream.
[0006] In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video and a bitstream of the video, wherein the bitstream comprises one or more output layer sets comprising one or more video layers according to a format rule, wherein the format rule specifies that a non-scalable-nested hypothetical reference decoder (HRD)-related supplemental enhancement information (SEI) message is omitted responsive to a condition that there does not exist an output layer set that includes a same set of layers as the bitstream.
[0007] In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video and a bitstream of the video, wherein the bitstream comprises one or more output layer sets comprising one or more video layers according to a format rule, wherein the format rule specifies that a value of layer identifier for a supplemental enhancement information (SEI) network abstraction layer (NAL) unit that includes a non-scalable-nested SEI message is not constrained.
[0008] In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video and a bitstream of the video, wherein the bitstream comprises one or more output layer sets comprising one or more video layers according to a format rule, wherein the format rule specifies that a particular payload type value corresponding to subpicture level information is disallowed from a list that includes allowable supplemental enhancement information (SEI) payload type values for non-hypothetical reference decoder (HRD) related supplemental enhancement information (SEI) messages.
[0009] In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video and a bitstream of the video, wherein the bitstream includes one or more output layer sets comprising one or more video layers according to a format rule, wherein the format rule specifies that a non-scalable-nested supplemental enhancement information, SEI, message that includes information irrelevant to hypothetical reference decoder (HRD) is applicable to all layers in the bitstream.
[0010] In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video and a bitstream of the video comprising one or more output layer sets according to a rule, wherein the rule specifies that a supplemental enhancement information (SEI) network abstraction layer (NAL) unit that includes a scalable-nested SEI message carrying picture timing information is not included due to use of a same picture timing in all output layer sets in the bitstream.
[0011] In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video and a bitstream of the video, wherein the bitstream comprises one or more supplemental enhancement information, SEI, network abstraction layer (NAL) units according to a rule, wherein the rule specifies that, responsive to an SEI NAL unit including a non-scalable-nested SEI message of a first payload type, the SEI NAL unit is disallowed to include another SEI message of a second payload type.
[0012] In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video and a bitstream of the video according to a rule, wherein the bitstream comprises one or more supplemental enhancement information, SEI, network abstraction layer (NAL) units according to a rule, wherein the rule specifies that, responsive to an SEI NAL unit including a scalable-nested SEI message of a first payload type, the SEI NAL unit is disallowed to include another SEI message of a second payload type.
[0013] In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video and a bitstream of the video, wherein the bitstream comprises one or more supplemental enhancement information, SEI, network abstraction layer (NAL) units according to a rule, wherein the rule specifies that, responsive to an SEI NAL unit including a SEI message of a first payload type, the SEI NAL unit is disallowed to include another SEI message not equal to the first payload type or a second payload type.
[0014] In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video and a bitstream of the video, wherein the bitstream comprises one or more output layer sets comprising one or more video layers according to a rule, wherein the rule specifies a particular decoding order between a subpicture level information (SLI) supplemental enhancement information (SEI) message and a buffering period (BP) SEI message that apply to a particular output layer set, responsive to a condition that the SLI SEI message and the BP SEI message are included in an access unit.
[0015] In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video and a bitstream of the video according to a rule, wherein the rule specifies that a first syntax field indicating sublayer representation information for which an initial coded picture buffer (CPB) removal delay related syntax elements are present is omitted, responsive to a particular value of a second syntax field indicative of a maximum number of temporal sublayers for which an initial CPB removal delay is indicated in a buffering period supplemental enhancement information (SEI) message.
[0016] In yet another example aspect, a video encoder apparatus is disclosed. The video encoder comprises a processor configured to implement above-described methods.
[0017] In yet another example aspect, a video decoder apparatus is disclosed. The video decoder comprises a processor configured to implement above-described methods.
[0018] In yet another example aspect, a computer readable medium having code stored thereon is disclose. The code embodies one of the methods described herein in the form of processor-executable code.
[0019] These, and other, features are described throughout the present document.
BRIEF DESCRIPTION OF DRAWINGS
[0020] FIG. 1 is a block diagram that illustrates a video coding system in accordance with some implementations of the disclosed technology.
[0021] FIG. 2 is a block diagram of an example hardware platform used for video processing.
[0022] FIG. 3 is a flowchart for an example method of video processing.
[0023] FIG. 4 is a block diagram that illustrates an example video coding system.
[0024] FIG. 5 is a block diagram that illustrates an encoder in accordance with some implementations of the disclosed technology.
[0025] FIG. 6 is a block diagram that illustrates a decoder in accordance with some implementations of the disclosed technology.
[0026] FIGS. 7A to 7E are flowcharts for example methods of video processing based on some implementations of the disclosed technology.
[0027] FIG. 8 is a flowchart for an example method of video processing based on some implementations of the disclosed technology.
[0028] FIGS. 9A to 9C are flowcharts for example methods of video processing based on some implementations of the disclosed technology.
[0029] FIGS. 10A and 10B are flowcharts for example methods of video processing based on some implementations of the disclosed technology.
DETAILED DESCRIPTION
[0030] Section headings are used in the present document for ease of understanding and do not limit the applicability of techniques and embodiments disclosed in each section only to that section. Furthermore, H.266 terminology is used in some description only for ease of understanding and not for limiting scope of the disclosed techniques. As such, the techniques described herein are applicable to other video codec protocols and designs also.
1. Introduction
[0031] This document is related to video coding technologies. Specifically, it is about defining levels and bitstream conformance for a video codec that supports both single-layer video coding and multi-layer video coding. It may be applied to any video coding standard or non-standard video codec that supports single-layer video coding and multi-layer video coding, e.g., Versatile Video Coding (VVC) that is being developed.
2. Abbreviations
-
- [0032] APS Adaptation Parameter Set
- [0033] AU Access Unit
- [0034] AUD Access Unit Delimiter
- [0035] AVC Advanced Video Coding
- [0036] BP Buffering Period
- [0037] CLVS Coded Layer Video Sequence
- [0038] CPB Coded Picture Buffer
- [0039] CRA Clean Random Access
- [0040] CTU Coding Tree Unit
- [0041] CVS Coded Video Sequence
- [0042] DPB Decoded Picture Buffer
- [0043] DPS Decoding Parameter Set
- [0044] DUI Decoding Unit Information
- [0045] EOB End Of Bitstream
- [0046] EOS End Of Sequence
- [0047] GCI General Constraints Information
- [0048] GDR Gradual Decoding Refresh
- [0049] HEVC High Efficiency Video Coding
- [0050] HRD Hypothetical Reference Decoder
- [0051] IDR Instantaneous Decoding Refresh
- [0052] JEM Joint Exploration Model
- [0053] MCTS Motion-Constrained Tile Sets
- [0054] NAL Network Abstraction Layer
- [0055] OLS Output Layer Set
- [0056] PH Picture Header
- [0057] PPS Picture Parameter Set
- [0058] PT Picture Timing
- [0059] PTL Profile, Tier and Level
- [0060] PU Picture Unit
- [0061] RRP Reference Picture Resampling
- [0062] RBSP Raw Byte Sequence Payload
- [0063] SEI Supplemental Enhancement Information
- [0064] SH Slice Header
- [0065] SLI Subpicture Level Information
- [0066] SPS Sequence Parameter Set
- [0067] SVC Scalable Video Coding
- [0068] VCL Video Coding Layer
- [0069] VPS Video Parameter Set
- [0070] VTM VVC Test Model
- [0071] VUI Video Usability Information
- [0072] VVC Versatile Video Coding
3. Initial Discussion
[0073] Video coding standards have evolved primarily through the development of the well-known ITU-T and ISO/IEC standards. The ITU-T produced H.261 and H.263, ISO/IEC produced MPEG-1 and MPEG-4 Visual, and the two organizations jointly produced the H.262/MPEG-2 Video and H.264/MPEG-4 Advanced Video Coding (AVC) and H.265/HEVC standards. Since H.262, the video coding standards are based on the hybrid video coding structure wherein temporal prediction plus transform coding are utilized. To explore the future video coding technologies beyond HEVC, the Joint Video Exploration Team (JVET) was founded by VCEG and MPEG jointly in 2015. Since then, many new methods have been adopted by JVET and put into the reference software named Joint Exploration Model (JEM). The JVET meeting is concurrently held once every quarter, and the new coding standard is targeting at 50% bitrate reduction as compared to HEVC. The new video coding standard was officially named as Versatile Video Coding (VVC) in the April 2018 JVET meeting, and the first version of VVC test model (VTM) was released at that time. As there are continuous effort contributing to VVC standardization, new coding techniques are being adopted to the VVC standard in every JVET meeting. The VVC working draft and test model VTM are then updated after every meeting. The VVC project is now aiming for technical completion (FDIS) at the July 2020 meeting.
3.1. Parameter Sets
[0074] AVC, HEVC, and VVC specify parameter sets. The types of parameter sets include SPS, PPS, APS, and VPS. SPS and PPS are supported in all of AVC, HEVC, and VVC. VPS was introduced since HEVC and is included in both HEVC and VVC. APS was not included in AVC or HEVC but is included in the latest VVC draft text.
[0075] SPS was designed to carry sequence-level header information, and PPS was designed to carry infrequently changing picture-level header information. With SPS and PPS, infrequently changing information need not to be repeated for each sequence or picture, hence redundant signaling of this information can be avoided. Furthermore, the use of SPS and PPS enables out-of-band transmission of the important header information, thus not only avoiding the need for redundant transmissions but also improving error resilience.
[0076] VPS was introduced for carrying sequence-level header information that is common for all layers in multi-layer bitstreams.
[0077] APS was introduced for carrying such picture-level or slice-level information that needs quite some bits to code, can be shared by multiple pictures, and in a sequence there can be quite many different variations.
3.2. Picture Resolution Change within a Sequence
[0078] In AVC and HEVC, the spatial resolution of pictures cannot change unless a new sequence using a new SPS starts, with an IRAP picture. VVC enables picture resolution change within a sequence at a position without encoding an IRAP picture, which is always intra-coded. This feature is sometimes referred to as reference picture resampling (RPR), as the feature needs resampling of a reference picture used for inter prediction when that reference picture has a different resolution than the current picture being decoded.
[0079] The scaling ratio is restricted to be larger than or equal to ½ (2 times downsampling from the reference picture to the current picture), and less than or equal to 8 (8 times upsampling). Three sets of resampling filters with different frequency cutoffs are specified to handle various scaling ratios between a reference picture and the current picture. The three sets of resampling filters are applied respectively for the scaling ratio ranging from ½ to 1/1.75, from 1/1.75 to 1/1.25, and from 1/1.25 to 8. Each set of resampling filters has 16 phases for luma and 32 phases for chroma which is same to the case of motion compensation interpolation filters. Actually the normal MC interpolation process is a special case of the resampling process with scaling ratio ranging from 1/1.25 to 8. The horizontal and vertical scaling ratios are derived based on picture width and height, and the left, right, top and bottom scaling offsets specified for the reference picture and the current picture.
[0080] Other aspects of the VVC design for support of this feature that are different from HEVC include: i) The picture resolution and the corresponding conformance window are signaled in the PPS instead of in the SPS, while in the SPS the maximum picture resolution is signaled. ii) For a single-layer bitstream, each picture store (a slot in the DPB for storage of one decoded picture) occupies the buffer size as required for storing a decoded picture having the maximum picture resolution.
3.3. Scalable Video Coding (SVC) in General and in VVC
[0081] Scalable video coding (SVC, sometimes also just referred to as scalability in video coding) refers to video coding in which a base layer (BL), sometimes referred to as a reference layer (RL), and one or more scalable enhancement layers (ELs) are used. In SVC, the base layer can carry video data with a base level of quality. The one or more enhancement layers can carry additional video data to support, for example, higher spatial, temporal, and/or signal-to-noise (SNR) levels. Enhancement layers may be defined relative to a previously encoded layer. For example, a bottom layer may serve as a BL, while a top layer may serve as an EL. Middle layers may serve as either ELs or RLs, or both. For example, a middle layer (e.g., a layer that is neither the lowest layer nor the highest layer) may be an EL for the layers below the middle layer, such as the base layer or any intervening enhancement layers, and at the same time serve as a RL for one or more enhancement layers above the middle layer. Similarly, in the Multiview or 3D extension of the HEVC standard, there may be multiple views, and information of one view may be utilized to code (e.g., encode or decode) the information of another view (e.g., motion estimation, motion vector prediction and/or other redundancies).
[0082] In SVC, the parameters used by the encoder or the decoder are grouped into parameter sets based on the coding level (e.g., video-level, sequence-level, picture-level, slice level, etc.) in which they may be utilized. For example, parameters that may be utilized by one or more coded video sequences of different layers in the bitstream may be included in a video parameter set (VPS), and parameters that are utilized by one or more pictures in a coded video sequence may be included in a sequence parameter set (SPS). Similarly, parameters that are utilized by one or more slices in a picture may be included in a picture parameter set (PPS), and other parameters that are specific to a single slice may be included in a slice header. Similarly, the indication of which parameter set(s) a particular layer is using at a given time may be provided at various coding levels.
[0083] Thanks to the support of reference picture resampling (RPR) in VVC, support of a bitstream containing multiple layers, e.g., two layers with SD and HD resolutions in VVC can be designed without the need any additional signal-processing-level coding tool, as upsampling needed for spatial scalability support can just use the RPR upsampling filter. Nevertheless, high-level syntax changes (compared to not supporting scalability) are needed for scalability support. Scalability support is specified in VVC version 1. Different from the scalability supports in any earlier video coding standards, including in extensions of AVC and HEVC, the design of VVC scalability has been made friendly to single-layer decoder designs as much as possible. The decoding capability for multi-layer bitstreams are specified in a manner as if there were only a single layer in the bitstream. E.g., the decoding capability, such as DPB size, is specified in a manner that is independent of the number of layers in the bitstream to be decoded. Basically, a decoder designed for single-layer bitstreams does not need much change to be able to decode multi-layer bitstreams. Compared to the designs of multi-layer extensions of AVC and HEVC, the HLS aspects have been significantly simplified at the sacrifice of some flexibilities. For example, an IRAP AU is required to contain a picture for each of the layers present in the CVS.
3.4. SEI Messages and General SEI Semantics and Constraints
[0084] Annex D of VVC specifies syntax and semantics for SEI message payloads for some SEI messages, and specifies the use of the SEI messages and VUI parameters for which the syntax and semantics are specified in ITU-T H.SEI|ISO/JEC 23002-7.
[0085] SEI messages assist in processes related to decoding, display or other purposes. However, SEI messages are not required for constructing the luma or chroma samples by the decoding process. Conforming decoders are not required to process this information for output order conformance. Some SEI messages are required for checking bitstream conformance and for output timing decoder conformance. Other SEI messages are not required for check bitstream conformance.
[0086] In the latest VVC draft text, the general SEI.
[0087] The syntax and semantics of the scalable nesting SEI message in the latest VVC draft text are as follows.
[0088]
D.2.2 General SET Payload Semantics
reserved_payload_extension_data shall not be present in bitstreams conforming to this version of this Specification. However, decoders conforming to this version of this Specification shall ignore the presence and value of reserved_payload_extension_data. When present, the length, in bits, of reserved_payload_extension_data is equal to 8*payloadSize−nEarlierBits−nPayloadZeroBits−1, where nEarlierBits is the number of bits in the sei_payload( ) syntax structure that precede the reserved_payload_extension_data syntax element, and nPayloadZeroBits is the number of payload_bit_equal_to_zero syntax elements at the end of the sei_payload( ) syntax structure.
payload_bit_equal_to_one shall be equal to 1.
payload_bit_equal_to_zero shall be equal to 0.
| D.2.1 General SEI message syntax | |
| Descriptor | |
| sei_payload( payloadType, payloadSize ) { | |
| if( nal_unit_type = = PREFIX_SEI_NUT ) | |
| if( payloadType = = 0) | |
| buffering_period( payloadSize ) | |
| else if( payloadType = = 1) | |
| pic_timing( payloadSize ) | |
| else if( payloadType = = 3 ) | |
| filler_payload( payloadSize ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| else if( payloadType = = 4 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| user_data_registered_itu_t_t35( payloadSize ) | |
| else if( payloadType = = 5 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| user_data_unregistered( payloadSize ) | |
| else if( payloadType = = 19) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| film_grain_characteristics( payloadSize ) | |
| else if( payloadType = = 45 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| frame_packing_arrangement( payloadSize ) | |
| else if( payloadType = = 129 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| parameter_sets_inclusion_indication( payloadSize ) | |
| else if( payloadType = = 130) | |
| decoding_unit_info( payloadSize ) | |
| else if( payloadType = = 133 ) | |
| scalable_nesting( payloadSize ) | |
| else if( payloadType = = 137) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| mastering_display_colour_volume( payloadSize ) | |
| else if( payloadType = = 144 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| content_light_level_info( payloadSize ) | |
| else if( payloadType = = 145 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| dependent_rap_indication( payloadSize ) | |
| else if( payloadType = = 147) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| alternative_transfer_characteristics( payloadSize ) | |
| else if( payloadType = = 148 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| ambient_viewing_environment( payloadSize ) | |
| else if( payloadType = = 149 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| content_colour_volume( payloadSize ) | |
| else if( payloadType = = 150 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| equirectangular_projection( payloadSize ) | |
| else if( payloadType = = 153 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| generalized_cubemap_projection( payloadSize ) | |
| else if( payloadType = = 154 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| sphere_rotation( payloadSize ) | |
| else if( payloadType = = 155 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| regionwise_packing( payloadSize ) | |
| else if( payloadType = = 156 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| omni_viewport( payloadSize ) | |
| else if( payloadType == 168 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| frame_field_info( payloadSize ) | |
| else if( payloadType = = 203 ) | |
| subpic_level_info( payloadSize ) | |
| else if( payloadType = = 204 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| sample_aspect_ratio_info( payloadSize ) | |
| else /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| reserved_message( payloadSize ) | |
| else /* nal_unit_type == SUFFIX SEI NUT */ | |
| if( payloadType = = 3 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| filler_payload( payloadSize ) | |
| if( payloadType == 132 ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| decoded_picture_hash( payloadSize ) | |
| else if( payloadType = = 133 ) | |
| scalable_nesting( payloadSize ) | |
| else /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */ | |
| reserved_message( payloadSize ) | |
| if( more_data_in_payload( ) ) { | |
| if( payload_extension_present( ) ) | |
| reserved_payload_extension_data | u(v) |
| payload_bit_equal_to_one /* equal to 1 */ | f(1) |
| while( !byte_aligned( ) ) | |
| payload_bit_equal_to_zero /* equal to 0 */ | f(1) |
| } | |
| } | |
D.2.2 General SET Payload Semantics
reserved_payload_extension_data shall not be present in bitstreams conforming to this version of this Specification. However, decoders conforming to this version of this Specification shall ignore the presence and value of reserved_payload_extension_data. When present, the length, in bits, of reserved_payload_extension_data is equal to 8*payloadSize−nEarlierBits−nPayloadZeroBits−1, where nEarlierBits is the number of bits in the sei_payload( ) syntax structure that precede the reserved_payload_extension_data syntax element, and nPayloadZeroBits is the number of payload_bit_equal_to_zero syntax elements at the end of the sei_payload( ) syntax structure.
payload_bit_equal_to_one shall be equal to 1.
payload_bit_equal_to_zero shall be equal to 0.
-
- [0089] NOTE 1—SEI messages with the same value of payloadType are conceptually the same SEI message regardless of whether they are contained in prefix or suffix SEI NAL units.
- [0090] NOTE 2—For SEI messages with payloadType in the mange of 0 to 47, inclusive, that are specified in this Specification, the payloadType values are aligned with similar SEI messages specified in Rec. ITU-T H.2641 ISO/IEC 14496-10.
The semantics and persistence scope for each SEI message are specified in the semantics specification for each particular SEI message. - [0091] NOTE 3—Persistence information for SEI messages is informatively summarized in Table D.1.
[0092]
The list VclAssociatedSeiList is set to consist of the payloadType values 3, 19, 45, 129, 132, 137, 144, 145, 147 to 150, inclusive, 153 to 156, inclusive, 168, 203, and 204.
The list PicUnitRepConSeiList is set to consist of the payloadType values 0, 1, 19, 45, 129, 132, 133, 137, 147 to 150, inclusive, 153 to 156, inclusive, 168, 203, and 204.
| TABLE D.1 | ||
|---|---|---|
| Persistence scope of SEI messages (informative) | ||
| SEI message | Persistence scope | |
| Buffering period | The remainder of the bitstream | |
| Picture timing | The AU containing the SEI message | |
| DU information | The AU containing the SEI message | |
| Scalable nesting | Depending on the scalable-nested SEI messages. | |
| Each scalable-nested SEI message has the | ||
| same persistence scope as if the SEI | ||
| message was not scalable-nested | ||
| Subpicture level | The CLVS containing the SEI message | |
| information | ||
The list VclAssociatedSeiList is set to consist of the payloadType values 3, 19, 45, 129, 132, 137, 144, 145, 147 to 150, inclusive, 153 to 156, inclusive, 168, 203, and 204.
The list PicUnitRepConSeiList is set to consist of the payloadType values 0, 1, 19, 45, 129, 132, 133, 137, 147 to 150, inclusive, 153 to 156, inclusive, 168, 203, and 204.
-
- [0093] NOTE 4—VclAssociatedSeiList consists of the payloadType values of the SEI messages that, when non-scalable-nested and contained in an SEI NAL unit, infer constraints on the NAL unit header of the SEI NAL unit on the basis of the NAL unit header of the associated VCL NAL unit. PicUnitRepConSeiList consists of the payloadType values of the SEI messages that are subject to the restriction on 4 repetitions per PU.
It is a requirement of bitstream conformance that the following restrictions apply on containing of SEI messages in SEI NAL units: - [0094] When an SEI NAL unit contains a non-scalable-nested BP SEI message, a non-scalable-nested PT SEI message, or a non-scalable-nested DUI SEI message, the SEI NAL unit shall not contain any other SEI message with payloadType not equal to 0 (BP), 1 (PT), or 130 (DUI).
- [0095] When an SEI NAL unit contains a scalable-nested BP SEI message, a scalable-nested PT SEI message, or a scalable-nested DUI SEI message, the SEI NAL unit shall not contain any other SEI message with payloadType not equal to 0 (BP), 1 (PT), 130 (DUI) or 133 (scalable nesting).
The following applies on the applicable OLSs or layers of non-scalable-nested SEI messages: - [0096] For a non-scalable-nested SEI message, when payloadType is equal to 0 (BP), 1 (PT), or 130 (DUI), the non-scalable-nested SEI message applies only to the 0-th OLS.
- [0097] For a non-scalable-nested SEI message, when payloadType is equal to any value among VclAssociatedSeiList, the non-scalable-nested SEI message applies only to the layer for which the VCL NAL units have nuh_layer_id equal to the nuh_layer_id of the SEI NAL unit containing the SEI message.
It is a requirement of bitstream conformance that the following restrictions apply on the value of nuh_layer_id of SEI NAL units: - [0098] When a non-scalable-nested SEI message has payloadType equal to 0 (BP), 1 (PT), or 130 (DUI), the SEI NAL unit containing the non-scalable-nested SEI message shall have nuh_layer_id equal to vps_layer_id[0].
- [0099] When a non-scalable-nested SEI message has payloadType equal to any value among VclAssociatedSeiList, the SEI NAL unit containing the non-scalable-nested SEI message shall have nuh_layer_id equal to the value of nuh_layer_id of the VCL NAL unit associated with the SEI NAL unit.
- [0100] An SEI NAL unit containing a scalable nesting SEI message shall have nuh_layer_id equal to the lowest value of nuh_layer_id of all layers to which the scalable-nested SEI messages apply (when sn_ols_flag of the scalable nesting SEI message is equal to 0) or the lowest value of nuh_layer_id of all layers in the OLSs to which the scalable-nested SEI message apply (when sn_ols_flag of the scalable nesting SEI message is equal to 1).
It is a requirement of bitstream conformance that the following restrictions apply on repetition of SEI messages: - [0101] For each of the payloadType values included in PicUnitRepConSeiList, there shall be less than or equal to 4 identical sei_payload( ) syntax structures within a PU.
- [0102] There shall be less than or equal to 4 identical sei_payload( ) syntax structures with payloadType equal to 130 within a DU.
The following applies on the order of BP, PT, and DUI SEI messages: - [0103] When a BP SEI message and a PT SEI message that apply to a particular OP are present within an AU, the BP SEI messages shall precede the PT SEI message in decoding order.
- [0104] When a BP SEI message and a DUI SEI message that apply to a particular OP are present within an AU, the BP SEI messages shall precede the DUI SEI message in decoding order.
- [0105] When a PT SEI message and a DUI SEI message that apply to a particular OP are present within an AU, the PT SEI messages shall precede the DUI SEI message in decoding order.
- [0093] NOTE 4—VclAssociatedSeiList consists of the payloadType values of the SEI messages that, when non-scalable-nested and contained in an SEI NAL unit, infer constraints on the NAL unit header of the SEI NAL unit on the basis of the NAL unit header of the associated VCL NAL unit. PicUnitRepConSeiList consists of the payloadType values of the SEI messages that are subject to the restriction on 4 repetitions per PU.
4. Technical Problems Solved by Disclosed Technical Solutions
[0106] The existing general SEI payload semantics, including the general SEI constraints, has the following problems:
-
- [0107] 1) Non-scalable-nested HRD-related SEI messages should be specified to apply to the OLSs that include the same set of layers as the entire bitstream (instead of apply only to the 0th OLS).
- [0108] 2) An entire bitstream may include multiple layers while there is no OLS specified that includes all the layer. In this case, there cannot be any non-scalable-nested HRD-related SEI message, as they would apply to the OLSs that include the same set of layers as the entire bitstream.
- [0109] 3) It is currently specified that a non-scalable-nested non-HRD-related SEI message only applies to the layer with nuh_layer_id equal to that of the SEI NAL unit. However, to be consistent with non-scalable-nested HRD-related SEI messages, it should be specified that non-scalable-nested non-HRD-related SEI messages apply to all layers in the entire bitstream.
- [0110] 4) It is currently specified that the value of nuh_layer_id for an SEI NAL unit containing non-scalable-nested HRD-related SEI messages shall be equal to vps_layer_id[0] and the value of nuh_layer_id for an SEI NAL unit containing non-scalable-nested non-HRD-related SEI messages shall be equal to the nuh_layer_id of the VCL NAL unit associated with the SEI NAL unit. However, as non-scalable-nested SEI messages apply to the entire bitstream, these constraints on the value of nuh_layer_id should be removed, such that the value of nuh_layer_id for SEI NAL units containing non-scalable-nested SEI messages is unconstrained, same as for the nuh_layer_id for DCI, VPS, AUD, and EOS NAL units.
- [0111] 5) The list variable VclAssociatedSeiList currently consists of the SEI payloadType values for non-HRD-related SEI messages. However, the value 203, for the SLI SEI message, is also an HRD-related SEI message. Therefore, the payloadType value 203 (SLI) should be removed from the list.
- [0112] 6) There lacks a constraint such that when general_same_pic_timing_in_all_ols_flag is equal to 1, there shall be no SEI NAL unit that contain a scalable-nested SEI message with payloadType equal to 1 (PT). This is because when general_same_pic_timing_in_all_ols_flag is equal to 1, there is no need to have PT SEI messages contained in scalable nesting SEI messages.
- [0113] 7) There lacks a constraint such that when an SEI NAL unit contains a non-scalable-nested SEI message with payloadType equal to 0 (BP), 1 (PT), 130 (DUI), or 203 (SLI), the SEI NAL unit shall not contain any other SEI message with payloadType not equal to 0, 1, 130, or 203. Only with this, removal of these four HRD-related SEI messages from the output bitstream during a sub-bitstream extraction process can be performed by simply removing SEI NAL units containing one or more of these SEI messages.
- [0114] 8) There lacks a constraint such that when an SEI NAL unit contains a scalable-nested SEI message with payloadType equal to 0 (BP), 1 (PT), 130 (DUI), or 203 (SLI), the SEI NAL unit shall not contain any other SEI message with payloadType not equal to 0, 1, 130, 203, or 133 (scalable nesting). Only with this, it is possible to set the value of sn_ols_flag of scalable nesting SEI messages for scalable-nested HRD-related and non-HRD-related SEI messages without a problem.
- [0115] 9) There lacks a constraint such that when an SEI NAL unit contains an SEI message with payloadType equal to 3 (filler payload), the SEI NAL unit shall not contain any other SEI message with payloadType not equal to 3. Only with this, removal of filler payload SEI messages from the output bitstream during a sub-bitstream extraction process can be performed by simply removing SEI NAL units containing one or more filler payload SEI messages.
- [0116] 10) There lacks a constraint such that when an SLI SEI message and a BP SEI message that apply to a particular OLS are present within an AU, the SLI SEI messages shall precede the BP SEI message in decoding order. This is needed because an SLI SEI message provides sequence level information like VPSs and SPSs, which also precede BP SEI messages, when present within the same AU as the BP SEI messages.
- [0117] 11) In the BP SEI message, the bp_sublayer_initial_cpb_removal_delay_present_flag is signalled even when bp_max_sublayers_minus1 is equal to 0. However, when bp_max_sublayers_minus1 is equal to 0, the value of bp_sublayer_initial_cpb_removal_delay_present_flag is known to be 0.
5. Examples of Solutions and Embodiments
[0118] To solve the above problems, and others, methods as summarized below are disclosed. The solution items should be considered as examples to explain the general concepts and should not be interpreted in a narrow way. Furthermore, these items can be applied individually or combined in any manner.
-
- [0119] 1) To solve the 1st problem, specify that non-scalable-nested HRD-related SEI messages apply to the OLSs that include the same set of layers as the entire bitstream (instead of apply only to the 0th OLS).
- [0120] a. In one example, HRD-related SEI messages refer to SEI messages with payloadType equal to 0 (BP), 1 (PT), 130 (DUI), or 203 (SLI).
- [0121] 2) To solve the 2nd problem, add a constraint such that when there is no OLS that includes the set of layers same as the entire bitstream, there shall be no non-scalable-nested HRD-related SEI messages.
- [0122] a. In one example, HRD-related SEI messages refer to SEI messages with payloadType equal to 0 (BP), 1 (PT), 130 (DUI), or 203 (SLI).
- [0123] 3) To solve the 3rd problem, specify that non-scalable-nested non-HRD-related SEI messages are applicable to all layers in the entire bitstream, to be consistent with non-scalable-nested HRD-related SEI messages.
- [0124] a. In one example, non-HRD-related SEI messages refer to SEI messages with payloadType not equal to 0 (BP), 1 (PT), 130 (DUI), or 203 (SLI).
- [0125] 4) To solve the 4th problem, remove the constraints on the value of nuh_layer_id for SEI NAL units containing non-scalable-nested SEI messages, such that the value of nuh_layer_id for SEI NAL units containing non-scalable-nested SEI messages is unconstrained, same as for the nuh_layer_id for DCI, VPS, AUD, and EOS NAL units.
- [0126] 5) To solve the 5th problem, rename VclAssociatedSeiList to NestingForLayersSeiList, and remove payloadType value 203 (SLI) from the list.
- [0127] 6) To solve the 6th problem, add a constraint such that when general_same_pic_timing_in_all_ols_flag is equal to 1, there shall be no SEI NAL unit that contain a scalable-nested SEI message with payloadType equal to 1 (PT).
- [0128] a. In one example, additionally, it is specified that when general_same_pic_timing_in_all_ols_flag is equal to 1, non-scalable-nested PT SEI messages apply to all OLSs as well as to the subpicture sequences that can be extracted from the bitstreams of the OLSs.
- [0129] b. In one example, alternatively, add a constraint such that when general_same_pic_timing_in_all_ols_flag is equal to 1, there shall be no SEI NAL unit that contains a scalable-nested SEI message with payloadType equal to 1 (PT) for which sn_subpic_flag is equal to 0.
- [0130] 7) To solve the 7th problem, it is specified that when an SEI NAL unit contains a non-scalable-nested SEI message with payloadType equal to 0 (BP), 1 (PT), 130 (DUI), or 203 (SLI), the SEI NAL unit shall not contain any other SEI message with payloadType not equal to 0, 1, 130, or 203.
- [0131] 8) To solve the 8th problem, it is specified that when an SEI NAL unit contains a scalable-nested SEI message with payloadType equal to 0 (BP), 1 (PT), 130 (DUI), or 203 (SLI), the SEI NAL unit shall not contain any other SEI message with payloadType not equal to 0, 1, 130, 203, or 133 (scalable nesting).
- [0132] 9) To solve the 9th problem, add a constraint such that when an SEI NAL unit contains an SEI message with payloadType equal to 3 (filler payload), the SEI NAL unit shall not contain any other SEI message with payloadType not equal to 3.
- [0133] a. In one example, additionally, it is specified that filler data SEI messages shall not be scalable-nested, i.e., shall not be contained in a scalable nesting SEI message.
- [0134] b. In one example, alternatively, add a constraint such that when an SEI NAL unit contains an SEI message with payloadType equal to 3 (filler payload), the SEI NAL unit shall not contain any other SEI message with payloadType not equal to 3 or 133 (scalable nesting).
- [0135] 10) To solve the 10th problem, add a constraint such that when an SLI SEI message and a BP SEI message that apply to a particular OLS are present within an AU, the SLI SEI messages shall precede the BP SEI message in decoding order.
- [0136] 11) To solve the 11th problem, it is specified that, when bp_max_sublayers_minus1 is equal to 0, bp_sublayer_initial_cpb_removal_delay_present_flag is skipped (i.e., not signalled in the BP SEI message).
- [0137] a. In one example, additionally, when bp_max_sublayers_minus1 is equal to 0, the value of bp_sublayer_initial_cpb_removal_delay_present_flag is inferred to be equal to 0.
- [0119] 1) To solve the 1st problem, specify that non-scalable-nested HRD-related SEI messages apply to the OLSs that include the same set of layers as the entire bitstream (instead of apply only to the 0th OLS).
6. Embodiments
Below are some example embodiments for some of the invention aspects summarized above in this Section, which can be applied to the VVC specification. The changed texts are based on the latest VVC text in JVET-S0152-v5. Most relevant parts that have been added or modified are bold and Italic, and some of the deleted parts are marked with double brackets (e.g., [[a]] denotes the deletion of the character “a”).
6.1. Embodiment 1
This embodiment is for items 1 to 11 and some of their sub-items.
. . .
D.2.2 General SEI Payload Semantics
The list [[VclAssociated]]NestingForLayersSeiList is set to consist of the payloadType values 3, 19, 45, 129, 132, 137, 144, 145, 147 to 150, inclusive, 153 to 156, inclusive, 168, [[203,]] and 204.
The list PicUnitRepConSeiList is set to consist of the payloadType values 0, 1, 19, 45, 129, 132, 133, 137, 147 to 150, inclusive, 153 to 156, inclusive, 168, 203, and 204.
-
- [0138] NOTE 4—[[VclAssociatedSeiList consists of the payloadType values of the SEI messages that, when non-scalable-nested and contained in an SEI NAL unit, infer constraints on the NAL unit header of the SEI NAL unit on the basis of the NAL unit header of the associated VCL NAL unit.]] NestingForLayersSeiList consists of the payloadType values of the non-HRD-related SEI messages, for which, when scalable-nested, the value of sn_ols_flag of the containing scalable nesting SEI message shall be equal to 1. PicUnitRepConSeiList consists of the payloadType values of the SEI messages that are subject to the restriction on 4 repetitions per PU.
It is a requirement of bitstream conformance that the following restrictions apply on containing of SEI messages in SEI NAL units: - [0139] When general_same_pic_timing_in_all_ols_flag is equal to 1, there shall be no SEI NAL unit that contain a scalable-nested SEI message with payloadType equal to 1 (PT).
- [0140] When an SEI NAL unit contains a non-scalable-nested SEI message with payloadType equal to 0 (BP), 1 (PT), [[or]] 130 (DUI), or 203 (SLI), the SEI NAL unit shall not contain any other SEI message with payloadType not equal to 0, 1, [[or]] 130, or 203.
- [0141] When an SEI NAL unit contains a scalable-nested SEI message with payloadType equal to 0 (BP), 1 (PT), [[or]]130 (DUI), or 203 (SLI), the SEI NAL unit shall not contain any other SEI message with payloadType not equal to 0, 1, 130, 203, or 133 (scalable nesting).
- [0142] When an SEI NAL unit contains an SEI message with payloadType equal to 3 (filler payload), the SEI NAL unit shall not contain any other SEI message with payloadType not equal to 3.
The following applies on the applicable OLSs or layers of non-scalable-nested SEI messages: - [0143] For a non-scalable-nested SEI message, when payloadType is equal to 0 (BP), 1 (PT), [[or]] 130 (DUI), or 203 (SLI), the non-scalable-nested SEI message applies to the OLSs, when present, that include the same set of layers as in the entire bitstream [[only to the 0-th OLS]]. When there is no OLS that includes the same set of layers as the entire bitstream, there shall be no non-scalable-nested SEI message with payloadType equal to 0 (BP), 1 (PT), 130 (DUI), or 203 (SLI).
- [0144] For a non-scalable-nested SEI message, when payloadType is equal to any value among [[VclAssociated]]NestingForLayersSeiList, the non-scalable-nested SEI message applies to all layers in the entire bitstream [[only to the layer for which the VCL NAL units have nuh_layer_id equal to the nuh_layer_id of the SEI NAL unit containing the SEI message]].
It is a requirement of bitstream conformance that the following restrictions apply on the value of nuh_layer_id of SEI NAL units: - [0145] [[When a non-scalable-nested SEI message has payloadType equal to 0 (BP), 1 (PT), or 130 (DUI), the SEI NAL unit containing the non-scalable-nested SEI message shall have nuh_layer_id equal to vps_layer_id[0].
- [0146] When a non-scalable-nested SEI message has payloadType equal to any value among VclAssociatedSeiList, the SEI NAL unit containing the non-scalable-nested SEI message shall have nuh_layer_id equal to the value of nuh_layer_id of the VCL NAL unit associated with the SEI NAL unit.]]
- [0147] An SEI NAL unit containing a scalable nesting SEI message shall have nuh_layer_id equal to the lowest value of nuh_layer_id of all layers to which the scalable-nested SEI messages apply (when sn_ols_flag of the scalable nesting SEI message is equal to 0) or the lowest value of nuh_layer_id of all layers in the OLSs to which the scalable-nested SEI message apply (when sn_ols_flag of the scalable nesting SEI message is equal to 1).
- [0148] NOTE 4—Same as for DCI, VPS, AUD, and EOB NAL units, the value of nuh_layer_id for SEI NAL units that do not contain a scalable nesting SEI message is not constrained.
It is a requirement of bitstream conformance that the following restrictions apply on repetition of SEI messages:
- [0148] NOTE 4—Same as for DCI, VPS, AUD, and EOB NAL units, the value of nuh_layer_id for SEI NAL units that do not contain a scalable nesting SEI message is not constrained.
- [0149] For each of the payloadType values included in PicUnitRepConSeiList, there shall be less than or equal to 4 identical sei_payload( ) syntax structures within a PU.
- [0150] There shall be less than or equal to 4 identical sei_payload( ) syntax structures with payloadType equal to 130 within a DU.
The following applies on the order of SLI, BP, PT, and DUI SEI messages: - [0151] When an SLI SEI message and a BP SEI message that apply to a particular OLS are present within an AU, the SLI SEI messages shall precede the BP SEI message in decoding order.
- [0152] When a BP SEI message and a PT SEI message that apply to a particular [[OP]]OLS are present within an AU, the BP SEI messages shall precede the PT SEI message in decoding order.
- [0153] When a BP SEI message and a DUI SEI message that apply to a particular [[OP]]OLS are present within an AU, the BP SEI messages shall precede the DUI SEI message in decoding order.
- [0154] When a PT SEI message and a DUI SEI message that apply to a particular [[OP]]OLS are present within an AU, the PT SEI messages shall precede the DUI SEI message in decoding order.
- [0138] NOTE 4—[[VclAssociatedSeiList consists of the payloadType values of the SEI messages that, when non-scalable-nested and contained in an SEI NAL unit, infer constraints on the NAL unit header of the SEI NAL unit on the basis of the NAL unit header of the associated VCL NAL unit.]] NestingForLayersSeiList consists of the payloadType values of the non-HRD-related SEI messages, for which, when scalable-nested, the value of sn_ols_flag of the containing scalable nesting SEI message shall be equal to 1. PicUnitRepConSeiList consists of the payloadType values of the SEI messages that are subject to the restriction on 4 repetitions per PU.
[0155]
D.3.2 Buffering period SEI message semantics
. . .
bp_sublayer_initial_cpb_removal_delay_present_flag equal to 1 specifies that initial CPB removal delay related syntax elements are present for sublayer representation(s) in the range of 0 to bp_max_sublayers_minus1, inclusive. bp_sublayer_initial_cpb_removal_delay_present_flag equal to 0 specifies that initial CPB removal delay related syntax elements are present for the bp_max_sublayers_minus1-th sublayer representation. When not present, the value of bp_sublayer_initial_cpb_removal_delay_present_flag is inferred to be equal to 0.
. . .
| D.3.1 Buffering period SEI message syntax | |
| Descriptor | |
| buffering_period( payloadSize ) { | |
| ... | |
| if( bp_max_sublayers_minus1 > 0 ) | |
| bp_sublayer_initial_cpb_removal_delay_present_flag | u(1) |
| ... | |
| } | |
D.3.2 Buffering period SEI message semantics
. . .
bp_sublayer_initial_cpb_removal_delay_present_flag equal to 1 specifies that initial CPB removal delay related syntax elements are present for sublayer representation(s) in the range of 0 to bp_max_sublayers_minus1, inclusive. bp_sublayer_initial_cpb_removal_delay_present_flag equal to 0 specifies that initial CPB removal delay related syntax elements are present for the bp_max_sublayers_minus1-th sublayer representation. When not present, the value of bp_sublayer_initial_cpb_removal_delay_present_flag is inferred to be equal to 0.
. . .
[0156] FIG. 1 is a block diagram showing an example video processing system 1900 in which various techniques disclosed herein may be implemented. Various implementations may include some or all of the components of the system 1900. The system 1900 may include input 1902 for receiving video content. The video content may be received in a raw or uncompressed format, e.g., 8 or 10 bit multi-component pixel values, or may be in a compressed or encoded format. The input 1902 may represent a network interface, a peripheral bus interface, or a storage interface. Examples of network interface include wired interfaces such as Ethernet, passive optical network (PON), etc. and wireless interfaces such as Wi-Fi or cellular interfaces.
[0157] The system 1900 may include a coding component 1904 that may implement the various coding or encoding methods described in the present document. The coding component 1904 may reduce the average bitrate of video from the input 1902 to the output of the coding component 1904 to produce a coded representation of the video. The coding techniques are therefore sometimes called video compression or video transcoding techniques. The output of the coding component 1904 may be either stored, or transmitted via a communication connected, as represented by the component 1906. The stored or communicated bitstream (or coded) representation of the video received at the input 1902 may be used by the component 1908 for generating pixel values or displayable video that is sent to a display interface 1910. The process of generating user-viewable video from the bitstream representation is sometimes called video decompression. Furthermore, while certain video processing operations are referred to as “coding” operations or tools, it will be appreciated that the coding tools or operations are used at an encoder and corresponding decoding tools or operations that reverse the results of the coding will be performed by a decoder.
[0158] Examples of a peripheral bus interface or a display interface may include universal serial bus (USB) or high definition multimedia interface (HDMI) or Displayport, and so on. Examples of storage interfaces include SATA (serial advanced technology attachment), PCI, IDE interface, and the like. The techniques described in the present document may be embodied in various electronic devices such as mobile phones, laptops, smartphones or other devices that are capable of performing digital data processing and/or video display.
[0159] FIG. 2 is a block diagram of a video processing apparatus 3600. The apparatus 3600 may be used to implement one or more of the methods described herein. The apparatus 3600 may be embodied in a smartphone, tablet, computer, Internet of Things (IoT) receiver, and so on. The apparatus 3600 may include one or more processors 3602, one or more memories 3604 and video processing hardware 3606. The processor(s) 3602 may be configured to implement one or more methods described in the present document. The memory (memories) 3604 may be used for storing data and code used for implementing the methods and techniques described herein. The video processing hardware 3606 may be used to implement, in hardware circuitry, some techniques described in the present document.
[0160] FIG. 4 is a block diagram that illustrates an example video coding system 100 that may utilize the techniques of this disclosure.
[0161] As shown in FIG. 4 , video coding system 100 may include a source device 110 and a destination device 120. Source device 110 generates encoded video data which may be referred to as a video encoding device. Destination device 120 may decode the encoded video data generated by source device 110 which may be referred to as a video decoding device.
[0162] Source device 110 may include a video source 112, a video encoder 114, and an input/output (I/O) interface 116.
[0163] Video source 112 may include a source such as a video capture device, an interface to receive video data from a video content provider, and/or a computer graphics system for generating video data, or a combination of such sources. The video data may comprise one or more pictures. Video encoder 114 encodes the video data from video source 112 to generate a bitstream. The bitstream may include a sequence of bits that form a coded representation of the video data. The bitstream may include coded pictures and associated data. The coded picture is a coded representation of a picture. The associated data may include sequence parameter sets, picture parameter sets, and other syntax structures. I/O interface 116 may include a modulator/demodulator (modem) and/or a transmitter. The encoded video data may be transmitted directly to destination device 120 via I/O interface 116 through network 130a. The encoded video data may also be stored onto a storage medium/server 130b for access by destination device 120.
[0164] Destination device 120 may include an I/O interface 126, a video decoder 124, and a display device 122.
[0165] I/O interface 126 may include a receiver and/or a modem. I/O interface 126 may acquire encoded video data from the source device 110 or the storage medium/server 130b. Video decoder 124 may decode the encoded video data. Display device 122 may display the decoded video data to a user. Display device 122 may be integrated with the destination device 120, or may be external to destination device 120 which be configured to interface with an external display device.
[0166] Video encoder 114 and video decoder 124 may operate according to a video compression standard, such as the High Efficiency Video Coding (HEVC) standard, Versatile Video Coding (VVC) standard and other current and/or further standards.
[0167] FIG. 5 is a block diagram illustrating an example of video encoder 200, which may be video encoder 114 in the system 100 illustrated in FIG. 4 .
[0168] Video encoder 200 may be configured to perform any or all of the techniques of this disclosure. In the example of FIG. 5 , video encoder 200 includes a plurality of functional components. The techniques described in this disclosure may be shared among the various components of video encoder 200. In some examples, a processor may be configured to perform any or all of the techniques described in this disclosure.
[0169] The functional components of video encoder 200 may include a partition unit 201, a predication unit 202 which may include a mode select unit 203, a motion estimation unit 204, a motion compensation unit 205 and an intra prediction unit 206, a residual generation unit 207, a transform unit 208, a quantization unit 209, an inverse quantization unit 210, an inverse transform unit 211, a reconstruction unit 212, a buffer 213, and an entropy encoding unit 214.
[0170] In other examples, video encoder 200 may include more, fewer, or different functional components. In an example, predication unit 202 may include an intra block copy (IBC) unit. The IBC unit may perform predication in an IBC mode in which at least one reference picture is a picture where the current video block is located.
[0171] Furthermore, some components, such as motion estimation unit 204 and motion compensation unit 205 may be highly integrated, but are represented in the example of FIG. 5 separately for purposes of explanation.
[0172] Partition unit 201 may partition a picture into one or more video blocks. Video encoder 200 and video decoder 300 may support various video block sizes.
[0173] Mode select unit 203 may select one of the coding modes, intra or inter, e.g., based on error results, and provide the resulting intra- or inter-coded block to a residual generation unit 207 to generate residual block data and to a reconstruction unit 212 to reconstruct the encoded block for use as a reference picture. In some example, Mode select unit 203 may select a combination of intra and inter predication (CIIP) mode in which the predication is based on an inter predication signal and an intra predication signal. Mode select unit 203 may also select a resolution for a motion vector (e.g., a sub-pixel or integer pixel precision) for the block in the case of inter-predication.
[0174] To perform inter prediction on a current video block, motion estimation unit 204 may generate motion information for the current video block by comparing one or more reference frames from buffer 213 to the current video block. Motion compensation unit 205 may determine a predicted video block for the current video block based on the motion information and decoded samples of pictures from buffer 213 other than the picture associated with the current video block.
[0175] Motion estimation unit 204 and motion compensation unit 205 may perform different operations for a current video block, for example, depending on whether the current video block is in an I slice, a P slice, or a B slice.
[0176] In some examples, motion estimation unit 204 may perform uni-directional prediction for the current video block, and motion estimation unit 204 may search reference pictures of list 0 or list 1 for a reference video block for the current video block. Motion estimation unit 204 may then generate a reference index that indicates the reference picture in list 0 or list 1 that contains the reference video block and a motion vector that indicates a spatial displacement between the current video block and the reference video block. Motion estimation unit 204 may output the reference index, a prediction direction indicator, and the motion vector as the motion information of the current video block. Motion compensation unit 205 may generate the predicted video block of the current block based on the reference video block indicated by the motion information of the current video block.
[0177] In other examples, motion estimation unit 204 may perform bi-directional prediction for the current video block, motion estimation unit 204 may search the reference pictures in list 0 for a reference video block for the current video block and may also search the reference pictures in list 1 for another reference video block for the current video block. Motion estimation unit 204 may then generate reference indexes that indicate the reference pictures in list 0 and list 1 containing the reference video blocks and motion vectors that indicate spatial displacements between the reference video blocks and the current video block. Motion estimation unit 204 may output the reference indexes and the motion vectors of the current video block as the motion information of the current video block. Motion compensation unit 205 may generate the predicted video block of the current video block based on the reference video blocks indicated by the motion information of the current video block.
[0178] In some examples, motion estimation unit 204 may output a full set of motion information for decoding processing of a decoder.
[0179] In some examples, motion estimation unit 204 may do not output a full set of motion information for the current video. Rather, motion estimation unit 204 may signal the motion information of the current video block with reference to the motion information of another video block. For example, motion estimation unit 204 may determine that the motion information of the current video block is sufficiently similar to the motion information of a neighboring video block.
[0180] In one example, motion estimation unit 204 may indicate, in a syntax structure associated with the current video block, a value that indicates to the video decoder 300 that the current video block has the same motion information as the another video block.
[0181] In another example, motion estimation unit 204 may identify, in a syntax structure associated with the current video block, another video block and a motion vector difference (MVD). The motion vector difference indicates a difference between the motion vector of the current video block and the motion vector of the indicated video block. The video decoder 300 may use the motion vector of the indicated video block and the motion vector difference to determine the motion vector of the current video block.
[0182] As discussed above, video encoder 200 may predictively signal the motion vector. Two examples of predictive signaling techniques that may be implemented by video encoder 200 include advanced motion vector predication (AMVP) and merge mode signaling.
[0183] Intra prediction unit 206 may perform intra prediction on the current video block. When intra prediction unit 206 performs intra prediction on the current video block, intra prediction unit 206 may generate prediction data for the current video block based on decoded samples of other video blocks in the same picture. The prediction data for the current video block may include a predicted video block and various syntax elements.
[0184] Residual generation unit 207 may generate residual data for the current video block by subtracting (e.g., indicated by the minus sign) the predicted video block(s) of the current video block from the current video block. The residual data of the current video block may include residual video blocks that correspond to different sample components of the samples in the current video block.
[0185] In other examples, there may be no residual data for the current video block for the current video block, for example in a skip mode, and residual generation unit 207 may not perform the subtracting operation.
[0186] Transform processing unit 208 may generate one or more transform coefficient video blocks for the current video block by applying one or more transforms to a residual video block associated with the current video block.
[0187] After transform processing unit 208 generates a transform coefficient video block associated with the current video block, quantization unit 209 may quantize the transform coefficient video block associated with the current video block based on one or more quantization parameter (QP) values associated with the current video block.
[0188] Inverse quantization unit 210 and inverse transform unit 211 may apply inverse quantization and inverse transforms to the transform coefficient video block, respectively, to reconstruct a residual video block from the transform coefficient video block. Reconstruction unit 212 may add the reconstructed residual video block to corresponding samples from one or more predicted video blocks generated by the predication unit 202 to produce a reconstructed video block associated with the current block for storage in the buffer 213.
[0189] After reconstruction unit 212 reconstructs the video block, loop filtering operation may be performed reduce video blocking artifacts in the video block.
[0190] Entropy encoding unit 214 may receive data from other functional components of the video encoder 200. When entropy encoding unit 214 receives the data, entropy encoding unit 214 may perform one or more entropy encoding operations to generate entropy encoded data and output a bitstream that includes the entropy encoded data.
[0191] FIG. 6 is a block diagram illustrating an example of video decoder 300 which may be video decoder 114 in the system 100 illustrated in FIG. 4 .
[0192] The video decoder 300 may be configured to perform any or all of the techniques of this disclosure. In the example of FIG. 5 , the video decoder 300 includes a plurality of functional components. The techniques described in this disclosure may be shared among the various components of the video decoder 300. In some examples, a processor may be configured to perform any or all of the techniques described in this disclosure.
[0193] In the example of FIG. 6 , video decoder 300 includes an entropy decoding unit 301, a motion compensation unit 302, an intra prediction unit 303, an inverse quantization unit 304, an inverse transformation unit 305, and a reconstruction unit 306 and a buffer 307. Video decoder 300 may, in some examples, perform a decoding pass generally reciprocal to the encoding pass described with respect to video encoder 200 (FIG. 5 ).
[0194] Entropy decoding unit 301 may retrieve an encoded bitstream. The encoded bitstream may include entropy coded video data (e.g., encoded blocks of video data). Entropy decoding unit 301 may decode the entropy coded video data, and from the entropy decoded video data, motion compensation unit 302 may determine motion information including motion vectors, motion vector precision, reference picture list indexes, and other motion information. Motion compensation unit 302 may, for example, determine such information by performing the AMVP and merge mode.
[0195] Motion compensation unit 302 may produce motion compensated blocks, possibly performing interpolation based on interpolation filters. Identifiers for interpolation filters to be used with sub-pixel precision may be included in the syntax elements.
[0196] Motion compensation unit 302 may use interpolation filters as used by video encoder 20 during encoding of the video block to calculate interpolated values for sub-integer pixels of a reference block. Motion compensation unit 302 may determine the interpolation filters used by video encoder 200 according to received syntax information and use the interpolation filters to produce predictive blocks.
[0197] Motion compensation unit 302 may uses some of the syntax information to determine sizes of blocks used to encode frame(s) and/or slice(s) of the encoded video sequence, partition information that describes how each macroblock of a picture of the encoded video sequence is partitioned, modes indicating how each partition is encoded, one or more reference frames (and reference frame lists) for each inter-encoded block, and other information to decode the encoded video sequence.
[0198] Intra prediction unit 303 may use intra prediction modes for example received in the bitstream to form a prediction block from spatially adjacent blocks. Inverse quantization unit 303 inverse quantizes, i.e., de-quantizes, the quantized video block coefficients provided in the bitstream and decoded by entropy decoding unit 301. Inverse transform unit 303 applies an inverse transform.
[0199] Reconstruction unit 306 may sum the residual blocks with the corresponding prediction blocks generated by motion compensation unit 202 or intra-prediction unit 303 to form decoded blocks. If desired, a deblocking filter may also be applied to filter the decoded blocks in order to remove blockiness artifacts. The decoded video blocks are then stored in buffer 307, which provides reference blocks for subsequent motion compensation/intra predication and also produces decoded video for presentation on a display device.
[0200] A listing of solutions describes some embodiments of the disclosed technology.
[0201] A first set of solutions is provided below. The following solutions show example embodiments of techniques discussed in the previous section (e.g., items 1-3).
[0202] 1. A video processing method (e.g., method 600 shown in FIG. 3 ), comprising: performing (602) a conversion between a video comprising one or more video layers and a coded representation of the video comprising one or more output layer sets, wherein the coded representation conforms to a format rule related to whether and how one or more syntax elements related to a non-scalable-nested hypothetical reference decoder (HRD) related supplemental enhancement information (SEI).
[0203] 2. The method of solution 1, wherein the format rule specifies that a message related to the non-scalable-nested HRD related SEI applies to output layer sets that include same set of layers as the entire coded representation.
[0204] 3. The method of any of solutions 1-2, wherein the format rule specifies to omit the one or more syntax elements in case that there is no output layer set that has a same set of layers as the entire coded representation.
[0205] 4. The method of solution 1, wherein the format rule specifies that the one or more syntax element are applicable to all layers in the coded representation.
[0206] The following solutions show example embodiments of techniques discussed in the previous section (e.g., items 4-10).
[0207] 5. A video processing method, comprising: performing a conversion between a video comprising one or more video layers and a coded representation of the video comprising one or more output layer sets, wherein the coded representation conforms to a format rule related to whether and how one or more syntax elements are included in a supplemental enhancement information (SEI) network abstraction layer (NAL) unit.
[0208] 6. The method of solution 5, wherein the format rule specifies that, in case that the SEI NAL unit includes a non-scalable-nested SEI message, a value of layer identifier is unconstrained.
[0209] 7. The method of any of solutions 5-6, wherein the format rule disables inclusion of a SEI NAL unit that includes a scalable-nested SEI message of a certain payload type due to signaling of use of a same picture timing in all output layer sets of in the coded representation.
[0210] 8. The method of any of solutions 5-7, wherein the format rule specifies that an SEI NAL unit that includes a non-scalable-nested SEI message of a first specific payload type is disallowed to include another SEI message of a second specific type.
[0211] 9. The method of solution 8, wherein the first specific payload type is equal to 0, 1, 130 or 203.
[0212] 10. The method of solutions 8 or 9, wherein the second specific payload type is equal to 0, 1, 130, 203, or 133.
[0213] 11. The method of solutions 8 to 10, wherein first specific payload type and the second specific payload type are 3.
[0214] 12. The method of any of solutions 1-11, wherein the performing the conversion comprises encoding the video to generate the coded representation.
[0215] 13. The method of any of solutions 1-11, wherein the performing the conversion comprises parsing and decoding the coded representation to generate the video.
[0216] 14. A video decoding apparatus comprising a processor configured to implement a method recited in one or more of solutions 1 to 13.
[0217] 15. A video encoding apparatus comprising a processor configured to implement a method recited in one or more of solutions 1 to 13.
[0218] 16. A computer program product having computer code stored thereon, the code, when executed by a processor, causes the processor to implement a method recited in any of solutions 1 to 13.
[0219] 17. A method, apparatus or system described in the present document.
[0220] A second set of solutions show example embodiments of techniques discussed in the previous section (e.g., items 1-5).
[0221] 1. A method of processing video data (e.g., method 700 as shown in FIG. 7A ), comprising: performing 702 a conversion between a video and a bitstream of the video, wherein the bitstream includes one or more output layer sets comprising one or more video layers according to a format rule, wherein the format rule specifies that a non-scalable-nested supplemental enhancement information, SEI, message that includes information regarding hypothetical reference decoder, HRD, is applicable to all output layer sets that include same video layers as the bitstream.
[0222] 2. The method of solution 1, wherein the non-scalable-nested SEI message is an SEI message that is not contained in a scalable nesting SEI message.
[0223] 3. The method of solution 1 or 2, wherein the non-scalable-nested SEI message that includes information regarding the HRD is a buffering period (BP) SEI message, a picture timing (PT) SEI message, a decoding unit information (DUI) SEI message, or a subpicture level information (SLI) SEI message.
[0224] 4. The method of solution 1 or 2, wherein the non-scalable-nested SEI message that includes information regarding the HRD has a payload type that is equal to 0, 1, 130, or 203.
[0225] 5. A method of processing video data (e.g., method 710 as shown in FIG. 7B ), comprising: performing 712 a conversion between a video and a bitstream of the video, wherein the bitstream comprises one or more output layer sets comprising one or more video layers according to a format rule, wherein the format rule specifies that a non-scalable-nested hypothetical reference decoder (HRD)-related supplemental enhancement information (SEI) message is omitted responsive to a condition that there does not exist an output layer set that includes a same set of layers as the bitstream.
[0226] 6. The method of solution 5, wherein the non-scalable-nested SEI message is an SEI message that is not contained in a scalable nesting SEI message.
[0227] 7. The method of solution 5 or 6, wherein the non-scalable-nested HRD-related SEI message is a buffering period (BP) SEI message, a picture timing (PT) SEI message, a decoding unit information (DUI) SEI message, or a subpicture level information (SLI) SEI message.
[0228] 8. The method of solution 5 or 6, wherein the non-scalable-nested HRD-related SEI message has a payload type that is equal to 0, 1, 130, or 203.
[0229] 9. A method of processing video data (e.g., method 720 as shown in FIG. 7C ), comprising: performing 722 a conversion between a video and a bitstream of the video, wherein the bitstream comprises one or more output layer sets comprising one or more video layers according to a format rule, wherein the format rule specifies that a value of layer identifier for a supplemental enhancement information (SEI) network abstraction layer (NAL) unit that includes a non-scalable-nested SEI message is not constrained.
[0230] 10. The method of solution 9, wherein the non-scalable-nested SEI message is an SEI message that is not contained in a scalable nesting SEI message.
[0231] 11. The method of solution 9, wherein the non-scalable-nested SEI message is a buffering period (BP) SEI message, a picture timing (PT) SEI message, a decoding unit information (DUI) SEI message, or a subpicture level information (SLI) SEI message.
[0232] 12. The method of solution 9, wherein the non-scalable-nested SEI message has a payload type that is equal to 0, 1, 130 or 203.
[0233] 13. A method of processing video data (e.g., method 730 as shown in FIG. 7D ), comprising: performing 732 a conversion between a video and a bitstream of the video, wherein the bitstream comprises one or more output layer sets comprising one or more video layers according to a format rule, wherein the format rule specifies that a particular payload type value corresponding to subpicture level information is disallowed from a list that includes allowable supplemental enhancement information (SEI) payload type values for non-hypothetical reference decoder (HRD) related supplemental enhancement information (SEI) messages.
[0234] 14. The method of solution 13, wherein the particular payload type value is 203.
[0235] 15. The method of solution 13, wherein the allowable SEI payload type values include filler payload, film grain characteristics, frame packing arrangement, parameter sets inclusion indication, mastering display color volume, content light level information, dependent rap indication, alternative transfer characteristics, ambient viewing environment, content color volume, equirectangular projection, generalized cube map projection, sphere rotation, region-wise packing, omni viewport, frame field information and sample aspect ratio information.
[0236] 16. The method of solution 13, wherein the allowable SEI payload type values include 3, 19, 45, 129, 137, 144, 145, 147 to 150, 153 to 156, 168, and 204.
[0237] 17. A method of processing video data, comprising: performing a conversion between a video and a bitstream of the video, wherein the bitstream includes one or more output layer sets comprising one or more video layers according to a format rule, wherein the format rule specifies that a non-scalable-nested supplemental enhancement information, SEI, message that includes information irrelevant to hypothetical reference decoder (HRD) is applicable to all layers in the bitstream.
[0238] 18. The method of solution 17, wherein the non-scalable-nested SEI message is an SEI message that is not contained in a scalable nesting SEI message.
[0239] 19. The method of solution 17 or 18, wherein the non-scalable-nested SEI message that includes information irrelevant to the HRD has a payload type that is not equal to 0, 1, 130, or 203.
[0240] 20. The method of solution 17 or 18, wherein the non-scalable-nested SEI message that includes information irrelevant to the HRD does not correspond to a buffering period (BP) SEI message, a picture timing (PT) SEI message, a decoding unit information (DUI) SEI message, or a subpicture level information (SLI) SEI message.
[0241] 21. The method of any of solutions 1 to 20, wherein the conversion includes encoding the video into the bitstream.
[0242] 22. The method of any of solutions 1 to 20, wherein the conversion includes decoding the video from the bitstream.
[0243] 23. The method of any of solutions 1 to 20, wherein the conversion includes generating the bitstream from the video, and the method further comprises: storing the bitstream in a non-transitory computer-readable recording medium.
[0244] 24. A video processing apparatus comprising a processor configured to implement a method recited in any one or more of solutions 1 to 23.
[0245] 25. A method of storing a bitstream of a video, comprising, a method recited in any one of solutions 1 to 23, and further including storing the bitstream to a non-transitory computer-readable recording medium.
[0246] 26. A computer readable medium storing program code that, when executed, causes a processor to implement a method recited in any one or more of solutions 1 to 23.
[0247] 27. A computer readable medium that stores a bitstream generated according to any of the above described methods.
[0248] 28. A video processing apparatus for storing a bitstream, wherein the video processing apparatus is configured to implement a method recited in any one or more of solutions 1 to 23.
[0249] A third set of solutions show example embodiments of techniques discussed in the previous section (e.g., item 6).
[0250] 1. A method of processing video data (e.g., method 800 as shown in FIG. 8 ), comprising: performing 802 a conversion between a video and a bitstream of the video comprising one or more output layer sets according to a rule, wherein the rule specifies that a supplemental enhancement information (SEI) network abstraction layer (NAL) unit that includes a scalable-nested SEI message carrying picture timing information is not included due to use of a same picture timing in all output layer sets in the bitstream.
[0251] 2. The method of solution 1, wherein the scalable-nested SEI message is an SEI message that is contained in a scalable nesting SEI message.
[0252] 3. The method of solution 1 or 2, wherein the scalable-nested SEI message carrying the picture timing information corresponds to a picture timing (PT) SEI message.
[0253] 4. The method of solution 1, wherein the scalable-nested SEI message carrying the picture timing information has a payload type equal to 1.
[0254] 5. The method of any of solutions 1 to 4, wherein the rule further specifies that non-scalable-nested SEI messages carrying the picture timing information apply to the all output layer sets and subpicture sequences that are allowed to be extracted from the bitstream.
[0255] 6. The method of solution 5, wherein a non-scalable-nested SEI message is an SEI message that is not contained in a scalable nesting SEI message.
[0256] 7. The method of any of solutions 1 to 4, wherein the rule further specifies that the SEI NAL unit that includes the scalable-nested SEI message carrying the picture timing information is not included in case that a syntax field has a value specifying that the scalable-nested SEI message that applies to specific output layer sets or layers applies to all subpictures of the specified output layer sets or layers.
[0257] 8. The method of any of solutions 1 to 7, wherein the conversion includes encoding the video into the bitstream.
[0258] 9. The method of any of solutions 1 to 7, wherein the conversion includes decoding the video from the bitstream.
[0259] 10. The method of any of solutions 1 to 7, wherein the conversion includes generating the bitstream from the video, and the method further comprises: storing the bitstream in a non-transitory computer-readable recording medium.
[0260] 11. A video processing apparatus comprising a processor configured to implement a method recited in any one or more of solutions 1 to 10.
[0261] 12. A method of storing a bitstream of a video, comprising, a method recited in any one of solutions 1 to 10, and further including storing the bitstream to a non-transitory computer-readable recording medium.
[0262] 13. A computer readable medium storing program code that, when executed, causes a processor to implement a method recited in any one or more of solutions 1 to 10.
[0263] 14. A computer readable medium that stores a bitstream generated according to any of the above described methods.
[0264] 15. A video processing apparatus for storing a bitstream, wherein the video processing apparatus is configured to implement a method recited in any one or more of solutions 1 to 10.
[0265] A fourth set of solutions show example embodiments of techniques discussed in the previous section (e.g., items 7-9).
[0266] 1. A method of processing video data (e.g., method 900 as shown in FIG. 9A ), comprising: performing 902 a conversion between a video and a bitstream of the video, wherein the bitstream comprises one or more supplemental enhancement information, SEI, network abstraction layer (NAL) units according to a rule, wherein the rule specifies that, responsive to an SEI NAL unit including a non-scalable-nested SEI message of a first payload type, the SEI NAL unit is disallowed to include another SEI message of a second payload type.
[0267] 2. The method of solution 1, wherein the non-scalable-nested SEI message is an SEI message that is not contained in a scalable nesting SEI message.
[0268] 3. The method of solution 1 or 2, wherein the non-scalable-nested SEI message of the first payload type corresponds to a buffering period (BP) SEI message, a picture timing (PT) SEI message, a decoding unit information (DUI) SEI message, or a subpicture level information (SLI) SEI message.
[0269] 4. The method of solution 1 or 2, wherein the first payload type is equal to 0, 1, 130 or 203.
[0270] 5. The method of any of solutions 1 to 4, wherein the non-scalable-nested SEI message of the second payload type does not correspond to any of a buffering period (BP) SEI message, a picture timing (PT) SEI message, a decoding unit information (DUI) SEI message, and a subpicture level information (SLI) SEI message.
[0271] 6. The method of any of solutions 1 to 4, wherein the second payload type is not equal to any of 0, 1, 130 and 203.
[0272] 7. A method of processing video data (e.g., method 910 as shown in FIG. 9B ), comprising: performing 912 a conversion between a video and a bitstream of the video according to a rule, wherein the bitstream comprises one or more supplemental enhancement information, SEI, network abstraction layer (NAL) units according to a rule, wherein the rule specifies that, responsive to an SEI NAL unit including a scalable-nested SEI message of a first payload type, the SEI NAL unit is disallowed to include another SEI message of a second payload type.
[0273] 8. The method of solution 7, wherein the scalable-nested SEI message is an SEI message that is contained in a scalable nesting SEI message.
[0274] 9. The method of solution 7 or 8, wherein the scalable-nested SEI message of the first payload type corresponds to a buffering period (BP) SEI message, a picture timing (PT) SEI message, a decoding unit information (DUI) SEI message, or a subpicture level information (SLI) SEI message.
[0275] 10. The method of solution 7 or 8, wherein the first payload type is equal to 0, 1, 130 or 203.
[0276] 11. The method of any of solutions 7 to 10, wherein the scalable-nested SEI message of the second payload type does not correspond to any of a buffering period (BP) SEI message, a picture timing (PT) SEI message, a decoding unit information (DUI) SEI message, a subpicture level information (SLI) SEI message, and a scalable nesting information SEI message.
[0277] 12. The method of any of solutions 7 to 10, wherein the second payload type is not equal to any of 0, 1, 130, 203, and 133.
[0278] 13. A method of processing video data (e.g., method 920 as shown in FIG. 9C ), comprising: performing 922 a conversion between a video and a bitstream of the video, wherein the bitstream comprises one or more supplemental enhancement information, SEI, network abstraction layer (NAL) units according to a rule, wherein the rule specifies that, responsive to an SEI NAL unit including a SEI message of a first payload type, the SEI NAL unit is disallowed to include another SEI message not equal to the first payload type or a second payload type.
[0279] 14. The method of solution 13, wherein the SEI message of the first payload type corresponds to a filler payload SEI message.
[0280] 15. The method of solution 13 or 14, wherein the first payload type is equal to 3.
[0281] 16. The method of any of solutions 13 to 15, wherein the rule further specifies that the SEI message of the first payload type is disallowed to be contained in a scalable nesting SEI message.
[0282] 17. The method of any of solutions 13 to 16, wherein the rule further specifies that the SEI message of the second payload type is a scalable nesting SEI message.
[0283] 18. The method of any of solutions 13 to 16, wherein the second payload type is equal to 133.
[0284] 19. The method of any of solutions 1 to 18, wherein the conversion includes encoding the video into the bitstream.
[0285] 20. The method of any of solutions 1 to 18, wherein the conversion includes decoding the video from the bitstream.
[0286] 21. The method of any of solutions 1 to 18, wherein the conversion includes generating the bitstream from the video, and the method further comprises: storing the bitstream in a non-transitory computer-readable recording medium.
[0287] 22. A video processing apparatus comprising a processor configured to implement a method recited in any one or more of solutions 1 to 21.
[0288] 23. A method of storing a bitstream of a video, comprising, a method recited in any one of solutions 1 to 21, and further including storing the bitstream to a non-transitory computer-readable recording medium.
[0289] 24. A computer readable medium storing program code that, when executed, causes a processor to implement a method recited in any one or more of solutions 1 to 21.
[0290] 25. A computer readable medium that stores a bitstream generated according to any of the above described methods.
[0291] 26. A video processing apparatus for storing a bitstream, wherein the video processing apparatus is configured to implement a method recited in any one or more of solutions 1 to 21.
[0292] A fifth set of solutions show example embodiments of techniques discussed in the previous section (e.g., items 10 and 11).
[0293] 1. A method of processing video data (e.g., method 1000 as shown in FIG. 10A ), comprising: performing 1002 a conversion between a video and a bitstream of the video, wherein the bitstream comprises one or more output layer sets comprising one or more video layers according to a rule, wherein the rule specifies a particular decoding order between a subpicture level information (SLI) supplemental enhancement information (SEI) message and a buffering period (BP) SEI message that apply to a particular output layer set, responsive to a condition that the SLI SEI message and the BP SEI message are included in an access unit.
[0294] 2. The method of solution 1, wherein the particular decoding order is that the SLI SEI message precedes the BP SEI message.
[0295] 3. A method of processing video data (e.g., method 1010 as shown in FIG. 10B ), comprising: performing 1012 a conversion between a video and a bitstream of the video according to a rule, wherein the rule specifies that a first syntax field indicating sublayer representation information for which an initial coded picture buffer (CPB) removal delay related syntax elements are present is omitted, responsive to a particular value of a second syntax field indicative of a maximum number of temporal sublayers for which an initial CPB removal delay is indicated in a buffering period supplemental enhancement information (SEI) message.
[0296] 4. The method of solution 3, wherein the particular value is 0.
[0297] 5. The method of solution 3 or 4, wherein the second syntax filed with the particular value specifies that the maximum number of temporal sublayers is 1.
[0298] 6. The method of any of solutions 3 to 5, wherein the first syntax field equal to another particular value specifies that the initial CPB removal delay related syntax elements are present for the sublayer representation in a range of 0 to the second syntax field, inclusive.
[0299] 7. The method of solution 6, wherein another particular value is 1.
[0300] 8. The method of any of solutions 3 to 7, wherein the syntax filed equal to another particular value specifies that the initial CPB removal delay related syntax elements are present for the sublayer representation corresponding to the particular value of the second syntax field.
[0301] 9. The method of solution 8, wherein the another particular value is 0.
[0302] 10. The method of any of solutions 3 to 9, wherein the rule further specifies to infer a value of the first syntax field to be equal to 0, responsive to the particular value of the second syntax field.
[0303] 11. The method of any of solutions 1 to 10, wherein the conversion includes encoding the video into the bitstream.
[0304] 12. The method of any of solutions 1 to 10, wherein the conversion includes decoding the video from the bitstream.
[0305] 13. The method of any of solutions 1 to 10, wherein the conversion includes generating the bitstream from the video, and the method further comprises: storing the bitstream in a non-transitory computer-readable recording medium.
[0306] 14. A video processing apparatus comprising a processor configured to implement a method recited in any one or more of solutions 1 to 13.
[0307] 15. A method of storing a bitstream of a video, comprising, a method recited in any one of solutions 1 to 13, and further including storing the bitstream to a non-transitory computer-readable recording medium.
[0308] 16. A computer readable medium storing program code that, when executed, causes a processor to implement a method recited in any one or more of solutions 1 to 13.
[0309] 17. A computer readable medium that stores a bitstream generated according to any of the above described methods.
[0310] 18. A video processing apparatus for storing a bitstream, wherein the video processing apparatus is configured to implement a method recited in any one or more of solutions 1 to 13.
[0311] The disclosed and other solutions, examples, embodiments, modules and the functional operations described in this document can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in combinations of one or more of them. The disclosed and other embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more them. The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
[0312] A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
[0313] The processes and logic flows described in this document can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).
[0314] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random-access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices. Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
[0315] While this patent document contains many specifics, these should not be construed as limitations on the scope of any subject matter or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular techniques. Certain features that are described in this patent document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
[0316] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Moreover, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.
[0317] Only a few implementations and examples are described and other implementations, enhancements and variations can be made based on what is described and illustrated in this patent document.
Claims
The invention claimed is:
1. A method of processing video data, comprising:
performing a conversion between a video and a bitstream of the video comprising one or more output layer sets according to a rule,
wherein the rule specifies that a supplemental enhancement information (SEI) network abstraction layer (NAL) unit that includes a scalable-nested SEI message with a payload type of picture timing (PT) is not included when a flag included in the bitstream named general_same_pic_timing_in_all_ols_flag has a value of 1,
wherein the rule further specifies that a non-scalable-nested hypothetical reference decoder (HRD)-related supplemental enhancement information (SEI) message is omitted responsive to a condition that there does not exist an output layer set that includes video layers as the bitstream, and
wherein the rule further specifies that a particular payload type value corresponding to subpicture level information is disallowed from VclAssociatedSeiList that is a list including one or more supplemental enhancement information (SEI) payload type values.
2. The method of claim 1, wherein the scalable-nested SEI message with the payload type of PT carries picture timing information.
3. The method of claim 1, wherein the scalable-nested SEI message with the payload type of PT has a payload type equal to 1.
4. The method of claim 1, wherein the rule further specifies that when the flag included in the bitstream named general_same_pic_timing_in_all_ols_flag has a value of 1, same picture timing in all output layer sets is used.
5. The method of claim 4, wherein the rule further specifies that when the flag included in the bitstream named general_same_pic_timing_in_all_ols_flag has a value of 1, non-scalable-nested SEI messages with the payload type of PT apply to all output layer sets.
6. The method of claim 1, wherein the conversion includes encoding the video into the bitstream.
7. The method of claim 1, wherein the conversion includes decoding the video from the bitstream.
8. An apparatus for processing video data comprising a processor and a non-transitory memory with instructions thereon, wherein the instructions upon execution by the processor, cause the processor to:
perform a conversion between a video and a bitstream of the video comprising one or more output layer sets according to a rule,
wherein the rule specifies that a supplemental enhancement information (SEI) network abstraction layer (NAL) unit that includes a scalable-nested SEI message with a payload type of picture timing (PT) is not included when a flag included in the bitstream named general_same_pic_timing_in_all_ols_flag has a value of 1,
wherein the rule further specifies that a non-scalable-nested hypothetical reference decoder (HRD)-related supplemental enhancement information (SEI) message is omitted responsive to a condition that there does not exist an output layer set that includes video layers as the bitstream, and
wherein the rule further specifies that a particular payload type value corresponding to subpicture level information is disallowed from VclAssociatedSeiList that is a list including one or more supplemental enhancement information (SEI) payload type values.
9. The apparatus of claim 8, wherein the scalable-nested SEI message with the payload type of PT carries picture timing information.
10. The apparatus of claim 8, wherein the scalable-nested SEI message with the payload type of PT has a payload type equal to 1.
11. The apparatus of claim 8, wherein the rule further specifies that when the flag included in the bitstream named general_same_pic_timing_in_all_ols_flag has a value of 1, same picture timing in all output layer sets is used.
12. The apparatus of claim 11, wherein the rule further specifies that when the flag included in the bitstream named general_same_pic_timing_in_all_ols_flag has a value of 1, non-scalable-nested SEI messages with the payload type of PT apply to all output layer sets.
13. A non-transitory computer-readable storage medium storing instructions that cause a processor to:
perform a conversion between a video and a bitstream of the video comprising one or more output layer sets according to a rule,
wherein the rule specifies that a supplemental enhancement information (SEI) network abstraction layer (NAL) unit that includes a scalable-nested SEI message with a payload type of picture timing (PT) is not included when a flag included in the bitstream named general_same_pic_timing_in_all_ols_flag has a value of 1,
wherein the rule further specifies that a non-scalable-nested hypothetical reference decoder (HRD)-related supplemental enhancement information (SEI) message is omitted responsive to a condition that there does not exist an output layer set that includes video layers as the bitstream, and wherein the rule further specifies that a particular payload type value corresponding to subpicture level information is disallowed from VclAssociatedSeiList that is a list including one or more supplemental enhancement information (SEI) payload type values.
14. The non-transitory computer-readable storage medium of claim 13, wherein the scalable-nested SEI message with the payload type of PT carries picture timing information, and wherein the scalable-nested SEI message with the payload type of PT has a payload type equal to 1.
15. The non-transitory computer-readable storage medium of claim 13, wherein the rule further specifies that when the flag included in the bitstream named general_same_pic_timing_in_all_ols_flag has a value of 1, same picture timing in all output layer sets is used, and non-scalable-nested SEI messages with the payload type of PT apply to all output layer sets.
16. A method for storing a bitstream of a video, wherein the method comprises:
generating the bitstream of the video comprising one or more output layer sets according to a rule, and
storing the bitstream in a non-transitory computer-readable recording medium,
wherein the rule specifies that a supplemental enhancement information (SEI) network abstraction layer (NAL) unit that includes a scalable-nested SEI message with a payload type of picture timing (PT) is not included when a flag included in the bitstream named general_same_pic_timing_in_all_ols_flag has a value of 1,
wherein the rule further specifies that a non-scalable-nested hypothetical reference decoder (HRD)-related supplemental enhancement information (SEI) message is omitted responsive to a condition that there does not exist an output layer set that includes video layers as the bitstream, and
wherein the rule further specifies that a particular payload type value corresponding to subpicture level information is disallowed from VclAssociatedSeiList that is a list including one or more supplemental enhancement information (SEI) payload type values.
17. The non-transitory computer-readable recording medium of claim 16, wherein the scalable-nested SEI message with the payload type of PT carries picture timing information, and wherein the scalable-nested SEI message with the payload type of PT has a payload type equal to 1.
18. The non-transitory computer-readable recording medium of claim 16, wherein the rule further specifies that when the flag included in the bitstream named general_same_pic_timing_in_all_ols_flag has a value of 1, same picture timing in all output layer sets is used, and non-scalable-nested SEI messages with the payload type of PT apply to all output layer sets.
19. The method of claim 1, wherein the one or more SEI payload type values include 3, 19, 45, 129, 137, 144, 145, 147 to 150, 153 to 156, 168, and 204.
20. The method of claim 1, wherein the particular payload type value is 203.
Patent Citations (43)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US6324415(B1) | 2001-11-01 | Spehr | Applicant |
| US9395142(B2) | 2016-07-01 | Rodich | Applicant |
| US10645404(B2) | 2020-05-01 | Wang | Applicant |
| US2010/0091837(A1) | 2010-04-01 | Zhu | Applicant |
| US2013/0135434(A1) | 2013-05-01 | Chen | Applicant |
| US2013/0290492(A1) | 2013-10-01 | ElArabawy | Applicant |
| US2014/0016707(A1) | 2014-01-01 | Wang | Applicant |
| US2014/0086341(A1) | 2014-03-01 | Wang | Applicant |
| US2014/0098895(A1) | 2014-04-01 | Wang | Applicant |
| US2014/0192149(A1) | 2014-07-01 | Wang | Examiner |
| US2014/0301476(A1) | 2014-10-01 | Deshpande | Applicant |
| US2014/0355692(A1) | 2014-12-01 | Ramasubramonian | Applicant |
| US2015/0103927(A1) | 2015-04-01 | Hannuksela | Applicant |
| US2015/0271498(A1) | 2015-09-01 | Wang | Applicant |
| US2015/0271529(A1) | 2015-09-01 | Wang | Applicant |
| US2015/0358640(A1) | 2015-12-01 | Hendry | Applicant |
| US2016/0381385(A1) | 2016-12-01 | Ugur | Applicant |
| US2016/0381394(A1) | 2016-12-01 | Sychev | Applicant |
| US2017/0214923(A1) | 2017-07-01 | He et al. | Applicant |
| US2018/0014033(A1) | 2018-01-01 | Wu | Applicant |
| US2019/0174144(A1) | 2019-06-01 | Hannuksela | Applicant |
| US2019/0364279(A1) | 2019-11-01 | Yasugi | Applicant |
| US2020/0077107(A1) | 2020-03-01 | Deshpande | Applicant |
| US2020/0154144(A1) | 2020-05-01 | Deshpande | Applicant |
| US2020/0296351(A1) | 2020-09-01 | Wang | Applicant |
| US2022/0377384(A1) | 2022-11-01 | Wang | Applicant |
| US2023/0037902(A1) | 2023-02-01 | Sánchez De La Fuente | Examiner |
| US2023/0043130(A1) | 2023-02-01 | Sánchez De La Fuente | Examiner |
| US2023/0095686(A1) | 2023-03-01 | Sánchez De La Fuente | Examiner |
| CA2951522(C) | 2019-08-01 | Applicant | |
| JP6162236(B2) | 2017-07-01 | Applicant | |
| JP6549288(B2) | 2019-07-01 | Applicant | |
| JP2020501430(A) | 2020-01-01 | Applicant | |
| JP7503663(B2) | 2024-06-01 | Applicant | |
| JP7508598(B2) | 2024-07-01 | Applicant | |
| JP7508599(B2) | 2024-07-01 | Applicant | |
| RU2619194(C2) | 2017-05-01 | Applicant | |
| RU2646378(C2) | 2018-03-01 | Applicant | |
| WO2014107396(A1) | 2014-07-01 | Applicant | |
| WO2021123159(A1) | 2021-06-01 | Applicant | |
| WO2021123166(A1) | 2021-06-01 | Applicant | |
| WO-2021201548(A1) | 2021-10-01 | Examiner | |
| WO2021252545(A1) | 2021-12-01 | Applicant |
Non-Patent Literature (42)
- “Series H: Audiovisual and Multimedia Systems Infrastructure of audiovisual services—Coding of moving video High efficiency video coding,” Rec. ITU-T H.265 | ISO/IEC 23008-2 (in force edition), Feb. 2018, 692 pages.Applicant
- Document: JVET-G1001-v1, Chen, J., et al., “Algorithm Description of Joint Exploration Test Model 7 (JEM 7),” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 7th Meeting: Torino, IT, Jul. 13-21, 2017, 50 pages.Applicant
- Document: JVET-R2001-vB, Bross, B., et al., “Versatile Video Coding (Draft 9),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 18th Meeting: by teleconference, Apr. 15-24, 2020, 530 pages.Applicant
- Document: JVET-S0152-v5, Wang, Y., “AHG2: Editorial input of a text integration for the May 2020 HLS AHG meeting outcome,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 19th Meeting: by teleconference, Jun. 22-Jul. 1, 2020, 5 pages.Applicant
- Document: JVET-Q2002-v3, Chen, J., et al., “Algorithm description for Versatile Video Coding and Test Model 8 (VTM 8),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 17th Meeting: Brussels, BE, Jan. 7-17, 2020, 97 pages.Applicant
- Li, X., VTM software: Retrieved from the internet: https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM.git, Mar. 3, 2023, 3 pages.Applicant
- Document: JCTVC-AC1005-v2, Boyce, J., et al., “HEVC Additional Supplemental Enhancement Information (Draft 4).” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 29th Meeting: Macao, CN, Oct. 19-25, 2017, 45 pages.Applicant
- Schierl et al.,“System Layer Integration of High Efficiency Video Coding ”, IEEE Transactions on Circuits and Systems for Video Technology, vol. 22, No. 12, Dec. 2012, 14 pages.Applicant
- Wang, Y., et al. “The High-Level Syntax of the Versatile Video Coding (VVC) Standard” Retrieved from the Internet: URL: https://ieeexplore.ieee.org/stamp/stamp.jsparnumber=9395142, IEEE Transactions on Circuits and Systems for Video Technology, vol. 31, No. 10, Oct. 2021, 23 pages.Applicant
- Foreign Communication From a Counterpart Application, PCT Application No. PCT/US2021/036484, International Search Report dated Sep. 1, 2021, 66 pages.Applicant
- Foreign Communication From a Counterpart Application, PCT Application No. PCT/US2021/036487, International Search Report dated Sep. 1, 2021, 29 pages.Applicant
- Foreign Communication From a Counterpart Application, Indian Application No. 202247071748, Indian Office Action dated Feb. 13, 2023, 6 pages.Applicant
- Foreign Communication From a Counterpart Application, PCT Application No. PCT/US2021/036489, International Search Report dated Sep. 1, 2021, 61 pages.Applicant
- Foreign Communication From a Counterpart Application, Indian Application No. 202247071693, Indian Office Action dated Feb. 13, 2023, 7 pages.Applicant
- Foreign Communication From a Counterpart Application, PCT Application No. PCT/US2021/036491, International Search Report dated Sep. 14, 2021, 16 pages.Applicant
- Foreign Communication From a Counterpart Application, Indian Application No. 202247071247, Indian Office Action dated Feb. 22, 2023, 6 pages.Applicant
- Foreign Communication From a Related Counterpart Application, Indian Application No. 202247071333, Indian Office Action dated May 9, 2023, 7 pages.Applicant
- Non-Final Office Action dated May 17, 2023, 14 pages, U.S. Appl. No. 18/077,886, filed Dec. 8, 2022.Applicant
- Non-Final Office Action dated Apr. 10, 2023, 16 pages, U.S. Appl. No. 18/077,866, filed Dec. 8, 2022.Applicant
- Document: JVET-Q0488-v1, Wan, W., et al., “AHG9: Bounding redundant SEI messages,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 17th Meeting: Brussels, BE, Jan. 7-17, 2020, 4 pages.Applicant
- Document: JVET-P2001-vE, Bross, B., et al., “Versatile Video Coding (Draft 7),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 16th Meeting: Geneva, CH, Oct. 1-11, 2019, 491 pages.Applicant
- Document: JVET-P0125-v1, Wang, Y.K., “AHG8/AHG17: Miscellaneous HLS topics,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 16th Meeting: Geneva, CH, Oct. 1-11, 2019, 3 pages.Applicant
- Document: JVET-Q0394, Sanchez, Y., “AHG9: On OLS extraction and scalable nesting SEI message,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 17th Meeting: Brussels, BE, Jan. 7-17, 2020, 5 pages.Applicant
- Document: JVET-Q0397, Skupin, R., et al., “AHG12: On subpicture extraction,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 17th Meeting: Brussels, BE, Jan. 7-17, 2020, 6 pages.Applicant
- Document: JVET-Q2001-vB, Bross, B., et al., “Versatile Video Coding (Draft 8),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 17th Meeting: Brussels, BE, Jan. 7-17, 2020, 519 pages.Applicant
- Extended European Search Report from European Application No. 21821514.3 dated Oct. 18, 2023, 9 pages.Applicant
- Extended European Search Report from European Application No. 21821749.5 dated Oct. 9, 2023, 11 pages.Applicant
- Partial Supplementary European Search Report from European Application No. 21822668.6 dated Oct. 20, 2023, 14 pages.Applicant
- Document: JVET-R0101-v1, Deshpande, S., et al., “On Alternative Timing Information Signalling,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 18th Meeting: by teleconference, Apr. 15-24, 2020, 4 pages.Applicant
- Document: JVET-R2001-vA, Bross, B., et al., “Versatile Video Coding (Draft 9),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 18th Meeting: by teleconference, Apr. 15-24, 2020, 524 pages.Applicant
- Non-Final Office Action from U.S. Appl. No. 18/077,810 dated Feb. 1, 2024, 8 pages.Applicant
- Extended European Search Report from European Application No. 21822668.6 dated Feb. 9, 2024, 14 pages.Applicant
- Document: JVET-S0157-v1, Wang, Y.K., et al., “AHG9: HRD and related cleanups,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 19th Meeting: by teleconference, Jun. 22-Jul. 1, 2020, 7 pages.Applicant
- Document: JVET-P0125-v2, Wang, Y.K., et al., “AHG8/AHG17: Miscellaneous HLS topics,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 16th Meeting: Geneva, CH, Oct. 1-11, 2019, 3 pages.Applicant
- Document: JVET-S0178-v3, Wang, Y.K., et al., “AHG9: General SEI semantics and constraints,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 19th Meeting: by teleconference, Jun. 22-Jul. 1, 2020, 5 pages.Applicant
- Japanese Notice of Allowance from Japanese Patent Application No. 2022-575702 dated May 21, 2024, 6 pages.Applicant
- Japanese Notice of Allowance from Japanese Patent Application No. 2022-575701 dated May 14, 2024, 5 pages.Applicant
- Document: JVET-Q0394, Sanchez, Y., et al., “AHG9: On OLS extraction and scalable nesting SEI message,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 17th Meeting: Brussels, BE, Jan. 7-17, 2020, 6 pages.Applicant
- Document: JVET-R2001-vA, Bross< B., et al., “Versatile Video Coding (Draft 9),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WVG 11 18th Meeting: by teleconference, Apr. 15-24, 2020, 524 pages.Applicant
- Russian Office Action from Russian Application No. 2022132302 dated Jun. 17, 2024, 19 pages.Applicant
- Document: JVET-Q2001-vE, Bross, B., et al., “Versatile Video Coding (Draft 8),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 17th Meeting: Brussels, BE, Jan. 7-17, 2020, 512 pages. XP030285390, Retrieved from URL: http://phenix.int-evry.fr/jvet/doc_end_user/documents/17_Brussels/wg11/JVET-Q2001-v15.zip JVET-Q2001-vE.docx.Applicant
- Request for the Submission of an Opinion for Korean Application No. 10-2022-7043181, Nov. 12, 2024, 13 pages.Applicant