Dpb size-based reference picture entry constraint

Abstract

To provide a video coding mechanism.SOLUTION: A mechanism includes receiving a bitstream including a reference picture list syntax structure (ref_pic_list_struct()) containing a current picture and the number of reference entries (num_ref_entries) constrained to a range from 0 to maximum decoded picture buffer size+offset. The current picture is decoded on the basis of the ref_pic_list_struct() to generate a decoded picture. The decoded picture is transferred for display as a part of a decoded video sequence.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This patent application claims priority to U.S. Provisional Patent Application No. 62 / 911,808, entitled "Scalability in Video Coding," filed on October 7, 2019 by Ye-Kui Wang, which is incorporated herein by reference.

[0002] FIELD This disclosure relates generally to video coding, and more particularly to mechanisms for preventing errors when sub-bitstream extraction is performed on multi-layer bitstreams. [Background technology]

[0003] The amount of video data required to render even a relatively short video can be substantially large, resulting in complications when the data is streamed or otherwise transmitted over a communication network that has limited bandwidth capacity. Thus, in today's telecommunication networks, video data is typically compressed before being transmitted. The size of the video can also be an issue when the video is stored in a storage device, which may also have limited memory resources. Video compression devices often use software and / or hardware at the source to code the video data before transmission or storage, thereby reducing the amount of data required to represent a digital video image. The compressed data is then received at the destination by a video decompression device, which decodes the video data. With limited network resources and ever-increasing demands for video quality, improvements in compression and decompression techniques that improve compression ratios with little or no sacrifice in image quality are desirable. Summary of the Invention [Means for solving the problem]

[0004] In one embodiment, the disclosure includes a method implemented by a decoder, the method including receiving, by the decoder, a bitstream including a current picture and a reference picture list syntax structure (ref_pic_list_struct()) including a number of reference entries (num_ref_entries) constrained to a range from 0 to a maximum decoded picture buffer size plus an offset, and decoding, by the decoder, the current picture based on the ref_pic_list_struct() to generate a decoded picture.

[0005] A picture may be coded according to intra prediction, inter prediction, and / or inter-layer prediction. In intra prediction, blocks in a picture are coded by referencing other blocks in the same picture. In inter prediction, blocks in a current picture are coded by referencing blocks in one or more other pictures. In inter-layer prediction, pictures are coded in layers, and blocks of a picture in an output layer are coded by referencing blocks of a picture in a reference layer. ref_pic_list_struct() may be employed to keep track of references between pictures, thereby supporting reconstruction of inter-predicted pictures. In some video coding systems, ref_pic_list_struct() includes the maximum number of reference entries that can be employed for the current picture. In such systems, the maximum number of reference entries for the current picture is a statically defined value that is global for all layers. The problem with this approach is that reference layers use a different amount of space in the decoded picture buffer than output layers. For example, reference layers use space for picture reconstruction, and output layers use space for both picture reconstruction and storage pending output. Thus, a statically defined maximum number of reference entries selected to support a smaller amount of space used for the reference layer may be overly restrictive when applied to an output layer picture. Alternatively, a statically defined maximum number of reference entries selected for an output layer may provide more space than necessary to decode a reference layer picture, thus wasting memory resources. Examples of the present invention include a mechanism for constraining ref_pic_list_struct() to support different picture buffer usage for different types of layers. For example, a num_ref_entries syntax element may be included in ref_pic_list_struct(). num_ref_entries indicates the number of entries used for each picture.num_ref_entries may be constrained to maintain a range selected based on a maximum decoded picture buffer size. The maximum decoded picture buffer size differs depending on whether the layer is a reference layer or an output layer. Thus, constraining num_ref_entries based on the maximum decoded picture buffer size allows a different number of reference pictures to be employed for the output layer and the reference layer. Furthermore, the set of reference pictures for each picture (setofRefPics) may be constrained by a different maximum decoded picture buffer size based on the layer instead of a static value that is global for all layers. By adopting such a constraint, a more efficient allocation of memory in the decoded picture buffer is supported, thus supporting high coding efficiency as more optimal memory usage encourages more efficient encoding. As a result, the functionality of the encoder and decoder is improved. Furthermore, coding efficiency is increased, thereby reducing the use of processor, memory, and / or network signaling resources in both the encoder and the decoder.

[0006] Optionally, in any of the aforementioned aspects, another implementation form of the aspect provides that ref_pic_list_struct() is referenced according to a list index (listIdx) and a reference picture list structure index (rplsIdx) and is denoted as ref_pic_list_struct(listIdx, rplsIdx), and that num_ref_entries is denoted as num_ref_entries[listIdx][rplsIdx], and that num_ref_entries[listIdx][rplsIdx] specifies the number of entries in ref_pic_list_struct(listIdx, rplsIdx).

[0007] Optionally, in any of the aforementioned aspects, another implementation of the aspect provides that the number of pictures in the setOfRefPics referenced in the ref_pic_list_struct is constrained to be less than or equal to the maximum decoded picture buffer size minus 1.

[0008] Optionally, in any of the aforementioned aspects, another implementation of the aspect specifies that ref_pic_list_struct() includes reference picture list 0 (RefPicList[0]) and reference picture list 1 (RefPicList[1]), and that setOfRefPics is a set-specific picture referenced by all entries in RefPicList[0] that have the same network abstraction layer (NAL) unit header layer identifier (nuh_layer_id) as the current picture and all entries in RefPicList[1] that have the same nuh_layer_id as the current picture.

[0009] Optionally, in any of the aforementioned aspects, another implementation of the aspect provides that setOfRefPics is the same set for all slices of each picture.

[0010] Optionally, in any of the aforementioned aspects, another implementation of the aspect specifies that the bitstream includes a decoded picture buffer parameters syntax structure (dpb_parameters()), and that the dpb_parameters() includes a maximum decoded picture buffer minus 1 (max_dec_pic_buffering_minus1), and that the maximum decoded picture buffer size corresponds to max_dec_pic_buffering_minus1.

[0011] Optionally, in any of the aforementioned aspects, another implementation form of the aspect provides that dpb_parameters() is included in a video parameter set (VPS) or a sequence parameter set (SPS).

[0012] In one embodiment, the disclosure includes a method implemented by an encoder, the method including: encoding, by the encoder, a current picture based on a reference picture, into a bitstream; encoding, by the encoder, a ref_pic_list_struct() indicating the reference pictures and including num_ref_entries constrained to range from 0 to a maximum decoded picture buffer size plus an offset, and storing, by the encoder, the bitstream for communication to a decoder.

[0013] A picture may be coded according to intra prediction, inter prediction, and / or inter-layer prediction. In intra prediction, blocks in a picture are coded by referencing other blocks in the same picture. In inter prediction, blocks in a current picture are coded by referencing blocks in one or more other pictures. In inter-layer prediction, pictures are coded in layers, and blocks of a picture in an output layer are coded by referencing blocks of a picture in a reference layer. ref_pic_list_struct() may be employed to keep track of references between pictures, thereby supporting reconstruction of inter-predicted pictures. In some video coding systems, ref_pic_list_struct() includes the maximum number of reference entries that can be employed for the current picture. In such systems, the maximum number of reference entries for the current picture is a statically defined value that is global for all layers. The problem with this approach is that reference layers use a different amount of space in the decoded picture buffer than output layers. For example, reference layers use space for picture reconstruction, and output layers use space for both picture reconstruction and storage pending output. Thus, a statically defined maximum number of reference entries selected to support a smaller amount of space used for the reference layer may be overly restrictive when applied to an output layer picture. Alternatively, a statically defined maximum number of reference entries selected for an output layer may provide more space than necessary to decode a reference layer picture, thus wasting memory resources. Examples of the present invention include a mechanism for constraining ref_pic_list_struct() to support different picture buffer usage for different types of layers. For example, a num_ref_entries syntax element may be included in ref_pic_list_struct(). num_ref_entries indicates the number of entries used for each picture.num_ref_entries may be constrained to maintain a range selected based on a maximum decoded picture buffer size. The maximum decoded picture buffer size differs depending on whether the layer is a reference layer or an output layer. Thus, constraining num_ref_entries based on the maximum decoded picture buffer size allows a different number of reference pictures to be employed for the output layer and the reference layer. Furthermore, the setofRefPics for each picture may be constrained by a different maximum decoded picture buffer size based on the layer instead of a static value that is global for all layers. By employing such constraints, a more efficient allocation of memory in the decoded picture buffer is supported, thus supporting high coding efficiency as more optimal memory usage encourages more efficient encoding. As a result, the functionality of the encoder and decoder is improved. Furthermore, coding efficiency is increased, thereby reducing the use of processor, memory, and / or network signaling resources in both the encoder and the decoder.

[0014] Optionally, in any of the aforementioned aspects, another implementation of the aspect provides that ref_pic_list_struct() is referenced according to listIdx and rplsIdx and is denoted as ref_pic_list_struct(listIdx, rplsIdx), and that num_ref_entries is denoted as num_ref_entries[listIdx][rplsIdx], and that num_ref_entries[listIdx][rplsIdx] specifies the number of entries in ref_pic_list_struct(listIdx, rplsIdx).

[0015] Optionally, in any of the aforementioned aspects, another implementation of the aspect provides that the number of pictures in the setOfRefPics referenced in the ref_pic_list_struct is constrained to be less than or equal to the maximum decoded picture buffer size minus 1.

[0016] Optionally, in any of the aforementioned aspects, another implementation of the aspect provides that ref_pic_list_struct() includes RefPicList[0] and RefPicList[1], and that setOfRefPics is a set-specific picture referenced by all entries in RefPicList[0] that have the same nuh_layer_id as the current picture and all entries in RefPicList[1] that have the same nuh_layer_id as the current picture.

[0017] Optionally, in any of the aforementioned aspects, another implementation of the aspect provides that setOfRefPics is the same set for all slices of each picture.

[0018] Optionally, in any of the aforementioned aspects, another implementation form of the aspect specifies that the bitstream includes dpb_parameters(), that the dpb_parameters() includes max_dec_pic_buffering_minus1, and that the maximum decoded picture buffer size corresponds to max_dec_pic_buffering_minus1.

[0019] Optionally, in any of the aforementioned aspects, another implementation form of the aspect provides that dpb_parameters() is included in the VPS or SPS.

[0020] In one embodiment, the present disclosure includes a video coding device comprising a processor, a receiver coupled to the processor, a memory coupled to the processor, and a transmitter coupled to the processor, wherein the processor, receiver, memory, and transmitter are configured to perform the method of any of the aforementioned aspects.

[0021] In one embodiment, the present disclosure includes a non-transitory computer-readable medium including a computer program product for use by a video coding device, the computer program product including computer-executable instructions stored on the non-transitory computer-readable medium that, when executed by a processor, cause the video coding device to perform a method of any of the aforementioned aspects.

[0022] In one embodiment, the present disclosure includes a decoder comprising receiving means for receiving a bitstream including a current picture and a ref_pic_list_struct() including num_ref_entries constrained to a range from 0 to a maximum decoded picture buffer size plus an offset, decoding means for decoding the current picture based on the ref_pic_list_struct() to generate a decoded picture, and forwarding means for forwarding the decoded picture for display as part of a decoded video sequence.

[0023] A picture may be coded according to intra prediction, inter prediction, and / or inter-layer prediction. In intra prediction, blocks in a picture are coded by referencing other blocks in the same picture. In inter prediction, blocks in a current picture are coded by referencing blocks in one or more other pictures. In inter-layer prediction, pictures are coded in layers, and blocks of a picture in an output layer are coded by referencing blocks of a picture in a reference layer. ref_pic_list_struct() may be employed to keep track of references between pictures, thereby supporting reconstruction of inter-predicted pictures. In some video coding systems, ref_pic_list_struct() includes the maximum number of reference entries that can be employed for the current picture. In such systems, the maximum number of reference entries for the current picture is a statically defined value that is global for all layers. The problem with this approach is that reference layers use a different amount of space in the decoded picture buffer than output layers. For example, reference layers use space for picture reconstruction, and output layers use space for both picture reconstruction and storage pending output. Thus, a statically defined maximum number of reference entries selected to support a smaller amount of space used for the reference layer may be overly restrictive when applied to an output layer picture. Alternatively, a statically defined maximum number of reference entries selected for an output layer may provide more space than necessary to decode a reference layer picture, thus wasting memory resources. Examples of the present invention include a mechanism for constraining ref_pic_list_struct() to support different picture buffer usage for different types of layers. For example, a num_ref_entries syntax element may be included in ref_pic_list_struct(). num_ref_entries indicates the number of entries used for each picture.num_ref_entries may be constrained to maintain a range selected based on a maximum decoded picture buffer size. The maximum decoded picture buffer size differs depending on whether the layer is a reference layer or an output layer. Thus, constraining num_ref_entries based on the maximum decoded picture buffer size allows a different number of reference pictures to be employed for the output layer and the reference layer. Furthermore, the setofRefPics for each picture may be constrained by a different maximum decoded picture buffer size based on the layer instead of a static value that is global for all layers. By employing such constraints, a more efficient allocation of memory in the decoded picture buffer is supported, thus supporting high coding efficiency as more optimal memory usage encourages more efficient encoding. As a result, the functionality of the encoder and decoder is improved. Furthermore, coding efficiency is increased, thereby reducing the use of processor, memory, and / or network signaling resources in both the encoder and the decoder.

[0024] Optionally, in any of the aforementioned aspects, another implementation of the aspect provides that the decoder is further configured to perform the method of any of the aforementioned aspects.

[0025] In one embodiment, the present disclosure includes an encoder comprising encoding means for encoding a current picture based on a reference picture into a bitstream, the ref_pic_list_struct() including num_ref_entries indicating the reference pictures and constrained to range from 0 to a maximum decoded picture buffer size plus an offset into the bitstream, and storage means for storing the bitstream for communication to a decoder.

[0026] A picture may be coded according to intra prediction, inter prediction, and / or inter-layer prediction. In intra prediction, blocks in a picture are coded by referencing other blocks in the same picture. In inter prediction, blocks in a current picture are coded by referencing blocks in one or more other pictures. In inter-layer prediction, pictures are coded in layers, and blocks of a picture in an output layer are coded by referencing blocks of a picture in a reference layer. ref_pic_list_struct() may be employed to keep track of references between pictures, thereby supporting reconstruction of inter-predicted pictures. In some video coding systems, ref_pic_list_struct() includes the maximum number of reference entries that can be employed for the current picture. In such systems, the maximum number of reference entries for the current picture is a statically defined value that is global for all layers. The problem with this approach is that reference layers use a different amount of space in the decoded picture buffer than output layers. For example, reference layers use space for picture reconstruction, and output layers use space for both picture reconstruction and storage pending output. Thus, a statically defined maximum number of reference entries selected to support a smaller amount of space used for the reference layer may be overly restrictive when applied to an output layer picture. Alternatively, a statically defined maximum number of reference entries selected for an output layer may provide more space than necessary to decode a reference layer picture, thus wasting memory resources. Examples of the present invention include a mechanism for constraining ref_pic_list_struct() to support different picture buffer usage for different types of layers. For example, a num_ref_entries syntax element may be included in ref_pic_list_struct(). num_ref_entries indicates the number of entries used for each picture.num_ref_entries may be constrained to maintain a range selected based on a maximum decoded picture buffer size. The maximum decoded picture buffer size differs depending on whether the layer is a reference layer or an output layer. Thus, constraining num_ref_entries based on the maximum decoded picture buffer size allows a different number of reference pictures to be employed for the output layer and the reference layer. Furthermore, the setofRefPics for each picture may be constrained by a different maximum decoded picture buffer size based on the layer instead of a static value that is global for all layers. By employing such constraints, a more efficient allocation of memory in the decoded picture buffer is supported, thus supporting high coding efficiency as more optimal memory usage encourages more efficient encoding. As a result, the functionality of the encoder and decoder is improved. Furthermore, coding efficiency is increased, thereby reducing the use of processor, memory, and / or network signaling resources in both the encoder and the decoder.

[0027] Optionally, in any of the aforementioned aspects, another implementation of the aspect provides that the encoder is further configured to perform the method of any of the aforementioned aspects.

[0028] For the sake of clarity, any one of the above-described embodiments may be combined with any one or more of the other above-described embodiments to form new embodiments within the scope of the present disclosure.

[0029] These and other features will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.

[0030] For a more complete understanding of the present disclosure, reference is now made to the following brief description taken in conjunction with the accompanying drawings and detailed description, in which like numerals represent like parts, and in which: [Brief description of the drawings]

[0031] [Figure 1] 1 is a flowchart of an exemplary method for coding a video signal. [Diagram 2] 1 is a schematic diagram of an example coding and decoding (codec) system for video coding. [Diagram 3] 1 is a schematic diagram illustrating an example video encoder. [Figure 4] 1 is a schematic diagram illustrating an exemplary video decoder. [Diagram 5] 1 is a schematic diagram illustrating an exemplary hypothetical reference decoder (HRD). [Figure 6] 1 is a schematic diagram illustrating an example multi-layer video sequence configured for inter-layer prediction. [Figure 7] 1 is a schematic diagram illustrating an exemplary reference picture list structure. [Figure 8] FIG. 2 is a schematic diagram illustrating an exemplary bitstream. [Figure 9] 1 is a schematic diagram of an example video coding device. [Figure 10] 1 is a flowchart of an example method for encoding a video sequence into a bitstream based on a reference picture list structure in which the number of reference entries is constrained according to a maximum decoded picture buffer size. [Figure 11] 1 is a flowchart of an example method for decoding a video sequence from a bitstream based on a reference picture list structure in which the number of reference entries is constrained according to a maximum decoded picture buffer size. [Figure 12] 1 is a schematic diagram of an example system for coding a video sequence into a bitstream based on a reference picture list structure in which the number of reference entries is constrained according to a maximum decoded picture buffer size. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0032] First, while an exemplary implementation of one or more embodiments is presented below, it should be understood that the disclosed system and / or method may be implemented using any number of currently known or existing technologies. The present disclosure should in no way be limited to the exemplary implementations, drawings, and technologies illustrated below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended claims along with the full scope of equivalents.

[0033] The following terms are defined as follows, unless used in the present specification in a contrary context. Specifically, the following definitions are intended to further clarify the present disclosure. However, terms may be explained differently in different contexts. Therefore, the following definitions should be considered as supplementary and not as limiting any other definitions of the explanations provided for such terms in the present specification.

[0034] A bitstream is a sequence of bits that includes video data that is compressed for transmission between an encoder and a decoder. An encoder is a device configured to compress video data into a bitstream using an encoding process. A decoder is a device configured to reconstruct video data into a bitstream for display using a decoding process. A picture is an array of luma samples and / or an array of chroma samples that make up a frame or a field thereof. A picture being encoded or decoded may be referred to as a current picture for clarity of description. A coded picture is a coded representation of a picture that includes a video coding layer (VCL) network abstraction layer (NAL) unit with a particular value of a NAL unit header layer identifier (nuh_layer_id) in an access unit (AU) and includes all coding tree units (CTUs) of the picture. A decoded picture is a picture that is generated by applying a decoding process to a coded picture. A slice is an integer number of complete tiles or an integer number of consecutive complete coding tree unit (CTU) rows (e.g., within a tile) of a picture that are exclusively contained in a single NAL unit (VCL NAL unit). A NAL unit is a syntax structure that contains data in the form of a raw byte sequence payload (RBSP), an indication of the type of data, interspersed with emulation prevention bytes if desired. A VCL NAL unit is a NAL unit that is coded to contain video data, such as a coded slice of a picture. A non-VCL NAL unit is a NAL unit that contains non-video data, such as syntax and / or parameters that support decoding the video data, performing conformance checks, or other operations. A layer is a set of VCL NAL units and associated non-VCL NAL units that share specified characteristics (e.g., a common resolution, frame rate, picture size, etc.) as indicated by a layer Id (identifier).The NAL unit header layer identifier (nuh_layer_id) is a syntax element that specifies the identifier of the layer that contains the NAL unit.

[0035] A hypothetical reference decoder (HRD) is a decoder model that runs on an encoder that checks the variability of the bitstream generated by the encoding process to verify conformance to specified constraints. Bitstream conformance testing is a test to determine whether the encoded bitstream conforms to a standard such as Versatile Video Coding (VVC). A video parameter set (VPS) is a syntax structure that contains parameters related to an entire video. A sequence parameter set (SPS) is a syntax structure that contains syntax elements that apply to zero or more entire coded layer video sequences (CLVS). A CLVS is a sequence of coded pictures that have the same nuh_layer_id value. A reference picture may be defined as a picture that is a short-term reference picture, a long-term reference picture, or an inter-layer reference picture. For example, a reference picture may be any picture that contains blocks and / or samples that are used to code blocks and / or samples of another picture by reference according to inter prediction. Reference picture list 0 (RefPicList[0]) is a reference picture list (e.g., containing a list of corresponding reference pictures) used for inter-prediction of a unidirectionally predicted (P) slice, or the first of two reference picture lists used for inter-prediction of a bidirectionally predicted (B) slice. Reference picture list 1 (RefPicList[1]) is a second reference picture list (e.g., used together with RefPicList[0]) used for inter-prediction of a B slice. Reference picture list syntax structure (ref_pic_list_struct()) is a syntax structure that includes RefPicList[0] and RefPicList[1]. A reference entry is an entry of a reference picture list that indicates a corresponding reference picture based on a reference index. A list index (listIdx) is an index that indicates a corresponding reference picture list, such as RefPicList[0] and / or RefPicList[1].The reference picture list structure index (rplsIdx) is an index indicating a reference entry in the corresponding reference picture list. The number of reference entries (num_ref_entries) is a syntax element indicating the number of reference entries in ref_pic_list_struct(). The set of reference pictures (setOfRefPics) is a set of unique pictures referenced by all entries in RefPicList[0] and / or RefPicList[1] that have the same nuh_layer_id value as the current picture. The decoded picture buffer (DPB) is a buffer configured to hold decoded pictures for reference, output reordering, or output delay, for example, in a decoder and / or HRD. The decoded picture buffer parameters syntax structure (dpb_parameters()) is a syntax structure that provides information about the DPB size, maximum picture reordering number, and maximum delay for one or more output layer sets (OLS). Maximum decoded picture buffer size is a derived variable that specifies the maximum required size of the DPB in units of picture storage buffer. Maximum decoded picture buffer-1 (max_dec_pic_buffering_minus1) is a syntax element that specifies the maximum required size of the DPB in units of picture storage buffer. An access unit (AU) is a set of coded pictures in different layers that are all associated with the same output time. A coded video sequence is a set of one or more coded pictures. A decoded video sequence is a set of one or more decoded pictures.

[0036] Acronyms used in this specification are: Access Unit (AU), Coding Tree Block (CTB), Coding Tree Unit (CTU), Coding Unit (CU), Coded Layer Video Sequence (CLVS), Coded Layer Video Sequence Start (CLVSS), Coded Video Sequence (CVS), Coded Video Sequence Start (CVSS), Joint Video Experts Team (JVET), Hypothetical Reference Decoder (HRD), Motion Constrained Tile Set (MCTS), Maximum Transmission Unit (MTU), Network Abstraction Layer (NAL), Output Layer Set (OLS), Operation Point (OP), Picture Order Count (POC), Random Access Point (RAP), Raw Byte Sequence Payload (RBSP), Sequence Parameter Set (SPS), Video Parameter Set (VPS), and Versatile Video Coding (VVC).

[0037] Many video compression techniques may be employed to reduce the size of a video file with minimal data loss. For example, video compression techniques may include performing spatial (e.g., intra-picture) prediction and / or temporal (e.g., inter-picture) prediction to reduce or remove data redundancy in a video sequence. For block-based video coding, a video slice (e.g., a video picture or a portion of a video picture) may be partitioned into several video blocks, which may also be referred to as tree blocks, coding tree blocks (CTBs), coding tree units (CTUs), coding units (CUs), and / or coding nodes. Video blocks in an intra-coded (I) slice of a picture are coded using spatial prediction with respect to reference samples in neighboring blocks in the same picture. Video blocks in an inter-coded unidirectionally predicted (P) or bidirectionally predicted (B) slice of a picture may be coded by employing spatial prediction with respect to reference samples in neighboring blocks in the same picture or temporal prediction with respect to reference samples in other reference pictures. A picture may be referred to as a frame and / or an image, and a reference picture may be referred to as a reference frame and / or a reference image. Spatial or temporal prediction results in a predictive block that represents an image block. The residual data represents pixel differences between the original image block and the predictive block. Thus, an inter-coded block is encoded according to a motion vector that points to a block of reference samples that form the predictive block, and the residual data that indicates the difference between the coded block and the predictive block. An intra-coded block is encoded according to an intra-coding mode and the residual data. For further compression, the residual data may be transformed from the pixel domain to a transform domain. These result in residual transform coefficients, which may be quantized. The quantized transform coefficients may initially be arranged in a two-dimensional array. The quantized transform coefficients may be scanned to generate a one-dimensional vector of transform coefficients.Entropy coding may be applied to achieve even further compression. Such video compression techniques are described in more detail below.

[0038] To ensure that the encoded video can be accurately decoded, the video is encoded and decoded according to a corresponding video coding standard. Video coding standards include International Telecommunication Union (ITU) Standardization Sector (ITU-T) H.261, International Organization for Standardization / International Electrotechnical Commission (ISO / IEC) Motion Picture Experts Group (MPEG)-1 Part 2, Advanced Video Coding (AVC), also known as ITU-T H.262 or ISO / IEC MPEG-2 Part 2, ITU-T H.263, ISO / IEC MPEG-4 Part 2, ITU-T H.264 or ISO / IEC MPEG-4 Part 10, and High Efficiency Video Coding (HEVC), also known as ITU-T H.265 or MPEG-H Part 2. AVC includes extensions such as Scalable Video Coding (SVC), Multiview Video Coding (MVC), Multiview Video Coding plus Depth (MVC+D), and Three-Dimensional (3D) AVC (3D-AVC). HEVC includes extensions such as Scalable HEVC (SHVC), Multiview HEVC (MV-HEVC), and 3D HEVC (3D-HEVC). The ITU-T and ISO / IEC Joint Video Experts Team (JVET) has begun development of a video coding standard called Versatile Video Coding (VVC). VVC is contained in working drafts (WDs), including JVET-O2001-v14.

[0039] A picture may be coded according to intra prediction, inter prediction, and / or inter-layer prediction. In intra prediction, blocks in a picture are coded by referencing other blocks in the same picture. In inter prediction, blocks in a current picture are coded by referencing blocks in one or more other pictures. In inter-layer prediction, pictures are coded in layers, and blocks of a picture in an output layer are coded by referencing blocks of a picture in a reference layer. A reference picture list syntax structure (ref_pic_list_struct()) may be employed to keep track of references between pictures, thereby supporting the reconstruction of inter-predicted pictures. In some video coding systems, ref_pic_list_struct() includes a maximum number of reference entries that can be employed for the current picture. In such systems, the maximum number of reference entries for the current picture is a statically defined value that is global for all layers. The problem with this approach is that reference layers use a different amount of space in the decoded picture buffer than the output layer. For example, the reference layer uses space for picture reconstruction, and the output layer uses space for both picture reconstruction and storage pending output. Thus, a statically defined maximum number of reference entries selected to support a smaller amount of space used for the reference layer may be overly restrictive when applied to pictures of the output layer. Alternatively, a statically defined maximum number of reference entries selected for the output layer may provide more space than necessary to decode pictures of the reference layer, thus wasting memory resources.

[0040] Disclosed herein is a mechanism for constraining ref_pic_list_struct() to support different picture buffer usage for different types of layers. For example, a number of reference entries (num_ref_entries) syntax element may be included in ref_pic_list_struct(). num_ref_entries indicates the number of entries used for each picture. num_ref_entries may be constrained to maintain a range selected based on a maximum decoded picture buffer size. The maximum decoded picture buffer size differs depending on whether the layer is a reference layer or an output layer. Thus, constraining num_ref_entries based on the maximum decoded picture buffer size allows different numbers of reference pictures to be employed for output layers and reference layers. Furthermore, the set of reference pictures for each picture (setofRefPics) may be constrained by different maximum decoded picture buffer sizes based on the layer instead of a static value that is global for all layers. By employing such constraints, a more efficient allocation of memory in the decoded picture buffer is supported, and thus high coding efficiency is supported as more optimal memory usage encourages more efficient encoding, resulting in improved encoder and decoder functionality. Furthermore, coding efficiency is increased, thereby reducing the use of processor, memory, and / or network signaling resources in both the encoder and decoder.

[0041] 1 is a flow chart of an exemplary operational method 100 of coding a video signal. Specifically, the video signal is encoded in an encoder. The encoding process compresses the video signal by using various mechanisms to reduce the video file size. The smaller file size allows the compressed video file to be transmitted to a user while reducing the associated bandwidth overhead. A decoder then decodes the compressed video file and reconstructs the original video signal for display to an end user. The decoding process generally mirrors the encoding process to allow the decoder to consistently reconstruct the video signal.

[0042] At step 101, a video signal is input to an encoder. For example, the video signal may be an uncompressed video file stored in memory. As another example, the video file may be captured by a video capture device, such as a video camera, and encoded to support live streaming of the video. The video file may include both audio and video components. The video component includes a series of image frames that, when viewed in sequence, give the visual impression of motion. The frames include pixels that are represented in terms of light, referred to herein as luma components (or luma samples), and color, referred to herein as chroma components (or color samples). In some examples, the frames may also include depth values ​​to support three-dimensional displays.

[0043] At step 103, the video is partitioned into several blocks. Partitioning involves subdividing pixels in each frame into square and / or rectangular blocks for compression. For example, in High Efficiency Video Coding (HEVC) (also known as H.265 and MPEG-H Part 2), a frame may first be partitioned into coding tree units (CTUs), which are blocks of a predefined size (e.g., 64 pixels by 64 pixels). A CTU contains both luma and chroma samples. A coding tree may be employed to partition a CTU into several blocks and then recursively subdivide the blocks until a configuration that supports further encoding is achieved. For example, the luma component of a frame may be subdivided until each block contains relatively homogenous illumination values. Furthermore, the chroma component of a frame may be subdivided until each block contains relatively homogenous color values. Thus, the partitioning mechanism differs depending on the content of the video frame.

[0044] At step 105, various compression mechanisms are employed to compress the image blocks partitioned at step 103. For example, inter prediction and / or intra prediction may be employed. Inter prediction is designed to take advantage of the fact that objects in a common scene tend to appear in successive frames. Thus, a block depicting an object in a reference frame does not need to be repeatedly described in adjacent frames. Specifically, an object such as a table may remain in a constant position across multiple frames. Thus, once a table is described, adjacent frames may refer back to the reference frame. Pattern matching mechanisms may be employed to match objects across multiple frames. Furthermore, objects may be represented that move across multiple frames, such as due to object movement or camera movement. As a specific example, a video may show a car moving across the screen across multiple frames. Motion vectors may be used to describe such movement. A motion vector is a two-dimensional vector that provides an offset from the coordinates of an object in a frame to the coordinates of the object in a reference frame. Hence, inter prediction may encode an image block in a current frame as a set of motion vectors that indicate an offset from a corresponding block in a reference frame.

[0045] Intra prediction encodes blocks within a common frame. Intra prediction exploits the fact that luma and chroma components tend to cluster within a frame. For example, a green patch in a part of a tree tends to be positioned adjacent to a similar patch of green. Intra prediction uses multiple directional prediction modes (e.g., 33 types in HEVC), planar mode, and direct current (DC) mode. These directional modes indicate that the current block is similar / same as the samples of neighboring blocks in the corresponding direction. Planar mode indicates that a series of blocks along a row / column (e.g., a plane) may be interpolated based on the neighboring blocks at the end of the row. Planar mode actually indicates a smooth transition of light / color across the row / column by using a relatively constant gradient in the changing values. DC mode is used for boundary smoothing and indicates that the block is similar / same as the average value associated with the samples of all neighboring blocks related to the angular direction of the directional prediction mode. Thus, intra prediction blocks can represent image blocks as various related prediction mode values ​​rather than actual values. Furthermore, inter prediction blocks can represent image blocks as motion vector values ​​rather than actual values. In either case, the prediction block may not exactly represent the image block in some cases. Any differences are contained within a residual block. To further compress the file, a transform may be applied to the residual block.

[0046] In step 107, various filtering techniques may be applied. In HEVC, filters are applied according to an in-loop filtering scheme. Block-based prediction, as described above, may result in blocky images at the decoder. Furthermore, the block-based prediction scheme may encode a block and then reconstruct the encoded block for later use as a reference block. The in-loop filtering scheme iteratively applies a noise suppression filter, a deblocking filter, an adaptive loop filter, and a sample adaptive offset (SAO) filter to the block / frame. These filters reduce such blocking artifacts, so that the encoded file can be accurately reconstructed. Furthermore, these filters reduce artifacts in the reconstructed reference block, so that the artifacts are less likely to cause further artifacts in subsequent blocks that are encoded based on the reconstructed reference block.

[0047] After the video signal has been partitioned, compressed, and filtered, the resulting data is encoded into a bitstream at step 109. The bitstream includes the data described above, as well as any signaling data desired to support proper video signal reconstruction at the decoder. For example, such data may include partition data, prediction data, residual blocks, and various flags that send coding instructions to the decoder. The bitstream may be stored in memory for transmission to the decoder upon request. The bitstream may also be broadcast and / or multicast to multiple decoders. Creation of the bitstream is an iterative process. Thus, steps 101, 103, 105, 107, and 109 may be performed sequentially and / or simultaneously across multiple frames and blocks. The order depicted in FIG. 1 is presented for clarity and ease of explanation and is not intended to limit the video coding process to a particular order.

[0048] The decoder receives the bitstream and begins the decoding process at step 111. Specifically, the decoder uses an entropy decoding scheme to convert the bitstream into corresponding syntax and video data. The decoder uses syntax data from the bitstream to determine the partition for the frame at step 111. The partition should match the result of the block partitioning at step 103. We now describe entropy encoding / decoding as employed at step 111. The encoder makes many choices in the compression process, such as selecting a block partitioning scheme from several possible choices based on the spatial positioning of values ​​in the input image. In signaling the exact choice, multiple bins may be used. As used herein, a bin is a binary value (e.g., a bit value that can change depending on the context) that is treated as a variable. Entropy coding allows the encoder to discard any options that are clearly infeasible for a particular case, leaving a set of acceptable options. Each acceptable option is then assigned a codeword. The length of the codeword is based on the number of allowable options (e.g., one bin for two options, two bins for three to four options, etc.). The encoder then encodes a codeword for the selected option. This scheme reduces the size of the codeword since it is desirable to uniquely indicate a selection from a small subset of allowable options, as opposed to uniquely indicating a selection from a potentially large set of all possible options. The decoder then decodes the selection by determining the set of allowable options in a manner similar to the encoder. By determining the set of allowable options, the decoder can read the codeword and determine the selection made by the encoder.

[0049] In step 113, the decoder performs block decoding. Specifically, the decoder employs an inverse transform to generate a residual block. The decoder then uses the residual block and a corresponding prediction block to reconstruct an image block according to the partitioning. The prediction block may include both intra-prediction blocks and inter-prediction blocks as generated in the encoder in step 105. The reconstructed image block is then positioned within a frame of the reconstructed video signal according to the partitioning data determined in step 111. The syntax for step 113 may also be signaled in the bitstream via entropy coding as described above.

[0050] At step 115, filtering is performed on the frames of the reconstructed video signal in a manner similar to step 107 at the encoder. For example, a noise suppression filter, a deblocking filter, an adaptive loop filter, and an SAO filter may be applied to the frames to remove blocking artifacts. After the frames are filtered, the video signal may be output to a display at step 117 for viewing by an end user.

[0051] FIG. 2 is a schematic diagram of an exemplary coding and decoding (codec) system 200 for video coding. Specifically, the codec system 200 provides functionality to support implementation of the operational method 100. The codec system 200 is generalized to depict components employed in both an encoder and a decoder. The codec system 200 receives and segments a video signal as described with respect to steps 101 and 103 of the operational method 100, resulting in a segmented video signal 201. The codec system 200 then compresses the segmented video signal 201 into a coded bitstream when operating as an encoder as described with respect to steps 105, 107, and 109 in the method 100. The codec system 200 generates an output video signal from the bitstream when operating as a decoder as described with respect to steps 111, 113, 115, and 117 of the operational method 100. Codec system 200 includes a general coder control component 211, a transform scaling and quantization component 213, an intra picture estimation component 215, an intra picture prediction component 217, a motion compensation component 219, a motion estimation component 221, a scaling and inverse transform component 229, a filter control analysis component 227, an in-loop filter component 225, a decoded picture buffer component 223, and a header formatting and context adaptive binary arithmetic coding (CABAC) component 231. Such components are coupled as shown. In FIG. 2, the black lines indicate the movement of data to be encoded / decoded, and the dashed lines indicate the movement of control data that controls the operation of the other components. The components of codec system 200 may all be present in an encoder. A decoder may include a subset of the components of codec system 200.For example, the decoder may include an intra-picture prediction component 217, a motion compensation component 219, a scaling and inverse transform component 229, an in-loop filter component 225, and a decoded picture buffer component 223. These components are now described.

[0052] The partitioned video signal 201 is a captured video sequence partitioned into several blocks of pixels by a coding tree. The coding tree employs various partitioning modes to subdivide the blocks of pixels into smaller blocks of pixels. These blocks may then be further subdivided into smaller blocks. The blocks may be referred to as nodes of the coding tree. Larger parent nodes are partitioned into smaller child nodes. The number of times a node is subdivided is referred to as the depth of the node / coding tree. The partitioned blocks may be included in a coding unit (CU) in some cases. For example, a CU may be a sub-part of a CTU that includes a luma block, a red-difference chroma (Cr) block, and a blue-difference chroma (Cb) block, along with corresponding syntax instructions for the CU. The partitioning modes may include a binary tree (BT), a ternary tree (TT), and a quad tree (QT), which are employed to partition a node into two, three, or four child nodes of various shapes, respectively, depending on the partitioning mode employed. The segmented video signal 201 is forwarded to a general coder control component 211, a transform scaling and quantization component 213, an intra-picture estimation component 215, a filter control analysis component 227, and a motion estimation component 221 for compression.

[0053] The general coder control component 211 is configured to make decisions related to the coding of images of a video sequence into a bitstream according to application constraints. For example, the general coder control component 211 manages the optimization of bitrate / bitstream size versus reconstruction quality. Such decisions may be based on storage space / bandwidth availability and image resolution requirements. The general coder control component 211 also manages buffer utilization in light of transmission rate to mitigate buffer under-run and over-run issues. To manage these issues, the general coder control component 211 manages segmentation, prediction, and filtering by other components. For example, the general coder control component 211 may dynamically increase compression complexity to increase resolution and bandwidth usage, or decrease compression complexity to decrease resolution and bandwidth usage. Thus, the general coder control component 211 controls other components of the codec system 200 to balance video signal reconstruction quality and bitrate considerations. The general coder control component 211 creates control data that controls the operation of other components. The control data is also forwarded to the header formatting and CABAC component 231 and encoded into the bitstream to signal parameters for decoding at the decoder.

[0054] The partitioned video signal 201 is also sent to a motion estimation component 221 and a motion compensation component 219 for inter prediction. A frame or slice of the partitioned video signal 201 may be divided into multiple video blocks. The motion estimation component 221 and the motion compensation component 219 perform inter predictive coding of the received video blocks with respect to one or more blocks in one or more reference frames to perform temporal prediction. The codec system 200 may perform multiple coding passes to, for example, select an appropriate coding mode for each block of video data.

[0055] The motion estimation component 221 and the motion compensation component 219 may be highly integrated, but are illustrated separately for conceptual purposes. Motion estimation performed by the motion estimation component 221 is a process of generating motion vectors, which estimate motion with respect to a video block. A motion vector may indicate, for example, the displacement of a coded object with respect to a predictive block. A predictive block is a block that is found to match well with a block to be coded with respect to pixel differences. A predictive block may also be referred to as a reference block. Such pixel differences may be determined by sum of absolute differences (SAD), sum of squared differences (SSD), or other difference metrics. HEVC employs several coded objects, including CTUs, coding tree blocks (CTBs), and CUs. For example, a CTU may be divided into CTBs, which may then be divided into CBs to be included in a CU. A CU may be encoded as a prediction unit (PU) that includes prediction data and / or a transform unit (TU) that includes transformed residual data for the CU. The motion estimation component 221 generates the motion vectors, PUs, and TUs by using a rate-distortion analysis as part of a rate-distortion optimization process. For example, the motion estimation component 221 may determine multiple reference blocks, multiple motion vectors, etc. for a current block / frame and select the reference block, motion vector, etc. with the best rate-distortion characteristics. The best rate-distortion characteristics balance both the quality of the video reconstruction (e.g., the amount of data lost due to compression) and the coding efficiency (e.g., the size of the final encoding).

[0056] In some examples, the codec system 200 may calculate values ​​for sub-integer pixel positions of reference pictures stored in the decoded picture buffer component 223. For example, the video codec system 200 may interpolate values ​​for quarter-pixel positions, eighth-pixel positions, or other fractional pixel positions of the reference pictures. Thus, the motion estimation component 221 may perform motion searches for full-pixel positions and fractional pixel positions and output motion vectors with fractional pixel accuracy. The motion estimation component 221 calculates motion vectors for PUs of video blocks in inter-coded slices by comparing the positions of the PUs with the positions of predictive blocks of the reference pictures. The motion estimation component 221 outputs the calculated motion vectors as header formatting for encoding and motion to the motion compensation component 219 and motion data to the CABAC component 231.

[0057] The motion compensation performed by the motion compensation component 219 may involve fetching or generating a predictive block based on a motion vector determined by the motion estimation component 221. Again, the motion estimation component 221 and the motion compensation component 219 may be functionally integrated in some examples. Upon receiving a motion vector for the PU of the current video block, the motion compensation component 219 may locate the predictive block to which the motion vector points. A residual video block is then formed by subtracting pixel values ​​of the predictive block from pixel values ​​of the current video block being coded to form pixel difference values. In general, the motion estimation component 221 performs motion estimation with respect to the luma component, and the motion compensation component 219 uses the motion vector calculated based on the luma component for both the chroma and luma components. The predictive block and the residual block are forwarded to the transform scaling and quantization component 213.

[0058] The partitioned video signal 201 is also sent to an intra-picture estimation component 215 and an intra-picture prediction component 217. As with the motion estimation component 221 and the motion compensation component 219, the intra-picture estimation component 215 and the intra-picture prediction component 217 may be highly integrated, but are illustrated separately for conceptual purposes. The intra-picture estimation component 215 and the intra-picture prediction component 217 intra-predict a current block with respect to blocks in a current frame, as an alternative to the inter-prediction performed by the motion estimation component 221 and the motion compensation component 219 between frames, as described above. In particular, the intra-picture estimation component 215 determines an intra-prediction mode to use to encode the current block. In some examples, the intra-picture estimation component 215 selects an appropriate intra-prediction mode to encode the current block from a plurality of tested intra-prediction modes. The selected intra-prediction mode is then forwarded to the header formatting and CABAC component 231 for encoding.

[0059] For example, the intra picture estimation component 215 calculates rate-distortion values ​​using a rate-distortion analysis for various tested intra prediction modes and selects an intra prediction mode with the best rate-distortion characteristics from among the tested modes. The rate-distortion analysis generally determines the amount of distortion (or error) between an encoded block and an original unencoded block that was encoded to generate the encoded block, as well as the bit rate (e.g., number of bits) used to generate the encoded block. The intra picture estimation component 215 calculates ratios from the distortion and rate for various encoded blocks to determine which intra prediction mode exhibits the best rate-distortion value for the block. In addition, the intra picture estimation component 215 may be configured to code a depth block of a depth map using a depth modeling mode (DMM) based on a rate-distortion optimization (RDO).

[0060] The intra picture prediction component 217 may generate a residual block from the prediction block based on a selected intra prediction mode determined by the intra picture estimation component 215 when implemented in an encoder, or may read the residual block from a bitstream when implemented in a decoder. The residual block includes value differences between the prediction block and the original block, represented as a matrix. The residual block is then forwarded to the transform scaling and quantization component 213. The intra picture estimation component 215 and the intra picture prediction component 217 may operate on both the luma and chroma components.

[0061] The transform scaling and quantization component 213 is configured to further compress the residual block. The transform scaling and quantization component 213 applies a transform, such as a discrete cosine transform (DCT), a discrete sine transform (DST), or a conceptually similar transform, to the residual block to generate a video block including residual transform coefficient values. A wavelet transform, an integer transform, a subband transform, or other types of transforms could also be used. The transform may convert the residual information from the pixel value domain to a transform domain, such as the frequency domain. The transform scaling and quantization component 213 is also configured to scale the transformed residual information, for example based on frequency. Such scaling involves applying a scale factor to the residual information such that different frequency information is quantized with different granularity, which may affect the final visual quality of the reconstructed video. The transform scaling and quantization component 213 is also configured to quantize the transform coefficients to further reduce the bit rate. The quantization process may reduce the bit depth associated with some or all of the coefficients. The degree of quantization may be changed by adjusting a quantization parameter. In some examples, the transform scaling and quantization component 213 may then perform a scan of a matrix containing the quantized transform coefficients, which are forwarded to the header formatting and CABAC component 231 and encoded into the bitstream.

[0062] The scaling and inverse transform component 229 applies the inverse operations of the transform scaling and quantization component 213 to support motion estimation. The scaling and inverse transform component 229 applies inverse scaling, transformation, and / or quantization to reconstruct a residual block in the pixel domain, for example, for later use as a reference block that may become a predictive block for another current block. The motion estimation component 221 and / or the motion compensation component 219 may calculate a reference block by adding the residual block back to the corresponding predictive block for use in motion estimation of a later block / frame. A filter is applied to the reconstructed reference block, thereby mitigating artifacts created during scaling, quantization, and transformation. Such artifacts may otherwise cause inaccurate predictions (and create additional artifacts) when subsequent blocks are predicted.

[0063] The filter control analysis component 227 and the in-loop filter component 225 apply filters to the residual block and / or the reconstructed image block. For example, the transformed residual block from the scaling and inverse transform component 229 may be combined with a corresponding prediction block from the intra-picture prediction component 217 and / or the motion compensation component 219 to reconstruct the original image block. A filter may then be applied to the reconstructed image block. In some examples, the filter may be applied to the residual block instead. As with the other components of FIG. 2, the filter control analysis component 227 and the in-loop filter component 225 are highly integrated and may be implemented together, but are depicted separately for conceptual purposes. The filters applied to the reconstructed reference block are applied to a particular spatial region and include multiple parameters to adjust how such filters are applied. The filter control analysis component 227 analyzes the reconstructed reference block to determine where such filters should be applied and sets the corresponding parameters. Such data is forwarded to the header formatting and CABAC component 231 as filter control data for encoding. The in-loop filter component 225 applies such filters based on the filter control data. The filters may include deblocking filters, noise suppression filters, SAO filters, and adaptive loop filters. Such filters may be applied in the spatial / pixel domain (e.g., on reconstructed pixel blocks) or in the frequency domain, depending on the example.

[0064] When operating as an encoder, the filtered reconstructed image blocks, residual blocks, and / or predictive blocks are stored in the decoded picture buffer component 223 for later use in motion estimation as described above. When operating as a decoder, the decoded picture buffer component 223 stores the reconstructed and filtered blocks and forwards them to a display as part of the output video signal. The decoded picture buffer component 223 may be any memory device capable of storing predictive blocks, residual blocks, and / or reconstructed image blocks.

[0065] The header formatting and CABAC component 231 receives data from various components of the codec system 200 and encodes such data into a coded bitstream for transmission towards a decoder. In particular, the header formatting and CABAC component 231 generates various headers to encode control data, such as general control data and filter control data. In addition, prediction data, including intra prediction data and motion data, as well as residual data in the form of quantized transform coefficient data, are all encoded into the bitstream. The final bitstream contains all the information desired for a decoder to reconstruct the original partitioned video signal 201. Such information may also include an intra prediction mode index table (also referred to as a codeword mapping table), definitions of encoding contexts for various blocks, indications of the most likely intra prediction modes, indications of partition information, etc. Such data may be encoded by employing entropy coding. For example, the information may be encoded by employing Context-Adaptive Variable Length Coding (CAVLC), CABAC, Syntax-Based Context-Adaptive Binary Arithmetic Coding (SBAC), Probability Interval Partitioning Entropy (PIPE) coding, or another entropy coding technique. Following entropy coding, the coded bitstream may be transmitted to another device (e.g., a video decoder) or archived for later transmission or removal.

[0066] 3 is a block diagram illustrating an example video encoder 300. The video encoder 300 may be employed to implement the encoding functionality of the codec system 200 and / or to implement steps 101, 103, 105, 107, and / or 109 of the method of operation 100. The encoder 300 segments an input video signal, resulting in a segmented video signal 301, which is substantially similar to the segmented video signal 201. The segmented video signal 301 is then compressed and encoded into a bitstream by components of the encoder 300.

[0067] Specifically, the partitioned video signal 301 is forwarded to an intra-picture prediction component 317 for intra prediction. The intra-picture prediction component 317 may be substantially similar to the intra-picture estimation component 215 and the intra-picture prediction component 217. The partitioned video signal 301 is also forwarded to a motion compensation component 321 for inter prediction based on a reference block in a decoded picture buffer component 323. The motion compensation component 321 may be substantially similar to the motion estimation component 221 and the motion compensation component 219. The prediction block and the residual block from the intra-picture prediction component 317 and the motion compensation component 321 are forwarded to a transform and quantization component 313 for transforming and quantizing the residual block. The transform and quantization component 313 may be substantially similar to the transform scaling and quantization component 213. The transformed and quantized residual blocks and the corresponding prediction blocks (along with associated control data) are forwarded to an entropy coding component 331 for coding into the bitstream. The entropy coding component 331 may be substantially similar to the header formatting and CABAC component 231.

[0068] The transformed and quantized residual block and / or the corresponding prediction block are transferred from the transform and quantization component 313 to the inverse transform and quantization component 329 for reconstructing into a reference block and for use by the motion compensation component 321. The inverse transform and quantization component 329 may be substantially similar to the scaling and inverse transform component 229. An in-loop filter in the in-loop filter component 325 is also applied to the residual block and / or the reconstructed reference block, depending on the example. The in-loop filter component 325 may be substantially similar to the filter control analysis component 227 and the in-loop filter component 225. The in-loop filter component 325 may comprise multiple filters as described with respect to the in-loop filter component 225. The filtered block is then stored in the decoded picture buffer component 323 for use as a reference block by the motion compensation component 321. The decoded picture buffer component 323 may be substantially similar to the decoded picture buffer component 223.

[0069] 4 is a block diagram illustrating an example video decoder 400. The video decoder 400 may be employed to implement the decoding functionality of the codec system 200 and / or to implement steps 111, 113, 115, and / or 117 of the method of operation 100. The decoder 400 receives a bitstream, for example, from the encoder 300, and generates a reconstructed output video signal based on the bitstream for display to an end user.

[0070] The bitstream is received by the entropy decoding component 433. The entropy decoding component 433 is configured to implement an entropy decoding scheme, such as CAVLC, CABAC, SBAC, PIPE coding, or other entropy coding techniques. For example, the entropy decoding component 433 may employ header information to provide a context for interpreting additional data encoded as codewords in the bitstream. The decoded information includes any desired information for decoding a video signal, such as general control data, filter control data, partition information, motion data, prediction data, and quantized transform coefficients from the residual block. The quantized transform coefficients are forwarded to the inverse transform and quantization component 429 for reconstruction into the residual block. The inverse transform and quantization component 429 may be similar to the inverse transform and quantization component 329.

[0071] The reconstructed residual block and / or predictive block are forwarded to the intra-picture prediction component 417 for reconstructing into an image block based on an intra-prediction operation. The intra-picture prediction component 417 may be similar to the intra-picture estimation component 215 and the intra-picture prediction component 217. Specifically, the intra-picture prediction component 417 employs a prediction mode to identify the location of a reference block in a frame and applies the residual block to the result to reconstruct an intra-predictive image block. The reconstructed intra-predictive image block and / or residual block and the corresponding inter-predictive data are forwarded to the decoded picture buffer component 423 via the in-loop filter component 425, which may be substantially similar to the decoded picture buffer component 223 and the in-loop filter component 225, respectively. The in-loop filter component 425 filters the reconstructed image block, the residual block and / or the predictive block, and such information is stored in the decoded picture buffer component 423. The reconstructed image block from the decoded picture buffer component 423 is forwarded to the motion compensation component 421 for inter prediction. The motion compensation component 421 may be substantially similar to the motion estimation component 221 and / or the motion compensation component 219. Specifically, the motion compensation component 421 employs a motion vector from a reference block to generate a prediction block and applies a residual block to the result to reconstruct an image block. The resulting reconstructed block may also be forwarded to the decoded picture buffer component 423 via the in-loop filter component 425. The decoded picture buffer component 423 continues to store additional reconstructed image blocks, which may be reconstructed into frames via the partition information. Such frames may be placed into a sequence. The sequence is output to a display as a reconstructed output video signal.

[0072] 5 is a schematic diagram illustrating an exemplary HRD 500. The HRD 500 may be employed in the codec system 200 and / or an encoder, such as the encoder 300. The HRD 500 may check the bitstream created in step 109 of the method 100 before the bitstream is forwarded to a decoder, such as the decoder 400. In some examples, the bitstream may be continuously forwarded through the HRD 500 as the bitstream is encoded. If a portion of the bitstream fails to conform to an associated constraint, the HRD 500 may inform the encoder of such failure and cause the encoder to re-encode the corresponding section of the bitstream by a different mechanism.

[0073] The HRD 500 comprises a virtual stream scheduler (HSS) 541. The HSS 541 is a component configured to execute a virtual distribution mechanism. The virtual distribution mechanism is used to check the conformance of a bitstream or a decoder with respect to the timing and data flow of the bitstream 551 input to the HRD 500. For example, the HSS 541 may receive the bitstream 551 output from an encoder and manage a conformance test process on the bitstream 551. In a particular example, the HSS 541 may control the rate at which coded pictures move through the HRD 500 and verify that the bitstream 551 does not contain non-conforming data.

[0074] The HSS 541 can forward the bitstream 551 to the CPB 543 at a predefined rate. The HRD 500 can manage data in a decoding unit (DU) 553. The DU 553 is an access unit (AU) or a subset of AUs and associated non-video coding layer (VCL) network abstraction layer (NAL) units. Specifically, an AU includes one or more pictures associated with an output time. For example, an AU may include a single picture in a single-layer bitstream and a picture for each layer in a multi-layer bitstream. Each picture of an AU may be divided into slices, each of which is included in a corresponding VCL NAL unit. Thus, the DU 553 may include one or more pictures, one or more slices of a picture, or a combination thereof. Also, parameters used to decode the AU / DU, picture, and / or slice may be included in the non-VCL NAL unit. Hence, the DU 553 includes non-VCL NAL units that include data necessary to support decoding the VCL NAL units in the DU 553. The CPB 543 is a first-in, first-out buffer within the HRD 500. The CPB 543 contains the DUs 553 that contain video data in decoding order. The CPB 543 stores video data for use during bitstream conformance verification.

[0075] The CPB 543 forwards the DU 553 to the decoding process component 545. The decoding process component 545 is a component that conforms to the VVC standard. For example, the decoding process component 545 may emulate the decoder 400 employed by the end user. The decoding process component 545 decodes the DU 553 at a rate that can be achieved by an exemplary end user's decoder. If the decoding process component 545 cannot decode the DU 553 fast enough to prevent overflow of the CPB 543 (or prevent buffer underrun), the bitstream 551 is not standard-conforming and should be re-encoded.

[0076] The decoding process component 545 decodes the DU 553 and creates a decoded DU 555. The decoded DU 555 contains the decoded picture. The decoded DU 555 is forwarded to the DPB 547. The DPB 547 may be substantially similar to the decoded picture buffer components 223, 323, and / or 423. To support inter-prediction, pictures marked for use as reference pictures 556 obtained from the decoded DU 555 are returned to the decoding process component 545 to support further decoding. The DPB 547 outputs the decoded video sequence as a series of pictures 557. The pictures 557 are reconstructed pictures that generally mirror the pictures encoded by the encoder into the bitstream 551.

[0077] Picture 557 is forwarded to output cropping component 549, which is configured to apply an adaptive cropping window to picture 557. This results in output cropped picture 559. Output cropped picture 559 is a fully reconstructed picture. Thus, output cropped picture 559 mimics what an end user would see after decoding bitstream 551. Therefore, at the encoder side, output cropped picture 559 can be reviewed to ensure that the encoding is satisfactory.

[0078] The HRD 500 is initialized based on HRD parameters in the bitstream 551. For example, the HRD 500 may read the HRD parameters from the VPS, SPS, and / or SEI messages. The HRD 500 may then perform a conformance test operation on the bitstream 551 based on the information in such HRD parameters. As a specific example, the HRD 500 may determine one or more CPB delivery schedules from the HRD parameters. The delivery schedules specify the timing for the delivery of video data to and / or from memory locations such as the CPB and / or DPB. Thus, the CPB delivery schedules specify the timing for the delivery of AUs, DUs 553, and / or pictures to / from the CPB 543. It should be noted that the HRD 500 may adopt a DPB delivery schedule for the DPB 547, which is similar to the CPB delivery schedule.

[0079] Video may be coded into different layers and / or OLSs for use by decoders with various levels of hardware capabilities, and also for various network conditions. The CPB delivery schedule is selected to reflect these issues. Thus, the upper layer sub-bitstreams are specified for optimal hardware and network conditions, and thus the upper layers may receive one or more CPB delivery schedules that employ large amounts of memory in the CPB 543 and short delays for the transfer of the DU 553 towards the DPB 547. Similarly, the lower layer sub-bitstreams are specified for limited decoder hardware capabilities and / or poor network conditions. Thus, the lower layers may receive one or more CPB delivery schedules that employ small amounts of memory in the CPB 543 and longer delays for the transfer of the DU 553 towards the DPB 547. The OLSs, layers, sub-layers, or combinations thereof may then be tested according to the corresponding delivery schedules to ensure that the resulting sub-bitstreams can be correctly decoded under the conditions expected for the sub-bitstreams. Thus, the HRD parameters in the bitstream 551 may indicate the CPB delivery schedule and may further include sufficient data to enable the HRD 500 to determine the CPB delivery schedule and correlate the CPB delivery schedule to a corresponding OLS, layer, and / or sublayer.

[0080] 6 is a schematic diagram illustrating an example multi-layer video sequence 600 configured to perform inter-layer prediction 621. The multi-layer video sequence 600 may be encoded by an encoder, such as the codec system 200 and / or the encoder 300, and decoded by a decoder, such as the codec system 200 and / or the decoder 400, for example, according to the method 100. Furthermore, the multi-layer video sequence 600 may be checked for conformance by an HRD, such as the HRD 500. The multi-layer video sequence 600 is included to illustrate an example application for layers in a coded video sequence. The multi-layer video sequence 600 is any video sequence employing multiple layers, such as layer N 631 and layer N+1 632.

[0081] In one example, the multi-layer video sequence 600 may employ inter-layer prediction 621. Inter-layer prediction 621 is applied between pictures 611, 612, 613, and 614 and pictures 615, 616, 617, and 618 in different layers. In the illustrated example, pictures 611, 612, 613, and 614 are part of layer N+1 632, and pictures 615, 616, 617, and 618 are part of layer N 631. A layer, such as layer N 631 and / or layer N+1 632, is a group of pictures that are all associated with similar values ​​of characteristics such as similar size, quality, resolution, signal-to-noise ratio, capacity, etc. A layer may be formally defined as a set of VCL NAL units and associated non-VCL NAL units. A VCL NAL unit is a NAL unit that is coded to contain video data, such as a coded slice of a picture. A non-VCL NAL unit is a NAL unit that contains non-video data, such as syntax and / or parameters that support decoding video data, performing conformance checks, or other operations.

[0082] In the illustrated example, layer N+1 632 is associated with a larger image size than layer N 631. Thus, pictures 611, 612, 613, and 614 in layer N+1 632 have a larger picture size (e.g., larger height and width, and therefore more samples) than pictures 615, 616, 617, and 618 in layer N 631 in this example. However, such pictures may be separated between layer N+1 632 and layer N 631 by other characteristics. Although only two layers, layer N+1 632 and layer N 631, are illustrated, a set of pictures may be separated into any number of layers based on associated characteristics. Layer N+1 632 and layer N 631 may also be indicated by a layer Id. A layer Id is an item of data associated with a picture and indicates that the picture is part of the layer being indicated. Thus, each picture 611-618 may be associated with a corresponding layer Id, thereby indicating which layer N+1 632 or layer N 631 contains the corresponding picture. For example, the layer Id may include a NAL unit header layer identifier (nuh_layer_id), which is a syntax element that specifies an identifier of a layer that contains a NAL unit (e.g., containing slices and / or parameters of a picture within a layer). A layer associated with a lower quality / bitstream size, such as layer N 631, is generally assigned a lower layer Id and is referred to as a lower layer. Furthermore, a layer associated with a higher quality / bitstream size, such as layer N+1 632, is generally assigned a higher layer Id and is referred to as an upper layer.

[0083] Pictures 611-618 in different layers 631-632 are configured to be displayed in alternative ways. As a specific example, a decoder may decode and display picture 615 at the current display time if a smaller picture is desired, or the decoder may decode and display picture 611 at the current display time if a larger picture is desired. Thus, pictures 611-614 in higher layer N+1 632 contain substantially the same image data as corresponding pictures 615-618 in lower layer N 631 (despite differences in picture size). Specifically, picture 611 contains substantially the same image data as picture 615, picture 612 contains substantially the same image data as picture 616, and so on.

[0084] Pictures 611-618 may be coded with reference to other pictures 611-618 in the same layer N 631 or N+1 632. Coding a picture with reference to another picture in the same layer results in inter prediction 623. Inter prediction 623 is indicated by a solid arrow. For example, picture 613 may be coded by employing inter prediction 623 using one or two of pictures 611, 612, and / or 614 in layer N+1 632 as references, one picture being referenced for unidirectional inter prediction and / or two pictures being referenced for bidirectional inter prediction. For example, picture 617 may be coded by employing inter prediction 623 using one or two of pictures 615, 616, and / or 618 in layer N 631 as references, one picture being referenced for unidirectional inter prediction and / or two pictures being referenced for bidirectional inter prediction. When a picture is used as a reference for another picture in the same layer when performing inter prediction 623, the picture may be referred to as a reference picture. For example, picture 612 may be a reference picture used to code picture 613 according to inter prediction 623. Inter prediction 623 may also be referred to as intra-layer prediction in a multi-layer context. Hence, inter prediction 623 is a mechanism for coding samples of a current picture by referencing indicated samples in a reference picture different from the current picture when the reference picture and the current picture are in the same layer.

[0085] Pictures 611-618 may also be coded by referencing other pictures 611-618 in different layers. This process is known as inter-layer prediction 621 and is indicated by dashed arrows. Inter-layer prediction 621 is a mechanism for coding samples of a current picture by referencing indicated samples in reference pictures where the current picture and the reference picture are in different layers and therefore have different layer IDs. For example, a picture in a lower layer N 631 may be used as a reference picture for coding a corresponding picture in an upper layer N+1 632. As a specific example, picture 611 may be coded by referencing picture 615 according to inter-layer prediction 621. In such a case, picture 615 is used as an inter-layer reference picture. An inter-layer reference picture is a reference picture used for inter-layer prediction 621. In most cases, inter-layer prediction 621 is constrained such that a current picture, such as picture 611, can only use inter-layer reference pictures that are included in the same AU and are in a lower layer, such as picture 615. When multiple layers (eg, more than two) are available, inter-layer prediction 621 can encode / decode the current picture based on multiple inter-layer reference pictures at a lower level than the current picture.

[0086] A video encoder may employ the multi-layer video sequence 600 to encode pictures 611-618 via many different combinations and / or permutations of inter-prediction 623 and inter-layer prediction 621. For example, picture 615 may be coded according to intra-prediction. Pictures 616-618 may then be coded according to inter-prediction 623 by using picture 615 as a reference picture. Furthermore, picture 611 may be coded according to inter-layer prediction 621 by using picture 615 as an inter-layer reference picture. Pictures 612-614 may then be coded according to inter-prediction 623 by using picture 611 as a reference picture. Hence, a reference picture may serve as both a single layer reference picture and an inter-layer reference picture for different coding mechanisms. By coding the upper layer N+1 632 picture based on the lower layer N 631 picture, the upper layer N+1 632 can avoid employing intra prediction, which has much lower coding efficiency than inter prediction 623 and inter-layer prediction 621. Hence, the coding inefficiency of intra prediction can be limited to the smallest / lowest quality pictures and thus limited to coding a minimum amount of video data. Pictures used as reference pictures and / or inter-layer reference pictures may be indicated in entries of a reference picture list included in a reference picture list structure.

[0087] It should be noted that layers, such as layer N+1 632 and layer N 631, may be included in an output layer set (OLS). An OLS is a set of one or more layers, with at least one layer being an output layer. For example, layer N 631 may be included in a first OLS, and layer N 631 and layer N-1 632 may both be included in a second OLS. This allows different OLSs to be sent to different decoders depending on the decoder-side conditions. For example, a sub-bitstream extraction process may remove data unrelated to the target OLS from the multi-layer video sequence 600 before the target OLS is sent to the decoder. Hence, an encoded copy of the multi-layer video sequence 600 may be stored in the encoder (or corresponding content server), and various OLSs may be extracted and sent to different decoders upon request.

[0088] Also note that different layers, such as layer N+1 632 and layer N 631, may be associated with different memory requirements in the HRD and / or decoder. Specifically, decoded pictures in the DPB may be marked as long-term reference use, short-term reference use, or unused for reference. The reference picture marking process may be invoked each time a new picture is decoded (e.g., when a new picture becomes the current picture). Specifically, the reference picture marking process may be applied to each picture in the DPB each time a decoding process is applied to a new picture. Pictures marked as unused for reference are stored until the picture can be output or immediately removed from the DPB if the picture is not scheduled for output. Thus, layers, such as layer N+1 632 and / or layer N 631, which are output layers, use the DPB space to hold reference pictures and hold pictures until such pictures can be output. However, layers such as layer N+1 632 and / or layer N 631 that are used only as reference layers for inter-layer prediction 621 (not output layers) only hold pictures used for reference. Non-output layers do not need to hold pictures marked unused for reference because pictures from non-output layers are never output. Hence, output layers employ larger DPB space than layers that are used only for reference (e.g., non-output layers). For example, output layers may employ approximately twice the memory space in the DPB than non-output reference layers.

[0089] 7 is a schematic diagram illustrating an example reference picture list (RPL) structure 700. The RPL structure 700 may be employed to store indications of reference pictures and / or inter-layer reference pictures used in inter prediction 623 and / or inter-layer prediction 621 when coding a video sequence such as the multi-layer video sequence 600. Thus, the RPL structure 700 may be employed by the codec system 200, the encoder 300, and / or the decoder 400 when performing the method 100. Additionally, the RPL structure 700 may be employed by an HRD, such as the HRD 500, when performing a conformance test on a bitstream including the encoded video sequence.

[0090] The RPL structure 700 is an addressable syntax structure that includes multiple reference picture lists, such as reference picture list 0 (RefPicList[0]) 711 and reference picture list 1 (RefPicList[1]) 712. The RPL structure 700 may be stored in a sequence parameter set (SPS), a picture parameter set (PPS), and / or a slice header of a bitstream, depending on the example. The reference picture lists, such as RefPicList[0] 711 and RefPicList[1] 712, are lists of reference pictures used for inter prediction and / or inter-layer prediction. RefPicList[0] 711 and RefPicList[1] 712 may each include multiple entries 715. The reference picture list structure entries 715 are addressable locations within the RPL structure 700 that indicate the reference pictures associated with a reference picture list, such as RefPicList[0] 711 and / or RefPicList[1] 712. Each entry 715 may include a picture order count (POC) value (or other pointer value) that references a picture used for inter prediction. Specifically, references to pictures used by unidirectional inter prediction are stored in RefPicList[0] 711, and references to pictures used by bidirectional inter prediction are stored in both RefPicList[0] 711 and RefPicList[1] 712. For example, unidirectional inter prediction may code a block of the current picture by referencing a block in one reference picture indicated by RefPicList[0] 711. Furthermore, bidirectional inter prediction may code a block of the current picture by referencing a block in one reference picture indicated by RefPicList[0] 711 and a block in one reference picture indicated by RefPicList[1] 712. It should be noted that slices coded according to unidirectional prediction are referred to as P slices, and slices coded according to bidirectional prediction are referred to as B slices.Therefore, RefPicList[0] 711 is a reference picture list (e.g., containing a list of corresponding reference pictures) used for inter prediction of a unidirectionally predicted (P) slice, or the first of two reference picture lists used for inter prediction of a bidirectionally predicted (B) slice. Furthermore, RefPicList[1] 712 is a second reference picture list (e.g., used in conjunction with RefPicList[0]) used for inter prediction of a B slice.

[0091] In a specific example, the RPL structure 700 may be represented as ref_pic_list_struct(listIdx, rplsIdx), where listIdx 721 is an index that identifies a corresponding reference picture list, such as RefPicList[0] 711 and / or RefPicList[1] 712, and rplsIdx 725 is an index that indicates a reference entry 715 in the corresponding reference picture list. Thus, ref_pic_list_struct() is a syntax structure that returns the reference entry 715 based on listIdx 721 and rplsIdx 725. ref_pic_list_struct() may be defined as a syntax structure that includes RefPicList[0] and RefPicList[1]. An encoder may encode a portion of the RPL structure 700 for each non-intra coded slice in a video sequence. A decoder may then resolve the corresponding portion of the RPL structure 700 before decoding each non-intra coded slice in a coded video sequence. For example, portions of the RPL structure 700 that pertain to many pictures in a sequence may be stored in the SPS, portions of the RPL structure 700 that apply to a small number of pictures may be stored in the PPS, and portions of the RPL structure 700 that apply to a particular slice may be stored in a slice header.

[0092] The set of reference pictures (setOfRefPics) 733 is a set of unique pictures referenced by all entries in RefPicList[0] 711 with the same nuh_layer_id as the current picture and all entries in RefPicList[1] 712 with the same nuh_layer_id as the current picture. RefPicList[0] 711 and RefPicList[1] 712 may be slice specific. Thus, setOfRefPics 733 may contain a set of unique reference pictures for the current slice in the current picture, where the set of unique reference pictures is in the same layer as the current picture. In some systems, the number of reference pictures in setOfRefPics 733 may be constrained by a static value that is global to all layers. However, as pointed out above, the amount of DPB space used may vary depending on whether a layer is an output layer or not. Therefore, applying the same static maximum value of pictures to setOfRefPics 733 regardless of layer may result in inefficient memory allocation. For example, a static maximum value may overly restrict the number of pictures that may be in setOfRefPics733 for output layers and / or may not be restrictive enough for reference layers (non-output layers). In an example of the present invention, this problem is addressed by constraining setOfRefPics733 based on a maximum decoded picture buffer size, which differs depending on whether a layer is a reference layer or an output layer. Therefore, setOfRefPics733 is instead constrained based on the amount of available memory space in the DPB for each layer, and not based on any static value. Thus, setOfRefPics733 may be dynamically limited to different sizes depending on whether the corresponding layer is an output layer or a reference layer.

[0093] In some examples, the encoder may also signal the number of reference entries (num_ref_entries) 732 in the RPL structure 700. The num_ref_entries 732 is a syntax element that indicates the number of reference entries in the RPL structure 700. The num_ref_entries 732 may be expressed as num_ref_entries[listIdx][rplsIdx]. Similar to the setOfRefPics 733, some video coding systems limit the num_ref_entries 732 based on a static value that may be overly restrictive or overly permissive depending on whether the layer is an output layer or a reference layer only. This disclosure may also constrain the num_ref_entries 732 based on a maximum decoded picture buffer size. Therefore, the num_ref_entries 732 is instead constrained based on the amount of available memory space in the DPB for the corresponding layer, and not based on any static value that is global for all layers. Therefore, num_ref_entries 732 may be dynamically limited to different sizes depending on whether the corresponding layer is an output layer or a reference layer.

[0094] 8 is a schematic diagram illustrating an exemplary bitstream 800. For example, the bitstream 800 may be generated by the codec system 200 and / or the encoder 300 for decoding by the codec system 200 and / or the decoder 400 according to the method 100. Furthermore, the bitstream 800 may include the encoded multi-layer video sequence 600, which may be coded by adopting the RPL structure 700. In addition, the bitstream 800 may include various parameters for controlling the operation of an HRD, such as the HRD 500. Based on such parameters, the HRD 500 may check the bitstream 800 for conformance to the standard before transmitting it to the decoder for decoding.

[0095] The bitstream 800 includes a VPS 811, one or more SPSs 813, a number of picture parameter sets (PPSs) 815, a number of picture headers 816, a number of slice headers 817, and image data 820. The VPS 811 includes data related to the entire bitstream 800. For example, the VPS 811 may include data related to the OLS, layers, and / or sublayers used in the bitstream 800. The SPS 813 includes sequence data that is common to all pictures in a coded video sequence included in the bitstream 800. For example, each layer may include one or more coded video sequences, and each coded video sequence may reference the SPS 813 for corresponding parameters. Parameters in the SPS 813 may include picture sizing, bit depth, coding tool parameters, bit rate limits, etc. It should be noted that while each sequence references an SPS 813, in some examples a single SPS 813 may include data for multiple sequences. The PPS 815 includes parameters that apply to the entire picture. Thus, each picture in a video sequence may reference a PPS 815. Note that while each sequence references a PPS 815, in some examples a single PPS 815 may contain data for multiple pictures. For example, multiple similar pictures may be coded according to similar parameters. In such a case, a single PPS 815 may contain data for such similar pictures. The PPS 815 may indicate coding tools available for slices, quantization parameters, offsets, etc. in the corresponding picture.

[0096] A slice header 817 includes parameters specific to a corresponding slice 827 in a picture 825. Thus, there may be one slice header 817 for each slice 827 in a video sequence. The slice header 817 may include slice type information, a picture order count (POC), a reference picture list, prediction weights, tile entry points, or deblocking parameters, etc. Note that in some examples, the bitstream 800 may also include a picture header 816, which is a syntax structure that includes parameters that apply to all slices 827 in a single picture 825. For this reason, the picture header 816 and the slice header 817 may be used interchangeably in some contexts. For example, some parameters may be moved between the slice header 817 and the picture header 816 depending on whether such parameters apply to a particular slice 827 or are common to all slices 827 in a picture 825.

[0097] The image data 820 includes video data encoded according to inter-, inter-layer, and / or intra-prediction, as well as corresponding transformed and quantized residual data. For example, the image data 820 may include a layer 823, a picture 825, and / or a slice 827. A layer 823 is a set of VCL NAL units 841 and associated non-VCL NAL units 842 that share specified characteristics (e.g., a common resolution, frame rate, image size, etc.) as indicated by a layer ID such as nuh_layer_id 835. For example, a layer 823 may include a set of pictures 825 that share the same nuh_layer_id 835 along with any parameter set used to decode the pictures 825 in the layer 823. For example, a layer 823 is substantially similar to layer N 631 and / or layer N+1 632, respectively, from FIG. 6.

[0098] nuh_layer_id 835 is a syntax element that specifies an identifier of a layer 823 that contains at least one NAL unit. For example, the lowest quality layer, known as a base layer, may contain the lowest value of nuh_layer_id 835 with higher values ​​of nuh_layer_id 835 for higher quality layers. Thus, lower layers are layers 823 with smaller values ​​of nuh_layer_id 835 and higher layers are layers 823 with larger values ​​of nuh_layer_id 835. Data of layers 823 are correlated based on nuh_layer_id 835. For example, parameter sets and video data may be associated with a value of nuh_layer_id 835 that corresponds to the lowest layer 823 that contains such parameter sets / video data. Hence, a set of VCL NAL units 841 is part of a layer 823 when the set of VCL NAL units 841 all have a particular value of nuh_layer_id 835.

[0099] A picture 825 is an array of luma samples and / or an array of chroma samples that make up a frame or a field thereof. For example, a picture 825 is a coded image that may be output for display or used to support coding of other pictures for output. A picture 825 includes one or more slices 827. A slice 827 may be defined as an integer number of complete tiles or an integer number of consecutive complete coding tree unit (CTU) rows (e.g., within a tile) of a picture 825 that are exclusively contained in a single NAL unit, such as a VCL NAL unit 841. A slice 827 is further divided into CTUs and / or coding tree blocks (CTBs). A CTU is a group of samples of a predefined size that may be partitioned by a coding tree. A CTB is a subset of a CTU and includes the luma or chroma components of the CTU. The CTUs / CTBs are further divided into coding blocks based on the coding tree. The coding blocks may then be encoded / decoded according to a prediction mechanism.

[0100] The bitstream 800 may be coded as a sequence of NAL units. A NAL unit is a container for video data and / or supporting syntax. The NAL units may be VCL NAL units 841 or non-VCL NAL units 842. A VCL NAL unit 841 is a NAL unit coded to include video data, such as image data 820 and associated slice headers 817. As a specific example, each slice 827 and associated slice headers 817 may be encoded into a single VCL NAL unit 841. A non-VCL NAL unit 842 is a NAL unit that includes non-video data, such as syntax and / or parameters that support decoding the video data, performing conformance checks, or other operations. For example, a non-VCL NAL unit 842 may include a VPS 811, an SPS 813, a PPS 815, a picture header 816, or other supporting syntax. Therefore, the bitstream 800 is a series of VCL NAL units 841 and non-VCL NAL units 842. Each NAL unit contains a nuh_layer_id 835, which allows an encoder or decoder to determine which layer 823 contains the corresponding NAL unit.

[0101] A bitstream 800 including multiple layers 823 may be encoded and stored until requested by a decoder. For example, a decoder may request a layer 823 including multiple layers 823, and / or an OLS. In a particular example, the layers 823 may include a base layer and one or more enhancement layers. The encoder and / or content server should send to the decoder only those layers 823 necessary to decode the requested output layers.

[0102] The bitstream may include a ref_pic_list_struct 831, which may be substantially similar to the RPL structure 700 of Figure 7. The ref_pic_list_struct 831 may include RefPicList[0] and RefPicList[1] that reference the setofRefPics used to code blocks in the slice 827 according to inter prediction and / or inter-layer prediction. The ref_pic_list_struct 831 may also include a num_ref_entries 832, which is substantially similar to the num_ref_entries 732 of Figure 7. Thus, the num_ref_entries 832 indicates the number of reference entries in the ref_pic_list_struct 831. The ref_pic_list_struct 831 may be stored in the SPS 813, the picture header 816, and / or the slice header 817 depending on the scope of the ref_pic_list_struct 831. For example, a ref_pic_list_struct 831 referencing reference pictures for the entire sequence is included in the SPS 813, a ref_pic_list_struct 831 referencing reference pictures for the entire picture 825 is included in the picture header 816, and a ref_pic_list_struct 831 referencing reference pictures for the slice 827 is included in the slice header 817.

[0103] The bitstream 800 may also include decoded picture buffer parameters (dpb_parameters) 837. The dpb_parameters 837 is a syntax structure that provides information on the DPB size, the maximum picture reordering number, and the maximum latency for one or more OLSs. Thus, the dpb_parameters 837 specifies the functionality of the DPB during the decoding process. As a specific example, the dpb_parameters 837 may include a maximum decoded picture buffer minus 1 (max_dec_pic_buffering_minus1) 838, which is a syntax element that specifies the maximum required size of the DPB in units of picture storage buffer. The dpb_parameters 837 may be stored in the VPS 811 and / or the SPS 813 depending on the scope. For example, dpb_parameters 837 that apply to the entire video may be stored in the VPS 811, while dpb_parameters 837 that apply to a particular video sequence and / or a particular layer 823 may be stored in the SPS 813.

[0104] As noted above, ref_pic_list_struct 831, also denoted as ref_pic_list_struct(listIdx, rplsIdx), may be employed to keep track of references between pictures, thereby supporting the reconstruction of inter-predicted pictures. In some video coding systems, ref_pic_list_struct 831 includes the maximum number of reference entries that can be employed for the current picture. Specifically, in some video coding systems, the maximum number of reference entries for the current picture is a statically defined value that is global for all layers. This results in limiting num_ref_entries 832, also denoted as num_ref_entries[listIdx][rplsIdx], based on a statically defined value regardless of layer. This also results in limiting setOfRefPics 733 of FIG. 7, which is referenced by ref_pic_list_struct 831, based on a statically defined value regardless of layer. The problem with this approach is that reference layers use a different amount of space in the decoded picture buffer than the output layers. For example, the reference layer uses space for picture reconstruction, and the output layer uses space for both picture reconstruction and storage pending output. Thus, a statically defined maximum number of reference entries selected to support a smaller amount of space used for the reference layer may be overly restrictive when applied to pictures of the output layer. Alternatively, a statically defined maximum number of reference entries selected for the output layer may provide more space than necessary to decode pictures of the reference layer, thus wasting memory resources.

[0105] To address the above-mentioned issues, the bitstream 800 constrains the ref_pic_list_struct 831 to support different picture buffer usage for different types of layers 823. For example, num_ref_entries 832, which indicates the number of reference entries in the ref_pic_list_struct 831 used for each picture, is constrained to maintain a range selected based on the maximum decoded picture buffer size. The maximum decoded picture buffer size differs depending on whether the layer is a reference layer or an output layer. Thus, constraining num_ref_entries 832 based on the maximum decoded picture buffer size allows different numbers of reference pictures to be employed for output layers and reference layers. In a particular example, max_dec_pic_buffering_minus1 838 in dpb_parameters 837 specifies the maximum required size of the DPB for the corresponding layer. Thus, the encoder and / or HRD may derive a maximum decoded picture buffer size based on max_dec_pic_buffering_minus1 838 and constrain num_ref_entries 832 based on the maximum decoded picture buffer size. The decoder may also receive ref_pic_list_struct 831 with num_ref_entries 832 constrained based on the maximum decoded picture buffer size. Notwithstanding this example, num_ref_entries 832 is constrained based on the maximum decoded picture buffer size, which is layer-specific and not a statically defined value that is global for all layers. In a further example, setOfRefPics 733 of FIG. 7 may be constrained in a similar manner. For example, the encoder and / or HRD may derive a maximum decoded picture buffer size based on max_dec_pic_buffering_minus1 838 and constrain setOfRefPics 733 based on the maximum decoded picture buffer size.The decoder may also receive a ref_pic_list_struct 831 with a setOfRefPics 733 that is constrained based on the maximum decoded picture buffer size. Notwithstanding this example, setOfRefPics 733 is constrained based on the maximum decoded picture buffer size, which is layer-specific and not a statically defined value that is global for all layers. By employing such a constraint, a more efficient allocation of memory in the decoded picture buffer is supported, and thus high coding efficiency is supported, as more optimal memory usage encourages more efficient encoding. As a result, the functionality of the encoder and decoder is improved. Furthermore, coding efficiency is increased, thereby reducing the use of processor, memory, and / or network signaling resources in both the encoder and the decoder.

[0106] The aforementioned information will then be described in more detail below in this specification. Layered video coding is also referred to as scalable video coding or video coding with scalability. Scalability in video coding can be supported by using multi-layer coding techniques. A multi-layer bitstream includes a base layer (BL) and one or more enhancement layers (EL). Examples of scalability include spatial scalability, quality / signal-to-noise ratio (SNR) scalability, multi-view scalability, frame rate scalability, etc. When multi-layer coding techniques are used, a picture or a portion thereof can be coded without using a reference picture (intra prediction), can be coded by referencing a reference picture that is in the same layer (inter prediction), and / or can be coded by referencing a reference picture that is in another layer (inter-layer prediction). A reference picture used for inter-layer prediction of a current picture is referred to as an inter-layer reference picture (ILRP). FIG. 6 illustrates an example of multi-layer coding for spatial scalability where pictures in different layers have different resolutions.

[0107] Some video coding families provide support for scalability in separate profiles from profiles for single-layer coding. Scalable Video Coding (SVC) is a scalable extension of Advanced Video Coding (AVC) that provides support for spatial, temporal, and quality scalability. For SVC, a flag is signaled in each macroblock (MB) in an EL picture to indicate whether the EL MB is predicted using co-located blocks from lower layers. Predictions from co-located blocks may include texture, motion vectors, and / or coding modes. An implementation of SVC cannot directly reuse unmodified AVC implementations in its design. The SVC EL macroblock syntax and decoding process are different from the AVC syntax and decoding process.

[0108] Scalable HEVC (SHVC) is an extension of HEVC that provides support for spatial and quality scalability. Multiview HEVC (MV-HEVC) is an extension of HEVC that provides support for multiview scalability. 3D HEVC (3D-HEVC) is an extension of HEVC that provides support for 3D video coding that is more advanced and efficient than MV-HEVC. Temporal scalability can be included as an integral part of a single-layer HEVC codec. In the multi-layer extension of HEVC, decoded pictures used for inter-layer prediction come only from the same AU and are treated as long-term reference pictures (LTRPs). Such pictures are assigned a reference index in a reference picture list along with other temporal reference pictures in the current layer. Inter-layer prediction (ILP) is achieved at the prediction unit (PU) level by setting the value of the reference index to refer to an inter-layer reference picture in the reference picture list. Spatial scalability resamples a reference picture or a portion thereof when the ILRP has a different spatial resolution than the current picture being encoded or decoded. Reference picture resampling can be realized either at the picture level or at the coding block level.

[0109] VVC may also support layered video coding. A VVC bitstream may contain multiple layers. The layers may all be independent of each other. For example, each layer may be coded without using inter-layer prediction. In this case, the layers are also referred to as simulcast layers. In some cases, some of the layers are coded using ILP. A flag in the VPS may indicate whether the layers are simulcast layers and whether some layers are using ILP. When some layers use ILP, layer dependencies between layers are also signaled in the VPS. Unlike SHVC and MV-HEVC, VVC may not specify an OLS. An OLS includes a specified set of layers, and one or more layers in the set of layers are specified to be output layers. An output layer is a layer of the OLS that is output. In some implementations of VVC, when a layer is a simulcast layer, only one layer may be selected for decoding and output. In some implementations of VVC, when any layer uses ILP, the entire bitstream including all layers is specified to be decoded. Additionally, certain of the layers are designated as output layers, which may be indicated to be only the top layer, all layers, or the top layer plus a set of indicated lower layers.

[0110] The aforementioned aspects include some scalability-related issues. Scalability designs in such systems include layer-specific profile, tier, and level (PTL) and even layer-specific Coded Picture Buffer (CPB) operations. PTL signaling efficiency should be improved. Signaling efficiency of sequence-level HRD parameters for sub-layers should be improved. DPB parameter signaling should be improved. Some designs cause single-layer bitstreams to reference VPS. The value range of num_ref_entries[][] in such designs is incorrect and causes unexpected errors to the decoder. The decoding process in such designs involves sub-bitstream extraction, which increases the burden on the decoder implementation. The general decoding process in such designs cannot work for scalable bitstreams that include multiple layers with inter-layer prediction. The derivation of the value of the variable NoOutputOfPriorPicsFlag in such designs is picture-based and cannot be AU-based in such designs. The scalable nesting SEI message in such a design should be simplified to apply directly to the OLS, rather than to a layer of OLS, when nesting_ols_flag is equal to 1. The non-scalable nesting SEI message may be specified to apply only to the 0th OLS when payloadType is equal to 0 (buffering period), 1 (picture timing), or 130 (decoding unit information).

[0111] In general, this disclosure describes various approaches for scalability in video coding. The description of the techniques is based on VVC. However, these techniques also apply to layered video coding based on other video codec specifications. One or more of the problems described above may be solved as follows. Specifically, this disclosure includes methods for improved scalability support in video coding.

[0112] The following are various example definitions: OP may be a temporal subset of the OLS, identified by the OLS index and the highest value of TemporalId. Output layer may be a layer of the OLS that is output. The OLS may be a set of layers, and one or more layers in the set of layers are designated to be output layers. The OLS layer index may be an index of a layer in the OLS into a list of layers in the OLS. The sub-bitstream extraction process may be a designated process that removes from the bitstream NAL units in the bitstream that do not belong to a target set, as determined by a target OLS index and a target highest TemporalId, and the output sub-bitstream includes NAL units in the bitstream that belong to the target set.

[0113] An example video parameter set RBSP syntax is as follows:

[0114] [Table 1A]

[0115] [Table 1B]

[0116] An exemplary sequence parameter set RBSP syntax is as follows:

[0117] [Table 2A]

[0118] [Table 2B]

[0119] An exemplary DPB parameter syntax is as follows:

[0120] [Table 3]

[0121] An exemplary general HRD parameter syntax is as follows:

[0122] [Table 4]

[0123] An exemplary OLD HRD parameter syntax is as follows:

[0124] [Table 5]

[0125] An example sub-layer HRD parameter syntax is as follows:

[0126] [Table 6]

[0127] Exemplary video parameter set RBSP semantics are: vps_max_layers_minus1+1 specifies the maximum allowed number of layers in each CVS that references the VPS. vps_max_sub_layers_minus1+1 specifies the maximum number of temporal sublayers that may be present in each CVS that references the VPS. The value of vps_max_sub_layers_minus1 may be in the range of 0 to 6. vps_all_layers_same_num_sub_layers_flag equal to 1 specifies that the number of temporal sublayers is the same for all layers in each CVS that references the VPS. vps_all_layers_same_num_sub_layers_flag equal to 0 specifies that layers in each CVS that references the VPS may or may not have the same number of temporal sublayers. When not present, the value of vps_all_layers_same_num_sub_layers_flag may be inferred to be equal to 1. vps_all_independent_layers_flag equal to 1 specifies that all layers in the CVS are coded independently without using inter-layer prediction. vps_all_independent_layers_flag equal to 0 specifies that one or more of the layers in the CVS may use inter-layer prediction. When not present, the value of vps_all_independent_layers_flag may be inferred to be equal to 1. When vps_all_independent_layers_flag is equal to 1, the value of vps_independent_layer_flag[i] is inferred to be equal to 1. When vps_all_independent_layers_flag is equal to 0, the value of vps_independent_layer_flag[0] is inferred to be equal to 1.

[0128] vps_direct_dependency_flag[i][j] equal to 0 specifies that the layer with index j is not a direct reference layer for the layer with index i. vps_direct_dependency_flag[i][j] equal to 1 specifies that the layer with index j is a direct reference layer for the layer with index i. When vps_direct_dependency_flag[i][j] is not present for i and j in the range from 0 to vps_max_layers_minus1, the flag is inferred to be equal to 0. The variables DirectDependentLayerIdx[i][j], which specifies the jth directly dependent layer of the ith layer, and LayerUsedAsRefLayerFlag[j], which specifies whether the layer with layer index j is used as a reference layer by any other layer, may be derived as follows: for(i=0; i<=vps_max_layers_minus1; i++) LayerUsedAsRefLayerFlag[j]=0 for(i=1; i <vps_max_layers_minus1; i++) if(!vps_independent_layer_flag[i]) for(j=i-1, k=0; j>=0; j--) if(vps_direct_dependency_flag[i][j]) { DirectDependentLayerIdx[i][k++]=j LayerUsedAsRefLayerFlag[j]=1 }

[0129] The variable GeneralLayerIdx[i], which specifies the layer index of the layer whose nuh_layer_id is equal to vps_layer_id[i], may be derived as follows: for(i=0; i<=vps_max_layers_minus1; i++) GeneralLayerIdx[vps_layer_id[i]]=i

[0130] each_layer_is_an_ols_flag equal to 1 specifies that each output layer set contains only one layer, and each layer in the bitstream is itself an output layer set where the single contained layer is the only output layer. each_layer_is_an_ols_flag equal to 0 specifies that an output layer set may contain multiple layers. If vps_max_layers_minus1 is equal to 0, the value of each_layer_is_an_ols_flag is inferred to be equal to 1. Otherwise, when vps_all_independent_layers_flag is equal to 0, the value of each_layer_is_an_ols_flag is inferred to be equal to 0.

[0131] ols_mode_idc equal to 0 specifies that the total number of OLSs specified by the VPS is equal to vps_max_layers_minus1+1, the i-th OLS contains layers with layer indices from 0 to i, and for each OLS, only the top layer in the OLS is output. ols_mode_idc equal to 1 specifies that the total number of OLSs specified by the VPS is equal to vps_max_layers_minus1+1, the i-th OLS contains layers with layer indices from 0 to i, and for each OLS, all layers within the OLS are output. ols_mode_idc equal to 2 specifies that the total number of OLSs specified by the VPS is explicitly signaled, and for each OLS, an explicitly signaled set of top and lower layers in the OLS are output. The value of ols_mode_idc can be in the range from 0 to 2. When vps_all_independent_layers_flag is equal to 1 and each_layer_is_an_ols_flag is equal to 0, the value of ols_mode_idc is inferred to be equal to 2. num_output_layer_sets_minus1+1 specifies the total number of OLS specified by the VPS when ols_mode_idc is equal to 2.

[0132] The variable TotalNumOlss, which specifies the total number of OLSs specified by the VPS, may be derived as follows: if(vps_max_layers_minus1==0) TotalNumOlss=1 else if(each_layer_is_an_ols_flag || ols_mode_idc==0 || ols_mode_idc==1) TotalNumOlss=vps_max_layers_minus1+1 else if(ols_mode_idc==2) TotalNumOlss=num_output_layer_sets_minus1+1

[0133] layer_included_flag[i][j] specifies that the jth layer (e.g., the layer with nuh_layer_id equal to vps_layer_id[j]) is included in the ith OLS when ols_mode_idc is equal to 2. layer_included_flag[i][j] equal to 1 specifies that the jth layer is included in the ith OLS. layer_included_flag[i][j] equal to 0 specifies that the jth layer is not included in the ith OLS. The variables NumLayersInOls[i], which specifies the number of layers in the ith OLS, and LayerIdInOls[i][j], which specifies the nuh_layer_id value of the jth layer in the ith OLS, may be derived as follows: NumLayersInOls[0] = 1 LayerIdInOls[0][0]=vps_layer_id[0] for(i=1, i <TotalNumOlss; i++) { if(each_layer_is_an_ols_flag) { NumLayersInOls[i] = 1 LayerIdInOls[i][0]=vps_layer_id[i] } else if(ols_mode_idc==0 | | ols_mode_idc==1) { NumLayersInOls[i]=i+1 for(j=0; j <NumLayersInOls[i]; j++) LayerIdInOls[i][j]=vps_layer_id[j] } else if(ols_mode_idc==2) { for(k=0, j=0; k<=vps_max_layers_minus1; k++) if(layer_included_flag[i][k]) LayerIdInOls[i][j++]=vps_layer_id[k] NumLayersInOls[i] = j } }

[0134] The variable OlsLayeIdx[i][j], which specifies the OLS layer index of the layer whose nuh_layer_id is equal to LayerIdInOls[i][j], may be derived as follows: for(i=0, i <TotalNumOlss; i++) for j=0; j <NumLayersInOls[i]; j++) OlsLayeIdx[i][LayerIdInOls[i][j]]=j

[0135] The bottom layer in each OLS shall be an independent layer. In other words, for each i in the range 0 to TotalNumOlss-1, the value of vps_independent_layer_flag[GeneralLayerIdx[LayerIdInOls[i][0]]] shall be equal to 1. Each layer shall be included in at least one OLS specified by the VPS. In other words, for each layer with a particular value of nuh_layer_id nuhLayerId equal to one of vps_layer_id[k] for k in the range 0 to vps_max_layers_minus1, there shall be at least one pair of values ​​of i and j, where i is in the range 0 to TotalNumOlss-1, j is in the range NumLayersInOls[i]-1, and the value of LayerIdInOls[i][j] equal to nuhLayerId. Any layer in the OLS may be either an output layer of the OLS or a reference layer (direct or indirect) of an output layer of the OLS.

[0136] vps_output_layer_flag[i][j] specifies whether the jth layer in the ith OLS is output when ols_mode_idc is equal to 2. vps_output_layer_flag[i] equal to 1 specifies that the jth layer in the ith OLS is output. vps_output_layer_flag[i] equal to 0 specifies that the jth layer in the ith OLS is not output. The value of vps_output_layer_flag[i] is inferred to be equal to 1 when vps_all_independent_layers_flag is equal to 1 and each_layer_is_an_ols_flag is equal to 0. The variable OutputLayerFlag[i][j], where a value of 1 specifies that the jth layer in the ith OLS is output and a value of 0 specifies that the jth layer in the ith OLS is not output, may be derived as follows: for(i=0, i <TotalNumOlss; i++) { OutputLayerFlag[i][NumLayersInOls[i]-1]=1 for(j=0; j <NumLayersInOls[i]-1; j++) if(ols_mode_idc[i]==0) OutputLayerFlag[i][j]=0 else if(ols_mode_idc[i]==1) OutputLayerFlag[i][j]=1 else if(ols_mode_idc[i]==2) OutputLayerFlag[i][j]=vps_output_layer_flag[i][j] }

[0137] Note that the 0th OLS only includes the lowest layers (e.g., layers with nuh_layer_id equal to vps_layer_id[0]) and for the 0th OLS, only included layers are output. vps_num_ptls specifies the number of profile_tier_level() syntax structures in the VPS. pt_present_flag[i] equal to 1 specifies that profile, tier, and general constraint information is present in the i-th profile_tier_level() syntax structure in the VPS. pt_present_flag[i] equal to 0 specifies that profile, tier, and general constraint information is not present in the i-th profile_tier_level() syntax structure in the VPS. The value of pt_present_flag[0] is inferred to be equal to 0. When pt_present_flag[i] is equal to 0, the profile, tier, and general constraint information for the i-th profile_tier_level() syntax structure in the VPS is inferred to be identical to that of the (i-1)-th profile_tier_level() syntax structure in the VPS.

[0138] ptl_max_temporal_id[i] specifies the TemporalId of the highest sublayer representation whose level information is present in the i-th profile_tier_level() syntax structure in the VPS. The value of ptl_max_temporal_id[i] SHALL be in the range of 0 to vps_max_sub_layers_minus1. When vps_max_sub_layers_minus1 is equal to 0, the value of ptl_max_temporal_id[i] is inferred to be equal to 0. When vps_max_sub_layers_minus1 is greater than 0 and vps_all_layers_same_num_sub_layers_flag is equal to 1, the value of ptl_max_temporal_id[i] is inferred to be equal to vps_max_sub_layers_minus1. vps_ptl_byte_alignment_zero_bit SHALL be equal to 0.

[0139] ols_ptl_idx[i] specifies an index into the list of profile_tier_level() syntax structures in the VPS for the profile_tier_level() syntax structures that apply to the i-th OLS. When present, the value of ols_ptl_idx[i] should be in the range from 0 to vps_num_ptls-1. When NumLayersInOls[i] is equal to 1, the profile_tier_level() syntax structures that apply to the i-th OLS are present in the SPS referenced by the layers in the i-th OLS. vps_num_dpb_params specifies the number of dpb_parameters() syntax structures in the VPS. The value of vps_num_dpb_params shall be in the range from 0 to 16. When not present, the value of vps_num_dpb_params may be inferred to be equal to 0. same_dpb_size_output_or_nonoutput_flag equal to 1 specifies that the layer_nonoutput_dpb_params_idx[i] syntax element is not present in the VPS. same_dpb_size_output_or_nonoutput_flag equal to 0 specifies that the layer_nonoutput_dpb_params_idx[i] syntax element may or may not be present in the VPS. vps_sub_layer_dpb_params_present_flag is used to control the presence of the max_dec_pic_buffering_minus1[ ], max_num_reorder_pics[ ], and max_latency_increase_plus1[ ] syntax elements in the dpb_parameters() syntax structure in the VPS. When not present, vps_sub_dpb_params_info_present_flag is inferred to be equal to 0.

[0140] dpb_size_only_flag[i] equal to 1 specifies that the max_num_reorder_pics[ ] and max_latency_increase_plus1[ ] syntax elements are not present in that VPS of the i-th dpb_parameters() syntax structure. dpb_size_only_flag[i] equal to 1 specifies that the max_num_reorder_pics[ ] and max_latency_increase_plus1[ ] syntax elements may be present in that VPS of the i-th dpb_parameters() syntax structure. dpb_max_temporal_id[i] specifies the TemporalId of the highest sublayer representation for which DPB parameters may be present in the i-th dpb_parameters() syntax structure within a VPS. The value of dpb_max_temporal_id[i] shall be in the range from 0 to vps_max_sub_layers_minus1. When vps_max_sub_layers_minus1 is equal to 0, the value of dpb_max_temporal_id[i] may be inferred to be equal to 0. When vps_max_sub_layers_minus1 is greater than 0 and vps_all_layers_same_num_sub_layers_flag is equal to 1, the value of dpb_max_temporal_id[i] is inferred to be equal to vps_max_sub_layers_minus1. layer_output_dpb_params_idx[i] specifies an index into the list of dpb_parameters() syntax structures in the VPS for the dpb_parameters() syntax structure that applies to the i-th layer when it is an output layer in OLS. When present, the value of layer_output_dpb_params_idx[i] shall be in the range from 0 to vps_num_dpb_params-1, inclusive.

[0141] If vps_independent_layer_flag[i] is equal to 1, then the dpb_parameters() syntax structure applied to the i-th layer, when it is an output layer, is the dpb_parameters() syntax structure present in the SPS referenced by the layer. Otherwise (vps_independent_layer_flag[i] is equal to 1), the following applies: When vps_num_dpb_params is equal to 1, the value of layer_output_dpb_params_idx[i] is inferred to be equal to 0. A bitstream conformance requirement may be that the value of layer_output_dpb_params_idx[i] is such that dpb_size_only_flag[layer_output_dpb_params_idx[i]] is equal to 0.

[0142] layer_nonoutput_dpb_params_idx[i] specifies an index into the list of dpb_parameters() syntax structures in the VPS for the dpb_parameters() syntax structures that apply to the ith layer when the ith layer is a non-output layer in OLS. When present, the value of layer_nonoutput_dpb_params_idx[i] should be in the range from 0 to vps_num_dpb_params-1. If same_dpb_size_output_or_nonoutput_flag is equal to 1, the following applies: If vps_independent_layer_flag[i] is equal to 1, the dpb_parameters() syntax structures that apply to the ith layer when the ith layer is a non-output layer are the dpb_parameters() syntax structures that exist in the SPS referenced by the layer. Otherwise (when vps_independent_layer_flag[i] is equal to 1), the value of layer_nonoutput_dpb_params_idx[i] is inferred to be equal to layer_output_dpb_params_idx[i]. Otherwise (when same_dpb_size_output_or_nonoutput_flag is equal to 0), when vps_num_dpb_params is equal to 1, the value of layer_output_dpb_params_idx[i] is inferred to be equal to 0.

[0143] general_hrd_params_present_flag equal to 1 specifies that the syntax elements num_units_in_tick and time_scale and the syntax structure general_hrd_parameters() are present in the SPS RBSP syntax structure. general_hrd_params_present_flag equal to 0 specifies that the syntax elements num_units_in_tick and time_scale and the syntax structure general_hrd_parameters() are not present in the SPS RBSP syntax structure. num_units_in_tick is the number of time units of a clock running at a frequency time_scale hertz (Hz) that corresponds to one increment (called a clock tick) of the clock tick counter. num_units_in_tick shall be greater than 0. A clock tick is in seconds and is equal to the quotient of num_units_in_tick divided by time_scale. For example, when the picture rate of a video signal is 25 Hz, time_scale may be equal to 27,000,000 and num_units_in_tick may be equal to 1,080,000, so that a clock tick is equal to 0.04 seconds. time_scale is the number of time units that pass in one second. For example, a time coordinate system that measures time using a 27 MHz clock has a time_scale of 27,000,000. Values ​​of time_scale shall be greater than 0.

[0144] vps_extension_flag equal to 0 specifies that the vps_extension_data_flag syntax element is not present in the VPS RBSP syntax structure. vps_extension_flag equal to 1 specifies that the vps_extension_data_flag syntax element is present in the VPS RBSP syntax structure. vps_extension_data_flag may have any value. The presence and value of vps_extension_data_flag may not affect decoder conformance to the profile. Conforming decoders may ignore all vps_extension_data_flag syntax elements.

[0145] Exemplary sequence parameter set RBSP semantics are as follows: An SPS RBSP shall be available to the decoding process before being referenced, either included in at least one access unit with TemporalId equal to 0 or provided through external means, and an SPS NAL unit containing an SPS RBSP shall have nuh_layer_id equal to the lowest nuh_layer_id value of the PPS NAL units that reference the SPS NAL unit. All SPS NAL units with a particular value of sps_seq_parameter_set_id in a CVS shall have the same content. sps_decoding_parameter_set_id, when greater than 0, specifies the value of dps_decoding_parameter_set_id for the DPS referenced by the SPS. When sps_decoding_parameter_set_id is equal to 0, the SPS does not reference a DPS, and the DPS is not referenced when decoding each CLVS that references the SPS. The value of sps_decoding_parameter_set_id shall be the same in all SPSs referenced by coded pictures in the bitstream.

[0146] When sps_video_parameter_set_id is greater than 0, it specifies the value of vps_video_parameter_set_id for the VPS referenced by the SPS. When sps_video_parameter_set_id is equal to 0, the SPS may not reference a VPS, and when decoding each CLVS that references the SPS, the VPS is not referenced, the value of GeneralLayerIdx[nuh_layer_id] should be inferred to be equal to 0, and the value of vps_independent_layer_flag[GeneralLayerIdx[nuh_layer_id]] may be inferred to be equal to 1. When vps_independent_layer_flag[GeneralLayerIdx[nuh_layer_id]] is equal to 1, the SPS referenced by a CLVS with a particular nuh_layer_id value nuhLayerId shall have nuh_layer_id equal to nuhLayerId.

[0147] sps_max_sub_layers_minus1+1 specifies the maximum number of temporal sub-layers that may be present in each CLVS that references an SPS. The value of sps_max_sub_layers_minus1 should be in the range of 0 to vps_max_sub_layers_minus1. sps_reserved_zero_4bits should be equal to 0 in conforming bitstreams. Other values ​​for sps_reserved_zero_4bits may be reserved.

[0148] sps_ptl_dpb_present_flag equal to 1 specifies that the profile_tier_level() and dpb_parameters() syntax structures are present in the SPS. sps_ptl_dpb_present_flag equal to 0 specifies that neither the profile_tier_level() nor the dpb_parameters() syntax structures are present in the SPS. The value of sps_ptl_dpb_present_flag shall be equal to vps_independent_layer_flag[nuh_layer_id]. If vps_independent_layer_flag[GeneralLayerIdx[nuh_layer_id]] is equal to 1, the variable MaxDecPicBuffMinus1 is set equal to max_dec_pic_buffering_minus1[sps_max_sub_layers_minus1] in the dpb_parameters() syntax structure in the SPS. Otherwise, MaxDecPicBuffMinus1 is set equal to max_dec_pic_buffering_minus1[sps_max_sub_layers_minus1] of the layer_nonoutput_dpb_params_idx[GeneralLayerIdx[nuh_layer_id]]th dpb_parameters() syntax structure in the VPS. gdr_enabled_flag equal to 1 specifies that GDR pictures may be present in the CLVS that references the SPS. gdr_enabled_flag equal to 0 specifies that GDR pictures are not present in the CLVS that references the SPS.

[0149] sps_sub_layer_dpb_params_flag is used to control the presence of max_dec_pic_buffering_minus1[i], max_num_reorder_pics[i], and max_latency_increase_plus1[i] syntax elements in the dpb_parameters() syntax in the SPS. When not present, sps_sub_dpb_params_info_present_flag is inferred to be equal to 0. long_term_ref_pics_flag equal to 0 specifies that LTRP is not used for inter prediction of any coded pictures in the CLVS. long_term_ref_pics_flag equal to 1 specifies that LTRP may be used for inter prediction of one or more coded pictures in the CLVS.

[0150] Exemplary general profile, tier, and level semantics are as follows: The profile_tier_level() syntax structure provides level information, and optionally profile, tier, subprofile, and general constraint information (denoted as PT information). When the profile_tier_level() syntax structure is included in a DPS, OlsInScope is an OLS that includes all layers in the entire bitstream that references the DPS. When the profile_tier_level() syntax structure is included in a VPS, OlsInScope is one or more OLSs specified by the VPS. When the profile_tier_level() syntax structure is included in an SPS, OlsInScope is an OLS that includes only layers that are the lowest layer among the layers that reference the SPS, which should be independent layers.

[0151] general_profile_idc indicates the profile to which OlsInScope conforms. general_tier_flag specifies the tier context for the interpretation of general_level_idc. num_sub_profiles specifies the number of general_sub_profile_idc[i] syntax elements. general_sub_profile_idc[i] indicates the ith interoperability metadata being registered. general_level_idc indicates the level to which OlsInScope conforms. Note that a higher value of general_level_idc indicates a higher level. The maximum level signaled in the DPS for OlsInScope may be higher than the level signaled in the SPS for the CVS contained within OlsInScope. Note also that when OlsInScope conforms to multiple profiles, general_profile_idc should indicate the profile that provides the preferred decoded result or preferred bitstream identification, as determined by the encoder. Please also note that when the profile_tier_level() syntax structure is included in the DPS and the CVS of OlsInScope conforms to different profiles, the general_profile_idc and level_idc should indicate the profile and level to the decoders that can decode OlsInScope.

[0152] sub_layer_level_present_flag[i] equal to 1 specifies that the level information is present in the profile_tier_level() syntax structure for the sub-layer representation with TemporalId equal to i. sub_layer_level_present_flag[i] equal to 0 specifies that the level information is not present in the profile_tier_level() syntax structure for the sub-layer representation with TemporalId equal to i. ptl_alignment_zero_bits shall be equal to 0. The semantics of the syntax element sub_layer_level_idc[i], apart from specifying the inference of a non-present value, are the same as the syntax element general_level_idc, but apply to the sub-layer representation with TemporalId equal to i.

[0153] Exemplary DPB parameter semantics are as follows: The dpb_parameters(maxSubLayersMinus1, subLayerInfoFlag) syntax structure provides information on the DPB size, the maximum number of picture reorders, and the maximum latency for each CLVS of the CVS. When the dpb_parameters() syntax structure is included in a VPS, the OLS to which the dpb_parameters() syntax structure applies is specified by the VPS. When the dpb_parameters() syntax structure is included in an SPS, the dpb_parameters() syntax structure applies to an OLS that contains only layers that are the lowest layer among the layers that reference the SPS, which shall be independent layers.

[0154] max_dec_pic_buffering_minus1[i]+1 specifies, for each CLVS of the CVS, the maximum required size of the decoded picture buffer in units of the picture storage buffer when Htid is equal to i. The value of max_dec_pic_buffering_minus1[i] should be in the range from 0 to MaxDpbSize-1. When i is greater than 0, max_dec_pic_buffering_minus1[i] should be greater than or equal to max_dec_pic_buffering_minus1[i-1]. When max_dec_pic_buffering_minus1[i] is not present for i in the range from 0 to maxSubLayersMinus1-1 due to subLayerInfoFlag equal to 0, max_dec_pic_buffering_minus1[i] is inferred to be equal to max_dec_pic_buffering_minus1[maxSubLayersMinus1].

[0155] max_num_reorder_pics[i] specifies, for each CLVS in the CVS, the maximum allowable number of pictures in the CLVS that can precede any picture in the CLVS in decoding order and follow it in output order when Htid is equal to i. The value of max_num_reorder_pics[i] should be in the range from 0 to max_dec_pic_buffering_minus1[i]. When i is greater than 0, max_num_reorder_pics[i] should be greater than or equal to max_num_reorder_pics[i-1]. When max_num_reorder_pics[i] is not present for i in the range from 0 to maxSubLayersMinus1-1 due to subLayerInfoFlag equal to 0, max_num_reorder_pics[i] is inferred to be equal to max_num_reorder_pics[maxSubLayersMinus1].

[0156] max_latency_increase_plus1[i] not equal to 0 is used to calculate the value of MaxLatencyPictures[i], which specifies, for each CLVS in the CVS, the maximum number of pictures in the CLVS that can precede any picture in the CLVS in output order and follow it in decoding order when Htid is equal to i. When max_latency_increase_plus1[i] is not equal to 0, the value of MaxLatencyPictures[i] may be specified as follows: MaxLatencyPictures[i]=max_num_reorder_pics[i]+max_latency_increase_plus1[i]-1 When max_latency_increase_plus1[i] is equal to 0, the corresponding limit is not expressed.

[0157] The value of max_latency_increase_plus1[i] shall be in the range from 0 to 2-2. When max_latency_increase_plus1[i] is not present for i in the range from 0 to maxSubLayersMinus1-1 due to subLayerInfoFlag equal to 0, max_latency_increase_plus1[i] is inferred to be equal to max_latency_increase_plus1[maxSubLayersMinus1].

[0158] Exemplary general HDR parameter semantics are as follows: The general_hrd_parameters() syntax structure specifies the HRD parameters used in the HRD operation. num_ols_hrd_params_minus1+1 specifies the number of ols_hrd_parameters() syntax structures present in the general_hrd_parameters() syntax structure. The value of num_ols_hrd_params_minus1 should be in the range of 0 to 63. When TotalNumOlss is greater than 1, the value of num_ols_hrd_params_minus1 is inferred to be equal to 0. hrd_cpb_cnt_minus1+1 specifies the number of alternative CPB specifications in the CVS bitstream. The value of hrd_cpb_cnt_minus1 should be in the range of 0 to 31. hrd_max_temporal_id[i] specifies the TemporalId of the top-level sublayer representation whose HRD parameters are included in the i-th layer_level_hrd_parameters() syntax structure. The value of hrd_max_temporal_id[i] should be in the range from 0 to vps_max_sub_layers_minus1. When vps_max_sub_layers_minus1 is equal to 0, the value of hrd_max_temporal_id[i] is inferred to be equal to 0. ols_hrd_idx[i] specifies the index of the ols_hrd_parameters() syntax structure that applies to the i-th OLS. The value of ols_hrd_idx[[i] should be in the range from 0 to num_ols_hrd_params_minus1. When not present, the value of ols_hrd_idx[[i] is inferred to be equal to 0.

[0159] Exemplary reference picture list structure semantics are as follows: The ref_pic_list_struct(listIdx, rplsIdx) syntax structure may be present in an SPS or in a slice header. Depending on whether the syntax structure is included in a slice header or an SPS, the following applies: If present in a slice header, the ref_pic_list_struct(listIdx, rplsIdx) syntax structure specifies the reference picture list listIdx of the current picture (the picture that contains the slice). Otherwise (if present in the SPS), the ref_pic_list_struct(listIdx, rplsIdx) syntax structure specifies candidates for the reference picture list listIdx, and the term current picture in the semantics specified in the remainder of this section refers to each picture in the CVS that has one or more slices with ref_pic_list_idx[listIdx] equal to an index into the list of ref_pic_list_struct(listIdx, rplsIdx) syntax structures contained in the SPS and that references the SPS. num_ref_entries[listIdx][rplsIdx] specifies the number of entries in the ref_pic_list_struct(listIdx, rplsIdx) syntax structure. The value of num_ref_entries[listIdx][rplsIdx] should be in the range from 0 to MaxDecPicBuffMinus1+14.

[0160] An exemplary general decoding process is as follows: The input to this process is a bitstream BitstreamToDecode. The output of this process is a list of decoded pictures. The decoding process is specified such that all decoders conforming to a specified profile and level will produce numerically identical cropped decoded output pictures when they invoke the decoding process associated with that profile on a bitstream conforming to that profile and level. Any decoding process that produces cropped decoded output pictures identical to those produced by the process described herein (with the correct output order or output timing, as specified) complies with the decoding process requirements.

[0161] For each IRAP AU in the bitstream, the following applies: If the AU is the first AU in the bitstream in decoding order, or the respective picture is an Instantaneous Decoding Refresh (IDR) picture, or the respective picture is the first picture of the layer following the end of the sequence NAL unit in decoding order, then the variable NoIncorrectPicOutputFlag is set equal to 1. Otherwise, if the variable HandleCraAsCvsStartFlag is set to a value for the AU, then HandleCraAsCvsStartFlag is set equal to the value provided by the tan external mechanism and NoIncorrectPicOutputFlag is set equal to HandleCraAsCvsStartFlag. Otherwise, HandleCraAsCvsStartFlag and NoIncorrectPicOutputFlag are both set equal to 0.

[0162] For each Gradual Decoding Refresh (GDR) AU in the bitstream, the following applies: If the AU is the first AU in the bitstream in decoding order, or the respective picture is the first picture of the layer following the end of the sequence NAL unit in decoding order, then the variable NoIncorrectPicOutputFlag is set equal to 1. Otherwise, if some external mechanism is available to set the variable HandleGdrAsCvsStartFlag to a value for the AU, then HandleGdrAsCvsStartFlag is set equal to the value provided by the external mechanism, and NoIncorrectPicOutputFlag is set equal to HandleGdrAsCvsStartFlag. Otherwise, HandleGdrAsCvsStartFlag and NoIncorrectPicOutputFlag are both set equal to 0. For both IRAP and GDR pictures, the above operations are used to identify the CVS in the bitstream. Decoding is repeatedly called for each coded picture in BitstreamToDecode in decoding order.

[0163] An exemplary decoding process for reference picture list construction is as follows: This process is invoked at the beginning of the decoding process for each slice of a non-IDR picture. Reference pictures are addressed through a reference index. The reference index is an index into the reference picture list. When decoding an I slice, the reference picture list is not used in decoding the slice data. When decoding a P slice, only reference picture list 0 (e.g., RefPicList[0]) is used in decoding the slice data. When decoding a B slice, reference picture list 0 and reference picture list 1 (e.g., RefPicList[1]) are used in decoding the slice data.

[0164] The following constraints apply for bitstream conformance: For each i equal to 0 or 1, num_ref_entries[i][RplsIdx[i]] should not be less than NumRefIdxActive[i]. The picture referenced by each active entry in RefPicList[0] or RefPicList[1] should be present in the DPB and should have a TemporalId less than or equal to the TemporalId of the current picture. The picture referenced by each entry in RefPicList[0] or RefPicList[1] should not be the current picture and should have a non_reference_picture_flag equal to 0. A short-term reference picture (STRP) entry in RefPicList[0] or RefPicList[1] of a slice of a picture and a long-term reference picture (LTRP) entry in RefPicList[0] or RefPicList[1] of the same slice or a different slice of the same picture should not reference the same picture. There should be no LTRP entries in RefPicList[0] or RefPicList[1] where the difference between the PicOrderCntVal of the current picture and the PicOrderCntVal of the picture referenced by that entry is 224 or more.

[0165] Let setOfRefPics be the set of unique pictures referenced by all entries in RefPicList[0] with the same nuh_layer_id as the current picture and all entries in RefPicList[1] with the same nuh_layer_id as the current picture. The number of pictures in setOfRefPics should be less than or equal to MaxDecPicBuffMinus1, and setOfRefPics should be the same for all slices of a picture. When the current picture is a Progressive Temporal Sub-layer Access (STSA) picture, there should be no active entries in RefPicList[0] or RefPicList[1] with TemporalId equal to the TemporalId of the current picture. When the current picture is a picture that follows, in decoding order, an STSA picture with a TemporalId equal to the TemporalId of the current picture, there shall be no picture with a TemporalId equal to the TemporalId of the current picture included as an active entry in RefPicList[0] or RefPicList[1] preceding the STSA picture in decoding order.

[0166] The pictures referenced by each Inter-Layer Reference Picture (ILRP) entry in RefPicList[0] or RefPicList[1] of the slices of the current picture shall be in the same access unit as the current picture. The pictures referenced by each ILRP entry in RefPicList[0] or RefPicList[1] of the slices of the current picture shall be present in the DPB and shall have a nuh_layer_id less than the nuh_layer_id of the current picture. Each ILRP entry in RefPicList[0] or RefPicList[1] of a slice shall be an active entry.

[0167] An example HRD specification is as follows: The HRD is used to check the conformance of the bitstream and the decoder. A set of bitstream conformance tests is used to check the conformance of the entire bitstream, denoted as the entireBitstream. The set of bitstream conformance tests is for testing the conformance of each OP of each OLS specified by the VPS.

[0168] For each test, the following ordered steps are applied in the order listed, followed by the process described after these steps in this section: An operation point to be tested, denoted targetOp, is selected by selecting the target OLS with OLS index opOlsIdx and highest TemporalId value opTid. The value of opOlsIdx is in the range from 0 to TotalNumOlss-1. The value of opTid is in the range from 0 to vps_max_sub_layers_minus1. For each selected pair of values ​​of opOlsIdx and opTid, it shall be such that the sub-bitstream output by invoking the sub-bitstream extraction process with entireBitstream, opOlsIdx, and opTid as inputs satisfies the following condition: There is at least one VCL NAL unit with nuh_layer_id value equal to nuh_layer_id in LayerIdInOls[opOlsIdx] in BitstreamToDecode. There is at least one VCL NAL unit in BitstreamToDecode whose TemporalId is equal to opTid.

[0169] If the layers in targetOp include all layers in the entireBitstream and opTid is greater than or equal to the highest TemporalId value among all NAL units in the entireBitstream, then BitstreamToDecode is set to be identical to the entireBitstream. Otherwise, BitstreamToDecode is set to be the output by invoking a sub-bitstream extraction process with entireBitstream, opOlsIdx, and opTid as input. The values ​​of TargetOlsIdx and Htid are set to be equal to the opOlsIdx and opTid of targetOp, respectively. A value of ScIdx is selected. The selected ScIdx shall be in the range from 0 to hrd_cpb_cnt_minus1. The access unit in BitstreamToDecode associated with the buffering period SEI message applicable to TargetOlsIdx (present in TargetLayerBitstream or available through an external mechanism) is selected as the HRD initialization point and is referred to as access unit 0 for each layer of the target OLS.

[0170] The subsequent steps are applied to each layer with OLS layer index TargetOlsLayerIdx in the target OLS. The ols_hrd_parameters() syntax structures and sub_layer_hrd_parameters() syntax structures applicable to BitstreamToDecode are selected as follows: The ols_hrd_idx[TargetOlsIdx]th ols_hrd_parameters() syntax structure in the VPS (or provided through an external mechanism) is selected. Within the selected ols_hrd_parameters() syntax structure, if BitstreamToDecode is a Type I bitstream, then the sub_layer_hrd_parameters(Htid) syntax structure that comes immediately after the condition if(general_vcl_hrd_params_present_flag) is selected and the variable NalHrdModeFlag is set equal to 0. Otherwise (if BitstreamToDecode is a type II bitstream), the sub_layer_hrd_parameters(Htid) syntax structure that comes immediately after either the condition if(general_vcl_hrd_params_present_flag) (in this case the variable NalHrdModeFlag is set equal to 0) or the condition if(general_nal_hrd_params_present_flag) (in this case the variable NalHrdModeFlag is set equal to 1) is selected. When BitstreamToDecode is a type II bitstream and NalHrdModeFlag is equal to 0, all non-VCL NAL units except filler data NAL units, as well as all leading_zero_8bits, zero_byte, start_code_prefix_one_3bytes, and trailing_zero_8bits syntax elements that form the byte stream from the NAL unit stream, when present, are discarded from BitstreamToDecode and the remaining bitstream is assigned to BitstreamToDecode.

[0171] When decoding_unit_hrd_params_present_flag is equal to 1, the CPB is scheduled to operate either at the access unit level (in this case the variable DecodingUnitHrdFlag is set equal to 0) or at the decoding unit level (in this case the variable DecodingUnitHrdFlag is set equal to 1). Otherwise, DecodingUnitHrdFlag is set equal to 0 and the CPB is scheduled to operate at the access unit level.

[0172] For each access unit in BitstreamToDecode starting with access unit 0, a buffering period SEI message (present in BitstreamToDecode or available through an external mechanism) associated with the access unit and applied to TargetOlsIdx is selected, a picture timing period SEI message (present in BitstreamToDecode or available through an external mechanism) associated with the access unit and applied to TargetOlsIdx is selected, and when DecodingUnitHrdFlag is equal to 1 and decoding_unit_cpb_params_in_pic_timing_sei_flag is equal to 0, a decoding unit information SEI message (present in BitstreamToDecode or available through an external mechanism) associated with a decoding unit in the access unit and applied to TargetOlsIdx is selected.

[0173] Each conformance test includes a combination of one option in each of the steps above. When there are multiple options for a step, only one option is selected for any particular conformance test. All possible combinations of all steps form the entire set of conformance tests. For each operation point under test, the number of bitstream conformance tests to be performed is equal to n0*n1*n2*n3, where the values ​​of n0, n1, n2, and n3 are specified as follows: n1 is equal to hrd_cpb_cnt_minus1+1. n1 is the number of access units in BitstreamToDecode associated with the buffering period SEI message. n2 is derived as follows: If BitstreamToDecode is a type I bitstream, then n0 is equal to 1. Otherwise (if BitstreamToDecode is a type II bitstream), then n0 is equal to 2. n3 is derived as follows: If decoding_unit_hrd_params_present_flag is equal to 0, then n3 is equal to 1. Otherwise, n3 is equal to 2.

[0174] The HRD includes a bitstream extractor (optionally present), a coded picture buffer (CPB), an instantaneous decoding process, a decoded picture buffer (DPB) that conceptually contains sub-DPBs for each layer, and output cropping. For each bitstream conformance test, the CPB size (in bits) is CpbSize[Htid][ScIdx], and the DPB parameters max_dec_pic_buffering_minus1[Htid], max_num_reorder_pics[Htid], and MaxLatencyPictures[Htid] for each layer are found in or derived from the dpb_parameters() syntax structure that applies to that layer depending on whether the layer is an independent layer and whether the layer is an output layer of the target OLS.

[0175] The HRD may operate as follows: The HDR is initialized at decoding unit 0, and both the CPB and each sub-DPB of the DPB are set to empty (the sub-DPB fullness for each sub-DPB is set to be equal to 0). After initialization, the HRD cannot be initialized again by a subsequent buffering period SEI message. The data associated with the decoding unit that flows into each CPB according to a specified arrival schedule is delivered by a virtual stream scheduler (HSS). The data associated with each decoding unit is removed and decoded instantly by an instantaneous decoding process at the CPB removal time of the decoding unit. Each decoded picture is placed in the DPB. The decoded picture is removed from the DPB when the decoded picture is no longer needed for inter-prediction reference and no longer needed for output.

[0176] An exemplary operation of the decoded picture buffer is as follows: These specifications may be applied independently to each set of selected decoded picture buffer (DPB) parameters. The decoded picture buffer conceptually includes sub-DPBs, each of which includes a picture storage buffer for storing decoded pictures of one layer. Each of the picture storage buffers may include decoded pictures that are marked for reference use or are retained for later output. The processes described herein are applied sequentially, and are applied independently for each layer starting from the lowest layer in the OLS, in order of increasing nuh_layer_id values ​​of the layers in the OLS. When these processes are applied for a particular layer, only the sub-DPB for the particular layer is affected. In the description of these processes, DPB refers to the sub-DPB for a particular layer, and that particular layer is referred to as the current layer.

[0177] In Output Timing DPB operation, decoded pictures in the same access unit with PicOutputFlag equal to 1 are output consecutively in ascending order of the decoded pictures' nuh_layer_id values. Let picture n and the current picture be the coded or decoded pictures of access unit n for a particular value of nuh_layer_id, where n is a non-negative integer value. Removal of pictures from the DPB before decoding of the current picture occurs as follows: Removal of pictures from the DPB before decoding of the current picture (but after parsing the slice header of the first slice of the current picture) occurs virtually instantaneously at the CPB removal time of the first decoding unit of access unit n (including the current picture) and proceeds as follows:

[0178] The decoding process for reference picture list construction is invoked, and the decoding process for reference picture marking is invoked. When the current AU is a Coded Video Sequence Start (CVSS) AU that is not AU0, the following ordered steps are applied: The variable NoOutputOfPriorPicsFlag is derived for the decoder under test as follows: If the values ​​of pic_width_max_in_luma_samples, pic_height_max_in_luma_samples, chroma_format_idc, separate_colour_plane_flag, bit_depth_luma_minus8, bit_depth_chroma_minus8 or max_dec_pic_buffering_minus1[Htid] derived for any picture in the current AU differ from the values ​​of pic_width_in_luma_samples, pic_height_in_luma_samples, chroma_format_idc, separate_colour_plane_flag, bit_depth_luma_minus8, bit_depth_chroma_minus8 or max_dec_pic_buffering_minus1[Htid] respectively derived for a preceding picture in the same CLVS, NoOutputOfPriorPicsFlag may be set to 1 by the decoder under test regardless of the value of no_output_of_prior_pics_flag. Although setting NoOutputOfPriorPicsFlag equal to no_output_of_prior_pics_flag may be preferable under these conditions, the decoder under test is permitted to set NoOutputOfPriorPicsFlag to 1 in this case. Otherwise, NoOutputOfPriorPicsFlag is set equal to no_output_of_prior_pics_flag.

[0179] The derived value of NoOutputOfPriorPicsFlag for the decoder under test is applied against the HRD so that when the value of NoOutputOfPriorPicsFlag is equal to 1, all picture storage buffers in the DPB are emptied without output of the pictures they contain and the DPB fullness is set to be equal to 0. When both of the following conditions are true for any picture k in the DPB, all such pictures k in the DPB are removed from the DPB: Picture k may be marked as unused for reference, or picture k may have PictureOutputFlag equal to 0, or the DPB output time is less than or equal to the CPB removal time of the first decoding unit (denoted as decoding unit m) of the current picture n, and DpbOutputTime[k] is less than or equal to DuCpbRemovalTime[m]. For each picture removed from the DPB, the DPB fullness is decremented by 1.

[0180] The operation of the output order DPB may be as follows: These processes may be applied independently for each set of selected decoded picture buffer (DPB) parameters. The decoded picture buffer conceptually includes sub-DPBs, each of which includes a picture storage buffer for storing decoded pictures of one layer. Each of the picture storage buffers includes decoded pictures that are marked for reference use or are retained for future output. A process for outputting and removing pictures from the DPB is invoked before the decoding of the current picture, followed by a process for marking and storing the current decoded picture, followed finally by a process for additional bumping. These processes are applied independently for each layer, starting with the lowest layer in the OLS, in order of increasing nuh_layer_id values ​​of the layers in the OLS. When these processes are applied for a particular layer, only the sub-DPB for the particular layer is affected.

[0181] In the operation of the Output Order DPB, similar to the operation of the Output Timing DPB, decoded pictures with PicOutputFlag equal to 1 within the same access unit are also output consecutively in ascending order of the nuh_layer_id values ​​of the decoded pictures. Let picture n and current picture be the coded or decoded pictures of access unit n for a particular value of nuh_layer_id, where n is a non-negative integer value. The output and removal of pictures from the DPB are described as follows:

[0182] Output and removal of a picture from the DPB before decoding of the current picture (but after parsing the slice header of the first slice of the current picture) occurs substantially instantaneously when the first decoding unit of the access unit containing the current picture is removed from the CPB, and proceeds as follows: The decoding process for reference picture list construction is invoked, and the decoding process for reference picture marking is invoked. If the current AU is a CVSS AU that is not AU0, then the following ordered steps are applied: The variable NoOutputOfPriorPicsFlag is derived for the decoder under test as follows: If the values ​​of pic_width_max_in_luma_samples, pic_height_max_in_luma_samples, chroma_format_idc, separate_colour_plane_flag, bit_depth_luma_minus8, bit_depth_chroma_minus8 or max_dec_pic_buffering_minus1[Htid] derived for any picture in the current AU differ from the values ​​of pic_width_in_luma_samples, pic_height_in_luma_samples, chroma_format_idc, separate_colour_plane_flag, bit_depth_luma_minus8, bit_depth_chroma_minus8 or max_dec_pic_buffering_minus1[Htid] respectively derived for a preceding picture in the same CLVS, NoOutputOfPriorPicsFlag may be set to 1 by the decoder under test regardless of the value of no_output_of_prior_pics_flag.

[0183] Although setting NoOutputOfPriorPicsFlag equal to no_output_of_prior_pics_flag may be preferable under these conditions, the decoder under test is allowed to set NoOutputOfPriorPicsFlag to 1 in this case. Otherwise, NoOutputOfPriorPicsFlag is set equal to no_output_of_prior_pics_flag. The value of the variable NoOutputOfPriorPicsFlag derived for the decoder under test is applied for the HRD as follows: If NoOutputOfPriorPicsFlag is equal to 1, all picture storage buffers in the DPB are emptied without output of the pictures they contain, and the DPB fullness is set equal to 0. Otherwise (NoOutputOfPriorPicsFlag is equal to 0), all picture storage buffers containing pictures marked as not needed for output and unused for reference are emptied (without output), all non-empty picture storage buffers in the DPB are emptied by repeatedly invoking bumping, and the DPB fullness is set equal to 0.

[0184] Otherwise (if the current picture is not a CLVSS picture), all picture storage buffers containing pictures marked as not needed for output and unused for reference are emptied (without output). For each picture storage buffer emptied, the DPB fullness is decremented by one. When one or more of the following conditions are true, the bumping process is repeatedly invoked while further decrementing the DPB fullness by one for each additional picture storage buffer emptied until none of the following conditions are true: The number of pictures in the DPB that are marked as needed for output is greater than max_num_reorder_pics[Htid]. max_latency_increase_plus1[Htid] is not equal to 0 and there is at least one picture in the DPB that is marked as needed for output whose associated variable PicLatencyCount is greater than or equal to MaxLatencyPictures[Htid]. The number of pictures in the DPB is greater than or equal to max_dec_pic_buffering_minus1[Htid]+1.

[0185] In one example, the additional bumping may occur as follows: The specified process may occur substantially instantaneously when the last decoding unit of the access unit n containing the current picture is removed from the CPB. When the current picture has PictureOutputFlag equal to 1, for each picture in the DPB that is marked as needed for output and that follows the current picture in output order, the associated variable PicLatencyCount is set equal to PicLatencyCount+1. The following also applies: If the current decoded picture has PictureOutputFlag equal to 1, the current decoded picture is marked as needed for output and the associated variable PicLatencyCount is set equal to 0. Otherwise (if the current decoded picture has PictureOutputFlag equal to 0), the current decoded picture is marked as not needed for output.

[0186] When one or more of the following conditions are true, the bumping process is repeatedly called until none of the following conditions are true: The number of pictures in the DPB that are marked as needed for output is greater than max_num_reorder_pics[Htid]. max_latency_increase_plus1[Htid] is not equal to 0 and there is at least one picture in the DPB that is marked as needed for output whose associated variable PicLatencyCount is greater than or equal to MaxLatencyPictures[Htid].

[0187] The bumping process includes the following ordered steps: The picture or pictures that are first for output are selected as those with the minimum value of PicOrderCntVal of all pictures in the DPB marked as needed for output. Each of these pictures is cropped using the conformance cropping window for pictures in ascending nuh_layer_id order, the cropped picture is output, and the picture is marked as not needed for output. Each picture storage buffer, including pictures marked as unused for reference, that was one of the cropped and output pictures is emptied and the fullness of the associated sub-DPB is decremented by one. For any two pictures picA and picB that belong to the same CVS and are output by the bumping process, when picA is output earlier than picB, the value of PicOrderCntVal of picA is less than the value of PicOrderCntVal of picB.

[0188] An exemplary sub-bitstream extraction process is as follows: The inputs to this process are the bitstream inBitstream, a target OLS index targetOlsIdx, and a target highest TemporalId value tIdTarget. The output of this process is the sub-bitstream outBitstream. A bitstream conformance requirement may be that for any input bitstream, the output from this process with inputs the bitstream, targetOlsIdx equal to an index into a list of OLSs specified by the VPS, and tIdTarget equal to any value in the range from 0 to 6, inclusive, is an output sub-bitstream that satisfies the following conditions: The output sub-bitstream contains at least one VCL NAL unit with nuh_layer_id equal to each of the nuh_layer_id values ​​in LayerIdInOls[targetOlsIdx]. The output sub-bitstream contains at least one VCL NAL unit with TemporalId equal to tIdTarget. A conforming bitstream contains one or more coded slice NAL units with TemporalId equal to 0, but may have no coded slice NAL units with nuh_layer_id equal to 0.

[0189] The output sub-bitstream OutBitstream is derived as follows: The bitstream outBitstream is set to be identical to the bitstream inBitstream. All NAL units with TemporalId greater than tIdTarget are removed from outBitstream. All NAL units with nuh_layer_id that is not included in the list LayerIdInOls[targetOlsIdx] are removed from outBitstream. All SEI NAL units that contain a scalable nesting SEI message with nesting_ols_flag equal to 1, no value of i is in the range from 0 to nesting_num_olss_minus1, and NestingOlsIdx[i] equal to targetOlsIdx are removed from outBitstream. When targetOlsIdx is greater than 0, all SEI NAL units, including non-scalable nested SEI messages with payloadType equal to 0 (buffering duration), 1 (picture timing), or 130 (decoding unit information), are removed from outBitstream.

[0190] An example scalable nesting SEI message syntax is as follows:

[0191] [Table 7]

[0192] Exemplary general SEI payload semantics are as follows: On the applicable layer or OLS of a non-scalable nested SEI message, the following applies: For a non-scalable nested SEI message, when payloadType is equal to 0 (buffering duration), 1 (picture timing), or 130 (decoding unit information), the non-scalable nested SEI message applies only to the 0th OLS. For a non-scalable nested SEI message, when payloadType is equal to any value in VclAssociatedSeiList, the non-scalable nested SEI message applies only to the layer with nuh_layer_id equal to the nuh_layer_id of the SEI NAL unit until which the VCL NAL unit contains the SEI message.

[0193] A bitstream conformance requirement may be that the following restrictions apply to the value of nuh_layer_id of an SEI NAL unit: When a non-scalable nested SEI message has payloadType equal to 0 (buffering duration), 1 (picture timing), or 130 (decoding unit information), the SEI NAL unit that contains the non-scalable nested SEI message should have nuh_layer_id equal to vps_layer_id[0]. When a non-scalable nested SEI message has payloadType equal to any value in VclAssociatedSeiList, the SEI NAL unit that contains the non-scalable nested SEI message should have nuh_layer_id equal to the value of nuh_layer_id of the VCL NAL unit associated with the SEI NAL unit. An SEI NAL unit containing a scalable nesting SEI message should have a nuh_layer_id equal to the minimum of nuh_layer_id of all layers to which the scalable nesting SEI message applies (when nesting_ols_flag of the scalable nesting SEI message is equal to 0) or the minimum of nuh_layer_id of all layers in the OLS to which the scalable nesting SEI message applies (when nesting_ols_flag of the scalable nesting SEI message is equal to 1).

[0194] Exemplary scalable nesting SEI message semantics are as follows: The scalable nesting SEI message provides a mechanism to associate an SEI message with a particular OLS or with a particular layer. The scalable nesting SEI message contains one or more SEI messages. An SEI message contained in a scalable nesting SEI message is also referred to as a scalable nest SEI message. A bitstream conformance requirement may be that the following restrictions apply to the inclusion of an SEI message within a scalable nesting SEI message:

[0195] An SEI message with payloadType equal to 132 (decoded picture hash) or 133 (scalable nesting) may not be included in a scalable nesting SEI message. When a scalable nesting SEI message contains a buffering period, picture timing, or decoding unit information SEI message, the scalable nesting SEI message should not also contain any other SEI message with payloadType not equal to 0 (buffering period), 1 (picture timing), or 130 (decoding unit information).

[0196] A bitstream conformance requirement may be that the following restrictions apply to the value of nal_unit_type of an SEI NAL unit that contains a scalable nesting SEI message: When a scalable nesting SEI message contains an SEI message with payloadType equal to 0 (buffering period), 1 (picture timing), 130 (decoding unit information), 145 (dependent RAP indication), or 168 (frame field information), the SEI NAL unit that contains the scalable nesting SEI message should have nal_unit_type equal to PREFIX_SEI_NUT.

[0197] nesting_ols_flag equal to 1 specifies that the scalable nesting SEI message applies to a specific OLS. nesting_ols_flag equal to 0 specifies that the scalable nesting SEI message applies to a specific layer. Bitstream conformance requirements may be that the following restrictions apply to the value of nesting_ols_flag: When the scalable nesting SEI message contains an SEI message with payloadType equal to 0 (buffering duration), 1 (picture timing), or 130 (decoding unit information), the value of nesting_ols_flag shall be equal to 1. When the scalable nesting SEI message contains an SEI message with payloadType equal to a value in VclAssociatedSeiList, the value of nesting_ols_flag shall be equal to 0. nesting_num_olss_minus1+1 specifies the number of OLSs to which the scalable nesting SEI message applies. The value of nesting_num_olss_minus1 should be in the range from 0 to TotalNumOlss-1.

[0198] nesting_ols_idx_delta_minus1[i] is used to derive the variable NestingOlsIdx[i], which specifies the OLS index of the ith OLS to which the scalable nesting SEI message applies when nesting_ols_flag is equal to 1. The value of nesting_ols_idx_delta_minus1[i] should be in the range from 0 to TotalNumOlss-2. The variable NestingOlsIdx[i] may be derived as follows: if(i==0) NestingOlsIdx[i]=nesting_ols_idx_delta_minus1[i] else NestingOlsIdx[i]=NestingOlsIdx[i-1]+nesting_ols_idx_delta_minus1[i]+1

[0199] nesting_all_layers_flag equal to 1 specifies that the scalable nesting SEI message applies to all layers with nuh_layer_id greater than or equal to the nuh_layer_id of the current SEI NAL unit. nesting_all_layers_flag equal to 0 specifies that the scalable nesting SEI message may or may not apply to all layers with nuh_layer_id greater than or equal to the nuh_layer_id of the current SEI NAL unit. nesting_num_layers_minus1+1 specifies the number of layers to which the scalable nesting SEI message applies. The value of nesting_num_layers_minus1 should be in the range from 0 to vps_max_layers_minus1-GeneralLayerIdx[nuh_layer_id], where nuh_layer_id is the nuh_layer_id of the current SEI NAL unit. nesting_layer_id[i] specifies the nuh_layer_id value of the i-th layer to which the scalable nested SEI message applies when nesting_all_layers_flag is equal to 0. The value of nesting_layer_id[i] should be greater than nuh_layer_id, where nuh_layer_id is the nuh_layer_id of the current SEI NAL unit.

[0200] When nesting_ols_flag is equal to 0, the variable NestingNumLayers, which specifies the number of layers to which the scalable nesting SEI message applies, and the list NestingLayerId[i], for i in the range from 0 to NestingNumLayers-1, which specifies the list of layer nuh_layer_id values ​​to which the scalable nesting SEI message applies, may be derived as follows, where nuh_layer_id is the nuh_layer_id of the current SEI NAL unit: if(nesting_all_layers_flag) { NestingNumLayers=vps_max_layers_minus1+1-GeneralLayerIdx[nuh_layer_id] for(i=0; i <NestingNumLayers; i++) NestingLayerId[i]=vps_layer_id[GeneralLayerIdx[nuh_layer_id]+i] } else { NestingNumLayers=nesting_num_layers_minus1+1 for(i=0; i <NestingNumLayers; i++) NestingLayerId[i]=(i==0) ? nuh_layer_id: nesting_layer_id[i] }

[0201] nesting_num_seis_minus1+1 specifies the number of scalable nested SEI messages. The value of nesting_num_seis_minus1 should be in the range of 0 to 63. nesting_zero_bit shall be equal to 0.

[0202] FIG. 9 is a schematic diagram of an exemplary video coding device 900. The video coding device 900 is suitable for implementing the disclosed examples / embodiments as described herein. The video coding device 900 comprises a downstream port 920, an upstream port 950, and / or a transceiver unit (Tx / Rx) 910 including a transmitter and / or a receiver for data communication upstream and / or downstream of a network. The video coding device 900 comprises a processor 930 including a logic unit and / or a central processing unit (CPU) for processing data, and a memory 932 for storing data. The video coding device 900 may also comprise electrical, optical-electrical (OE) components, electrical-optical (EO) components, and / or wireless communication components coupled to the upstream port 950 and / or the downstream port 920 for data communication over an electrical, optical, or wireless communication network. The video coding device 900 may also include an input and / or output (I / O) device 960 for communicating data to and receiving data from a user. The I / O devices 960 may include output devices such as a display for displaying video data, speakers for outputting audio data, etc. The I / O devices 960 may also include input devices such as a keyboard, mouse, trackball, etc., and / or corresponding interfaces for interactively manipulating such output devices.

[0203] The processor 930 is implemented by hardware and software. The processor 930 may be implemented as one or more CPU chips, cores (e.g., as a multi-core processor), field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), and digital signal processors (DSPs). The processor 930 communicates with the downstream port 920, the Tx / Rx 910, the upstream port 950, and the memory 932. The processor 930 comprises a coding module 914. The coding module 914 implements the disclosed embodiments described herein, such as the methods 100, 1000, and 1100, and may employ the multi-layer video sequence 600, the RPL structure 700, and / or the bitstream 800. The coding module 914 may also implement any other method / mechanism described herein. Furthermore, the coding module 914 may implement the codec system 200, the encoder 300, the decoder 400, and / or the HRD 500. For example, the coding module 914 may constrain the number of reference entries of the RPL structure based on the maximum decoded picture size. The maximum decoded picture buffer size may vary depending on whether the layer is a reference layer or an output layer. Hence, by applying this constraint, the coding module 914 may allow a different number of reference pictures to be employed for the output layer and the reference layer. This allows the coding module 914 to more optimally use memory and increase coding efficiency. Thus, the coding module 914 may be configured to perform mechanisms to address one or more of the problems described above. Thus, the coding module 914 causes the video coding device 900 to provide additional functionality and / or coding efficiency when coding video data. Thus, the coding module 914 improves the functionality of the video coding device 900 and also addresses problems specific to video coding techniques.Additionally, the coding module 914 performs transformations to different states of the video coding device 900. Alternatively, the coding module 914 may be implemented as instructions stored in the memory 932 and executed by the processor 930 (e.g., as a computer program product stored on a non-transitory medium).

[0204] Memory 932 may include one or more memory types such as a disk, a tape drive, a solid state drive, a read only memory (ROM), a random access memory (RAM), flash memory, a ternary content addressable memory (TCAM), a static random access memory (SRAM), etc. Memory 932 may store programs when such programs are selected for execution, and may be used as an overflow data storage device to store instructions and data retrieved during the execution of programs.

[0205] 10 is a flowchart of an example method 1000 of encoding a video sequence into a bitstream, such as bitstream 800, based on a reference picture list structure, such as RPL structure 700, in which the number of reference entries is constrained according to a maximum decoded picture buffer size. Method 1000 may be employed by an encoder, such as codec system 200, encoder 300, and / or video coding device 900, when performing method 100. Furthermore, method 1000 may operate on HRD 500 and thus perform conformance tests on multi-layer video sequence 600 and / or its extracted layers.

[0206] The method 1000 may start when an encoder receives a video sequence and decides to encode the video sequence, such as a multi-layer video sequence, into a bitstream, for example based on a user input. In step 1001, the encoder encodes a picture from the video sequence into a bitstream. For example, the encoder may encode a current picture according to inter prediction and / or inter-layer prediction. Thus, the encoder encodes the current picture based on a reference picture.

[0207] In step 1003, the encoder may encode ref_pic_list_struct() into the bitstream, for example in an SPS, a picture header, and / or a slice header. ref_pic_list_struct() indicates reference pictures used when coding the current picture according to inter prediction. Specifically, ref_pic_list_struct() includes RefPicList[0] and RefPicList[1]. RefPicList[0] and RefPicList[1] each include one or more reference entries that reference any reference pictures used in coding the current picture. ref_pic_list_struct() is referenced according to a list index (listIdx) and a reference picture list structure index (rplsIdx), and is denoted as ref_pic_list_struct(listIdx, rplsIdx). ref_pic_list_struct() references setOfRefPics, a set-specific picture referenced by all entries in RefPicList[0] with the same nuh_layer_id as the current picture and all entries in RefPicList[1] with the same nuh_layer_id as the current picture. Thus, setOfRefPics contains all of the reference pictures for the current picture that are in the same layer as the current picture. setOfRefPics may be constrained to be the same set for all slices of each picture. Hence, setOfRefPics may be constrained to be the same set for all slices of the current picture. Furthermore, ref_pic_list_struct(), and therefore the bitstream, contains num_ref_entries. num_ref_entries may be denoted as num_ref_entries[listIdx][rplsIdx]. num_ref_entries[listIdx][rplsIdx] specifies the number of entries in ref_pic_list_struct(listIdx, rplsIdx).num_ref_entries is constrained to a range based on the maximum decoded picture buffer size, such as a range from 0 to the maximum decoded picture buffer size plus an offset such as 13 or 14 entries. Additionally, setOfRefPics referenced in ref_pic_list_struct is constrained to be less than or equal to the maximum decoded picture buffer size minus 1. In this manner, both num_ref_entries and setOfRefPics are constrained based on available memory in the DPB, which varies based on layer, and not based on a static value global to all layers. This allows these values ​​to change based on whether the current picture is associated with an output layer, which takes up more memory space, or a reference layer, which takes up less space. Hence, constraining num_ref_entries and setOfRefPics based on the maximum DPB size supports improved coding efficiency (better compression), which reduces the use of processor, memory, and / or network signaling resources.

[0208] The encoder also encodes dpb_parameters() in the bitstream, e.g., in the VPS and / or SPS. dpb_parameters() may include max_dec_pic_buffering_minus1, which specifies the maximum required size of the DPB in units of picture storage buffer. Hence, the maximum decoded picture buffer size used to constrain num_ref_entries and setOfRefPics corresponds to max_dec_pic_buffering_minus1.

[0209] In step 1005, the HRD in the encoder may perform a series of bitstream conformance tests on the bitstream. As a specific example, the HRD may check the bitstream to ensure that num_ref_entries and setOfRefPics are constrained based on the maximum DPB size, e.g., as described by max_dec_pic_buffering_minus1 in dpb_parameters(). The encoder may then store the bitstream in step 1007 for communication to a decoder upon request. For example, the encoder may store the bitstream locally and / or forward the bitstream to a content server for storage. Additionally, the encoder and / or content server may perform sub-bitstream extraction on the bitstream to separate content related to layers and / or OLS for transmission to a decoder upon request.

[0210] 11 is a flowchart of an example method 1100 of decoding a video sequence from a bitstream, such as bitstream 800, based on a reference picture list structure, such as RPL structure 700, in which the number of reference entries is constrained according to a maximum decoded picture buffer size. Method 1100 may be employed by a decoder, such as codec system 200, decoder 400, and / or video coding device 900, when performing method 100. Additionally, method 1100 may be employed on multi-layer video sequence 600, or an extracted layer thereof, that has been checked for conformance by an HRD, such as HRD 500.

[0211] Method 1100 may start when a decoder begins to receive a bitstream including a coded video sequence, such as a coded layer video sequence, from one or more layers of a multi-layer bitstream, e.g., as a result of method 1000. In step 1101, the decoder receives a bitstream. The bitstream includes a sequence of pictures including a current picture, which may be any specified picture being decoded at a specified time. In this example, the current picture is coded according to inter prediction and / or inter-layer prediction. Hence, the encoder encodes the current picture based on a reference picture.

[0212] The bitstream also includes a ref_pic_list_struct(), e.g., in an SPS, a picture header, and / or a slice header. The ref_pic_list_struct() indicates the reference pictures used when coding the current picture according to inter prediction. Specifically, the ref_pic_list_struct() includes RefPicList[0] and RefPicList[1]. RefPicList[0] and RefPicList[1] each include one or more reference entries that reference any reference pictures used in coding the current picture. The ref_pic_list_struct() is referenced according to a list index (listIdx) and a reference picture list structure index (rplsIdx), and is denoted as ref_pic_list_struct(listIdx, rplsIdx). ref_pic_list_struct() references setOfRefPics, a set-specific picture referenced by all entries in RefPicList[0] with the same nuh_layer_id as the current picture and all entries in RefPicList[1] with the same nuh_layer_id as the current picture. Thus, setOfRefPics contains all of the reference pictures for the current picture that are in the same layer as the current picture. setOfRefPics may be constrained to be the same set for all slices of each picture. Hence, setOfRefPics may be constrained to be the same set for all slices of the current picture. Furthermore, ref_pic_list_struct(), and therefore the bitstream, contains num_ref_entries. num_ref_entries may be denoted as num_ref_entries[listIdx][rplsIdx]. num_ref_entries[listIdx][rplsIdx] specifies the number of entries in ref_pic_list_struct(listIdx, rplsIdx).num_ref_entries is constrained to a range based on the maximum decoded picture buffer size, such as a range from 0 to the maximum decoded picture buffer size plus an offset such as 13 or 14 entries. Additionally, setOfRefPics referenced in ref_pic_list_struct is constrained to be less than or equal to the maximum decoded picture buffer size minus 1. In this manner, both num_ref_entries and setOfRefPics are constrained based on the available memory in the DPB for the corresponding layer, and not based on a static value applicable to all layers. This allows these values ​​to change based on whether the current picture is associated with an output layer that employs more memory space, or a reference layer that employs less space. Hence, constraining num_ref_entries and setOfRefPics based on the maximum DPB size supports improved coding efficiency (better compression), thereby reducing the use of processor, memory, and / or network signaling resources.

[0213] The bitstream further includes dpb_parameters(), for example in the VPS and / or SPS. The dpb_parameters() may include max_dec_pic_buffering_minus1, which specifies the maximum required size of the DPB in units of picture storage buffer. Hence, the maximum decoded picture buffer size used to constrain num_ref_entries and setOfRefPics corresponds to max_dec_pic_buffering_minus1.

[0214] In step 1103, the decoder may decode the current picture based on ref_pic_list_struct() and / or dpb_parameters() to generate a decoded picture. For example, the decoder may employ dpb_parameters() and / or max_dec_pic_buffering_minus1 to allocate memory space in the DPB. The decoder may also analyze ref_pic_list_struct() for the current picture to determine reference entries in RefPicList[0] and / or RefPicList[1] that indicate reference pictures used to code the current picture. The decoder may determine the relevant reference entries based on num_ref_entries and may determine setOfRefPics based on the reference entries. The decoder may also employ a reference picture marking process to mark all of the pictures in setOfRefPics as long-term reference use or short-term reference use based on ref_pic_list_struct(). The reference picture marking process may mark one or more of the pictures not included in setOfRefPics as reference use. Such pictures may be evicted from the DPB when they are no longer needed for output. After the reference pictures are marked, the decoder can decode the current picture based on the setOfRefPics. The decoder can also manage the DPB based on the marking of various pictures after the reference picture marking process.

[0215] The decoder may then forward the decoded pictures for display as part of a decoded video sequence, at step 1105. For example, the decoder may forward the decoded pictures and / or the decoded video sequence to a screen, head mounted display, or other display device for viewing by an end user.

[0216] 12 is a schematic diagram of an example system 1200 for coding a video sequence into a bitstream 800 based on a reference picture list structure, such as the RPL structure 700, in which the number of reference entries is constrained according to a maximum decoded picture buffer size. The system 1200 may be implemented by an encoder and a decoder, such as the codec system 200, the encoder 300, the decoder 400, and / or the video coding device 900. Furthermore, the system 1200 may employ the HRD 500 to perform a conformance test on the multi-layer video sequence 600 and / or the bitstream 800. In addition, the system 1200 may be employed when implementing the methods 100, 1000, and / or 1100.

[0217] The system 1200 comprises a video encoder 1202. The video encoder 1202 comprises an encoding module 1205 for encoding a current picture into a bitstream based on the reference picture. The encoding module 1205 is further for encoding a ref_pic_list_struct() into the bitstream, the ref_pic_list_struct() indicating the reference picture and including a number of reference entries (num_ref_entries) constrained to a range based on a maximum decoded picture buffer size. The video encoder 1202 further comprises a storage module 1206 for storing the bitstream for communication towards a decoder. The video encoder 1202 further comprises a transmission module 1207 for transmitting the bitstream towards a video decoder 1210. The video encoder 1202 may be further configured to perform any of the steps of the method 1000.

[0218] The system 1200 also comprises a video decoder 1210. The video decoder 1210 comprises a receiving module 1211 for receiving a bitstream including a current picture and a ref_pic_list_struct() including num_ref_entries that are range-constrained based on a maximum decoded picture buffer size. The video decoder 1210 further comprises a decoding module 1213 for decoding the current picture based on the ref_pic_list_struct() to generate a decoded picture. The video decoder 1210 further comprises a transport module 1215 for transporting the decoded picture for display as part of a decoded video sequence. The video decoder 1210 may be further configured to perform any of the steps of the method 1100.

[0219] A first component is directly coupled to a second component when there are no intervening components, other than a line, trace, or another medium between the first and second components. A first component is indirectly coupled to a second component when there are intervening components, other than a line, trace, or another medium between the first and second components. The term "coupled" and variations thereof include both directly coupled and indirectly coupled. Additionally, the term "about" refers to a range that includes ±10% of the succeeding numerical value, unless otherwise specified.

[0220] It should also be understood that the steps of the exemplary methods described herein do not necessarily have to be performed in the order described, and the order of steps of such methods should be understood to be merely exemplary. Similarly, additional steps may be included in such methods, and certain steps may be omitted or combined, in methods consistent with various embodiments of the present disclosure.

[0221] Although several embodiments are provided in this disclosure, it can be understood that the disclosed systems and methods can be embodied in many other specific forms without departing from the spirit or scope of the disclosure. The examples should be considered illustrative and not restrictive, and the invention should not be limited to the details set forth in the specification. For example, various elements or components can be combined or integrated in another system, or certain features can be omitted or not implemented.

[0222] Additionally, the techniques, systems, subsystems, and methods described and illustrated in various embodiments as being discrete or separate may be combined or integrated with other systems, components, techniques, or methods without departing from the scope of the present disclosure. Other examples of changes, substitutions, and alterations will be ascertainable by those skilled in the art and may be made without departing from the spirit and scope disclosed herein. [Explanation of symbols]

[0223] 100 How it works, how it works 200 Coding and Decoding (Codec) Systems, Codec Systems 201 Segmented Video Signal 211 General Coder Control Component 213 Transform Scaling and Quantization Components 215 In-Picture Estimation Component 217 Intra-Picture Prediction Component 219 Motion Compensation Component 221 Motion Estimation Component 223 Decoded Picture Buffer Component 225 In-Loop Filter Components 227 Filter Control Analysis Component 229 Scaling and Inverse Transformation Components 231 Header Formatting and Context-Adaptive Binary Arithmetic Coding (CABAC) Components 300 Video Encoder, Encoder 301 Segmented Video Signal 313 Transform and Quantize Components 317 In-Picture Prediction Component 321 Motion Compensation Component 323 Decoded Picture Buffer Component 325 In-Loop Filter Components 329 Inverse Transform and Quantization Components 331 Entropy Coding Component 400 Video Decoder, Decoder 417 In-Picture Prediction Component 421 Motion Compensation Component 423 Decoded Picture Buffer Component 425 In-Loop Filter Components 429 Inverse Transform and Quantization Components 433 Entropy Decoding Component 500HRD 541 Virtual Stream Scheduler (HSS) 543 CPB 545 Decoding Process Components 547 DPB 549 Output Cropping Component 551 Bitstream 553 Decoding Unit (DU) 555 Decoded DUs 556 Reference Pictures 557 Pictures 559 Output Cropped Picture 600 Multi-layer Video Sequences 611, 612, 613, 614 Pictures 615, 616, 617, 618 Pictures 621 Inter-layer Prediction 623 Inter Prediction 631 Lower Layer N 632 Upper Layer N+1 700 Reference Picture List (RPL) Structure 711 Reference Picture List 0 (RefPicList[0]) 712 Reference Picture List 1 (RefPicList[1]) 715 Reference Picture List Structure Entry 721 listIdx 725 rplsIdx 732 Number of reference entries (num_ref_entries) 733 Set of reference pictures (setOfRefPics) 800 bitstream 811 VPS 813 SPS 815 Picture Parameter Set (PPS) 816 Picture Header 817 slice header 820 Image data 823 Layer 825 Pictures 827 Slice 831 ref_pic_list_struct 832 num_ref_entries 835 nuh_layer_id 837 Decoded Picture Buffer Parameters (dpb_parameters) 838 max_dec_pic_buffering_minus1 841 VCL NAL units 842 non-VCL NAL units 900 Video Coding Device 910 Transceiver unit (Tx / Rx) 914 Coding Module 920 Downstream Port 930 Processor 932 Memory 950 Upstream Port 960 Input and / or Output (I / O) Devices 1000, 1100 ways 1200 System 1202 Video Encoder 1205 Encoding Module 1206 Memory Module 1207 Transmission Module 1210 Video Decoder 1211 Receiver Module 1213 Decoding Module 1215 Transfer Module

Claims

1. A method implemented by a decoder, comprising: receiving, by the decoder, a bitstream including a current picture and a reference picture list syntax structure (ref_pic_list_struct()) including a number of reference entries (num_ref_entries) constrained to range from 0 to a maximum decoded picture buffer size plus an offset; and decoding, by the decoder, the current picture based on the ref_pic_list_struct() to generate a decoded picture.

2. 2. The method of claim 1, wherein the ref_pic_list_struct() is referenced according to a list index (listIdx) and a reference picture list structure index (rplsIdx) and is denoted as ref_pic_list_struct(listIdx, rplsIdx), and the num_ref_entries is denoted as num_ref_entries[listIdx][rplsIdx], where num_ref_entries[listIdx][rplsIdx] specifies the number of entries in the ref_pic_list_struct(listIdx, rplsIdx).

3. The method of claim 1 or 2, wherein the number of pictures in a set of reference pictures (setOfRefPics) referenced in the ref_pic_list_struct is constrained to be less than or equal to the maximum decoded picture buffer size -1.

4. 4. The method of claim 1, wherein the ref_pic_list_struct() includes reference picture list 0 (RefPicList[0]) and reference picture list 1 (RefPicList[1]), and the setOfRefPics is a set-specific picture referenced by all entries in RefPicList[0] that have the same network abstraction layer (NAL) unit header layer identifier (nuh_layer_id) as the current picture and all entries in RefPicList[1] that have the same nuh_layer_id as the current picture.

5. 5. The method of claim 1, wherein the setOfRefPics is the same set for all slices of each picture.

6. 6. The method of claim 1, wherein the bitstream includes a decoded picture buffer parameters syntax structure (dpb_parameters()), the dpb_parameters() including a maximum decoded picture buffer minus 1 (max_dec_pic_buffering_minus1), the maximum decoded picture buffer size corresponding to the max_dec_pic_buffering_minus1.

7. The method according to claim 1 , wherein the dpb_parameters() is included in a video parameter set (VPS) or a sequence parameter set (SPS).

8. A method implemented by an encoder, comprising: encoding, by the encoder, a current picture based on a reference picture into a bitstream; encoding, by the encoder, into the bitstream, a reference picture list syntax structure (ref_pic_list_struct()) that indicates the reference picture and includes a number of reference entries (num_ref_entries) constrained to range from 0 to a maximum decoded picture buffer size plus an offset; storing, by the encoder, the bitstream for communication to a decoder.

9. 9. The method of claim 8, wherein the ref_pic_list_struct() is referenced according to a list index (listIdx) and a reference picture list structure index (rplsIdx) and is denoted as ref_pic_list_struct(listIdx, rplsIdx), and the num_ref_entries is denoted as num_ref_entries[listIdx][rplsIdx], where num_ref_entries[listIdx][rplsIdx] specifies the number of entries in the ref_pic_list_struct(listIdx, rplsIdx).

10. The method of claim 8 or 9, wherein the number of pictures in a set of reference pictures (setOfRefPics) referenced in the ref_pic_list_struct is constrained to be less than or equal to the maximum decoded picture buffer size -1.

11. 11. The method of claim 8, wherein the ref_pic_list_struct() includes a reference picture list 0 (RefPicList[0]) and a reference picture list 1 (RefPicList[1]), and the setOfRefPics is a set-specific picture referenced by all entries in RefPicList[0] that have the same network abstraction layer (NAL) unit header layer identifier (nuh_layer_id) as the current picture and all entries in RefPicList[1] that have the same nuh_layer_id as the current picture.

12. 12. The method of claim 8, wherein the setOfRefPics is the same set for all slices of each picture.

13. 13. A method according to claim 8, wherein the bitstream includes a decoded picture buffer parameters syntax structure (dpb_parameters()), the dpb_parameters() including a maximum decoded picture buffer minus 1 (max_dec_pic_buffering_minus1), the maximum decoded picture buffer size corresponding to the max_dec_pic_buffering_minus1.

14. The method according to claim 8 , wherein the dpb_parameters() is included in a video parameter set (VPS) or a sequence parameter set (SPS).

15. 15. A video coding device comprising: a processor; a receiver coupled to the processor; a memory coupled to the processor; and a transmitter coupled to the processor, wherein the processor, the receiver, the memory, and the transmitter are configured to perform the method of any one of claims 1 to 14.

16. A non-transitory computer-readable medium comprising a computer program product for use by a video coding device, the computer program product comprising computer-executable instructions stored on the non-transitory computer-readable medium that, when executed by a processor, causes the video coding device to perform a method according to any one of claims 1 to 14.

17. receiving means for receiving a bitstream including a current picture and a reference picture list syntax structure (ref_pic_list_struct()) including a number of reference entries (num_ref_entries) constrained to be in the range from 0 to a maximum decoded picture buffer size plus an offset; and decoding means for decoding the current picture based on the ref_pic_list_struct() to generate a decoded picture.

18. The decoder of claim 17, further configured to perform the method of any one of claims 1 to 7.

19. Encoding a current picture based on a reference picture into a bitstream; encoding means for encoding within the bitstream a reference picture list syntax structure (ref_pic_list_struct()) that indicates the reference picture and includes a number of reference entries (num_ref_entries) constrained to range from 0 to a maximum decoded picture buffer size plus an offset; and storage means for storing said bitstream for communication to a decoder.

20. 20. The encoder of claim 19, further configured to perform a method according to any one of claims 8 to 14.

Images