Sub-block MV inheritance between color components

Information

  • Patent Grant
  • 11659192
  • Patent Number
    11,659,192
  • Date Filed
    Friday, April 2, 2021
    3 years ago
  • Date Issued
    Tuesday, May 23, 2023
    a year ago
Abstract
Devices, systems and methods for sub-block based prediction are described. In a representative aspect, a method for video processing includes partitioning a first component of a current video block into a first set of sub-blocks and partitioning a second component of the current video block into a second set of sub-blocks. A sub-block of the second component corresponds to one or more sub-blocks of the first component. The method also includes deriving, based on a color format of the current video block, motion vectors for a sub-block of the second component based on motion vectors for one or more corresponding sub-blocks of the first color component.
Description
TECHNICAL FIELD

This patent document is directed generally to image and video coding technologies.


BACKGROUND

Motion compensation is a technique in video processing to predict a frame in a video, given the previous and/or future frames by accounting for motion of the camera and/or objects in the video. Motion compensation can be used in the encoding and decoding of video data for video compression.


SUMMARY

Devices, systems and methods related to sub-block based prediction for image and video coding are described.


In one representative aspect, the disclosed technology may be used to provide a method for video encoding. This method includes partitioning a first component of a current video block into a first set of sub-blocks and partitioning a second component of the current video block into a second set of sub-blocks. A sub-block of the second component corresponds to one or more sub-blocks of the first component. The method also includes deriving, based on a color format of the current video block, motion vectors for the sub-block of the second component based on motion vectors for one or more corresponding sub-blocks of the first color component.


In another representative aspect, the disclosed technology may be used to provide a method for video decoding. The method includes receiving a block of video data that comprises a first component and at least a second component. The first component is partitioned into a first set of sub-blocks and the second component is partitioned into a second set of sub-blocks. A sub-block of the second component corresponds to one or more sub-blocks of the first component. The method includes deriving, based on a color format of the block of video data, motion vectors for a sub-block of the second component based on motion vectors for one or more corresponding sub-blocks of the first color component. The method also includes reconstructing, based on the derived motion vectors, the block of video data or decoding other blocks of video data in a same picture.


In yet another representative aspect, the above-described method is embodied in the form of processor-executable code and stored in a computer-readable program medium.


In yet another representative aspect, a device that is configured or operable to perform the above-described method is disclosed. The device may include a processor that is programmed to implement this method.


In yet another representative aspect, a video encoder or a video decoder apparatus may implement a method as described herein.


The above and other aspects and features of the disclosed technology are described in greater detail in the drawings, the description and the claims.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows an example of sub-block based prediction.



FIG. 2 shows an example of a simplified affine motion model.



FIG. 3 shows an example of an affine motion vector field (MVF) per sub-block.



FIG. 4 shows an example of motion prediction using the alternative temporal motion vector prediction (ATMVP) algorithm for a coding unit (CU).



FIG. 5 shows an example of one CU with four sub-blocks and neighboring blocks.



FIG. 6 shows an example of an optical flow trajectory used by the bi-directional optical flow (BIO) algorithm.



FIG. 7 shows an example of bilateral matching in the frame-rate up conversion (FRUC) algorithm.



FIG. 8 shows an example of template matching in the FRUC algorithm.



FIG. 9 shows an example of unilateral Motion Estimation (ME) in the FRUC method.



FIG. 10 shows an example of deriving a motion vector (MV) of a component for sub-blocks in the 4:2:0 format in accordance with the present technology.



FIG. 11 shows another example of deriving an MV of a component for sub-blocks in the 4:2:0 format in accordance with the present technology.



FIG. 12 shows yet another example of deriving an MV of a component for sub-blocks in accordance with the present technology.



FIG. 13 is a flowchart of an example method for video encoding in accordance with one or more embodiments of the present technology.



FIG. 14 is a flowchart of another example method for video encoding in accordance with one or more embodiments of the present technology.



FIG. 15 is a block diagram illustrating an example encoding apparatus that can be utilized to implement various portions of the presently disclosed technology.



FIG. 16 is a block diagram illustrating an example encoding apparatus that can be utilized to implement various portions of the presently disclosed technology.



FIG. 17 is a block diagram illustrating an example of the architecture for a computer system or other control device that can be utilized to implement various portions of the presently disclosed technology.



FIG. 18 shows a block diagram of an example embodiment of a mobile device that can be utilized to implement various portions of the presently disclosed technology.





DETAILED DESCRIPTION

Due to the increasing demand of higher resolution video, video coding methods and techniques are ubiquitous in modern technology. Video codecs typically include an electronic circuit or software that compresses or decompresses digital video, and are continually being improved to provide higher coding efficiency. A video codec converts uncompressed video to a compressed format or vice versa. There are complex relationships between the video quality, the amount of data used to represent the video (determined by the bit rate), the complexity of the encoding and decoding algorithms, sensitivity to data losses and errors, ease of editing, random access, and end-to-end delay (latency). The compressed format usually conforms to a standard video compression specification, e.g., the High Efficiency Video Coding (HEVC) standard (also known as H.265 or MPEG-H Part 2), the Versatile Video Coding standard to be finalized, or other current and/or future video coding standards.


Sub-block based prediction is first introduced into the video coding standard by the High Efficiency Video Coding (HEVC) standard. With sub-block based prediction, a block, such as a Coding Unit (CU) or a Prediction Unit (PU), is divided into several non-overlapped sub-blocks. Different sub-blocks may be assigned different motion information, such as reference index or motion vector (MV), and motion compensation (MC) is performed individually for each sub-block. FIG. 1 shows an example of sub-block based prediction.


Embodiments of the disclosed technology may be applied to existing video coding standards (e.g., HEVC, H.265) and future standards to improve runtime performance. Section headings are used in the present document to improve readability of the description and do not in any way limit the discussion or the embodiments (and/or implementations) to the respective sections only.


Future video coding technologies are explored using a reference software known as the Joint Exploration Model (JEM). In JEM, sub-block based prediction is adopted in several coding tools, such as affine prediction, alternative temporal motion vector prediction (ATMVP), spatial-temporal motion vector prediction (STMVP), bi-directional optical flow (BIO), Frame-Rate Up Conversion (FRUC), Locally Adaptive Motion Vector Resolution (LAMVR), Overlapped Block Motion Compensation (OBMC), Local Illumination Compensation (LIC), and Decoder-side Motion Vector Refinement (DMVR).


In HEVC, only a translation motion model is applied for motion compensation prediction (MCP). However, the camera and objects may have many kinds of motion, e.g. zoom in/out, rotation, perspective motions, and/or other irregular motions. JEM, on the other hand, applies a simplified affine transform motion compensation prediction. FIG. 2 shows an example of an affine motion field of a block 200 described by two control point motion vectors V0 and V1. The motion vector field (MVF) of the block 200 can be described by the following equation:









{





v
x

=




(


v

1

x


-

v

0

x



)

w


x

-



(


v

1

y


-

v

0

y



)

w


y

+

v

0

x










v
y

=




(


v

1

y


-

v

0

y



)

w


x

+



(


v

1

x


-

v

0

x



)

w


y

+

v

0

y











Eq
.





(
1
)









FIG. 3 shows an example of affine MVF per sub-block for a block 300. To derive motion vector of each M×N sub-block, the motion vector of the center sample of each sub-block can be calculated according to Eq. (1), and rounded to the motion vector fraction accuracy (e.g., 1/16 in JEM). Then the motion compensation interpolation filters can be applied to generate the prediction of each sub-block with derived motion vector. After the MCP, the high accuracy motion vector of each sub-block is rounded and saved as the same accuracy as the normal motion vector.


In the JEM, there are two affine motion modes: AF_INTER mode and AF_MERGE mode. For CUs with both width and height larger than 8, AF_INTER mode can be applied. An affine flag in CU level is signaled in the bitstream to indicate whether AF_INTER mode is used. In the AF_INTER mode, a candidate list with motion vector pair {(v0, v1)|v0={vA, vB, vc}, v1={vD,vE}} is constructed using the neighboring blocks.


In JEM, the non-merge affine mode can be used only when the width and the height of the current block are both larger than 8; the merge affine mode can be used only when the area (i.e. width×height) of the current block is not smaller than 64.



FIG. 4 shows an example of alternative temporal motion vector prediction (ATMVP) motion prediction process for a CU 400. The ATMVP method predicts the motion vectors of the sub-CUs 401 within a CU 400 in two steps. The first step is to identify the corresponding block 451 in a reference picture 450 with a temporal vector. The reference picture 450 is also referred to as the motion source picture. The second step is to split the current CU 400 into sub-CUs 401 and obtain the motion vectors as well as the reference indices of each sub-CU from the block corresponding to each sub-CU.


In the first step, a reference picture 450 and the corresponding block is determined by the motion information of the spatial neighboring blocks of the current CU 400. In the second step, a corresponding block of the sub-CU 451 is identified by the temporal vector in the motion source picture 450, by adding to the coordinate of the current CU the temporal vector. For each sub-CU, the motion information of its corresponding block (e.g., the smallest motion grid that covers the center sample) is used to derive the motion information for the sub-CU. After the motion information of a corresponding N×N block is identified, it is converted to the motion vectors and reference indices of the current sub-CU, in the same way as TMVP of HEVC, wherein motion scaling and other procedures apply.


In the Spatial-Temporal Motion Vector Prediction (STMVP) method, the motion vectors of the sub-CUs are derived recursively, following raster scan order. FIG. 5 shows an example of one CU with four sub-blocks and neighboring blocks. Consider an 8×8 CU 500 that includes four 4×4 sub-CUs A (501), B (502), C (503), and D (504). The neighboring 4×4 blocks in the current frame are labelled as a (511), b (512), c (513), and d (514).


The motion derivation for sub-CU A starts by identifying its two spatial neighbors. The first neighbor is the N×N block above sub-CU A 501 (block c 513). If this block c (513) is not available or is intra coded the other N×N blocks above sub-CU A (501) are checked (from left to right, starting at block c 513). The second neighbor is a block to the left of the sub-CU A 501 (block b 512). If block b (512) is not available or is intra coded other blocks to the left of sub-CU A 501 are checked (from top to bottom, staring at block b 512). The motion information obtained from the neighboring blocks for each list is scaled to the first reference frame for a given list. Next, temporal motion vector predictor (TMVP) of sub-block A 501 is derived by following the same procedure of TMVP derivation as specified in HEVC. The motion information of the collocated block at block D 704 is fetched and scaled accordingly. Finally, after retrieving and scaling the motion information, all available motion vectors are averaged separately for each reference list. The averaged motion vector is assigned as the motion vector of the current sub-CU.


The bi-directional optical flow (BIO) method is a sample-wise motion refinement performed on top of block-wise motion compensation for bi-prediction. In some implementations, the sample-level motion refinement does not use signaling.


Let I(k) be the luma value from reference k (k=0, 1) after block motion compensation, and ∂I(k)/∂x, ∂I(k)/∂y are horizontal and vertical components of the I(k) gradient, respectively. Assuming the optical flow is valid, the motion vector field (vx, vy) is given by:

I(k)/∂t+vx∂I(k)/∂x+vy∂I(k)/∂y=0.  Eq. (2)


Combining this optical flow equation with Hermite interpolation for the motion trajectory of each sample results in a unique third-order polynomial that matches both the function values I(k) and ∂I(k)/∂x, ∂I(k)/∂y derivatives at the ends. The value of this polynomial at t=0 is the BIO prediction:

preBIO=½·(I(0)+I(1)+vX/2·(τ1∂I(1)/∂x−τ0∂I(0)/∂x)+vy/2·(τ1∂I(1)/∂y−τ0∂I(0)/∂y)).  Eq. (3)



FIG. 6 shows an example optical flow trajectory in the Bi-directional Optical flow (BIO) method. Here, τ0 and τ1 denote the distances to the reference frames. Distances τ0 and τ1 are calculated based on POC for Ref0 and Ref1: τ0=POC(current)−POC(Ref0), τ1=POC(Ref1)−POC(current). If both predictions come from the same time direction (either both from the past or both from the future) then the signs are different (e.g., τ0·τ1<0). In this case, BIO is applied if the prediction is not from the same time moment (e.g., τ0≠τ1). Both referenced regions have non-zero motion (e.g., MVx0, MVy0, MVx1, MVy1≠0) and the block motion vectors are proportional to the time distance (e.g., MVx0/MVx1=MVy0/MVy1=−τ01). In the JEM, BIO can be applied to all bi-predicted blocks when the two predictions are from different reference pictures. When Local Illumination Compensation (LIC) is enabled for a CU, BIO can be disabled.


In some cases, a FRUC flag can be signaled for a CU when its merge flag is true. When the FRUC flag is false, a merge index can be signaled and the regular merge mode is used. When the FRUC flag is true, an additional FRUC mode flag can be signaled to indicate which method (e.g., bilateral matching or template matching) is to be used to derive motion information for the block.


At the encoder side, the decision on whether using FRUC merge mode for a CU is based on RD cost selection as done for normal merge candidate. For example, multiple matching modes (e.g., bilateral matching and template matching) are checked for a CU by using RD cost selection. The one leading to the minimal cost is further compared to other CU modes. If a FRUC matching mode is the most efficient one, FRUC flag is set to true for the CU and the related matching mode is used.


Typically, motion derivation process in FRUC merge mode has two steps: a CU-level motion search is first performed, then followed by a Sub-CU level motion refinement. At CU level, an initial motion vector is derived for the whole CU based on bilateral matching or template matching. First, a list of MV candidates is generated and the candidate that leads to the minimum matching cost is selected as the starting point for further CU level refinement. Then a local search based on bilateral matching or template matching around the starting point is performed. The MV results in the minimum matching cost is taken as the MV for the whole CU. Subsequently, the motion information is further refined at sub-CU level with the derived CU motion vectors as the starting points.



FIG. 7 shows an example of bilateral matching used in the Frame-Rate Up Conversion (FRUC) method. The bilateral matching is used to derive motion information of the current CU by finding the closest match between two blocks along the motion trajectory of the current CU (700) in two different reference pictures (710, 711). Under the assumption of continuous motion trajectory, the motion vectors MV0 (701) and MV1 (702) pointing to the two reference blocks are proportional to the temporal distances, e.g., TD0 (703) and TD1 (704), between the current picture and the two reference pictures. In some embodiments, when the current picture 700 is temporally between the two reference pictures (710, 711) and the temporal distance from the current picture to the two reference pictures is the same, the bilateral matching becomes mirror based bi-directional MV.



FIG. 8 shows an example of template matching used in the Frame-Rate Up Conversion (FRUC) method. Template matching can be used to derive motion information of the current CU 800 by finding the closest match between a template (e.g., top and/or left neighboring blocks of the current CU) in the current picture and a block (e.g., same size to the template) in a reference picture 810. Except the aforementioned FRUC merge mode, the template matching can also be applied to AMVP mode. In both JEM and HEVC, AMVP has two candidates. With the template matching method, a new candidate can be derived. If the newly derived candidate by template matching is different to the first existing AMVP candidate, it is inserted at the very beginning of the AMVP candidate list and then the list size is set to two (e.g., by removing the second existing AMVP candidate). When applied to AMVP mode, only CU level search is applied.


The MV candidate set at CU level can include the following: (1) original AMVP candidates if the current CU is in AMVP mode, (2) all merge candidates, (3) several MVs in the interpolated MV field (described later), and/or (4) top and left neighboring motion vectors.


When using bilateral matching, each valid MV of a merge candidate can be used as an input to generate a MV pair with the assumption of bilateral matching. For example, one valid MV of a merge candidate is (MVa, refa) at reference list A. Then the reference picture refb of its paired bilateral MV is found in the other reference list B so that refa and refb are temporally at different sides of the current picture. If such a refb is not available in reference list B, refb is determined as a reference which is different from refa and its temporal distance to the current picture is the minimal one in list B. After refb is determined, MVb is derived by scaling MVa based on the temporal distance between the current picture and refa, refb.


In some implementations, four MVs from the interpolated MV field can also be added to the CU level candidate list. More specifically, the interpolated MVs at the position (0, 0), (W/2, 0), (0, H/2) and (W/2, H/2) of the current CU are added. When FRUC is applied in AMVP mode, the original AMVP candidates are also added to CU level MV candidate set. In some implementations, at the CU level, 15 MVs for AMVP CUs and 13 MVs for merge CUs can be added to the candidate list.


The MV candidate set at sub-CU level includes an MV determined from a CU-level search, (2) top, left, top-left and top-right neighboring MVs, (3) scaled versions of collocated MVs from reference pictures, (4) one or more ATMVP candidates (e.g., up to four), and/or (5) one or more STMVP candidates (e.g., up to four). The scaled MVs from reference pictures are derived as follows. The reference pictures in both lists are traversed. The MVs at a collocated position of the sub-CU in a reference picture are scaled to the reference of the starting CU-level MV. ATMVP and STMVP candidates can be the four first ones. At the sub-CU level, one or more MVs (e.g., up to 17) are added to the candidate list.


Before coding a frame, interpolated motion field is generated for the whole picture based on unilateral ME. Then the motion field may be used later as CU level or sub-CU level MV candidates.


In some embodiments, the motion field of each reference pictures in both reference lists is traversed at 4×4 block level. FIG. 9 shows an example of unilateral Motion Estimation (ME) 900 in the FRUC method. For each 4×4 block, if the motion associated to the block passing through a 4×4 block in the current picture and the block has not been assigned any interpolated motion, the motion of the reference block is scaled to the current picture according to the temporal distance TD0 and TD1 (the same way as that of MV scaling of TMVP in HEVC) and the scaled motion is assigned to the block in the current frame. If no scaled MV is assigned to a 4×4 block, the block's motion is marked as unavailable in the interpolated motion field.


When a motion vector points to a fractional sample position, motion compensated interpolation is needed. To reduce complexity, bi-linear interpolation instead of regular 8-tap HEVC interpolation can be used for both bilateral matching and template matching.


The calculation of matching cost is a bit different at different steps. When selecting the candidate from the candidate set at the CU level, the matching cost can be the absolute sum difference (SAD) of bilateral matching or template matching. After the starting MV is determined, the matching cost C of bilateral matching at sub-CU level search is calculated as follows:

C=SAD+w·(|MVx−MVxs|+|MVy−MVys|)  Eq. (4)


Here, w is a weighting factor. In some embodiments, w can be empirically set to 4. MV and MVs indicate the current MV and the starting MV, respectively. SAD may still be used as the matching cost of template matching at sub-CU level search.


In FRUC mode, MV is derived by using luma samples only. The derived motion will be used for both luma and chroma for MC inter prediction. After MV is decided, final MC is performed using 8-taps interpolation filter for luma and 4-taps interpolation filter for chroma.


MV refinement is a pattern based MV search with the criterion of bilateral matching cost or template matching cost. In the JEM, two search patterns are supported—an unrestricted center-biased diamond search (UCBDS) and an adaptive cross search for MV refinement at the CU level and sub-CU level, respectively. For both CU and sub-CU level MV refinement, the MV is directly searched at quarter luma sample MV accuracy, and this is followed by one-eighth luma sample MV refinement. The search range of MV refinement for the CU and sub-CU step are set equal to 8 luma samples.


In the bilateral matching merge mode, bi-prediction is applied because the motion information of a CU is derived based on the closest match between two blocks along the motion trajectory of the current CU in two different reference pictures. In the template matching merge mode, the encoder can choose among uni-prediction from list0, uni-prediction from list1, or bi-prediction for a CU. The selection ca be based on a template matching cost as follows:


If costBi<=factor*min (cost0, cost1)

    • bi-prediction is used;
    • Otherwise, if cost0<=cost1
    • uni-prediction from list0 is used;
    • Otherwise,
    • uni-prediction from list1 is used;


Here, cost0 is the SAD of list0 template matching, cost1 is the SAD of list1 template matching and costBi is the SAD of bi-prediction template matching. For example, when the value of factor is equal to 1.25, it means that the selection process is biased toward bi-prediction. The inter prediction direction selection can be applied to the CU-level template matching process.


Human visual system is less sensitive to the position and motion of color than luminance. Thus, bandwidth can be optimized by storing more luminance detail than color detail. In video systems, this is achieved by using color difference components. The signal is divided into a luma (Y′) component and two color difference (chroma) components. Chroma subsampling is the practice of encoding images by implementing less resolution for chroma information than for luma information, taking advantage of the human visual system's lower acuity for color differences than for luminance. For example, common types of subsampling include 4:2:2 (the two chroma components are sampled at half the sample rate of luma), 4:1:1 (the horizontal color resolution is quartered), and 4:2:0 (the vertical resolution is halved as compared to 4:1:1 because the Cb and Cr channels are only sampled on each alternate line). In an example, the HEVC standard defines how to derive the MV used for MC in chroma components (noted as mvC) from the MV used for MC in the luma component (noted as mv). Generally speaking, mvC is calculated as mv multiplying a factor, which relies on the color format, such as 4:2:0 or 4:2:2.


Intra block copy (IBC, or intra picture block compensation), also named current picture referencing (CPR) was adopted in HEVC screen content coding extensions (SCC). This tool is very efficient for coding of screen content video in that repeated patterns in text and graphics rich content occur frequently within the same picture. Having a previously reconstructed block with equal or similar pattern as a predictor can effectively reduce the prediction error and therefore improve coding efficiency.


Similar to the design of CRP in HEVC SCC, In VVC, the use of the IBC mode is signaled at both sequence and picture level. When the IBC mode is enabled at sequence parameter set (SPS), it can be enabled at picture level. When the IBC mode is enabled at picture level, the current reconstructed picture is treated as a reference picture. Therefore, no syntax change on block level is needed on top of the existing VVC inter mode to signal the use of the IBC mode.


Features of IBC mode include the following:

    • It is treated as a normal inter mode. Therefore, merge and skip modes are also available for the IBC mode. The merge candidate list construction is unified, containing merge candidates from the neighboring positions that are either coded in the IBC mode or the HEVC inter mode. Depending on the selected merge index, the current block under merge or skip mode can merge into either an IBC mode coded neighbor or otherwise an normal inter mode coded one with different pictures as reference pictures.
    • Block vector prediction and coding schemes for the IBC mode reuse the schemes used for motion vector prediction and coding in the HEVC inter mode (AMVP and MVD coding).
    • The motion vector for the IBC mode, also referred as block vector, is coded with integer-pel precision, but stored in memory in 1/16-pel precision after decoding as quarter-pel precision is required in interpolation and deblocking stages. When used in motion vector prediction for the IBC mode, the stored vector predictor will be right shifted by 4.
    • Search range: it is restricted to be within the current CTU.
    • CPR is disallowed when affine mode/triangular mode/GBI/weighted prediction is enabled.


In some cases, pairwise average candidates are generated by averaging predefined pairs of candidates in the current merge candidate list, and the predefined pairs are defined as {(0, 1), (0, 2), (1, 2), (0, 3), (1, 3), (2, 3)}, where the numbers denote the merge indices to the merge candidate list. The averaged motion vectors are calculated separately for each reference list. If both motion vectors are available in one list, these two motion vectors are averaged even when they point to different reference pictures; if only one motion vector is available, use the one directly; if no motion vector is available, keep this list invalid. The pairwise average candidates replaces the combined candidates in HEVC standard. Suppose the MVs of two merge candidates are MV0=(MV0x, MV0y) and MV1=(MV1x, MV1y), then the MV of the pairwise merge candidate denoted as MV*=(MV*x, MV*y) is derived as

MV*x=(MV0x+MV1x)/2, and
MV*y=(MV0y+MV1y)/2.


In addition, when MV0 and MV1 refer to the current picture (i.e., CPR mode), MV*x and MV*y are further rounded to remove the part with a higher precision than full pixel to make sure the integer MV is obtained:

MV*x=(MV*x/16)<<4, and
MV*y=(MV*y/16)<<4.


It is noted that for each pair, if one of the two is coded with CPR and the other is not, such pair is disallowed to generate the pairwise average candidate.


The concept of the triangular prediction mode (TPM) is to introduce a new triangular partition for motion compensated prediction. It splits a CU into two triangular prediction units, in either diagonal or inverse diagonal direction. Each triangular prediction unit in the CU is inter-predicted using its own uni-prediction motion vector and reference frame index which are derived from a single uni-prediction candidate list. An adaptive weighting process is performed to the diagonal edge after predicting the triangular prediction units. Then, the transform and quantization process are applied to the whole CU. It is noted that this mode is only applied to merge mode (note: skip mode is treated as a special merge mode). Uni-prediction candidate list for TPM.


The uni-prediction candidate list, named TPM motion candidate list, consists of five uni-prediction motion vector candidates. It is derived from seven neighboring blocks including five spatial neighboring blocks and two temporal co-located blocks. The motion vectors of the seven neighboring blocks are collected and put into the uni-prediction candidate list according in the order of uni-prediction motion vectors, L0 motion vector of bi-prediction motion vectors, L1 motion vector of bi-prediction motion vectors, and averaged motion vector of the L0 and L1 motion vectors of bi-prediction motion vectors. If the number of candidates is less than five, zero motion vector is added to the list. Motion candidates added in this list for TPM are called TPM candidates, motion information derived from spatial/temporal blocks are called regular motion candidates.


More specifically, the following steps are involved:


(1) Obtain regular motion candidates from A1, B1, B0, A0, B2, Col and Col2 (similar as those in the regular merge mode) without any pruning operations.


(2) Set variable numCurrMergeCand=0


(3) For each regular motion candidates derived from A1, B1, B0, A0, B2, Col and Col2 and numCurrMergeCand is less than 5, if the regular motion candidate is uni-prediction (either from List 0 or List 1), it is directly added to the merge list as an TPM candidate with numCurrMergeCand increased by 1. Such a TPM candidate is named “originally uni-predicted candidate”.


Full pruning is applied.


(4) For each motion candidates derived from A1, B1, B0, A0, B2, Col and Col2 and numCurrMergeCand is less than 5, if the regular motion candidate is bi-prediction, the motion information from List 0 is added to the TPM merge list (that is, modified to be uni-prediction from List 0) as a new TPM candidate and numCurrMergeCand increased by 1. Such a TPM candidate is named ‘Truncated List0-predicted candidate’.


Full pruning is applied.


(5) For each motion candidates derived from A1, B1, B0, A0, B2, Col and Col2 and numCurrMergeCand is less than 5, if the regular motion candidate is bi-prediction, the motion information from List 1 is added to the TPM merge list (that is, modified to be uni-prediction from List 1) and numCurrMergeCand increased by 1. Such a TPM candidate is named ‘Truncated List1-predicted candidate’.


Full pruning is applied.


(6) For each motion candidates derived from A1, B1, B0, A0, B2, Col and Col2 and numCurrMergeCand is less than 5, if the regular motion candidate is bi-prediction, the motion information of List 1 is firstly scaled to List 0 reference picture, and the average of the two MVs (one is from original List 0, and the other is the scaled MV from List 1) is added to the TPM merge list, such a candidate is called averaged uni-prediction from List 0 motion candidate and numCurrMergeCand increased by 1.


Full pruning is applied.


(7) If numCurrMergeCand is less than 5, zero motion vector candidates are added.


When inserting a candidate to the list, if it has to be compared to all previously added candidates to see whether it is identical to one of them, such a process is called full pruning.


Assume the scaled MV denoted by (MV1′x, MV1′y) and the List 0 MV by (MV0x, MV0y). The averaged uni-prediction from List 0 motion candidate denoted by (MV*x, MV*y) is defined as:

MV*x=(MV0x+MV1′x+1)>>1, and
MV*y=(MV0y+MV1′y+1)>>1.


In some existing implementations, such as the affine prediction in JEM, MVs of each sub-block are calculated with the affine model as shown in Eq. (1) independently for each component, which may result in misalignment of motion vectors between luma and chroma components. Multiple calculations for the components also result in coding inefficiency. In some other existing implementations, the motion vector averaging operation to derive the pairwise merge candidate/averaged uni-prediction from List 0 motion candidate need to be aligned with the rounding method used in the sub-block prediction. It is thus desirable to obtain a unified design.


This patent document discloses techniques that can be implemented in various embodiments to calculate the MV of a sub-block of one component (e.g., a chroma component) from MV(s) of one or more sub-blocks of another component (e.g., a luma component). The disclosed techniques eliminate the need to determining MV(s) of different components multiple times, thereby improving video coding efficiency. The disclosed techniques also introduce a unified design with respect to the averaging operation and the round method.


The use of such techniques is elucidated in the following examples described for various implementations. In the following examples, which should not be construed to be limiting, Shift (x, s) is defined as Shift(x, s)=(x+off)>>s, and

    • SignShift (x, s) is defined as:







SignShift






(

x
,
s

)


=

{






(

x
+
off

)





>>
s




x

0






-

(


(


-
x

+
off

)





>>
s

)





x
<
0




.






Herein, off is an integer, e.g. 0 or 1<<(s−1).


In some embodiments, the MV of a sub-block of one component can be derived based on the MV(s) of one or more sub-blocks of another component. Here, the MV(s) of one or more sub-blocks of another component has (have) already been derived with the affine model. This way, there is no need to derive motion information multiple times.


In some embodiments, the HEVC standard defines how to derive the MV in chroma components (noted as mvC) from the MV used for MC in the luma component (noted as mv). Generally speaking, mvC is calculated as mv multiplying a factor, which relies on the color format, such as 4:2:0 or 4:2:2. FIG. 10 shows an example of deriving an MV of a component for sub-blocks in the 4:2:0 format in accordance with the present technology. In this example, the block size is 16×16 for Y (luma component) and 8×8 for Cb/Cr (chroma components). The sub-block size of the luma component is 4×4, while the sub-block size of the chroma components is 2×2. A MV* is first derived for a 4×4 sub-block in the Y component. The MVs of the 2×2 sub-block in the Cb and/or Cr components can be derived based on MV*. In this specific example, the value of MV* is copied first, and the MV(s) of the 2×2 sub-block in the Cb and/or Cr component(s) are calculated based on MV* according to the HEVC standard.



FIG. 11 shows another example of deriving an MV of a component for sub-blocks in the 4:2:0 format in accordance with the present technology. In this example, the block size is 16×16 for the luma component and 8×8 for a chroma component. The sub-block size of all the components is 4×4. A 4×4 sub-block in the Cb or Cr component corresponds to four 4×4 sub-block in the Y component. A MV* for the luma component is first calculated. The MV of the 4×4 sub-block in the Cb or Cr component is then derived based on MV* according to the HEVC standard.


In some embodiments, MV* is calculated as the average of all corresponding sub-block MVs in the Y component: MV*=(MV0+MV1+MV2+MV3)/4. Suppose MV*=(MV*x, MV*y), MV0=(MV0x, MV0y), MV1=(MV1x, MV1y), MV2=(MV2x, MV2y) and MV3=(MV3x, MV3y).


In some embodiments, MV*x=Shift (MV0x+MV1x+MV2x+MV3x, 2), MV*y=Shift (MV0y+MV1y+MV2y+MV3y, 2). In some embodiments, MV*x=SignShift (MV0x+MV1x+MV2x+MV3x, 2), MV*y=SignShift (MV0y+MV1y+MV2y+MV3y, 2).


In some embodiments, the calculation of MV* can be performed using the following operations:


1.a MV′x=Shift (MV0x+MV1x, 1),


1.b MV′y=Shift (MV0y+MV1y, 1),


1.c MV″x=Shift (MV2x+MV3x, 1),


1.d MV″y=Shift (MV2y+MV3y, 1),


1.e MV*x=Shift (MV′x+MV″x, 1), and


1.f MV*y=Shift (MV′y+MV″y, 1).


In some embodiments, the calculation of MV* can be performed using the following operations:


2.a MV′x=Shift (MV0x+MV2x, 1),


2.b MV′y=Shift (MV0y+MV2y, 1),


2.c MV″x=Shift (MV1x+MV3x, 1),


2.d MV″y=Shift (MV1y+MV3y, 1),


2.e MV*x=Shift (MV′x+MV″x, 1), and


2.f MV*y=Shift (MV′y+MV″y, 1).


In some embodiments, the calculation of MV* can be performed using the following operations:


3.a MV′x=SignShift (MV0x+MV1x, 1),


3.b MV′y=SignShift (MV0y+MV1y, 1),


3.c MV″x=SignShift (MV2x+MV3x, 1),


3.d MV″y=SignShift (MV2y+MV3y, 1),


3.e MV*x=SignShift (MV′x+MV″x, 1), and


3.f MV*y=SignShift (MV′y+MV″y, 1).


In some embodiments, the calculation of MV* can be performed using the following operations:


4.a MV′x=SignShift (MV0x+MV2x, 1),


4.b MV′y=SignShift (MV0y+MV2y, 1),


4.c MV″x=SignShift (MV1x+MV3x, 1),


4.d MV″y=SignShift (MV1y+MV3y, 1),


4.e MV*x=SignShift (MV′x+MV″x, 1), and


4.f MV*y=SignShift (MV′y+MV″y, 1).


In some embodiments, MV* is calculated based on the MV of top-left sub-block in the Y component (e.g., MV0 as shown in FIG. 11). In some embodiments, MV* is calculated based on the MV of center sub-block in the Y component. In some embodiments, MV* is calculated based on the median MVs of all corresponding sub-blocks in the Y component. In this specific example shown in FIG. 11, MV*=median (MV0, MV1, MV2, MV3).


In some embodiments, the derivation of MVs of sub-blocks for color components can be determined based on the color format, such as 4:2:0, 4:2:2 and/or 4:4:4. For example, when the color format is 4:4:4, no subsampling occurs. The sub-block sizes and the number of sub-blocks in a block of video data are the same for all components. The MV of a sub-block in one component is the same as the MV of a corresponding sub-block in another component.


As another example, when the color format is 4:2:2. the sub-block sizes can be the same for all components, while the number of blocks can be different for different components. A MV* for the luma component is first calculated based on the MVs of several corresponding sub-blocks. The MV(s) of the corresponding sub-block in the Cb or Cr component is then derived from MV*.



FIG. 12 shows yet another example of deriving an MV of a component for sub-blocks in accordance with the present technology. In this example, the block size is 16×16 for the luma component and 8×16 for the chroma components. The sub-block size of all the components is 4×4. A 4×4 sub-block in the Cb or Cr component corresponds to two 4×4 sub-block in the Y component. A MV* for the luma component is first calculated. The MV of the 4×4 sub-block in the Cb or Cr component is then derived based on MV* according to the HEVC standard.


In some embodiments, MV* is calculated as the average of all corresponding sub-block MVs in the Y component: MV*=(MV0+MV1)/2. Suppose MV*=(MV*x, MV*y), MV0=(MV0x, MV0y), MV1=(MV1x, MV1y),


In some embodiments, MV*x=Shift (MV0x+MV1x, 1), MV*y=Shift (MV0y+MV1y, 1). In some embodiments, MV*x=SignShift (MV0x+MV1x, 1), MV*y=SignShift (MV0y+MV1y, 1).



FIG. 13 is a flowchart of an example method 1300 for video encoding in accordance with one or more embodiments of the present technology. The method 1300 includes, at operation 1310, partitioning a first component of a current video block into a first set of sub-blocks. The method 1300 includes, at operation 1320, partitioning a second component of the current video block into a second set of sub-blocks. A sub-block of the second component corresponds to one or more sub-blocks of the first component. The method 1300 also includes, at operation 1330, deriving, based on a color format of the current video block, motion vectors for a sub-block of the second component based on motion vectors for one or more corresponding sub-blocks of the first color component.



FIG. 14 is a flowchart of another example method 1400 for video encoding in accordance with one or more embodiments of the present technology. The method 1400 includes, at operation 1410, receiving a block of video data that comprises a first component and at least a second component. The first component is partitioned into a first set of sub-blocks and the second component is partitioned into a second set of sub-blocks. A sub-block of the second component corresponds to one or more sub-blocks of the first component. The method 1400 includes, at operation 1420, deriving, based on a color format of the block of video data, motion vectors for a sub-block of the second component based on motion vectors for one or more corresponding sub-blocks of the first color component. The method 1400 includes, at operation 1430, reconstructing, based on the derived motion vectors, the block of video data or decoding other blocks of video data in a same picture.


In some embodiments, the sub-block of the second component corresponds to a sub-block of the first component. For example, these two sub-blocks may be spatially co-located in the picture. The method 1300 or 1400 further includes calculating an intermediate set of motion vectors by copying motion vectors of the sub-block of the first component and applying a factor to the intermediate set of motion vectors to obtain the derived motion vectors, wherein the factor is associated with the color format.


In some embodiments, the color format is not 4:4:4 (e.g., is 4:2:2, or 4:2:0) and the size of at least one of the first set of sub-blocks is different than the size of at least one of the second set sub-blocks. In some embodiments, the color format is 4:4:4 and the size of at least one of the first set of sub-blocks is same as the size of at least one of the second set sub-blocks.


In some embodiments, the color format is not 4:4:4 and a size of at least one of the first set of sub-blocks is same as a size of at least one of the second set sub-blocks. A sub-block of the second component corresponds to multiple sub-blocks of the first component. In some embodiments, at least one of the motion vectors for a sub-block of the second component is derived based on an average of corresponding motion vectors of the multiple sub-blocks of the first component.


In some implementations, the sub-block of the second component corresponds to four sub-blocks of the first component. The four sub-blocks have motion vectors MV0=(MV0x, MV0y), MV1=(MV1x, MV1y), MV2=(MV2x, MV2y) and MV3=(MV3x, MV3y) respectively. The method 1300 or 1400 includes calculating an intermediate set of motion vectors MV*=(MV*x, MV*y) as MV*x=Shift(MV0x+MV1x+MV2x+MV3x, 2) and MV*y=Shift(MVy0+MVy1+MVy2+MVy3,2), wherein Shift(x, s)=(x+off)>>s, wherein off and s are integers, and wherein >> represents a right shift operation. The method 1300 or 1400 also includes applying a factor to the intermediate set of motion vectors to obtain the derived motion vectors, wherein the factor is associated with the color format.


In some implementations, the sub-block of the second component corresponds to four sub-blocks of the first component. The four sub-blocks have motion vectors MV0=(MV0x, MV0y), MV1=(MV1x, MV1y), MV2=(MV2x, MV2y) and MV3=(MV3x, MV3y) respectively. The method 1300 or 1400 comprises calculating an intermediate set of motion vectors MV*=(MV*x, MV*y) as MV*x=SignShift(MV0x+MV1x+MV2x+MV3x, 2) and MV*y=SignShift(MV0y+MV1y+MV2y+MV3y, 2), wherein







SignShift






(

x
,
s

)


=

{






(

x
+
off

)





>>
s




x

0






-

(


(


-
x

+
off

)





>>
s

)





x
<
0




,







wherein off and s are integers, and wherein >> represents a shift operation. The method 1300 or 1400 also includes applying a factor to the intermediate set of motion vectors to obtain the derived motion vectors, wherein the factor is associated with the color format.


In some implementations, the sub-block of the second component corresponds to four sub-blocks of the first component. The four sub-blocks have motion vectors MV0=(MV0x, MV0y), MV1=(MV1x, MV1y), MV2=(MV2x, MV2y) and MV3=(MV3x, MV3y) respectively. The method 1300 or 1400 includes calculating an intermediate set of motion vectors MV*=(MV*x, MV*y) as MV*x=Shift(MV′x+MV″x, 1) and MV*y=Shift(MV′y+MV″y, 1), wherein MV′x=Shift(MV0x+MV1x, 1), MV′y=Shift(MV0y+MV1y,1), MV″x=Shift(MV2x+MV3x,1), and MV″y=Shift(MV2y+MV3y, 1), wherein Shift(x,s)=(x+off)>>s, wherein off and s are integers, and wherein >> represents a right shift operation. The method 1300 or 1400 also includes applying a factor to the intermediate set of motion vectors to obtain the derived motion vectors, wherein the factor is associated with the color format.


In some implementations, the sub-block of the second component corresponds to four sub-blocks of the first component. The four sub-blocks have motion vectors MV0=(MV0x, MV0y), MV1=(MV1x, MV1y), MV2=(MV2x, MV2y) and MV3=(MV3x, MV3y) respectively. The method 1300 or 1400 includes calculating an intermediate set of motion vectors MV*=(MV*x, MV*y) as MV*x=Shift(MV′x+MV″x, 1) and MV*y=Shift(MV′y+MV″y,1), wherein MV′x=Shift(MV0x+MV2x, 1), MV′y=Shift(MV0y+MV2y,1), MV″x=Shift(MV1x+MV3x,1), and MV″y=Shift(MV1y+MV3y,1), wherein Shift(x, s)=(x+off)>>s, wherein off and s are integers, and wherein >> represents a right shift operation. The method 1300 or 1400 also includes applying a factor to the intermediate set of motion vectors to obtain the derived motion vectors, wherein the factor is associated with the color format.


In some implementations, the sub-block of the second component corresponds to four sub-blocks of the first component. The four sub-blocks have motion vectors MV0=(MV0x, MV0y), MV1=(MV1x, MV1y), MV2=(MV2x, MV2y) and MV3=(MV3x, MV3y) respectively. The method 1300 or 1400 includes calculating an intermediate set of motion vectors MV*=(MV*x, MV*y) as MV*x=SignShift(MV′x+MV″x, 1) and MV*y=SignShift(MV′y+MV″y, 1), wherein MV′x=SignShift(MV0x+MV1x,1), MV′y=SignShift(MV0y+MV1y, 1), MV″x=SignShift(MV2x+MV3x, 1), and MV″y=SignShift(MV2y+MV3y, 1), wherein







SignShift






(

x
,
s

)


=

{






(

x
+
off

)





>>
s




x

0






-

(


(


-
x

+
off

)





>>
s

)





x
<
0




,







wherein off and s are integers, and wherein >> represents a shift operation. The method 1300 or 1400 also includes applying a factor to the intermediate set of motion vectors to obtain the derived motion vectors, wherein the factor is associated with the color format.


In some implementations, the sub-block of the second component corresponds to four sub-blocks of the first component. The four sub-blocks have motion vectors MV0=(MV0x, MV0y), MV1=(MV1x, MV1y), MV2=(MV2x, MV2y) and MV3=(MV3x, MV3y) respectively. The method 1300 or 1400 includes calculating an intermediate set of motion vectors MV*=(MV*x, MV*y) as MV*x=SignShift(MV′x+MV″x, 1) and MV*y=SignShift(MV′y+MV″y, 1), wherein MV′x=SignShift(MV0x+MV2x,1), MV′y=SignShift(MV0y+MV2y, 1), MV″x=SignShift(MV1x+MV3x, 1), and MV″y=SignShift(MV1y+MV3y, 1), wherein







SignShift






(

x
,
s

)


=

{






(

x
+
off

)





>>
s




x

0






-

(


(


-
x

+
off

)





>>
s

)





x
<
0




,







wherein off and s are integers, and wherein >> represents a shift operation. The method 1300 or 1400 also includes applying a factor to the intermediate set of motion vectors to obtain the derived motion vectors, wherein the factor is associated with the color format.


In some implementations, the sub-block of the second component corresponds to two sub-blocks of the first component. The two sub-blocks have motion vectors MV0=(MV0x, MV0y) and MV1=(MV1x, MV1y) respectively. The method 1300 or 1400 includes calculating an intermediate set of motion vectors MV*=(MV*x, MV*y) as MV*x=Shift(MV0x+MV1x, 1) and MV*y=Shift(MVy0+MVy1,1), wherein Shift(x, s)=(x+off)>>s, wherein off and s are integers, and wherein >> represents a right shift operation. The method 1300 or 1400 also includes applying a factor to the intermediate set of motion vectors to obtain the derived motion vectors, wherein the factor is associated with the color format.


In some implementations, the sub-block of the second component corresponds to two sub-blocks of the first component. The two sub-blocks have motion vectors MV0=(MV0x, MV0y) and MV1=(MV1x, MV1y) respectively.


The method 1300 or 1400 includes calculating an intermediate set of motion vectors MV*=(MV*x, MV*y) as MV*x=SignShift(MV0x+MV1x, 1) and MV*y=SignShift(MVy0+MVy1,1), wherein







SignShift






(

x
,
s

)


=

{






(

x
+
off

)





>>
s




x

0






-

(


(


-
x

+
off

)





>>
s

)





x
<
0




,






wherein off and s are integers, and wherein >> represents a shift operation. The method 1300 or 1400 also includes applying a factor to the intermediate set of motion vectors to obtain the derived motion vectors, wherein the factor is associated with the color format.


In some embodiments, the method 1300 or 1400 further comprises calculating an intermediate set of motion vectors based on motion vectors of a selected sub-block among the multiple sub-blocks of the first component and applying a factor to the intermediate set of motion vectors to obtain the derived motion vectors. The factor is associated with the color format. In some implementations, the selected sub-block is a top-left sub-block of the multiple sub-blocks of the first component. In some implementations, the selected sub-block is a center sub-block of the multiple sub-blocks of the first component.


In some embodiments, the method 1300 or 1400 includes calculating an intermediate set of motion vectors based on a median of motion vectors of the multiple sub-blocks of the first component and applying a factor to the intermediate set of motion vectors to obtain the derived motion vectors, wherein the factor is associated with the color format.


In some embodiments, the applying of the factor is specified in a High Efficiency Video Coding (HEVC) standard.


The examples described above may be incorporated in the context of the methods described below, e.g., methods 1300 and 1400, which may be implemented at a video decoder and/or video encoder.



FIG. 15 is a block diagram illustrating an example encoding apparatus 1500 that can be utilized to implement various portions of the presently disclosed technology, including (but not limited to) method 1300 and method 1400. The encoding apparatus 1500 includes a quantizer 1505 for compressing input data bits. The encoding apparatus 1500 also includes a dequantizer 1515 so that data bits can be fed into memory 1525 and predictor 1520 to perform motion estimation. The encoding apparatus 1500 further includes a binary encoder 1530 to generated encoded binary codes.



FIG. 16 is a block diagram illustrating an example encoding apparatus 1600 that can be utilized to implement various portions of the presently disclosed technology, including (but not limited to) method 1300 and method 1400. The decoding apparatus 1600 includes a bindery decoder 1605 to decode the binary codes. The decoding apparatus 1600 also includes a dequantizer 1615 so that decoded data bits can be fed into memory 1625 and predictor 1620 to perform motion estimation on the decoding side.



FIG. 17 is a block diagram illustrating an example of the architecture for a computer system or other control device 1700 that can be utilized to implement various portions of the presently disclosed technology, including (but not limited to) method 1300 and method 1400. In FIG. 17, the computer system 1700 includes one or more processors 1705 and memory 1710 connected via an interconnect 1725. The interconnect 1725 may represent any one or more separate physical buses, point to point connections, or both, connected by appropriate bridges, adapters, or controllers. The interconnect 1725, therefore, may include, for example, a system bus, a Peripheral Component Interconnect (PCI) bus, a HyperTransport or industry standard architecture (ISA) bus, a small computer system interface (SCSI) bus, a universal serial bus (USB), IIC (I2C) bus, or an Institute of Electrical and Electronics Engineers (IEEE) standard 674 bus, sometimes referred to as “Firewire.”


The processor(s) 1705 may include central processing units (CPUs) to control the overall operation of, for example, the host computer. In certain embodiments, the processor(s) 1705 accomplish this by executing software or firmware stored in memory 1710. The processor(s) 1705 may be, or may include, one or more programmable general-purpose or special-purpose microprocessors, digital signal processors (DSPs), programmable controllers, application specific integrated circuits (ASICs), programmable logic devices (PLDs), or the like, or a combination of such devices.


The memory 1710 can be or include the main memory of the computer system. The memory 1710 represents any suitable form of random access memory (RAM), read-only memory (ROM), flash memory, or the like, or a combination of such devices. In use, the memory 1710 may contain, among other things, a set of machine instructions which, when executed by processor 1705, causes the processor 1705 to perform operations to implement embodiments of the presently disclosed technology.


Also connected to the processor(s) 1705 through the interconnect 1725 is a (optional) network adapter 1715. The network adapter 1715 provides the computer system 1700 with the ability to communicate with remote devices, such as the storage clients, and/or other storage servers, and may be, for example, an Ethernet adapter or Fiber Channel adapter.



FIG. 18 shows a block diagram of an example embodiment of a mobile device 1800 that can be utilized to implement various portions of the presently disclosed technology, including (but not limited to) method 1600. The mobile device 1800 can be a laptop, a smartphone, a tablet, a camcorder, or other types of devices that are capable of processing videos. The mobile device 1800 includes a processor or controller 1801 to process data, and memory 1802 in communication with the processor 1801 to store and/or buffer data. For example, the processor 1801 can include a central processing unit (CPU) or a microcontroller unit (MCU). In some implementations, the processor 1801 can include a field-programmable gate-array (FPGA). In some implementations, the mobile device 1800 includes or is in communication with a graphics processing unit (GPU), video processing unit (VPU) and/or wireless communications unit for various visual and/or communications data processing functions of the smartphone device. For example, the memory 1802 can include and store processor-executable code, which when executed by the processor 1801, configures the mobile device 1800 to perform various operations, e.g., such as receiving information, commands, and/or data, processing information and data, and transmitting or providing processed information/data to another device, such as an actuator or external display.


To support various functions of the mobile device 1800, the memory 1802 can store information and data, such as instructions, software, values, images, and other data processed or referenced by the processor 1801. For example, various types of Random Access Memory (RAM) devices, Read Only Memory (ROM) devices, Flash Memory devices, and other suitable storage media can be used to implement storage functions of the memory 1802. In some implementations, the mobile device 1800 includes an input/output (I/O) unit 1803 to interface the processor 1801 and/or memory 1802 to other modules, units or devices. For example, the I/O unit 1803 can interface the processor 1801 and memory 1802 with to utilize various types of wireless interfaces compatible with typical data communication standards, e.g., such as between the one or more computers in the cloud and the user device. In some implementations, the mobile device 1800 can interface with other devices using a wired connection via the I/O unit 1803. The mobile device 1800 can also interface with other external interfaces, such as data storage, and/or visual or audio display devices 1804, to retrieve and transfer data and information that can be processed by the processor, stored in the memory, or exhibited on an output unit of a display device 1804 or an external device. For example, the display device 1804 can display a video frame that includes a block (a CU, PU or TU) that applies the intra-block copy based on whether the block is encoded using a motion compensation algorithm, and in accordance with the disclosed technology.


From the foregoing, it will be appreciated that specific embodiments of the presently disclosed technology have been described herein for purposes of illustration, but that various modifications may be made without deviating from the scope of the invention. Accordingly, the presently disclosed technology is not limited except as by the appended claims.


Implementations of the subject matter and the functional operations described in this patent document can be implemented in various systems, digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Implementations of the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a tangible and non-transitory computer readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more of them. The term “data processing unit” or “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.


A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.


The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).


Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices. Computer readable media suitable for storing computer program instructions and data include all forms of nonvolatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.


It is intended that the specification, together with the drawings, be considered exemplary only, where exemplary means an example. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Additionally, the use of “or” is intended to include “and/or”, unless the context clearly indicates otherwise.


While this patent document contains many specifics, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this patent document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.


Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Moreover, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.


Only a few implementations and examples are described and other implementations, enhancements and variations can be made based on what is described and illustrated in this patent document.

Claims
  • 1. A method of processing video data, comprising: determining, during a conversion between a current video unit of a video which comprises a luma block and at least one chroma block and a bitstream of the video, that motion vectors of control points for the luma block based on an affine mode;dividing the luma block into luma sub-blocks, wherein each luma sub-block has a second size;dividing a chroma block of the at least one chroma block into chroma sub-blocks, wherein each chroma sub-block has a first size;determining a luma motion vector for each luma sub-block based on the motion vectors of the control points;deriving a chroma motion vector for each chroma sub-block based on luma motion vectors of multiple luma sub-blocks and a color format of the current video unit; andreconstructing the luma block based on the luma motion vector of each luma sub-block;wherein the chroma block comprises at least one first chroma group and the first chroma group includes two or four chroma sub-blocks according to the color format of the current video unit, and wherein motion vectors of the chroma sub-blocks included in the first chroma group are same, andwherein predicted samples of the chroma block are derived using the chroma sub-blocks having the first size equal to the second size in a case that a color format applied for the luma block and the chroma block is 4:2:0 or 4:2:2.
  • 2. The method of claim 1, wherein the motion vectors of the chroma sub-blocks included in the first chroma group are derived based on applying a scaling factor to an intermediate motion vector MV*.
  • 3. The method of claim 2, wherein the first chroma group includes two chroma sub-blocks in a case that the color format is 4:2:2, two luma sub-blocks corresponding to the two chroma sub-blocks has motion vectors MV0 and MV1 respectively, and wherein the intermediate motion vector MV* is derived based on the MV0 and the MV1.
  • 4. The method of claim 3, wherein the intermediate motion vector MV* is derived based on applying an offset-based averaging operation on the MV0 and the MV1.
  • 5. The method of claim 4, wherein the intermediate motion vector MV*=Shift(MV0+MV1,1), wherein Shift(x,1)=(x+offset)>>1, offset is equal to 0 or 1, and wherein >>represents a right shift operation.
  • 6. The method of claim 2, wherein the first chroma group includes four chroma sub-blocks in a case that the color format is 4:2:0, a top-left one of four luma sub-blocks has motion vector MV0, a top-right one of the four luma sub-blocks has motion vector MV1, a bottom-left one of the four luma sub-blocks has motion vector MV2 and a bottom-right one of the four luma sub-blocks has motion vector MV3, and wherein the four luma sub-blocks correspond to the four chroma sub-blocks and the intermediate motion vector MV* is derived at least based on the MV0 and the MV3.
  • 7. The method of claim 6, wherein the intermediate motion vector MV* is derived based on applying an offset-based averaging operation at least on the MV0 and MV3.
  • 8. The method of claim 1, further comprising: reconstructing the chroma block based on the motion vectors of the chroma sub-blocks included in the first chroma group.
  • 9. The method of claim 8, wherein reconstructing the chroma block in units of the first chroma group.
  • 10. The method of claim 1, wherein the conversion includes encoding the current video unit into the bitstream.
  • 11. The method of claim 1, wherein the conversion includes decoding the current video unit from the bitstream.
  • 12. An apparatus for processing video data comprising a processor and a non-transitory memory with instructions thereon, wherein the instructions upon execution by the processor, cause the processor to: determine, during a conversion between a current video unit of a video which comprises a luma block and at least one chroma block and a bitstream of the video, that motion vectors of control points for the luma block based on an affine mode;divide the luma block into luma sub-blocks, wherein each luma sub-block has a second size;divide a chroma block of the at least one chroma block into chroma sub-blocks, wherein each chroma sub-block has a first size;determine a luma motion vector for each luma sub-block based on the motion vectors of the control points;derive a chroma motion vector for each chroma sub-block based on luma motion vectors of multiple luma sub-blocks and a color format of the current video unit; andreconstruct the luma block based on the luma motion vector of each luma sub-block;wherein the chroma block comprises at least one first chroma group and the first chroma group includes two or four chroma sub-blocks according to the color format of the current video unit, and wherein motion vectors of the chroma sub-blocks included in the first chroma group are same, andwherein predicted samples of the chroma block are derived using the chroma sub-blocks having the first size equal to the second size in a case that a color format applied for the luma block and the chroma block is 4:2:0 or 4:2:2.
  • 13. The apparatus of claim 12, wherein the motion vectors of the chroma sub-blocks included in the first chroma group are derived based on applying a scaling factor to an intermediate motion vector MV*.
  • 14. The apparatus of claim 13, wherein the first chroma group includes two chroma sub-blocks in a case that the color format is 4:2:2, two luma sub-blocks corresponding to the two chroma sub-blocks has motion vectors MV0 and MV1 respectively, and wherein the intermediate motion vector MV* is derived based on the MV0 and the MV1.
  • 15. The apparatus of claim 14, wherein the intermediate motion vector MV* is derived based on applying an offset-based averaging operation on the MV0 and the MV1.
  • 16. The apparatus of claim 15, wherein the intermediate motion vector MV*=Shift(MV0+MV1,1), wherein Shift(x,1)=(x+offset)>>1, offset is equal to 0 or 1, and wherein >>represents a right shift operation.
  • 17. The apparatus of claim 12, wherein the instructions upon execution by the processor, further cause the processor to: reconstruct the chroma block based on the motion vectors of the chroma sub-blocks included in the first chroma group.
  • 18. The apparatus of claim 17, wherein reconstruct the chroma block in units of the first chroma group.
  • 19. A non-transitory computer-readable storage medium storing instructions that cause a processor to: determine, during a conversion between a current video unit of a video which comprises a luma block and at least one chroma block and a bitstream of the video, that motion vectors of control points for the luma block based on an affine mode;divide the luma block into luma sub-blocks, wherein each luma sub-block has a second size;divide a chroma block of the at least one chroma block into chroma sub-blocks, wherein each chroma sub-block has a first size;determine a luma motion vector for each luma sub-block based on the motion vectors of the control points;derive a chroma motion vector for each chroma sub-block based on luma motion vectors of multiple luma sub-blocks and a color format of the current video unit; andreconstruct the luma block based on the luma motion vector of each luma sub-block;wherein the chroma block comprises at least one first chroma group and the first chroma group includes two or four chroma sub-blocks according to the color format of the current video unit, and wherein motion vectors of the chroma sub-blocks included in the first chroma group are same, andwherein predicted samples of the chroma block are derived using the chroma sub-blocks having the first size equal to the second size in a case that a color format applied for the luma block and the chroma block is 4:2:0 or 4:2:2.
  • 20. A non-transitory computer-readable recording medium storing a bitstream of a video which is generated by a method performed by a video processing apparatus, wherein the method comprises: determining, during a conversion between a current video unit of the video which comprises a luma block and at least one chroma block and a bitstream of the video, that motion vectors of control points for the luma block based on an affine mode;dividing the luma block into luma sub-blocks, wherein each luma sub-block has a second size;dividing a chroma block of the at least one chroma block into chroma sub-blocks, wherein each chroma sub-block has a first size;determining a luma motion vector for each luma sub-block based on the motion vectors of the control points;deriving a chroma motion vector for each chroma sub-block based on luma motion vectors of multiple luma sub-blocks and a color format of the current video unit; andgenerating the bitstream based on above determining and dividing, wherein the conversion include reconstructing the luma block based on the luma motion vector of each luma sub-block;wherein the chroma block comprises at least one first chroma group and the first chroma group includes two or four chroma sub-blocks according to the color format of the current video unit, and wherein motion vectors of the chroma sub-blocks included in the first chroma group are same, and
Priority Claims (2)
Number Date Country Kind
PCT/CN2018/092118 Jun 2018 WO international
PCT/CN2018/114931 Nov 2018 WO international
CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 17/071,412, filed on Oct. 15, 2020, which is a continuation of International Application No. PCT/IB2019/055247, filed on Jun. 21, 2019, which claims the priority to and benefits of International patent Application No. PCT/CN2018/092118, filed on Jun. 21, 2018, PCT/CN2018/114931, filed on Nov. 10, 2018. All the aforementioned patent applications are hereby incorporated by reference in their entireties.

US Referenced Citations (200)
Number Name Date Kind
7529302 Mukerjee et al. May 2009 B2
8184715 Rosenzweig et al. May 2012 B1
8462846 Zhang Jun 2013 B2
9294777 Wang Mar 2016 B2
9374595 Kim et al. Jun 2016 B2
9432684 Lee et al. Aug 2016 B2
9521425 Chen et al. Dec 2016 B2
9615089 Fartukov et al. Apr 2017 B2
9667996 Chen et al. May 2017 B2
9674542 Chen et al. Jun 2017 B2
9762927 Chen et al. Sep 2017 B2
9900593 Xiu et al. Feb 2018 B2
9948930 Panusopone et al. Apr 2018 B2
9955186 Chon et al. Apr 2018 B2
10045014 Zhang et al. Aug 2018 B2
10142655 Lin et al. Nov 2018 B2
10298950 Wang et al. May 2019 B2
10362330 Li et al. Jul 2019 B1
10404990 Hendry et al. Sep 2019 B2
10419763 Huang et al. Sep 2019 B2
10448010 Chen et al. Oct 2019 B2
10484686 Xiu et al. Nov 2019 B2
10523964 Chuang et al. Dec 2019 B2
10560712 Zou et al. Feb 2020 B2
10701366 Chen et al. Jun 2020 B2
10708592 Dong et al. Jul 2020 B2
10757417 Zhang et al. Aug 2020 B2
10778999 Li et al. Sep 2020 B2
10779002 Chen et al. Sep 2020 B2
10785494 Chien et al. Sep 2020 B2
10805630 Li et al. Oct 2020 B2
10841609 Liu et al. Nov 2020 B1
10904565 Chuang et al. Jan 2021 B2
11172196 Zhang et al. Nov 2021 B2
11197003 Zhang et al. Dec 2021 B2
11197007 Zhang et al. Dec 2021 B2
11202065 Zhang et al. Dec 2021 B2
11202081 Zhang et al. Dec 2021 B2
11477463 Zhang et al. Oct 2022 B2
11509915 Zhang et al. Nov 2022 B2
20070192762 Eichenberger et al. Aug 2007 A1
20110002386 Zhang Jan 2011 A1
20110194609 Rusert et al. Aug 2011 A1
20110200107 Ryu Aug 2011 A1
20120219216 Sato Aug 2012 A1
20120287999 Li et al. Nov 2012 A1
20120320984 Zhou et al. Dec 2012 A1
20130003842 Kondo Jan 2013 A1
20130101041 Fishwick et al. Apr 2013 A1
20130107958 Shimada et al. May 2013 A1
20130128976 Koyama et al. May 2013 A1
20130182755 Chen et al. Jul 2013 A1
20130229485 Rusanovskyy et al. Sep 2013 A1
20130272410 Seregin et al. Oct 2013 A1
20130329007 Zhang et al. Dec 2013 A1
20140086325 Chen et al. Mar 2014 A1
20140286408 Zhang et al. Sep 2014 A1
20140286416 Jeon et al. Sep 2014 A1
20140294066 Kondo Oct 2014 A1
20140294078 Seregin et al. Oct 2014 A1
20140334551 Kim et al. Nov 2014 A1
20150023423 Zhang et al. Jan 2015 A1
20150181216 Zhang et al. Jun 2015 A1
20150249828 Rosewarne et al. Sep 2015 A1
20150312588 Yamamoto et al. Oct 2015 A1
20150373350 Hendry et al. Dec 2015 A1
20150373357 Pang et al. Dec 2015 A1
20150373362 Pang et al. Dec 2015 A1
20160057420 Pang et al. Feb 2016 A1
20160073132 Zhang et al. Mar 2016 A1
20160100189 Pang et al. Apr 2016 A1
20160142729 Wang et al. May 2016 A1
20160286229 Li et al. Sep 2016 A1
20160366441 An et al. Dec 2016 A1
20160373756 Yu et al. Dec 2016 A1
20170054996 Xu Feb 2017 A1
20170085905 Kadono et al. Mar 2017 A1
20170142418 Li et al. May 2017 A1
20170223378 Tao et al. Aug 2017 A1
20170238005 Chien et al. Aug 2017 A1
20170238011 Pettersson Aug 2017 A1
20170272748 Seregin et al. Sep 2017 A1
20170272782 Li et al. Sep 2017 A1
20170289566 He et al. Oct 2017 A1
20170310990 Hsu Oct 2017 A1
20170332095 Zou et al. Nov 2017 A1
20170332099 Lee et al. Nov 2017 A1
20170339404 Panusopone et al. Nov 2017 A1
20170339405 Wang et al. Nov 2017 A1
20180041762 Ikai et al. Feb 2018 A1
20180048889 Zhang et al. Feb 2018 A1
20180054628 Pettersson et al. Feb 2018 A1
20180063553 Zhang et al. Mar 2018 A1
20180098062 Li et al. Apr 2018 A1
20180098087 Li et al. Apr 2018 A1
20180124394 Xu et al. May 2018 A1
20180131952 Xiu et al. May 2018 A1
20180184117 Chen et al. Jun 2018 A1
20180192069 Chen et al. Jul 2018 A1
20180192072 Chen et al. Jul 2018 A1
20180199056 Sato Jul 2018 A1
20180220149 Son et al. Aug 2018 A1
20180247396 Pouli et al. Aug 2018 A1
20180249172 Chen et al. Aug 2018 A1
20180270500 Li et al. Sep 2018 A1
20180278951 Seregin et al. Sep 2018 A1
20180288425 Panusopone et al. Oct 2018 A1
20180288441 Zhang et al. Oct 2018 A1
20180324454 Lin et al. Nov 2018 A1
20180332298 Liu et al. Nov 2018 A1
20180376166 Chuang et al. Dec 2018 A1
20190020895 Liu et al. Jan 2019 A1
20190037231 Ikai et al. Jan 2019 A1
20190052886 Chiang et al. Feb 2019 A1
20190058897 Han et al. Feb 2019 A1
20190068977 Zhang et al. Feb 2019 A1
20190075293 Lim et al. Mar 2019 A1
20190104303 Xiu et al. Apr 2019 A1
20190124332 Lim et al. Apr 2019 A1
20190158866 Kim May 2019 A1
20190182504 Lainema Jun 2019 A1
20190191171 Ikai et al. Jun 2019 A1
20190222859 Chuang et al. Jul 2019 A1
20190246128 Xu et al. Aug 2019 A1
20190246143 Zhang et al. Aug 2019 A1
20190273943 Zhao et al. Sep 2019 A1
20190306502 Gadde et al. Oct 2019 A1
20190320181 Chen et al. Oct 2019 A1
20190320189 Cooper et al. Oct 2019 A1
20190335170 Lee et al. Oct 2019 A1
20190342547 Lee et al. Nov 2019 A1
20190364295 Li et al. Nov 2019 A1
20190373261 Eglimez et al. Dec 2019 A1
20190387250 Boyce et al. Dec 2019 A1
20200021837 Ikai et al. Jan 2020 A1
20200021839 Pham Van et al. Jan 2020 A1
20200045310 Chen et al. Feb 2020 A1
20200045311 Yoo Feb 2020 A1
20200053364 Seo Feb 2020 A1
20200084441 Lee et al. Mar 2020 A1
20200084454 Liu et al. Mar 2020 A1
20200099951 Hung et al. Mar 2020 A1
20200112741 Han Apr 2020 A1
20200120334 Xu et al. Apr 2020 A1
20200128237 Xu et al. Apr 2020 A1
20200128258 Chen et al. Apr 2020 A1
20200137398 Zhao Apr 2020 A1
20200145688 Zou et al. May 2020 A1
20200154127 Lee May 2020 A1
20200169726 Kim et al. May 2020 A1
20200177911 Aono et al. Jun 2020 A1
20200213594 Liu et al. Jul 2020 A1
20200213612 Liu et al. Jul 2020 A1
20200213622 Xu et al. Jul 2020 A1
20200221077 Park et al. Jul 2020 A1
20200221110 Chien et al. Jul 2020 A1
20200221120 Robert et al. Jul 2020 A1
20200267408 Lee et al. Aug 2020 A1
20200275120 Lin et al. Aug 2020 A1
20200296380 Aono et al. Sep 2020 A1
20200296382 Zhao et al. Sep 2020 A1
20200296415 Chen et al. Sep 2020 A1
20200336738 Xiu et al. Oct 2020 A1
20200351505 Seo Nov 2020 A1
20200359029 Liu et al. Nov 2020 A1
20200374543 Liu et al. Nov 2020 A1
20200374544 Liu et al. Nov 2020 A1
20200382771 Liu et al. Dec 2020 A1
20200382795 Zhang et al. Dec 2020 A1
20200382807 Liu et al. Dec 2020 A1
20200396453 Zhang et al. Dec 2020 A1
20200396462 Zhang et al. Dec 2020 A1
20200396465 Zhang et al. Dec 2020 A1
20200404255 Zhang et al. Dec 2020 A1
20200404260 Zhang et al. Dec 2020 A1
20200413048 Zhang et al. Dec 2020 A1
20210006780 Zhang et al. Jan 2021 A1
20210006787 Zhang et al. Jan 2021 A1
20210029356 Zhang et al. Jan 2021 A1
20210029362 Liu et al. Jan 2021 A1
20210029368 Zhang et al. Jan 2021 A1
20210037240 Zhang et al. Feb 2021 A1
20210037256 Zhang et al. Feb 2021 A1
20210051339 Liu et al. Feb 2021 A1
20210067783 Liu et al. Mar 2021 A1
20210076050 Zhang et al. Mar 2021 A1
20210076063 Liu et al. Mar 2021 A1
20210092379 Zhang et al. Mar 2021 A1
20210092435 Liu et al. Mar 2021 A1
20210105482 Zhang et al. Apr 2021 A1
20210152846 Zhang et al. May 2021 A1
20210203958 Zhang et al. Jul 2021 A1
20210218980 Zhang et al. Jul 2021 A1
20210352302 Zhang et al. Nov 2021 A1
20210392341 Zhang et al. Dec 2021 A1
20220070488 Chen et al. Mar 2022 A1
20220070489 Zhang et al. Mar 2022 A1
20220078452 Zhang et al. Mar 2022 A1
20220217363 Zhang et al. Jul 2022 A1
20220264125 Zhang et al. Aug 2022 A1
Foreign Referenced Citations (75)
Number Date Country
3025490 Dec 2017 CA
3037685 Mar 2018 CA
1672174 Sep 2005 CN
1710959 Dec 2005 CN
1777283 May 2006 CN
101605255 Dec 2009 CN
101895751 Nov 2010 CN
102577388 Jul 2012 CN
103561263 Feb 2014 CN
104053005 Sep 2014 CN
104170381 Nov 2014 CN
104221376 Dec 2014 CN
104904207 Sep 2015 CN
105306944 Feb 2016 CN
105532000 Apr 2016 CN
105678808 Jun 2016 CN
105723713 Jun 2016 CN
105917650 Aug 2016 CN
106303543 Jan 2017 CN
106416245 Feb 2017 CN
106537915 Mar 2017 CN
106559669 Apr 2017 CN
106688232 May 2017 CN
107079161 Aug 2017 CN
107113424 Aug 2017 CN
107113442 Aug 2017 CN
107211156 Sep 2017 CN
107409225 Nov 2017 CN
107426568 Dec 2017 CN
107534778 Jan 2018 CN
107615765 Jan 2018 CN
107852490 Mar 2018 CN
107925775 Apr 2018 CN
107979756 May 2018 CN
108012153 May 2018 CN
108028929 May 2018 CN
108432250 Aug 2018 CN
108632629 Oct 2018 CN
112020829 Dec 2020 CN
2539213 Dec 2016 GB
H08186825 Jul 1996 JP
2007272733 Oct 2007 JP
2011077761 Apr 2011 JP
2013098745 May 2013 JP
2021513818 May 2021 JP
20200128154 Nov 2020 KR
201540047 Oct 2015 TW
201709738 Mar 2017 TW
201832557 Sep 2018 TW
2000065829 Nov 2000 WO
2009080133 Jul 2009 WO
2013168407 Nov 2013 WO
2016048834 Mar 2016 WO
2016057701 Apr 2016 WO
2016091161 Jun 2016 WO
2016138513 Sep 2016 WO
2016183224 Nov 2016 WO
2017130696 Mar 2017 WO
2017118411 Jul 2017 WO
2017133661 Aug 2017 WO
2017157264 Sep 2017 WO
2017157281 Sep 2017 WO
2017165391 Sep 2017 WO
2017188509 Nov 2017 WO
2017195554 Nov 2017 WO
2017197126 Nov 2017 WO
2017197146 Nov 2017 WO
2017206803 Dec 2017 WO
2018047668 Mar 2018 WO
2018066241 Apr 2018 WO
2018067823 Apr 2018 WO
2018097692 May 2018 WO
2018097693 Jul 2018 WO
2018184589 Oct 2018 WO
2020086331 Apr 2020 WO
Non-Patent Literature Citations (102)
Entry
Final Office Action from U.S. Appl. No. 17/031,451 dated Dec. 21, 2021.
Notice of Allowance nfrom U.S. Appl. No. 17/071,357 dated Feb. 2, 2022.
Office Action from Indian Patent Application No. 202127002718 dated Jan. 6, 2022.
Final Office Action from U.S. Appl. No. 17/161,391 dated Jul. 14, 2021.
Non-Final Office Action from U.S. Appl. No. 17/031,451 dated Dec. 4, 2020.
Notice of Allowance from U.S. Appl. No. 17/011,131 dated Dec. 10, 2020.
Non-Final Office Action from U.S. Appl. No. 17/074,842 dated Dec. 23, 2020.
Non-Final Office Action from U.S. Appl. No. 17/074,892 dated Dec. 24, 2020.
Non-Final Office Action from U.S. Appl. No. 17/005,521 dated Jan. 7, 2021.
Notice of Allowance from U.S. Appl. No. 17/071,412 dated Jan. 7, 2021.
Final Office Action from U.S. Appl. No. 17/019,629 dated Feb. 26, 2021.
Non-Final Office Action from U.S. Appl. No. 17/161,391 dated Mar. 25, 2021.
Final Office Action from U.S. Appl. No. 17/005,521 dated Apr. 26, 2021.
Advisory Action from U.S. Appl. No. 17/074,892 dated Aug. 4, 2021.
Non-Final Office Action from U.S. Appl. No. 17/071,357 dated Sep. 21, 2021.
Alshin et al. “Bi-Directional Optical Flow for Improving Motion Compensation,” 28th Picture Coding Symposium, PCS2010, Dec. 8, 2010, Nagoya, Japan, pp. 422-425.
Bross et al. “Versatlie Video Coding (Draft 2),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 11th Meeting, Ljubljana, SI, Jul. 10-18, 2018, document JVET-K1001, 2018.
Bross et al. “Versatile Video Coding (Draft 4),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting, Marrakech, MA, Jan. 9-18, 2019, document JVET-M1001, 2019.
Bross et al. “Versatile Video Coding (Draft 5),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 14th Meeting, Geneva, CH, Mar. 19-27, 2019, document JVET-N1001, 2019.
Chen et al. “EE3: Generalized Bi-Prediction,” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 4th Meeting, Chengdu, CN, Oct. 15-21, 2016, document JVET-D0102, 2016.
Chen et al. “Algorithm Description of Joint Exploration Test Model 7 (JEM 7),” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 7th Meeting, Torino, IT, Jul. 13-21, 2017, document JVET-31001, 2017.
Chen et al. “Description of SDR, HDR and 360 degree Video Coding Technology Proposal by Qualcomm and Technicolor—low and high complexity versions,” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/EC JTC 1/SC 29/WG 11, 10th Meeting, San Diego, US, Apr. 10-20, 2018, document JVET-J0021, 2018.
Chen et al. “Description of SDR, HDR and 360 degree Video Coding Technology Proposal by Huawei, GoPro, HiSilicon, and Samsung,” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 10th Meeting, San Diego, US, Apr. 10-20, 2018, document JVET-J0025, 2018.
Chen et al. “DMVR Extension baed on Template Matching,” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 10th Meeting, San Diego, US, Apr. 10-20, 2018, document JVET-J0057, 2018.
Chien et al. “Modification of Merge Candidate Derivation,” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 2nd Meeting, San Diego, USA, Feb. 20-26, 2016, document JVET-B0058, 2016.
JEM-7.0: https://jvet.hhi.fraunhofer.de/svn/svn_HMJEMSoftware/tags/ HM-16.6-JEM-7.0. (only website).
Han et al. “CE4-Related: Modification on Merge List,” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting, Marrakech, MA, Jan. 9-18, 2019, document JVET-M0127, 2019.
He et al. “Non-SCCE1: Improved Intra Block Copy Coding with Block Vector Derivation,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 18th Meeting, Sapporo, JP, Jun. 30-Jul. 9, 2017, document JCTVC-R0165, 2014.
“High Efficiency Video Coding” Series H: Audiovisual and Multimedia Systems: Infrastructure of Audiovisual Services—Coding of Moving Video, ITU-T, H.265, 2018.
Hsiao et al. “CE4.2.8: Merge Mode Enhancement,” Joint Video Experts Team (JVET of ITU-T SG 16 WP 3 and ISO/EC JTC 1/SC 29/WG 11, 11th Meeting: Ljubljana, SI, Jul. 10-18, 2018, document JVET-K0245, 2018.
H.265/HEVC, https://www.itu.int/rec/T-REC-H.265.
Li et al. “Affine Deformation Model Based Intra Block Copy for Intra Frame Coding,” 2020, Institute of Information and Communication Engineering, Zhejiang University.
Li et al. “Multi-Type-Tree.” Joint Video Exploration Team (JVET), of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 4th Meeting: Chengdu, CN, Oct. 15-21, 2016, document JVET-D0117rl, 2016.
Li et al. “Non-CE4: Harmonization between HMVP and Gbi,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting: Marrakech, MA, Jan. 9-18, 2019, document JVET-M0264, 2019.
Li et al. “Adaptive Motion Vector Resolution for Screen Content,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 19th Meeting, Strasbourg, FR, Oct. 17-24, 2014, document JCTVC-S0085, 2014.
Li et al. “Combining Directional Intra Prediction and Intra Block Copy with Block Partitioning for HEVC,” 2016 IEEE International Conference on Image Processing (ICIP), Phoenix, AZ, USA, 2016, pp. 524-528.
Luthra et al. Overview of the H.264/AVC Video Coding Standard, Proc. SPIE, 5203, Applications of Digital Image Processing, Nov. 19, 2003, Optical Science and Technology, SPIE 48th annutal Meeting, San Diego, CA, US, 2003.
Su et al. “CE4.4.1: Generalized Bi-Prediction for Intercoding,” Joint Video Exploration Team of ISO/IEC JTC 1/SC 29/WG 11 and ITU-T SG 16, Ljubljana, Jul. 11-18, 2018, document No. JVET-K0248, 2018.
Sullivan et al. “Overview of the High Efficiency Video Coding (HEVC) Standard,” IEEE Transactions on Circuits and Systems for Video Technology, Dec. 2012, 22(12):1649-1668.
Sullivan et al. “Meeting Report of the 18th Meeting of the Joint Collaborative Team on Video Coding (JCT-VC), Sapporo, JP, Jun. 30-Jul. 9, 2014”, Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG16 WP3 and ISO/IEC JTC1/SC29/WG11, 18th Meeting: Sapporo, JP, Jun. 30-Jul. 9, 2014, JCTVC-R_Notes_d, 2014.
Toma et al. “Description of SDR Video Coding Technology Proposal by Panasonic,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 10th Meetingmm San Diego, US, Apr. 10-20, 2018, document JVET-J0020, 2018.
Van Der Auwera et al. “Description of Core Experiment 3: Intra Prediction and Mode Coding,” Joint Video Experts Feam (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 10th Meeting, San Diego, USA, Apr. 10-20, 2018. document JVET-J1023, 2018.
Xu et al. “Intra Block Copy in HEVC Screen Content Coding Extensions,” IEEE Journal on Emerging and Selected Topics in Circuits and Systems, Dec. 2016, 6(4):409-419.
Xu et al. “CE8-Related Combination Test of JVET-N0176/JVET-N0317/JVET-N0382 on Simplification of IBC Vector Prediction,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP3 and ISO/IEC JTC 1/SC 29/WG 11, 14th Meeting, Geneva, CH, Mar. 19-27, 2019, document JVET-N0843, 2019.
Yang et al. “Description of Core Experiment 4 (CE4): Inter Prediction and Motion Vector Coding,” Joint Video Experts Feam (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 11th Meeting, Ljubljana, SI, Jul. 10-18, 2018, document JVET-K1024, 2018.
Zhang et al. “Rotate Intra Block Copy for Still Image Coding,” 2015 IEEE International Conference on Image Processing (ICIP), IEEE, Sep. 27, 2015, pp. 4102-4106.
Zhang et al. “CE4-related: History-based Motion Vector Prediction”, Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 11th Meeting, Ljubljana, SI, Jul. 10-18, 2018, Document JVET-K0104, 2018.
Zhang et al. “CE4.2.14: Planar Motion Vector Prediction,” Joint Video Experts Team (JVET) of ITU-T SG 16 and WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 11th Meeting: Ljubljaba, SI, Jul. 10-18, 2018, document JVET-K0135, 2018.
Zhang et al. “BoG Report on CE4 Related Contributions,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting: Marrakech, MA, Jan. 9-18, 2019, document JVET-M0843, 2019.
Zhang et al. “On Adaptive Motion Vector Resolution,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 20th Meeting, Geneva, CH, Feb. 10-18, 2015, document JCTVC-T0059, 2015.
Zou et al. “Improved Affine Motion Prediction,” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP3 and ISO/EC JTC 1/SC 29/WG 11, 3rd Meeting, Geneva, CH, May 26-Jun. 1, 2016, document JVET-C0062, 2016.
Zhou et al. “Spatial-Temporal Merge Mode (Non Subblock STMVP),” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 11th Meeting: Ljubljana, SI, Jul. 10-18, 2018, document JVET-K0532, and JVET-K0161, 2018.
International Search Report and Written Opinion from PCT/IB2019/054602 dated Aug. 21, 2019 (17 pages).
International Search Report and Written Opinion from PCT/IB2019/054604 dated Sep. 26, 2019 (17 pages).
International Search Report and Written Opinion from PCT/IB2019/054611 dated Aug. 29, 2019 (88 pages).
International Search Report and Written Opinion from PCT/IB2019/054612 dated Sep. 26, 2019 (17 pages).
International Search Report and Written Opinion from PCT/IB2019/054614 dated Aug. 27, 2019 (14 pages).
International Search Report and Written Opinion from PCT/IB2019/054650 dated Oct. 28, 2019 (20 pages).
International Search Report and Written Opinion from PCT/IB2019/054652 dated Sep. 27, 2019 (18 pages).
International Search Report and Written Opinion from PCT/IB2019/054654 dated Aug. 27, 2019 (85 pages).
International Search Report and Written Opinion from PCT/IB2019/058078 dated Mar. 3, 2020(20 pages).
International Search Report and Written Opinion from PCT/IB2019/058079 dated Mar. 3, 2020(26 pages).
International Search Report and Written Opinion from PCT/IB2019/058081 dated Mar. 25, 2020(21 pages).
Non-Final Office Action from U.S. Appl. No. 17/019,629 dated Nov. 13, 2020.
Non-Final Office Action from U.S. Appl. No. 17/011,157 dated Nov. 17, 2020.
Hsiao et al. “CE4.4.12: Pairwise Average Candidates,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 12th Meeting, Macao, CN, Oct. 3-12, 2018, document JVET-L0090, 2019.
Hsu et al. “Description of SDR Video Coding Technology Proposal by MediaTek,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 10th Meeting, San Diego, US, Apr. 10-20, 2018, document JVET-J0018, 2018.
Lee et al. “Unified Condition for Affine Merge and Affine Inter Mode,” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTc 1/SC 29/WG 11, 5th Meeting, Geneva, CH, Jan. 12-20, 2017, JVET-E0039, 2017.
Liao et al. “CE10.1.b: Triangular Prediction Unit Mode,” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 12th Meeting, Macao, CN, Oct. 3-12, 2018, document JVET-L0124. 2018.
Zhang et al. “CE4-Related: Simplified Affine Prediction,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 11th Meeting, Ljubljana, SI, Jul. 10-18, 2018, document JVET-K0103. 2018.
Zhang et al. “CE4: Affine Prediction with 4x4 Sub-blocks for Chroma Components (Test 4.1.16),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 12th Meeting, Macao, CN, Oct. 3-12, 2018, document JVET-L0265, 2018.
Zhang et al. “CE3-Related: Modified Chroma Derived Mode,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 12th Meeting, Macao, CN, Oct. 3-12, 2018, document JVET-L0272, 2018.
Zhang et al. “Adaptive Motion Vector Resolution Rounding Align,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 2/WG 11, 12th Meeting, Macao, CN, Oct. 3-12, 2018, document JVET-L0377, 2018.
International Search Report and Written Opinion from PCT/CN2019/117116 dated Jan. 2, 2020 (9 pages).
International Search Report and Written Opinion from PCT/CN2019/117118 dated Feb. 5, 2020 (9 pages).
International Search Report and Written Opinion from PCT/CN2019/117119 dated Jan. 23, 2020 (9 pages).
International Search Report and Written Opinion from PCT/IB2019/055244 dated Nov. 18, 2019 (18 pages).
International Search Report and Written Opinion from PCT/IB2019/055246 dated Nov. 7, 2019 (18 pages).
International Search Report and Written Opinion from PCT/IB2019/055247 dated Nov. 7, 2019 (21 pages).
Non-Final Office Action from U.S. Appl. No. 17/071,357 dated Dec. 8, 2020.
Non-Final Office Action from U.S. Appl. No. 17/099,042 dated Dec. 31, 2020.
Huang, Wanzhang, “Research on Side Information Generation of Distributed Video Coding,” South China University of Technology, Guangzhou, China, 2012. (cited in CN201910487926.0 OA dated Feb. 18, 2022).
Jang et al. “Non-CE8: Modification on SbTMVP Process Regarding with CPR,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting, Marrakech, MA, Jan. 9-18, 2019, document JVET-M0335, 2019. (cited in JP2020-568474 OA dated Feb. 8, 2022).
Lai et al. “CE8-Related: Clarification on Interaction Between CPR and other Inter Coding Tools,” Joint Video Experts feram (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting, Marrakech, MA, Jan. 9-18, 2019, document JVET-M0175, 2019. (cited in JP2020-568474 OA dated Feb. 8, 2022).
Solovyev et al. “Non-CE4: Merge Mode Modification,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 11th Meeting: Ljubljana, SI, Jul. 10-18, 2018, document JVET-K0056, 2018. (cited in CN201910907742.5 OA dated Apr. 8, 2022).
Xu et al. “Non-CE8: Mismatch Between Text Specification and Reference Software on ATMVP Candidate Derivation When CPR is Enabled,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 29/WG 11, 13th Meeting, Marrakech, MA, Jan. 9-18, 2019, document JVET-M0409, 2019. (cited in JP2020-568474 OA dated Feb. 8, 2022).
Yang et al. “BoG Report on CE4 Related Contributions,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 11th Meeting: Ljubljana, SI, Jul. 10-18, 2018, document JVET-K0546, 2018. (cited in CN201910907742.5 OA dated Apr. 8, 2022).
Zhao et al. “Intra Mini-Block Copy Algorithm for Screen Content Coding,” Journal of Computer Applications, 2016, 36(7): 1938-1943. (cited in CN201910487926.0 OA dated Feb. 18, 2022).
Zuo et al. “Intra Block Copy for Intra-Frame Coding,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 10th Meeting: San Diego, US, Apr. 10-20, 2018, document JVET-J0042, 2018. (cited in CN201910487926.0 OA dated Feb. 18, 2022).
Non Final Office Action from U.S. Appl. No. 17/019,629 dated Jun. 8, 2022.
Bross et al. “Versatile Video Coding (Draft 3),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 12th Meeting, Macao, CN, Oct. 3-12, 2018. document JVET-L1001, 2018.
Zhang et al. “AHG16: Clean-up on MV Rounding,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting, Marrakech, MA Jan. 9-18, 2019, document JVET-M0265, 2019.
Extended European Search Report from European Patent Application No. 19882864.2 dated Mar. 21, 2022 (9 pages).
Koyama et al. “Modification of Derivation Process of Motion Vector Information for Interlace Format,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG16 WP3 and ISO/IEC JTC1/SC29/WG11 7th Meeting: Geneva, CH, Nov. 21-30, 2011, document JCTVC-G196, 2011. (cited in JP2021-524354 OA dated Aug. 2, 2022).
Shimada et al. “Non-CE9/Non-CE13: Averaged Merge Candidate,” Joint Collaborative Team on Video Coding (JCT-VC)of ITU-T SG16 WP3 and ISO/IEC JTC1/SC29/WG11 7th Meeting: Geneva, CH, Nov. 21-30, 2011, document JCTVC-G195,2011. (cited in JP2021-524354 OA dated Aug. 2, 2022).
Han et al. “ A Dynamic Motion Vector Referencing Scheme for Video Coding,” 2016 IEEE International Conference on Image Processing (ICIP), 2016, pp. 2032-2036.
Non Final Office Action from U.S. Appl. No. 17/210,797 dated Aug. 2, 2022.
Non Final Office Action from U.S. Appl. No. 17/529,607 dated Oct. 31, 2022.
Non Final Office Action from U.S. Appl. No. 17/525,745 dated Nov. 10, 2022.
Non Final Office Action from U.S. Appl. No. 17/412,771 dated Feb. 16, 2023.
Non Final Office Action from U.S. Appl. No. 17/732,849 dated Mar. 2, 2023.
Examination Report from Indian Patent Application No. 202228045435 dated Dec. 26, 2022.
Related Publications (1)
Number Date Country
20210227234 A1 Jul 2021 US
Continuations (2)
Number Date Country
Parent 17071412 Oct 2020 US
Child 17221122 US
Parent PCT/IB2019/055247 Jun 2019 US
Child 17071412 US