Apparatus and method for signaling picture count information for decoding video pictures

By sending and decoding the image order counting information in video encoding technology, the information transmission problems in video data redundancy and encoding standard extensions are solved, and the performance and encoding efficiency of the video distribution system are improved.

CN112970265BActive Publication Date: 2024-11-08SHARP KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980056240.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2018-10-29
Filing Date
2019-06-28
Publication Date
2024-11-08
Estimated Expiration
2039-06-28

AI Technical Summary

Technical Problem

Existing video encoding technologies have data redundancy when transmitting and storing video data, resulting in increased bandwidth and storage requirements. In the expansion and improvement of video encoding standards such as ITU-T H.264 and HEVC, there is a lack of effective methods to Send and decode the order count information of the picture, affecting the performance of the video distribution system.

Method used

The method of signaling the picture order counting information includes specifying the value of the most significant bit period element using the picture order counting the most significant bit existence mark and the POC MSB first mark, and using the maximum picture order counting when decoding The lowest significant bit subtracts the four elements to set the maximum value of the most significant bit period element in the picture order counting, and optimizes the encoding and decoding process of video data.

Benefits of technology

It reduces transmission bandwidth, improves the parallelism of video encoder and decoder, improves the performance of video distribution systems, and is suitable for future video encoding standards and different video encoding systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112970265B_ABST
    Figure CN112970265B_ABST
Patent Text Reader

Abstract

Provided is a method and device for sending a signal to notify picture count information for decoding a plurality of video pictures. The method comprises: sending a picture order count POC most significant bit MSB first flag, the POC MSB first flag indicating the presence of a POC MSB second flag, wherein the POC MSB first flag is present in a sequence parameter set SPS; when the value of the POC MSB first flag present in the SPS is true, additionally sending a maximum POC MSB period minus one element specifying the length of the POC MSB period element; directly sending a first POC LSB value without additional conditions for the first POC least significant bit LSB value, wherein the length of the first POC LSB value is set based on the maximum POC LSB minus four log2_max_pic_order_cnt_lsb_minus4 value; sending the POC MSB second flag to indicate whether the POC MSB period element is present; and when the value of the POC MSB second flag is true, sending the POC MSB period element specifying the value of the POC MSB period.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to video coding, and more particularly, to techniques for signaling picture order count values ​​in encoded video. Background Art

[0002] Digital video capabilities can be incorporated into various devices, including digital televisions, laptop or desktop computers, tablet computers, digital recording devices, digital media players, video game devices, cellular phones (including so-called smart phones), medical imaging devices, etc. Digital video can be encoded according to a video coding standard. Video coding standards can be combined with video compression technology. Examples of video coding standards include ISO / IEC MPEG-4Visual and ITU-T H.264 (also known as ISO / IEC MPEG-4AVC) and High Efficiency Video Coding (HEVC). HEVC is described in High Efficiency Video Coding (HEVC) of the ITU-T H.265 Recommendation in December 2016, which is incorporated herein by reference and is referred to as ITU-TH.265 in this article. ITU-T H.265 is currently being considered for expansion and improvement to develop the next generation of video coding standards. For example, the ITU-T Video Coding Experts Group (VCEG) and the ISO / IEC Moving Picture Experts Group (MPEG) (collectively referred to as the Joint Video Study Group (JVET)) are studying the potential need for standardization of future video coding technologies with compression capabilities significantly exceeding the current HEVC standard. The Joint Exploration Model 7 (JEM 7), algorithm description of the Joint Exploration Test Model 7 (JEM 7), ISO / IEC JTC1 / SC29 / WG11 document: JVET-G1001 (July 2017, Turin, Italy), which is incorporated herein by reference, describes the coding features under the Joint Test Model study by JVET, which is a potential enhanced video coding technology beyond the capabilities of ITU-T H.265. It should be noted that the coding features of JEM 7 are implemented in the JEM reference software. As used herein, the term JEM may refer collectively to the algorithms included in JEM 7 and the specific implementation of the JEM reference software. In addition, in response to the "Joint Call for Proposals on Video Compression with Capabilities beyond HEVC" jointly issued by VCEG and MPEG, various groups proposed and responded to a variety of video coding descriptions at the 10th meeting of ISO / IEC JTC1 / SC29 / WG11 in San Diego, California from April 16 to 20, 2018. As a result of the description of multiple video coding, a draft text of a video coding specification is described in "Generic Video Coding (Draft 1)", document JVET-J1001-v2, of the 10th meeting of ISO / IEC JTC1 / SC29 / WG11, San Diego, California, April 16-20, 2018, which is incorporated herein by reference and is referred to as JVET-J1001.

[0003] Video compression techniques reduce the data requirements for storing and transmitting video data by exploiting the inherent redundancy in video sequences. Video compression techniques can subdivide video sequences into successively smaller parts (i.e., groups of frames within a video sequence, frames within a group of frames, segments within a frame, coding tree units (e.g., macroblocks) within a segment, coding blocks within a coding tree unit, etc.). Intra-frame prediction coding techniques (e.g., within a picture (space)) and inter-frame prediction techniques (i.e., between pictures (time)) can be used to generate the difference between the video data unit to be encoded and the reference unit of the video data. The difference may be referred to as residual data. The residual data may be encoded as quantized transform coefficients. Syntax elements may involve residual data and reference coding units (e.g., intra-frame prediction mode indexes, motion vectors, and block vectors). The residual data and syntax elements may be entropy encoded. Entropy-encoded residual data and syntax elements may be included in a compatible bitstream. The compatible bitstream and associated metadata may be formatted according to a data structure. Summary of the invention

[0004] In one example, a method for signaling picture count information is provided, the method comprising:

[0005] A picture order count most significant bit existence flag is sent, wherein the picture order count most significant bit existence flag indicates whether there is a picture order count most significant bit period element; and when the value of the picture order count most significant bit existence flag is equal to one, the picture order count most significant bit period element is sent to specify the value of the picture order count most significant bit period, wherein the maximum value of the picture order count most significant bit period element is set by using the maximum picture order count least significant bit minus four elements.

[0006] In one example, a method for decoding video data includes: decoding a picture order count most significant bit existence flag, the picture order count most significant bit existence flag indicating whether there is a picture order count most significant bit period element; and when the value of the picture order count most significant bit existence flag is equal to one, decoding the picture order count most significant bit period element for specifying the value of the picture order count most significant bit period, wherein the maximum value of the picture order count most significant bit period element is set by using the maximum picture order count least significant bit minus four elements.

[0007] In one example, a method for sending a signal to notify picture count information for decoding multiple video pictures is provided, the method comprising: sending a picture order count POC most significant bit MSB first flag, the POC MSB first flag indicating the presence of a POC MSB second flag, wherein the POC MSB first flag is present in a sequence parameter set SPS; when the value of the POC MSB first flag present in the SPS is true, additionally sending a maximum POC MSB period minus one element specifying the length of the POC MSB period element; directly sending a first POC LSB value without additional conditions for the first POC least significant bit LSB value, wherein the length of the first POC LSB value is set based on the maximum POC LSB minus four log2_max_pic_order_cnt_lsb_minus4 value; sending the POC MSB second flag to indicate whether the POC MSB period element is present; and when the value of the POC MSB second flag is true, sending the POC MSB period element specifying the value of the POC MSB period.

[0008] In one example, a device for sending a signal to notify picture count information for decoding a video picture is provided, the device comprising: at least one processor; and a storage device, which is coupled to the at least one processor and stores a plurality of indications, and when the plurality of indications are executed by the at least one processor, the at least one processor is caused to: send a picture order count POC most significant bit MSB first flag, the POC MSB first flag indicating the presence of a POC MSB second flag, wherein the POC MSB first flag is present in a sequence parameter set SPS; when the value of the POC MSB first flag present in the SPS is true, additionally send a maximum POC MSB period minus one element specifying the length of the POC MSB period element; directly send a first POC LSB value without additional conditions for a first POC least significant bit LSB value, wherein the length of the first POC LSB value is set based on the maximum POC LSB minus four log2_max_pic_order_cnt_lsb_minus4 value; send the POC MSB second flag to indicate whether the POC MSB period element exists; and when the value of the POC MSB second flag is true, send a maximum POC MSB period minus one element specifying the length of the POC MSB period element. The MSB period value of the POC MSB period element. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 is a block diagram illustrating an example of a system that may be configured to encode and decode video data in accordance with one or more techniques of this disclosure.

[0010] Figure 2 is a conceptual diagram illustrating encoded video data and corresponding data structures in accordance with one or more techniques of this disclosure.

[0011] Figure 3 is a conceptual diagram illustrating a data structure that encapsulates encoded video data and corresponding metadata in accordance with one or more techniques of this disclosure.

[0012] Figure 4 is a conceptual diagram illustrating an example of components that may be included in an implementation of a system that may be configured to encode and decode video data in accordance with one or more techniques of this disclosure.

[0013] Figure 5 is a block diagram illustrating an example of a video encoder that may be configured to encode video data in accordance with one or more techniques of this disclosure.

[0014] Figure 6 is a block diagram illustrating an example of a video decoder that may be configured to decode video data in accordance with one or more techniques of this disclosure. DETAILED DESCRIPTION

[0015] Generally speaking, the present disclosure describes various techniques for encoding video data. Specifically, the present disclosure describes techniques for signaling the type of pictures of encoded videos. Signaling the type of pictures according to the techniques described herein may be particularly useful for improving the performance of video distribution systems by reducing transmission bandwidth and / or promoting the parallelization of video encoders and / or decoders. It should be noted that although the techniques of the present disclosure are described with respect to ITU-T H.264, ITU-T H.265, and JVET-J1001, the techniques of the present disclosure may be generally applicable to video coding. For example, the coding techniques described herein may be incorporated into video coding systems (including video coding systems based on future video coding standards), including block structures, intra-frame prediction techniques, inter-frame prediction techniques, transform techniques, filtering techniques, and / or entropy coding techniques, which are different from those included in ITU-T H.265. Therefore, references to ITU-T H.264, ITU-T H.265, and / or JVET-J1001 are for descriptive purposes and should not be interpreted as limiting the scope of the techniques described herein. In addition, it should be noted that the incorporation of documents by reference herein should not be interpreted as limiting or creating ambiguity regarding the terms used herein. For example, in the event that a definition of a term provided in an incorporated reference differs from that provided in another incorporated reference and / or as used herein, the term should be interpreted in a manner that broadly includes each corresponding definition and / or in a manner that includes each specific definition in alternatives.

[0016] In one example, a method for signaling picture count information includes: determining a most significant bit period value for a picture order count; signaling a flag in a parameter set indicating that a syntax indicating a most significant bit period value for a picture order count is present in a segment header; and signaling a value of a syntax element in a segment header indicating a most significant bit period value for a picture order count.

[0017] In one example, a device includes one or more processors configured to: determine a most significant bit period value for a picture order count; signal a flag in a parameter set indicating that syntax indicating a most significant bit period value for a picture order count is present in a segment header; and signal a value of a syntax element in the segment header indicating a most significant bit period value for a picture order count.

[0018] In one example, a non-transitory computer-readable storage medium includes instructions stored thereon that, when executed, cause one or more processors of a device to: determine a picture order count most significant bit period value; signal a flag in a parameter set that indicates the presence of syntax in a segment header that indicates a picture order count most significant bit period value; and signal a value of a syntax element in a segment header that indicates a picture order count most significant bit period value.

[0019] In one example, an apparatus includes: a device for determining a most significant bit period value for a picture order count; a device for signaling a flag in a parameter set, the flag indicating the presence of syntax in a segment header indicating a most significant bit period value for a picture order count; and a device for signaling a value of a syntax element in a segment header indicating a most significant bit period value for a picture order count.

[0020] In one example, a method for decoding video data includes: parsing a tag in a parameter set, the tag indicating that a syntax indicating a most significant bit period value of a picture order count is present in a segment header; conditionally parsing a value of a syntax element indicating a most significant bit period value of a picture order count in a segment header based on the value of the tag in the parameter set; and determining a most significant bit period value of a picture order count.

[0021] In one example, a device includes one or more processors configured to: parse a flag in a parameter set, the flag indicating that a syntax indicating a most significant bit period value of a picture order count is present in a segment header; conditionally parse a value of a syntax element in a segment header indicating a most significant bit period value of a picture order count based on the value of the flag in the parameter set; and determine a most significant bit period value of a picture order count.

[0022] In one example, a non-transitory computer-readable storage medium includes instructions stored thereon that, when executed, cause one or more processors of a device to: parse a flag in a parameter set, the flag indicating the presence of syntax in a segment header that indicates a most significant bit period value for a picture order count; conditionally parse a value of a syntax element in a segment header that indicates a most significant bit period value for a picture order count based on the value of the flag in the parameter set; and determine a most significant bit period value for a picture order count.

[0023] In one example, a device includes: a device for parsing a flag in a parameter set, the flag indicating the presence of syntax in a segment header indicating a most significant bit period value for a picture order count; a device for conditionally parsing a value of a syntax element in a segment header indicating a most significant bit period value for a picture order count based on the value of the flag in the parameter set; and a device for determining a most significant bit period value for a picture order count.

[0024] The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims.

[0025] Video content typically includes a video sequence consisting of a series of frames. A series of frames may also be referred to as a group of pictures (GOP). Each video frame or picture may include one or more segments, wherein a segment includes multiple video blocks. A video block includes an array of pixel values ​​(also referred to as samples) that can be predictively encoded. Video blocks may be sorted according to a scanning mode (e.g., raster scanning). The video encoder performs predictive coding on video blocks and their sub-partitions. ITU-T H.264 specifies a macroblock including 16×16 luminance samples. ITU-T H.265 specifies a similar coding tree unit (CTU) structure (which may be referred to as a maximum coding unit (LCU)), wherein a picture may be partitioned into CTUs of the same size, and each CTU may include a coding tree block (CTB) having 16×16, 32×32, or 64×64 luminance samples. As used herein, the term "video block" may generally refer to an area of ​​a picture, or may more specifically refer to a maximum array of pixel values ​​that may be predictively encoded, its sub-partitions, and / or corresponding structures. Furthermore, according to ITU-T H.265, each video frame or picture may be partitioned to include one or more tiles, where a tile is a sequence of coding tree units corresponding to a rectangular region of a picture.

[0026] In ITU-T H.265, a CTU consists of a corresponding CTB for each component of the video data, for example, luma (Y) and chroma (Cb and Cr). In addition, in ITU-T H.265, a CTU can be partitioned according to a quadtree (QT) partitioning structure, which allows the CTB of a CTU to be partitioned into coding blocks (CBs). That is, in ITU-T H.265, a CTU can be partitioned into quadtree leaf nodes. According to ITU-T H.265, a luma CB together with two corresponding chroma CBs and associated syntax elements is referred to as a coding unit (CU). In ITU-T H.265, a signal may be sent to notify the minimum allowed size of a CB. In ITU-T H.265, the minimum allowed minimum size of a luma CB is 8×8 luma samples. In ITU-T H.265, the decision to encode a picture area using intra prediction or inter prediction is made at the CU level.

[0027] In ITU-T H.265, a CU is associated with a prediction unit (PU) structure having its root at the CU. In ITU-T H.265, the PU structure allows the partitioning of luma CB and chroma CB to generate corresponding reference samples. That is, in ITU-T H.265, the luma CB and chroma CB can be partitioned into corresponding luma and chroma prediction blocks (PBs), where the PBs include blocks of sample values ​​to which the same prediction is applied. In ITU-T H.265, the CB can be divided into 1, 2, or 4 PBs. ITU-T H.265 supports PB sizes from 64×64 samples down to 4×4 samples. In ITU-T H.265, square PBs are supported for intra prediction, where the CBs can form a PB, or the CBs can be partitioned into four square PBs (i.e., the intra prediction PB size types include M×M or M / 2×M / 2, where M is the height and width of the square CB). In ITU-T H.265, in addition to square PBs, rectangular PBs are also supported for inter prediction, where the CB can be halved vertically or horizontally to form a PB (i.e., inter prediction PB types include M×M, M / 2×M / 2, M / 2×M, or M×M / 2). In addition, it should be noted that in ITU-T H.265, for inter prediction, four asymmetric PB partitions are supported, where the CB is divided into two PBs at one quarter of the height (top or bottom) or width (left or right) of the CB (i.e., asymmetric partitions include M / 4×M left, M / 4×M right, M×M / 4 top, and M×M / 4 bottom). Intra prediction data (e.g., intra prediction mode syntax elements) or inter prediction data (e.g., motion data syntax elements) corresponding to the PB are used to generate reference and / or prediction sample values ​​for the PB.

[0028] JEM specifies a CTU with a maximum size of 256×256 luma samples. JEM specifies a quadtree plus binary tree (QTBT) block structure. In JEM, the QTBT structure allows the quadtree leaf nodes to be further divided by the binary tree (BT) structure. That is, in JEM, the binary tree structure allows the quadtree leaf nodes to be recursively divided vertically or horizontally. Therefore, the binary tree structure in JEM implements square and rectangular leaf nodes, each of which includes a CB. Figure 2 As shown, a picture included in a GOP may include segments, each of which includes a CTU sequence, and each CTU may be divided according to a QTBT structure. In JEM, CBs are used for prediction without any further division. That is, in JEM, CBs may be blocks of sample values ​​to which the same prediction is applied. Therefore, a JEM QTBT leaf node may be similar to a PB in ITU-T H.265.

[0029] Intra-prediction data (e.g., intra-prediction mode syntax elements) or inter-prediction data (e.g., motion data syntax elements) may associate the PU with corresponding reference samples. The residual data may include a corresponding difference value array corresponding to each component of the video data (e.g., luma (Y) and chroma (Cb and Cr)). The residual data may be in the pixel domain. A transform such as a discrete cosine transform (DCT), a discrete sine transform (DST), an integer transform, a wavelet transform, or a conceptually similar transform may be applied to the pixel difference values ​​to generate transform coefficients. It should be noted that in ITU-T H.265, a CU may be further subdivided into transform units (TUs). That is, in order to generate transform coefficients, the array of pixel difference values ​​may be subdivided (e.g., four 8×8 transforms may be applied to a 16×16 array of residual values ​​corresponding to a 16×16 luma CB), and such sub-partitions may be referred to as transform blocks (TBs). The transform coefficients may be quantized according to a quantization parameter (QP). The quantized transform coefficients (which may be referred to as level values) may be entropy encoded according to an entropy coding technique (e.g., content adaptive variable length coding (CAVLC), context adaptive binary arithmetic coding (CABAC), probability interval partitioning entropy coding (PIPE), etc.). In addition, syntax elements (such as syntax elements indicating a prediction mode) may also be entropy encoded. The entropy-encoded quantized transform coefficients and the corresponding entropy-encoded syntax elements may form a compatible bitstream that may be used to reproduce video data. Binarization may be performed on the syntax elements as part of the entropy coding process. Binarization refers to the process of converting syntax values ​​into a sequence of one or more bits. These bits may be referred to as "bins".

[0030] As described above, intra prediction data or inter prediction data is used to generate reference sample values ​​of a block of sample values. The difference between the sample values ​​included in the current PB or another type of picture area structure and the associated reference samples (e.g., those generated using prediction) can be referred to as residual data. As described above, intra prediction data or inter prediction data can associate a region of a picture (e.g., PB or CB) with a corresponding reference sample. For intra prediction coding, an intra prediction mode may specify the position of a reference sample within a picture. In ITU-T H.265, the possible intra prediction modes defined include a plane (i.e., surface fitting) prediction mode (predMode:0), a DC (i.e., flat overall average) prediction mode (predMode:1), and 33 angle prediction modes (predMode:2-34). In JEM, the possible intra prediction modes defined include a plane prediction mode (predMode:0), a DC prediction mode (predMode:1), and 65 angle prediction modes (predMode:2-66). It should be noted that planar prediction mode and DC prediction mode may be referred to as non-directional prediction modes, and angular prediction mode may be referred to as directional prediction mode.It should be noted that the techniques described herein may be generally applicable regardless of the number of possible prediction modes defined.

[0031] For inter-frame prediction coding, a motion vector (MV) identifies a reference sample in a picture other than the picture of the video block to be encoded, thereby exploiting temporal redundancy in the video. For example, the current video block can be predicted from one or more reference blocks located in one or more previously encoded frames, and a motion vector can be used to indicate the location of the reference block. The motion vector and associated data may describe, for example, the horizontal component of the motion vector, the vertical component of the motion vector, the resolution of the motion vector (e.g., quarter-pixel precision, half-pixel precision, one-pixel precision, two-pixel precision, four-pixel precision), the prediction direction, and / or the reference picture index value. In addition, coding standards such as ITU-T H.265 may support motion vector prediction. Motion vector prediction allows the motion vector to be specified to use the motion vectors of neighboring blocks. Examples of motion vector prediction include advanced motion vector prediction (AMVP), temporal motion vector prediction (TMVP), the so-called "merge" mode, and "skip" and "direct" motion inference. In addition, JEM supports advanced temporal motion vector prediction (ATMVP), spatio-temporal motion vector prediction (STMVP), pattern matching motion vector derivation (PMMVD) mode (which is a special merge mode based on frame rate up conversion (FRUC) technology) and affine transform motion compensated prediction.

[0032] The residual data may include a corresponding array of difference values ​​corresponding to each component of the video data. The residual data may be in the pixel domain. A transform such as a discrete cosine transform (DCT), a discrete sine transform (DST), an integer transform, a wavelet transform, or a conceptually similar transform may be applied to the difference array to generate transform coefficients. In ITU-T H.265, a CU is associated with a transform unit (TU) structure having its root at the CU level. That is, in ITU-T H.265, as described above, in order to generate transform coefficients, the array of difference values ​​may be subdivided (e.g., four 8×8 transforms may be applied to a 16×16 residual value array). It should be noted that in ITU-T H.265, TBs are not necessarily aligned with PBs.

[0033] It should be noted that in JEM, the residual values ​​corresponding to CB are used to generate transform coefficients without further partitioning. That is, in JEM, the QTBT leaf node can be similar to both PB and TB in ITU-T H.265. It should be noted that in JEM, a core transform and a subsequent secondary transform can be applied (in a video encoder) to generate transform coefficients. For a video decoder, the order of transforms is reversed. In addition, in JEM, whether a secondary transform is applied to generate transform coefficients may depend on the prediction mode.

[0034] A quantization process may be performed on the transform coefficients. Quantization approximates the transform coefficients by limiting the amplitude to a set of specified values. Quantization may be used to change the amount of data required to represent a set of transform coefficients. Quantization may be achieved by dividing the transform coefficients by a scaling factor and any associated rounding function (e.g., rounding to the nearest integer). The quantized transform coefficients may be referred to as coefficient level values. Inverse quantization (or "dequantization") may include multiplying the coefficient level values ​​by the scaling factor. It should be noted that, as used herein, the term quantization process may in some cases refer to dividing by a scaling factor to generate a level value, or in some cases may refer to multiplying by a scaling factor to recover the transform coefficients. That is, the quantization process may in some cases refer to quantization, and in some cases may refer to inverse quantization.

[0035] For the formulas used in this article, the following arithmetic operators can be used:

[0036] +Addition

[0037] - Subtraction

[0038] * Multiplication, including matrix multiplication

[0039] x y Exponentiation. Raises x to the power of y. In other contexts, such symbols are used for superscripts and are not intended to be interpreted as exponentiation.

[0040] / Integer division truncates the result towards zero. For example, 7 / 4 and -7 / -4 are truncated to 1, and -7 / 4 and 7 / -4 are truncated to -

[0041] 1.

[0042] ÷ is used to represent division in mathematical formulas when truncation or rounding is not intended.

[0043] Used to represent division in mathematical formulas without the intent to truncate or round.

[0044] Additionally, the following math functions are available:

[0045] Log2(x), logarithm of x to base 2;

[0046]

[0047] Ceil(x), the smallest integer greater than or equal to x.

[0048] With respect to the exemplary syntax used herein, the following definition of logical operators may be applied: x&&y Boolean logical "and" of x and y

[0049] x||y Boolean logical OR of x and y

[0050] ! Boolean logic "NO"

[0051] x? y:z If x is TRUE or not equal to 0, it evaluates to y; otherwise, it evaluates to z.

[0052] Additionally, the following relational operators can be applied:

[0053] > Greater than

[0054] >= greater than or equal to

[0055] < less than

[0056] <= less than or equal to

[0057] == is equal to

[0058] ! = Not equal to

[0059] Furthermore, it should be noted that among the syntax descriptors used in this document, the following descriptors may be applied:

[0060] -f(n): Use a fixed pattern bit string with n bits (from left to right) written left first. The parsing process of this descriptor is specified by the return value of the function read_bits(n).

[0061] u(n): an unsigned integer using n bits. When n is "v" in the syntax table, the number of bits varies in a manner that depends on the values ​​of other syntax elements. The parsing process of this descriptor is specified by the return value of the function read_bits(n), which is interpreted as the binary representation of the unsigned integer with the most significant bit written first.

[0062] ue(v): unsigned integer order 0 Exp-Golomb coded syntax element written left first.

[0063] i(n): A signed integer using n bits. When n is "v" in the syntax table, the number of bits varies in a manner that depends on the values ​​of other syntax elements. The parsing process of this descriptor is specified by the return value of the function read_bits(n), which is interpreted as a two's complement integer representation with the most significant bit written first.

[0064] As described above, according to ITU-T H.265, each video frame or picture may be partitioned to include one or more segments, and further partitioned to include one or more tiles. Figure 2 is a conceptual diagram showing an example of a picture group including a fragment. Figure 2 In the example shown, the image 4 is shown as comprising two segments (i.e., segment 1 and snippets 2 ), where each fragment comprises a sequence of CTUs (e.g., arranged in raster scan order). It should be noted that a fragment is a sequence of one or more fragment segments starting from an independent fragment segment and including all subsequent subordinate fragment segments (if any) before the next independent fragment segment (if any) within the same access unit. Fragment segments (such as fragments) are sequences of coding tree units. In the examples described herein, in some cases, the terms "fragment" and "fragment segment" are used interchangeably to indicate a sequence of coding tree units. It should be noted that in ITU-T H.265, a tile can be composed of coding tree units contained in more than one fragment, and a fragment can be composed of coding tree units contained in more than one tile. However, ITU-T H.265 specifies that one or both of the following conditions should be met: (1) all coding tree units in a fragment belong to the same tile; and (2) all coding tree units in a tile belong to the same fragment. Tile sets can be used to define boundaries for coding dependencies (e.g., intra-frame prediction dependencies, entropy coding dependencies, etc.), and thus parallelism can be enabled in encoding.

[0065] In ITU-T H.265, a coded video sequence (CVS) can be encapsulated (or structured) as a series of access units, each of which includes video data constructed as a network abstraction layer (NAL) unit. In ITU-T H.265, a bitstream is described as including a sequence of NAL units forming one or more CVSs. It should be noted that ITU-T H.265 supports multi-layer extensions, including format range extension (RExt), scalability (SHVC), multi-view (MV-HEVC) and 3-D (3D-HEVC). Multi-layer extensions enable video presentation to include a base layer and one or more additional enhancement layers. For example, a base layer can enable a video presentation with a basic quality level (e.g., high-definition presentation), and an enhancement layer can enable a video presentation with an enhanced quality level (e.g., ultra-high-definition rendering). In ITU-T H.265, an enhancement layer can be encoded by referring to a base layer. That is, for example, a picture in an enhancement layer can be encoded (e.g., using inter-frame prediction techniques) by referring to one or more pictures in the base layer (including a scaled version thereof). In ITU-T H.265, each NAL unit may include an identifier indicating the video data layer with which the NAL unit is associated. It should be noted that sub-bitstream extraction may refer to a process in which a device receiving a compatible bitstream forms a new compatible bitstream by discarding and / or modifying data in the received bitstream. For example, sub-bitstream extraction may be used to form a new compatible bitstream corresponding to a specific representation (e.g., a high-quality representation) of a video.

[0066] refer to Figure 2 The example shown in Pic 4 Each video data segment (i.e., Slice 1 and Slice 2) is shown as encapsulated in a NAL unit. In ITU-T H.265, each of a video sequence, GOP, picture, fragment, and CTU may be associated with metadata describing video coding attributes. ITU-T H.265 defines parameter sets that can be used to describe video data and / or video coding attributes. In ITU-T H.265, parameter sets may be encapsulated as a special type of NAL unit, or may be signaled as a message. A NAL unit including coded video data (e.g., a fragment) may be referred to as a VCL (video coding layer) NAL unit, and a NAL unit including metadata (e.g., a parameter set) may be referred to as a non-VCL NAL unit. In addition, ITU-T H.265 enables supplemental enhancement information (SEI) messages to be signaled. In ITU-T H.265, SEI messages assist processes related to decoding, display, or other purposes, however, SEI messages may not be required to construct luminance or chrominance samples through a decoding process. In ITU-T H.265, non-VCL NAL units may be used to signal SEI messages in a bitstream. Furthermore, SEI messages may be conveyed in a manner other than by being present in the bitstream (ie, signaled out-of-band).

[0067] Figure 3 An example of a bitstream including a plurality of CVSs is shown, wherein the CVSs are represented by NAL units included in corresponding access units. Figure 3In the example shown, the non-VCL NAL unit includes respective parameter set units (i.e., video parameter set (VPS), sequence parameter set (SPS), and picture parameter set (PPS) units) and access unit delimiter NAL units. ITU-T H.265 defines NAL unit header semantics, which specifies the type of raw byte sequence payload (RBSP) data structure included in the NAL unit. It should be noted that ITU-T H.265 provides various picture types defined based on decoding order and / or output order. In ITU-T H.265, an intra random access point (IRAP) picture is a picture that does not reference any picture other than itself used for inter-frame prediction during its decoding process, and the first picture in the decoding order in the bitstream must be an IRAP picture. It should be noted that in ITU-T H.265, there may be pictures in the bitstream that are not IRAP pictures and do not reference any pictures other than themselves used for inter-frame prediction during its decoding process. Examples of IRAP pictures include an Instantaneous Decoding Refresh (IDR) picture, which is a picture that does not reference any picture other than itself for inter-frame prediction during its decoding process, and may be the first picture in the decoding order in the bitstream, or may appear later in the bitstream. ITU-T H.265 provides a case where a leading picture is a picture that precedes the associated IRAP picture in the output order, and a trailing picture is a non-IRAP picture that follows the associated IRAP picture in the output order. It should be noted that the trailing picture associated with an IRAP picture is also after the IRAP picture in the decoding order, and pictures that follow the associated IRAP picture in the output order and precede the associated IRAP picture in the decoding order are not allowed.

[0068] ITU-T H.265 provides that each coded picture is associated with a picture order count variable, denoted as PicOrderCntVal. In ITU-T H.265, the picture order count is used to identify pictures, for deriving motion parameters in merge mode and motion vector prediction, and for decoder consistency checking. In ITU-T H.265, in a CVS, the PicOrderCntVal values ​​of all coded pictures are unique. In addition, in ITU-T H.265, the picture order count provides the relative output order of the pictures included in the CVS (i.e., from the decoded picture buffer, e.g., for display) (i.e., pictures with lower picture order counts are output first, and pictures with higher picture order counts are output later). In ITU-T H.265, the value of PicOrderCntVal is between -2 and 1. 31 to 2 31-1In ITU-T H.265, the sequence parameter set syntax includes the syntax element log2_max_pic_order_cnt_lsb_minus4, which specifies the value of the variable MaxPicOrderCntLsb used in the decoding process of the picture order count as follows:

[0069] MaxPicOrderCntLsb=2 (log2 _ max _ pic _ order _ cnt _ lsb _ minus4+4)

[0070] The value of log2_max_pic_order_cnt_lsb_minus4 should be in the range of 0 to 12 (including the end values).

[0071] ITU-T H.265 provides the case where PicOrderCntVal is equal to PicOrderCntMsb + slice_pic_order_cnt_lsb. slice_pic_order_cnt_lsb is derived as follows:

[0072] When the current picture is not an IRAP picture and is output, the variable prevPicOrderCntLsb is derived as follows:

[0073] - Let prevTid0Pic be the previous picture in decoding order with TemporalId equal to 0 and not a random access skipped preamble (RASL), random access decodable preamble (RADL), or sub-layer non-reference (SLNR) picture.

[0074] -The variable prevPicOrderCntLsb is set equal to slice_pic_order_cnt_lsb of prevTid0Pic.

[0075] Wherein, when the picture is not an IRAP picture, the syntax element slice_pic_order_cnt_lsb is conditionally included in the slice_segment_header() syntax and has the following definition:

[0076] slice_pic_order_cnt_lsb specifies the picture order count modulo MaxPicOrderCntLsb of the current picture. The length of the slice_pic_order_cnt_lsb syntax element is log2_max_pic_order_cnt_lsb, and if log2_max_pic_order_cnt_lsb is not present, slice_pic_order_cnt_lsb is inferred to be equal to 0 (for all but generated pictures).

[0077] In ITU-T H.265, PicOrderCntMsb is derived as follows:

[0078] When the current picture is not an IRAP picture and is output, the variable prevPicOrderCntLsb is derived as follows:

[0079] The variable prevPicOrderCntMsb is set equal to the PicOrderCntMsb of prevTid0Pic.

[0080] - If the current picture is an IRAP picture with NoRaslOutputFlag equal to 1, PicOrderCntMsb is set equal to 0.

[0081] - Otherwise, PicOrderCntMsb is derived as follows:

[0082]

[0083] It should be noted that in ITU-T H.265, all IDR pictures will have PicOrderCntVal equal to 0, because for IDR pictures, slice_pic_order_cnt_lsb is inferred to be 0, and both prevPicOrderCntLsb and prevPicOrderCntMsb are set equal to 0.

[0084] It should be noted that JVET-J1001 provides the fragment header syntax shown in Table 1.

[0085]

[0086] Table 1

[0087] JVET-J1001 provides the following definitions for the corresponding syntax elements shown in Table 1.

[0088] slice_pic_parameter_set_id specifies the value of pps_pic_parameter_set_id of the PPS currently used. The value of slice_pic_parameter_set_id should be in the range of 0 to 63 (inclusive).

[0089] slice_address specifies the address of the first CTB in a slice in the CTB raster scan of a picture. The length of the slice_address syntax element is Ceil(Log2(PicSizeInCtbsY)) bits. The value of slice_address shall be in the range of 0 to PicSizeInCtbsY-1, inclusive, and shall not be equal to the value of slice_address of any other coded slice NAL unit of the same coded picture.

[0090] The variable CtbAddrInRs, which specifies the address of the CTB in the CTB raster scan of the picture, is set equal to slice_address.

[0091] slice_type specifies the encoding type of the slice according to Table 2.

[0092] slice_type The name of slice_type 0 B(B segment) 1 P(P fragment) 2 I (I fragment)

[0093] Table 2

[0094] When nal-unit_type has a value in the range of [to be determined] (inclusive), that is, when the picture is an IRAP picture, slice_type shall be equal to 2.

[0095] log2_diff_ctu_max_bt_size specifies the difference between the luma CTB size and the maximum luma size (width or height) of a coding block that can be partitioned using binary partitioning. The value of log2_diff_ctu_max_bt_size should be in the range of 0 to CtbLog2SizeY-MinCbLog2SizeY (inclusive).

[0096] It should be noted that a B slice refers to a slice that allows bi-predictive inter prediction, uni-predictive inter prediction, and intra prediction; a P slice refers to a slice that allows uni-predictive inter prediction and intra prediction; and an I slice refers to the case where only intra prediction is allowed. It should be noted that in some cases, B slices and P slices are collectively referred to as inter slices.

[0097] The present disclosure describes a technique for signaling a picture order count value, which is simpler and provides greater flexibility than the technique described in ITU-T H.265. According to the technique described herein, a video encoder can signal a picture order count value, etc., using the syntax and semantics described herein. A video decoder can determine a picture order count value, etc. by parsing the signaling using the syntax and semantics described herein, and perform video decoding and output pictures based on the determined picture order count value.

[0098] Figure 1 1 is a block diagram illustrating an example of a system that may be configured to encode (e.g., encode and / or decode) video data in accordance with one or more techniques of this disclosure. System 100 represents an example of a system that may encapsulate video data in accordance with one or more techniques of this disclosure. Figure 1 As shown, system 100 includes source device 102, communication medium 110, and target device 120. Figure 1 In the example shown, source device 102 may include any device configured to encode video data and transmit the encoded video data to communication medium 110. Target device 120 may include any device configured to receive the encoded video data via communication medium 110 and decode the encoded video data. Source device 102 and / or target device 120 may include computing devices equipped for wired and / or wireless communication, and may include, for example, set-top boxes, digital video recorders, televisions, desktop, laptop or tablet computers, game consoles, medical imaging devices, and mobile devices (including, for example, smart phones, cellular phones, personal gaming devices).

[0099] The communication medium 110 may include any combination of wireless and wired communication media and / or storage devices. The communication medium 110 may include coaxial cables, fiber optic cables, twisted pair cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other device that can be used to facilitate communication between various devices and sites. The communication medium 110 may include one or more networks. For example, the communication medium 110 may include a network configured to allow access to the World Wide Web, such as the Internet. The network may operate according to a combination of one or more telecommunication protocols. The telecommunication protocol may include proprietary aspects and / or may include standardized telecommunication protocols. Examples of standardized telecommunication protocols include digital video broadcasting (DVB) standards, advanced television system committee (ATSC) standards, integrated service digital broadcasting (ISDB) standards, cable data service interface specifications (DOCSIS) standards, global mobile communication systems (GSM) standards, code division multiple access (CDMA) standards, 3rd generation partnership project (3GPP) standards, European Telecommunications Standards Institute (ETSI) standards, Internet Protocol (IP) standards, wireless application protocol (WAP) standards, and Institute of Electrical and Electronics Engineers (IEEE) standards.

[0100] A storage device may include any type of device or storage medium capable of storing data. The storage medium may include a tangible or non-transitory computer-readable medium. The computer-readable medium may include an optical disk, a flash memory, a magnetic memory, or any other suitable digital storage medium. In some examples, a memory device or a portion thereof may be described as a non-volatile memory, and in other examples, a portion of a memory device may be described as a volatile memory. Examples of volatile memory may include random access memory (RAM), dynamic random access memory (DRAM), and static random access memory (SRAM). Examples of non-volatile memory may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable and programmable (EEPROM) memory. One or more storage devices may include a memory card (e.g., a secure digital (SD) memory card), an internal / external hard drive, and / or an internal / external solid-state drive. Data may be stored on a storage device according to a defined file format.

[0101] Figure 4 is a conceptual diagram illustrating examples of components that may be included in a specific implementation of system 100. Figure 4 In the exemplary implementation shown, system 100 includes one or more computing devices 402A-402N, a television service network 404, a television service provider site 406, a wide area network 408, a local area network 410, and one or more content provider sites 412A-412N. Figure 4The specific implementations shown in represent examples of a system that can be configured to allow digital media content (such as movies, live sporting events, etc.) and data and applications associated therewith and media presentations to be distributed to and accessed by multiple computing devices (such as computing devices 402A to 402N). Figure 4 In the example shown, computing devices 402A to 402N may include any device configured to receive data from one or more of television service network 404, wide area network 408, and / or local area network 410. For example, computing devices 402A to 402N may be equipped for wired and / or wireless communications and may be configured to receive services over one or more data channels, and may include televisions, including so-called smart televisions, set-top boxes, and digital video recorders. In addition, computing devices 402A to 402N may include desktop computers, laptop or tablet computers, game consoles, mobile devices (including, for example, "smart" phones, cellular phones, and personal gaming devices).

[0102] The television service network 404 is an example of a network configured to allow distribution of digital media content that may include television services. For example, the television service network 404 may include a public air television network, a public or subscription-based satellite television service provider network, and a public or subscription-based cable television provider network and / or a cloud or Internet service provider. It should be noted that, although in some examples, the television service network 404 may be primarily used to allow the provision of television services, the television service network 404 may also allow the provision of other types of data and services according to any combination of the telecommunications protocols described herein. In addition, it should be noted that in some examples, the television service network 404 may allow two-way communication between the television service provider site 406 and one or more of the computing devices 402A to 402N. The television service network 404 may include any combination of wireless and / or wired communication media. The television service network 404 may include coaxial cables, fiber optic cables, twisted pair cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other device that can be used to facilitate communication between various devices and sites. The television service network 404 may operate according to a combination of one or more telecommunications protocols. The telecommunications protocol may include proprietary aspects and / or may include standardized telecommunications protocols. Examples of standardized telecommunication protocols include the DVB standard, the ATSC standard, the ISDB standard, the DTMB standard, the DMB standard, the Data Over Cable Service Interface Specification (DOCSIS) standard, the HbbTV standard, the W3C standard, and the UPnP standard.

[0103] Reference again Figure 4, the television service provider site 406 may be configured to distribute television services via the television service network 404. For example, the television service provider site 406 may include one or more broadcast stations, cable television providers, or satellite television providers, or Internet-based television providers. For example, the television service provider site 406 may be configured to receive transmissions (including television programs) via satellite uplink / downlink. In addition, as Figure 4 As shown, television service provider site 406 may be in communication with wide area network 408 and may be configured to receive data from content provider sites 412A through 412N. It should be noted that in some examples, television service provider site 406 may include a television studio and content may originate from the television studio.

[0104] The wide area network 408 may include a packet-based network and may be operated according to a combination of one or more telecommunication protocols. The telecommunication protocol may include proprietary aspects and / or may include standardized telecommunication protocols. Examples of standardized telecommunication protocols include the Global System for Mobile Communications (GSM) standard, the Code Division Multiple Access (CDMA) standard, the 3rd Generation Partnership Project (3GPP) standard, the European Telecommunications Standards Institute (ETSI) standard, the European Standard (EN), the IP standard, the Wireless Application Protocol (WAP) standard, and the Institute of Electrical and Electronics Engineers (IEEE) standard, such as one or more IEEE 802 standards (e.g., Wi-Fi). The wide area network 408 may include any combination of wireless and / or wired communication media. The wide area network 408 may include coaxial cables, fiber optic cables, twisted pair cables, Ethernet cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other device that may be used to facilitate communication between various devices and sites. In one example, the wide area network 408 may include the Internet. The local area network 410 may include a packet-based network and may be operated according to a combination of one or more telecommunication protocols. The local area network 410 may be distinguished from the wide area network 408 based on access levels and / or physical infrastructure. For example, the local area network 410 may include a secure home network.

[0105] Reference again Figure 4, content provider sites 412A to 412N represent examples of sites that can provide multimedia content to television service provider sites 406 and / or computing devices 402A to 402N. For example, a content provider site may include a studio with one or more studio content servers, which are configured to provide multimedia files and / or streams to television service provider sites 406. In one example, content provider sites 412A to 412N may be configured to provide multimedia content using an IP suite. For example, a content provider site may be configured to provide multimedia content to a receiver device according to a real-time streaming protocol (RTSP), HTTP, etc. In addition, content provider sites 412A to 412N may be configured to provide data including hypertext-based content, etc. to one or more of receiver devices 402A to 402N and / or television service provider sites 406 via a wide area network 408. Content provider sites 412A to 412N may include one or more web servers. The data provided by data provider sites 412A to 412N may be defined according to a data format.

[0106] Reference again Figure 1 , source device 102 includes video source 104, video encoder 106, data encapsulator 107 and interface 108. Video source 104 may include any device configured to capture and / or store video data. For example, video source 104 may include a camera and a storage device operably coupled thereto. Video encoder 106 may include any device configured to receive video data and generate a compatible bitstream representing the video data. A compatible bitstream may refer to a bitstream from which a video decoder can receive and reproduce video data. Various aspects of a compatible bitstream may be defined according to a video coding standard. When generating a compatible bitstream, video encoder 106 may compress the video data. The compression may be lossy (perceptible or imperceptible to the viewer) or lossless. Figure 5 is a block diagram illustrating an example of a video encoder 500 that can implement the techniques described herein for encoding video data. It should be noted that although the exemplary video encoder 500 is illustrated as having different functional blocks, such illustration is intended for descriptive purposes and does not limit the video encoder 500 and / or its subcomponents to a particular hardware or software architecture. The functionality of the video encoder 500 may be implemented using any combination of hardware, firmware, and / or software implementations.

[0107] The video encoder 500 can perform intra-frame prediction encoding and inter-frame prediction encoding of a picture region and thus can be referred to as a hybrid video encoder. Figure 5In the example shown, the video encoder 500 receives a source video block. In some examples, the source video block may include a picture region that has been divided according to a coding structure. For example, the source video data may include macroblocks, CTUs, CBs, sub-partitions thereof, and / or additional equivalent coding units. In some examples, the video encoder 500 may be configured to perform additional subdivision of the source video block. It should be noted that the techniques described herein are generally applicable to video encoding regardless of how the source video data is partitioned before and / or during encoding. Figure 5 In the example shown, the video encoder 500 includes a summer 502, a transform coefficient generator 504, a coefficient quantization unit 506, an inverse quantization and transform coefficient processing unit 508, a summer 510, an intra prediction processing unit 512, an inter prediction processing unit 514, a filter unit 516, and an entropy coding unit 518. Figure 5 As shown, video encoder 500 receives source video blocks and outputs a bitstream.

[0108] exist Figure 5 In the example shown, the video encoder 500 can generate residual data by subtracting the predicted video block from the source video block. The selection of the predicted video block is described in detail below. The summer 502 represents a component configured to perform the subtraction operation. In one example, the subtraction of the video block occurs in the pixel domain. The transform coefficient generator 504 applies a transform such as a discrete cosine transform (DCT), a discrete sine transform (DST), or a conceptually similar transform (e.g., four 8×8 transforms can be applied to a 16×16 residual value array) to the residual block or its sub-partition to generate a set of residual transform coefficients. The transform coefficient generator 504 can be configured to perform any and all combinations of transforms included in the discrete triangular transform series, including its approximation. The transform coefficient generator 504 can output the transform coefficients to a coefficient quantization unit 506. The coefficient quantization unit 506 can be configured to perform quantization of the transform coefficients. The quantization process can reduce the bit depth associated with some or all coefficients. The degree of quantization can change the rate distortion (i.e., the relationship between bit rate and video quality) of the encoded video data. The degree of quantization can be modified by adjusting a quantization parameter (QP). The quantization parameter can be determined based on a slice level value and / or a CU level value (e.g., a CU delta QP value). The QP data may include any data used to determine the QP used to quantize a particular set of transform coefficients. Figure 5 As shown, the quantized transform coefficients (which may be referred to as level values) are output to the inverse quantization and transform coefficient processing unit 508. The inverse quantization and transform processing unit 508 may be configured to apply inverse quantization and inverse transform to generate reconstructed residual data. Figure 5As shown, at the summer 510, the reconstructed residual data can be added to the predicted video block. In this way, the encoded video block can be reconstructed, and the resulting reconstructed video block can be used to evaluate the coding quality of a given prediction, transformation and / or quantization. The video encoder 500 can be configured to perform multiple encoding rounds (e.g., performing encoding while changing one or more of the prediction, transformation parameters and quantization parameters). The rate distortion or other system parameters of the bitstream can be optimized based on the evaluation of the reconstructed video block. In addition, the reconstructed video block can be stored and used as a reference for predicting subsequent blocks.

[0109] Reference again Figure 5 , the intra-frame prediction processing unit 512 may be configured to select an intra-frame prediction mode for a video block to be encoded. The intra-frame prediction processing unit 512 may be configured to evaluate a frame and determine an intra-frame prediction mode for encoding a current block. As described above, possible intra-frame prediction modes may include a planar prediction mode, a DC prediction mode, and an angular prediction mode. In addition, it should be noted that in some examples, the prediction mode of the chrominance component may be inferred based on the prediction mode of the luma prediction mode. The intra-frame prediction processing unit 512 may select an intra-frame prediction mode after performing one or more encoding rounds. Furthermore, in one example, the intra-frame prediction processing unit 512 may select a prediction mode based on a rate-distortion analysis. As Figure 5 As shown, the intra prediction processing unit 512 outputs intra prediction data (e.g., syntax elements) to the entropy coding unit 518 and the transform coefficient generator 504. As described above, the transform performed on the residual data can be mode-dependent (e.g., the secondary transform matrix can be determined based on the prediction mode).

[0110] Reference again Figure 5 , the inter-frame prediction processing unit 514 may be configured to perform inter-frame prediction encoding for the current video block. The inter-frame prediction processing unit 514 may be configured to receive a source video block and calculate a motion vector of a PU of the video block. The motion vector may indicate the displacement of a PU of a video block within a current video frame relative to a prediction block within a reference frame. Inter-frame prediction encoding may use one or more reference pictures. In addition, motion prediction may be unidirectional prediction (using one motion vector) or bidirectional prediction (using two motion vectors). The inter-frame prediction processing unit 514 may be configured to select a prediction block by calculating a pixel difference determined by, for example, the sum of absolute differences (SAD), the sum of square differences (SSD), or other difference metrics. As described above, a motion vector may be determined and specified based on motion vector prediction. As described above, the inter-frame prediction processing unit 514 may be configured to perform motion vector prediction. The inter-frame prediction processing unit 514 may be configured to generate a prediction block using motion prediction data. For example, the inter-frame prediction processing unit 514 may locate a prediction video block ( Figure 5). Note that the inter-frame prediction processing unit 514 may be further configured to apply one or more interpolation filters to the reconstructed residual block to calculate sub-integer pixel values ​​for motion estimation. The inter-frame prediction processing unit 514 may output the motion prediction data of the calculated motion vector to the entropy coding unit 518.

[0111] Reference again Figure 5 , filter unit 516 receives the reconstructed video blocks and the encoding parameters and outputs modified reconstructed video data. Filter unit 516 may be configured to perform deblocking and / or sample adaptive offset (SAO) filtering. SAO filtering is a non-linear amplitude mapping that can be used to improve reconstruction by adding an offset to the reconstructed video data. It should be noted that, as Figure 5 As shown, the intra prediction processing unit 512 and the inter prediction processing unit 514 can receive the modified reconstructed video block via the filter unit 216. The entropy coding unit 518 receives the quantized transform coefficients and the prediction syntax data (i.e., the intra prediction data and the motion prediction data). It should be noted that in some examples, the coefficient quantization unit 506 can perform a scan of the matrix including the quantized transform coefficients before outputting the coefficients to the entropy coding unit 518. In other examples, the entropy coding unit 518 can perform the scan. The entropy coding unit 518 can be configured to perform entropy coding according to one or more of the techniques described herein. As such, the video encoder 500 represents an example of a device configured to generate encoded video data according to one or more techniques of the present invention.

[0112] Reference again Figure 1 , the data encapsulator 107 can receive the encoded video data and generate a compatible bitstream according to a defined data structure, for example, a sequence of NAL units. A device receiving the compatible bitstream can reproduce the video data therefrom. In addition, as described above, sub-bitstream extraction can refer to the process by which a device receiving a bitstream compliant with ITU-T H.265 forms a new bitstream compliant with ITU-T H.265 by discarding and / or modifying data in the received bitstream. It should be noted that the term conforming bitstream can be used instead of the term compatible bitstream.

[0113] As described above, ITU-T H.265 provides a case where the sequence parameter set syntax includes a syntax element log2_max_pic_order_cnt_lsb_minus4, which specifies the value of the variable MaxPicOrderCntLsb. According to the techniques herein, the sequence parameter set syntax may also include a syntax element log2_max_pic_order_cnt_msb_cycle_minus1 (e.g., immediately before or after log2_max_pic_order_cnt_lsb_minus4, or in some other position in the sequence parameter set or in another parameter set). In one example, log2_max_pic_order_cnt_msb_cycle_minus1 may be based on the following definition:

[0114] log2_max_pic_order_cnt_msb_cycle_minus1 specifies the value of the variable MaxPicOrderCntMSBCycle in the decoding process for the picture order count as follows:

[0115] MaxPicOrderCntMSBCycle=2 (log2_max_pic_order_cnt_msb_cycle_minus1+1)

[0116] The value of log2_max_pic_order_cnt_msb_cycle_minus1 shall be in the range of 0 to 15 (inclusive).

[0117] It should be noted that in some examples, the value of log2_max_pic_order_cnt_msb_cycle_minus1 may be in other ranges (eg, 0 to 16 (inclusive), 0 to 28 (inclusive), 0 to 48 (inclusive), etc.).

[0118] In one example, the slice header may include a slice_poc_info() syntax. For example, Table 3 shows an example of a slice header including a slice_poc_info() syntax. The syntax elements included in slice_header() may be based on the definitions provided above.

[0119]

[0120] Table 3

[0121] Table 4 provides an example of the syntax of slice_poc_info().

[0122]

[0123] Table 4

[0124] The syntax elements slice_pic_order_cnt_lsb, slice_pic_order_cnt_msb_cycle_present, and slice_pic_order_cnt_msb_cycle in Table 4 may be based on the following exemplary definitions:

[0125] slice_pic_order_cnt_lsb specifies the picture order count modulo MaxPicOrderCntLsb of the current picture. The length of the slice_pic_order_cnt_lsb syntax element is log2_max_pic_order_cnt_lsb_minus4+4 bits. The value of slice_pic_order_cnt_lsb shall be in the range of 0 to MaxPicOrderCntLsb-1, inclusive.

[0126] slice_pic_order_cnt_msb_cycle_present equal to 1 indicates that slice_pic_order_cnt_msb_cycle immediately follows. slice_pic_order_cnt_msb_cycle_present equal to 0 indicates that the slice_pic_order_cnt_msb_cycle syntax element is not signaled. When not signaled, slice_pic_order_cnt_msb_cycle_present is inferred to be equal to 0. slice_pic_order_cnt_msb_cycle_present shall be equal to 0 when the current picture is an IDR picture.

[0127] slice_pic_order_cnt_msb_cycle specifies the picture order count MSB period value. The length of the slice_pic_order_cnt_msb_cycle syntax element is log2_max_pic_order_cnt_msb_cycle_minus1+1 bits. The value of slice_pic_order_cnt_msb_cycle shall be in the range of 0 to MaxPicOrderCntMSBCycle-1, inclusive. slice_pic_order_cnt_msb_cycle is the POC MSB period element.

[0128] It should be noted that in some examples slice_pic_order_cnt_msb_cycle may be encoded as i(v) to allow signaling of negative values ​​of slice_pic_order_cnt_msb_cycle.

[0129] It should be noted that in some examples, minus-one signaling may not be used for log2_max_pic_order_cnt_msb_cycle_minus1. That is, log2_max_pic_order_cnt_msb_cycle_minus1 may be replaced by a syntax element log2_max_pic_order_cnt_msb_cycle, which may be based on the following definition:

[0130] log2_max_pic_order_cnt_msb_cycle specifies the value of the variable MaxPicOrderCntMSBCycle in the decoding process for the picture order count as follows:

[0131] MaxPicOrderCntMSBCycle=2 (log2_max_pic_order_cnt_msb_cycle)

[0132] The value of log2_max_pic_order_cnt_msb_cycle should be in the range of 0 to 16 (inclusive) (or 0 to 15 (inclusive), 0 to 28 (inclusive), 0 to 48 (inclusive), etc.).

[0133] When using log2_max_pic_order_cnt_msb_cycle, the definition of slice_pic_order_cnt_msb_cycle can be modified as follows:

[0134] slice_pic_order_cnt_msb_cycle specifies the picture order count MSB cycle value. The length of the slice_pic_order_cnt_msb_cycle syntax element is log2_max_pic_order_cnt_msb_cycle bits. The value of slice_pic_order_cnt_msb_cycle shall be in the range of 0 to MaxPicOrderCntMSBCycle-1, inclusive.

[0135] It should be noted that in some examples, log2_max_pic_order_cnt_msb_cycle_minus1 may not be used, and in this case, slice_pic_order_cnt__msb_cycle may be signaled using the ue(v) data type instead of the u(v) data type.

[0136] In one example, instead of signaling log2_max_pic_order_cnt_msb_cycle_minus1, the value of MaxPicOrderCntMSBCycle may be derived from the value of log2_max_pic_order_cnt_lsb_minus4 and the predefined MaxPicOrderCnt. In one example, MaxPicOrderCntMSBCycle may be derived as follows:

[0137] PicOrderCntBitDepth=Ceil(Log2(MaxPicOrderCnt))

[0138] Log2MaxPicOrderCntMSBCycle=PicOrderCntBitDepth-(log2_max_pic_order_cnt_lsb_minus4+4)

[0139] MaxPicOrderCntMSBCycle=2 Log2MaxPicOrderCntMSBCycle

[0140] In one example, instead of signaling log2__max_pic_order_cnt_lsb_minus4, the value of MaxPicOrderCntLsb may be derived from the value of log2_max_pic_order_cnt_msb_cycle_minus1 and the predefined MaxPicOrderCnt. In one example, MaxPicOrderCntLsb may be derived as follows:

[0141] PicOrderCntBitDepth=Ceil(Log2(MaxPicOrderCnt))

[0142] Log2MaxPicOrderCntLSB=PicOrderCntBitDepth-

[0143] (log2_max_pic_order_cnt_msb_cycle_minus1+1)

[0144] MaxPicOrderCntLsb=2 Log2MaxPicOrderCntLSB

[0145] Based on the syntax elements provided in slice_poc_info(), PicOrderCntVal equal to PicOrderCntMsb+slice_pic_order_cnt_lsb can be derived as follows:

[0146] When the current picture is not an IDR picture or the current picture does not cause the slice_pic_order_cnt_msb_cycle to be signaled, the variables prevPicOrderCntLsb and prevPicOrderCntMsb are derived as follows:

[0147] - Let prevTid0Pic be the previous picture with TemporalId equal to 0 in decoding order and a sub-layer non-reference picture.

[0148] -The variable prevPicOrderCntLsb is set equal to slice_pic_order_cnt_lsb of prevTid0pic.

[0149] -The variable prevPicOrderCntMsb is set equal to the PicOrderCntMsb of prevTid0Pic.

[0150] The variable PicOrderCntMsb of the current picture is exported as follows:

[0151] - If the current picture is an IDR picture, or if the log2_max_pic_order_cnt_msb_cycle of the active SPS of the slice exists and is equal to 0, the variable PicOrderCntMsb is set equal to 0.

[0152] - Additionally, if the slice of the current picture has signaled slice_pic_order_cnt_msb_cycle, the variable PicOrderCntMSB is set equal to slice_pic_order_cnt_msb_cycle multiplied by MaxPicOrderCntLsb.

[0153] - Otherwise, PicOrderCntMsb is derived as follows:

[0154]

[0155] PicOrderCntVal is derived as follows:

[0156] PicOrderCntVal=PicOrderCntMsb+slice_pic_order_cnt_lsb

[0157] It should be noted that in some examples, the value of PicOrderCntVal should be between -2 31 to 2 31-1 (including the end value).

[0158] In another example, PicOrderCntVal equal to currentPicOrderCntMsb+slice_pic_order_cnt_lsb may be derived as follows:

[0159] If the current picture is an IDR picture, currentPicOrderCntMsb is set equal to 0.

[0160] - Additionally, if the slice of the current picture has signaled slice_pic_order_cnt_msb_cycle, the variable currentPicOrderCntMsb is set equal to slice_pic_order_cnt_msb_cycle multiplied by MaxPicOrderCntLsb.

[0161] Otherwise, the variable current PicOrderCntMSB is derived as follows:

[0162] - Let prevPOCMSBPic be the previous picture in decoding order for which slice_pic_order_cnt_msb_cycle has been signaled or the IDR picture, whichever is closer in decoding order to the current picture.

[0163] - If prevPOCMSBPic is an IDR picture, the variable currentPicOrderCntMsb is set equal to 0, or if prevPOCMSBPic is not an IDR picture, the variable is set equal to the slice_pic_order_cnt_msb_cycle of the prevPOCMSBPic picture multiplied by MaxPicOrderCntLsb.

[0164] PicOrderCntVal is derived as follows:

[0165] PicOrderCntVal=PicOrderCntMsb+slice_pic_order_cnt_lsb

[0166] In one example, a flag for controlling the signaling of slice-level MSB picture order count related syntax elements may be signaled in a parameter set (eg, VPS, SPS, or PPS). Table 5 shows an example of a sequence parameter set including slice_pic_order_cnt_msb_signaling_present.

[0167]

[0168] Table 5

[0169] With respect to Table 5, the semantics of the various syntax elements may be as follows:

[0170] log2_max_pic_order_cnt_lsb_minus4 specifies the value of the variable MaxPicOrderCntLsb used in the decoding process of the picture order count as follows:

[0171] MaxPicOrderCntLsb=2 (log2_max_pic_order_cnt_lsb_minus4+4)

[0172] The value of log2_max_pic_order_cnt_lsb_minus4 shall be in the range of 0 to 12 (inclusive).

[0173] In another example, the value of log2_max_pic_order_cnt_lsb_minus4 should be in the range of 0 to 16 (inclusive).In general, some other valid value range may be declared for log2_max_pic_order_cnt_lsb_minus4.

[0174] slice_pic_order_cnt_msb_signaling_present equal to 0 indicates that POC MSB related information for picture order count is not signaled in the slice header. slice_pic_order_cnt_msb_signaling_present equal to 1 indicates that POC MSB related information may be signaled in the slice header. slice_pic_order_cnt_msb_signaling_present may be a POC MSB first flag, which is a POC MSB signaling present flag.

[0175] log2_max_pic_order_cnt_msb_cycle specifies the value of the variable MaxPicOrderCntMSBCycle as follows:

[0176] MaxPicOrderCntMSBCycle=2 (log2_max_pic_order_cnt_lsb_msb_cycle)

[0177] The value of log2_max_pic_order_cnt_lsb_cycle shall be in the range of 0 to 28 (inclusive).

[0178] In another example, the value of log2_max_pic_order_cnt_msb_cycle should be in the range of 0 to 16 (inclusive).In general, some other valid value range may be declared for log2_max_pic_order_cnt_msb_cycle.

[0179] When the syntax element slice_pic_order_cnt_msb_signaling_present is included in the parameter set, slice_poc_info() may be as shown in Table 6.

[0180]

[0181]

[0182] Table 6

[0183] With respect to Table 6, the semantics of the various syntax elements may be as follows:

[0184] slice_pic_order_cnt_lsb specifies the picture order count modulo MaxPicOrderCntLsb of the current picture. The length of the slice_pic_order_cnt_lsb syntax element is log2_max_pic_order_cnt_lsb_minus4+4 bits. The value of slice_pic_order_cnt_lsb shall be in the range of 0 to MaxPicOrderCntLsb-1, inclusive.

[0185] In the case of the examples shown in Tables 5 and 6, slice_pic_order_cnt_msb_cycle_present and slice_pic_order_cnt_msb_cycle may be based on the following definitions:

[0186] slice_pic_order_cnt_msb_cycle_present equal to 1 indicates that slice_pic_order_cnt_msb_cycle follows immediately. slice_pic_order_cnt_msb_cycle_present equal to 0 indicates that the slice_pic_order_cnt_msb_cycle syntax element is not signaled. When not signaled, slice_pic_order_cnt_msb_cycle_present is inferred to be equal to 0. When the current picture is an IDR picture, slice_pic_order_cnt_msb_cycle_present shall be equal to 0. When log2_max_pic_order_cnt_msb_cycle is equal to 0, slice_pic_order_cnt_msb_cycle_present shall be equal to 0. slice_pic_order_cnt_msb_cycle_present may be a POC MSB second flag, which is a POC MSB present flag.

[0187] slice_pic_order_cnt_msb_cycle specifies the picture order count MSB cycle value. The length of the slice_pic_order_cnt_msb_cycle syntax element is log2_max_pic_order_cnt_msbcycle bits. The value of slice_pic_order_cnt_msb_cycle shall be in the range of 0 to MaxPicOrderCntMSBCycle-1, inclusive.

[0188] In one example, slice_pic_order_cnt_msb_cycle_present may be included in the parameter set. When the syntax element slice_pic_order_cnt_msb_cycle_present is included in the parameter set, slice_poc_info() may be modified as shown in Table 7.

[0189]

[0190] Table 7

[0191] In some examples, the presence of syntax elements in slice_poc_info() can be based on the value of log2_max_pic_order_cnt_msb_cycle_minus1 or log2_max_pic_order_cnt_msb_cycle. For example, Table 8 shows an example where the condition for the presence of slice_pic_order_cnt_msb_cycle_present and slice_pic_order_cnt_msb_cycle is that log2_max_pic_order_cnt_msb_cycle is not equal to zero. In one example, if log2_max_pic_order_cnt_msb_cycle is equal to zero, slice_pic_order_cnt_msb_cycle_present should be constrained to be equal to zero.

[0192]

[0193] Table 8

[0194] In one example, instead of signaling slice_pic_order_cnt_msb_cycle, the value of the syntax element slice_pic_order_msb may be signaled. The syntax element slice_pic_order_msb may be coded as ue(v) or u(v). In this case, instead of log2_max_pic_order_cnt_msb_minus1, the syntax element log2_max_pic_order_cnt_msb_cycle_minus1 may be signaled with the following semantics:

[0195] log2_max_pic_order_cnt_msb_minus1 specifies the value of the variable MaxPicOrderCntMSB used in the decoding process of the picture order count as follows:

[0196] MaxPicOrderCntMSB=2 (log2_max_pic_order_cnt_minus1+1)

[0197] In some examples, a constraint may be imposed on MaxPicOrderCntMSB. Furthermore, in this case, the decoding process for the picture order count may be modified such that the variable PicOrderCntMSB is set equal to slice_pic_order_msb.

[0198] In one example, when slice_pic_order_cnt_lsb is equal to zero, slice_pic_order_cnt_msb_cycle may be always signaled. In one example, this may be further controlled by additional slice and / or parameter set level flags. In other cases, constraints may be imposed on whether slice_pic_order_cnt_msb_cycle is signaled and its possible values. In another example, slice_pic_order_cnt_msb_cycle may be always signaled for TId 0 pictures. In one example, constraints may be imposed on various syntax elements and / or across slices and / or parameter sets.

[0199] In one example, the sequence parameter set may include a flag to indicate whether the syntax element slice_pic_order_cnt is present in the slice header. slice_pic_order_cnt may specify the value of the picture order count value without separating the bits into MSB and LSB, and may be based on the following definition.

[0200] slice_pic_order_cnt specifies the picture order count value of the current picture. The value of slice_pic_order_cnt should be in the range of 0 to MaxPicOrderCnt (inclusive).

[0201] Tables 9 and 10 show an example in which the flag full_pic_order_cnt_signal_flag indicates whether log2_max_pic_order_cnt_lsb_minus4 and log2_max_pic_order_cnt_msb_cycle_minus1 exist in the sequence parameter set and whether the syntax element slice_pic_order_cnt exists in the slice header.

[0202]

[0203] Table 9

[0204]

[0205] Table 10

[0206] In the case of the examples shown in Tables 9 and 10, PicOrderCntVal may be derived as follows:

[0207]

[0208] In the case of the examples shown in Tables 5 and 6, PicOrderCntVal may be derived as follows:

[0209] When the current picture is not an IRAP picture or the current picture does not cause slice_pic_order_cnt-msb_cycle to be signaled, the variables prevPicOrderCntLsb and prevPicOrderCntMsb are derived as follows:

[0210] - Let prevTid0Pic be the previous picture with TemporalId equal to 0 in decoding order.

[0211] -The variable prevPicOrderCntLsb is set equal to slice_pic_order_cnt_lsb of prevTid0Pic.

[0212] -The variable prevPicOrderCntMsb is set equal to the PicOrderCntMsb of prevTid0Pic.

[0213] The variable PicOrderCntMsb of the current picture is exported as follows:

[0214] - If the current picture is an IRAP picture, or if the log2_max_pic_order_cnt_msb_cycle of the active SPS of the slice exists and is equal to 0, the variable PicOrderCntMsb is set equal to 0.

[0215] - Additionally, if the slice of the current picture has signaled slice_pic_order_cnt_msb_cycle, the variable PicOrderCntMsb is set equal to slice_pic_order_cnt-msb_cycle multiplied by PicOrderCntMsb.

[0216] - Otherwise, PicOrderCntMsb is derived as follows:

[0217]

[0218] PicOrderCntVal is derived as follows:

[0219] PicOrderCntVal=PicOrderCntMsb+slice_pic_order_cnt_lsb

[0220] If slice_pic_order_cnt_msb_signaing_present is equal to 1, the value of PicOrderCntVal shall be between -2 (log2_max_pic_order_cnt_lsb_minus4 + log2_max_pic_order_cnt_msb_cycle+3) to 2 (log2 _max_pic_order_cnt_lsb_minus4+log2_max_pic_order_cnt_msb_cycle+3) -1 (inclusive) range.

[0221] Otherwise, the value of PicOrderCntVal should be -2 31 to 2 31 -1 (inclusive) range.

[0222] In another example, if in the coded video sequence, only slice_pic_order_cnt_msb_cycle is signaled, then the value of PicOrderCntVal should be -2 (log2 _max_pic_order_cnt_lsb_minus4+log2_max_pic_order_cnt_msb_cycle+3) to 2 (log2 _max_pic_order_cnt_lsb_minus4+log2_max_pic_order_cnt_msb_cycle+3) -1 (inclusive) range.

[0223] Otherwise, the value of PicOrderCntVal should be -2 31 to 2 31 -1 (inclusive) range.

[0224] In yet another example, the other parts stated above can be used in conjunction with 2 31 For example, 2 31 Can be replaced with some other value in other parts above, such as 2 48 or 2 64 or 2 16 wait.

[0225] Furthermore, in one example, an Instantaneous Decoding Refresh (IDR) picture may be described as an IRAP picture that does not reference any picture other than itself for inter-prediction during its decoding process and is the first picture of the coded video sequence in decoding order.

[0226] As described above, a picture can be divided into fragments and / or tiles, where a fragment includes a sequence of CTUs in raster scan order, and where a tile is a sequence of CTUs corresponding to a rectangular area of ​​a picture. As described above, a fragment may include one or more tiles. In addition, there may be cases where the same CTU group (i.e., a group of CTUs covering a rectangular area of ​​a picture) can be classified as a fragment or a tile. "Tiles groups for VVC", document JVET-L0415-v1 of the 12th meeting of ISO / IEC JTC1 / SC29 / WG11 (October 3-12, 2018), referred to herein as JVET-L0415, describes a situation where a fragment is required to consist of an integer number of complete tiles rather than an integer number of complete CTUs. Therefore, in JVET-L0415, raster scanned CTU fragments that are not rectangular areas of a picture are no longer supported, and the name "fragment" is changed to "tile group". JVET-L0415 retains the structure of the slice header, but calls it a tile group header, replaces the slice address with the tile group address in the tile group header, adds a syntax element num_tiles_in_tile_group that specifies the number of tiles in the tile group, and removes the end_of_slice_flag syntax element, instead, the end of the tile group is given by the tile group address and num_tiles_in_tile_group. Although the techniques described herein are described above with respect to slices, the techniques described herein are also applicable to situations where slices are restricted to being composed of an integer number of complete tiles. That is, the techniques described herein for indicating picture order count values ​​can be incorporated into techniques where slices include tile groups.

[0227] For example, Table 11 and Table 12 show examples of tile group header syntax indicating a picture order count value according to the techniques herein.

[0228]

[0229] Table 11

[0230]

[0231] Table 12

[0232] With respect to Table 11 and Table 12, the semantics of various syntax elements may be as follows:

[0233] When present, the value of the tile group header syntax element tile_group_pic_parameter_set_id shall be the same in all tile group headers of a coded picture.

[0234] tile_group_pic_parameter_set_id specifies the value of pps_pic_parameter_set_id of the PPS currently used. The value of tile_group_pic_parameter_set_id should be in the range of 0 to 63 (inclusive).

[0235] The tile_group_pic_order_cnt_lsb specifies the picture order count modulo MaxPicOrderCntLsb of the current picture. The length of the tile_group_pic_order_cnt_lsb syntax element is log2_max_pic_order_cnt_lsb_minus4+4 bits. The value of tile_group_pic_order_cnt_lsb_minus4+4 bits. The value of tile_group_pic_order_cnt_lsb shall be in the range of 0 to MaxPicOrderCntLsb-1, inclusive.

[0236] In another example:

[0237] tile_group_pic_order_cnt_lsb specifies the picture order count modulo MaxPicOrderCntLsb of the pictures to which this tile group belongs. The length of the tile_group_pic_order_cnt_lsb syntax element is log2_max_pic_order_cnt_lsb_minus4+4 bits. The value of tile_group_pic_order_cnt_lsb shall be in the range of 0 to MaxPicOrderCntLsb-1, inclusive.

[0238] In another example, the tile_group_pic_order_cntl_lsb syntax element may be referred to as some other name. For example, tile_group_pic_order_cntl_lsb may be referred to as pic_order_cnt_lsb. Or, tile_group_pic_order_cnt_lsb may be referred to as tile_set_pic_order_cnt_lsb. Or some other name may be used for tile_group_pic_order_cntl_lsb.

[0239] tile_group_address specifies the tile address of the first tile in the tile group. The length of tile_group_address is Ceil(Log2(NumTilesInPic)) bits. The value of tile_group_address shall be in the range of 0 to NumTilesInPic-1 (inclusive), and the value of tile_group_address shall not be equal to the value of tile_group_address of any other coded tile group NAL unit of the same coded picture. When tile_group_address is not present, it is inferred to be equal to 0.

[0240] num_tiles_in_tile_group_minus1 plus 1 specifies the number of tiles in the tile group. The value of num_tiles_in_the_group_minus1 should be in the range of 0 to NumTilesInPic-1, inclusive. When not present, the value of num_tiles_in_tile_group_minus1 is inferred to be equal to 0.

[0241] tile_group_type specifies the encoding type of the tile group according to Table 13.

[0242] tile_group_type The name of the tile_group_type 0 B(B tile group) 1 P(P tile group) 2 I (I tile group)

[0243] Table 13

[0244] When nal_unit_type is equal to IRAP_NUT, ie, the picture is an IRAP picture, tile_group_type shall be equal to 2.

[0245] log2_diff_ctu_max_bt_size specifies the difference between the luma CTB size and the maximum luma size (width or height) of a coding block that can be partitioned using binary partitioning. The value of log2_diff_ctu_max_bt_size should be in the range of 0 to CtbLog2SizeY-MinCbLog2SizeY (inclusive).

[0246] When log2_diff_ctu_max_bt_size does not exist, the value of log2_diff_ctu_max_bt_size is inferred to be equal to 2.

[0247] The variables MinQtLog2SizeY, MaxBtLog2SizeY, MinBtLog2SizeY, MaxTtLog2SizeY, MinTtLog2SizeY, MaxBtSizeY, MinBtSizeY, MaxTtSizeY, MinTtSizeY and MaxMttDepth are derived as follows:

[0248] MinQtLog2SizeY = (tile_group_type == I)? MinQtLog2SizeIntraY :

[0249] MinQtLog2SizeInterY

[0250] MaxBtLog2SizeY = CtbLog2SizeY - log2_diff_ctu_max_bt_size

[0251] MinBtLog2SizeY = MinCbLog2SizeY

[0252] MaxTtLog2SizeY = (tile_group_type == I)? 5 : 6

[0253] MinTtLog2SizeY = MinCbLog2SizeY

[0254] MinQtSizeY = 1 << MinQtLog2SizeY

[0255] MaxBtSizeY = 1 << MaxBtLog2SizeY

[0256] MinBtSizeY = 1 << MinBtLog2SizeY

[0257] MaxTtSizeY = 1 << MaxTtLog2SizeY

[0258] MinTtSizeY = 1 << MinTtLog2SizeY

[0259] MaxMttDepth = (tile_group_type == I)?

[0260] max_mtt_hierarchy_depth_intra_tile_groups :

[0261] max_mtt_hierarchy_depth_inter_tile_groups

[0262] sbtmvp_size_override_flag equal to 1 specifies that the syntax element log2_sbtmvp_active_size_minus2 is present for the current tile group. sbtmvp_size_override_flag equal to 0 specifies that the syntax element log2_atmvp_active_size_minus2 is not present, inferring that log2_sbtmvp_size_active-minus2 is equal to log2_stmvp_default_size_minus2.

[0263] log2_sbtmvp_active_size_minus2 plus 2 specifies the value of the sub-block size, which is used to drive the motion parameters of the sub-block-based TMVP for the current tile group. When log2_sbtmvp_active_size_minus2 does not exist, it is inferred to be equal to log2_sbtmvp_default_size_minus2. This variable is derived as follows:

[0264] log2sbtmvpSize=log2_sbtmvp_size_active_minus2+2

[0265] tile_group_temporal_mvp_enabled_flag specifies whether the temporal motion vector predictor can be used for inter prediction. If tile_group_temporal_mvp_enabled_flag is equal to 0, the syntax elements of the current picture should be constrained so that the temporal motion vector predictor is not used when decoding the current picture. Otherwise (tile_group_temporal_mvp_enabled_flag is equal to 1), the temporal motion vector predictor is used when decoding the current picture. When not present, the value of tile_group_temporal_mvp_enabled_flag is inferred to be equal to 0.

[0266] mvd_11_zero_flag equal to 1 indicates that the mvd_coding(x0, y0, 1) syntax structure is not parsed and for compIdx=0...1, MvdL1[x0]xy0][compIdx] is set equal to 0. mvd_11_zero_flag equal to 0 indicates that the mvd_coding(x0, y0, 1) syntax structure is parsed.

[0267] collocated_from_10_flag equal to 1 specifies that the collocated picture used for temporal motion vector prediction is derived from reference picture list 0. collocated_from_10_flag equal to 0 specifies that the collocated picture used for temporal motion vector prediction is derived from reference picture list 1. When collocated_from_10_flag is not present, it is inferred to be equal to 1.

[0268] six_minus_max_num_merge_cand specifies 6 minus the maximum number of merge motion vector prediction (MVP) candidates supported in a tile group. The maximum number of merge MVP candidates MaxNumMergeCand is derived as follows:

[0269] MaxNumMergeCand=6–six_minus_max_num_merge_cand

[0270] The value of MaxNumMergeCand should be in the range of 1 to 6 (inclusive).

[0271] dep_quart_enabled_flag equal to 0 specifies that dependent quantization is disabled.

[0272] dep_quart_enabled_flag equal to 1 specifies that dependent quantization is enabled.

[0273] sign-data-hiding_enabled_flag equal to 0 specifies that sign bit hiding is disabled.

[0274] sign-data-hiding_enabled_flag equal to 1 specifies that sign bit hiding is enabled.

[0275] When sign-data-hiding_enabled_flag is not present, it is inferred to be equal to 0.

[0276] offset_len_minus1 plus 1 specifies the length of the entry_point_offset_minus1[i] syntax element in bits. The value of offset_len_minus1 shall be in the range of 0 to 31 (inclusive).

[0277] entry_point_offset_)minus1[i] plus 1 specifies the i-th entry point offset in bytes and is represented by offset_len - minus1 plus 1 bit. The tile group data following the tile group header consists of num_tiles_in_tile_group_minus1+1 subsets, where the subset index values ​​range from 0 to num_tiles_in_tile_group_minus1 (inclusive). The first byte of the tile group data is considered to be byte 0. When present, the anti-contention bytes appearing in the tile group data portion of a coded tile group NAL unit are counted as part of the tile group data for the purpose of subset identification. Subset 0 consists of bytes 0 to entry_point_offset_minu1[0] (inclusive) of the coded tile group data, and subset k (where k is in the range of 1 to num_tiles_in_tile_group_minus1-1 (inclusive)) consists of bytes firstByte[k] to lastByte[k] (inclusive) of the coded tile group data, where firstByte[k] and lastByte[k] are defined as:

[0278]

[0279] lastByte[k]=firstByte[k]+entry_point_offset_minus1[k]

[0280] The last subset (where the subset index equals num-tiles_in_tile_group_minus1) consists of the remaining bytes encoding the tile group data.

[0281] Each subset shall consist of all coded bits of all CTUs in the tile group that are within the same tile.

[0282] In the case of the examples shown in Tables 11 and 12, PicOrderCntVal may be derived as follows:

[0283] The output of this process is PicOrderCntVal, the picture order count of the current picture. Each coded picture is associated with a picture order count variable, denoted PicOrderCntVal.

[0284] In another example:

[0285] Each tile group is associated with a picture order count variable, denoted as PicOrderCntVal.

[0286] Each tile group of a coded picture is associated with a picture order count variable, denoted as PicOrderCntVal.

[0287] When the current picture is not an IRAP picture, the variables prePicOrderCntLsb and prePicOrderCntMsb are derived as follows:

[0288] - Let prevTid0Pic be the previous picture with TemporalId equal to 0 in decoding order.

[0289] -The variable prePicOrderCntLsb is set equal to tile_group_pic_ordercnt_lsb of prevTid0Pic.

[0290] -The variable prevPicOrderCntMsb is set equal to the PicOrderCntMsb of prevTid0Pic.

[0291] The variable PicOrderCntMsb of the current picture is exported as follows:

[0292] - If the current picture is an IRAP picture, PicOrderCntMsb is set equal to 0.

[0293] - Otherwise, PicOrderCntMsb is derived as follows:

[0294] if((tile_group_pic_order_cnt_lsb<prevPicOrderCntLsb)&&

[0295] ((prevPicOrderCntLsb-tile_group_pic_order_cnt_lsb)>=

[0296] (MaxPicOrderCntLsb / 2)))

[0297] PicOrderCntMsb=prevPicOrderCntMsb+MaxPicOrderCntLsb

[0298] else if((tile_group_pic_order_cnt_lsb>prevPicOrderCntLsb)&&

[0299] ((tile_group_pic_order_cnt_lsb-prevPicOrderCntLsb)>

[0300] (MaxPieOrderCntLsb / 2)))

[0301] PicOrderCntMsb=prevPicOrderCntMsb--MaxPicOrderCntLsb

[0302] else

[0303] PicOrderCntMsb=prevPicOrderCntMsb

[0304] PicOrderCntVal is derived as follows:

[0305] PicOrderCntVal=PicOrderCntMsb+tile_group_pic_order_cnt_lsb

[0306] The value of PicOrderCntVal should be -2 31 to 2 31 -1 (inclusive) range.

[0307] In a CVS, the PicOrderCntVal values ​​of any two coded pictures shall be different.

[0308] The function PicOrderCnt(picX) is specified as follows:

[0309] PicOrderCnt(picX)=PicOrderCntVal of the picture picX

[0310] The function DiffPicOrderCnt(picA, picB) is specified as follows:

[0311] DiffPicOrderCnt(picA,picB)=PicOrderCnt(picA)-PicOrderCnt(picB)

[0312] The bitstream shall not contain any value that would cause the value of DiffPicOrderCnt(picA, picB) used during decoding to be other than -2. 15 to 2 -15 -1 (including the end value).

[0313] NOTE 2—Let X be the current picture and Y and Z be two other pictures in the same CVS. Y and Z are considered to be in the same output order direction as X when DiffPicOrderCnt(X, Y) and DiffPicOrderCnt(X, Z) are both positive or both negative.

[0314] As such, source device 102 represents an example of a device configured to: determine a picture order count most significant bit period value; signal a flag in a parameter set indicating that syntax indicating a picture order count most significant bit period value is present in a slice header; and signal a value of a syntax element in a slice header indicating a picture order count most significant bit period value.

[0315] Reference again Figure 1 , interface 108 may include any device configured to receive data generated by data encapsulator 107 and send and / or store the data to a communication medium. Interface 108 may include a network interface card such as an Ethernet card, and may include an optical transceiver, a radio frequency transceiver, or any other type of device that can send and / or receive information. In addition, interface 108 may include a computer system interface that enables files to be stored on a storage device. For example, interface 108 may include a computer system interface that supports peripheral component interconnect (PCI) and peripheral component express interconnect (PCIe) bus protocols, proprietary bus protocols, universal serial bus (USB) protocols, I 2 C's chipset or any other logical and physical structure that can be used to interconnect peer devices.

[0316] Reference again Figure 1 , target device 120 includes interface 122, data decapsulator 123, video decoder 124, and display 126. Interface 122 may include any device configured to receive data from a communication medium. Interface 122 may include a network interface card such as an Ethernet card, and may include an optical transceiver, a radio frequency transceiver, or any other type of device that can receive and / or send information. In addition, interface 122 may include a computer system interface that allows a compatible video bitstream to be retrieved from a storage device. For example, interface 122 may include a computer system that supports PCI and PCIe bus protocols, proprietary bus protocols, USB protocols, I 2 The data decapsulator 123 may be configured to receive and parse any of the exemplary parameter sets described herein.

[0317] Video decoder 124 may include any device configured to receive a bitstream (e.g., MCTS sub-bitstream extraction) and / or acceptable variants thereof and reproduce video data therefrom. Display 126 may include any device configured to display video data. Display 126 may include one of a variety of display devices such as a liquid crystal display (LCD), a plasma display, an organic light emitting diode (OLED) display, or another type of display. Display 126 may include a high definition display or an ultra high definition display. It should be noted that although in Figure 1 In the example shown, the video decoder 124 is described as outputting data to a display 126, but the video decoder 124 can be configured to output video data to various types of devices and / or subcomponents thereof. For example, the video decoder 124 can be configured to output video data to any communication medium, as described herein.

[0318] Figure 6 600 is a block diagram illustrating an example of a video decoder that can be configured to decode video data according to one or more techniques of the present disclosure. In one example, the video decoder 600 can be configured to decode transform data and reconstruct residual data from transform coefficients based on the decoded transform data. The video decoder 600 can be configured to perform intra-frame prediction decoding and inter-frame prediction decoding, and can therefore be referred to as a hybrid decoder. The video decoder 600 can be configured to parse any combination of the syntax elements described above in Tables 1 to 10. The video decoder 600 can perform video decoding based on the values ​​of the parsed syntax elements. For example, different video decoding techniques can be performed based on whether a picture belongs to a particular type.

[0319] exist Figure 6 In the example shown, the video decoder 600 includes an entropy decoding unit 602, an inverse quantization unit and a transform coefficient processing unit 604, an intra-frame prediction processing unit 606, an inter-frame prediction processing unit 608, an adder 610, a post-filter unit 612, and a reference buffer 614. The video decoder 600 can be configured to decode video data in a manner consistent with a video encoding system. It should be noted that although the exemplary video decoder 600 shown has different functional blocks, such illustrations are intended for descriptive purposes and do not limit the video decoder 600 and / or its subcomponents to a specific hardware or software architecture. The functionality of the video decoder 600 can be implemented using any combination of hardware, firmware, and / or software implementations.

[0320] like Figure 6As shown, the entropy decoding unit 602 receives an entropy-encoded bitstream. The entropy decoding unit 602 may be configured to decode syntax elements and quantized coefficients from the bitstream according to a process that is inverse to the entropy encoding process. The entropy decoding unit 602 may be configured to perform entropy decoding according to any of the entropy encoding techniques described above. The entropy decoding unit 602 may determine the values ​​of syntax elements in the encoded bitstream in a manner consistent with the video coding standard. Figure 6 As shown, the entropy decoding unit 602 can determine the quantization parameter, the quantization coefficient value, the transformation data and the prediction data from the bit stream. Figure 6 As shown, the inverse quantization unit and transform coefficient processing unit 604 receives the quantization parameters, quantization coefficient values, transform data and prediction data from the entropy decoding unit 602, and outputs reconstructed residual data.

[0321] See again Figure 6 , the reconstructed residual data may be provided to the adder 610. The adder 610 may add the reconstructed residual data to the predicted video block and generate the reconstructed video data. The predicted video block may be determined according to a predictive video technique, namely intra prediction and inter prediction. The intra prediction processing unit 606 may be configured to receive an intra prediction syntax element and retrieve the predicted video block from a reference buffer 614. The reference buffer 614 may include a memory device configured to store one or more frames of video data. The intra prediction syntax element may identify an intra prediction mode, such as the intra prediction mode described above. The inter prediction processing unit 608 may receive the inter prediction syntax element and generate a motion vector to identify a predicted block in one or more reference frames stored in the reference buffer 616. The inter prediction processing unit 608 may generate a motion compensation block, possibly performing interpolation based on an interpolation filter. An identifier of an interpolation filter for motion estimation with sub-pixel precision may be included in the syntax element. The inter prediction processing unit 608 may use an interpolation filter to calculate interpolated values ​​of sub-integer pixels of a reference block. The post-filter unit 614 may be configured to perform filtering on the reconstructed video data. For example, the post-filter unit 614 may be configured to perform deblocking and / or sample adaptive offset (SAO) filtering, for example based on parameters specified in the bitstream. Furthermore, it should be noted that in some examples, the post-filter unit 614 may be configured to perform dedicated arbitrary filtering (e.g., visual enhancement, such as mosquito noise removal). Figure 6As shown, the video decoder 600 can output a reconstructed video block. Thus, the video decoder 600 represents an example of a device configured to perform the following operations: parse a flag in a parameter set, the flag indicating that there is a syntax indicating a most significant bit period value of a picture order count in a slice header; conditionally parse the value of a syntax element indicating a most significant bit period value of a picture order count in a slice header based on the value of the flag in the parameter set; and determine the most significant bit period value of a picture order count.

[0322] In one or more examples, the functions may be implemented by hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or codes on or transmitted via a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media corresponding to tangible media such as data storage media, or propagation media including any medium that facilitates the transmission of a computer program from one place to another, for example, according to a communication protocol. Thus, computer-readable media may generally correspond to: (1) a non-transitory tangible computer-readable storage medium, or (2) a communication medium such as a signal or carrier wave. The data storage medium may be any available medium that can be accessed by one or more computers or one or more processors to retrieve instructions, codes, and / or data structures for implementing the techniques described in the present disclosure. A computer program product may include a computer-readable medium.

[0323] By way of example and not limitation, such computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, flash memory, or any other medium that can be used to store the required program code in the form of instructions or data structures and can be accessed by a computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave is used to transmit instructions from a website, server or other remote source, then the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of the medium. However, it should be understood that computer-readable storage media and data storage media do not include connections, carriers, signals or other transient media, but are directed to non-transient tangible storage media. As used herein, disks and optical disks include compact disks (CDs), laser disks, optical optical disks, digital versatile disks (DVDs), floppy disks and Blu-ray disks, wherein disks usually copy data magnetically, while optical disks use lasers to copy data optically. The above combination should also be included in the scope of computer-readable media.

[0324] Instructions may be executed by one or more processors such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Therefore, the term "processor" as used herein may refer to any of the aforementioned structures or any other structure suitable for implementing the techniques described herein. In addition, in some aspects, the functions described herein may be provided within dedicated hardware and / or software modules configured for encoding and decoding, or incorporated into a combined codec. Moreover, these techniques may be implemented entirely in one or more circuits or logic elements.

[0325] The techniques of the present disclosure may be implemented in a variety of devices or apparatuses including wireless handsets, integrated circuits (ICs), or a set of ICs (e.g., chipsets). Various components, modules, or units are described in the present disclosure to emphasize functional aspects of devices configured to perform the disclosed techniques, but do not necessarily need to be implemented by different hardware units. Instead, as described above, the various units may be combined in a codec hardware unit, or provided by a collection of interoperable hardware units including one or more processors as described above, in combination with appropriate software and / or firmware.

[0326] In addition, each functional block or various features of the base station equipment and terminal equipment used in each of the above-mentioned embodiments can be implemented or executed by a circuit (usually an integrated circuit or multiple integrated circuits). The circuit designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), a dedicated or general-purpose integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic devices, or discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or each of the above-mentioned circuits may be configured by a digital circuit, or may be configured by an analog circuit. In addition, when the technology of the integrated circuit that replaces the current integrated circuit appears due to the progress of semiconductor technology, the integrated circuit produced by the technology can also be used.

[0327] Various examples have been described. These and other examples are within the scope of the following claims.

[0328] <Cross Reference>

[0329] This non-provisional patent application claims priority under 35 U.S.C. §119 to provisional applications 62 / 692,839 filed on July 1, 2018, 62 / 739,059 filed on September 28, 2018, and 62 / 752,226 filed on October 29, 2018, the entire contents of which are hereby incorporated by reference.

Claims

1. A method for signaling picture count information for decoding a plurality of video pictures, It is characterized in that The method comprises: Send a picture order count POC most significant bit MSB first flag, the POC MSB first flag indicating the presence of a POC MSB second flag, wherein the POC MSB first flag is present in a sequence parameter set SPS; When the value of the POC MSB first flag present in the SPS is true, additionally sending a maximum POC MSB period minus one element specifying the length of the POC MSB period element; directly sending the first POC LSB value without additional conditions for the first POC least significant bit LSB value, wherein the length of the first POC LSB value is set based on the maximum POC LSB minus four log2_max_pic_order_cnt_lsb_minus4 value; sending the POC MSB second flag to indicate whether the POC MSB period element exists; and When the value of the POC MSB second flag is true, the POC MSB period element specifying the value of the POC MSB period is transmitted.

2. The method according to claim 1, It is characterized in that Sending the POC MSB first marker comprises sending the POC MSB first marker as a sequence parameter of the sequence of the plurality of video pictures; The sequence parameters are included in a sequence parameter set (SPS) header associated with the sequence of the plurality of video pictures; as well as The SPS header is specified in an SPS Raw Byte Sequence Payload (RBSP) syntax for the sequence of the plurality of video pictures.

3. The method according to claim 2, It is characterized in that The POC MSB second flag and the POC MSB period element are associated with a video picture in the sequence of the plurality of video pictures.

4. The method according to claim 1, It is characterized in that The POC MSB second flag is a POC MSB presence flag, and When the value of the POC MSB second flag is false, the POC MSB period element for specifying the value of the POC MSB period is not sent.

5. The method according to claim 1, It is characterized in that The POC MSB second marker is associated with the first video picture.

6. The method according to claim 5, It is characterized in that The method further comprises: sending another POC MSB second flag associated with the second video picture and indicating the absence of a POC MSB period element, and Sending the POC MSB period element for decoding a block of the second video picture is abandoned.

7. The method according to claim 1, It is characterized in that At least one of the plurality of flags or the periodic elements is used by a decoder to decode a video picture in the sequence of the plurality of video pictures.

8. The method according to claim 7, It is characterized in that The POC MSB period is used by the decoder to calculate the POC MSB value, and The POC MSB value is combined with the first POC LSB value to generate a POC value used to decode a first video picture.

9. The method according to claim 7, It is characterized in that When the POC MSB period element is not transmitted, the decoder derives a POC value based on the first POC LSB value and a first variable, and The first variable is equal to the second POC LSB value of the previous picture in decoding order.

10. The method according to claim 1, It is characterized in that The POC MSB period element is a variable length element, wherein the length of the POC MSB period element is based on the value of at least one other element.

11. A device for signaling picture count information for decoding a video picture, It is characterized in that The device comprises: at least one processor; and a storage device, coupled to the at least one processor and storing a plurality of instructions, which, when executed by the at least one processor, cause the at least one processor to: Send a picture order count POC most significant bit MSB first flag, the POC MSB first flag indicating the presence of a POC MSB second flag, wherein the POC MSB first flag is present in a sequence parameter set SPS; When the value of the POC MSB first flag present in the SPS is true, additionally sending a maximum POC MSB period minus one element specifying the length of the POC MSB period element; directly sending the first POC LSB value without additional conditions for the first POC least significant bit LSB value, wherein the length of the first POC LSB value is set based on the maximum POC LSB minus four log2_max_pic_order_cnt_lsb_minus4 value; sending the POC MSB second flag to indicate whether the POC MSB period element exists; and When the value of the POC MSB second flag is true, the POC MSB period element specifying the value of the POC MSB period is transmitted.