HRD parameters for the layer

Abstract

To provide: a video coding method that includes encoding a bitstream that includes one or more layers of a coded image; and a method performed by a decoder.SOLUTION: A method for encoding a video sequence into a bitstream includes encoding a bitstream including one or more layers of coded pictures, encoding, into the bitstream, a syntax structure of hypothetical reference decoder (HRD) parameters that specify that all of the multiple layers are associated with the same number of coded picture buffer (CPB) delivery schedules, performing a set of bitstream conformance tests on the multiple layers on the basis of the CPB delivery schedules, and storing the bitstream for communication to a decoder.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This patent application claims the benefit of U.S. Provisional Patent Application No. 62 / 905,244, entitled "Hypothetical Reference Decoder (HRD) for Multi-Layer Video Bitstreams," filed September 24, 2019 by Ye-Kui Wang, and is incorporated herein by reference.

[0002] FIELD This disclosure relates generally to video coding, and more particularly to hypothetical reference decoder (HRD) parameter modification to support efficient encoding and / or conformance testing of multi-layer bitstreams. [Background technology]

[0003] The amount of video data required to depict even a relatively short video can be enormous, which can present challenges when streaming or otherwise communicating the data over communication networks with limited bandwidth capacity. Therefore, video data is typically compressed before being communicated over modern telecommunications networks. Furthermore, when storing video on a storage device, the size of the video can be an issue because memory resources may be limited. Video compression devices often use software and / or hardware to encode video data at the source 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 increasing demands for higher quality video, improved compression and decompression techniques are desirable that increase compression ratios with little or no sacrifice in image quality. Summary of the Invention

[0004] In one embodiment, the present disclosure includes a method implemented by a decoder, the method including: receiving, by a receiver of the decoder, a bitstream including a syntax structure of hypothetical reference decoder (HRD) parameters and one or more layers of a coded image, such that all of the multiple layers are associated with as many coded picture buffer (CPB) delivery schedules as specified by the syntax structure of the HRD parameters; and decoding, by a processor of the decoder, an image from one of the layers to obtain a decoded image.

[0005] Video coding systems employ various conformance tests to ensure that a bitstream is decodable by a decoder. For example, a conformance check can include testing the entire bitstream for conformance, then testing each layer of the bitstream for conformance, and finally checking potential decodable outputs for conformance. To perform a conformance check, corresponding parameters are included in the bitstream. The HRD can read the parameters and perform the test. A video can include many layers and many different output layer sets (OLSs). Upon request, an encoder transmits one or more layers of a selected OLS. For example, the encoder can transmit the best layer from the OLS that can be supported by the current network bandwidth. Problems can arise when a video coding system performs a conformance check on a bitstream. Video may be coded into multiple layers and / or sublayers, which can then be organized into OLSs. Each layer and / or sublayer of each OLS is checked for conformance according to a delivery schedule. Each delivery schedule is associated with a different CPB size and CPB delay to account for different transmission bandwidths and system capabilities. Some video coding systems allow each sublayer to define any number of delivery schedules. This can result in a large amount of signaling to support conformance checking, resulting in reduced bitstream coding efficiency. The disclosed embodiments include a mechanism for improving coding efficiency for videos that include multiple layers. Specifically, all layers and / or sublayers are constrained to include the same number of CPB delivery schedules. For example, an encoder may determine the maximum number of CPB delivery schedules to be used for any one layer and set the number of CPB delivery schedules for all layers to this maximum number. The number of delivery schedules may then be signaled once, for example, as part of the HRD parameters in the VPS.This eliminates the need to signal several schedules per layer / sublayer. In some examples, all layers / sublayers of an OLS may even share the same delivery schedule index. These changes reduce the amount of data used to signal data related to conformance checking. This reduces the bitstream size and therefore reduces the utilization of processor, memory, and / or network resources in both the encoder and decoder.

[0006] Optionally, in any of the foregoing aspects, there is provided another implementation of the aspect, wherein the CPB delivery schedule is associated with a set of bitstream conformance tests performed by an HRD running on the encoder.

[0007] Optionally, in any of the foregoing aspects, another embodiment of the aspect is provided, wherein the number of CPB delivery schedules is specified by HRD CPB count-1 (hrd_cpb_cnt_minus1), where hrd_cpb_cnt_minus1 is in the range of 0 to 31, inclusive.

[0008] Optionally, in any of the foregoing aspects, another implementation of the aspect is provided, wherein multiple layers are organized into one or more output layer sets (OLS), and the corresponding CPB delivery schedule of the target OLS is referenced by a schedule index (ScIdx) ranging from 0 to the value of hrd_cpb_cnt_minus1, inclusive.

[0009] Optionally, in any of the aforementioned aspects, another embodiment of the aspect is provided, wherein each of the CPB delivery schedules is described by a Network Abstraction Layer (NAL) initial CPB removal delay (nal_initial_cpb_removal_delay) and a NAL initial CPB removal offset (nal_initial_cpb_removal_offset).

[0010] Optionally, in any of the aforementioned aspects, another embodiment of the aspect is provided, wherein each layer is associated with a buffering period (BP) CPB count -1 (bp_cpb_cnt_minus1) +1 that specifies the number of nal_initial_cpb_removal_delay and nal_initial_cpb_removal_offset pairs for each layer, where bp_cpb_cnt_minus1 is equal to the value of hrd_cpb_cnt_minus1.

[0011] Optionally, in any of the foregoing aspects, another embodiment of the aspect is provided, wherein the syntax structure of the HRD parameters is included in the bitstream in a video parameter set (VPS) that specifies the OLS.

[0012] In one embodiment, the present disclosure includes a method implemented by an encoder, the method including: encoding, by a processor of the encoder, a bitstream including one or more layers of a coded image; encoding, by the processor, into the bitstream a syntax structure of HRD parameters specifying that all of the multiple layers are associated with the same number of CPB delivery schedules; and performing, by the processor, a set of bitstream conformance tests on the multiple layers based on the CPB delivery schedules.

[0013] Video coding systems employ various conformance tests to ensure that a bitstream is decodable by a decoder. For example, a conformance check can include testing the entire bitstream for conformance, then testing each layer of the bitstream for conformance, and finally checking potential decodable outputs for conformance. To perform a conformance check, corresponding parameters are included in the bitstream. The HRD can read the parameters and perform the test. A video can include many layers and many different OLSs. Upon request, an encoder transmits one or more layers of a selected OLS. For example, the encoder can transmit the best layer from the OLS that can be supported by the current network bandwidth. Problems can arise when a video coding system performs a conformance check on a bitstream. Video may be coded into multiple layers and / or sublayers, which can then be organized into OLSs. Each layer and / or sublayer of each OLS is checked for conformance according to a delivery schedule. Each delivery schedule is associated with a different CPB size and CPB delay to account for different transmission bandwidths and system capabilities. Some video coding systems allow each sublayer to define any number of delivery schedules. This can result in a large amount of signaling to support conformance checking, resulting in reduced bitstream coding efficiency. The disclosed embodiments include a mechanism for improving coding efficiency for videos that include multiple layers. Specifically, all layers and / or sublayers are constrained to include the same number of CPB delivery schedules. For example, an encoder may determine the maximum number of CPB delivery schedules to be used for any one layer and set the number of CPB delivery schedules for all layers to this maximum number. The number of delivery schedules may then be signaled once, for example, as part of the HRD parameters in the VPS.This eliminates the need to signal several schedules per layer / sublayer. In some examples, all layers / sublayers of an OLS may even share the same delivery schedule index. These changes reduce the amount of data used to signal data related to conformance checking. This reduces the bitstream size and therefore reduces the utilization of processor, memory, and / or network resources in both the encoder and decoder.

[0014] Optionally, in any of the foregoing aspects, another implementation of the aspect is provided, wherein the set of bitstream conformance tests is performed by an HRD running on a processor.

[0015] Optionally, in any of the foregoing aspects, there is provided another embodiment of the aspect, wherein the number of CPB delivery schedules is specified by hrd_cpb_cnt_minus1, where hrd_cpb_cnt_minus1 is in the range of 0 to 31, inclusive.

[0016] Optionally, in any of the foregoing aspects, another embodiment of the aspect is provided, wherein multiple layers are organized into one or more OLSs, and the corresponding CPB delivery schedule of the target OLS is referenced by an ScIdx ranging from 0 to the value of hrd_cpb_cnt_minus1, inclusive.

[0017] Optionally, in any of the foregoing aspects, there is provided another implementation of the aspect, wherein each of the CPB delivery schedules is described by a nal_initial_cpb_removal_delay and a nal_initial_cpb_removal_offset.

[0018] Optionally, in any of the aforementioned aspects, another implementation of the aspect is provided, wherein each layer is associated with bp_cpb_cnt_minus1+1, which specifies the number of pairs of nal_initial_cpb_removal_delay and nal_initial_cpb_removal_offset for each layer, and bp_cpb_cnt_minus1 is equal to the value of hrd_cpb_cnt_minus1.

[0019] Optionally, in any of the foregoing aspects, there is provided another embodiment of the aspect, wherein the syntax structure of the HRD parameters is encoded into the bitstream in a VPS that specifies the OLS.

[0020] In one embodiment, the present disclosure includes a video coding apparatus 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 comprising a computer program product for use by a video coding apparatus, the computer program product comprising computer-executable instructions stored on the non-transitory computer-readable medium that, when executed by a processor, cause the video coding apparatus to perform the method of any of the foregoing aspects.

[0022] In one embodiment, the present disclosure includes a decoder comprising: receiving means for receiving a bitstream including a syntax structure of HRD parameters and one or more layers of a coded image, such that all of the multiple layers are associated with as many CPB delivery schedules as specified by the HRD parameters; decoding means for decoding an image from one of the layers to obtain a decoded image; and forwarding means for forwarding the decoded image for display as part of a decoded video sequence.

[0023] Optionally, in any of the preceding aspects, there is provided another implementation of the aspect, wherein the decoder is further configured to perform the method of any of the preceding aspects.

[0024] In one embodiment, the present disclosure includes an encoder comprising: encoding means for encoding a bitstream comprising one or more layers of a coded image, and encoding into the bitstream a syntax structure of HRD parameters specifying that all of the multiple layers are associated with the same number of CPB delivery schedules; HRD means for performing a set of bitstream conformance tests on the multiple layers based on the CPB delivery schedules; and storage means for storing the bitstream for communication to a decoder.

[0025] Optionally, in any of the preceding aspects, there is provided another implementation of the aspect, wherein the encoder is further configured to perform the method of any of the preceding aspects.

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

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

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

[0029] [Figure 1] 1 is a flowchart of an exemplary method for encoding a video signal.

[0030] [Figure 2] 1 is a schematic diagram of an exemplary coding-decoding (codec) system for video coding.

[0031] [Figure 3] FIG. 1 is a schematic diagram illustrating an exemplary video encoder.

[0032] [Figure 4] FIG. 1 is a schematic diagram illustrating an exemplary video decoder.

[0033] [Figure 5] 1 is a schematic diagram illustrating an exemplary hypothetical reference decoder (HRD).

[0034] [Figure 6] FIG. 1 is a schematic diagram illustrating an example multi-layer video sequence configured for inter-layer prediction.

[0035] [Figure 7] FIG. 1 is a schematic diagram illustrating an example multi-layer video sequence configured for temporal scalability.

[0036] [Figure 8] FIG. 2 is a schematic diagram illustrating an exemplary bitstream.

[0037] [Figure 9] 1 is a schematic diagram of an exemplary video coding device;

[0038] [Figure 10] 1 is a flowchart of an exemplary method for encoding a video sequence into a bitstream, where all layers in the bitstream have the same number of coded picture buffer (CPB) delivery schedules.

[0039] [Figure 11]10 is a flowchart of an example method for decoding a video sequence from a bitstream, where all layers in the bitstream have the same number of CPB delivery schedules.

[0040] [Figure 12] 1 is a schematic diagram of an example system for coding a video sequence using a bitstream, where all layers in the bitstream have the same number of coded picture buffer (CPB) delivery schedules. DETAILED DESCRIPTION OF THE INVENTION

[0041] While exemplary implementations of one or more embodiments are provided below, it should be understood at the outset that the disclosed systems and / or methods may be implemented using any number of technologies, whether currently known or in existence. The present disclosure should in no way be limited to the exemplary implementations, drawings, and technologies shown below, including the exemplary designs and implementations shown and described herein, but may be modified within the scope of the appended claims, along with their full range of equivalents.

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

[0043] A bitstream is a sequence of bits containing compressed video data for transmission between an encoder and a decoder. An encoder is a device configured to employ an encoding process to compress video data into a bitstream. A decoder is a device configured to employ a decoding process to reconstruct video data from the bitstream for display. A picture is an array of luma samples and / or chroma samples that make up a frame or its fields. The picture being encoded or decoded is sometimes referred to as the current picture for clarity. A network abstraction layer (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, and optionally interspersed emulation prevention bytes. A video coding layer (VCL) NAL unit is a NAL unit coded to contain video data, such as a coded slice of a picture. A non-VCL NAL unit is a NAL unit containing non-video data, such as syntax and / or parameters, that support decoding the video data, performing conformance checks, or other operations. An access unit (AU) is a set of NAL units associated with each other according to specified classification rules and related to one particular output time. A decoding unit (DU) is an AU or a subset of AUs and associated non-VCL NAL units. For example, an AU includes a VCL NAL unit and any non-VCL NAL units associated with the VCL NAL units in the AU. Furthermore, a DU includes a set or subset of VCL NAL units from the AU and any non-VCL NAL units associated with the VCL NAL units in the DU. 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, image size, etc.). Decoding order is the order in which syntax elements are processed by the decoding process.A video parameter set (VPS) is a data unit that contains parameters related to an entire video.

[0044] A temporal scalable bitstream is a bitstream coded in multiple layers that provide various temporal resolutions / frame rates (e.g., each layer is coded to support a different frame rate). A sublayer is a temporally scalable layer of a temporally scalable bitstream that includes VCL NAL units with a specific temporal identifier value and associated non-VCL NAL units. For example, a temporal sublayer is a layer that includes video data associated with a specified frame rate. A sublayer representation is a subset of a bitstream that includes NAL units of a specific sublayer and lower sublayer. Thus, one or more temporal sublayers can be combined to achieve a sublayer representation that can be decoded to result in a video sequence with a specified frame rate. An output layer set (OLS) is a set of layers in which one or more layers are designated as output layers. An output layer is a layer designated for output (e.g., to a display). An OLS index is an index that uniquely identifies the corresponding OLS. The zeroth (0th) OLS is an OLS that includes only the lowest layer (the layer with the lowest layer identifier) ​​and therefore only includes output layers. The temporal identifier (ID) is a data element that indicates that the data corresponds to a temporal position within a video sequence. The sub-bitstream extraction process is a process that removes from the bitstream NAL units that do not belong to a target set determined by a target OLS index and a target highest temporal ID. The sub-bitstream extraction process outputs a sub-bitstream that contains NAL units that are part of the target set from the bitstream.

[0045] An HRD is a decoder model that runs on an encoder and checks the variability of the bitstream generated by the encoding process to verify its conformance with specified constraints. Bitstream conformance tests determine whether the encoded bitstream complies with standards such as Versatile Video Coding (VVC). HRD parameters are syntax elements that initialize and / or define the operating conditions of the HRD. HRD parameters can be included in an HRD parameter syntax structure. A syntax structure is a data object configured to contain multiple different parameters. A syntax element is a data object that contains one or more parameters of the same type. Therefore, a syntax structure can contain multiple syntax elements. Sequence-level HRD parameters are HRD parameters that apply to the entire coded video sequence. The maximum HRD temporal ID (hrd_max_tid[i]) specifies the temporal ID of the highest sublayer representation whose HRD parameters are included in the ith OLS HRD parameter set. The general HRD parameters (general_hrd_parameters) syntax structure contains sequence-level HRD parameters. An operating point (OP) is a temporal subset of an OLS and is identified by an OLS index and a highest temporal ID. The OP to be tested (targetOp) is the OP selected for conformance testing in the HRD. The target OLS is the OLS selected for extraction from the bitstream. The decoding unit HRD parameter present flag (decoding_unit_hrd_params_present_flag) indicates whether the corresponding HRD parameter operates at the DU level or the AU level. The coded picture buffer (CPB) is a first-in-first-out buffer in the HRD that contains coded pictures in decoding order for use during bitstream conformance verification. The decoded picture buffer (DPB) is a buffer for holding decoded pictures for reference, output reordering, and / or output delay.

[0046] A Supplemental Enhancement Information (SEI) message is a semantically specified syntax structure that conveys information not required by the decoding process to determine the values ​​of samples of a decoded image. A scalable nesting SEI message is a message that contains multiple SEI messages corresponding to one or more OLSs or one or more layers. A non-scalable nested SEI message is a non-nested message and therefore contains a single SEI message. A buffering period (BP) SEI message is an SEI message that contains HRD parameters for initializing the HRD to manage the CPB. A picture timing (PT) SEI message is an SEI message that contains HRD parameters for managing the distribution information of AUs in the CPB and / or DPB. A decoding unit information (DUI) SEI message is an SEI message that contains HRD parameters for managing the distribution information for DUs in the CPB and / or DPB.

[0047] The CPB removal delay is the period of time that the corresponding current AU can remain in the CPB before being removed and output to the DPB. The initial CPB removal delay is the default CPB removal delay for each picture, AU, and / or DU in the bitstream, OLS, and / or layer. The CPB removal offset is a location in the CPB used to determine the boundary of the corresponding AU in the CPB. The initial CPB removal offset is the default CPB removal offset associated with each picture, AU, and / or DU in the bitstream, OLS, and / or layer. The decoded picture buffer (DPB) output delay information is the period of time that the corresponding AU can remain in the DPB before being output. The CPB removal delay information is information related to the removal of the corresponding DU from the CPB. The delivery schedule specifies the timing for delivery of video data to and / or from memory locations such as the CPB and / or DPB. The VPS layer ID (vps_layer_id) is a syntax element that indicates the layer ID of the ith layer indicated in the VPS. The number of output layer sets minus 1 (num_output_layer_sets_minus1) is a syntax element that specifies the total number of OLSs specified by the VPS. The HRD coded picture buffer count (hrd_cpb_cnt_minus1) is a syntax element that specifies the number of alternative CPB delivery schedules. The sublayer CPB parameters present flag (sublayer_cpb_params_present_flag) is a syntax element that specifies whether the set of OLS HRD parameters contains HRD parameters for the specified sublayer representation. The schedule index (ScIdx) is an index that identifies a delivery schedule. The BP CPB count minus 1 (bp_cpb_cnt_minus1) is a syntax element that specifies the number of initial CPB removal delay and offset pairs, and therefore the number of delivery schedules available for a temporal sublayer. 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.The fixed picture rate general flag (fixed_pic_rate_general_flag) syntax element is a syntax element that specifies whether to constrain the temporal distance between the HRD output times of consecutive pictures in output order. The sublayer HRD parameters (sublayer_hrd_parameters) syntax structure is a syntax structure that contains the HRD parameters of the corresponding sublayer. The general VCL HRD parameters present flag (general_vcl_hrd_params_present_flag) is a flag that specifies whether VCL HRD parameters are present in the general HRD parameters syntax structure. The BP max sublayers-1 (bp_max_sublayers_minus1) syntax element is a syntax element that specifies the maximum number of temporal sublayers for which the CPB removal delay and CPB removal offset are indicated in the BP SEI message. The VPS max sublayers-1 (vps_max_sublayers_minus1) syntax element is a syntax element that specifies the maximum number of temporal sublayers that can exist in a layer specified by the VPS. The scalable nesting OLS flag is a flag that specifies whether the scalable nested SEI message applies to a specific OLS or to a specific layer. The number of scalable nesting OLSs - 1 (num_olss_minus1) is a syntax element that specifies the number of OLSs to which the scalable nested SEI message applies. The nesting OLS index (NestingOlsIdx) is a syntax element that specifies the OLS index of the OLS to which the scalable nested SEI message applies. The target OLS index (targetOlsIdx) is a variable that identifies the OLS index of the OLS to be decoded. The total number of OLSs - 1 (OLS-1) is a syntax element that specifies the total number of OLSs specified in the VPS.

[0048] The following acronyms are used herein: 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), Picture Order Count (POC), Random Access Point (RAP), Raw Byte Sequence Payload (RBSP), Sequence Parameter Set (SPS), Video Parameter Set (VPS), Generic Video Coding (VVC).

[0049] Many video compression techniques can be employed to minimize data loss and reduce video file sizes. For example, video compression techniques can 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. In block-based video coding, video slices (e.g., video images or portions of video images) may be divided into 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 intra-coded (I) slices of an image are coded using spatial prediction with respect to reference samples of neighboring blocks within the same image. Video blocks in inter-coded unidirectionally predictive (P) or bidirectionally predictive (B) slices of an image may be coded by employing spatial prediction with respect to reference samples of neighboring blocks within the same image or temporal prediction with respect to reference samples of other reference images. An image may be referred to as a frame and / or an image, and a reference image may be referred to as a reference frame and / or a reference image. Spatial or temporal prediction results in a predictive block representing an image block. Residual data represents pixel differences between the original image block and the predictive block. Thus, inter-coded blocks are coded according to a motion vector pointing to a block of reference samples forming the predictive block and residual data indicating the differences between the coded block and the predictive block. Intra-coded blocks are coded 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, resulting in residual transform coefficients that may be quantized. The quantized transform coefficients may first be arranged in a two-dimensional array. The quantized transform coefficients may then be scanned to generate a one-dimensional vector of transform coefficients. Entropy coding may then be applied to achieve even greater compression. Such video compression techniques are described in more detail below.

[0050] 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 Advanced Video Coding (AVC), also known as 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, 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) and 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 included in several Working Drafts (WDs), including JVET-O2001-v14.

[0051] Video coding systems employ various conformance tests to ensure that a bitstream is decodable by a decoder. For example, conformance checks may include testing the entire bitstream for conformance, then testing each layer of the bitstream for conformance, and finally checking potential decodable outputs for conformance. To perform conformance checks, corresponding parameters are included in the bitstream. A hypothetical reference decoder (HRD) can read the parameters and perform the tests. A video may contain many layers and many different output layer sets (OLSs). Upon request, the encoder transmits one or more layers of a selected OLS. For example, the encoder may transmit the best layer from the OLS that can be supported by the current network bandwidth. A first problem with this approach is that a significant number of layers are tested but not actually transmitted to the decoder. However, parameters to support such tests may still be included in the bitstream, unnecessarily increasing the size of the bitstream.

[0052] In a first embodiment, a mechanism for applying a bitstream conformance test to only each OLS is disclosed herein. In this way, when testing the corresponding OLS, the entire bitstream, each layer, and the decodable output are tested together. Therefore, the number of conformance tests is reduced, thereby reducing processor and memory resource usage at the encoder. Furthermore, reducing the number of conformance tests can reduce the number of associated parameters included in the bitstream. This reduces the bitstream size, thus reducing processor, memory, and / or network resource utilization at both the encoder and decoder.

[0053] A second problem is that the signaling process of HRD parameters used for HRD conformance testing in some video coding systems can become complicated in a multi-layer context. For example, a set of HRD parameters may be signaled for each layer of each OLS. Such HRD parameters may be signaled at different locations in the bitstream depending on the intended range of the parameters. As a result, the scheme becomes more complex as more layers and / or OLSs are added. Furthermore, the HRD parameters for different layers and / or OLSs may contain redundant information.

[0054] In a second embodiment, a mechanism for signaling a global set of sequence-level HRD parameters for an OLS and corresponding layers is disclosed herein. For example, all sequence-level HRD parameters that apply to all OLSs and all layers included in the OLS are signaled in a video parameter set (VPS). The VPS is signaled once in the bitstream, and therefore, sequence-level HRD parameters are signaled once. Furthermore, sequence-level HRD parameters may be constrained to be identical across all OLSs. In this way, redundant signaling is reduced, improving coding efficiency. This approach also simplifies the HRD process. As a result, processor, memory, and / or network signaling resource usage is reduced in both the encoder and decoder.

[0055] A third problem can arise when a video coding system performs bitstream conformance checks. Video may be coded into multiple layers and / or sublayers, which can then be organized into an OLS. Each layer and / or sublayer in each OLS is checked for conformance according to a delivery schedule. Each delivery schedule is associated with a different coded picture buffer (CPB) size and CPB delay to account for different transmission bandwidths and system capabilities. Some video coding systems allow each sublayer to define any number of delivery schedules. This can result in a large amount of signaling to support conformance checks, resulting in reduced bitstream coding efficiency.

[0056] In a third example embodiment, a mechanism for improving coding efficiency for videos containing multiple layers is disclosed herein. Specifically, all layers and / or sublayers are constrained to include the same number of CPB delivery schedules. For example, an encoder can determine the maximum number of CPB delivery schedules to be used for any one layer and set the number of CPB delivery schedules for all layers to this maximum number. The number of delivery schedules may then be signaled once, for example, as part of the HRD parameters in the VPS. This eliminates the need to signal several schedules per layer / sublayer. In some examples, all layers / sublayers in the OLS may also share the same delivery schedule index. These changes reduce the amount of data used to signal data related to conformance checking. This reduces the bitstream size and, therefore, reduces processor, memory, and / or network resource utilization in both the encoder and decoder.

[0057] A fourth problem may arise when video is coded into multiple layers and / or sublayers, which are then organized into an OLS. The OLS may include a zeroth (0th) OLS containing only the output layer. Supplemental Enhancement Information (SEI) messages may be included in the bitstream to inform the HRD of layer / OLS-specific parameters used to test the multiple layers of the bitstream for conformance to the standard. Specifically, when an OLS is included in the bitstream, a scalable nesting SEI message is employed. The scalable nesting SEI message contains one or more OLSs and / or a group of nested SEI messages that apply to one or more layers of the OLS. Each nested SEI message may contain an indicator to indicate its association with the corresponding OLS and / or layer. Nested SEI messages are configured for use with multiple layers and may contain irrelevant information when applied to a zeroth OLS containing a single layer.

[0058] In a fourth embodiment, a mechanism for improving coding efficiency for video including a zeroth OLS is disclosed herein. A non-scalable nested SEI message is employed for the zeroth OLS. The non-scalable nested SEI message is constrained to apply only to the zeroth OLS and, therefore, only to the output layers included in the zeroth OLS. In this way, irrelevant information such as nesting relationships, layer indications, etc. can be omitted from the SEI message. The non-scalable nested SEI message may be used as a buffering period (BP) SEI message, a picture timing (PT) SEI message, a decoding unit (DU) SEI message, or a combination thereof. These modifications reduce the amount of data used to signal conformance check-related information for the zeroth OLS. This reduces the bitstream size and, therefore, reduces processor, memory, and / or network resource utilization in both the encoder and decoder.

[0059] A fifth problem may arise when video is separated into multiple layers and / or sublayers. An encoder may encode these layers into a bitstream. Furthermore, the encoder may use an HRD that performs conformance tests to check the bitstream for conformance with the standard. To support such conformance tests, the encoder may be configured to include layer-specific HRD parameters in the bitstream. Layer-specific HRD parameters may be coded for each layer in some video coding systems. In some cases, the layer-specific HRD parameters are the same for each layer, resulting in redundant information that unnecessarily increases the size of the video encoding.

[0060] In a fifth embodiment, a mechanism for reducing HRD parameter redundancy for video employing multiple layers is disclosed herein. An encoder may encode the HRD parameters of the highest layer. The encoder may also encode a sublayer CPB parameter present flag (sublayer_cpb_params_present_flag). Setting sublayer_cpb_params_present_flag to 0 may indicate that all lower layers should use the same HRD parameters as the highest layer. In this context, the highest layer has the highest layer identifier (ID), and a lower layer is any layer with a layer ID lower than the layer ID of the highest layer. In this manner, the HRD parameters of lower layers may be omitted from the bitstream. This reduces the bitstream size and, therefore, reduces processor, memory, and / or network resource utilization in both the encoder and decoder.

[0061] The sixth issue concerns the use of sequence parameter sets (SPSs), which contain syntax elements related to each video sequence in a video. Video coding systems can code video in layers and / or sublayers. A video sequence may operate differently in different layers and / or sublayers. Therefore, different layers may reference different SPSs. A BP SEI message can indicate the layer / sublayer for which conformance to the standard is being checked. Some video coding systems may indicate that the BP SEI message applies to the layer / sublayer indicated in the SPS. This can cause problems if different layers reference different SPSs, as these SPSs may contain conflicting information, resulting in unexpected errors.

[0062] In a sixth embodiment, a mechanism for addressing errors related to conformance checks when multiple layers are employed in a video sequence is disclosed herein. Specifically, the BP SEI message is modified to indicate that conformance can be checked for any number of layers / sublayers described in the VPS. For example, the BP SEI message can include a BP max sublayers-1 (bp_max_sublayers_minus1) syntax element, which indicates the number of layers / sublayers associated with the data in the BP SEI message. Meanwhile, the VPS max sublayers-1 (vps_max_sublayers_minus1) syntax element in the VPS indicates the number of sublayers in the entire video. The bp_max_sublayers_minus1 syntax element can be set to any value between 0 and the value of the vps_max_sublayers_minus1 syntax element. In this way, conformance can be checked for any number of layers / sublayers in a video while avoiding layer-based sequencing issues related to SPS inconsistency. Therefore, the present disclosure avoids layer-based coding errors and thus improves the functionality of the encoder and / or decoder. Furthermore, the present disclosure supports layer-based coding, which can improve coding efficiency. Therefore, the present disclosure supports reducing processor, memory, and / or network resource usage in the encoder and / or decoder.

[0063] The seventh issue concerns the layers included in an OLS. Each OLS includes at least one output layer configured to be displayed by a decoder. The HRD of the encoder can check each OLS for conformance with the standard. A conforming OLS can always be decoded and displayed by a conforming decoder. The HRD process may be partially managed by SEI messages. For example, a scalable nesting SEI message may include scalable nested SEI messages. Each scalable nested SEI message may include data related to the corresponding layer. When performing a conformance check, the HRD can perform a bitstream extraction process on the target OLS. Data not related to a layer in the OLS is generally removed before conformance testing (e.g., before transmission) so that each OLS can be checked separately. Some video coding systems do not remove scalable nesting SEI messages during the sub-bitstream extraction process because such messages pertain to multiple layers. For this reason, scalable nesting SEI messages may remain in the bitstream after sub-bitstream extraction even if they are not related to any layer of the target OLS (the OLS being extracted), which may increase the size of the final bitstream without providing any additional functionality.

[0064] In a seventh embodiment, a mechanism for reducing the size of a multi-layer bitstream is disclosed herein. During sub-bitstream extraction, scalable nesting SEI messages may be considered for removal from the bitstream. If the scalable nesting SEI message is associated with one or more OLSs, the scalable nested SEI messages in the scalable nesting SEI message are checked. If the scalable nesting SEI message is not associated with any layer of the target OLS, the entire scalable nesting SEI message may be removed from the bitstream. This results in a smaller size of the bitstream sent to the decoder. This embodiment therefore improves coding efficiency and reduces processor, memory, and / or network resource usage in both the encoder and decoder.

[0065] 1 is a flowchart of an exemplary operational method 100 for coding a video signal. Specifically, a video signal is encoded by an encoder. The encoding process compresses the video signal by employing various mechanisms to reduce the video file size. The reduced file size allows the compressed video file to be transmitted to a user while reducing the associated bandwidth overhead. A decoder decodes the compressed video file to reconstruct the original video signal for display to an end user. The decoding process generally mirrors the encoding process so that the decoder can coherently reconstruct the video signal.

[0066] In 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 an audio component and a video component. The video component includes a series of image frames, which, when viewed sequentially, create the visual impression of motion. The frames include pixels 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 views.

[0067] In step 103, the video is divided into blocks. The division involves subdividing pixels within 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 can first be divided into coding tree units (CTUs), which are blocks of a predefined size (e.g., 64 pixels by 64 pixels). CTUs contain both luma and chroma samples. A coding tree can be employed to divide the CTUs into blocks, and then the blocks can be recursively subdivided 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 uniform lighting values. Furthermore, the chroma component of a frame may be subdivided until each block contains relatively uniform color values. Thus, the division mechanism varies depending on the content of the video frame.

[0068] In step 105, various compression mechanisms are employed to compress the image blocks partitioned in step 103. For example, inter-prediction and / or intra-prediction can be employed. Inter-prediction is designed to take advantage of the fact that objects tend to appear in consecutive frames within a common scene. Therefore, blocks representing an object in a reference frame need not be repeatedly described in adjacent frames. Specifically, an object such as a table may remain in a constant position across multiple frames. Therefore, the table may be described once, and adjacent frames may reference the reference frame. A pattern matching mechanism can be used to match objects across multiple frames. Furthermore, moving objects may be represented across multiple frames, for example, due to object movement or camera movement. As a specific example, a video may show a car moving across the screen over multiple frames. Such movement can be described using motion vectors. 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. Thus, inter-prediction can encode an image block in a current frame as a set of motion vectors indicating its offset from a corresponding block in a reference frame.

[0069] Intra prediction encodes blocks within a common frame. Intra prediction takes advantage of the fact that luma and chroma components tend to cluster within a frame. For example, some green patches in a tree tend to be located adjacent to similar green patches. Intra prediction employs multiple directional prediction modes (e.g., 33 in HEVC), planar mode, and direct current (DC) mode. The directional mode indicates that the current block is similar / identical to samples in neighboring blocks in the corresponding direction. The planar mode indicates that a series of blocks along a row / column (e.g., a plane) can be interpolated based on neighboring blocks at the edge of the row. The planar mode effectively indicates a smooth transition of light / color across the row / column by using a relatively constant slope in changing values. The DC mode is employed for boundary smoothing and indicates that the block is similar / identical to the average value associated with samples in all neighboring blocks associated with the angular direction of the directional prediction mode. Therefore, intra prediction blocks can represent image blocks as various relational prediction mode values ​​rather than their actual values. Additionally, inter-predicted blocks can represent image blocks as motion vector values ​​rather than actual values. In either case, the predicted blocks may not accurately represent the image blocks in some cases. Any differences are stored in residual blocks. Transforms can be applied to the residual blocks to further compress the file.

[0070] Various filtering techniques can be applied in step 107. In HEVC, filters are applied according to an in-loop filtering scheme. The block-based prediction described above may produce a blocky image at the decoder. Furthermore, after encoding a block, the block-based prediction scheme may 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, thereby enabling accurate reconstruction of the encoded file. Furthermore, these filters reduce artifacts in the reconstructed reference block, thereby reducing the likelihood that the artifacts will create additional artifacts in subsequent blocks that are coded based on the reconstructed reference block.

[0071] Once the video signal has been segmented, compressed, and filtered, the resulting data is encoded into a bitstream in 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 segmentation data, prediction data, residual blocks, and various flags that provide coding instructions to the decoder. The bitstream may be stored in memory for transmission to a 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 occur sequentially and / or simultaneously across many frames and blocks. The order shown in FIG. 1 is presented for clarity and ease of discussion and is not intended to limit the video coding process to any particular order.

[0072] The decoder receives the bitstream and begins the decoding process in step 111. Specifically, the decoder employs an entropy decoding scheme to convert the bitstream into corresponding syntax and video data. In step 111, the decoder uses syntax data from the bitstream to determine the frame partitioning. This partitioning should match the result of the block partitioning in step 103. Next, we will explain the entropy encoding / decoding employed in step 111. The encoder makes many choices during the compression process, such as selecting a block partitioning scheme from several possible options based on the spatial arrangement of values ​​in the input image. Signaling the exact selection may use a number of bins. 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 allowable options. Each allowable 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 the codeword for the selected option. This scheme reduces the size of the codeword because the codeword is desired to uniquely indicate a selection from a small subset of allowable options, rather than uniquely indicating a selection from a potentially large set of all possible options. The decoder then decodes this selection by determining the set of allowable options, 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.

[0073] In step 113, the decoder performs block decoding. Specifically, the decoder generates a residual block using an inverse transform. Then, the decoder uses the residual block and the corresponding prediction block to reconstruct an image block according to the partition. The prediction block may include both intra-predicted blocks and inter-predicted blocks generated by the encoder in step 105. Then, the reconstructed image block is placed in a frame of the reconstructed video signal according to the partition data determined in step 111. The syntax of step 113 may also be signaled in the bitstream via entropy coding, as described above.

[0074] In step 115, filtering is performed on the frames of the reconstructed video signal in a manner similar to step 107 in 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. Once the frames have been filtered, the video signal may be output to a display for viewing by an end user in step 117.

[0075] FIG. 2 is a schematic diagram of an exemplary coding-decoding (codec) system 200 for video coding. Specifically, codec system 200 provides functionality supporting implementation of operational method 100. Codec system 200 is generalized to show components used in both encoders and decoders. Codec system 200 receives and segments a video signal, as described with respect to steps 101 and 103 of operational method 100, resulting in segmented video signal 201. When operating as an encoder, codec system 200 then compresses segmented video signal 201 into a coded bitstream, as described with respect to steps 105, 107, and 109 of method 100. When operating as a decoder, codec system 200 generates an output video signal from the bitstream, as described with respect to steps 111, 113, 115, and 117 of 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. These components are coupled as shown. In Figure 2, black lines indicate the movement of data to be coded / decoded, and dashed lines indicate the movement of control data that controls the operation of other components. All of the components of codec system 200 may reside within an encoder. A decoder may include a subset of the components of codec system 200.For example, the decoder may include an intra-image prediction component 217, a motion compensation component 219, a scaling and inverse transform component 229, an in-loop filter component 225, and a decoded image buffer component 223. These components will now be described.

[0076] The segmented video signal 201 is a captured video sequence that has been segmented into blocks of pixels by a coding tree. The coding tree subdivides the blocks of pixels into smaller blocks of pixels using various segmentation modes. These blocks can then be further subdivided into smaller blocks. Blocks are sometimes referred to as nodes on the coding tree. Larger parent nodes are segmented into smaller child nodes. The number of times a node is segmented is referred to as the depth of the node / coding tree. The segmented blocks may be included in coding units (CUs). For example, a CU may be a subpart 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 segmentation modes may include a binary tree (BT), a ternary tree (TT), and a quad tree (QT), which are employed to segment a node into two, three, or four child nodes of various shapes, respectively, depending on the segmentation mode used. The segmented video signal 201 is forwarded to a general coder control component 211, a transform scaling and quantization component 213, an intra-image estimation component 215, a filter control analysis component 227, and a motion estimation component 221 for compression.

[0077] The general coder control component 211 is configured to make decisions related to coding 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 can be made based on storage space / bandwidth availability and image resolution requests. The general coder control component 211 also manages buffer utilization, taking transmission speed into account, to mitigate buffer underrun and overrun 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 can dynamically increase compression complexity to improve resolution and increase bandwidth usage, or decrease compression complexity to reduce resolution and bandwidth usage. Thus, the general coder control component 211 controls other components of the codec system 200 to balance the relationship between video signal reconstruction quality and bitrate. The general coder control component 211 generates control data that controls the operation of other components. 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.

[0078] The segmented 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 segmented video signal 201 may be divided into multiple video blocks. The motion estimation component 221 and the motion compensation component 219 perform relative inter-predictive coding of the received video blocks with respect to one or more blocks in one or more reference frames to provide temporal prediction. The codec system 200 may perform multiple coding passes, for example, to select an appropriate coding mode for each block of video data.

[0079] The motion estimation component 221 and the motion compensation component 219 may be highly integrated but are shown separately for conceptual purposes. Motion estimation, performed by the motion estimation component 221, is the process of generating motion vectors that estimate the motion of video blocks. A motion vector may indicate, for example, the relative displacement of a coded object relative to a predictive block. A predictive block is a block that is found to closely match a block to be coded in terms of pixel differences. A predictive block is sometimes 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, and the CTBs may then be divided into CBs for inclusion in CUs. A CU may be coded as a prediction unit (PU) containing predictive data and / or a transform unit (TU) containing residual data transformed for the CU. The motion estimation component 221 generates motion vectors, PUs, and TUs by using rate-distortion analysis as part of a rate-distortion optimization process. For example, the motion estimation component 221 can 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 loss due to compression) and the coding efficiency (e.g., the size of the final encoding).

[0080] In some examples, the codec system 200 can calculate values ​​for sub-integer pixel positions of the reference image stored in the decoded image buffer component 223. For example, the video codec system 200 can interpolate values ​​for quarter-pixel positions, eighth-pixel positions, or other fractional pixel positions of the reference image. Therefore, the motion estimation component 221 can perform relative motion search between full-pixel positions and fractional pixel positions and output motion vectors with fractional pixel accuracy. The motion estimation component 221 calculates the motion vector of the PU of the reference image for a video block in an inter-coded slice by comparing the position of the PU with the position of the predictive block. The motion estimation component 221 outputs the calculated motion vector as motion data to the header formatting and CABAC component 231 for encoding and outputs the motion to the motion compensation component 219.

[0081] The motion compensation performed by the motion compensation component 219 may include fetching or generating a predictive block based on the 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 the 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. Generally, the motion estimation component 221 performs motion estimation on 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.

[0082] The split video signal 201 is also sent to an intra-image estimation component 215 and an intra-image prediction component 217. Like the motion estimation component 221 and motion compensation component 219, the intra-image estimation component 215 and the intra-image prediction component 217 may be highly integrated but are shown separately for conceptual purposes. The intra-image estimation component 215 and the intra-image prediction component 217 intra-predict the current block relative to blocks within the 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-image estimation component 215 determines the intra-prediction mode to use to encode the current block. In some examples, the intra-image estimation component 215 selects an appropriate intra-prediction mode to encode the current block from multiple tested intra-prediction modes. The selected intra-prediction mode is then forwarded to the header formatting and CABAC component 231 for encoding.

[0083] For example, the intra-image estimation component 215 may calculate rate-distortion values ​​for various tested intra-prediction modes using a rate-distortion analysis and select the intra-prediction mode with the best rate-distortion characteristics among the tested modes. The rate-distortion analysis generally determines the amount of distortion (or error) between the coded block and the original uncoded block coded to generate the coded block, as well as the bit rate (e.g., number of bits) used to generate the coded block. The intra-image estimation component 215 may calculate a ratio from the distortion and rate of the various coded blocks and determine which intra-prediction mode exhibits the best rate-distortion value for the block. In addition, the intra-image estimation component 215 may be configured to code depth blocks of the depth map using a rate-distortion optimization (RDO)-based depth modeling mode (DMM).

[0084] The intra-image prediction component 217, when implemented on an encoder, can generate a residual block from the predicted block based on the selected intra-prediction mode determined by the intra-image estimation component 215, or, when implemented on a decoder, can read the residual block from the bitstream. The residual block contains the value difference between the predicted block and the original block and is represented as a matrix. The residual block is then forwarded to the transform scaling and quantization component 213. The intra-image estimation component 215 and the intra-image prediction component 217 can operate on both the luma and chroma components.

[0085] 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 containing residual transform coefficient values. A wavelet transform, an integer transform, a subband transform, or other types of transforms may 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 may involve applying a scale factor to the residual information such that different frequency information is quantized with different granularities, 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 modified by adjusting a quantization parameter. In some examples, the transform scaling and quantization component 213 can then perform a scan of a matrix containing the quantized transform coefficients, which are forwarded to the header formatting and CABAC component 231 for encoding into a bitstream.

[0086] 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, transform, and / or quantization to reconstruct a residual block in the pixel domain for later use as a reference block, which may become a predictive block for another current block, for example. The motion estimation component 221 and / or motion compensation component 219 can calculate a reference block by adding the residual block to the corresponding predictive block for use in motion estimation for a later block / frame. A filter is applied to the reconstructed reference block to mitigate artifacts generated during scaling, quantization, and transform. Such artifacts may otherwise cause inaccurate predictions (and generate additional artifacts) when predicting subsequent blocks.

[0087] The filter control analysis component 227 and the in-loop filter component 225 apply filters to residual blocks and / or reconstructed image blocks. For example, a transformed residual block from the scaling and inverse transform component 229 can be combined with a corresponding prediction block from the intra-image prediction component 217 and / or the motion compensation component 219 to reconstruct the original image block. A filter can then be applied to the reconstructed image block. In some examples, a filter can be applied to the residual block instead. Like the other components in FIG. 2, the filter control analysis component 227 and the in-loop filter component 225 may be highly integrated and implemented together, but are shown separately for conceptual purposes. The filters applied to the reconstructed reference block are applied to specific spatial regions and include multiple parameters for adjusting 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 set 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., to reconstructed pixel blocks) or in the frequency domain, depending on the implementation.

[0088] When operating as an encoder, the filtered reconstructed image blocks, residual blocks, and / or prediction 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 prediction blocks, residual blocks, and / or reconstructed image blocks.

[0089] 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 to a decoder. Specifically, the header formatting and CABAC component 231 generates various headers for encoding control data, such as general control data and filter control data. Additionally, prediction data, including intra-prediction and motion data, and residual data in the form of quantized transform coefficient data are all encoded into the bitstream. The final bitstream contains all information required by a decoder to reconstruct the original segmented video signal 201. Such information may include an intra-prediction mode index table (also called a codeword mapping table), definitions of coding contexts for various blocks, indications of the most probable intra-prediction mode, indications of segmentation information, etc. Such data may be encoded using 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 retrieval.

[0090] 3 is a block diagram illustrating an exemplary video encoder 300. Video encoder 300 can be employed to perform the encoding functions of codec system 200 and / or to perform steps 101, 103, 105, 107, and / or 109 of method of operation 100. Encoder 300 splits an input video signal, resulting in a split video signal 301 that is substantially similar to split video signal 201. Split video signal 301 is then compressed and encoded into a bitstream by components of encoder 300.

[0091] Specifically, the segmented video signal 301 is forwarded to an intra-image prediction component 317 for intra prediction. The intra-image prediction component 317 may be substantially similar to the intra-image estimation component 215 and the intra-image prediction component 217. The segmented video signal 301 is also forwarded to a motion compensation component 321 for inter prediction based on a reference block in a decoded image 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 residual block from the intra-image 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 block and the corresponding prediction block (along with associated control data) are forwarded to an entropy coding component 331 for coding into a bitstream. The entropy coding component 331 may be substantially similar to the header formatting and CABAC component 231 .

[0092] The transformed and quantized residual block and / or the corresponding prediction block are also transferred from the transform and quantization component 313 to the inverse transform and quantization component 329 for reconstructing into a reference block 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. Depending on the embodiment, an in-loop filter of the in-loop filter component 325 is also applied to the residual block and / or the reconstructed reference block. 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 include multiple filters such as those 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.

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

[0094] 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 can employ header information to provide context for interpreting additional data encoded as codewords in the bitstream. The decoded information includes any desired information for decoding the video signal, such as general control data, filter control data, segmentation 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 can be similar to the inverse transform and quantization component 329.

[0095] The reconstructed residual block and / or predictive block are forwarded to the intra image prediction component 417 for reconstructing into an image block based on an intra prediction operation. The intra image prediction component 417 may be similar to the intra image estimation component 215 and the intra image prediction component 217. Specifically, the intra image prediction component 417 uses the prediction mode to locate a reference block within a frame and applies the residual block to the result to reconstruct an intra predicted image block. The reconstructed intra predicted image block and / or residual block and corresponding inter prediction data are forwarded to the decoded image buffer component 423 via the in-loop filter component 425, which may be substantially similar to the decoded image buffer component 223 and the in-loop filter component 225, respectively. The in-loop filter component 425 filters the reconstructed image block, residual block, and / or predictive block, and such information is stored in the decoded image buffer component 423. The reconstructed image block from the decoded image 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 generates a prediction block using a motion vector from a reference block and applies a residual block to the result to reconstruct an image block. The resulting reconstructed block may also be transferred 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 that can be reconstructed into frames via the segmentation information. Such frames may also be arranged in a sequence. The sequence is output to a display as a reconstructed output video signal.

[0096] 5 is a schematic diagram illustrating an exemplary HRD 500. The HRD 500 can be employed in the codec system 200 and / or an encoder, such as the encoder 300. The HRD 500 can 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 does not conform to an associated constraint, the HRD 500 can indicate such failure to the encoder, causing the encoder to re-encode the corresponding section of the bitstream with a different mechanism.

[0097] The HRD 500 includes a virtual stream scheduler (HSS) 541. The HSS 541 is a component configured to implement a virtual distribution mechanism. The virtual distribution mechanism is used to check the conformance of a bitstream or decoder with respect to the timing and data flow of a 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 testing process for the bitstream 551. In a particular example, the HSS 541 may control the rate at which coded images move through the HRD 500 and verify that the bitstream 551 does not contain non-conforming data.

[0098] The HSS 541 can transfer the bitstream 551 to the CPB 543 at a predetermined rate. The HRD 500 can manage data in a decoding unit (DU) 553. A DU 553 is an 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 images associated with an output time. For example, an AU can include a single image in a single-layer bitstream or an image for each layer in a multi-layer bitstream. Each image in an AU can be divided into slices, each of which is included in a corresponding VCL NAL unit. Thus, a DU 553 can include one or more images, one or more slices of an image, or a combination thereof. Additionally, parameters used to decode an AU, image, and / or slice can be included in the non-VCL NAL units. Thus, a DU 553 includes non-VCL NAL units that contain data necessary to support the decoding of the VCL NAL units in the DU 553. The CPB 543 is a first-in, first-out buffer in the HRD 500. CPB 543 contains DUs 553 containing video data in decoding order. CPB 543 stores video data for use during bitstream conformance verification.

[0099] The CPB 543 forwards the DU 553 to a decoding process component 545. The decoding process component 545 is a VVC standard-compliant component. For example, the decoding process component 545 may emulate the decoder 400 used by an end user. The decoding process component 545 decodes the DU 553 at a rate achievable by an exemplary end-user decoder. If the decoding process component 545 cannot decode the DU 553 fast enough to prevent the CPB 543 from overflowing, the bitstream 551 is non-compliant and needs to be re-encoded.

[0100] The decoding process component 545 decodes the DU 553 to generate a decoded DU 555. The decoded DU 555 includes a decoded image. The decoded DU 555 is forwarded to the DPB 547. The DPB 547 may be substantially similar to the decoded image buffer components 223, 323, and / or 423. To support inter-prediction, images marked for use as reference images 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 images 557. The images 557 are reconstructed images that generally mirror the images encoded by the encoder into the bitstream 551.

[0101] Image 557 is forwarded to output cropping component 549, which is configured to apply an adaptive cropping window to image 557. This results in cropped output image 559. Cropped output image 559 is a perfectly reconstructed image. Thus, cropped output image 559 mimics what an end user would see when decoding bitstream 551. In this way, the encoder can review cropped output image 559 to ensure that the encoding is satisfactory.

[0102] The HRD 500 is initialized based on HRD parameters in the bitstream 551. For example, the HRD 500 can read the HRD parameters from a VPS, SPS, and / or SEI message. The HRD 500 can then perform conformance testing operations on the bitstream 551 based on the information in such HRD parameters. As a specific example, the HRD 500 can determine one or more CPB delivery schedules 561 from the HRD parameters. The delivery schedules specify the timing for delivery of video data to and / or from memory locations, such as the CPB and / or DPB. Thus, the CPB delivery schedules 561 specify the delivery timing of AUs, DUs 553, and / or pictures to / from the CPB 543. For example, the CPB delivery schedules 561 can describe the bitrate and buffer size of the CPB 543, where such bitrate and buffer size correspond to a particular class of decoder and / or network conditions. Thus, the CPB delivery schedules 561 can indicate how long data can remain in the CPB 543 before evacuation. The inability of the HRD 500 to maintain the CPB delivery schedule 561 during conformance testing indicates that a decoder compatible with the CPB delivery schedule 561 cannot decode the corresponding bitstream. Note that the HRD 500 can use a DPB delivery schedule similar to the CPB delivery schedule 561 for the DPB 547.

[0103] Video may be coded into different layers and / or OLSs for use by decoders with varying levels of hardware capabilities and for varying network conditions. The CPB delivery schedule 561 is selected to reflect these challenges. Accordingly, the upper layer sub-bitstreams are designated for optimal hardware and network conditions, and therefore the upper layers may receive one or more CPB delivery schedules 561 that use large amounts of memory in the CPB 543 and short delays for the transfer of DUs 553 towards the DPB 547. Similarly, the lower layer sub-bitstreams are designated for limited decoder hardware capabilities and / or poor network conditions. Thus, the lower layers may receive one or more CPB delivery schedules 561 that use small amounts of memory in the CPB 543 and longer delays for the transfer of DUs 553 towards the DPB 547. The OLSs, layers, sub-layers, or combinations thereof may then be tested according to the corresponding delivery schedules 561 to ensure that the resulting sub-bitstreams can be correctly decoded under the conditions expected for the sub-bitstreams. Each CPB delivery schedule 561 is associated with a schedule index (ScIdx) 563. ScIdx 563 is an index that identifies the delivery schedule. Thus, the HRD parameters in bitstream 551 can not only indicate a CPB delivery schedule 561 by ScIdx 563, but can also include sufficient data to enable HRD 500 to determine the CPB delivery schedule 561 and correlate the CPB delivery schedule 561 to a corresponding OLS, layer, and / or sublayer.

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

[0105] 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 of 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 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 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.

[0106] In the illustrated example, layer N+1 632 is associated with a larger image size than layer N 631. Thus, in this example, images 611, 612, 613, and 614 of layer N+1 632 have a larger image size (e.g., larger height and width, and therefore more samples) than images 615, 616, 617, and 618 of layer N 631. However, such images can 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 shown, a set of images can be separated into any number of layers based on associated characteristics. Layer N+1 632 and layer N 631 are sometimes represented by a layer ID. A layer ID is an item of data associated with an image that indicates that the image is part of a specified layer. Thus, each picture 611-618 may be associated with a corresponding layer ID to indicate 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 the identifier of the layer that contains the NAL unit (e.g., contains slices and / or parameters of the picture within the layer). Layers associated with lower quality / bitstream sizes, such as layer N 631, are generally assigned lower layer IDs and are referred to as lower layers. Furthermore, layers associated with higher quality / bitstream sizes, such as layer N+1 632, are generally assigned higher layer IDs and are referred to as upper layers.

[0107] The images 611-618 of different layers 631-632 are configured to be alternatively displayed. Thus, images of different layers 631-632 can share a temporal ID 622 as long as these images are included in the same AU. The temporal ID 622 is a data element indicating that data corresponds to a temporal position in a video sequence. An AU is a set of NAL units associated with each other according to a specified classification rule and related to one particular output time. For example, an AU can include one or more images in different layers, such as image 611 and image 615, if such images are associated with the same temporal ID 622. As a specific example, a decoder can decode and display image 615 at the current display time if a smaller image is desired, or the decoder can decode and display image 611 at the current display time if a larger image is desired. Thus, images 611-614 of upper layer N+1 632 contain substantially the same image data as corresponding images 615-618 of lower layer N 631 (despite the difference in image size). Specifically, image 611 contains substantially the same image data as image 615, image 612 contains substantially the same image data as image 616, and so on.

[0108] Images 611-618 can be coded by referencing other images 611-618 in the same layer N 631 or N+1 632. Coding an image by referencing another image in the same layer results in inter-prediction 623. Inter-prediction 623 is depicted by a solid arrow. For example, image 613 may be coded by employing inter-prediction 623 using one or two of images 611, 612, and / or 614 in layer N+1 632 as references, where one image is referenced for unidirectional inter-prediction and / or two images are referenced for bidirectional inter-prediction. Furthermore, image 617 may be coded by employing inter-prediction 623 using one or two of images 615, 616, and / or 618 in layer N 531 as references, where one image is referenced for unidirectional inter-prediction and / or two images are referenced for bidirectional inter-prediction. When performing inter prediction 623, a picture may be referred to as a reference picture when it is used as a reference for another picture in the same layer. 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. Thus, 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, where the reference picture and the current picture are in the same layer.

[0109] Pictures 611-618 can also be coded by referencing other pictures 611-618 in different layers. This process is known as inter-layer prediction 621 and is depicted by the dashed arrows. Inter-layer prediction 621 is a mechanism for coding samples of a current picture by referencing indicated samples in a reference picture, where the current picture and the reference picture are in different layers and therefore have different layer IDs. For example, a picture in lower layer N 631 can be used as a reference picture for coding a corresponding picture in upper layer N+1 632. As a specific example, picture 611 can be coded by referencing picture 615 according to inter-layer prediction 621. In such a case, picture 615 is used as the 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 so that a current picture, such as picture 611, can only use inter-layer reference pictures in lower layers, such as picture 615, that are contained in the same AU. If multiple layers (e.g., three or more) are available, inter-layer prediction 621 can encode / decode the current image based on multiple inter-layer reference images at a lower level than the current image.

[0110] Using the multi-layer video sequence 600, a video encoder can encode images 611-618 through many different combinations and / or permutations of inter-prediction 623 and inter-layer prediction 621. For example, image 615 may be coded according to intra-prediction. Images 616-618 can then be coded according to inter-prediction 623 by using image 615 as a reference image. Furthermore, image 611 may be coded according to inter-layer prediction 621 by using image 615 as an inter-layer reference image. Images 612-614 can then be coded according to inter-prediction 623 by using image 611 as a reference image. Thus, reference images can serve as both single-layer and inter-layer reference images for different coding mechanisms. By coding images of the upper layer N+1 632 based on images of the lower layer N 631, 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. Therefore, the low coding efficiency of intra prediction can be limited to images of the smallest / lowest quality, and therefore limited to coding a minimum amount of video data. Images used as reference images and / or inter-layer reference images can be indicated in reference image list entries included in a reference image list structure.

[0111] To perform such operations, layers such as layer N 631 and layer N+1 632 may be included in one or more of OLSs 625 and 626. Specifically, images 611-618 are coded as layers 631-632 of the bitstream 600, and then each layer 631-632 of the image is assigned to one or more of the OLSs 625 and 626. The OLSs 625 and / or 626 may then be selected, and the corresponding layers 631 and / or 632 may be transmitted to the decoder depending on the capabilities and / or network conditions at the decoder. The OLS 625 is a set of layers, one or more of which are designated as output layers. An output layer is a layer designated for output (e.g., to a display). For example, layer N 631 may be included only to support inter-layer prediction 621 and never be output. In such a case, layer N+1 632 is decoded and output based on layer N 631. In such a case, the OLS 625 includes layer N+1 632 as the output layer. When an OLS includes only output layers, that OLS is referred to as the 0th OLS 626. The 0th OLS 626 is an OLS that includes only the lowest layer (the layer with the lowest layer identifier) ​​and is therefore an OLS that includes only output layers. In other cases, the OLS 625 may include many layers in different combinations. For example, the output layer of the OLS 625 may be coded according to inter-layer prediction 621 based on one, two, or many lower layers. Furthermore, the OLS 625 may include more than one output layer. Thus, the OLS 625 may include one or more output layers and any support layers necessary to reconstruct the output layer. Although only two OLSs 625 and 626 are shown, the multi-layer video sequence 600 may be coded by employing many different OLSs 625 and / or 626, each employing a different combination of layers. Each OLS 625 and 626 is associated with an OLS index 629, which is an index that uniquely identifies the corresponding OLS 625 and 626.

[0112] Checking the conformance of a multi-layer video sequence 600 with the HRD 500 can be complex depending on the number of layers 631-632 and OLSs 625 and 626. The HRD 500 can separate the multi-layer video sequence 600 into a series of operation points 627 for testing. The OLSs 625 and / or 626 are identified by an OLS index 629. An operation point 627 is a temporal subset of an OLS 625 / 626. An operation point 627 can be identified by both the OLS index 629 and the highest time ID 622 of the corresponding OLS 625 / 626. As a specific example, a first operation point 627 can include all images in the first OLS 625 from time ID 0 to time ID 200, a second operation point 627 can include all images in the first OLS 625 from time ID 201 to time ID 400, and so on. In such a case, the first operating point 627 is described by the OLS index 629 of the first OLS 625 and a time ID of 200. Further, the second operating point 627 is described by the OLS index 629 of the first OLS 625 and a time ID of 400. The operating point 627 selected for testing at a specified instant is called the test target OP (targetOp). Thus, targetOp is the operating point 627 selected for conformance testing in the HRD 500.

[0113] 7 is a schematic diagram illustrating an example multi-layer video sequence 700 configured for temporal scalability. The multi-layer video sequence 700 may be encoded by an encoder, such as codec system 200 and / or encoder 300, and decoded by a decoder, such as codec system 200 and / or decoder 400, according to, for example, method 100. Additionally, the multi-layer video sequence 700 may be checked for conformance by an HRD, such as HRD 500. The multi-layer video sequence 700 is included to illustrate another example application for layers in a coded video sequence. For example, the multi-layer video sequence 700 may be employed as a separate embodiment or combined with the techniques described with respect to the multi-layer video sequence 600.

[0114] The multi-layer video sequence 700 includes sublayers 710, 720, and 730. A sublayer is a temporal scalable layer of a temporal scalable bitstream that includes VCL NAL units (e.g., pictures) with specific temporal identifier values ​​and associated non-VCL NAL units (e.g., supporting parameters). For example, a layer such as layer N 631 and / or layer N+1 632 may be further divided into sublayers 710, 720, and 730 to support temporal scalability. Sublayer 710 may be referred to as a base layer, and sublayers 720 and 730 may be referred to as enhancement layers. As shown, sublayer 710 includes a picture 711 at a first frame rate, such as 30 frames per second. Because sublayer 710 includes the base / lowest frame rate, sublayer 710 is a base layer. Sublayer 720 includes a picture 721 that is temporally offset from picture 711 of sublayer 710. As a result, sublayer 710 and sublayer 720 can be combined, resulting in an overall frame rate that is higher than the frame rate of sublayer 710 alone. For example, sublayers 710 and 720 can have a combined frame rate of 60 frames per second. Thus, sublayer 720 enhances the frame rate of sublayer 710. Furthermore, sublayer 730 includes image 731 that is also temporally offset from images 721 and 711 of sublayers 720 and 710. Thus, sublayer 730 can be combined with sublayers 720 and 710 to further enhance sublayer 710. For example, sublayers 710, 720, and 730 can have a combined frame rate of 90 frames per second.

[0115] Sublayer representation 740 can be dynamically created by combining sublayers 710, 720, and / or 730. Sublayer representation 740 is a subset of the bitstream that includes NAL units of a particular sublayer and lower sublayers. In the illustrated example, sublayer representation 740 includes image 741, which is a composite image 711, 721, and 731 of sublayers 710, 720, and 730. Thus, multi-layer video sequence 700 can be temporally scaled to a desired frame rate by selecting sublayer representation 740 that includes the desired set of sublayers 710, 720, and / or 730. Sublayer representation 740 may be created by employing an optical link scaler (OLS) that includes sublayers 710, 720, and / or 730 as layers. In such a case, sublayer representation 740 is selected as the output layer. Thus, temporal scalability is one of several mechanisms that can be achieved using multi-layer mechanisms.

[0116] 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 multi-layer video sequences 600 and / or 700. Furthermore, 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 may check the bitstream 800 for conformance with the standard before sending it to the decoder for decoding.

[0117] The bitstream 800 includes a VPS 811, one or more SPSs 813, multiple picture parameter sets (PPSs) 815, multiple slice headers 817, image data 820, and an SEI message 819. 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 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 an SPS 813 for corresponding parameters. The parameters of the SPS 813 may include picture sizing, bit depth, coding tool parameters, bit rate limits, etc. Note 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 image in a video sequence can reference a PPS 815. While each image references a PPS 815, it should be noted that in some instances, a single PPS 815 can contain data for multiple images. For example, multiple similar images may be coded according to similar parameters. In such cases, a single PPS 815 can contain data for such similar images. The PPS 815 can indicate coding tools, quantization parameters, offsets, etc. available for slices of the corresponding image.

[0118] The slice header 817 contains parameters specific to each slice in a picture. Thus, there may be one slice header 817 for each slice in a video sequence. The slice header 817 may include slice type information, POC, a reference picture list, prediction weights, tile entry points, deblocking parameters, etc. Note that in some examples, the bitstream 800 may also include a picture header, which is a syntax structure that contains parameters that apply to all slices in a single picture. For this reason, picture header and slice header 817 may be used interchangeably in some contexts. For example, certain parameters may move between the slice header 817 and the picture header depending on whether such parameters are common to all slices in the picture.

[0119] The image data 820 includes video data coded according to inter-prediction and / or intra-prediction, as well as corresponding transformed and quantized residual data. For example, the image data 820 may include AUs 821, DUs 822, and / or pictures 823. An AU 821 is a set of NAL units associated with each other according to specified classification rules and associated with one particular output time. A DU 822 is an AU or a subset of AUs and associated non-VCL NAL units. A picture 823 is an array of luma samples and / or an array of chroma samples that make up a frame or a field thereof. In layman's terms, an AU 821 includes various video data that may be displayed at a specified instant in a video sequence, as well as supporting syntax data. Thus, an AU 821 may include a single picture 823 in a single-layer bitstream, or multiple pictures from multiple layers all associated with the same instant in a multi-layer bitstream. A picture 823, on the other hand, is a coded image that may be output for display or used to support the coding of other pictures 823 for output. A DU 822 may include one or more pictures 823 and any supporting syntax data necessary for decoding. For example, DU 822 and AU 821 may be used interchangeably in a simple bitstream (e.g., when an AU includes a single picture). However, in a more complex multi-layer bitstream, a DU 822 may include only a portion of the video data from an AU 821. For example, an AU 821 may include pictures 823 in several layers and / or sublayers, some of which are associated with different OLSs. In such cases, a DU 822 may include only pictures 823 from a specified OLS and / or a specified layer / sublayer.

[0120] The image 823 includes one or more slices 825. A slice 825 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 the image 823, where a tile or CTU row is exclusively contained in a single NAL unit 829. Thus, a slice 825 is also contained in a single NAL unit 829. The slice 825 is further divided into CTUs and / or coding tree blocks (CTBs). A CTU is a group of samples of a predefined size that can be divided by a coding tree. A CTB is a subset of a CTU and includes the luma or chroma component 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.

[0121] The bitstream 800 is a sequence of NAL units 829. The NAL units 829 are containers for video data and / or supporting syntax. The NAL units 829 can be VCL NAL units or non-VCL NAL units. A VCL NAL unit is a NAL unit 829 coded to contain video data, such as a coded slice 825 and associated slice header 817. A non-VCL NAL unit is a NAL unit 829 that contains 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 may include a VPS 811, an SPS 813, a PPS 815, an SEI message 819, or other supporting syntax.

[0122] The SEI message 819 is a semantically specified syntax structure that conveys information not required by the decoding process to determine the values ​​of samples of the decoded image. For example, the SEI message may include data to support the HRD process or other support data not directly related to decoding the bitstream 800 at the decoder. The SEI message 819 may include a scalable nesting SEI message and / or a non-scalable nesting SEI message. A scalable nesting SEI message is a message that includes multiple SEI messages corresponding to one or more OLSs or one or more layers. A non-scalable nesting SEI message is a non-nested message and therefore includes a single SEI message. The SEI message 819 may include a BP SEI message that includes HRD parameters for initializing the HRD to manage the CPB. The SEI message 819 may also include a PT SEI message that includes HRD parameters for managing distribution information for AUs 821 in the CPB and / or DPB. The SEI message 819 may also include a DUI SEI message that includes HRD parameters for managing delivery information for the DU 822 in the CPB and / or DPB.

[0123] The bitstream 800 includes an integer (i) set of sequence-level HRD parameters 833, which are syntax elements that initialize and / or define the operating conditions of an HRD, such as the HRD 500. In some examples, a general HRD parameters (general_hrd_parameters) syntax structure can include sequence-level HRD parameters 833 that apply to all OLSs specified by the VPS 811. Sequence-level HRD parameters are HRD parameters that apply to an entire coded video sequence. A coded video sequence is one or more images 823. In one example, an encoder can encode a video sequence into layers. Each layer can include a coded video sequence. The encoder can then encode the sequence-level HRD parameters 833 into the bitstream to appropriately configure the HRD to perform conformance checks on the sequences in the OLS. The HRD parameters 833 can also indicate to a decoder that it can decode the bitstream according to a delivery schedule. The sequence-level HRD parameters 833 are included in the VPS 811. Additional parameters used to configure the HRD may also be included in the SEI message 819.

[0124] As described above, a video stream can include many OLSs and many layers, such as OLS 625, layer N 631, layer N+1 632, sublayer 710, sublayer 720, and / or sublayer 730. Furthermore, some layers may be included in multiple OLSs. Each layer and / or sublayer of each OLS is checked for conformance by the HRD according to a delivery schedule. Each delivery schedule is associated with a different CPB size and CPB delay to account for different transmission bandwidths and system capabilities. Some video coding systems allow each sublayer to define any number of delivery schedules. This can result in a large amount of signaling to support conformance checking, resulting in reduced bitstream coding efficiency. Furthermore, such flexibility introduces significant complexity, resulting in a significant increase in processor and memory resource usage in the encoder.

[0125] This disclosure includes a mechanism for simplifying HRD signaling and improving coding efficiency for videos containing multiple layers. Specifically, all layers and / or sublayers are constrained to include the same number of CPB delivery schedules. For example, an encoder can determine the maximum number of CPB delivery schedules to be used for any one layer and set the number of CPB delivery schedules for all layers to this maximum number. The number of delivery schedules may then be signaled once, for example, as part of the HRD parameters in the VPS. This eliminates the need to signal several schedules per layer / sublayer. All layers / sublayers in an OLS may also share the same delivery schedule index. These changes reduce the amount of data used to signal data related to conformance checking. This reduces the bitstream size and therefore reduces processor, memory, and / or network resource utilization in both the encoder and decoder.

[0126] Specifically, the HRD parameters 833 of the VPS 811 may include an HRD CPB count, which can be expressed as hrd_cpb_cnt_minus1 831. hrd_cpb_cnt_minus1 831 is a syntax element that specifies the number of CPB delivery schedules used in the bitstream 800. minus1 indicates that the value of hrd_cpb_cnt_minus1 831 is 1 less than the indicated value and that +1 should be added to obtain the true value. hrd_cpb_cnt_minus1 831 may range from 0 to 31, inclusive. This indicates that 1 to 32 CPB delivery schedules may be specified for the bitstream 800.

[0127] The SEI message 819 may include data describing the CPB delivery schedule indicated in the HRD parameters 833. For example, the BP SEI message may include a BP CPB count-1 (bp_cpb_cnt_minus1) 835, an initial CPB removal delay (nal_initial_cpb_removal_delay) 837, and an initial CPB removal offset (nal_initial_cpb_removal_offset) 839, which may be used to describe the CPB delivery schedule of the corresponding layer. The CPB delivery schedule is described by the pair nal_initial_cpb_removal_delay 837 and nal_initial_cpb_removal_offset 839, respectively. The nal_initial_cpb_removal_delay 837 is the default removal delay used when removing data units from the CPB of the HRD when checking pictures, AUs, and / or DUs within the bitstream, OLS, and / or layer. Thus, nal_initial_cpb_removal_delay 837 describes the timing of the CPB delivery schedule. nal_initial_cpb_removal_offset 839 is a default CPB removal offset associated with each picture, AU, and / or DU in the bitstream, OLS, and / or layer. For example, the offset may indicate the size of the data unit to be removed from the CPB of the HRD. Thus, nal_initial_cpb_removal_offset 839 describes the cache size used in the CPB delivery schedule. Thus, the HRD can determine the CPB delivery schedule based on nal_initial_cpb_removal_delay 837 and nal_initial_cpb_removal_offset 839. Thus, such a pair of values ​​is used to define each CPB delivery schedule, such as CPB delivery schedule 561.

[0128] bp_cpb_cnt_minus1 835 is a syntax element that specifies the number of nal_initial_cpb_removal_delay 837 and nal_initial_cpb_removal_offset 839 pairs used for the corresponding temporal sublayer, such as sublayers 710, 720, and / or 730. Thus, bp_cpb_cnt_minus1 835 specifies the number of delivery schedules available per layer / sublayer. The value of bp_cpb_cnt_minus1 835 can be set equal to the value of hrd_cpb_cnt_minus1 831. This ensures that the number of delivery schedules for each layer is the same as the total number of CPB delivery schedules. Thus, all layers have the same number of CPB delivery schedules. Ensuring that all layers have the same number of CPB delivery schedules reduces complex and / or redundant signaling in the bitstream 800, thereby increasing coding efficiency. This approach also simplifies the HRD process. As a result, processor, memory, and / or network signaling resource usage is reduced in both the encoder and decoder. Note also that each CPB delivery schedule in the target layer / OLS can be referenced by a unique schedule index (ScIdx). ScIdx can include values ​​ranging from 0 to the value of hrd_cpb_cnt_minus1 831, inclusive. This indicates that ScIdx can vary from a value of 0 for the first CPB delivery schedule to a value of hrd_cpb_cnt_minus1 for the last CPB delivery schedule. Because each layer / sublayer contains the same number of CPB delivery schedules and ScIdx can uniquely identify any CPB delivery schedule, layers / sublayers within an OLS can also share the same set of ScIdx values. This further reduces the complexity of the HRD process. Therefore, the mechanism described with respect to bitstream 800 can enhance the functionality of the encoder and / or decoder.Additionally, the mechanisms described with respect to bitstream 800 may support increased coding efficiency and / or reduced processor, memory, and / or network communication resources in the encoder and / or decoder.

[0129] The aforementioned information will now be described in more detail below. Layered video coding is also referred to as scalable video coding or scalable video coding. 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, multiview scalability, frame rate scalability, etc. When using multi-layer coding techniques, an image or a portion thereof may be coded without using a reference picture (intra-prediction), coded by referencing a reference picture in the same layer (inter-prediction), and / or coded by referencing a reference picture in another layer (inter-layer prediction). The reference picture used for inter-layer prediction of the current image is called an inter-layer reference picture (ILRP). Figure 6 shows an example of multi-layer coding for spatial scalability in which images of different layers have different resolutions.

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

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

[0132] VVC can also support layered video coding. A VVC bitstream can include multiple layers. All layers may 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 can indicate whether a layer is a simulcast layer or whether some layers use ILP. If 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 designated as output layers. An output layer is a layer of the OLS that is output. In some implementations of VVC, if a layer is a simulcast layer, only one layer may be selected for decoding and output. In some implementations of VVC, the entire bitstream including all layers is designated to be decoded if any layer uses ILP. Furthermore, certain layers of the layers are designated as output layers. The output layer may be designated to be the top layer only, all layers, or the top layer plus a set of designated lower layers.

[0133] Video coding standards may specify an HRD for verifying bitstream conformance through specified HRD conformance tests. SHVC and MV-HEVC employ three sets of bitstream conformance tests to check bitstream conformance. The bitstream is referred to as the entire bitstream and is denoted as entireBitstream. The first set of bitstream conformance tests is for testing the conformance of the entire bitstream and its corresponding temporal subset. Such tests are employed regardless of whether there is a layer set specified by the active VPS that includes all nuh_layer_id values ​​of VCL NAL units present in the entire bitstream. Therefore, the entire bitstream is always checked for conformance, even if one or more layers are not included in the output set. The second set of bitstream conformance tests is for testing the conformance of the layer set and associated temporal subset specified by the active VPS. For all these tests, only base layer pictures (e.g., pictures with nuh_layer_id equal to 0) are decoded and output. Other pictures are ignored by the decoder when the decoding process is invoked. A third set of bitstream conformance tests is employed to test conformance of the OLS and associated temporal subsets specified by the VPS extension portion of the active VPS based on the OLS and bitstream partitioning, where the bitstream partitioning includes one or more layers of the OLS of a multi-layer bitstream.

[0134] The above-described aspects involve certain problems. For example, the first two sets of conformance tests may be applied to layers that are not decoded or output. For example, layers other than the lowest layer are not decoded or output. In a practical application, a decoder may only receive data that is decoded. Therefore, using the first two sets of conformance tests both complicates the codec design and may waste bits to carry both sequence-level and picture-level parameters used to support the conformance tests. The third set of conformance tests involves bitstream splitting. Such splitting may relate to one or more layers of the OLS of a multi-layer bitstream. Instead, if conformance tests always operate separately for each layer, the HRD may be significantly simplified.

[0135] Signaling sequence-level HRD parameters can be complex. For example, sequence-level HRD parameters may be signaled in multiple places, such as both the SPS and the VPS. Furthermore, sequence-level HRD parameter signaling can include redundancy. For example, information that may generally be the same for the entire bitstream may be repeated for each layer in each OLS. Furthermore, the exemplary HRD scheme allows for the selection of a different delivery schedule per layer. Such a delivery schedule may be selected from a list of schedules signaled for each layer per operation point, where an operation point is an OLS or a temporal subset of an OLS. Such a system is complex. Furthermore, the exemplary HRD scheme allows for the association of incomplete AUs with buffering period SEI messages. An incomplete AU is an AU that does not have images for all layers present in the CVS. However, HRD initialization in such AUs can be problematic. For example, the HRD may not be properly initialized for layers that have layer access units that are not present in the incomplete AU. In addition, the demultiplexing process to derive layer bitstreams may not be efficient enough to remove nested SEI messages that do not apply to the target layer. Layer bitstreams occur when a bitstream split contains only one layer. Furthermore, the applicable OLSs of non-scalable nested buffering periods, picture timing, and decoding unit information SEI messages may be specified for the entire bitstream. However, the non-scalable nested buffering period should instead be applicable to the 0th OLS.

[0136] Furthermore, some VVC implementations may fail to infer HDR parameters when sub_layer_cpb_params_present_flag is equal to 0. Such inference may enable proper HRD operation. In addition, the values ​​of bp_max_sub_layers_minus1 and pt_max_sub_layers_minus1 may be required to be equal to the value of sps_max_sub_layers_minus1. However, buffering period and picture timing SEI messages may be nested and applicable to multiple OLSs and multiple layers in each of the multiple OLSs. In such a context, the involved layer may refer to multiple SPSs. Therefore, it may be difficult for the system to track which SPS corresponds to each layer. Therefore, the values ​​of these two syntax elements should be constrained based on the value of vps_max_sub_layers_minus1 instead. Furthermore, because different layers can have different numbers of sublayers, the values ​​of these two syntax elements may not always be equal to a specific value in all buffering period and picture timing SEI messages.

[0137] Additionally, the following issues are associated with the HRD design in both SHVC / MV-HEVC and VVC: The sub-bitstream extraction process may not remove SEI NAL units that contain nested SEI messages that are not required for the target OLS.

[0138] Generally, this disclosure describes techniques for scalable nesting of SEI messages for output layer sets in a multi-layer video bitstream. The description of this technique is based on VVC. However, the technique also applies to layered video coding based on other video codec specifications.

[0139] One or more of the above-mentioned problems can be solved as follows. Specifically, the present disclosure includes a method and related aspects for HRD design that enables efficient signaling of HRD parameters using much simpler HRD operations compared to SHVC and MV-HEVC. Each of the solutions described below addresses the above-mentioned problems. For example, instead of requiring three sets of conformance tests, the present disclosure only needs to employ one set of conformance tests to test the conformance of an OLS specified by a VPS. Furthermore, instead of a bitstream splitting-based design, the disclosed HRD mechanism can always operate separately for each layer of an OLS. Furthermore, sequence-level HRD parameters that are global to all layers and sublayers of all OLSs only need to be signaled once, for example, in a VPS. In addition, a single number of delivery schedules need only be signaled for all layers and sublayers of all OLSs. The same delivery schedule index can also be applied to all layers of an OLS. Furthermore, an incomplete AU does not need to be associated with a buffering period SEI message. An incomplete AU is an AU that does not contain pictures for all layers present in the CVS. This ensures that the HRD is always properly initialized for all layers of the OLS. Also, a mechanism for efficiently removing nested SEI messages that do not apply to the target layer in the OLS is disclosed. This supports the demultiplexing process for deriving the layer bitstream. Additionally, the applicable OLS for the non-scalable nested buffering period, picture timing, and decoding unit information SEI messages may be specified as the 0th OLS. Furthermore, when sub_layer_cpb_params_present_flag is equal to 0, HDR parameters can be inferred, potentially enabling proper HRD operation. The values ​​of bp_max_sub_layers_minus1 and pt_max_sub_layers_minus1 may be required to be in the range of 0 to vps_max_sub_layers_minus1.Thus, such parameters do not need to be specific values ​​for all buffering period and picture timing SEI messages. Also, the sub-bitstream extraction process can remove SEI NAL units that contain nested SEI messages that do not apply to the target OLS.

[0140] An exemplary implementation of the aforementioned mechanism is as follows: An output layer is a layer of an output layer set that is output. An OLS is a set of layers that includes a specified set of layers, where one or more layers in the set of layers are designated to be output layers. An OLS layer index is an index of a layer in an OLS to a list of layers in the OLS. A sub-bitstream extraction process is a specified process in which NAL units in a bitstream that do not belong to a target set, as determined by a target OLS index and a target highest TemporalId, are removed from the bitstream, and the output sub-bitstream contains NAL units in the bitstream that belong to the target set.

[0141] An example video parameter set syntax is as follows: [Table 1]

[0142] The syntax of an exemplary sequence parameter set RBSP is as follows: [Table 2]

[0143] An exemplary DPB parameter syntax is as follows: [Table 3]

[0144] An exemplary general HRD parameter syntax is as follows: [Table 4]

[0145] The semantics of an example video parameter set RBSP are as follows: Setting each_layer_is_an_ols_flag equal to 1 specifies that each output layer set contains only one layer, that each layer in the bitstream is itself an output layer set, and that the single included layer is the only output layer. Setting each_layer_is_an_ols_flag equal to 0 specifies that an output layer set can contain more than one layer. If vps_max_layers_minus1 is equal to 0, then the value of each_layer_is_an_ols_flag is inferred to be equal to 1. Otherwise, if vps_all_independent_layers_flag is equal to 0, then the value of each_layer_is_an_ols_flag is inferred to be equal to 0.

[0146] Setting 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, where the i-th OLS contains layers with layer indices from 0 to i, inclusive, and for each OLS, only the top layer of the OLS is output. Setting 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, where the i-th OLS contains layers with layer indices from 0 to i, inclusive, and for each OLS, all layers of the OLS are output. Setting ols_mode_idc equal to 2 specifies that the total number of OLSs specified by the VPS are explicitly signaled, and for each OLS, the top layer of the OLS and the set of explicitly signaled lower layers are output. The value of ols_mode_idc shall be in the range from 0 to 2, inclusive. The value 3 of ols_mode_idc is reserved. If 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 OLSs specified by the VPS when ols_mode_idc is equal to 2.

[0147] The variable TotalNumOlss, which specifies the total number of OLSs specified by the VPS, is derived as follows:

number

[0148] layer_included_flag[i][j] specifies whether to include the jth layer (layer with nuh_layer_id equal to vps_layer_id[j]) in the ith OLS when ols_mode_idc is equal to 2. Setting layer_included_flag[i][j] equal to 1 specifies that the jth layer is to be included in the ith OLS. Setting layer_included_flag[i][j] equal to 0 specifies that the jth layer is not to be included in the ith OLS.

[0149] The variable NumLayersInOls[i] that specifies the number of layers of the i-th OLS and the variable LayerIdInOls[i][j] that specifies the nuh_layer_id value of the j-th layer of the i-th OLS are derived as follows:

number

[0150] The variable LayerIdInOls[i][j], which specifies the OLS layer index of the layer whose nuh_layer_id is equal to OlsLayeIdx[i][j], is derived as follows:

number

[0151] The lowest layer in each OLS shall be an independent layer. In other words, for each i in the range 0 to TotalNumOlss-1, inclusive, 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 k in the range 0 to vps_max_layers_minus1, inclusive, for each layer for which a particular value of nuh_layer_id nuhLayerId is equal to one of vps_layer_id[k], there may be at least one pair of values ​​of i and j, where i is in the range 0 to TotalNumOlss-1, inclusive, and j is in the range NumLayersInOls[i]-1, inclusive, and the value of LayerIdInOls[i][j] is equal to nuhLayerId. Any layer of the OLS may be an output layer of the OLS or a reference layer (direct or indirect) of an output layer of the OLS.

[0152] vps_output_layer_flag[i][j] specifies whether the jth layer of 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 of the ith OLS is output. Setting vps_output_layer_flag[i] equal to 0 specifies that the jth layer of the ith OLS is not output. When vps_all_independent_layers_flag is equal to 1 and each_layer_is_an_ols_flag is equal to 0, the value of vps_output_layer_flag[i] is inferred to be equal to 1. The variable OutputLayerFlag[i][j], where a value of 1 specifies that the jth layer of the ith OLS is output and a value of 0 specifies that the jth layer of the ith OLS is not output, is derived as follows:

number

[0153] Setting vps_extension_flag equal to 0 specifies that the vps_extension_data_flag syntax element is not present in the VPS RBSP syntax structure. Setting 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 can have any value. The presence and value of vps_extension_data_flag does not affect the decoder's conformance to the specified profile. Decoders shall ignore all vps_extension_data_flag syntax elements.

[0154] Exemplary DPB parameter semantics are as follows: The dpb_parameters() syntax structure provides DPB size information and, optionally, maximum image reordering and maximum latency (MRML) information. Each SPS contains one or more dpb_parameters() syntax structures. The first dpb_parameters() syntax structure of an SPS contains both DPB size information and MRML information. If present, the second dpb_parameters() syntax structure of an SPS contains only DPB size information. The MRML information in the first dpb_parameters() syntax structure of an SPS applies to the layer referencing the SPS, regardless of whether that layer is an output layer of the OLS. The DPB size information in the first dpb_parameters() syntax structure of an SPS applies to the layer referencing the SPS if that layer is an output layer of the OLS. The DPB size information contained in the second dpb_parameters() syntax structure of an SPS, if present, applies to the layer referencing the SPS if that layer is a non-output layer of the OLS. If an SPS contains only one dpb_parameters() syntax structure, the DPB size information for the layer as a non-output layer is inferred to be the same as for the layer as an output layer.

[0155] Exemplary general HRD parameter semantics are as follows: The general_hrd_parameters() syntax structure provides the HRD parameters used in HRD operations. Setting sub_layer_cpb_params_present_flag equal to 1 specifies that the i-th layer_level_hrd_parameters() syntax structure includes HRD parameters for sub-layer representations whose TemporalId is in the range from 0 to hrd_max_temporal_id[i], inclusive. Setting sub_layer_cpb_params_present_flag equal to 0 specifies that the i-th layer_level_hrd_parameters() syntax structure includes HRD parameters for sub-layer representations whose TemporalId is equal to hrd_max_temporal_id[i] only. If vps_max_sub_layers_minus1 is equal to 0, the value of sub_layer_cpb_params_present_flag is inferred to be equal to 0. If sub_layer_cpb_params_present_flag is equal to 0, the HRD parameters for sub-layer representations whose TemporalId is in the range from 0 to hrd_max_temporal_id[i]-1, inclusive, are inferred to be the same as those for sub-layer representations whose TemporalId is equal to hrd_max_temporal_id[i]. These include the HRD parameters in the layer_level_hrd_parameters syntax structure starting from the fixed_pic_rate_general_flag[i] syntax element up to the sub_layer_hrd_parameters(i) syntax structure immediately below the conditional statement if(general_vcl_hrd_params_present_flag). num_layer_hrd_params_minus1+1 specifies the number of layer_level_hrd_parameters() syntax structures present in the general_hrd_parameters() syntax structure.The value of num_layer_hrd_params_minus1 shall be in the range of 0 to 63, inclusive. hrd_cpb_cnt_minus1+1 specifies the number of alternative CPB specifications in the CVS bitstream. The value of hrd_cpb_cnt_minus1 shall be in the range of 0 to 31, inclusive. hrd_max_temporal_id[i] specifies the TemporalId of the highest 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] shall be in the range of 0 to vps_max_sub_layers_minus1, inclusive. If vps_max_sub_layers_minus1 is equal to 0, the value of hrd_max_temporal_id[i] is inferred to be equal to 0. layer_level_hrd_idx[i][j] specifies the index of the layer_level_hrd_parameters() syntax structure that applies to the jth layer of the ith OLS. The value of layer_level_hrd_idx[[i][j] shall be in the range from 0 to num_layer_hrd_params_minus1, inclusive. If not present, the value of layer_level_hrd_idx[[0][0] is inferred to be equal to 0.

[0156] 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. The bitstream conformance requirement for an input bitstream is that any output sub-bitstream that is the output of the process specified in this section for a bitstream with inputs targetOlsIdx equal to the index of the list of OLSs specified by the VPS and tIdTarget equal to any value in the range 0 to 6, inclusive, and that satisfies the following conditions is a conforming bitstream: The output sub-bitstream should contain at least one VCL NAL unit whose nuh_layer_id is equal to each of the nuh_layer_id values ​​in LayerIdInOls[targetOlsIdx]. The output sub-bitstream should contain at least one VCL NAL unit whose TemporalId is equal to tIdTarget. A conformant bitstream contains one or more coded slice NAL units with TemporalId equal to 0, but need not contain any coded slice NAL units with nuh_layer_id equal to 0.

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

[0158] General aspects of an exemplary HRD are as follows: This section specifies the HRD and its usage for checking bitstream and decoder conformance. A set of bitstream conformance tests is used to check the conformance of a bitstream, called the entire bitstream, denoted entireBitstream. A set of bitstream conformance tests is for testing the conformance of each OLS and temporal subset of each OLS specified by the VPS. For each test, the following ordered steps are applied in the order listed:

[0159] The operation point under test, denoted targetOp, is selected by selecting the target OLS with the OLS index opOlsIdx and the highest TemporalId value opTid. The value of opOlsIdx lies in the range 0 to TotalNumOlss-1, inclusive. The value of opTid lies in the range 0 to vps_max_sub_layers_minus1, inclusive. The values ​​of opOlsIdx and opTid are such that the sub-bitstream BitstreamToDecode, which is the output of invoking the sub-bitstream extraction process with entireBitstream, opOlsIdx, and opTid as inputs, satisfies the following conditions: There is at least one VCL NAL unit whose nuh_layer_id is equal to each of the nuh_layer_id values ​​in LayerIdInOls[opOlsIdx] of BitstreamToDecode. There is at least one VCL NAL unit whose TemporalId is equal to opTid of BitstreamToDecode.

[0160] The values ​​of TargetOlsIdx and Htid are set 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, inclusive. The access unit in the BitstreamToDecode associated with the buffering period SEI message applicable to TargetOlsIdx (present in TargetLayerBitstream or available through an external mechanism not specified herein) is selected as the HRD initialization point and is called access unit 0 for each layer of the target OLS.

[0161] The subsequent steps are applied to each layer with OLS layer index TargetOlsLayerIdx in the target OLS. If there is only one layer in the target OLS, the tested layer bitstream TargetLayerBitstream is set equal to BitstreamToDecode. Otherwise, TargetLayerBitstream is derived by invoking a demultiplexing process to derive the layer bitstream with BitstreamToDecode, TargetOlsIdx, and TargetOlsLayerIdx as inputs, and the output is assigned to TargetLayerBitstream.

[0162] The layer_level_hrd_parameters() syntax structure and sub_layer_hrd_parameters() syntax structure applicable to the TargetLayerBitstream are selected as follows: The layer_level_hrd_idx[TargetOlsIdx][TargetOlsLayerIdx]th layer_level_hrd_parameters() syntax structure in the VPS (or provided through an external mechanism such as user input) is selected. In the selected layer_level_hrd_parameters() syntax structure, if BitstreamToDecode is a Type I bitstream, the sub_layer_hrd_parameters(Htid) syntax structure immediately following 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 immediately follows either the condition if(general_vcl_hrd_params_present_flag) (in which case the variable NalHrdModeFlag is set equal to 0) or the condition if(general_nal_hrd_params_present_flag) (in which case the variable NalHrdModeFlag is set equal to 1) is selected. If 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, if present, are discarded from the TargetLayerBitstream, and the remaining bitstream is assigned to the TargetLayerBitstream.

[0163] If 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. For each access unit in the TargetLayerBitstream starting with access unit 0, a buffering period SEI message (present in the TargetLayerBitstream or available through an external mechanism) associated with the access unit and applied to TargetOlsIdx and TargetOlsLayerIdx is selected, a picture timing SEI message (present in the TargetLayerBitstream or available through an external mechanism) associated with the access unit and applied to TargetOlsIdx and TargetOlsLayerIdx is selected, and if 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 the TargetLayerBitstream or available through an external mechanism) associated with the decoding unit within the access unit and applied to TargetOlsIdx and TargetOlsLayerIdx is selected.

[0164] Each conformance test includes a combination of one option in each of the above steps. If more than one option exists for a step, only one option is selected for any particular conformance test. All possible combinations of all steps form the complete set of conformance tests. For each operating point being tested, the number of bitstream conformance tests 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, n0 is equal to 1. Otherwise (if BitstreamToDecode is a Type II bitstream), 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.

[0165] The HRD includes a bitstream demultiplexer (optionally present), a coded picture buffer (CPB) for each layer, an instantaneous decoding process for each layer, a decoded picture buffer (DPB) containing sub-DPBs for each layer, and output cropping.

[0166] In one example, the HRD operates as follows: The HRD is initialized to 0 in a decoding unit, and each CPB and each sub-DPB of the DPB is set to be empty. The sub-DPB fullness of each sub-DPB is set equal to 0. After initialization, the HRD is not reinitialized by subsequent buffering period SEI messages. Data associated with each decoding unit that flows into each CPB according to the specified arrival schedule is delivered by the HSS. Data associated with each decoding unit is removed by the instantaneous decoding process at the CPB removal time of the decoding unit and is instantly decoded. Each decoded image is placed in a DPB. A decoded image is removed from the DPB when it is no longer needed for inter-prediction reference and no longer needed for output.

[0167] In one example, the demultiplexing process for deriving layer bitstreams is as follows: The inputs to this process are bitstream inBitstream, target OLS index targetOlsIdx, and target OLS layer index targetOlsLayerIdx. The output of this process is layer bitstream outBitstream. The output layer bitstream outBitstream is derived as follows: Bitstream outBitstream is set to be identical to bitstream inBitstream. Remove all NAL units from outBitstream whose nuh_layer_id is not equal to LayerIdInOls[targetOlsIdx][targetOlsLayerIdx]. Remove from outBitstream all SEI NAL units containing scalable nesting SEI messages with nesting_ols_flag equal to 1 and with values ​​of i and j not in the ranges from 0 to nesting_num_ols_minus1, inclusive, and from 0 to nesting_num_olss_layers_minus1[i], inclusive, respectively, so that NestingOlsLayerIdx[i][j] is equal to targetOlsLayerIdx. Remove from outBitstream all SEI NAL units containing scalable nesting SEI messages with nesting_ols_flag equal to 1 and with values ​​of i and j not in the ranges from 0 to nesting_num_olss_minus1, inclusive, and from 0 to nesting_num_ols_layers_minus1[i], inclusive, respectively, so that NestingOlsLayerIdx[i][j] is less than targetOlsLayerIdx.Remove from outBitstream all SEI NAL units containing scalable nesting SEI messages with nesting_ols_flag equal to 0 and no value of i in the range from 0 to LayerIdInOls-1, inclusive, so that NestingLayerId[i] is equal to NestingNumLayers[targetOlsIdx][targetOlsLayerIdx]. Remove from outBitstream all SEI NAL units containing scalable nesting SEI messages with nesting_ols_flag equal to 0 and at least one value of i in the range from 0 to LayerIdInOls-1, inclusive, so that NestingLayerId[i] is less than NestingNumLayers[targetOlsIdx][targetOlsLayerIdx].

[0168] An exemplary buffering period SEI message syntax is as follows: [Table 5]

[0169] An exemplary scalable nesting SEI message syntax is as follows: [Table 6]

[0170] Exemplary general SEI payload semantics are as follows: The following apply to the applicable layers of a non-scalable nested SEI message (in the context of an OLS or in general): For a non-scalable nested SEI message, if 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 lowest layer in the context of the 0th OLS. For a non-scalable nested SEI message, if payloadType is equal to any value in VclAssociatedSeiList, the non-scalable nested SEI message applies only to layers whose nuh_layer_id of the VCL NAL unit is equal to the nuh_layer_id of the SEI NAL unit containing the SEI message.

[0171] The semantics of an exemplary buffering period SEI message are as follows: The buffering period SEI message provides initial CPB removal delay and initial CPB removal delay offset information for initializing the HRD at the position of the associated access unit in decoding order. When a buffering period SEI message is present, a picture whose TemporalId is equal to 0 and that is not a RASL or RADL (random access decodable leading) picture is said to be a notDiscardablePic picture. If the current picture is not the first picture of the bitstream in decoding order, let prevNonDiscardablePic be the preceding picture in decoding order whose TemporalId is equal to 0 and that is not a RASL or RADL picture.

[0172] The presence of a buffering period SEI message is specified as follows: If NalHrdBpPresentFlag is equal to 1 or VclHrdBpPresentFlag is equal to 1, then the following applies for each access unit in the CVS: If the access unit is an IRAP or Gradual Decoder Refresh (GDR) access unit, then a buffering period SEI message applicable to the operation point shall be associated with the access unit. Otherwise, if the access unit contains notDiscardablePic, then a buffering period SEI message applicable to the operation point may or may not be associated with the access unit. Otherwise, the access unit shall not be associated with a buffering period SEI message applicable to the operation point. Otherwise (if both NalHrdBpPresentFlag and VclHrdBpPresentFlag are equal to 0), then no access unit in the CVS shall be associated with a buffering period SEI message. In some applications, it may be desirable for buffering period SEI messages to be present frequently (e.g., for random access in IRAP or non-IRAP pictures, or for bitstream splicing). If pictures in an access unit are associated with a buffering period SEI message, the access unit shall have pictures of each of the layers present in the CVS, and each picture in the access unit shall be associated with a buffering period SEI message.

[0173] bp_max_sub_layers_minus1+1 specifies the maximum number of temporal sublayers for which the CPB removal delay and CBP removal offset are indicated in the buffering period SEI message. The value of bp_max_sub_layers_minus1 shall be in the range from 0 to vps_max_sub_layers_minus1, inclusive. bp_cpb_cnt_minus1+1 specifies the number of syntax element pairs nal_initial_cpb_removal_delay[i][j] and nal_initial_cpb_removal_offset[i][j] for the i-th temporal sublayer when bp_nal_hrd_params_present_flag is equal to 1, and specifies the number of syntax element pairs vcl_initial_cpb_removal_delay[i][j] and vcl_initial_cpb_removal_offset[i][j] for the i-th temporal sublayer when bp_vcl_hrd_params_present_flag is equal to 1. The value of bp_cpb_cnt_minus1 shall be in the range 0 to 31, inclusive. The value of bp_cpb_cnt_minus1 shall be equal to the value of hrd_cpb_cnt_minus1.

[0174] The semantics of an exemplary picture timing SEI message are as follows: The picture timing SEI message provides CPB removal delay and DPB output delay information for the access unit associated with the SEI message. If bp_nal_hrd_params_present_flag or bp_vcl_hrd_params_present_flag of the buffering period SEI message applicable to the current access unit is equal to 1, then the variable CpbDpbDelaysPresentFlag is set equal to 1. Otherwise, CpbDpbDelaysPresentFlag is set equal to 0. The presence of a picture timing SEI message is specified as follows: If CpbDpbDelaysPresentFlag is equal to 1, then a picture timing SEI message shall be associated with the current access unit. Otherwise (CpbDpbDelaysPresentFlag is equal to 0), then there shall be no picture timing SEI message associated with the current access unit. The TemporalId in the picture timing SEI message syntax is the TemporalId of the SEI NAL unit that contains the picture timing SEI message. pt_max_sub_layers_minus1+1 specifies the TemporalId of the highest sub-layer representation whose CPB removal delay information is included in the picture timing SEI message. The value of pt_max_sub_layers_minus1 shall be in the range from 0 to vps_max_sub_layers_minus1, inclusive.

[0175] The semantics of an exemplary scalable nesting SEI message are as follows: The scalable nesting SEI message provides a mechanism for associating an SEI message with a specific layer within the context of a specific OLS or with a specific layer not within the context of an OLS. The scalable nesting SEI message contains one or more SEI messages. An SEI message included in a scalable nesting SEI message is also referred to as a scalable nested SEI message. A bitstream conformance requirement is that the following restrictions apply to the inclusion of SEI messages in a scalable nesting SEI message: SEI messages with payloadType equal to 132 (decoded image hash) or 133 (scalable nesting) shall not be included in a scalable nesting SEI message. If a scalable nesting SEI message contains a buffering period, picture timing, or decoding unit information SEI message, the scalable nesting SEI message shall not contain any other SEI message whose payloadType is not equal to 0 (buffering period), 1 (picture timing), or 130 (decoding unit information).

[0176] The bitstream conformance requirements are that the following restrictions apply to the value of nal_unit_type of SEI NAL units that contain scalable nesting SEI messages: If the scalable nesting SEI message contains an SEI message with payloadType equal to 0 (buffering duration), 1 (picture timing), 130 (decoded unit information), 145 (dependent RAP indication), or 168 (frame field information), the SEI NAL unit that contains the scalable nesting SEI message shall have nal_unit_type equal to PREFIX_SEI_NUT. If the scalable nesting SEI message contains an SEI message with payloadType equal to 132 (decoded image hash), the SEI NAL unit that contains the scalable nesting SEI message shall have nal_unit_type equal to SUFFIX_SEI_NUT.

[0177] Set nesting_ols_flag to 1 to specify that the scalable nesting SEI message applies to a particular layer in the context of a particular OLS. Set nesting_ols_flag to 0 to specify that the scalable nesting SEI message applies to a particular layer in general (not in the context of an OLS). Bitstream conformance requirements are that the following restrictions apply to the value of nesting_ols_flag: If 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. If the scalable nesting SEI message contains an SEI message with payloadType equal to a value of 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 shall be in the range from 0 to TotalNumOlss-1, inclusive. 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 nested SEI message applies if nesting_ols_flag is equal to 1. The value of nesting_ols_idx_delta_minus1[i] shall be in the range from 0 to TotalNumOlss-2, inclusive. The variable NestingOlsIdx[i] is derived as follows:

number

[0178] nesting_num_ols_layers_minus1[ i ]+1 specifies the number of layers to which the scalable nesting SEI message applies in the context of the NestingOlsIdx[i]th OLS. The value of nesting_num_ols_layers_minus1[i] shall be in the range from 0 to NumLayersInOls[NestingOlsIdx[i]]-1, inclusive. nesting_ols_layer_idx_delta_minus1[i][j] is used to derive the variable NestingOlsLayerIdx[i][j], which specifies the OLS layer index of the jth layer to which the scalable nesting SEI message applies in the context of the NestingOlsIdx[i]th OLS, when nesting_ols_flag is equal to 1. The value of nesting_ols_layer_idx_delta_minus1[i] shall be in the range from 0 to NumLayersInOls[nestingOlsIdx[i]]-2, inclusive. The variable NestingOlsLayerIdx[i][j] is derived as follows:

number

[0179] The smallest of all values ​​of LayerIdInOls[NestingOlsIdx[i]][NestingOlsLayerIdx[i][0]] for i in the range from 0 to nesting_num_olss_minus1, inclusive, shall be equal to the nuh_layer_id of the current SEI NAL unit (the SEI NAL unit that contains the scalable nesting SEI message). nesting_all_layers_flag is set to 1 to specify that the scalable nesting SEI message applies generically to all layers whose nuh_layer_id is greater than or equal to the nuh_layer_id of the current SEI NAL unit. nesting_all_layers_flag is set to 0 to specify that the scalable nesting SEI message may or may not apply generically to all layers whose nuh_layer_id is greater than or equal to the nuh_layer_id of the current SEI NAL unit.

[0047] nesting_num_layers_minus1+1 specifies the number of layers to which a scalable nested SEI message generally applies. The value of nesting_num_layers_minus1 shall be in the range from 0 to vps_max_layers_minus1-GeneralLayerIdx[nuh_layer_id], inclusive, 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 ith layer to which a scalable nested SEI message generally applies if nesting_all_layers_flag is equal to 0. The value of nesting_layer_id[i] shall be greater than nuh_layer_id, where nuh_layer_id is the nuh_layer_id of the current SEI NAL unit.If nesting_ols_flag is equal to 0, the variable NestingNumLayers, which specifies the number of layers to which the scalable nested SEI message generally applies, and the list NestingLayerId[i], for i ranging from 0 to NestingNumLayers-1, inclusive, which specifies the list of nuh_layer_id values ​​of the layers to which the scalable nested SEI message generally applies, are derived as follows, where nuh_layer_id is the nuh_layer_id of the current SEI NAL unit:

number

[0180] nesting_num_seis_minus1+1 specifies the number of scalable nested SEI messages. The value of nesting_num_seis_minus1 shall be in the range of 0 to 63, inclusive. nesting_0_bit shall be equal to 0.

[0181] 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 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 communicating data upstream and / or downstream over a network. The video coding device 900 also includes a processor 930 including a logic unit and / or central processing unit (CPU) for processing data and a memory 932 for storing data. The video coding device 900 may also include electrical, optical-electrical (OE) components, electrical-optical (EO) components, and / or wireless communication components coupled to the upstream port 950 and / or downstream port 920 for communication of data over an electrical, optical, or wireless communication network. The video coding device 900 may also include input and / or output (I / O) devices 960 for communicating data to and 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 interacting with such output devices.

[0182] 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 methods 100, 1000, and 1100, which may employ the multi-layer video sequence 600, the multi-layer video sequence 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 be employed to implement an HRD. Furthermore, the coding module 914 may be employed to encode parameters into a bitstream and support an HRD conformance check process. Accordingly, the coding module 914 may be configured to execute a mechanism to address one or more of the above-mentioned problems. Accordingly, the coding module 914 causes the video coding device 900 to provide additional functionality and / or coding efficiency when coding video data. Accordingly, the coding module 914 improves the functionality of the video coding device 900 while also addressing problems specific to video coding techniques. Furthermore, the coding module 914 effects a transformation of the video coding device 900 into a different state. 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).

[0183] Memory 932 comprises one or more memory types such as a disk, tape drive, solid state drive, read-only memory (ROM), random access memory (RAM), flash memory, ternary content addressable memory (TCAM), static random access memory (SRAM), etc. Memory 932 is used as an overflow data storage device, stores programs when such programs are selected for execution, and can store instructions and data read during program execution.

[0184] 10 is a flowchart of an example method 1000 for encoding a video sequence into a bitstream, such as bitstream 800, where all layers in the bitstream have the same number of CPB delivery schedules, such as CPB delivery schedule 561. Method 1000 may be employed by an encoder, such as codec system 200, encoder 300, and / or video coding device 900, in performing method 100. Furthermore, method 1000 may operate on HRD 500 and, therefore, may perform conformance testing on multi-layer video sequences 600 and / or 700.

[0185] Method 1000 may begin when an encoder receives a video sequence and determines, based on, for example, user input, to encode the video sequence into a multi-layer bitstream. In step 1001, the encoder encodes a bitstream including coded images of one or more layers, such as layer N 631, layer N+1 632, sublayer 710, sublayer 720, and / or sublayer 730. In some examples, the multiple layers are organized into one or more OLSs, such as OLS 625.

[0186] In step 1003, the encoder encodes the HRD parameter syntax structure into the bitstream. The HRD parameter syntax structure is a data object containing one or more HRD parameters, which may be included in syntax elements within the syntax structure. The HRD parameters of the HRD syntax structure specify that all of the multiple layers are associated with the same number of CPB delivery schedules. In one example, the number of CPB delivery schedules is specified by the HRD CPB count - 1 (hrd_cpb_cnt_minus1) syntax element. minus1 indicates that the value of hrd_cpb_cnt_minus1 is 1 less than the indicated value and that +1 should be added to obtain a true value. hrd_cpb_cnt_minus1 may range from 0 to 31, inclusive. This indicates that 1 to 32 CPB delivery schedules may be specified and that all layers are associated with the same number of CPB delivery schedules. The HRD parameter syntax structure can be encoded into the bitstream within a VPS that specifies an OLS.

[0187] In some examples, each corresponding CPB delivery schedule of a target OLS can be referenced by a unique schedule index (ScIdx). ScIdx can include values ​​ranging from 0 to the value of hrd_cpb_cnt_minus1, inclusive. This indicates that ScIdx can vary from a value of 0 for the first CPB delivery schedule to a value of hrd_cpb_cnt_minus1 for the last CPB delivery schedule. In some examples, each CPB delivery schedule is described by a pair of an initial CPB removal delay and an initial CPB removal offset. The initial CPB removal delay (nal_initial_cpb_removal_delay) is the default removal delay used when removing data units from the CPB of an HRD when checking pictures, AUs, and / or DUs in the bitstream, OLS, and / or layer. The initial CPB removal offset (nal_initial_cpb_removal_offset) is the default CPB removal offset associated with each picture, AU, and / or DU in the bitstream, OLS, and / or layer. A layer may also be associated with a BP CPB count-1 (bp_cpb_cnt_minus1)+1 syntax element. BP CPB count-1 is a syntax element that specifies the number of pairs of initial CPB removal delay and initial CPB removal offset, and therefore the number of delivery schedules available for each layer / sublayer. The value of bp_cpb_cnt_minus1 may be set equal to the value of hrd_cpb_cnt_minus1. This ensures that the number of delivery schedules for each layer is the same as the total number of CPB delivery schedules. Thus, all layers have the same number of CPB delivery schedules. Syntax elements describing CPB delivery schedules may be included in an SEI message. For example, nal_initial_cpb_removal_delay, nal_initial_cpb_removal_offset, and bp_cpb_cnt_minus1 may be included in a BP SEI message.

[0188] In step 1005, the HRD obtains HRD parameters from the HRD parameter syntax structure and performs a set of bitstream conformance tests on multiple layers based on the CPB delivery schedule. For example, the HRD may obtain hrd_cpb_cnt_minus1 to determine the number of CPB delivery schedules. The HRD may also obtain bp_cpb_cnt_minus1 to determine the number of CPB delivery schedules for each layer. The HRD may also obtain nal_initial_cpb_removal_delay and nal_initial_cpb_removal_offset to determine each of the CPB delivery schedules. The HRD may then perform conformance tests on multiple layers based on the CPB delivery schedule. The HRD may run on the same processor as the encoder. In another example, the HRD may run on a processor in the same chassis as the encoder. In another example, the HRD may run on a processor in the same network as the encoder.

[0189] In step 1007, the encoder stores the bitstream for communication to the decoder.

[0190] 11 is a flowchart of an example method 1100 for decoding a video sequence from a bitstream, such as bitstream 800, where all layers in the bitstream have the same number of CPB delivery schedules, e.g., CPB delivery schedule 561, as checked for conformance by an HRD, such as HRD 500. 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 operate on a bitstream including multi-layer video sequences 600 and / or 700.

[0191] Method 1100 may begin when a decoder begins receiving a bitstream of coded data representing a multi-layer video sequence, for example, as a result of method 1000. In step 1101, the decoder may receive the bitstream. The bitstream includes a syntax structure for HRD parameters. The syntax structure for HRD parameters is a data object that includes one or more HRD parameters that may be included in syntax elements within the syntax structure. The bitstream may also include one or more layers of the coded image, such as layer N 631, layer N+1 632, sublayer 710, sublayer 720, and / or sublayer 730. In some examples, the multiple layers are organized into one or more OLSs, such as OLS 625. The HRD parameters specify that all of the multiple layers are associated with the same number of CPB delivery schedules. The CPB delivery schedule may be associated with a set of bitstream conformance tests to be performed by an HRD running on the encoder. The HRD parameters may be included in a VPS that specifies the OLSs. In one example, the number of CPB delivery schedules is specified with the HRD CPB count - 1 (hrd_cpb_cnt_minus1) syntax element. minus1 indicates that the value of hrd_cpb_cnt_minus1 is 1 less than the indicated value and that +1 should be added to obtain a true value. hrd_cpb_cnt_minus1 may range from 0 to 31, inclusive. This indicates that 1 to 32 CPB delivery schedules may be specified and that all layers are associated with the same number of CPB delivery schedules.

[0192] In some examples, each corresponding CPB delivery schedule of a target OLS can be referenced by a unique schedule index (ScIdx). ScIdx can include values ​​ranging from 0 to the value of hrd_cpb_cnt_minus1, inclusive. This indicates that ScIdx can vary from a value of 0 for the first CPB delivery schedule to a value of hrd_cpb_cnt_minus1 for the last CPB delivery schedule. In some examples, each CPB delivery schedule is described by a pair of an initial CPB removal delay and an initial CPB removal offset. The initial CPB removal delay (nal_initial_cpb_removal_delay) is the default removal delay used when removing data units from the CPB of an HRD when checking pictures, AUs, and / or DUs in the bitstream, OLS, and / or layer. The initial CPB removal offset (nal_initial_cpb_removal_offset) is the default CPB removal offset associated with each picture, AU, and / or DU in the bitstream, OLS, and / or layer. Each layer may also be associated with a BP CPB count-1 (bp_cpb_cnt_minus1)+1 syntax element. BP CPB count-1 is a syntax element that specifies the number of pairs of initial CPB removal delay and initial CPB removal offset, and therefore the number of delivery schedules available for each layer / sublayer. The value of bp_cpb_cnt_minus1 may be set equal to the value of hrd_cpb_cnt_minus1. This ensures that the number of delivery schedules for each layer is the same as the total number of CPB delivery schedules. Thus, all layers have the same number of CPB delivery schedules. Syntax elements describing the CPB delivery schedules may be included in an SEI message. For example, nal_initial_cpb_removal_delay, nal_initial_cpb_removal_offset, and bp_cpb_cnt_minus1 may be included in a BP SEI message.

[0193] In step 1103, the decoder may decode the image / coded image from one of the layers and / or the OLS to obtain a decoded image. The decoder may also forward the decoded image for display as part of the decoded video sequence in step 1105.

[0194] 12 is a schematic diagram of an example system 1200 for coding a video sequence using a bitstream in which all layers in the bitstream have the same number of CPB delivery schedules, such as CPB delivery schedule 561. System 1200 may be implemented by an encoder and decoder, such as codec system 200, encoder 300, decoder 400, and / or video coding device 900. Furthermore, system 1200 can employ HRD 500 to perform conformance testing on multi-layer video sequence 600, multi-layer video sequence 700, and / or bitstream 800. In addition, system 1200 may be employed in implementing methods 100, 1000, and / or 1100.

[0195] The system 1200 includes a video encoder 1202. The video encoder 1202 comprises an encoding module 1203 for encoding a bitstream including one or more layers of coded pictures. The encoding module 1203 is further for encoding into the bitstream a syntax structure of HRD parameters specifying that all of the multiple layers are associated with the same number of coded picture buffer (CPB) delivery schedules. The video encoder 1202 further comprises an HRD module 1205 for performing a set of bitstream conformance tests on the multiple layers based on the CPB delivery schedule. The video encoder 1202 further comprises a storage module 1206 for storing the bitstream for communication toward a decoder. The video encoder 1202 further comprises a transmission module 1207 for transmitting the bitstream toward a video decoder 1210. The video encoder 1202 may be further configured to perform any of the steps of the method 1000.

[0196] System 1200 also includes a video decoder 1210. The video decoder 1210 comprises a receiving module 1211 for receiving a bitstream comprising the syntax structure of the HRD parameters and one or more layers of the coded image, such that all of the layers are associated with the same number of CPB delivery schedules as specified by the syntax structure of the HRD parameters. The video decoder 1210 further comprises a decoding module 1213 for decoding an image from one of the layers to obtain a decoded image. The video decoder 1210 further comprises a forwarding module 1215 for forwarding the decoded image for display as part of a decoded video sequence. The video decoder 1210 may be further configured to perform any of the steps of method 1100.

[0197] A first component is directly coupled to a second component when there are no intervening components, other than lines, traces, 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 lines, traces, or another medium, between the first and second components. The term "coupled" and variations thereof include both directly coupled and indirectly coupled. The use of the term "about," unless otherwise specified, means a range that includes ±10% of the succeeding number.

[0198] 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 the 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.

[0199] While several embodiments are provided in this disclosure, it will be understood that the disclosed systems and methods may 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 provided herein. For example, various elements or components may be combined or integrated in another system, or certain features may be omitted or not implemented.

[0200] Additionally, the techniques, systems, subsystems, and methods described and illustrated in various embodiments as 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 modifications, substitutions, and alterations may be ascertainable by those skilled in the art and may be made without departing from the spirit and scope disclosed herein. Other possible claims (Item 1) A method implemented by a decoder, comprising: receiving, by a receiver of the decoder, a bitstream comprising a syntax structure of hypothetical reference decoder (HRD) parameters and one or more layers of a coded picture, such that all of the plurality of layers are associated with as many coded picture buffer (CPB) delivery schedules as specified by the syntax structure of the HRD parameters; decoding, by a processor of the decoder, an image from one of the plurality of layers to obtain a decoded image; A method comprising: (Item 2) Item 14. The method of item 1, wherein the CPB delivery schedule is associated with a set of bitstream conformance tests performed by an HRD running on an encoder. (Item 3) 3. The method of claim 1 or 2, wherein the number of CPB delivery schedules is specified by the HRD CPB count minus 1 (hrd_cpb_cnt_minus1), where hrd_cpb_cnt_minus1 is in the range of 0 to 31, inclusive. (Item 4) 4. The method of any one of items 1 to 3, wherein the plurality of layers are organized into one or more output layer sets (OLS), and the corresponding CPB delivery schedule of the target OLS is referenced by a schedule index (ScIdx) ranging from 0 to the value of hrd_cpb_cnt_minus1, inclusive. (Item 5) 5. The method of any one of items 1 to 4, wherein each of the CPB delivery schedules is described by a Network Abstraction Layer (NAL) initial CPB removal delay (nal_initial_cpb_removal_delay) and a NAL initial CPB removal offset (nal_initial_cpb_removal_offset). (Item 6) 6. A method according to any one of items 1 to 5, wherein each layer is associated with a buffering period (BP) CPB count -1 (bp_cpb_cnt_minus1) + 1, which specifies the number of pairs of nal_initial_cpb_removal_delay and nal_initial_cpb_removal_offset for said each layer, where bp_cpb_cnt_minus1 is equal to the value of hrd_cpb_cnt_minus1. (Item 7) 7. The method of any one of items 1 to 6, wherein the HRD parameters are included in the bitstream in a video parameter set (VPS) that specifies the plurality of OLSs. (Item 8) 1. A method implemented by an encoder, comprising: encoding, by a processor of the encoder, a bitstream comprising one or more layers of a coded image; encoding, by the processor, a hypothetical reference decoder (HRD) parameter syntax structure into the bitstream that specifies that all of the plurality of layers are associated with the same number of coded picture buffer (CPB) delivery schedules; performing, by the processor, a set of bitstream conformance tests on the plurality of layers based on the CPB delivery schedule; A method comprising: (Item 9) Item 9. The method of item 8, wherein the set of bitstream conformance tests is performed by an HRD running on the processor. (Item 10) 10. The method of claim 8 or 9, wherein the number of CPB delivery schedules is specified by the HRD CPB count minus 1 (hrd_cpb_cnt_minus1), where hrd_cpb_cnt_minus1 is in the range of 0 to 31, inclusive. (Item 11) 11. The method of any one of items 8 to 10, wherein the plurality of layers are organized into one or more output layer sets (OLS), and the corresponding CPB delivery schedule of the target OLS is referenced by a schedule index (ScIdx) ranging from 0 to the value of hrd_cpb_cnt_minus1, inclusive. (Item 12) 12. The method of any one of items 8 to 11, wherein each of the CPB delivery schedules is described by a Network Abstraction Layer (NAL) initial CPB removal delay (nal_initial_cpb_removal_delay) and a NAL initial CPB removal offset (nal_initial_cpb_removal_offset). (Item 13) 13. A method according to any one of items 8 to 12, wherein each layer is associated with a buffering period (BP) CPB count -1 (bp_cpb_cnt_minus1) +1, which specifies the number of pairs of nal_initial_cpb_removal_delay and nal_initial_cpb_removal_offset for each layer, where bp_cpb_cnt_minus1 is equal to the value of hrd_cpb_cnt_minus1. (Item 14) 14. The method of any one of items 8 to 13, wherein a syntax structure of the HRD parameters is encoded into the bitstream in a video parameter set (VPS) that specifies the plurality of OLSs. (Item 15) 1. 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 one of items 1 to 14. Video coding device. (Item 16) 15. A non-transitory computer-readable medium comprising a computer program product for use by a video coding device, the non-transitory computer-readable medium comprising computer-executable instructions stored on the non-transitory computer-readable medium, the computer program product, when executed by a processor, causing the video coding device to perform the method of any one of items 1 to 14. (Item 17) A decoder comprising: receiving means for receiving a bitstream comprising a syntax structure of hypothetical reference decoder (HRD) parameters and one or more layers of a coded picture, such that all of the plurality of layers are associated with as many coded picture buffer (CPB) delivery schedules as specified by the syntax structure of the HRD parameters; decoding means for decoding an image from one of the plurality of layers to obtain a decoded image; transferring means for transferring the decoded image for display as part of a decoded video sequence; A decoder comprising: (Item 18) Item 18. The decoder of item 17, wherein the decoder is further configured to perform the method of any one of items 1 to 7. (Item 19) 1. An encoder comprising: encoding a bitstream comprising one or more layers of a coded image; encoding into the bitstream a syntax structure of hypothetical reference decoder (HRD) parameters that specifies that all of the plurality of layers are associated with the same number of coded picture buffer (CPB) delivery schedules; and encoding means for HRD means for performing a set of bitstream conformance tests on the plurality of layers based on the CPB delivery schedule; storage means for storing said bitstream for communication to a decoder; An encoder comprising: (Item 20) 20. The encoder of claim 19, further configured to perform the method of any one of claims 8 to 14.

Claims

1. A method implemented by a decoder, comprising: receiving a coded video bitstream having one or more output layer sets (OLS), a video parameter set (VPS), a syntax structure of hypothetical reference decoder (HRD) parameters, and a plurality of layers of coded pictures, wherein the VPS includes a first syntax element, a total number of the one or more OLSs is obtained based on the first syntax element, all of the plurality of layers are associated with the same number of coded picture buffer (CPB) delivery schedules, and the syntax structure of the HRD parameters includes a second syntax element specifying the same number; decoding an image from one of the plurality of layers to obtain a decoded image; A method comprising:

2. The method of claim 1 , wherein the CPB delivery schedule is associated with a set of bitstream conformance tests performed by an HRD running on an encoder.

3. A method as claimed in claim 1 or 2, wherein the second syntax element is specified as HRD CPB count - 1 (hrd_cpb_cnt_minus1), the multiple layers are organised into the one or more OLSs, and the corresponding CPB delivery schedule of the target OLS is referenced by a schedule index (ScIdx) ranging from 0 to the value of hrd_cpb_cnt_minus1, inclusive.

4. 4. The method of claim 1, wherein each of the CPB delivery schedules is described by a Network Abstraction Layer (NAL) initial CPB removal delay (nal_initial_cpb_removal_delay) and a NAL initial CPB removal offset (nal_initial_cpb_removal_offset).

5. A method according to claim 1, wherein the second syntax element is specified as HRD CPB count - 1 (hrd_cpb_cnt_minus1), and each layer is associated with a buffering period (BP) CPB count - 1 (bp_cpb_cnt_minus1) + 1 that specifies the number of pairs of nal_initial_cpb_removal_delay and nal_initial_cpb_removal_offset for each layer, and bp_cpb_cnt_minus1 is equal to the value of hrd_cpb_cnt_minus1.

6. The method of claim 1 , wherein the HRD parameters are included in the VPS.

7. 1. A method implemented by an encoder, comprising: encoding a video bitstream including multiple layers of coded images; encoding one or more output layer sets (OLS), a video parameter set (VPS), and a syntax structure of hypothetical reference decoder (HRD) parameters into the video bitstream, wherein the VPS includes a first syntax element, a total number of the one or more OLSs is obtained based on the first syntax element, all of the plurality of layers are associated with the same number of coded picture buffer (CPB) delivery schedules, and the syntax structure of the HRD parameters includes a second syntax element that specifies the same number; A method comprising:

8. 8. The method of claim 7, wherein a set of bitstream conformance tests is performed on the plurality of layers based on the CPB delivery schedule, the set of bitstream conformance tests being performed by an HRD running on a processor of the encoder.

9. The method of claim 7 or 8, wherein the second syntax element is specified as HRD CPB count-1 (hrd_cpb_cnt_minus1), the multiple layers are organized into the one or more OLSs, and the corresponding CPB delivery schedule of the target OLS is referenced by a schedule index (ScIdx) ranging from 0 to the value of hrd_cpb_cnt_minus1, inclusive.

10. 10. The method of claim 7, wherein each of the CPB delivery schedules is described by a Network Abstraction Layer (NAL) initial CPB removal delay (nal_initial_cpb_removal_delay) and a NAL initial CPB removal offset (nal_initial_cpb_removal_offset).

11. A method according to any one of claims 7 to 10, wherein the second syntax element is specified as HRD CPB count - 1 (hrd_cpb_cnt_minus1), and each layer is associated with a buffering period (BP) CPB count - 1 (bp_cpb_cnt_minus1) + 1 that specifies the number of pairs of nal_initial_cpb_removal_delay and nal_initial_cpb_removal_offset for each layer, where bp_cpb_cnt_minus1 is equal to the value of hrd_cpb_cnt_minus1.

12. The method according to claim 7 , wherein the syntax structure of the HRD parameters is encoded into the VPS.

13. A system 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 6. decoder.

14. 13. A system 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 7 to 12. Encoder.

15. A computer program product for causing a processor to carry out the method of any one of claims 1 to 12.

16. A decoder comprising: a receiving means for receiving a coded video bitstream having one or more output layer sets (OLSs), a video parameter set (VPS) specifying the OLSs, a syntax structure of hypothetical reference decoder (HRD) parameters, and a plurality of layers of coded pictures, wherein the VPS includes a first syntax element, a total number of the one or more OLSs is obtained based on the first syntax element, all of the plurality of layers are associated with the same number of coded picture buffer (CPB) delivery schedules, and the syntax structure of the HRD parameters includes a second syntax element specifying the same number; decoding means for decoding an image from one of the plurality of layers to obtain a decoded image; transferring means for transferring said decoded images for display as part of a decoded video sequence; A decoder comprising:

17. 17. The decoder of claim 16, wherein the decoder is further configured to perform the method of any one of claims 1 to 6.

18. 1. An encoder comprising: encoding a video bitstream having multiple layers of coded images; encoding one or more output layer sets (OLS), a video parameter set (VPS) specifying the OLS, and a syntax structure of hypothetical reference decoder (HRD) parameters into the video bitstream; wherein the VPS includes a first syntax element, a total number of the one or more OLSs is obtained based on the first syntax element, all of the plurality of layers are associated with the same number of coded picture buffer (CPB) delivery schedules, and a syntax structure of the HRD parameters includes a second syntax element that specifies the same number; storage means for storing said video bitstream for communication to a decoder; An encoder comprising:

19. 19. The encoder of claim 18, wherein the encoder is further configured to perform the method of any one of claims 7 to 12.

20. A non-transitory computer-readable storage medium storing program code that, when executed by a computing device, causes the computing device to perform the method of any one of claims 1 to 6 or any one of claims 7 to 12.

21. a transceiver unit, a processor, a memory, Equipped with The transceiver unit is configured to communicate a video bitstream over a network, the memory is configured to store the video bitstream, the video bitstream having one or more output layer sets (OLS), a video parameter set (VPS), a syntax structure of hypothetical reference decoder (HRD) parameters, and a plurality of layers of a coded image, the VPS including a first syntax element, a total number of the one or more OLSs is obtained based on the first syntax element, and a total number of all of the plurality of layers is obtained based on the first syntax element. and a processor for parsing the video bitstream to obtain the one or more OLSs, the VPSs, the syntax structure of the HRD parameters, and the plurality of layers of the coded image, and for decoding an image from one of the plurality of layers based on the syntax structure of the one or more OLSs, the VPSs, and the HRD parameters to obtain a decoded image.

Images