Patent Grant
12132888
The present disclosure relates to video coding and decoding techniques, devices and systems.
In spite of the advances in video compression, digital video still accounts for the largest bandwidth use on the internet and other digital communication networks. As the number of connected user devices capable of receiving and displaying video increases, it is expected that the bandwidth demand for digital video usage will continue to grow.
The present disclosure describes various embodiments for buffer management and block vector coding for intra block copy mode for decoding or encoding video or images.
In one example aspect, a method of visual media processing is disclosed. The method includes determining, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the current video block, a block vector (BVx, BVy), wherein validity of the block vector (BVx, BVy) is independent of (1) a location (P, Q) of a sample block and/or (2) whether a sample at the location (P, Q) is reconstructed, and/or (3) a location of the current video block, wherein, the block vector (BVx, BVy) represents a pixel displacement between the current video block and the sample block; and performing, using the block vector, the conversion in an intra block copy mode which is based on a reconstructed block located in same video region with the current video block comprising reference samples used for deriving a prediction block of the current video block, wherein, during the conversion, a prediction sample with a location (A, B) from reference samples in a buffer is determined at least according to a size of the buffer and/or the block vector (BVx, BVy).
In another example aspect, another method of visual media processing is disclosed. The method includes determining, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data, whether a block vector (BVx, BVy) corresponding to the current video block is valid according to a rule, wherein the block vector (BVx, BVy) represents a pixel displacement between the current video block and a sample block; and performing, using the block vector, the conversion based on a reference region from the current picture comprising reference samples used for deriving a prediction block of the current video block, wherein the rule specifies that the block vector (BVx, BVy) is valid in case that (1) one or more samples from the sample block are outside the current picture and/or (2) one or more samples from the sample block are outside at least one coding tree unit (CTU) associated with the current video block, and/or (3) one or more samples from the sample block fail to be reconstructed.
In yet another example aspect, another method of visual media processing is disclosed. The method includes performing a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data, wherein, the conversion is based on a reference region from the current picture comprising reference samples used for deriving a prediction block of the current video block, and wherein a virtual buffer of a defined size is used for tracking availability of the reference samples for deriving the prediction block.
In yet another example aspect, another method of visual media processing is disclosed. The method includes maintaining, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data, a buffer comprising reference samples from the current picture for a derivation of a prediction block of the current video block, wherein one or more reference samples in the buffer that are marked unavailable for the derivation have values outside of a pixel value range.
In another example aspect, another method of video processing is disclosed. The method includes performing a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data using a buffer comprising reference samples from the current picture for derivation of a prediction block of the current video block, wherein the conversion is based according to rule which specifies that, for the bitstream representation to conform the rule, a reference sample in the buffer is to satisfy a bitstream conformance constraint.
In yet another example aspect, a video encoder or decoder apparatus comprising a processor configured to implement an above described method is disclosed.
In another example aspect, a computer readable program medium is disclosed. The medium stores code that embodies processor executable instructions for implementing one of the disclosed methods.
These, and other, aspects are described in greater detail in the present disclosure.
Section headings are used in the present disclosure for ease of understanding and do not limit scope of the disclosed embodiments in each section only to that section. The present disclosure describes various embodiments for buffer management and block vector coding for intra block copy mode for decoding or encoding video or images.
The present disclosure is related to video coding technologies. Specifically, it is related to intra block copy in video coding. It may be applied to the standard under development, e.g., versatile video coding (VVC). It may be also applicable to future video coding standards or video codec.
Video coding standards have evolved primarily through the development of the well-known International Telecommunication Union (ITU) Telecommunication Standardization Sector (ITU-T) and International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) standards. The ITU-T produced H.261 and H.263, ISO/IEC produced Moving Picture Experts Group (MPEG)-1 and MPEG-4 Visual, and the two organizations jointly produced the H.262/MPEG-2 Video and H.264/MPEG-4 Advanced Video Coding (AVC) and H.265/HEVC standards. Since H.262, the video coding standards are based on the hybrid video coding structure wherein temporal prediction plus transform coding are utilized. To explore the future video coding technologies beyond HEVC, Joint Video Exploration Team (JVET) was founded by Video Coding Experts Group (VCEG) and MPEG jointly in 2015. Since then, many new methods have been adopted by JVET and put into the reference software named Joint Exploration Model (JEM). In April 2018, the Joint Video Expert Team (JVET) between VCEG (Q6/16) and ISO/IEC JTC1 SC29/WG11 (MPEG) was created to work on the VVC standard targeting a 50% bitrate reduction compared to HEVC.
Each inter-predicted picture unit (PU) has motion parameters for one or two reference picture lists. Motion parameters include a motion vector (MV) and a reference picture index. Usage of one of the two reference picture lists may also be signalled using inter_pred_idc. Motion vectors may be explicitly coded as deltas relative to predictors.
When a coding unit (CU) is coded with skip mode, one PU is associated with the CU, and there are no significant residual coefficients, no coded motion vector delta or reference picture index. A merge mode is specified whereby the motion parameters for the current PU are obtained from neighboring PUs, including spatial and temporal candidates. The merge mode can be applied to any inter-predicted PU, not only for skip mode. The alternative to merge mode is the explicit transmission of motion parameters, where motion vector (to be more precise, motion vector differences (MVD) compared to a motion vector predictor), corresponding reference picture index for each reference picture list and reference picture list usage are signalled explicitly per each PU. Such a mode is named advanced motion vector prediction (AMVP) in this disclosure.
When signalling indicates that one of the two reference picture lists is to be used, the PU is produced from one block of samples. This is referred to as ‘uni-prediction’. Uni-prediction is available both for P-slices and B-slices.
When signalling indicates that both of the reference picture lists are to be used, the PU is produced from two blocks of samples. This is referred to as ‘bi-prediction’. Bi-prediction is available for B-slices only.
The following text provides the details on the inter prediction modes specified in HEVC. The description will start with the merge mode.
Current picture referencing (CPR), or once named as intra block copy (IBC) has been adopted in HEVC screen content coding extensions (HEVC-SCC) and the current VVC test model (VTM). IBC extends the concept of motion compensation from inter-frame coding to intra-frame coding. As demonstrated in
Following a BV to find its reference block, the prediction can be generated by copying the reference block. The residual can be generated by subtracting the reference pixels from the original signals. Then transform and quantization can be applied as in other coding modes.
However, when a reference block is outside of the picture, or overlaps with the current block, or outside of the reconstructed area, or outside of the valid area restricted by some constraints, part or all pixel values are not defined. Basically, there are two solutions to handle such a problem. One is to disallow such a situation, e.g., in bitstream conformance. The other is to apply padding for those undefined pixel values. The following sub-sections describe the solutions in detail.
In the screen content coding extensions of HEVC, when a block uses current picture as reference, it should guarantee that the whole reference block is within the available reconstructed area, as indicated in the following spec text:
The variables offsetX and offsetY are derived as follows:
offsetX=(ChromaArrayType==0)?0:(myCLX[0]&0x7?2:0) (8-104)
offsetY=(ChromaArrayType==0)?0:(myCLX[1]&0x7?2:0) (8-105)
It is a requirement of bitstream conformance that when the reference picture is the current picture, the luma motion vector mvLX shall obey the following constraints:
Thus, the case that the reference block overlaps with the current block or the reference block is outside of the picture will not happen. There is no need to pad the reference or prediction block.
In a VVC test model, the whole reference block should be with the current coding tree unit (CTU) and does not overlap with the current block. Thus, there is no need to pad the reference or prediction block.
When dual tree is enabled, the partition structure may be different from luma to chroma CTUs. Therefore, for the 4:2:0 color format, one chroma block (e.g., CU) may correspond to one collocated luma region which have been split to multiple luma CUs.
The chroma block could only be coded with the CPR mode when the following conditions shall be true:
If any of the two conditions is false, the chroma block shall not be coded with CPR mode.
It is noted that the definition of ‘valid BV’ has the following constraints:
In some examples, the reference area for CPR/IBC is restricted to the current CTU, which is up to 128×128. The reference area is dynamically changed to reuse memory to store reference samples for CPR/IBC so that a CPR/IBC block can have more reference candidate while the reference buffer for CPR/IBC can be kept or reduced from one CTU.
Suppose that the current luma CU's position relative to the upper-left corner of the picture is (x, y) and block vector is (BVx, BVy). In the current design, if the BV is valid can be told by that the luma position ((x+BVx)>>6<<6+(1<<7), (y+BVy)>>6<<6) has not been reconstructed and ((x+BVx)>>6<<6+(1<<7), (y+BVy)>>6<<6) is not equal to (x>>6<<6, y>>6<<6).
The basic idea of in-loop reshaping (ILR) is to convert the original (in the first domain) signal (prediction/reconstruction signal) to a second domain (reshaped domain)
The in-loop luma reshaper is implemented as a pair of look-up tables (LUTs), but only one of the two LUTs needs to be signalled as the other one can be computed from the signalled LUT. Each LUT is a one-dimensional, 10-bit, 1024-entry mapping table (1D-LUT). One LUT is a forward LUT, FwdLUT, that maps input luma code values Yi to altered values Yr: Yr=FwdLUT[Yi]. The other LUT is an inverse LUT, InvLUT, that maps altered code values Yr to Ŷi:Ŷi=InvLUT[Yr]. (Ŷi represents the reconstruction values of Yi.).
Conceptually, piecewise linear (PWL) is implemented in the following way:
Let x1, x2 be two input pivot points, and y1, y2 be their corresponding output pivot points for one piece. The output value y for any input value x between x1 and x2 can be interpolated by the following equation:
y=((y2−y1)/(x2−x1))*(x−x1)+y1
In fixed point implementation, the equation can be rewritten as:
y=((m*x+2FP_PREC-1)>>FP_PREC)+c
where m is scalar, c is an offset, and FP_PREC is a constant value to specify the precision.
In some examples, the PWL model is used to precompute the 1024-entry FwdLUT and InvLUT mapping tables; but the PWL model also allows embodiments to calculate identical mapping values on-the-fly without pre-computing the LUTs.
A method of the in-loop luma reshaping provides a lower complexity pipeline that also eliminates decoding latency for block-wise intra prediction in inter slice reconstruction. Intra prediction is performed in reshaped domain for both inter and intra slices.
Intra prediction is always performed in reshaped domain regardless of slice type. With such arrangement, intra prediction can start immediately after previous transform unit (TU) reconstruction is done. Such arrangement can also provide a unified process for intra mode instead of being slice dependent.
16-piece PWL models are tested for luma and chroma residue scaling instead of the 32-piece PWL models.
Inter slice reconstruction with in-loop luma reshaper (shaded blocks indicate signal in reshaped domain: luma residue; intra luma predicted; and intra luma reconstructed).
Luma-dependent chroma residue scaling is a multiplicative process implemented with fixed-point integer operation. Chroma residue scaling compensates for luma signal interaction with the chroma signal. Chroma residue scaling is applied at the TU level. More specifically, the following applies:
The average is used to identify an index in a PWL model. The index identifies a scaling factor cScaleInv. The chroma residual is multiplied by that number.
It is noted that the chroma scaling factor is calculated from forward-mapped predicted luma values rather than reconstructed luma values.
The parameters are (currently) sent in the tile group header (similar to adaptive loop filter (ALF)). These reportedly take 40-100 bits.
In some examples, the added syntax is highlighted in italics.
In 7.3.2.1 Sequence parameter set RBSP syntax
Descriptor
sps_seq_parameter_set_id
...
sps_triangle_enabled_flag
sps_ladf_enabled_flag
sps_num_ladf_intervals_minus2
sps_ladf_lowest_interval_qp_offset
sps_ladf_qp_offset[i ]
sps_ladf_delta_threshold_minus1[i ]
}
}
In 7.3.3.1 General tile
group
header
syntax
Descriptor
u(1)
tile_group_reshaper_model ( )
u(1)
if (
tile_group_reshaper_enable_flag && (!(
qtbtt_dual_tree_intra_flag && tile_group_type == I ) ) )
u(1)
Add a new syntax table tile
group
reshaper model:
tile_group_reshaper_model ( ) {
ue(v)
ue(v)
_
ue(v)
for ( i = reshaper_model_min_bin_idx; i < =
reshaper_model_max_bin_idx; i++ ) {
[ i ]
u(v)
if (
reshaper_model_bin_delta_abs_CW[ i ] ) > 0)
[ i ]
u(1)
}
}
In General sequence parameter set RBSP semantics, add the following semantics:
sps_reshaper_enabled_flag equal to 1 specifies that reshaper is used in the coded video sequence (CVS). sps_reshaper_enabled_flag equal to 0 specifies that reshaper is not used in the CVS.
In tile group header syntax, add the following semantics
tile_group_reshaper_model_present_flag equal to 1 specifies tile_group_reshaper_model( ) is present in tile group header. tile_group_reshaper_model_present_flag equal to 0 specifies tile_group_reshaper_model( ) is not present in tile group header. When tile_group_reshaper_model_present_flag is not present, it is inferred to be equal to 0.
tile_group_reshaper_enabled_flag equal to 1 specifies that reshaper is enabled for the current tile group. tile_group_reshaper_enabled_flag equal to 0 specifies that reshaper is not enabled for the current tile group. When tile_group_reshaper_enable_flag is not present, it is inferred to be equal to 0.
tile_group_reshaper_chroma_residual_scale_flag equal to 1 specifies that chroma residual scaling is enabled for the current tile group. tile_group_reshaper_chroma_residual_scale_flag equal to 0 specifies that chroma residual scaling is not enabled for the current tile group. When tile_group_reshaper_chromaresidual_scale_flag is not present, it is inferred to be equal to 0.
Add tile group reshaper model( ) syntax
reshape_model_min_bin_idx specifies the minimum bin (or piece) index to be used in the reshaper construction process. The value of reshape_model_min_bin_idx shall be in the range of 0 to MaxBinIdx, inclusive. The value of MaxBinIdx shall be equal to 15.
reshape_modeldeltamax_bin_idx specifies the maximum allowed bin (or piece) index MaxBinIdx minus the maximum bin index to be used in the reshaper construction process. The value of reshape_model_max_bin_idx is set equal to MaxBinIdx−reshape_model_delta_max_bin_idx.
reshaper_model_bin_delta_abs_cw_prec_minus1 plus 1 specifies the number of bits used for the representation of the syntax reshape_model_bin_delta_abs_CW[i].
reshape_model_bin_delta_abs_CW[i] specifies the absolute delta codeword value for the ith bin.
reshaper_model_bin_delia_sign_CW_flag[i] specifies the sign of reshape_model_bin_delta_abs_CW[i] as follows:
When reshape_model_bin_delta_sign_CW_flag[i] is not present, it is inferred to be equal to 0.
The variable RspDeltaCW[i]=(1 2*reshape_model_bin_deltasign_CW[i])*reshape_model_bin_delta_abs_CW[i];
The variable RspCW[i] is derived as following steps:
The variable OrgCW is set equal to (1<<BitDepthY)/(MaxBinIdx+1).
The value of RspCW[i] shall be in the range of 32 to 2*OrgCW−1 if the value of BitDepthy is equal to 10.
The variables InputPivot[i] with i in the range of 0 to MaxBinIdx+1, inclusive are derived as follows:
InputPivot[i]=i*OrgCW
The variable ReshapePivot[i] with i in the range of 0 to MaxBinIdx+1, inclusive, the variable ScaleCoef[i] and InvScaleCoeff[i] with i in the range of 0 to MaxBinIdx, inclusive, are derived as follows:
The variable ChromaScaleCoef[i] with i in the range of 0 to MaxBinIdx, inclusive, are derived as follows:
At the encoder side, each picture (or tile group) is firstly converted to the reshaped domain And all the coding process is performed in the reshaped domain. For intra prediction, the neighboring block is in the reshaped domain; for inter prediction, the reference blocks (generated from the original domain from decoded picture buffer) are firstly converted to the reshaped domain. Then the residuals are generated and coded to the bitstream.
After the whole picture (or tile group) finishes encoding/decoding, samples in the reshaped domain are converted to the original domain, then deblocking filter and other filters are applied.
Forward reshaping to the prediction signal is disabled for the following cases:
Current block is intra-coded.
Current block is coded as CPR (current picture referencing, aka intra block copy, IBC).
Current block is coded as combined inter-intra mode (CIIP) and the forward reshaping is disabled for the intra prediction block.
In the current design of CPR/IBC, some problems exist.
In some embodiments, a regular buffer can be used for CPR/IBC block to get reference.
A function isRec(x,y) is defined to indicate if pixel (x,y) has been reconstructed and be referenced by IBC mode. When (x,y) is out of picture, of different slice/tile/brick, isRec(x,y) returns false; when (x,y) has not been reconstructed, isRec(x,y) returns false. In another example, when sample (x,y) has been reconstructed but some other conditions are satisfied, it may also be marked as unavailable, such as out of the reference area/in a different VPDU, and isRec(x,y) returns false.
A function isRec(c, x,y) is defined to indicate if sample (x,y) for component c is available. For example, if the sample (x, y) has not yet been reconstructed, it is marked as unavailable. In another example, when sample (x,y) has been reconstructed but some other conditions are satisfied, it may also be marked as unavailable, such as it is out of picture/in a different slice/tile/brick/in a different VPDU, out of allowed reference area. isRec(c, x,y) returns false when sample (x, y) is unavailable, otherwise, it returns true.
In the following discussion, the reference samples can be reconstructed samples. It is noted that ‘pixel buffer’ may response to ‘buffer of one color component’ or ‘buffer of multiple color components’.
1. It is proposed to use a M×N pixel buffer to store the luma reference samples for CPR/IBC.
2. M and/or N may be different in different profiles/levels/tiers defined in a standard. It is proposed to use another Mc×Nc pixel buffer to store the chroma reference samples for CPR/IBC.
3. It is proposed to use a M×N sample buffer to store the RGB reference samples for CPR/IBC.
4. It is proposed that the buffer can store reconstructed pixels before loop-filtering. Loop-filtering may refer to deblocking filter, ALF, sample adaptive offset (SAO), a cross-component ALF, or any other filters.
6. It is proposed that the buffer can store both reconstructed samples before loop-filtering and after loop-filtering. Loop-filtering may refer to deblocking filter, ALF, SAO, a cross-component ALF, or any other filters.
7. It is proposed that the buffer stores samples with a given bit-depth which may be different from the bit-depth for coded video data.
8. It is proposed to initialize the buffer with a given value
9. Alternatively, it is proposed to initialize the buffer with decoded pixels from previously coded blocks.
10. For a block to use pixels in the buffer as a reference, it can use a position (x,y), x=0,1,2, . . . ,M−1; y=0,1,2, . . . ,N−1, within the buffer to indicate where to get the reference.
11. Alternatively, the reference position can be denoted as 1=y*M+x, 1=0,1, . . . ,M*N−1.
12. Denote the upper-left position of a block related to the current CTU as (x0,y0), a block vector (BVx,BVy)=(x−x0,y−y0) may be sent to the decoder to indicate where to get the reference in the buffer.
13. Alternatively, a block vector (BVx,BVy) can be defined as (x−x0+Tx,y−y0+Ty) where Tx and Ty are predefined offsets.
14. For any pixel (x0, y0) and (BVx, BVy), its reference in the buffer can be found at (x0+BVx, y0+BVy).
15. For any pixel (x0, y0) and (BVx, BVy), when (x0+BVx, y0+BVy) is outside of the buffer, its reference value may be derived from the values in the buffer.
16. It may disallow a certain coordinate outside of the buffer range.
17. When the signalled or derived block vector of one block points to somewhere outside the buffer, padding may be applied according to the buffer.
18. The methods to handle out of the buffer reference may be different horizontally and vertically or may be different according to the location of the current block (e.g., closer to picture boundary or not).
19. Each component of a block vector (BVx, BVy) or one of the components may be normalized to a certain range.
20. BVx and BVy may have different normalized ranges.
21. A block vector difference (BVDx, BVDy) can be normalized to a certain range.
a. In one example, BVDx can be replaced by (BVDx mod M) wherein the function mod returns the reminder.
22. BVDx and BVDy may have different normalized ranges.
Denote the width and height of an IBC buffer as Wbuf and Hbuf. For a W×H block (may be a luma block, chroma block, CU, TU, 4×4, 2×2, or other subblocks) starting from (X, Y) relative to the upper-left corner of a picture, the following may apply to tell if a block vector (BVx, BVy) is valid or not. Let Wpic and Hpic be the width and height of a picture and; Wctu and Hctu be the width and height of a CTU. Function floor(x) returns the largest integer no larger than x. Function isRec(x, y) returns whether sample (x, y) has been reconstructed.
23. Block vector (BVx, BVy) may be set as valid even if any reference position is outside of picture boundary.
24. Block vector (BVx, BVy) may be set as valid even if any reference position is outside of the current CTU row.
25. Block vector (BVx, BVy) may be set as valid even if any reference position is outside of the current and left (n−1) CTUs, where n is the number of CTUs (including or excluding the current CTU) that can be used as reference area for IBC.
26. Block vector (BVx, BVy) may be set as valid even if a certain sample has not been reconstructed.
27. Block vector (BVx, BVy) may be always set as valid when a block is not of the 1st CTU in a CTU row.
28. Block vector (BVx, BVy) may be always set as valid when the following 3 conditions are all satisfied:
X+BVx>=0;
Y+BVy>=floor(Y/Hctu); and
isRec(X+BVx+W−1,Y+BVy+H−1) true.
29. When a block vector (BVx, BVy) is valid, sample copying for the block may be based on the block vector.
30. When coding a new picture or tile, the buffer may be reset.
31. When finishing coding of a VPDU, the buffer may be updated with the reconstructed values of the VPDU.
32. When finishing coding of a CTU, the buffer may be updated with the reconstructed values of the CTU.
33. The buffer can be reset at the beginning of each CTU row.
34. When finishing coding a block starting from (x,y), the buffer's corresponding area, starting from (x,y) will be updated with reconstruction from the block.
35. When finishing coding a block relative to the picture, the buffer's corresponding area will be updated with reconstruction from the block.
36. When finishing coding a block starting from (x,y), the buffer's corresponding area, starting from (xb,yb) will be updated with reconstruction from the block wherein (xb, yb) and (x, y) are two different coordinates.
37. For above examples, the reconstructed values of a block may indicate the reconstructed values before filters (e.g., deblocking filter) are applied.
38. When the buffer is updated from reconstructed samples, the reconstructed samples may be firstly modified before being stored, such as sample bit-depth can be changed.
39. When use the buffer samples to form prediction, a preprocessing can be applied.
40. The buffer can be updated in a given order.
41. When the buffer is full, the samples in the buffer can be replaced with latest reconstructed samples.
42. Instead of always using the previously coded three 64×64 blocks as a reference region, it is proposed to adaptively change it based on current block's (or VPDU's) location.
43. Instead of using the z-scan order, vertical scan order may be utilized instead.
The following, the width and height of a VPDU is denoted as WVPDU (e.g., 64) and HVPDU (e.g., 64), respectively in luma samples. Alternatively, WVPDU and/or HVPDU may denote the width and/or height of another video unit (e.g., CTU).
44. A virtual buffer may be maintained to keep track of the IBC reference region status.
45. An array may be used to track the availability of each sample associated with the virtual buffer.
46. After finishing decoding a VPDU or a video unit, certain samples associated with the virtual buffer may be marked as unavailable for IBC reference.
47. The position of most recently decoded VPDU may be recorded to help to identify which samples associated with the virtual buffer may be marked as unavailable.
48. When a CU contains multiple VPDUs, instead of applying IBC reference availability marking process according to VPDU, the IBC reference availability marking process may be according to the CU.
49. For a reference block or sub-block, the reference availability status of the upper-right corner may not need to be checked to tell if the block vector associated with the reference block is valid or not.
50. The IBC buffer size may depend on VPDU size (wherein the width/height is denoted by vSize) and/or CTB/CTU size (wherein the width/height is denoted by ctbSize).
51. An IBC buffer may contain values outside of pixel range, which indicates that the position may not be available for IBC reference, e.g., not utilized for predicting other samples.
52. Availability marking for samples in the IBC buffer may depend on position of the current block, size of the current block, CTU/CTB size and VPDU size. In one example, let (xCb, yCb) denotes the block's position relative to top-left of the picture; ctb Size is the size (i.e., width and/or height) of a CTU/CTB; vSize=min(ctbSize, 64); wIbcBuf and hIbcBuf are the IBC buffer width and height.
53. At the beginning of decoding a video unit (e.g., VPDU (xV, yV)) relative to the top-left position of a picture, corresponding positions in the IBC buffer may be set to a value outside of pixel range.
54. A bitstream conformance constraint may be according to the value of a sample in the IBC buffer.
55. A bitstream conformance constraint may be set according to the availability indication in the IBC buffer.
56. Bitstream conformance constraints may depend on partitioning tree types and current CU's coding treeType
57. The prediction for IBC can have a lower precision than the reconstruction.
58. Part of the prediction of IBC can have a lower precision and the other part has the same precision as the reconstruction.
59. When CTU size is M×M and reference area size is nM×nM, the reference area is the nearest available n×n CTU in a CTU row.
60. When CTU size is M and reference area size is nM, the reference area is the nearest available n−1 CTUs in a CTU row/tile.
61. When CTU size is M, VPDU size is kM and reference area size is nM, and the reference area is the nearest available n−k CTUs in a CTU row/tile.
62. For a w×h block with upper-left corner being (x, y) using IBC, there are constraints that keep reference block from certain area for memory reuse, wherein w and h are width and height of the current block.
63. When CTU size is not M×M and reference area size is nM×nM, the reference area is the nearest available n×n−1 CTU in a CTU row.
64. For a CU within a 64×64 block starting from (2m*64, 2n*64), i.e., an upper-left 64×64 block in a 128×128 CTU, its IBC prediction can be from reconstructed samples in the 64×64 block starting from ((2m−2)*64, 2n*64), the 64×64 block starting from ((2m−1)*64, 2n*64), the 64×64 block starting from ((2m−1)*64, (2n+1)*64) and the current 64×64 block.
65. For a CU within a 64×64 block starting from ((2m+1)*64, (2n+1)*64), i.e., a bottom-right 64×64 block in a 128×128 CTU, its IBC prediction can be from the current 128×128 CTU.
66. For a CU within a 64×64 block starting from ((2m+1)*64, 2n*64), i.e., an upper-right 64×64 block in a 128×128 CTU, its IBC prediction can be from reconstructed samples in the 64×64 block starting from ((2m−1)*64, 2n*64), the 64×64 block starting from ((2m−1)*64, (2n+1)*64), the 64×64 block starting from (2m*64, 2n*64) and the current 64×64 block.
67. For a CU within a 64×64 block starting from (2m*64, (2n+1)*64), i.e., a bottom-left 64×64 block in a 128×128 CTU, its IBC prediction can be from reconstructed samples in the 64×64 block starting from ((2m−1)*64, (2n+1)*64), the 64×64 block starting from (2m*64, 2n*64); the 64×64 block starting from ((2m+1)*64, 2n*64) and the current 64×64 block.
68. It is proposed to adjust the reference area based on which 64×64 blocks the current CU belongs to.
69. For a block starting from (x,y) and with block vector (BVx, BVy), if isRec(((x+BVx)>>6<<6)+128−(((y+BVy)>>6)&1)*64+(x %64), ((y+BVy)>>6<<6)+(y %64)) is true, the block vector is invalid.
70. For a chroma block in 4:2:0 format starting from (x,y) and with block vector (BVx, BVy), if isRec(((x+BVx)>>5<<5)+64−(((y+BVy)>>5)&1)*32+(x %32), ((y+BVy)>>5<<5)+(y %32)) is true, the block vector is invalid.
71. The determination of whether a BV is invalid or not for a block of component c may rely on the availability of samples of component X, instead of checking the luma sample only.
72. For all bullets mentioned above, it is assumed that the reference buffer contains multiple M×M blocks (M=64). However, it could be extended to other cases such as the reference buffer contains multiple N×M blocks (e.g., N=128, M=64).
73. For all bullets mentioned above, further restrictions may be applied that the reference buffer should be within the same brick/tile/tile group/slice as the current block.
74. It is proposed to have K1 most recently coded VPDU, if available, in the 1st VPDU row of the CTU/CTB row and K2 most recently coded VPDU, if available, in the 2nd VPDU row of the CTU/CTB row as the reference area for IBC, excluding the current VPDU.
75. The above methods may be applied in different stages.
An embodiment of the buffer for IBC is described below.
The buffer size is 128×128. CTU size is also 128×128. For coding of the 1st CTU in a CTU row, the buffer is initialized with 128 (for 8-bit video signal). For coding of the k-th CTU in a CTU row, the buffer is initialized with the reconstruction before loop-filtering of the (k−1)-th CTU.
When coding a block starting from (x,y) related to the current CTU, a block vector (BVx, BVy)=(x−x0, y−y0) is sent to the decoder to indicate the reference block is from (x0,y0) in the IBC buffer. Suppose the width and height of the block are w and h respectively. When finishing coding of the block, a w×h area starting from (x,y) in the IBC buffer will be updated with the block's reconstruction before loop-filtering.
Suppose that CTU size is W×W, an embodiment of IBC buffer with size mW×W and bit-depth being B, at the decoder is as below.
At the beginning of decoding a CTU row, initialize the buffer with value (1<<(B−1)) and set the starting point to update (xb, yb) to be (0,0).
When a CU starting from (x, y) related to a CTU upper-left corner and with size w×h is decoded, the area starting from (xb+x, yb+y) and w×h size will be updated with the reconstructed pixel values of the CU, after bit-depth aligned to B-bit.
After a CTU is decoded, the starting point to update (xb, yb) will be set as ((xb+W)mod mW, 0).
When decoding an IBC CU with block vector (BVx, BVy), for any pixel (x, y) related to a CTU upper-left corner, its prediction is extracted from the buffer at position ((x+BVx)mod mW, (y+BVy) mode W) after bit-depth alignment to the bit-depth of prediction signals.
In one example, B is set to 7, or 8 while the output/input bit-depth of the block may be equal to 10.
For a luma CU or joint luma/chroma CU starting from (x,y) related to the upper-left corner of a picture and a block vector (BVx, BVy), the block vector is invalid when isRec(((x+BVx)>>6<<6)+128−(((y+BVy)>>6)&1)*64+(x %64), ((y+BVy)>>6<<6)+(y %64)) is true.
For a chroma CU starting from (x,y) related to the upper-left corner of a picture and a block vector (BVx, BVy), the block vector is invalid when isRec(((x+BVx)>>5<<5)+64−(((y+BVy)>>5)&1)*32+(x %32), ((y+BVy)>>5<<5)+(y %32)) is true.
For a chroma block or sub-block starting from (x,y) in 4:2:0 format related to the upper-left corner of a picture and a block vector (BVx, BVy), the block vector is invalid when isRec(c, (x+BVx+64, y+BVy) is true, where c is a chroma component.
For a chroma block or sub-block starting from (x,y) in 4:4:4 format related to the upper-left corner of a picture and a block vector (BVx, BVy), the block vector is invalid when isRec(c, (x+BVx+128, y+BVy) is true, where c is a chroma component.
For a luma CU or joint luma/chroma CU starting from (x,y) related to the upper-left corner of a picture and a block vector (BVx, BVy), the block vector is invalid when isRec(((x+BVx)>>6<<6)+128−(((y+BVy)>>6)&1)*64+(x %64), ((y+BVy)>>6<<6)+(y %64)) is true.
For a chroma block or sub-block starting from (x,y) in 4:2:0 format related to the upper-left corner of a picture and a block vector (BVx, BVy), the block vector is invalid when isRec(c, ((x+BVx)>>5<<5)+64−(((y+BVy)>>5)&1)*32+(x %32), ((y+BVy)>>5<<5)+(y %32)) is true, where c is a chroma component.
This embodiment is an embodiment of keeping two most coded VPDUs in the 1st VPDU row and one most coded VPDU in the rd VPDU row of a CTU/CTB row, excluding the current VPDU.
When VPDU coding order is top to bottom and left to right, the reference area is illustrated as in
When VPDU coding order is left to right and top to bottom and the current VPDU is not to the right side of the picture boundary, the reference area is illustrated as in
When VPDU coding order is left to right and top to bottom and the current VPDU is to the right side of the picture boundary, the reference area may be illustrated as
Given a luma block (x, y) with size w×h, a block vector (BVx, BVy) is valid or not can be told by checking the following condition:
isRec(((x+BVx+128)>>6<<6)−(refy&0x40)+(x%64), ((y+BVy)>>6<<6)+(refy>>6==y>>6)?(y%64):0), where refy=(y&0x40)?(y+BVy):(y+BVy+w−1).
If the above function returns true, the block vector (BVx, BVy) is invalid, otherwise the block vector might be valid.
If CTU size is 192×128, a virtual buffer with size 192×128 is maintained to track the reference samples for IBC.
A sample (x, y) relative to the upper-left corner of the picture is associated with the position (x %192, y %128) relative to the upper-left corner of the buffer. The following steps show how to mark availability of the samples associate with the virtual buffer for IBC reference.
A position (xPrevVPDU, yPrevVPDU) relative to the upper-left corner of the picture is recorded to stand for the upper-left sample of the most recently decoded VPDU.
If CTU size is 128×128 or CTU size is greater than VPDU size (e.g., 64×64 in current design) or CTU size is greater than VPDU size (e.g., 64×64 in current design), a virtual buffer with size 192×128 is maintained to track the reference samples for IBC. In the following, when a<0, (a % b) is defined as floor(a/b)*b, where floor (c) returns the largest integer no larger than c.
A sample (x, y) relative to the upper-left corner of the picture is associated with the position (x %192, y %128) relative to the upper-left corner of the buffer. The following steps show how to mark availability of the samples associate with the virtual buffer for IBC reference.
A position (xPrevVPDU, yPrevVPDU) relative to the upper-left corner of the picture is recorded to stand for the upper-left sample of the most recently decoded VPDU.
If CTU size is S×S, S is not equal to 128, let Wbuf be equal to 128*128/S. A virtual buffer with size Wbuf×S is maintained to track the reference samples for IBC. The VPDU size is equal to the CTU size in such a case.
A position (xPrevVPDU, yPrevVPDU) relative to the upper-left corner of the picture is recorded to stand for the upper-left sample of the most recently decoded VPDU.
If CTU size is 128×128 or CTU size is greater than VPDU size (e.g., 64×64 in current design) or CTU size is greater than VPDU size (e.g., 64×64 in current design), a virtual buffer with size 256×128 is maintained to track the reference samples for IBC. In the following, when a <0, (a % b) is defined as floor(a/b)*b, where floor(c) returns the largest integer no larger than c.
A sample (x, y) relative to the upper-left corner of the picture is associated with the position (x %256, y %128) relative to the upper-left corner of the buffer. The following steps show how to mark availability of the samples associate with the virtual buffer for IBC reference.
A position (xPrevVPDU, yPrevVPDU) relative to the upper-left corner of the picture is recorded to stand for the upper-left sample of the most recently decoded VPDU.
When CTU size is not 128×128 or less than 64×64 or less than 64×64, the same process applies as in the previous embodiment, i.e., embodiment #14.
An IBC reference availability marking process is described as follows. The changes are indicated in bolded, underlined, italicized text in this disclosure.
Descriptor
_
_
_
_
_
_
_
_
_
Descriptor
This process is invoked when decoding a coding unit coded in IBC prediction mode.
Inputs to this process are:
For each coding subblock at subblock index (xSbIdx, ySbIdx) with xSbIdx=0 . . . numSbX−1, and ySbIdx=0 . . . numSbY−1, the following applies:
Inputs to this process are:
Output of this process are
This is identical to the previous embodiment except for the following changes:
Descriptor
The changes in some examples are indicated in bolded, underlined, text in this disclosure.
Descriptor
When all the following conditions are true, the history-based motion vector predictor (HMVP) list for the shared merging candidate list region is updated by setting NumHmvpSmrIbcCand equal to NumHmvpIbcCand, and setting HmvpSmrIbcCandList[i] equal to HmvpIbcCandList[i] for i=0 . . . NumHmvpIbcCand−1:
The following assignments are made for x=x0 . . . x0+cbWidth−1 and y=y0 . . . y0+cbHeight−1:
CbPosX[x][y]=x0 (7-135)
CbPosY[x][y]=y0 (7-136)
CbWidth[x][y]=cbWidth (7-137)
CbHeight[x][y]=cbHeight (7-138)
Inputs to this process are:
Outputs of this process are:
The luma motion vector mvL is derived as follows:
The updating process for the history-based motion vector predictor list as specified in clause 8.6.2.6 is invoked with luma motion vector mvL.
Inputs to this process are:
Output of this process a reconstructed picture sample array recSamples
Depending on the value of the color component cIdx, the following assignments are made:
Depending on the value of slice_lmcs_enabled_flag, the following applies:
The changes in some examples are indicated in bolded, underlined, italicized text in this disclosure.
Descriptor
When all the following conditions are true, the history-based motion vector predictor list for the shared merging candidate list region is updated by setting NumHmvpSmrIbcCand equal to NumHmvpIbcCand, and setting HmvpSmrIbcCandList[i] equal to HmvpIbcCandList[i] for i=0 . . . NumHmvpIbcCand−1:
The following assignments are made for x=x0 . . . x0+cbWidth−1 and y=y0 . . . y0+cbHeight−1:
CbPosX[x][y]=x0 (7-135)
CbPosY[x][y]=y0 (7-135)
CbWidth[x][y]=cbWidth (7-135)
CbHeight[x][y]=cbHeight (7-135)
Inputs to this process are:
Outputs of this process are:
The luma motion vector mvL is derived as follows:
The updating process for the history-based motion vector predictor list as specified in clause 8.6.2.6 is Invoked With Luma Motion Vector mvL.
This process is invoked when decoding a coding unit coded in IBCprediction mode.
Inputs to this process are:
Outputs of this process are:
Inputs to this process are:
Output of this process a reconstructed picture sample array recSamples
Depending on the value of the color component cIdx, the following assignments are made:
Depending on the value of slice_lmcs_enabled_flag, the following applies:
The changes in some examples are indicated in bolded, underlined, text in this disclosure.
Descriptor
When all the following conditions are true, the history-based motion vector predictor list for the shared merging candidate list region is updated by setting NumHmvpSmrIbcCand equal to NumHmvpIbcCand, and setting HmvpSmrIbcCandList[i] equal to HmvpIbcCandList[i] for i=0 . . . NumHmvpIbcCand−1:
The following assignments are made for x=x0 . . . x0+cbWidth−1 and y=y0 . . . y0+cbHeight−1:
CbPosX[x][y]=x0 (7-135)
CbPosY[x][y]=y0 (7-136)
CbWidth[x][y]=cbWidth (7-137)
CbHeight[x][y]=cbHeight (7-138)
Inputs to this process are:
Outputs of this process are:
The luma motion vector mvL is derived as follows:
The updating process for the history-based motion vector predictor list as specified in clause 8.6.2.6 is invoked with luma motion vector mvL.
This process is invoked when decoding a coding unit coded in IBC prediction mode.
Inputs to this process are:
Inputs to this process are:
Output of this process are a reconstructed picture sample array recSamples and IBC buffer arrays ibcBufL, ibcBufCb, ibcBufCr.
Depending on the value of the color component cIdx, the following assignments are made:
Depending on the value of slice_lmcs_enabled_flag, the following applies:
The changes in some examples are indicated in bolded, underlined, italicized text in this disclosure.
Descriptor
When all the following conditions are true, the history-based motion vector predictor list for the shared merging candidate list region is updated by setting NumHmvpSmrIbcCand equal to NumHmvpIbcCand, and setting HmvpSmrIbcCandList[i] equal to HmvpIbcCandList[i] for i=0 . . . NumHmvpIbcCand−1:
The following assignments are made for x=x0 . . . x0+cbWidth−1 and y=y0 . . . y0+cbHeight−1:
CbPosX[x][y]=x0 (7-135)
CbPosY[x][y]=y0 (7-136)
CbWidth[x][y]=cbWidth (7-137)
CbHeight[x][y]=cbHeight (7-138)
Inputs to this process are:
Outputs of this process are:
The luma motion vector mvL is derived as follows:
The updating process for the history-based motion vector predictor list as specified in clause 8.6.2.6 is invoked with luma motion vector mvL.
This process is invoked when decoding a coding unit coded in IBC prediction mode.
Inputs to this process are:
Inputs to this process are:
Output of this process are a reconstructed picture sample array recSamples and IBC buffer arrays ibcBufL, ibcBufCb, ibcBufCr.
Depending on the value of the color component cIdx, the following assignments are made:
Depending on the value of slice_lmcs_enabled_flag, the following applies:
The following clauses describe some example preferred features implemented by embodiments of method 600 and other methods. Additional examples are provided in Section 4 of the present disclosure.
1. A method of video processing, comprising: determining, for a conversion between a current video block and a bitstream representation of the current video block, a size of a buffer to store reference samples for the current video block using an intra-block copy coding mode; and performing the conversion using the reference samples stored in the buffer.
2. The method of clause 1, wherein the size of the buffer is a predetermined constant.
3. The method of any of clauses 1-2, wherein the size is M×N, where M and N are integers.
4. The method of clause 3, wherein M×N is equal to 64×64 or 128×128 or 64×128.
5. The method of clause 1, wherein the size of the buffer is equal to a size of a coding tree unit of the current video block.
6. The method of clause 1, wherein the size of the buffer is equal to a size of a virtual pipeline data unit used during the conversion.
7. The method of clause 1, wherein the size of the buffer corresponds to a field in the bitstream representation.
8. The method of clause 7, wherein the field is included in the bitstream representation at a video parameter set or sequence parameter set or picture parameter set or a picture header or a slice header or a tile group header level.
9. The method of any of clauses 1-8, wherein the size of the buffer is different for reference samples for luma component and reference samples for chroma components.
10. The method of any of clauses 1-8, wherein the size of the buffer is dependent on chroma subsampling format of the current video block.
11. The method of any of clauses 1-8, wherein the reference samples are stored in RGB format.
12. The method of any of clauses 1-11, wherein the buffer is used for storing reconstructed samples before loop filtering and after loop filtering.
13. The method of clause 12, wherein loop filtering includes deblocking filtering or adaptive loop filtering (ALF) or sample adaptive offset (SAO) filtering.
14. A method of video processing, comprising: initializing, for a conversion between a current video block and a bitstream representation of the current video block, a buffer to store reference samples for the current video block using an intra-block copy coding mode using initial values for the reference samples; and performing the conversion using the reference samples stored in the buffer.
15. The method of clause 14, wherein the initial values correspond to a constant.
16. The method of any of clauses 14-15, wherein the initial values are a function of bit-depth of the current video block.
17. The method of clause 15, wherein the constant corresponds to a mid-grey value.
18. The method of clause 14, wherein the initial values correspond to pixel values of a previously decoded video block.
19. The method of clause 18, wherein the previously decoded video block corresponds to a decoded block prior to in-loop filtering.
20. The method of any of clauses 14-19, wherein a size of the buffer is at recited in one of clauses 1-13.
21. The method of any of clauses 1-20, wherein pixel locations within the buffer as addressed using x and y numbers.
22. The method of any of clauses 1-20, wherein pixel locations within the buffer as addressed using a single number that extends from 0 to M*N−1, where M and N are pixel width and pixel height of the buffer.
23. The method of any of clauses 1-20, wherein, the current bitstream representation includes a block vector for the conversion, wherein the block vector, denoted as (BVx,BVy) is equal to (x−x0,y−y0), where (x0, y0) correspond to an upper-left position of a coding tree unit of the current video block.
24. The method of any of clauses 1-20, wherein, the current bitstream representation includes a block vector for the conversion, wherein the block vector, denoted as (BVx,BVy) is equal to (x−x0+Tx,y−y0+Ty), where (x0, y0) correspond to an upper-left position of a coding tree unit of the current video block and wherein Tx and Ty are offset values.
25. The method of clause 24, wherein Tx and Ty are pre-defined offset values.
26. The method of any of clauses 1-20, wherein during the conversion, for a pixel at location (x0, y0) and having a block vector (BVx, BVy), a corresponding reference in the buffer is found at a reference location (x0+BVx, y0+BVy).
27. The method of clause 26, wherein in case that the reference location is outside the buffer, the reference in the buffer is determined by clipping at a boundary of the buffer.
28. The method of clause 26, wherein in case that the reference location is outside the buffer, the reference in the buffer is determined to have a predetermined value.
29. The method of any of clauses 1-20, wherein during the conversion, for a pixel at location (x0, y0) and having a block vector (BVx, BVy), a corresponding reference in the buffer is found at a reference location ((x0+BVx)mod M, (y0+BVy)mod N) where “mod” is modulo operation and M and N are integers representing x and y dimensions of the buffer.
30. A method of video processing, comprising: resetting, during a conversion between a video and a bitstream representation of the current video block, a buffer that stores reference samples for intra block copy coding at a video boundary; and performing the conversion using the reference samples stored in the buffer.
31. The method of clause 30, wherein the video boundary corresponds to a new picture or a new tile.
32. The method of clause 30, wherein the conversion is performed by updating, after the resetting, the buffer with reconstructed values of a Virtual Pipeline Data Unit (VPDU).
33. The method of clause 30, wherein the conversion is performed by updating, after the resetting, the buffer with reconstructed values of a coding tree unit.
34. The method of clause 30, wherein the resetting is performed at beginning of each coding tree unit row.
35. The method of clause 1, wherein the size of the buffer corresponds to L 64×64 previously decoded blocks., where L is an integer.
36. The method of any of clauses 1-35, wherein a vertical scan order is used for reading or storing samples in the buffer during the conversion.
37. A method of video processing, comprising: using, for a conversion between a current video block and a bitstream representation of the current video block, a buffer to store reference samples for the current video block using an intra-block copy coding mode, wherein a first bit-depth of the buffer is different than a second bit-depth of the coded data; and performing the conversion using the reference samples stored in the buffer.
38. The method of clause 37, wherein the first bit-depth is greater than the second bit-depth.
39. The method of any of clauses 37-38, wherein the first bit-depth is identical to a bit-depth of a reconstruction buffer used during the conversion.
40. The method of any of clauses 37-39, wherein the first bit-depth is signalled in the bitstream representation as a value or a difference value.
41. The method of any of clauses 37-40, wherein the conversion uses different bit-depths for chroma and luma components.
Additional embodiments and examples of clauses 37 to 41 are described in Item 7 in Section 4.
42. A method of video processing, comprising: performing a conversion between a current video block and a bitstream representation of the current video block using an intra-block copy mode in which a first precision used for prediction calculations during the conversion is lower than a second precision used for reconstruction calculations during the conversion.
43. The method of clause 42, wherein the prediction calculations include determining a prediction sample value from a reconstructed sample value using clip{{p+[1<<(b−1)]}>>b,0,(1<<bitdepth)−1}<<b, where p is the reconstructed sample value, b is a predefined bit-shifting value, and bitdepth is a prediction sample precision.
Additional embodiments and examples of clauses 42 to 43 are described in Items 28 to 31 and 34 in Section 4.
44. A method of video processing, comprising: performing a conversion between a current video block and a bitstream representation of the current video block using an intra-block copy mode in which a reference area of size nM×nM is used for a coding tree unit size M×M, where n and M are integers and wherein the current video block is positioned in the coding tree unit, and wherein the reference area is a nearest available n×n coding tree unit in a coding tree unit row corresponding to the current video block.
Additional embodiments and examples of clause 4 are described in Item 35 in Section 4.
45. A method of video processing, comprising: performing a conversion between a current video block and a bitstream representation of the current video block using an intra-block copy mode in which a reference area of size nM×nM is used for a coding tree unit size other than M×M, where n and M are integers and wherein the current video block is positioned in the coding tree unit, and wherein the reference area is a nearest available n×n-1 coding tree unit in a coding tree unit row corresponding to the current video block.
Additional embodiments and examples of clause 4 are described in Item 36 in Section 4.
46. The method of clause 44 or 45, wherein M=mW and N=H, where W and H are width and height of a coding tree unit (CTU) of the current video block, and m is a positive integer.
47. The method of clause 44 or 45, wherein M=W and N=nH, where W and H are width and height of a coding tree unit (CTU), and n is a positive integer.
48. The method of clause 44 or 45, wherein M=mW and N=nH, where W and H are width and height of a coding tree unit (CTU), m and n are positive integers.
49. The method of any of clauses 46-48, wherein n and m depend on a size of the CTU.
50. A method of video processing, comprising: determining, for a conversion between a current video block of a video and a bitstream representation of the current video block, validity of a block vector corresponding to the current video block of a component c of the video using a component X of the video, wherein the component X is different from a luma component of the video; and performing the conversion using the block vector upon determining that the block vector is valid for the current video block. Here, the block vector, denoted as (BVx,BVy) is equal to (x−x0,y−y0), where (x0, y0) correspond to an upper-left position of a coding tree unit of the current video block.
51. The method of clause 50, wherein the component c corresponds to the luma component of the video.
52. The method of clause 50, wherein the current video block is a chroma block and the video is in a 4:4:4 format.
53. The method of clause 50, wherein the video is in a 4:2:0 format, and wherein the current video block is a chroma block starting at position (x, y), and wherein the determining comprises determining the block vector to be invalid for a case in which isRec(c, ((x+BVx)>>5<<5)+64−(((y+BVy)>>5)&1)*32+(x %32), ((y+BVy)>>5<<5)+(y %32)) is true.
54. The method of clause 50, wherein the video is in a 4:2:0 format, and wherein the current video block is a chroma block starting at position (x, y), and wherein the determining comprises determining the block vector to be invalid for a case in which if isRec(c, x+BVx+ChromaSTU_size, y) is true.
55. A method of video processing, comprising: determining, selectively for a conversion between a current video block of a current virtual pipeline data unit (VPDU) of a video region and a bitstream representation of the current video block, to use K1 previously processed VPDUs from a first row of the video region and K2 previously processed VPDUs from a second row of the video region; and performing the conversion, wherein the conversion excludes using remaining of the current VPDU.
56. The method of clause 55, wherein K1=1 and K2=2.
57. The method of any of clauses 55-56, wherein the current video block is selectively processed based on a dimension of the video region or a dimension of the current VPDU.
58. A method of video processing, comprising: performing a validity check of a block vector for a conversion between a current video block and a bitstream representation of the current video block, wherein the block vector is used for intra block copy mode; and using a result of the validity check to selectively use the block vector during the conversion.
59. The method of clause 58, wherein an intra block copy (IBC) buffer is used during the conversion, wherein a width and a height of the IBC buffer as Wbuf and Hbuf an dimensions of the current video block are W×H and wherein the block vector is represented as (BVx, BVy), and wherein the current video block is in a current picture having dimensions Wpic and Hpic and a coding tree unit having Wctu and Hctu as width and height, and wherein the validity check uses a pre-determined rule.
60. The method of any of clauses 58-59, wherein the current video block is a luma block, a chroma block, a coding unit CU, a transform unit TU, a 4×4 block, a 2×2 block, or a subblock of a parent block starting from pixel coordinates (X, Y).
61. The method of any of clauses 58-60, wherein the validity check considers the block vector that falls outside a boundary of the current picture as valid.
62. The method of any of clauses 58-60, wherein the validity check considers the block vector that falls outside a boundary of the coding tree unit as valid.
Items 23-30 in the previous section provide additional examples and variations of the above clauses 58-62.
63. The method of any of clauses 1-62, wherein the conversion includes generating the bitstream representation from the current video block.
64. The method of any of clauses 1-62, wherein the conversion includes generating pixel values of the current video block from the bitstream representation.
65. A video encoder apparatus comprising a processor configured to implement a method recited in any one or more of clauses 1-62.
66. A video decoder apparatus comprising a processor configured to implement a method recited in any one or more of clauses 1-62.
67. A computer readable medium having code stored thereon, the code embodying processor-executable instructions for implementing a method recited in any of or more of clauses 1-62.
The bitstream representation corresponding to a current video block need not be a contiguous set of bits and may be distributed across headers, parameter sets, and network abstraction layer (NAL) packets.
In Section A, we present another example embodiment in which the current version of the VVC standard may be modified for implementing some of the embodiments described in the present disclosure.
This section analyzes several issues in the current IBC reference buffer design and presents a different design to address the issues. An independent IBC reference buffer is proposed instead of mixing with decoding memory. Compared with the current anchor, the proposed scheme shows −0.99%/−0.71%/−0.79% AI/RA/LD-B luma BD-rate for class F and −2.57%/−1.81%/−1.36% for 4:2:0 TGM, with 6.7% memory reduction; or −1.31%/−1.01%/−0.81% for class F and −3.23%/−2.33%/−1.71% for 4:2:0 TGM with 6.7% memory increase.
Intra block copy, i.e., IBC (or current picture referencing, i.e., CPR previously) coding mode, is adopted. It is realized that IBC reference samples should be stored in on-chip memory and thus a limited reference area of one CTU is defined. To restrict the extra on-chip memory for the buffer, the current design reuses the 64×64 memory for decoding the current VPDU so that only 3 additional 64×64 blocks' memory is needed to support IBC. When CTU size is 128×128, currently the reference area is shown in
In the current draft (VVC draft 4), the area is defined as
Thus, the total reference size is a CTU.
The current design assumes to reuse the 64×64 memory for decoding the current VPDU and the IBC reference is aligned to VPDU memory reuse accordingly. Such a design bundles VPDU decoding memory with the IBC buffer. There might be several issues:
To address issues listed in the above sub-section, we propose to have a dedicated IBC buffer, which is not mixed with decoding memory.
For 128×128 CTU, the buffer is defined as 128×128 with 8-bit samples, when a CU (x, y) with size w×h has been decoded, its reconstruction before loop-filtering is converted to 8-bit and written to the w×h block area starting from position (x %128, y %128). Here the modulo operator % always returns a positive number, i.e., for x<0, x % L−(−x % L), e.g., −3%128=125.
Assume that a pixel (x,y) is coded in IBC mode with BV=(BVx,BVy), it is prediction sample in the IBC reference buffer locates at ((x+BVx) %128, (y+BVy) %128) and the pixel value will be converted to 10-bit before prediction.
When the buffer is considered as (W, H), after decoding a CTU or CU starting from (x, y), the reconstructed pixels before loop-filtering will be stored in the buffer starting from (x % W, y % H). Thus, after decoding a CTU, the corresponding IBC reference buffer will be updated accordingly. Such setting might happen when CTU size is not 128×128. For example, for 64×64 CTU, with the current buffer size, it can be considered as a 256×64 buffer. For 64×64 CTU,
In such a design, because the IBC buffer is different from the VPDU decoding memory, all the IBC reference buffer can be used as reference.
When the bit-depth of the IBC buffer is 8-bit, compared with the current design that needs 3 additional 10-bit 64×64 buffer, the on-chip memory increase is (8*4)/(10*3)−100%=6.7%.
If we further reduce the bit-depth. The memory requirement can be further reduced. For example, for 7-bit buffer, the on-chip memory saving is 100%−(7*4)/(10*3)=6.7%.
With the design, the only bitstream conformance constraint is that the reference block shall be within the reconstructed area in the current CTU row of the current Tile.
When initialization to 512 is allowed at the beginning of each CTU row, all bitstream conformance constraints can be removed.
In some embodiments, the disclosed methods can be implemented using VTM-4.0 software.
For a 10-bit buffer implementation and common test conditions (CTC), the decoder is fully compatible to the current VTM4.0 encoder, which means that the proposed decoder can exactly decode the VTM-4.0 CTC bitstreams.
For a 7-bit buffer implementation, the results shown in Table I.
For an 8-bit buffer implementation, the results shown in Table II.
The system 1700 may include a coding component 1704 that may implement the various coding or encoding methods described in the present disclosure. The coding component 1704 may reduce the average bitrate of video from the input 1702 to the output of the coding component 1704 to produce a coded representation of the video. The coding techniques are therefore sometimes called video compression or video transcoding techniques. The output of the coding component 1704 may be either stored, or transmitted via a communication connected, as represented by the component 1706. The stored or communicated bitstream (or coded) representation of the video received at the input 1702 may be used by the component 1708 for generating pixel values or displayable video that is sent to a display interface 1710. The process of generating user-viewable video from the bitstream representation is sometimes called video decompression. Furthermore, while certain video processing operations are referred to as “coding” operations or tools, it will be appreciated that the coding tools or operations are used at an encoder and corresponding decoding tools or operations that reverse the results of the coding will be performed by a decoder.
Examples of a peripheral bus interface or a display interface may include universal serial bus (USB) or high definition multimedia interface (HDMI) or DisplayPort, and so on. Examples of storage interfaces include serial advanced technology attachment (SATA), peripheral component interface (PCI), integrated drive electronics (IDE) interface, and the like. The embodiments described in the present disclosure may be embodied in various electronic devices such as mobile phones, laptops, smartphones or other devices that are capable of performing digital data processing and/or video display.
Some embodiments of the present disclosure are now presented in clause-based format.
L1. A visual media processing method, comprising:
determining, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the current video block, a block vector (BVx,BVy), wherein validity of the block vector (BVx, BVy) is independent of (1) a location (P, Q) of a sample block and/or (2) whether a sample at the location (P,Q) is reconstructed, and/or (3) a location of the current video block, wherein, the block vector (BVx, BVy) represents a pixel displacement between the current video block and the sample block; and
performing, using the block vector, the conversion in an intra block copy mode which is based on a reconstructed block located in same video region with the current video block comprising reference samples used for deriving a prediction block of the current video block, wherein, during the conversion, a prediction sample with a location (A, B) from reference samples in a buffer is determined at least according to a size of the buffer and/or the block vector (BVx, BVy).
L2. A visual media processing method, comprising:
determining, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data, whether a block vector (BVx, BVy) corresponding to the current video block is valid according to a rule, wherein the block vector (BVx, BVy) represents a pixel displacement between the current video block and a sample block; and
performing, using the block vector, the conversion based on a reference region from the current picture comprising reference samples used for deriving a prediction block of the current video block, wherein the rule specifies that the block vector (BVx, BVy) is valid in case that (1) one or more samples from the sample block are outside the current picture and/or (2) one or more samples from the sample block are outside at least one coding tree unit (CTU) associated with the current video block, and/or (3) one or more samples from the sample block fail to be reconstructed.
L3. The method of clause L2, wherein, upon identifying that the block vector (BVx, BVy) is valid, a prediction sample with a location (A, B) from reference samples in a buffer is determined at least according to a size of the buffer and/or the block vector (BVx, BVy).
L4. The method of any one or more of clauses L1 or L3, wherein the reference samples in the buffer corresponds to reconstructed samples of a region of the current picture.
L5. The method of clause L4, wherein the region includes a coding tree unit (CTU) row associated with the current video block.
L6. The method of any one or more of clauses L1-L5, wherein the block vector (BVx, BVy) is determined to be valid regardless of whether the location (P, Q) computed according to the block vector (BVx, BVy) and the upper-left position (x, y) of the current video block is outside a boundary of a picture.
L7. The method of clause L6, wherein the block vector (BVx, BVy) is valid regardless of whether x+BVx<0 or x+BVx>0.
L8. The method of clause L6, wherein the block vector (BVx, BVy) is valid regardless of whether x+W+BVx>Wpic or x+W+BVx<Wpic, where W denotes a width of the current video block and Wpic denotes a width of the picture.
L9. The method of clause L6, wherein the block vector (BVx, BVy) is valid regardless of whether y+BVy<0 or y+BVy>0.
L10. The method of clause L6, wherein the block vector (BVx, BVy) is valid regardless of whether x+H+BVx >Hpic or x+H+BVx<Hpic, where H denotes a height of the current video block and Hpic denotes a height of the picture.
L11. The method of any one or more of clauses L1-L5, wherein the block vector (BVx, BVy) is valid regardless of whether the location (P, Q) computed according to the block vector (BVx, BVy) and the upper-left position (x, y) of the current video block is outside a coding tree unit including the current video block.
L12. The method of clause L11, wherein the block vector (BVx, BVy) is valid regardless of whether y+BVy<floor(y/Hctu)*Hctu or y+BVy>floor(y/Hctu)*Hctu, where Hctu denotes a height of the coding tree unit and floor(a) is the largest integer no greater than a.
L13. The method of clause L11, wherein the block vector (BVx, BVy) is valid regardless of whether y+H+BVy<floor(y/Hctu)*Hctu or y+H+BVy>floor(y/Hctu)*Hctu, where H denotes a height of the current video block, Hctu denotes a height of the coding tree unit, and floor(a) is the largest integer no greater than a.
L14. The method of any one or more of clauses L1-L5, wherein the block vector (BVx, BVy) is valid regardless of whether the location (P, Q) computed according to the block vector (BVx, BVy) and the upper-left position (x, y) of the current video block is outside a coding tree unit including the current video block and (n−1) coding tree units along a left direction.
L15. The method of clause L14, wherein the block vector (BVx, BVy) is valid regardless of whether x+BVx<floor(x/Wctu)*Wctu−(n−1)*Wctu or x+BVx>floor(X/Wctu)*Wctu−(n−1)*Wctu, where Wctu denotes a weight of the coding tree unit and floor(a) is the largest integer no greater than a.
L16. The method of clause L14, wherein the block vector (BVx, BVy) is valid regardless of whether x+W+BVx>floor(X/Wctu)*Wctu+Wctu or x+W+BVx<floor(X/Wctu)*Wctu+Wctu, where W denotes a width of the current video block, Wctu denotes a weight of the coding tree unit, and floor(a) is the largest integer no greater than a.
L17. The method of any one or more of clauses L1-L5, wherein the block vector (BVx, BVy) is valid regardless of whether the location (P, Q) computed according to the block vector (BVx, BVy) and the upper-left position (x, y) of the current video block is outside a current CTU row including a current coding tree unit including the current video block.
L18. The method of clause L17, wherein the block vector (BVx, BVy) is valid regardless of whether Y+BVy<floor(Y/Hctu)*Hctu or Y+H+BVy>=floor(Y/Hctu)*Hctu+Hctu, wherein, Wctu and Hctu denote a width and height of a CTU respectively and floor(a) is the largest integer no greater than a.
L19. The method of any one or more of clauses L1-L5, wherein the block vector (BVx, BVy) is determined to be valid regardless of whether a sample fails to be reconstructed.
L20. The method of clause L19, wherein the block vector (BVx, BVy) is valid regardless of whether isRec(x+BVx, y+BVy) is false, where isRec(x,y) is true if pixel (x,y) is reconstructed by an intra block copy mode.
L21. The method of clause L19, wherein the block vector (BVx, BVy) is valid regardless of whether isRec(x+BVx+W−1, y+BVy) is false, where isRec(x,y) is true if pixel (x, y) is reconstructed by an intra block copy mode and W denotes a width of the current video block.
L22. The method of clause L19, wherein the block vector (BVx, BVy) is valid regardless of whether isRec(x+BVx, y+BVy+H−1) is false, where isRec(x,y) is true if pixel (x, y) is reconstructed by an intra block copy mode and H denotes a height of the current video block.
L23. The method of clause L19, wherein the block vector (BVx, BVy) is valid regardless of whether isRec(x+BVx+W-1, y+BVy+H-1) is false, where isRec(x, y) is true if pixel (x, y) is reconstructed by an intra block copy mode, W denotes a width of the current video block, and H denotes a height of the current video block.
L24. The method of any one or more of clauses L1-L5 wherein the block vector (BVx, BVy) is determined to be valid regardless of whether the current video block is included in a first coding tree unit of a coding tree unit row.
L25. The method of any one or more of clauses L1-L5, wherein the block vector (BVx, BVy) is determined to be valid when all the following conditions are satisfied: (i) x+BVx>=0, (ii) y+BVy>=floor(y/Hctu), and (iii) isRec(x+BVx+W−1, y+BVy+H−1) is true, where isRec(x, y) is true if sample (x, y) is reconstructed by an intra block copy mode, W denotes a width of the current video block, H denotes a height of the current video block, where floor(a) is the largest integer no greater than a.
L26. The method of clause L25, wherein the block vector is a located in a first CTU in a CTU row.
L27. The method of clause L3, wherein the prediction sample with the location (A, B) is determined according to the size of the buffer, the block vector (BVx, BVy), and the upper-left position (x,y).
L28. The method of clause L27, wherein the prediction sample with the location (A, B) comprises a predication sample with a location computed according to ((X+BVx) % Wbuf, (Y+BVy) % Hbuf), wherein Wbuf and Hbuf denote a width of the buffer and a height of the buffer respectively.
L29. The method of any one or more of clauses L1-L28, wherein the conversion is performed in an intra block copy mode.
M1. A visual media processing method, comprising:
performing a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data,
wherein, the conversion is based on a reference region from the current picture comprising reference samples used for deriving a prediction block of the current video block, and
wherein a virtual buffer of a defined size is used for tracking availability of the reference samples for deriving the prediction block.
M2. The method of clause M1, wherein the virtual buffer is maintained using a virtual pipeline data unit (VPDU), and wherein a size of the virtual buffer is m*WVPDU×n*HVPDU, where WVPDU and HVPDU denote a width and a height of the VPDU.
M3. The method of clause M2, wherein m=4 and n=2.
M4. The method of clause M2, wherein m and/or n are based at least in part on a resolution of a picture associated with the current video block or a size of a coding tree unit including the current video block.
M5. The method of clause M2, wherein m and/or are predefined quantities.
M6. The method of clause M2, wherein m and/or are signalled as fields in the bitstream representation.
M7. The method of clause M1, wherein a sample in the current video block is mapped to (x % (m*WVPDU), y % (n*HVPDU)) in the virtual buffer, where the sample in the current video block is located at (x, y) relative to a upper-left corner of a picture; “x % y” is defined as y=x−y*floor(x/y), where floor(a) is the largest integer no greater than a, and WVPDU and HVPDU denote a width and a height of the VPDU.
M8. The method of clause M1, further comprising:
using an array for tracking availabilities of samples stored in the virtual buffer.
M9. The method of clause M8, wherein the array includes a flag to indicate if one or more samples stored in the buffer are used for prediction in an intra block copy mode.
M10. The method of clause M8, wherein the array corresponds to one or more VPDUs of size 3×2.
M11. The method of clause M8, wherein the array corresponds to one or more VPDUs of size 4×2.
M12. The method of clause M1, wherein a subset of samples stored in the virtual buffer are flagged as unavailable for prediction.
M13. The method of clause M12, wherein, the subset of samples flagged as unavailable for prediction are based on a position of a most-recently processed VPDU.
M14. The method of clause M13, wherein the samples are flagged as unavailable at a beginning of processing a VPDU.
M15. The method of clause M14, wherein, if yPrevVPDU % (n*HVPDU) is equal to 0, then the subset of samples located at positions (x, y) are flagged as unavailable, wherein x lies in a first predetermined range and y lies in a second predetermined range, where (xPrevVPDU, yPrevVPDU) denotes an upper-left corner of a coding tree unit of a most-recently processed VPDU, and WVPDU and HVPDU denote a width and a height of the VPDU.
M16. The method of clause M15, wherein the first range is expressed as [xPrevVPDU−2WVPDU+2mWVPDU) % mWVPDU, ((xPrevVPDU−2*WVPDU+2*m*WVPDU) % (m*WVPDU)−1+WVPDU] and the second range is expressed as [yPrevVPDU % (n*HVPDU), (yPrevVPDU % (n*HVPDU))−1+HVPDU].
M17. The method of clause M15, wherein the first range is expressed as [xPrevVPDU−2*WVPDU+2*m*WVPDU) % mWVPDU, ((xPrevVPDU−2*WVPDU+2*m*WVPDU) % (m*WVPDU)−1+WVPDU] and the second range is expressed as [yPrevVPDU % (n*HVPDU), (yPrevVPDU % (n*HVPDU))−1+HVPDU].
M18. The method of clause M14, wherein, if yPrevVPDU % (n*HVPDU) is not equal to 0, then the subset of samples located at positions (x, y) are flagged as unavailable, wherein x lies in a first predetermined range and y lies in a second predetermined range, where (xPrevVPDU, yPrevVPDU) denotes an upper-left corner of a coding tree unit of a most-recently processed VPDU, and WVPDU and HVPDU denote a width and a height of the VPDU.
M19. The method of clause M18, wherein the first range is expressed as [xPrevVPDU−WVPDU+2*m*WVPDU) % (m*WVPDU), ((xPrevVPDU−WVPDU+2*m*WVPDU) % (m*WVPDU)−1+WVPDU] and the second range is expressed as [yPrevVPDU % (n*HVPDU), (yPrevVPDU % (n*HVPDU))−1+HVPDU].
M20. The method of clause M18, wherein the first range is expressed as [xPrevVPDU−WVPDU+2*m*WVPDU) % mWVPDU, ((xPrevVPDU−WVPDU+2*m*WVPDU) % (m*WVPDU))−1+WVPDU] and the second range is expressed as [yPrevVPDU % (n*HVPDU), (yPrevVPDU % (n*HVPDU))−1+HVPDU].
M21. The method of clause M12, wherein, when the coding tree includes VPDUs, the subset of samples flagged as unavailable for prediction are based on a position of a most-recently processed coding tree unit.
M22. The method of clause M21, wherein the samples are flagged as unavailable at a beginning of processing a coding tree unit.
M23. The method of any one or more of clauses M1-M22, further comprising:
determining validity of a block vector corresponding to the current video block based on an upper-left position of the current video block, a bottom-left position of the current video block, and a bottom-right position of the current video block, wherein the determining excludes use of an upper-right position of the current video block.
M24. The method of any one or more of clauses M 1-M23, wherein the conversion is performed in an intra block copy mode.
N1. A visual media processing method, comprising:
maintaining, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data, a buffer comprising reference samples from the current picture for a derivation of a prediction block of the current video block,
wherein one or more reference samples in the buffer that are marked unavailable for the derivation have values outside of a pixel value range.
N2. The method of clause N1, wherein the pixel value range is expressed as [0, 1<<(bit_depth)−1], where bit_depth is a positive integer.
N3. The method of clause N2, wherein bit_depth is a precision used for processing the sample.
N4. The method of clause N1, wherein the method further comprises:
initializing a set of samples in the buffer to a predetermined value indicative of unavailability of the set of samples.
N5. The method of clause N4, wherein the predetermined value is −1.
N6. The method of any one or more of clauses N4-N5, wherein locations of the set of samples and/or whether to initialize the set of the samples to the predetermined value is/are based on one or more of: a position of the current video block, a size of the current video block, a size of a VPDU including the current video block, and/or a size of a coding tree unit including the current video block.
N7. The method of clause N6, wherein, if (xCb % vSize) is equal to 0 and (yCb % vSize) is equal to 0, the set of samples are marked as unavailable, where xCb, yCb denote a position of the current video block relative to the sample and vSize=min(ctbSize, 64), where ctbSize denotes a width or a height of the coding tree unit.
N8. The method of clause N1, wherein, if a size of the current video block is less than min(ctbSize, 64), the set of samples in the buffer are marked unavailable, where ctbSize denotes a width or a height of the coding tree unit.
N9. The method of clause N8, wherein locations of the plurality of samples are related to a size of a VPDU.
N10. The method of clause N8, wherein locations of the set of samples are related to a size of the coding tree unit including the current video block.
N11. The method of clause N4, wherein the set of samples in the buffer have with positions expressed as (x % wIbcBuf, y % hIbcBuf), where x=xV, . . . , xV+ctbSize−1 and y=yV, . . . , yV+ctbSize−1, and xV, yV denote the upper-left position of a VPDU relative to an upper-left position of a picture, where ctbSize denotes a size of the coding tree unit including the current video block, and wIbcBuf and hIbcBuf denote a buffer width and a buffer height.
N12. The method of clause N11, wherein the set of samples in the buffer are initialized to −1.
N13. The method of clause N4, wherein the set of samples are initialized at a beginning of decoding a video unit.
N14. The method of any one or more of clauses N1-N13, wherein the conversion is performed in an intra block copy mode.
O1. A visual media processing method, comprising:
performing a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data using a buffer comprising reference samples from the current picture for derivation of a prediction block of the current video block,
wherein the conversion is based according to rule which specifies that, for the bitstream representation to conform the rule, a reference sample in the buffer is to satisfy a bitstream conformance constraint.
O2. The method of clause O1, wherein the bitstream conformance constraint is based on at least one of (1) a value of the reference sample in the buffer and/or (2) an availability information of the sample in the buffer.
O3. The method of any one or more of clauses O1-O2, wherein the bitstream conformance constraint specifies that the bitstream representation is non-conforming, if the sample in the buffer has a value outside of a pixel range.
O4. The method of clause O3, wherein the range is [K0, K1], wherein K0 is set to 0 and K1 is set to (1<<BitDepth−1), where BitDepth represents a precision of a prediction sample.
O5. The method of any one or more of clauses O1-O2, wherein the bitstream conformance constraint specifies that the bitstream representation is non-conforming, if the availability information of the sample in the buffer indicates that the sample is unavailable for the current video block.
O6. The method of any one or more of clauses O1-O2, wherein the sample is a luma sample, and wherein the bitstream conformance constraint specifies that the bitstream representation is non-conforming, if the availability information of the sample in the buffer indicates that the sample is unavailable for the current video block and a single tree partitioning is used for the current video block.
O7. The method of clause any one or more of clauses O1-O6, further comprising:
marking the availability information of the sample according to the value of the sample in the buffer.
O8. The method of clause O7, wherein, if the value of the sample lies in an interval denoted as [K0, K1], the availability information of the sample is marked as available.
O9. The method of clause O8, wherein K0 is set to 0 and K1 is set to (1<<BitDepth−1), where BitDepth is represents a precision of a prediction sample.
O10. The method of any one or more of clauses O1-O8, wherein the bitstream conformance constraint is further based on a partitioning type and a tree type of a coding unit associated with the current video block.
O11. The method of clause O10, wherein, if the partitioning type is dual tree and the tree type is single tree, then the bitstream conformance constraint specifies checking if all color components of the sample are marked as unavailable.
O12. The method of clause O10, wherein if the partitioning type is dual tree and the tree type is dual tree, then the bitstream conformance constraint specifies excludes checking if a chroma component of the sample is marked as unavailable.
O13. The method of any one or more of clauses O1-O12, wherein the conversion is performed in an intra block copy mode.
O14. The method of any of clauses L1-O13, wherein the conversion includes generating the bitstream representation from the current video block.
O15. The method of any of clauses L1-O13, wherein the conversion includes generating pixel values of the current video block from the bitstream representation.
P1. A video encoder apparatus comprising a processor configured to implement a method recited in any one or more of clauses L1-O15.
P2. A video decoder apparatus comprising a processor configured to implement a method recited in any one or more of clauses L1-O15.
P3. A computer readable medium having code stored thereon, the code embodying processor-executable instructions for implementing a method recited in any of or more of clauses L1-O15.
In the present disclosure, the term “video processing” may refer to video encoding, video decoding, video compression or video decompression. For example, video compression algorithms may be applied during conversion from pixel representation of a video to a corresponding bitstream representation or vice versa. The bitstream representation of a current video block may, for example, correspond to bits that are either co-located or spread in different places within the bitstream, as is defined by the syntax. For example, a macroblock may be encoded in terms of transformed and coded error residual values and also using bits in headers and other fields in the bitstream.
From the foregoing, it will be appreciated that specific embodiments of the present disclosure have been described herein for purposes of illustration, but that various modifications may be made without deviating from the scope of these embodiments. Accordingly, the present disclosure is not limited except as by the appended claims.
Embodiments of the subject matter and the functional operations described in the present disclosure 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. Embodiments 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., a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC).
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., erasable programmable read-only memory (EPROM), electronically erasable programmable read-only memory (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 use of “or” is intended to include “and/or”, unless the context clearly indicates otherwise.
While the present disclosure 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 the present disclosure 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 the present disclosure should not be understood as requiring such separation in all embodiments.
Only a few embodiments and examples are described and other embodiments, enhancements and variations can be made based on what is described and illustrated in the present disclosure.
| Number | Date | Country | Kind |
|---|---|---|---|
| PCT/CN2019/094957 | Jul 2019 | WO | international |
| PCT/CN2019/095297 | Jul 2019 | WO | international |
This application is a continuation application of U.S. application Ser. No. 17/569,390 filed on Jan. 5, 2022, which is a continuation of International Application No. PCT/CN2020/099702 filed on Jul. 1, 2020, which claims the priority to and benefits of International Patent Application No. PCT/CN2019/094957 filed on Jul. 6, 2019 and International Patent Application No. PCT/CN2019/095297 filed on Jul. 9, 2019. All the aforementioned patent applications are hereby incorporated by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 7916728 | Mimms | Mar 2011 | B1 |
| 8295361 | Tseng et al. | Oct 2012 | B2 |
| 8947449 | Dodd | Feb 2015 | B1 |
| 9426463 | Seregin et al. | Aug 2016 | B2 |
| 9491460 | Seregin et al. | Nov 2016 | B2 |
| 9591325 | Li et al. | Mar 2017 | B2 |
| 9860559 | Zhang et al. | Jan 2018 | B2 |
| 9877043 | He et al. | Jan 2018 | B2 |
| 9918105 | Pang et al. | Mar 2018 | B2 |
| 10148981 | Zhu et al. | Dec 2018 | B2 |
| 10178403 | Seregin et al. | Jan 2019 | B2 |
| 10200706 | Hellman | Feb 2019 | B2 |
| 10264290 | Xu et al. | Apr 2019 | B2 |
| 10284874 | He et al. | May 2019 | B2 |
| 10306240 | Xiu et al. | May 2019 | B2 |
| 10368091 | Li et al. | Jul 2019 | B2 |
| 10412387 | Pang et al. | Sep 2019 | B2 |
| 10440378 | Xu et al. | Oct 2019 | B1 |
| 10469863 | Zhu et al. | Nov 2019 | B2 |
| 10516882 | He et al. | Dec 2019 | B2 |
| 10728552 | Tsukuba | Jan 2020 | B2 |
| 10567754 | Li et al. | Feb 2020 | B2 |
| 10582213 | Li et al. | Mar 2020 | B2 |
| 10841607 | Park et al. | Nov 2020 | B2 |
| 10873748 | Chen et al. | Dec 2020 | B2 |
| 11025945 | Park et al. | Jun 2021 | B2 |
| 11070816 | Xu et al. | Jul 2021 | B2 |
| 11184637 | Li et al. | Nov 2021 | B2 |
| 11228775 | Xu et al. | Jan 2022 | B2 |
| 11523107 | Xu | Dec 2022 | B2 |
| 11570753 | Xue | Jan 2023 | B2 |
| 11729414 | Park | Aug 2023 | B2 |
| 11876957 | Jang | Jan 2024 | B2 |
| 20040076237 | Kadono | Apr 2004 | A1 |
| 20040218816 | Hannuksela | Nov 2004 | A1 |
| 20050129115 | Jeon | Jun 2005 | A1 |
| 20050212970 | Joskin | Sep 2005 | A1 |
| 20060233237 | Lu | Oct 2006 | A1 |
| 20060244748 | Long | Nov 2006 | A1 |
| 20080025407 | Winger | Jan 2008 | A1 |
| 20080043845 | Nakaishi | Feb 2008 | A1 |
| 20080181300 | Hosaka | Jul 2008 | A1 |
| 20080219352 | Tokumitsu et al. | Sep 2008 | A1 |
| 20080260034 | Wang | Oct 2008 | A1 |
| 20100014584 | Feder et al. | Jan 2010 | A1 |
| 20100054329 | Bronstein | Mar 2010 | A1 |
| 20100228957 | Rabinovitch | Sep 2010 | A1 |
| 20110122950 | Ji | May 2011 | A1 |
| 20110217714 | Makrigiorgos | Sep 2011 | A1 |
| 20110249754 | Karczewicz et al. | Oct 2011 | A1 |
| 20120002716 | Antonellis et al. | Jan 2012 | A1 |
| 20120201308 | Prasad et al. | Aug 2012 | A1 |
| 20120236931 | Karczewicz et al. | Sep 2012 | A1 |
| 20130003864 | Sullivan | Jan 2013 | A1 |
| 20130246746 | Gainey, Jr. | Sep 2013 | A1 |
| 20130329784 | Chuang et al. | Dec 2013 | A1 |
| 20140072041 | Seregin et al. | Mar 2014 | A1 |
| 20140160139 | MacInnis et al. | Jun 2014 | A1 |
| 20140301465 | Kwon et al. | Oct 2014 | A1 |
| 20140314148 | Lainema | Oct 2014 | A1 |
| 20140348240 | Kim et al. | Nov 2014 | A1 |
| 20140376611 | Kim et al. | Dec 2014 | A1 |
| 20150063440 | Pang et al. | Mar 2015 | A1 |
| 20150131724 | Lin et al. | May 2015 | A1 |
| 20150176721 | Schoonover | Jun 2015 | A1 |
| 20150195559 | Chen et al. | Jul 2015 | A1 |
| 20150208084 | Zhu | Jul 2015 | A1 |
| 20150264348 | Zou | Sep 2015 | A1 |
| 20150264372 | Kolesnikov et al. | Sep 2015 | A1 |
| 20150264373 | Wang et al. | Sep 2015 | A1 |
| 20150264383 | Cohen et al. | Sep 2015 | A1 |
| 20150264386 | Pang et al. | Sep 2015 | A1 |
| 20150264396 | Zhang et al. | Sep 2015 | A1 |
| 20150271487 | Li et al. | Sep 2015 | A1 |
| 20150271517 | Pang | Sep 2015 | A1 |
| 20150296213 | Hellman | Oct 2015 | A1 |
| 20150334405 | Rosewarne et al. | Nov 2015 | A1 |
| 20150373357 | Pang | Dec 2015 | A1 |
| 20150373358 | Pang et al. | Dec 2015 | A1 |
| 20150373359 | He et al. | Dec 2015 | A1 |
| 20160100163 | Rapaka | Apr 2016 | A1 |
| 20160100189 | Pang et al. | Apr 2016 | A1 |
| 20160104457 | Wu et al. | Apr 2016 | A1 |
| 20160105682 | Rapaka | Apr 2016 | A1 |
| 20160219298 | Li | Jul 2016 | A1 |
| 20160227222 | Hu et al. | Aug 2016 | A1 |
| 20160227244 | Rosewarne | Aug 2016 | A1 |
| 20160241858 | Li et al. | Aug 2016 | A1 |
| 20160241868 | Li et al. | Aug 2016 | A1 |
| 20160241875 | Wu et al. | Aug 2016 | A1 |
| 20160323573 | Ikai | Nov 2016 | A1 |
| 20160330474 | Liu et al. | Nov 2016 | A1 |
| 20160337661 | Pang et al. | Nov 2016 | A1 |
| 20160360210 | Xiu | Dec 2016 | A1 |
| 20160360234 | Tourapis et al. | Dec 2016 | A1 |
| 20170054996 | Xu et al. | Feb 2017 | A1 |
| 20170070748 | Li | Mar 2017 | A1 |
| 20170076419 | Fries et al. | Mar 2017 | A1 |
| 20170094271 | Liu et al. | Mar 2017 | A1 |
| 20170094299 | Damudi | Mar 2017 | A1 |
| 20170094314 | Zhao et al. | Mar 2017 | A1 |
| 20170099490 | Seregin et al. | Apr 2017 | A1 |
| 20170099495 | Rapaka et al. | Apr 2017 | A1 |
| 20170134724 | Liu et al. | May 2017 | A1 |
| 20170142418 | Li | May 2017 | A1 |
| 20170188033 | Lin et al. | Jun 2017 | A1 |
| 20170223379 | Chuang et al. | Aug 2017 | A1 |
| 20170280159 | Xu et al. | Sep 2017 | A1 |
| 20170289566 | He et al. | Oct 2017 | A1 |
| 20170289572 | Ye | Oct 2017 | A1 |
| 20170295379 | Sun et al. | Oct 2017 | A1 |
| 20170302936 | Li et al. | Oct 2017 | A1 |
| 20170310961 | Liu | Oct 2017 | A1 |
| 20170372494 | Zhu et al. | Dec 2017 | A1 |
| 20170374369 | Chuang | Dec 2017 | A1 |
| 20180048909 | Liu | Feb 2018 | A1 |
| 20180101708 | Gao | Apr 2018 | A1 |
| 20180103260 | Chuang et al. | Apr 2018 | A1 |
| 20180115787 | Koo | Apr 2018 | A1 |
| 20180124411 | Nakagami | May 2018 | A1 |
| 20180152727 | Chuang et al. | May 2018 | A1 |
| 20180160122 | Xu | Jun 2018 | A1 |
| 20180184093 | Xu et al. | Jun 2018 | A1 |
| 20180205966 | Kang | Jul 2018 | A1 |
| 20180220130 | Zhang et al. | Aug 2018 | A1 |
| 20180255304 | Jeon | Sep 2018 | A1 |
| 20180302645 | Laroche et al. | Oct 2018 | A1 |
| 20180343471 | Jacobson | Nov 2018 | A1 |
| 20180376165 | Alshin et al. | Dec 2018 | A1 |
| 20190007705 | Zhao et al. | Jan 2019 | A1 |
| 20190031194 | Kim | Jan 2019 | A1 |
| 20190068992 | Tourapis et al. | Feb 2019 | A1 |
| 20190089975 | Liu | Mar 2019 | A1 |
| 20190191167 | Drugeon et al. | Jun 2019 | A1 |
| 20190200038 | He et al. | Jun 2019 | A1 |
| 20190208217 | Zhou et al. | Jul 2019 | A1 |
| 20190215532 | He | Jul 2019 | A1 |
| 20190238864 | Xiu et al. | Aug 2019 | A1 |
| 20190246143 | Zhang et al. | Aug 2019 | A1 |
| 20200007877 | Zhou | Jan 2020 | A1 |
| 20200036997 | Li | Jan 2020 | A1 |
| 20200037002 | Xu | Jan 2020 | A1 |
| 20200045329 | Hashimoto et al. | Feb 2020 | A1 |
| 20200077087 | He et al. | Mar 2020 | A1 |
| 20200084454 | Liu et al. | Mar 2020 | A1 |
| 20200092579 | Zhu et al. | Mar 2020 | A1 |
| 20200099953 | Xu et al. | Mar 2020 | A1 |
| 20200137401 | Kim et al. | Apr 2020 | A1 |
| 20200177900 | Xu | Jun 2020 | A1 |
| 20200177910 | Li et al. | Jun 2020 | A1 |
| 20200177911 | Aono | Jun 2020 | A1 |
| 20200204819 | Hsieh | Jun 2020 | A1 |
| 20200213608 | Chen et al. | Jul 2020 | A1 |
| 20200213610 | Kondo | Jul 2020 | A1 |
| 20200244991 | Li et al. | Jul 2020 | A1 |
| 20200260072 | Park | Aug 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 |
| 20210021811 | Xu et al. | Jan 2021 | A1 |
| 20210029373 | Park et al. | Jan 2021 | A1 |
| 20210120261 | Lim et al. | Apr 2021 | A1 |
| 20210136405 | Chen et al. | May 2021 | A1 |
| 20210152833 | Gao | May 2021 | A1 |
| 20210258598 | Hendry | Aug 2021 | A1 |
| 20210274201 | Xu et al. | Sep 2021 | A1 |
| 20210274202 | Xu et al. | Sep 2021 | A1 |
| 20210297674 | Xu et al. | Sep 2021 | A1 |
| 20210314560 | Lai | Oct 2021 | A1 |
| 20210321127 | Zhao | Oct 2021 | A1 |
| 20210352279 | Xu et al. | Nov 2021 | A1 |
| 20210360270 | Xu et al. | Nov 2021 | A1 |
| 20210368164 | Xu et al. | Nov 2021 | A1 |
| 20210368178 | Xu et al. | Nov 2021 | A1 |
| 20210385437 | Xu et al. | Dec 2021 | A1 |
| 20220132105 | Xu et al. | Apr 2022 | A1 |
| 20220150474 | Xu et al. | May 2022 | A1 |
| 20220150540 | Xu | May 2022 | A1 |
| 20220166993 | Xu et al. | May 2022 | A1 |
| 20220174310 | Xu et al. | Jun 2022 | A1 |
| 20230007273 | Gao | Jan 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 1589028 | Mar 2005 | CN |
| 1759610 | Apr 2006 | CN |
| 102017638 | Apr 2011 | CN |
| 102595118 | Jul 2012 | CN |
| 103026706 | Apr 2013 | CN |
| 105027567 | Nov 2015 | CN |
| 105393536 | Mar 2016 | CN |
| 105474645 | Apr 2016 | CN |
| 105532000 | Apr 2016 | CN |
| 105556967 | May 2016 | CN |
| 105659602 | Jun 2016 | CN |
| 105684409 | Jun 2016 | CN |
| 105765974 | Jul 2016 | CN |
| 105847795 | Aug 2016 | CN |
| 105847843 | Aug 2016 | CN |
| 105874791 | Aug 2016 | CN |
| 105874795 | Aug 2016 | CN |
| 105981382 | Sep 2016 | CN |
| 106105215 | Nov 2016 | CN |
| 106415607 | Feb 2017 | CN |
| 106416243 | Feb 2017 | CN |
| 106416250 | Feb 2017 | CN |
| 106464896 | Feb 2017 | CN |
| 106464904 | Feb 2017 | CN |
| 106464921 | Feb 2017 | CN |
| 106576171 | Apr 2017 | CN |
| 106576172 | Apr 2017 | CN |
| 106717004 | May 2017 | CN |
| 106797466 | May 2017 | CN |
| 106797475 | May 2017 | CN |
| 106797476 | May 2017 | CN |
| 106961609 | Jul 2017 | CN |
| 107005717 | Aug 2017 | CN |
| 107018418 | Aug 2017 | CN |
| 107205149 | Sep 2017 | CN |
| 107211155 | Sep 2017 | CN |
| 107409226 | Nov 2017 | CN |
| 107431819 | Dec 2017 | CN |
| 107615762 | Jan 2018 | CN |
| 107615763 | Jan 2018 | CN |
| 107615765 | Jan 2018 | CN |
| 107646195 | Jan 2018 | CN |
| 107683606 | Feb 2018 | CN |
| 107846597 | Mar 2018 | CN |
| 107852490 | Mar 2018 | CN |
| 107852505 | Mar 2018 | CN |
| 107925769 | Apr 2018 | CN |
| 107925773 | Apr 2018 | CN |
| 101198063 | Jun 2018 | CN |
| 108141605 | Jun 2018 | CN |
| 108141619 | Jun 2018 | CN |
| 108632609 | Oct 2018 | CN |
| 109076210 | Dec 2018 | CN |
| 109691099 | Apr 2019 | CN |
| 109792487 | May 2019 | CN |
| 110495177 | Nov 2019 | CN |
| 110945871 | Mar 2020 | CN |
| 3253059 | Dec 2017 | EP |
| 2882190 | Nov 2018 | EP |
| 2533905 | Jul 2016 | GB |
| 201847033775 | Oct 2018 | IN |
| 4360093 | Nov 2009 | JP |
| 2016534660 | Nov 2016 | JP |
| 2016539542 | Dec 2016 | JP |
| 2017130938 | Jul 2017 | JP |
| 2017519460 | Jul 2017 | JP |
| 2017535148 | Nov 2017 | JP |
| 2017535150 | Nov 2017 | JP |
| 6324590 | May 2018 | JP |
| 2018521539 | Aug 2018 | JP |
| 2020017970 | Jan 2020 | JP |
| 20160072181 | Jun 2016 | KR |
| 20170020928 | Feb 2017 | KR |
| 20170063895 | Jun 2017 | KR |
| 20190137806 | Dec 2019 | KR |
| 2587420 | Jun 2016 | RU |
| 2654129 | May 2018 | RU |
| 2679566 | Feb 2019 | RU |
| 2004008772 | Jan 2004 | WO |
| 2008047316 | Apr 2008 | WO |
| 2008067734 | Jun 2008 | WO |
| 2011127964 | Oct 2011 | WO |
| 2012167713 | Dec 2012 | WO |
| 2013128010 | Sep 2013 | WO |
| 2015108793 | Jul 2015 | WO |
| 2015142854 | Sep 2015 | WO |
| 2016054985 | Apr 2016 | WO |
| 2016057208 | Apr 2016 | WO |
| 2016057701 | Apr 2016 | WO |
| 2016127889 | Aug 2016 | WO |
| 2016138854 | Sep 2016 | WO |
| 2016150343 | Sep 2016 | WO |
| 2016192594 | Dec 2016 | WO |
| 2016192677 | Dec 2016 | WO |
| 2016200043 | Dec 2016 | WO |
| 2016200984 | Dec 2016 | WO |
| 2017041692 | Mar 2017 | WO |
| 2017058633 | Apr 2017 | WO |
| 2018190207 | Oct 2018 | WO |
| 2019006300 | Jan 2019 | WO |
| 2019009590 | Jan 2019 | WO |
| 2019017694 | Jan 2019 | WO |
| 2019022843 | Jan 2019 | WO |
| 2019131778 | Jul 2019 | WO |
| 2020156540 | Aug 2020 | WO |
| 2020228744 | Nov 2020 | WO |
| 2020259677 | Dec 2020 | WO |
| Entry |
|---|
| Document: JVET-J0042-v3, Zuo, X., 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, 5 pages. |
| Document: JCTVC-W1005-v4, Joshi, R., “High Efficiency Video Coding (HEVC) Screen Content Coding: Draft 6,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 23rd Meeting: San Diego, USA, Feb. 19-26, 2016, 692 pages. |
| Huang, S., et al., “Fast intra prediction for HEVC screen content,” Journal of Optoelectronics—Laser vol. 29 No. 6, Jun. 2018, 6 pages. |
| Non-Final Office Action from U.S. Appl. No. 17/571,748 dated Sep. 14, 2023. |
| Non-Final Office Action from U.S. Appl. No. 17/386,403 dated Sep. 22, 2023. |
| Non-Final Office Action from U.S. Appl. No. 17/386,430 dated Sep. 7, 2023. |
| Non-Final Office Action from U.S. Appl. No. 17/386,519 dated Oct. 5, 2023. |
| Non-Final Office Action from U.S. Appl. No. 17/461,150, filed Sep. 15, 2023. |
| Document: JVET-M0474-v3, Van, L., et al., “CE8.1.3: Extended CPR reference with 1 buffer line,” 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, 2018, 12 pages. |
| Non-Final Office Action dated Mar. 10, 2023, 44 pages, U.S. Appl. No. 17/978,263, filed Nov. 1, 2022. |
| Document: JVET-M0407-v1, Xu, X., et al., “CE8: CPR reference memory reuse without increasing memory requirement (CE8.1.2a and CE8.1.2d),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 13th Meeting: Marrakesh, MA, Jan. 9-18, 2019, 9 pages. |
| Document: JVET-M0890-v2, Chen, H., et al., “CE9-related: BDOF buffer reduction and enabling VPDU based application,” 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, 3 pages. |
| Document: JVET-M0888-v4, Tsai, C., et al., “CE1-related: Picture boundary CU split satisfying the VPDU constraint,” 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, 7 pages. |
| “Series H: Audiovisual and Multimedia Systems Infrastructure of audiovisual services—Coding of moving video High efficiency video coding,” Recommendation ITU-T H.265, Apr. 2013, 317 pages. |
| Non-Final Office Action dated Aug. 4, 2023, 53 pages, U.S. Appl. No. 17/896,761, filed Aug. 26, 2022. |
| Foreign Communication From a Related Counterpart Application, Australian Application No. 2020214083, Australian Office Action dated May 19, 2023, 3 pages. |
| Extended European Search Report from European Patent Application No. 20836430.7 dated Jul. 22, 2022 (12 pages). |
| Extended European Search Report from European Patent Application No. 20837885.1 dated Jul. 7, 2022 (15 pages). |
| Extended European Search Report from European Patent Application No. 20837744.0 dated Jul. 5, 2022 (12 pages). |
| Extended European Search Report from European Patent Application No. 20747609.4 dated May 11, 2022 (10 pages). |
| Extended European Search Report from European Patent Application No. 20748900.6 dated May 11, 2022 (10 pages). |
| Extended European Search Report from European Patent Application No. 20765739.6 dated May 19, 2022 (7 pages). |
| Non Final Office Action from U.S. Appl. No. 17/570,723 dated Mar. 25, 2022. |
| Non Final Office Action from U.S. Appl. No. 17/570,753 dated Mar. 31, 2022. |
| Non Final Office Action from U.S. Appl. No. 17/569,390 dated Apr. 1, 2022. |
| Extended European Search Report from European Patent Application No. 20766750.2 dated Feb. 18, 2022 (21 pages). |
| Final Office Action from U.S. Appl. No. 17/320,033 dated Nov. 5, 2021. |
| Final Office Action from U.S. Appl. No. 17/319,994 dated Nov. 16, 2021. |
| Non Final Office Action from U.S. Appl. No. 17/384,246 dated Nov. 26, 2021. |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/074155 dated Apr. 21, 2020 (11 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/074156 dated Apr. 22, 2020 (10 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/074159 dated Apr. 22, 2020 (9 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/074160 dated Apr. 23, 2020 (10 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/074161 dated Apr. 28, 2020 (11 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/074162 dated Apr. 28, 2020 (8 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/074163 dated Apr. 22, 2020 (11 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/074164 dated Apr. 29, 2020 (8 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/077415 dated Apr. 26, 2020 (9 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/077416 dated May 27, 2020 (10 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/077417 dated May 27, 2020 (9 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/077418 dated May 28, 2020 (9 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/098471 dated Oct. 10, 2020 (10 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/099702 dated Aug. 27, 2020 (9 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/100992 dated Sep. 28, 2020 (10 pages). |
| International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/100998 dated Oct. 12, 2020 (9 pages). |
| Non Final Office Action from U.S. Appl. No. 17/320,008 dated Jul. 12, 2021. |
| Non Final Office Action from U.S. Appl. No. 17/319,994 dated Jul. 26, 2021. |
| Non Final Office Action from U.S. Appl. No. 17/320,033 dated Jul. 27, 2021. |
| Foreign Communication From a Related Counterpart Application, European Application No. 20748417.1, Extended European Search Report dated Oct. 25, 2022, 11 pages. |
| Non-Final Office Action dated Nov. 19, 2021, 38 pages, U.S. Appl. No. 17/362,341, filed Jun. 29, 2021. |
| Notice of Allowance dated Jul. 7, 2022, 24 pages, U.S. Appl. No. 17/362,341, filed Jun. 29, 2021. |
| Foreign Communication From a Related Counterpart Application, European Application No. 20766750.2, Extended European Search Report dated Feb. 18, 2022, 21 pages. |
| Notice of Allowance dated Jul. 27, 2022, 14 pages, U.S. Appl. No. 17/570,723, filed Jan. 7, 2022. |
| Document: JVET-L1028-v3, Xu, X., et al., “Description of Core Experiment 8: Screen Content Coding Tools,” 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, 14 pages. |
| Document: JVET-L1001-v5, Bross, B., 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, 4 pages. |
| Document: JVET-M1001-v5, Bross, B., 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, 287 pages. |
| Final Office Action from U.S. Appl. No. 17/571,748 dated Jan. 11, 2024, 13 pages. |
| Final Office Action from U.S. Appl. No. 17/386,510 dated Jan. 16, 2024, 87 pages. |
| Ku et al. “CE8: CPR Reference Memory Reuse Without Increasing Memory Requirement (CE8.1.2a and CE8.1.2d),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 13 Meeting, Marrakesh, MA, Jan. 9-18, 2019, document JVET-M0407, 2019. |
| 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. |
| https://vcgil.hhi.fraunhofer.de/jveWVCSoftware_VTM/-/lagsNTM-3.0, Nov. 14, 2022. |
| Venugopal et al. “Cross Check of JVET-L0297 (CE8-Related: CPR Mode with Local Search Range Optimization),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP3 and ISO/IEC JTC 1/SC 29/WG 11, 12th Meeting, Macao, CN, Oct. 3-12, 2018, document JVET-L0518, 2018. |
| Ku et al. “CE8: CPR Reference Memory Reuse Without Reduced Memory Requirement (CEB.1.2b and CE8.1.2c),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 13 Meeting, Marrakesh, MA, Jan. 9-18, 2019, document JVET-M0408. |
| Information Technology—High Efficiency Coding and Media Delivery in Heterogeneous Environments—Part 2: High Efficiency Video Coding Apr. 20, 2018, ISO/DIS 23008, 4th Edition. |
| Rosewarne et al. “High Efficiency Video Coding (HEVC) Test Model 16 (HM 16) Improved Encoder Description Update 7,” Joint Collaborative Team on Video Coding (JCT-VC) ITU-T SG 16 WP3 and ISO/IEC JTC1/SC29/WG11, 15th Meeting, Chengdu, CN, Oct. 14-21, 2019, document JCTVC-Y1002, 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-G1001, 2017. |
| JEM-7.0: https://jvet.hhi.fraunhofer.de/svn/svn_HMJEMSoftware/tags/ HM-16.6-JEM-7.0, Nov. 14, 2022. |
| Liao et al. “CE10.3.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. |
| Chen et al. “CE4: Separate List for Sub-Block Merge Candidates {Test 4.2.8),” Joint Video Experts Team {JVET) of TU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 12th Meeting, Macao, CN, Oct. 3-12, 2018, document JVET L0369, 2018. |
| Lu et al. “CE12: Mapping Functions {Test CE12-1 and CE12-2),” Joint Video Experts Team (JVET) of ITU-I SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting, Marrakech, MA, Jan. 9-18, 2019, document JVET-M0427, 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. |
| Ku et al. “Non-CE8: Reference Memory Reduction for Intra Block Copy,” 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-N0250, 2019. |
| Ku et al. “Non-CE8: Intra Block Copy Clean-Up,” 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, documentJVET-N0251, 2019. |
| Ku et al. “Non-CE8: On IBC Reference Buffer Design,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and SO/IEC JTC 1/SC 29/WG 11 14th Meeting, Geneva, CH, Mar. 19-27, 2019, document JVET-N0472, 2019. |
| Pang et al. “Intra Block Copy with Larger Search Region,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 17th Meeting, Valencia, ES, 27 Mar.-Apr. 4, 2014, document JCTVC-Q0139, 2014. |
| Zhang et al. “Symmetric Intra Block Copy,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 17th Meeting, Valencia, ES, Mar. 27-Apr. 4, 2014, document JCTVC-Q0082, 2014. |
| Hendry et al. “APS Partial Update—APS Buffer Management,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 9th Meeting, Geneva, CH, Apr. 27- May 7, 2012, document JCTVC-I0082, 2012. |
| Budagavi et al. “AHG8: Video-Coding Using Intra Motion Compensation,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting, Incheon, KR, Apr. 18-26, 2013, document JCTVC-M0350, 2013. |
| 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. |
| Yang et al. “CE:4 Summary Report on Inter Prediction and Motion Vector Coding,” 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-L0024, 2018. |
| Nam et al. “Non-CEB: Block Vector Predictor for IBC,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and SO/IEC JTC 1/SC 29/WG 11 12th Meeting, Macau, CN, Oct. 8-12, 2018, document JVET-L0159, 2018. |
| Sole et al. “HEVC Screen Content Coding Core Experiment 1 (SCCE1): Intra Block Copying Extensions,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG 16 WP 3 and ISO/IEC JTC1/SC29/WG11 17th Meeting, Valencia, ES Mar. 27-Apr. 4, 2014 , document JCTVC-Q1121, 2014. |
| Pang et al. “SCCE1: Test 1.1—Intra Block Copy with Different Areas,” Joint Collaborative Team on Video Coding JCT-VC) of ITU-T SG 16 WP 3 and ISO/IEC JTC1/SC29/WG11 18th Meeting, Sapporo, JP, Jun. 30-Jul. 9, 2014, document JCTVC-R0184, 2014. |
| Ku et al. “Non-CE8: IBC Search Range Adjustment for Implementation Consideration,” 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-N0383, 2019. |
| Gao et al. “CE8-Related: Dedicated IBC Reference Buffer without Bitstream Restrictions,” Joint Video Experts Team JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 15th Meeting, Gothenburg, SE, Jul. 3-12, 2019, document JVET-O0248, 2019. |
| Li et al. “CE8-Related: IBC Modifications,” Joint Video Experts Team {JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 15th Meeting, Gothenburg, SE, Jul. 3-12, 2019, document JVET-O0127, 2019. |
| Chen et al., “CE4: Affine Merge Enhancement with Simplification (Test 4.2.2),” 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-L0368, 2018. |
| Van et al. “CE8-Related: Restrictions for the Search Area of the IBC Blocks in CPR,” 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, 208, document JVET-L0404, 2018. |
| Flynn et al. “BoG Report on Range Extensions Topics,” Joint Collaborative Team on Video Coding (JCT-VC) on ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 15th Meeting, Geneva, CH, Oct. 23-Nov. 1, 2013, document JCTVC-O0352, 2013. |
| Ku 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, XP011636923. |
| Ku et al. “CE8-Related: CPR Mode with Local Search Range Optimization,” Joint Video Experts Team (JVET) of ITU-SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 12th Meeting, Macao, CN, Oct. 3-12, 2018, document JVET-0297, 2018. |
| Chen et al. “Algorithm Description for Versatlie Video Coding and Test Model 3 {VTM 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-L1002, 2018. |
| Chen et al. “Algorithm Description for Versatlie Video Coding and Test Model 4 {VTM 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-M1002, 2019. |
| Encoder Decoder + Intra Block Copy + Buffer or Reference Buffer+ Bit Depth or Bit-Depth Google Search, Mar. 22, 2022. |
| Intra Block Copy Library USTPO Query for NPL, Mar. 22, 2022. |
| Document: JCTVC-V0050r1, Rapaka, K., et al., “On Storage of unfiltered and filtered current decoded pictures,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 22nd Meeting: Geneva, CH, Oct. 15-21, 2015. |
| Heng et al. “Non-CE8: Comments on Current Picture Referencing,” 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-M0402, 2019. |
| Gao et al. “Bitstream Conformance with a Virtual IBC Buffer Concept,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 15th Meeting, Gothenburg, SE, Jul. 3-12, 2019, document JVET-O1171, 2019. |
| Ku et al. “Bitstream Conformance with a Virtual IBC Buffer Concept,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 15th Meeting, Gothenburg, SE, Jul. 3-12, 2019, document JVET-O1170, 2019. |
| Hannuksela et al. “AHG 12: single_slice_per_subpic_flag,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 16th Meeting: Geneva, CH, Oct. 1-11, 2019, document JVET-P1024, 2019. |
| Hannuksela et al. Versatile Video Coding (Draft 6), Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and SO/IEC JTC 1/SC 29/WG 11, 15th Meeting, Gothenburg, SE Jul. 3-12, 2019, document JVET-O2001, 2019. |
| Ku et al. “An Implementation of JVET-O0568 based on the IBC Buffer Design of JVET-O0127,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 15th Meeting, Gothenburg, SE, Jul. 3-12, 2019, document JVET-O1161, 2019. |
| Ku et al. “Non-CE8: IBC Search Range Increase for Small CTU Size,” 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-N0384, 2019. |
| Document: JVET-M0028-v3, Xu, X., et al., “CE8: Summary Report on Screen Content Coding” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 13th Meeting, Marrakesh, MA, Jan. 9-18, 2019, 6 pages. |
| Document: JCTVC-O0183, Li, et al., “On Intra BC mode,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 15th Meeting: Geneva, CH, Oct. 23-Nov. 1, 2013, 15 pages. |
| Document: JVET-L1028-v3, Xu, X., et al., “Description of Core Experiment 8 (CE8): Screen Content Coding Tools,” 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, 14 pages. |
| Document: JCTVC-P0211, Alshin, E., et al., “RCE3: intra block copy search range (tests A),” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 16th Meeting: San José, US, Jan. 9-17, 2014, 11 pages. |
| Document: JCTVC-R0141, Wang, W., et al., “SCCE1: Result of Test 1.2 for IBC with constrained buffers from left CTUs,” 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, 2014, 8 pages. |
| Document: JVET-L0297-v1, Xu, X., et al., “CE8-related: CPR mode with local search range optimization,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 14th Meeting: Macao, CN, Oct. 3-12, 2018, 6 pages. |
| Document: JVET-N0472, Xu, J., et al., “Non-CE8: On IBC reference buffer design,” 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, 4 pages. |
| Document: JVET-O0127-v3, Li, J., et al., “CE8-related: IBC modifications,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 15th Meeting: Gothenburg, SE, Jul. 3-12, 2019, 11 pages. |
| Non-Final Office Action from U.S. Appl. No. 18/076,031 dated Feb. 26, 2024, 65 pages. |
| European Office Action from European Application No. 20766750.2 dated Feb. 26, 2024, 10 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230135007 A1 | May 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17569390 | Jan 2022 | US |
| Child | 18083919 | US | |
| Parent | PCT/CN2020/099702 | Jul 2020 | WO |
| Child | 17569390 | US |
