Prediction using intra-buffer samples for intra block copy in video coding

Description

TECHNICAL FIELD

This patent document relates to video coding and decoding techniques, devices and systems.

BACKGROUND

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.

SUMMARY

The present document describes various embodiments and techniques 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 video or image (visual data) processing is disclosed. The method includes determining a size of a buffer to store reference samples for prediction in an intra block copy mode; and performing a conversion between a current video block of visual media data and a bitstream representation of the current video block, using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture.

In another example aspect, another method of visual data processing is disclosed. The method includes determining, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reconstructed samples for prediction in an intra block copy mode, wherein the buffer is used for storing the reconstructed samples before a loop filtering step; and performing the conversion using the reconstructed samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture.

In yet another example aspect, another method of visual data processing is disclosed. The method includes determining, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reconstructed samples for prediction in an intra block copy mode, wherein the buffer is used for storing the reconstructed samples after a loop filtering step; and performing the conversion using the reconstructed samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in a same video region with the current video block without referring to a reference picture.

In another example aspect, another method of video processing is disclosed. The method includes using a buffer to store reference samples for prediction in an intra block copy mode, wherein a first bit-depth of the buffer is different than a second bit-depth used to represent visual media data in the bitstream representation; and performing a conversion between a current video block of the visual media data and a bitstream representation of the current video block, using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture.

In yet another example aspect, another method of video processing is disclosed. The method includes initializing a buffer to store reference samples for prediction in an intra block copy mode, wherein the buffer is initialized with a first value; and performing a conversion between a current video block of visual media data and a bitstream representation of the current video block using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture.

In yet another example aspect, another method of video processing is disclosed. The method includes initializing a buffer to store reference samples for prediction in an intra block copy mode, wherein, based on availability of one or more video blocks in visual media data, the buffer is initialized with pixel values of the one or more video blocks in the visual media data; and performing a conversion between a current video block that does not belong to the one or more video blocks of the visual media data and a bitstream representation of the current video block, using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture.

In yet another example aspect, another method of video processing is disclosed. The method includes determining, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reference samples for prediction in an intra block copy mode; performing the conversion using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture; and for a pixel spatially located at location (x0, y0) and having a block vector (BVx, BVy) included in the motion information, computing a corresponding reference in the buffer based on a reference location (P mod M, Q mod N) where “mod” is modulo operation and M and N are integers representing x and y dimensions of the buffer, wherein the reference location (P, Q) is determined using the block vector (BVx, BVy) and the location (x0, y0).

In yet another example aspect, another method of video processing is disclosed. The method includes determining, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reference samples for prediction in an intra block copy mode; performing the conversion using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture; and for a pixel spatially located at location (x0, y0) and having a block vector (BVx, BVy) included in the motion information, computing a corresponding reference in the buffer based on a reference location (P, Q), wherein the reference location (P, Q) is determined using the block vector (BVx, BVy) and the location (x0, y0).

In yet another example aspect, another method of video processing is disclosed. The method includes determining, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reference samples for prediction in an intra block copy mode, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture; for a pixel spatially located at location (x0, y0) of the current video block and having a block vector (BVx, BVy), computing a corresponding reference in the buffer at a reference location (P, Q), wherein the reference location (P, Q) is determined using the block vector (BVx, BVy) and the location (x0, y0); and upon determining that the reference location (P, Q) lies outside the buffer, re-computing the reference location using a sample in the buffer.

In yet another example aspect, another method of video processing is disclosed. The method includes determining, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reference samples for prediction in an intra block copy mode, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture; for a pixel spatially located at location (x0, y0) of the current video block relative to an upper-left position of a coding tree unit including the current video block and having a block vector (BVx, BVy), computing a corresponding reference in the buffer at a reference location (P, Q), wherein the reference location (P, Q) is determined using the block vector (BVx, BVy) and the location (x0, y0); and upon determining that the reference location (P, Q) lies outside the buffer, constraining at least a portion of the reference location to lie within a pre-defined range.

In yet another example aspect, another method of video processing is disclosed. The method includes determining, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reference samples for prediction in an intra block copy mode, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture; for a pixel spatially located at location (x0, y0) of the current video block relative to an upper-left position of a coding tree unit including the current video block and having a block vector (BVx, BVy), computing a corresponding reference in the buffer at a reference location (P, Q), wherein the reference location (P, Q) is determined using the block vector (BVx, BVy) and the location (x0, y0); and upon determining that the block vector (BVx, BVy) lies outside the buffer, padding the block vector (BVx, BVy) according to a block vector of a sample value inside the buffer.

In yet another example aspect, another method of video processing is disclosed. The method includes resetting, during a conversion between a video and a bitstream representation of the video, a buffer that stores reference samples for prediction in an intra block copy mode at a video boundary; and performing the conversion using the reference samples stored in the buffer, wherein the conversion of a video block of the video is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the video block without referring to a reference picture.

In yet another example aspect, another method of video processing is disclosed. The method includes performing a conversion between a current video block and a bitstream representation of the current video block; and updating a buffer which is used to store reference samples for prediction in an intra-block copy mode, wherein the buffer is used for a conversion between a subsequent video block and a bitstream representation of the subsequent video block, wherein the conversion between the subsequent video block and a bitstream representation of the subsequent video block is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the subsequent video block without referring to a reference picture.

In yet another example aspect, another method of video processing is disclosed. The method includes determining, for a conversion between a current video block and a bitstream representation of the current video block, a buffer that is used to store reconstructed samples for prediction in an intra block copy mode, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture; and applying a pre-processing operation to the reconstructed samples stored in the buffer, in response to determining that the reconstructed samples stored in the buffer are to be used for predicting sample values during the conversation.

In yet another example aspect, another method of video processing is disclosed. The method includes 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, whether to use K1 previously processed VPDUs from an even-numbered row of the video region and/or K2 previously processed VPDUs from an odd-numbered row of the video region; and performing the conversion, wherein the conversion excludes using remaining of the current VPDU, wherein the conversion is performed in an intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the video block without referring to a reference picture.

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 details in the present document.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows an example of current picture referencing or intra block copy video or image coding technique.

FIG. 2 shows an example of dynamic reference area.

FIG. 3 shows an example of coding of a block starting from (x, y).

FIG. 4 shows examples of possible alternative way to choose the previous coded 64×64 blocks.

FIG. 5 shows an example of a possible alternative way to change the coding/decoding order of 64×64 blocks.

FIG. 6 is a flowchart of an example method of video or image processing.

FIG. 7 is a block diagram of a hardware platform for video or image coding or decoding.

FIG. 8 shows another possible alternative way to choose the previous coded 64×64 blocks, when the decoding order for 64×64 blocks is from top to bottom, left to right.

FIG. 9 shows another possible alternative way to choose the previous coded 64×64 blocks.

FIG. 10 shows an example flowchart for a decoding process with reshaping.

FIG. 11 shows another possible alternative way to choose the previous coded 64×64 blocks, when the decoding order for 64×64 blocks is from left to right, top to bottom.

FIG. 12 is an illustration of IBC reference buffer status, where a block denotes a 64×64 CTU.

FIG. 13 shows one arrangement of reference area for IBC.

FIG. 14 shows another arrangement of reference area for IBC.

FIG. 15 shows another arrangement of reference area for IBC when the current virtual pipeline data unit (VPDU) is to the right side of the picture boundary.

FIG. 16 shows an example of the status of virtual buffer when VPDUs in a CTU row are decoded sequentially.

FIG. 17 is a block diagram of an example video processing system in which disclosed techniques may be implemented.

FIG. 18 is a flowchart of an example method of visual data processing.

FIG. 19 is a flowchart of an example method of visual data processing.

FIG. 20 is a flowchart of an example method of visual data processing.

FIG. 21 is a flowchart of an example method of visual data processing.

FIG. 22 is a flowchart of an example method of visual data processing.

FIG. 23 is a flowchart of an example method of visual data processing.

FIG. 24 is a flowchart of an example method of visual data processing.

FIG. 25 is a flowchart of an example method of visual data processing.

FIG. 26 is a flowchart of an example method of visual data processing.

FIG. 27 is a flowchart of an example method of visual data processing.

FIG. 28 is a flowchart of an example method of visual data processing.

FIG. 29 is a flowchart of an example method of visual data processing.

FIG. 30 is a flowchart of an example method of visual data processing.

FIG. 31 is a flowchart of an example method of visual data processing.

FIG. 32 is a flowchart of an example method of visual data processing.

FIG. 33 is a flowchart of an example method of visual data processing.

FIG. 34 is a flowchart of an example method of visual data processing.

DETAILED DESCRIPTION

Section headings are used in the present document for ease of understanding and do not limit scope of the disclosed embodiments in each section only to that section. The present document describes various embodiments and techniques for buffer management and block vector coding for intra block copy mode for decoding or encoding video or images.

1. SUMMARY

This patent document 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. It may be also applicable to future video coding standards or video codec.

2. BRIEF DISCUSSION

Video coding standards have evolved primarily through the development of the well-known ITU-T and ISO/IEC standards. The ITU-T produced H.261 and H.263, ISO/IEC produced 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 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 at 50% bitrate reduction compared to HEVC.

2.1 Inter Prediction in HEVC/H.265

Each inter-predicted PU has motion parameters for one or two reference picture lists. Motion parameters include a motion vector 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 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 neighbouring 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.

2.2 Current Picture Referencing

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. IBC extends the concept of motion compensation from inter-frame coding to intra-frame coding. As demonstrated in FIG. 1, the current block is predicted by a reference block in the same picture when CPR is applied. The samples in the reference block must have been already reconstructed before the current block is coded or decoded. Although CPR is not so efficient for most camera-captured sequences, it shows significant coding gains for screen content. The reason is that there are lots of repeating patterns, such as icons and text characters in a screen content picture. CPR can remove the redundancy between these repeating patterns effectively. In HEVC-SCC, an inter-coded coding unit (CU) can apply CPR if it chooses the current picture as its reference picture. The MV is renamed as block vector (BV) in this case, and a BV always has an integer-pixel precision. To be compatible with main profile HEVC, the current picture is marked as a “long-term” reference picture in the Decoded Picture Buffer (DPB). It should be noted that similarly, in multiple view/3D video coding standards, the inter-view reference picture is also marked as a “long-term” reference picture.

Following a BV to find its reference block, the prediction can be generated by copying the reference block. The residual can be got by subtracting the reference pixels from the original signals. Then transform and quantization can be applied as in other coding modes.

FIG. 1 is an example illustration of Current Picture Referencing.

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 constrains, 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-sessions describe the solutions in detail.

2.3 CPR in HEVC Screen Content Coding Extensions

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:(mcCLX[0]&0x7?2:0) (8-104)
offsetY=(ChromaArrayType==0)?0:(mcCLX[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:

- When the deviation process for z-scan order block availability as specified in clause 6.4.1 is invoked with (xCurr, yCurr) set equal to (xCb, yCb) and the neighbouring luma location (xNbY, yNbY) set equal to (xPb+(mvLX[0]>>2)−offsetX, yPb+(mvLX[1]>>2)−offsetY) as inputs, the output shall be equal to TRUE.
- When the deviation process for z-scan order block availability as specified in clause 6.4.1 is invoked with (xCurr, yCurr) set equal to (xCb, yCb) and the neighbouring luma location (xNbY, yNbY) set equal to (xPb+(mvLX[0]>>2)+nPbW−1+offsetX, yPb+(mvLX[1]>>2)−nPbH−1+offsetY) as inputs, the output shall be equal to TRUE.
- One or both of the following conditions shall be true:
  - The value of (mvLX[0]>>2)+nPbW+xB1+offsetX is less than or equal to 0.
  - The value of (mvLX[1]>>2)+nPbH+yB1+offsetY is less than or equal to 0.
- The following conditions shall be true:
  
  (xPb+(mvLX[0]>>2)+nPbSw−1+offsetX)/CtbSizeY−xCb/CtbSizeYyCb/CtbSizeY−(yPb+(mvLX[1]>>2)+nPbSh−1+offsetY)/CtbSizeY (8-106)

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.

2.4 Examples of CPR/IBC

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 colour 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:

- 1) each of the luma CU within the collocated luma block shall be coded with CPR mode
- 2) each of the luma 4×4 block′ BV is firstly converted to a chroma block's BV and the chroma block's BV is a valid BV.

If any of the two condition 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:

- 1) all samples within the reference block identified by a BV shall be within the restricted search range (e.g., shall be within the same CTU in current VVC design).
- 2) all samples within the reference block identified by a BV have been reconstructed.
  
  2.5 Examples of CPR/IBC

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.

FIG. 2 shows a method, where a block is of 64×64 and a CTU contains 464×64 blocks. When coding a 64×64 block, the previous 364×64 blocks can be used as reference. By doing so, a decoder just needs to store 464×64 blocks to support CPR/IBC.

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).

2.6 In-Loop Reshaping (ILR)

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 need to be signaled as the other one can be computed from the signaled 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 Y_ito altered values Y_r: Y_r=FwdLUT [K]. The other LUT is an inverse LUT, InvLUT, that maps altered code values Y_rto Y_r: Ŷ_i=InvLUT [Y_r]. (Y_Lrepresents the reconstruction values of Y_rto Ŷ_i:

2.6.1 PWL Model

Conceptually, piece-wise 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+2^FP_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 implementations to calculate identical mapping values on-the-fly without pre-computing the LUTs.

2.6.2.1 Luma Reshaping

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 TU reconstruction is done. Such arrangement can also provide a unified process for intra mode instead of being slice dependent. FIG. 10 shows the block diagram of the CE12-2 decoding process based on mode.

16-piece piece-wise linear (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 (light-green shaded blocks indicate signal in reshaped domain: luma residue; intra luma predicted; and intra luma reconstructed)

2.6.2.2 Luma-Dependent Chroma Residue Scaling

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:

- For intra, the reconstructed luma is averaged.
- For inter, the prediction luma is averaged.

The average is used to identify an index in a PWL model. The index identifies a scaling factor cScalelnv. 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

2.6.2.3 Signalling of ILR Side Information

The parameters are (currently) sent in the tile group header (similar to 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

seq_parameter_set_rbsp( ) {
Descriptor

sps_seq_parameter_set_id
ue(v)

...

sps_triangle_enabled_flag
u(1)

sps_ladf_enabled_flag
u(1)

if ( sps_ladf_enabled_flag ) {

sps_num_ladf_intervals_minus2
u(2)

sps_ladf_lowest_interval_qp_offset
se(v)

for( i = 0; i <sps_num_ladf_intervals_minus2 + 1; i++) {

sps_ladf_qp_offset[ i ]
se(v)

sps_ladf_delta_threshold_minus1[ i ]
ue(v)

}

}

custom character

u(1)

rbsp_trailing_bits( )

}

In 7.3.3.1 General tile group header syntax

tile_group_header( ) {
Descriptor

...

if( num_tiles_in_tile_group_minus1 > 0 ) {

offset_len_minus1
ue(v)

for( i = 0; i < num_tiles_in_tile_group_minus1; i++)

entry_point_offset_minus1[ i ]
u(v)

}

if ( sps_reshaper_enabled_flag ) {

custom character

u(1)

if ( tile_group_reshaper_model_present_flag )

tile_group_reshaper_model ( )

custom character

u(1)

if ( tile_group_reshaper_enable_flag && (!(

qtbtt_dual_tree_intra_flag && tile_group_type = = I ) ) )

custom character

u(1)

}

byte_alignment( )

}

Add a new syntax table tile group reshaper model:

tile_group_reshaper_model ( ) {
Descriptor

custom character

ue(v)

ue(v)

for ( i = reshaper_model_min_bin_idx; i < =

reshaper_model_max_bin_idx; i+ + ) {

custom character

u(v)

if( reshaper_model_bin_delta_abs_CW[ i ] ) > 0 )

custom character

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_chroma_residual_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_model_delta_max_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_minusl 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_delta_sign_CW_flag[i] specifies the sign of reshape_model_bin_delta_abs_CW[i] as follows:
- If reshape_model_bin_delta_sign_CW_flag[i] is equal to 0, the corresponding variable RspDeltaCW[i] is a positive value.
- Otherwise (reshape_model_bin_delta_sign_CW_flag[i] is not equal to 0), the corresponding variable RspDeltaCW[i] is a negative value.

When reshape_model_bin_delta_sign_CW_flag[i] is not present, it is inferred to be equal to 0.

The variable RspDeltaCW[i]=(12*reshape_model_bin_delta_sign_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).

- If reshaper_model_min_bin jdx<=i<=reshaper_model_max_bin_idx
  
  RspCW[i]=OrgCW+RspDeltaCW[i].
- Otherwise, RspCW[i]=0.

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:

shiftY = 14

ReshapePivot[ 0 ] = 0;

for( i = 0; i <= MaxBinIdx ; i++) {

ReshapePivot[ i + 1 ] = ReshapePivot[ i ] + RspCW[ i ]

ScaleCoef[ i ] = ( RspCW[ i ] * (1 << shiftY) + (1 << (Log2(OrgCW) − 1))) >>

(Log2(OrgCW))

if ( RspCW[ i ] == 0 )

InvScaleCoeff[ i ] = 0

else

InvScaleCoeff[ i ] = OrgCW * (1 << shiftY) / RspCW[ i ]

}

The variable ChromaScaleCoef[i] with i in the range of 0 to MaxBinIdx, inclusive, are derived as follows:

- ChromaResidualScaleLut1641=116384, 16384, 16384, 16384, 16384, 16384, 16384, 8192, 8192, 8192, 8192, 5461, 5461, 5461, 5461, 4096, 4096, 4096, 4096, 3277, 3277, 3277, 3277, 2731, 2731, 2731, 2731, 2341, 2341, 2341, 2048, 2048, 2048, 1820, 1820, 1820, 1638, 1638, 1638, 1638, 1489, 1489, 1489, 1489, 1365, 1365, 1365, 1365, 1260, 1260, 1260, 1260, 1170, 1170, 1170, 1170, 1092, 1092, 1092, 1092, 1024, 1024, 1024, 10241;
- shiftC=11
  - if (RspCW[i]==0)
  - ChromaScaleCoef[i]=(1<<shiftC)
  - Otherwise (RspCW[i]!=0), ChromaScaleCoef[i]=ChromaResidualScaleLut[RspCW[i]>>1]
    
    2.6.2.4 Usage of ILR

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 residual 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

3. EXAMPLES OF PROBLEMS SOLVED BY VARIOUS EMBODIMENTS

In the current design of CPR/IBC, some problems exist.

- 1) The reference area changes dynamically, which makes encoder/decoder processing complicated.
- 2) Invalid block vectors are easily generated and difficult to check, which complicates both encoder and decoder.
- 3) Irregular reference area leads to inefficient coding of block vector.
- 4) How to handle CTU size smaller than 128×128 is not clear.
- 5) In the determination process of whether a BV is valid or invalid, for chroma blocks, the decision is based on the luma sample's availability which may result in wrong decisions due to the dual tree partition structure.

4. EXAMPLE EMBODIMENTS

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) return 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) hasn't been reconstructed yet, 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’.

Reference Buffer for CPR/IBC

- 1. It is proposed to use a M×N pixel buffer to store the luma reference samples for CPR/IBC.
  - a. In one example, the buffer size is 64×64.
  - b. In one example, the buffer size is 128×128.
  - c. In one example, the buffer size is 64×128.
  - d. In one example, the buffer size is 128×64.
  - e. In one example, N equals to the height of a CTU.
  - f. In one example, N=nH, where H is the height of a CTU, n is a positive integer.
  - g. In one example, M equals to the width of a CTU.
  - h. In one example, M=mW, where W is the width of a CTU, m is a positive integer.
  - i. In one example, the buffer size is unequal to the CTU size, such as 96×128 or 128×96.
  - j. In one example, the buffer size is equal to the CTU size
  - k. In one example, M=mW and N=H, where W and H are width and height of a CTU, m is a positive integer.
  - l. In one example, M=W and N=nH, where W and H are width and height of a CTU, n is a positive integer.
  - m. In one example, M=mW and N=nH, where W and H are width and height of a CTU, m and n are positive integers.
  - n. In above example, m and n may depend on CTU size.
    - i. In one example, when CTU size is 128×128, m=1 and n=1.
    - ii. In one example, when CTU size is 64×64, m=4 and n=1.
    - iii. In one example, when CTU size is 32×32, m=16 and n=1.
    - iv. In one example, when CTU size is 16×16, m=64 and n=1.
  - o. Alternatively, the buffer size corresponds to CTU size.
  - p. Alternatively, the buffer size corresponds to a Virtual Pipeline Data Unit (VPDU) size.
  - q. M and/or N may be signaled from the encoder to the decoder, such as in VPS/SPS/PPS/picture header/slice header/tile group header.
- 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.
  - a. In one example, Mc=M/2 and Nc=N/2 for 4:2:0 video
  - b. In one example, Mc=M and Nc=N for 4:4:4 video
  - c. In one example, Mc=M and Nc=N/2 for 4:2:2 video
  - d. Alternatively, Mc and Nc can be independent of M and N.
  - e. In one example, the chroma buffer includes two channels, corresponding to Cb and Cr.
  - f. In one example, Mc=M and Nc=N.
- 3. It is proposed to use a M×N sample buffer to store the RGB reference samples for CPR/IBC
  - a. In one example, the buffer size is 64×64.
  - b. In one example, the buffer size is 128×128.
  - c. In one example, the buffer size is 64×128.
  - d. In one example, the buffer size is 128×64.
  - e. Alternatively, the buffer size corresponds to CTU size.
  - f. Alternatively, the buffer size corresponds to a Virtual Pipeline Data Unit (VPDU) size.
- 4. It is proposed that the buffer can store reconstructed pixels before loop-filtering. Loop-filtering may refer to deblocking filter, adaptive loop filter (ALF), sample adaptive offset (SAO), a cross-component ALF, or any other filters.
  - a. In one example, the buffer can store samples in the current CTU.
  - b. In one example, the buffer can store samples outside of the current CTU.
  - c. In one example, the buffer can store samples from any part of the current picture.
  - d. In one example, the buffer can store samples from other pictures.
- 5. It is proposed that the buffer can store reconstructed pixels after loop-filtering. Loop-filtering may refer to deblocking filter, adaptive loop filter (ALF), sample adaptive offset (SAO), a cross-component ALF, or any other filters.
  - a. In one example, the buffer can store samples in the current CTU.
  - b. In one example, the buffer can store samples outside of the current CTU.
  - c. In one example, the buffer can store samples from any part of the current picture.
  - d. In one example, the buffer can store samples from other pictures.
- 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, adaptive loop filter (ALF), sample adaptive offset (SAO), a cross-component ALF, or any other filters.
  - a. In one example, the buffer can store both samples from the current picture and samples from other pictures, depending on the availability of those samples.
  - b. In one example, reference samples from other pictures are from reconstructed samples after loop-filtering.
  - c. In one example, reference samples from other pictures are from reconstructed samples before loop-filtering.
- 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.
  - a. In one example, the bit-depth for the reconstruction buffer/coded video data is larger than that for IBC reference samples stored in the buffer.
  - b. In one example, even when the internal bit-depth is different from the input bit-depth for a video sequence, such as (10 bits vs 8 bits), the IBC reference samples are stored to be aligned with the input bit-depth.
  - c. In one example, the bit-depth is identical to that of the reconstruction buffer.
  - d. In one example, the bit-depth is identical to that of input image/video.
  - e. In one example, the bit-depth is identical to a predefine number.
  - f. In one example, the bit-depth depends on profile of a standard.
  - g. In one example, the bit-depth or the bit-depth difference compared to the output bit-depth/input bit-depth/internal bit-depth may be signalled in SPS/PPS/sequence header/picture header/slice header/Tile group header/Tile header or other kinds of video data units.
  - h. The proposed methods may be applied with the proposed buffer definitions mentioned in other bullets, alternatively, they may be also applicable to existing design of IBC.
  - i. The bit-depth of each color component of the buffer may be different.
    
    Buffer Initiation
- 8. It is proposed to initialize the buffer with a given value
  - a. In one example, the buffer is initialized with a given value.
    - i. In one example, the given value may depend on the input bit-depth and/or internal bit-depth.
    - ii. In one example, the buffer is initialized with mid-grey value, e.g. 128 for 8-bit signal or 512 for 10-bit signal.
    - iii. In one example, the buffer is initialized with forwardLUT(m) when ILR is used. E.g. m=1<<(Bitdepth−1).
  - b. Alternatively, the buffer is initialized with a value signalled in SPS/VPS/APS/PPS/sequence header/Tile group header/Picture header/tile/CTU/Coding unit/VPDU/region.
  - c. In one example, the given value may be derived from samples of previously decoded pictures or slices or CTU rows or CTUs or CUs.
  - d. The given value may be different for different color component.
- 9. Alternatively, it is proposed to initialize the buffer with decoded pixels from previously coded blocks.
  - a. In one example, the decoded pixels are those before in-loop filtering.
  - b. In one example, when the buffer size is a CTU, the buffer is initialized with decoded pixels of the previous decoded CTU, if available.
  - c. In one example, when the buffer size is of 64×64, its buffer size is initialized with decoded pixels of the previous decoded 64×64 block, if available.
  - d. Alternatively, furthermore, if no previously coded blocks are available, the methods in bullet 8 may be applied.
    
    Reference to the Buffer
- 10. For a block to use pixels in the buffer as 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 reference.
- 11. Alternatively, the reference position can be denoted as 1=y*M+x, 1=0, 1, . . . , M*N−1.
- 12. Denote that 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 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)
  - a. In one example, when (x0+BVx, y0+BVy) is outside of the buffer, it will be clipped to the boundary.
  - b. Alternatively, when (x0+BVx, y0+BVy) is outside of the buffer, its reference value is predefined as a given value, e.g. mid-grey.
  - c. Alternatively, the reference position is defined as ((x0+BVx) mod M, (y0+BVy) mod N) so that it is always within the buffer.
- 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.
  - a. In one example, the value is derived from the sample ((x0+BVx) mod M, (y0+BVy) mod N) in the buffer.
  - b. In one example, the value is derived from the sample ((x0+BVx) mod M, clip(y0+BVy, 0, N−1)) in the buffer.
  - c. In one example, the value is derived from the sample (clip(x0+BVx, 0, M−1), (y0+BVy) mod N) in the buffer.
  - d. In one example, the value is derived from the sample (clip(x0+BVx, 0, M−1), clip(y0+BVy, 0, N−1)) in the buffer.
- 16. It may disallow a certain coordinate outside of the buffer range
  - a. In one example, for any pixel (x0, y0) relative to the upperleft corner of a CTU and block vector (BVx, BVy), it is a bitstream constraint that y0+BVy should be in the range of [0, . . . , N−1].
  - b. In one example, for any pixel (x0, y0) relative to the upperleft corner of a CTU and block vector (BVx, BVy), it is a bitstream constraint that x0+BVx should be in the range of [0, . . . , M−1].
  - c. In one example, for any pixel (x0, y0) relative to the upperleft corner of a CTU and block vector (BVx, BVy), it is a bitstream constraint that both y0+BVy should be in the range of [0, . . . , N−1] and x0+BVx should be in the range of [0, . . . , M−1].
- 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.
  - a. In one example, the value of any sample outside of the buffer is defined with a predefined value.
    - i. In one example, the value can be 1<<(Bitdepth−1), e.g. 128 for 8-bit signals and 512 for 10-bit signals.
    - ii. In one example, the value can be forwardLUT(m) when ILR is used. E.g. m=1<<(Bitdepth−1).
    - iii. Alternatively, indication of the predefined value may be signalled or indicated at SPS/PPS/sequence header/picture header/slice header/Tile group/Tile/CTU/CU level.
  - b. In one example, any sample outside of the buffer is defined as the value of the nearest sample in 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).
  - a. In one example, when y0+BVy is outside of [0, N−1], the sample value of (x0+BVx, y0+BVy) is assigned as a predefined value.
  - b. In one example, when x0+BVx is outside of [0, M−1], the sample value of (x0+BVx, y0+BVy) is assigned as a predefined value.
  - c. Alternatively, the sample value of (x0+BVx, y0+BVy) is assigned as the sample value of ((x0+BVx)mod M, y0+BVy), which may invoke other method to further derive the value if ((x0+BVx)mod M, y0+BVy) is still outside of the buffer.
  - d. Alternatively, the sample value of (x0+BVx, y0+BVy) is assigned as the sample value of (x0+BVx, (y0+BVy) mod N), which may invoke other method to further derive the value if (x0+BVx, (y0+BVy) mod N) is still outside of the buffer.
    
    Block Vector Representation
- 19. Each component of a block vector (BVx, BVy) or one of the component may be normalized to a certain range.
  - a. In one example, BVx can be replaced by (BVx mod M).
  - b. Alternatively, BVx can be replaced by ((BVx+X) mod M)−X, where X is a predefined value.
    - i. In one example, X is 64.
    - ii. In one example, X is M/2;
    - iii. In one example, X is the horizontal coordinate of a block relative to the current CTU.
  - c. In one example, BVy can be replaced by (BVy mod N).
  - d. Alternatively, BVy can be replaced by ((BVy+Y) mod N)−Y, where Y is a predefined value.
    - i. In one example, Y is 64.
    - ii. In one example, Y is N/2;
    - iii. In one example, Y is the vertical coordinate of a block relative to the current CTU.
- 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.
  - b. Alternatively, BVDx can be replaced by ((BVDx+X) mod M)−X, where X is a predefined value.
    - i. In one example, X is 64.
    - ii. In one example, X is M/2;
  - c. In one example, BVy can be replaced by (BVDy mod N).
  - d. Alternatively, BVy can be replaced by ((BVDy+Y) mod N)−Y, where Y is a predefined value.
    - i. In one example, Y is 64.
    - ii. In one example, Y is N/2;
- 22. BVDx and BVDy may have different normalized ranges.
  
  Validity Check for a Block Vector

Denote the width and height of an IBC buffer as W_bufand H_buf. 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 W_picand H_picbe the width and height of a picture and; W_ctuand H_ctube the width and height of a CTU. Function floor(x) returns the largest integer no larger than x. Function isRec(x, y) returns if 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.
  - a. In one example, the block vector may be set as valid even if X+BVx<0.
  - b. In one example, the block vector may be set as valid even if X+W+BVx>W_pic.
  - c. In one example, the block vector may be set as valid even if Y+BVy<0.
  - d. In one example, the block vector may be set as valid even if Y+H+BVy>H_pic.
- 24. Block vector (BVx, BVy) may be set as valid even if any reference position is outside of the current CTU row.
  - a. In one example, the block vector may be set as valid even if Y+BVy<floor(Y/H_ctu)*H_ctu.
  - b. In one example, the block vector may be set as valid even if Y+H+BVy>=floor(Y/H_ctu)*H_ctu+H_ctu.
- 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.
  - a. In one example, the block vector may be set as valid even if X+BVx<floor(X/W_ctu)*W_ctu−(n−1)*W_ctu.
  - b. In one example, the block vector may be set as valid even if X+W+BVx>floor(X/W_ctu)*W_ctu+W_ctu
- 26. Block vector (BVx, BVy) may be set as valid even if a certain sample has not been reconstructed.
  - a. In one example, the block vector may be set as valid even if isRec(X+BVx, Y+BVy) is false.
  - b. In one example, the block vector may be set as valid even if isRec(X+BVx+W−1, Y+BVy) is false.
  - c. In one example, the block vector may be set as valid even if isRec(X+BVx, Y+BVy+H−1) is false.
  - d. In one example, the block vector may be set as valid even if isRec(X+BVx+W−1, Y+BVy+H−1) is false.
- 27. Block vector (BVx, BVy) may be always set as valid when a block is not of the 1^stCTU in a CTU row.
  - a. Alternatively, the block vector may be always set as valid.
- 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/H_ctu)
  isRec(X+BVx+W−1,Y+BVy+H−1)==true
  - a. Alternatively, when the three conditions are all satisfied for a block of the 1st CTU in a CTU row, the block vector may be always set as valid.
- 29. When a block vector (BVx, BVy) is valid, sample copying for the block may be based on the block vector.
  - a. In one example, prediction of sample (X, Y) may be from ((X+BVx) % W_buf, (Y+BVy) % H_buf)
    
    Buffer Update
- 30. When coding a new picture or tile, the buffer may be reset.
  - a. The term “reset” may refer that the buffer is initialized.
  - b. The term “reset” may refer that all samples/pixels in the buffer is set to a given value (e.g., 0 or −1).
- 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.
  - a. In one example, when the buffer is not full, the buffer may be updated CTU by CTU sequentially.
  - b. In one example, when the buffer is full, the buffer area corresponding to the oldest CTU will be updated.
  - c. In one example, when M=mW and N=H (W and H are CTU size; M and N are the buffer size) and the previous updated area started from (kW, 0), the next starting position to update will be ((k+1)W mod M, 0).
- 33. The buffer can be reset at the beginning of each CTU row.
  - a. Alternatively, the buffer may be reset at the beginning of decoding each CTU.
  - b. Alternatively, the buffer may be reset at the beginning of decoding one tile.
  - c. Alternatively, the buffer may be reset at the beginning of decoding one tile group/picture.
- 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.
  - a. In one example, (x, y) is a position relative to the upper-left corner of a CTU.
- 35. When finishing coding a block relative to the picture, the buffer's corresponding area will be updated with reconstruction from the block.
  - a. In one example, the value at position (x mod M, y mod N) in the buffer may be updated with the reconstructed pixel value of position (x, y) relative to the upper-left corner of the picture.
  - b. In one example, the value at position (x mod M, y mod N) in the buffer may be updated with the reconstructed pixel value of position (x, y) relative to the upper-left corner of the current tile.
  - c. In one example, the value at position (x mod M, y mod N) in the buffer may be updated with the reconstructed pixel value of position (x, y) relative to the upper-left corner of the current CTU row.
  - d. In one example, the value in the buffer may be updated with the reconstructed pixel values after bit-depth alignment.
- 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
  - a. In one example, (x, y) is a position related to the upper-left corner of a CTU, and (xb, yb) is (x+update_x, y+update_y), wherein update_x and update_y point to a updatable position in the buffer.
- 37. For above examples, the reconstructed values of a block may indicate the reconstructed values before filters (e.g., deblocking filter) applied.
  - a. Alternatively, the reconstructed values of a block may indicate the reconstructed values after filters (e.g., deblocking filter) 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.
  - a. In one example, the buffer is updated with reconstructed sample value after bit-depth alignment to the bitdepth of the buffer.
  - b. In one example, the buffer value is updated according to the value {p+[1<<(b−1)]}>>b, where p is reconstructed sample value, b is a predefined bit-shifting value.
  - c. In one example, the buffer value is updated according to the value clip({p+[1<<(b−1)]}>>b, 0, (1<<bitdepth)−1), where p is reconstructed sample value, b is a predefined bit-shifting value, bitdepth is the buffer bit-depth.
  - d. In one example, the buffer value is updated according to the value {p+[1<<(b−1)−1]}>>b, where p is reconstructed sample value, b is a predefined bit-shifting value.
  - e. In one example, the buffer value is updated according to the value clip({p+[1<<(b−1)−1]}>>b, 0, (1<<bitdepth)−1), where p is reconstructed sample value, b is a predefined bit-shifting value, bitdepth is the buffer bit-depth.
  - f. In one example, the buffer value is updated according to the value p>>b.
  - g. In one example, the buffer value is updated according to the value clip(p>>b, 0, (1<<bitdepth)−1), where bitdepth is the buffer bit-depth.
  - h. In the above examples, b can be reconstructed bit-depth minus input sample bit-depth.
- 39. When use the buffer samples to form prediction, a preprocessing can be applied.
  - a. In one example, the prediction value is p<<b, where p is a sample value in the buffer, and b is a predefined value.
  - b. In one example, the prediction value is clip(p<<b, 0, 1<<bitdepth), where bitdepth is the bit-depth for reconstruction samples.
  - c. In one example, the prediction value is (p<<b)±(1<<(bitdepth−1)), where p is a sample value in the buffer, and b is a predefined value, bitdepth is the bit-depth for reconstruction samples.
  - d. In the above examples, b can be reconstructed bit-depth minus input sample bit-depth.
- 40. The buffer can be updated in a given order.
  - a. In one example, the buffer can be updated sequentially.
  - b. In one example, the buffer can be updated according to the order of blocks reconstructed.
- 41. When the buffer is full, the samples in the buffer can be replaced with latest reconstructed samples.
  - a. In one example, the samples can be updated in a first-in-first-out manor
  - b. In one example, the oldest samples will be replaced.
  - c. In one example, the samples can be assigned a priority and replaced according to the priority.
  - d. In one example, the samples can be marked as “long-term” so that other samples will be replaced first.
  - e. In one example, a flag can be sent along with a block to indicate a high priority.
  - f. In one example, a number can be sent along with a block to indicate priority.
  - g. In one example, samples from a reconstructed block with a certain characteristic will be assign a higher priority so that other samples will be replace first.
    - i. In one example, when the percentage of samples coded in IBC mode is larger than a threshold, all samples of the block can be assigned a high priority.
    - ii. In one example, when the percentage of samples coded in Palette mode is larger than a threshold, all samples of the block can be assigned a high priority.
    - iii. In one example, when the percentage of samples coded in IBC or Palette mode is larger than a threshold, all samples of the block can be assigned a high priority.
    - iv. In one example, when the percentage of samples coded in transform-skip mode is larger than a threshold, all samples of the block can be assigned a high priority.
    - v. The threshold can be different according to block-size, color component, CTU size.
    - vi. The threshold can be signalled in SPS/PPS/sequence header/slice header/Tile group/Tile level/a region.
  - h. In one example, that buffer is full may mean that the number of available samples in the buffer is equal or larger than a given threshold.
    - i. In one example, when the number of available samples in the buffer is equal or larger than 64×64×3 luma samples, the buffer may be determined as full.
      
      Alternative Buffer Combination
- 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 (or VPDU)'s location.
  - a. In one example, when coding/decoding a 64×64 block, previous 364×64 blocks can be used as reference. Compared to FIG. 2, more kinds of combination of previous 64×64 blocks can be applied. FIG. 2 shows an example of a different combination of previous 64×64 blocks.
- 43. Instead of using the z-scan order, vertical scan order may be utilized instead.
  - a. In one example, when one block is split into 4 VPDUs with index 0 . . . 3 in z-scan order, the encoding/decoding order is 0, 2, 1, 3.
  - b. In one example, when coding/decoding a 64×64 blocks, previous 364×64 blocks can be used as reference. Compared to FIG. 2, more kind of coding/decoding orders of 64×64 blocks can be applied. FIG. 4 shows an example of a different coding/decoding order of 64×64 blocks.
  - c. Alternatively, above methods may be applied only for screen content coding
  - d. Alternatively, above methods may be applied only when CPR is enabled for one tile/tile group/picture.
  - e. Alternatively, above methods may be applied only when CPR is enabled for one CTU or one CTU row.
    
    Virtual IBC Buffer

The following, the width and height of a VPDU is denoted as W_VPDU(e.g., 64) and H_VPDU(e.g., 64), respectively in luma samples. Alternatively, W_VPDUand/or H_VPDUmay denote the width and/or height of other video unit (e.g., CTU).

- 44. A virtual buffer may be maintained to keep track of the IBC reference region status.
  - a. In one example, the virtual buffer size is mWVPDU×nHVPDU.
    - i. In one example, m is equal to 3 and n is equal to 2.
    - ii. In one example, m and/or n may depend on the picture resolution, CTU sizes.
    - iii. In one example, m and/or n may be signaled or pre-defined.
  - b. In one example, the methods described in above bullets and sub-bullets may be applied to the virtual buffer.
  - c. In one example, a sample (x, y) relative to the upper-left corner of the picture/slice/tile/brick may be mapped to (x % (mW_VPDU), y % (nH_VPDU))
- 45. An array may be used to track the availability of each sample associated with the virtual buffer.
  - a. In one example, a flag may be associated with a sample in the virtual buffer to specify if the sample in the buffer can be used as IBC reference or not.
  - b. In one example, each 4×4 block containing luma and chroma samples may share a flag to indicate if any samples associated with that block can be used as IBC reference or not.
- 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.
  - a. In one example, which samples may be marked as unavailable depend on the position of the most recently decoded VPDU.
  - b. When one sample is marked unavailable, prediction from the sample is disallowed.
    - i. Alternatively, other ways (e.g., using default values) may be further applied to derive a predictor to replace the unavailable sample.
- 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.
  - a. In one example, at the beginning of decoding a VPDU, certain samples associated with the virtual buffer may be marked as unavailable according to the position of most recently decoded VPDU.
    - i. In one example, denote (xPrevVPDU, yPrevVPDU) as the upper-left position relative to the upper-left corner of the picture/slice/tile/brick/other video processing unit of most recently decoded VPDU, if yPrevVPDU % (nHVPDU) is equal to 0, certain positions (x, y) may be marked as unavailable.
      - 1. In one example, x may be within a range, such as [xPrevVPDU−2WVPDU+2mWVPDU) % mWVPDU, ((xPrevVPDU−2WVPDU+2mWVPDU) % mWVPDU)−1+WVPDU];
      - 2. In one example, y may be within a range, such as [yPrevVPDU % (nHVPDU), (yPrevVPDU % (nHVPDU))−1+HVPDU];
      - 3. In one example, x may be within a range, such as [xPrevVPDU−2WVPDU+2mWVPDU) % mWVPDU, ((xPrevVPDU−2WVPDU+2mWVPDU) % mWVPDU)−1+WVPDU] and y may be within a range, such as [yPrevVPDU % (nHVPDU), (yPrevVPDU % (nHVPDU))−1+HVPDU].
    - ii. In one example, denote (xPrevVPDU, yPrevVPDU) as the upper-left position relative to the upper-left corner of the picture/slice/tile/brick/other video processing unit of most recently decoded VPDU, if yPrevVPDU % (nHVPDU) is not equal to 0, certain positions (x, y) may be marked as unavailable.
      - 1. In one example, x may be within a range, such as [xPrevVPDU−WVPDU+2mWVPDU) % mWVPDU, ((xPrevVPDU-WVPDU+2mWVPDU) % mWVPDU)−1+WVPDU];
      - 2. In one example, y may be within a range, such as [yPrevVPDU % (nHVPDU), (yPrevVPDU % (nHVPDU))−1+HVPDU]
      - 3. In one example, x may be within a range, such as [xPrevVPDU−WVPDU+2mWVPDU) % mWVPDU, ((xPrevVPDU−WVPDU+2mWVPDU) % mWVPDU)−1+WVPDU] and y may be within a range, such as lyPrevVPDU % (nHVPDU), (yPrevVPDU % (nHVPDU))−1+HVPDUl.
- 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
  - a. In one example, at the beginning of decoding a CU containing multiple VPDUs, the IBC reference availability marking process may be applied for each VPDU before the VPDU within the CU is decoded.
  - b. In such a case, 128×64 and 64×128 IBC blocks may be disallowed.
    - i. In one example, pred_mode_ibc_flag for 128×64 and 64×128 CUs may not be sent and may be inferred to equal to 0.
- 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.
  - a. In one example, only the upper-left, bottom-left and bottom-right corner of a block/sub-block will be checked to tell if the block vector 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)
  - a. In one example, the height of the buffer may be equal to ctbSize.
  - b. In one example, the width of the buffer may depend on min(ctbSize, 64)
    - i. In one example, the width of the buffer may be (128*128/vSize, min(ctbSize, 64))
- 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.
  - a. A sample value may be set to a value which indicates the sample is unavailable.
  - b. In one example, the value may be −1.
  - c. In one example, the value may be any value outside of [0, 1<<(internal_bit_depth)−1] wherein internal_bit_depth is a positive integer value. For example, internal_bit_depth is the internal bitdepth used for encoding/decoding a sample for a color component.
  - d. In one example, the value may be any value outside of [0, 1<<(input_bit_depth)−1] wherein input_bit_depth is a positive integer value. For example, input_bit_depth is the input bitdepth used for encoding/decoding a sample for a color component.
- 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; ctbSize 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.
  - a. In one example, if (xCb % vSize) is equal to 0 and (yCb % vSize) is equal to 0, a certain set of positions in the IBC buffer may be marked as unavailable.
  - b. In one example, when the current block size is smaller than the VPDU size, i.e. min(ctbSize, 64), the region marked as unavailable may be according to the VPDU size.
  - c. In one example, when the current block size is larger than the VPDU size, i.e. min(ctbSize, 64), the region marked as unavailable may be according to the CU size.
- 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.
  - a. In one example, buffer samples with position (x % wIbcBuf, y % hIbcBuf) in the buffer, with x=xV, . . . , xV+ctbSize−1 and y=yV, . . . , yV+ctbSize−1, will be set to value −1. Where wIbcBuf and hIbcBuf are the IBC buffer width and height, ctbSize is the width of a CTU/CTB.
    - i. In one example, hIbcBuf may be equal to ctbSize.
- 54. A bitstream conformance constrain may be according to the value of a sample in the IBC buffer
  - a. In one example, if a reference block associate with a block vector in IBC buffer contains value outside of pixel range, the bitstream may be illegal.
- 55. A bitstream conformance constrain may be set according to the availability indication in the IBC buffer.
  - a. In one example, if any reference sample mapped in the IBC buffer is marked as unavailable for encoding/decoding a block, the bitstream may be illegal.
  - b. In one example, when singletree is used, if any luma reference sample mapped in the IBC buffer for encoding/decoding a block is marked as unavailable, the bitstream may be illegal.
  - c. A conformance bitstream may satisfy that for an IBC coded block, the associated block vector may point to a reference block mapped in the IBC buffer and each luma reference sample located in the IBC buffer for encoding/decoding a block shall be marked as available (e.g., the values of samples are within the range of [K0, K1] wherein for example, K0 is set to 0 and K1 is set to (1<<BitDepth−1) wherein BitDepth is the internal bit-depth or the input bit-depth).
- 56. Bitstream conformance constrains may depend on partitioning tree types and current CU's coding treeType
- a. In one example, if dualtree is allowed in high-level (e.g., slice/picture/brick/tile) and the current video block (e.g., CU/PU/CB/PB) is coded with single tree, bitstreams constrains may need to check if all components' positions mapped in the IBC buffer is marked as unavailable or not.
- b. In one example, if dualtree is allowed in high-level (e.g., slice/picture/brick/tile) and the current luma video block (e.g., CU/PU/CB/PB) is coded with dual tree, bitstreams constrains may neglect chroma components' positions mapped in the IBC buffer is marked as unavailable or not.
  - i. Alternatively, in such a case, bitstreams constrains may still check all components' positions mapped in the IBC buffer is marked as unavailable or not.
- c. In one example, if single tree is used, bitstreams constrains may neglect chroma components' positions mapped in the IBC buffer is marked as unavailable or not.
  
  Improvement to the Current VTM Design
- 57. The prediction for IBC can have a lower precision than the reconstruction.
  - a. In one example, the prediction value is according to the value clip{{p+[1<<(b−1)]}>>b,0,(1<<bitdepth)−1}<<b, where p is reconstructed sample value, b is a predefined bit-shifting value, bitdepth is prediction sample bit-bitdepth.
  - b. In one example, the prediction value is according to the value clip{{p+[1<<(b−1)−1]}>>b,0,(1<<bitdepth)−1}<<b, where p is reconstructed sample value, b is a predefined bit-shifting value.
  - c. In one example, the prediction value is according to the value ((p>>b)±(1<<(bitdepth−1)))<<b, where bitdepth is prediction sample bit-bitdepth.
  - d. In one example, the prediction value is according to the value (clip((p>>b),0,(1<<(bitdepth−b)))+(1<<(bitdepth−1)))<<b, where bitdepth is prediction sample bit-bitdepth.
  - e. In one example, the prediction value is clipped in different ways depending on whether ILR is applied or not.
  - f. In the above examples, b can be reconstructed bit-depth minus input sample bit-depth.
  - g. In one example, the bit-depth or the bit-depth difference compared to the output bit-depth/input bit-depth/internal bit-depth may be signalled in SPS/PPS/sequence header/picture header/slice header/Tile group header/Tile header or other kinds of video data units.
- 58. Part of the prediction of IBC can have a lower precision and the other part has the same precision as the reconstruction.
  - a. In one example, the allowed reference area may contain samples with different precisions (e.g., bit-depth).
  - b. In one example, reference from other 64×64 blocks than the current 64×64 block being decoded is of low precision and reference from the current 64×64 block has the same precision as the reconstruction.
  - c. In one example, reference from other CTUs than the current CTU being decoded is of low precision and reference from the current CTU has the same precision as the reconstruction.
  - d. In one example, reference from a certain set of color components is of low precision and reference from the other color components 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.
  - a. In one example, when reference area size is 128×128 and CTU size is 64×64, the nearest available 4 CTUs in a CTU row can be used for IBC reference.
  - b. In one example, when reference area size is 128×128 and CTU size is 32×32, the nearest available 16 CTUs in a CTU row can be used for IBC reference.
- 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.
  - a. In one example, when reference area size is 128×128 or 256×64 and CTU size is 64×64, the nearest available 3 CTUs in a CTU row can be used for IBC reference.
  - b. In one example, when reference area size is 128×128 or 512×32 and CTU size is 32×32, the nearest available 15 CTUs in a CTU row can be used for IBC reference.
- 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.
  - a. In one example, CTU size is 64×64, VPDU size is also 64×64, reference are size is 128×128, the nearest 3 CTUs in a CTU row can be used for IBC reference.
  - b. In one example, CTU size is 32×32, VPDU size is also 64×64, reference are size is 128×128, the nearest (16-4)=12 CTUs in a CTU row can be used for IBC reference.
- 62. For a w×h block with upper-left corner being (x, y) using IBC, there are constrains that keep reference block from certain area for memory reuse, wherein w and h are width and height of the current block.
  - a. In one example, when CTU size is 128×128 and (x, y)=(m×64,n×64), the reference block cannot overlap with the 64×64 region starting from ((m−2)×64, n×64).
  - b. In one example, when CTU size is 128×128, the reference block cannot overlap with the w×h block with upper-left corner being (x−128, y).
  - c. In one example, when CTU size is 128×128, (x+BVx, y+BVy) cannot be within the w*h block with upper-left corner being (x−128, y), where BVx and BVy denote the block vector for the current block.
  - d. In one example, when CTU size is M×M and IBC buffer size is k×M×M, reference block cannot overlap with the w×h block with upper-left corner being (x−k×M, y), where BVx and BVy denote the block vector for the current block.
  - e. In one example, when CTU size is M×M and IBC buffer size is k×M×M, (x+BVx, y+BVy) cannot be within the w×h block with upper-left corner being (x−k×M, y), where BVx and BVy denote the block vector for 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.
  - a. In one example, when reference area size is 128×128 and CTU size is 64×64, the nearest available 3 CTUs in a CTU row can be used for IBC reference.
  - b. In one example, when reference area size is 128×128 and CTU size is 32×32, the nearest available 15 CTUs in a CTU row can be used for IBC reference.
- 64. For a CU within a 64×64 block starting from (2m*64, 2n*64), i.e., a 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., a 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.
  - a. Alternatively, if the 64×64 block starting from (2m*64, (2n+1)*64) has been reconstructed, the 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*64, 2n*64), the 64×64 block starting from (2m*64, (2n+1)*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.
  - a. Alternatively, if the 64×64 block starting from ((2m+1)*64, 2n*64) has not been reconstructed, the 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.
- 68. It is proposed to adjust the reference area based on which 64×64 blocks the current CU belongs to.
  - a. In one example, for a CU starting from (x, y), when (y>>6)&1==0, two or up to two previous 64×64 blocks, starting from ((x>>6<<6)−128, y>>6<<6) and ((x>>6<<6)−64, y>>6<<6) can be referenced by IBC mode.
  - b. In one example, for a CU starting from (x, y), when (y>>6)&1==1, one previous 64×64 block, starting from ((x>>6<<6)−64, y>>6<<6) can be referenced by IBC mode.
- 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.
  - a. In one example, the block is a luma block.
  - b. In one example, the block is a chroma block in 4:4:4 format
  - c. In one example, the block contains both luma and chroma components
- 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.
  - a. For a block of component c starting from (x, y) and with block vector (BVx, BVy), if isRec(c, ((x+BVx)>>6<<6)+128−(((y+BVy)>>6)&1)*64+(x %64), ((y+BVy)>>6<<6)+(y %64)) is true, the block vector may be treated as invalid.
    - i. In one example, the block is a luma block (e.g., c is the luma component, or G component for RGB coding).
    - ii. In one example, the block is a chroma block in 4:4:4 format (e.g., c is the cb or cr component, or B/R component for RGB coding).
    - iii. In one example, availability of samples for both luma and chroma components may be checked, e.g., the block contains both luma and chroma components
  - b. For a chroma block in 4:2:0 format starting from (x, y) of component c and with block vector (BVx, BVy), if isRec(c, ((x+BVx)>>5<<5)+64−(((y+BVy)>>5)&1)*32+(x %32), ((y+BVy)>>5<<5)+(y %32)) is true, the block vector may be treated as invalid.
  - c. For a chroma block or sub-block starting from (x, y) of component c and with block vector (BVx, BVy), if isRec(c, x+BVx+Chroma_CTU_size, y) for a chroma component is true, the block vector may be treated as invalid, where Chroma_CTU_size is the CTU size for chroma component.
    - i. In one example, for 4:2:0 format, Chroma_CTU_size may be 64.
    - ii. In one example, a chroma sub-block may be a 2×2 block in 4:2:0 format.
    - iii. In one example, a chroma sub-block may be a 4×4 block in 4:4:4 format.
    - iv. In one example, a chroma sub-block may correspond to the minimal CU size in luma component.
      - 1. Alternatively, a chroma sub-block may correspond to the minimal CU size for the chroma component.
- 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.
  - a. In one example, if partial of the reference buffer is outside the current brick/tile/tile group/slice, the usage of IBC may be disabled. The signalling of IBC related syntax elements may be skipped.
  - b. Alternatively, if partial of the reference buffer is outside the current brick/tile/tile group/slice, IBC may be still enabled for one block, however, the block vector associated with one block may only point to the remaining reference buffer.
- 74. It is proposed to have K1 most recently coded VPDU, if available, in the 1^stVPDU row of the CTU/CTB row and K2 most recently coded VPDU, if available, in the 2^ndVPDU row of the CTU/CTB row as the reference area for IBC, excluding the current VPDU.
  - a. In one example, K1 is equal to 2 and K2 is equal to 1.
  - b. In one example, the above methods may be applied when the CTU/CTB size is 128×128 and VPDU size is 64×64.
  - c. In one example, the above methods may be applied when the CTU/CTB size is 64×64 and VPDU size is 64×64 and/or 32×32.
  - d. In one example, the above methods may be applied when the CTU/CTB size is 32×32 and VPDU size is 32×32 or smaller.
- 75. The above methods may be applied in different stages.
  - a. In one example, the module operation (e.g., a mod b) of block vectors (BVs) may be invoked in the availability check process of BVs to decide whether the BV is valid or not.
  - b. In one example, the module operation (e.g., a mod b) of block vectors (BVs) may be invoked to identify a reference sample's location (e.g., according to the module results of a current sample's location and BV) in the IBC virtual buffer or reconstructed picture buffer (e.g., before in-loop filtering process).

5. EMBODIMENTS
5.1 Embodiment #1

An implementation of the buffer for IBC is described below:

The buffer size is 128×128. CTU size is also 128×128. For coding of the 1^stCTU 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.

FIG. 3 shows an example of coding of a block starting from (x, y).

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.

5.2 Embodiment #2

FIG. 4 shows examples of possible alternative way to choose the previous coded 64×64 blocks.

5.3 Embodiment #3

FIG. 5 shows an example of a possible alternative way to change the coding/decoding order of 64×64 blocks.

5.4 Embodiment #4

FIG. 8 shows another possible alternative way to choose the previous coded 64×64 blocks, when the decoding order for 64×64 blocks is from top to bottom, left to right.

5.5 Embodiment #5

FIG. 9 shows another possible alternative way to choose the previous coded 64×64 blocks.

5.6 Embodiment #6

FIG. 11 shows another possible alternative way to choose the previous coded 64×64 blocks, when the decoding order for 64×64 blocks is from left to right, top to bottom.

5.7 Embodiment #7

Suppose that CTU size is W×W, an implementation of IBC buffer with size mW×W and bitdepth 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 wxh 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 bitdepth of the block may be equal to 10.

5.8 Embodiment #8

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.

5.9 Embodiment #9

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.

5.10 Embodiment #10

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.

5.11 Embodiment #11

This embodiment highlights an implementation of keeping two most coded VPDUs in the 1^stVPDU row and one most coded VPDU in the 2^ndVPDU 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 FIG. 13.

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 FIG. 14.

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 FIG. 15.

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.

5.12 Embodiment #12

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.

- 1) At the beginning of decoding a VPDU row, all positions of the buffer are marked as unavailable. (xPrevVPDU, yPrevVPDU) is set as (0,0).
- 2) At the beginning of decoding the 1st CU of a VPDU, positions (x, y) with x=(xPrevVPDU−2WVPDU+2mWVPDU) % (mWVPDU), ((xPrevVPDU−2WVPDU+2mWVPDU) % (mWVPDU))−1+WVPDU; and y=yPrevVPDU % (nHVPDU), (yPrevVPDU % (nHVPDU))−1+HVPDU may be marked as unavailable. Then (xPrevVPDU, yPrevVPDU) is set as (xCU, yCU), i.e. the upper-left position of the CU relative to the picture.
- 3) After decoding a CU, positions (x, y) with x=xCU % (mWVPDU), . . . , (xCU+CU_width−1)% (mWVPDU) and y=yCU % (nHVPDU), . . . , (yCU+CU_height−1)% (nHVPDU) are marked as available.
- 4) For an IBC CU with a block vector (xBV, yBV), if any position (x, y) with x=(xCU+xBV) % (mWVPDU), (xCU+xBV+CU_width−1)% (mWVPDU) and y=(yCU+yBV) % (nHVPDU), . . . , (yCU+yBV+CU_height−1)% (nHVPDU) is marked as unavailable, the block vector is considered as invalid.

FIG. 16 shows the buffer status along with the VPDU decoding status in the picture.

5.13 Embodiment #13

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© returns the largest integer no larger than c.

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.

- 1) At the beginning of decoding a VPDU row, all positions of the buffer are marked as unavailable. (xPrevVPDU, yPrevVPDU) is set as (0,0).
- 2) At the beginning of decoding the 1^stCU of a VPDU,
  - a. If yPrevVPDU %64 is equal to 0, positions (x, y) with x=(xPrevVPDU−128)%192, . . . , ((xPrevVPDU 128)%192)+63; and y=yPrevVPDU %128, (yPrevVPDU %128)+63, are marked as unavailable. Then (xPrevVPDU, yPrevVPDU) is set as (xCU, yCU), i.e. the upper-left position of the CU relative to the picture.
  - b. Otherwise, positions (x, y) with x=(xPrevVPDU 64)%192, . . . , ((xPrevVPDU−64)%192)+63; and y=yPrevVPDU %128, . . . , (yPrevVPDU %128)+63, are marked as unavailable. Then (xPrevVPDU, yPrevVPDU) is set as (xCU, yCU), i.e. the upper-left position of the CU relative to the picture.
- 3) After decoding a CU, positions (x, y) with x=xCU %192, . . . , (xCU+CU_width−1)%192 and y=yCU %128, . . . , (yCU+CU_height−1)%128 are marked as available.
- 4) For an IBC CU with a block vector (xBV, yBV), if any position (x, y) with x=(xCU+xBV) %192, . . . , (xCU+xBV+CU_width−1)%192 and y=(yCU+yBV) %128, . . . , (yCU+yBV+CU_height−1)%128 is marked as unavailable, the block vector is considered as invalid.

If CTU size is SxS, S is not equal to 128, let Wbuf be equal to 128*128/S. A virtual buffer with size WbufxS 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.

- 1) At the beginning of decoding a VPDU row, all positions of the buffer are marked as unavailable. (xPrevVPDU, yPrevVPDU) is set as (0,0).
- 2) At the beginning of decoding the 1^stCU of a VPDU, positions (x, y) with x=(xPrevVPDU−W_buf*S) % S, . . . , ((xPrevVPDU W_buf*S) % S)+S−1; and y=yPrevVPDU % S, . . . , (yPrevVPDU % S)+S−1; are marked as unavailable. Then (xPrevVPDU, yPrevVPDU) is set as (xCU, yCU), i.e. the upper-left position of the CU relative to the picture.
- 3) After decoding a CU, positions (x, y) with x=xCU % (W_buf), (xCU+CU_width−1)% (W_buf) and y=yCU % S, . . . , (yCU+CU_height−1)% S are marked as available.
- 4) For an IBC CU with a block vector (xBV, yBV), if any position (x, y) with x=(xCU+xBV) % (Wbuf), . . . , (xCU+xBV+CU_width−1)% (Wbuf) and y=(yCU+yBV) % S, . . . , (yCU+yBV+CU_height−1)% S is marked as unavailable, the block vector is considered as invalid.

5.14 Embodiment #14

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© 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.

- 1) At the beginning of decoding a VPDU row, all positions of the buffer are marked as unavailable. (xPrevVPDU, yPrevVPDU) is set as (0,0).
- 2) At the beginning of decoding the 1^stCU of a VPDU,
  - a. If yPrevVPDU %64 is equal to 0, positions (x, y) with x=(xPrevVPDU 128)%256, ((xPrevVPDU 128)% 256)+63; and y=yPrevVPDU %128, (yPrevVPDU %128)+63, are marked as unavailable. Then (xPrevVPDU, yPrevVPDU) is set as (xCU, yCU), i.e. the upper-left position of the CU relative to the picture.
  - b. Otherwise, positions (x, y) with x=(xPrevVPDU 64)% 256, . . . , ((xPrevVPDU 64)% 256)+63; and y=yPrevVPDU %128, (yPrevVPDU %128)+63, are marked as unavailable. Then (xPrevVPDU, yPrevVPDU) is set as (xCU, yCU), i.e. the upper-left position of the CU relative to the picture.
- 3) After decoding a CU, positions (x, y) with x=xCU %256, (xCU+CU_width−1)%256 and y=yCU %128, . . . , (yCU+CU_height−1)%128 are marked as available.
- 4) For an IBC CU with a block vector (xBV, yBV), if any position (x, y) with x=(xCU+xB V) %256, (xCU+xB V+CU_width−1)%256 and y=(yCU+yBV) %128, . . . , (yCU+yBV+CU_height−1)%128 is marked as unavailable, the block vector is considered as invalid.

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.

5.15 Embodiment #15

An IBC reference availability marking process is described as follows. The changes are indicated in bolded, underlined, italicized text in this document.

7.3.7.1 General Slice Data Syntax

slice_data( ) {
Descriptor

for( i = 0; i < NumBricksInCurrSlice; i++) {

CtbAddrInBs = FirstCtbAddrBs[ SliceBrickIdx[ i ] ]

for( j = 0; j < NumCtusInBrick[ SliceBrickIdx[ i ] ]; j++, CtbAddrInBs++

) {

if( ( j % BrickWidth[ SliceBrickIdx[ i ] ]) = = 0) {

NumHmvpCand = 0

NumHmvpIbcCand = 0

custom character

}

CtbAddrInRs = CtbAddrBsToRs[ CtbAddrInBs ]

......

Descriptor

custom character

BufWidth is equal to (CtbSizeY=128)?256:(128*128/CtbSizeY) and BufHeight is equal to CtbSizeY.

7.3.7.5 Coding Unit Syntax

coding_unit( x0, y0, cbWidth, cbHeight, treeType ) {
Descriptor

custom character

if( slice_type != I | | sps_ibc_enabled_flag ) {

if( treeType != DUAL_TREE_CHROMA &&

!( cbWidth = = 4 && cbHeight = = 4 && !sps_ibc_enabled_flag ) )

cu_skip_flag[ x0 ][ y0 ]
ae(v)

if( cu_skip_flag[ x0 ][ y0 ] = = 0 && slice_type != I

&& !( cbWidth = = 4 && cbHeight = = 4 ) )

pred_mode_flag
ae(v)

if( ( ( slice_type = = I && cu_skip_flag[ x0 ][ y0 ] = =0 ) | |

( slice_type != I && ( CuPredMode[ x0 ][ y0 ] != MODE_INTRA | |

( cbWidth = = 4 && cbHeight = = 4 && cu_skip_flag[ x0 ][ y0 ] = =

0 ) ) ) ) &&

sps_ibc_enabled_flag && ( cbWidth != 128 custom character

cbHeight != 128 ) )

pred_mode_ibc_flag
ae(v)

}

...

8.6.2 Derivation Process for Motion Vector Components for IBC Blocks

8.6.2.1 General

. . .

It is a requirement of bitstream conformance that when the block vector validity checking process in clause 8.6.3.2 is invoked with the block vector mvL, isBVvalid shall be true.

. . .

8.6.3 Decoding Process for Ibc Blocks

8.6.3.1 General

This process is invoked when decoding a coding unit coded in ibc prediction mode.

Inputs to this process are:

- a luma location (xCb, yCb) specifying the top-left sample of the current coding block relative to the top-left luma sample of the current picture,
- a variable cbWidth specifying the width of the current coding block in luma samples,
- a variable cbHeight specifying the height of the current coding block in luma samples,
- variables numSbX and numSbY specifying the number of luma coding subblocks in horizontal and vertical direction,
- the motion vectors mv[xSbIdx][ySbIdx] with xSbIdx=0 numSbX−1, and ySbIdx=0 numSbY−1,
- a variable cIdx specifying the colour component index of the current block.
- a (nIbcBufW)×(ctbSize) array ibcBuf

. . .

For each coding subblock at subblock index (xSbIdx, ySbIdx) with xSbIdx=0 numSbX−1, and ySbIdx=0 . . . numSbY−1, the following applies:

- The luma location (xSb, ySb) specifying the top-left sample of the current coding subblock relative to the top-left luma sample of the current picture is derived as follows:
  
  (xSb,ySb)=(xCb+xSbIdx*sbWidth,yCb+ySbIdx*sbHeight) (8-913)

If cIdx is equal to 0, nIbcBufW is set to ibcBufferWidth, otherwise nIbcBufW is set to (ibcBufferWidth/SubWidthC). The foiling applies:

predSamples[xSb+x][ySb+y]=ibcBuf[(xSb+x+(mv[xSb][ySb][0]>>4))% nIbcRefW][ySb+y+(mv[xSb][ySb][1]>>4)]

- with x=0 . . . sbWidth−1 and y=0 . . . sbHeight−1.
- . . .
  
  8.6.3.2 Block Vector Validity Checking Process

Inputs to this process are:

- a luma location (xCb, yCb) specifying the top-left sample of the current coding block relative to the top-left luma sample of the current picture,
- a variable cbWidth specifying the width of the current coding block in luma samples,
- a variable cbHeight specifying the height of the current coding block in lama samples,
- variables numSbX and numSbY specifying the number of lama coding subblocks in horizontal and vertical direction,
- the block vectors mv[xSbIdx][ySbIdx] with xSbIdx=0 . . . numSbX−1, and ySbIdx=0 . . . numSbY−1,
- a variable cIdx specifying the colour component index of the current block.
- a (nIbcBufW)×(ctbSize) array ibcBuf

Outputs of this process is a flag isBVvalid to indicate if the block vector is valid or not.

The following applies

- 1. isBVvalid is set mod to true.
- 2. If ((yCb & (ctbSize−1))+mv[0][0][1]+cbHeizht)>ctbSize, isBVvalid is set mod to false.
- 3. Otherwise, for each subblock index xSbIdx, ySbIdx with xSbIdx=0 . . . numSbX−1, and ySbIdx=0 . . . numSbY−1, its position relative to the top-left lama sample of the ibcBuf is derived:
  
  xTL=(xCb+xSbIdx*sbWidth+mv[xSbIdx][ySbIdx][0]) & (nIbcBufW−1)
  yTL=(yCb & (ctbSize−1))+ySbIdx*sbHeight+mv[xSbIdx][ySbIdx][1]
  xBR=(xCb+xSbIdx*sbWidth+sbWidth−1+mv[xSbIdx][ySbIdx][0]) & (nIbcBufW−1)
  yBR=(yCb & (ctbSize−1))+ySbIdx*sbHeight+sbHeight−1+mv[xSbIdx][ySbIdx][1]

if (isDecoded[xTL>>2][yTL>>2]==0) or (isDecoded[xBR>>2][yTL>>2]==0) or (isDecoded[xBR>>2][yBR>>2]==0), isBVvalid is set aural to false.

8.7.5 Picture Reconstruction Process

8.7.5.1 General

Inputs to this process are:

- a location (xCurr, yCurr) specifying the top-left sample of the current block relative to the top-left sample of the current picture component,
- the variables nCurrSw and nCurrSh specifying the width and height, respectively, of the current block,
- a variable cIdx specifying the colour component of the current block,
- an (nCurrSw)×(nCurrSh) array predSamples specifying the predicted samples of the current block,
- an (nCurrSw)×(nCurrSh) array resSamples specifying the residual samples of the current block.

Output of this process are

- a reconstructed picture sample array recSamples.
- an IBC reference array ibcBuf
- . . .

Denote nIbcBufW as the width of ibcBuf, the following applies:

ibcBuf[(xCurr+i) & (nIbcBufW−1)][(yCurr+j) & (ctbSize−1)]=recSamples[xCurr+i][yCurr+j]

- with i=0 . . . nCurrSw−1, i=0 . . . nCurrSh−1.

5.16 Embodiment #16

This is identical to the previous embodiment except for the following changes

slice_data( ) {
Descriptor

for( i = 0; i < NumBricksInCurrSlice; i++ ) {

CtbAddrInBs = FirstCtbAddrBs[ SliceBrickIdx[ i ] ]

for( j = 0; j < NumCtusInBrick[ SliceBrickIdx[ i ] ]; j++, CtbAddrInBs++

) {

if( ( j % BrickWidth[ SliceBrickIdx[ i ] ] ) = = 0 ) {

NumHmvpCand = 0

NumHmvpIbcCand = 0

custom character

}

CtbAddrInRs = CtbAddrBsToRs[ CtbAddrInBs ]

......

reset ibc isDecoded(x0, y0, w, h, BufWidth, BufHeight) {
Descriptor

if( x0 >=0)

for (x = x0 % BufWidth; x < x0 + w; x+=4)

for (y = y0 % BufHeight; y < y0 + h; y+=4)

isDecoded[ x >>2 ][y >> 2 ] = 0

}

BufWidth is equal to (CtbSizeY==128)?192:(128*128/CtbSizeY) and BufHeight is equal to CtbSizeY.

5.17 Embodiment #17

The changes in some examples are indicated in bolded, underlined, text in this document.

7.3.7 Slice Data Syntax

7.3.7.1 General Slice Data Syntax

slice_data( ) {
Descriptor

for( i = 0; i < NumBricksInCurrSlice; i++ ) {

CtbAddrInBs = FirstCtbAddrBs[ SliceBrickIdx[ i ] ]

for( j = 0; j < NumCtusInBrick[ SliceBrickIdx[ i ] ]; j++, CtbAddrInBs++ )

{

if( ( j % BrickWidth[ SliceBrickIdx[ i ] ] ) = = 0 ) {

NumHmvpCand = 0

NumHmvpIbcCand = 0

custom character

}

CtbAddrInRs = CtbAddrBsToRs[ CtbAddrInBs ]

coding_tree_unit( )

if( entropy_coding_sync_enabled_flag &&

( ( j + 1 ) % BrickWidth[ SliceBrickIdx[ i ] ] = = 0 ) ) {

end_of_subset_one_bit /* equal to 1 */
ae(v)

if( j < NumCtusInBrick[ SliceBrickIdx[ i ] ] − 1 )

byte_alignment( )

}

}

if( !entropy_coding_sync_enabled_flag ) {

end_of_brick_one_bit /* equal to 1 */
ae(v)

if( i < NumBricksInCurrSlice −1 )

byte_alignment( )

}

}

}

7.4.8.5 Coding Unit Semantics

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:

- IsInSmr[x0][y0] is equal to TRUE.
- SmrX[x0][y0] is equal to x0.
- SmrY[x0][y0] is equal to y0.

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)

Set vSize as min(ctbSize, 64) and wIbcBuf as (128*128/ctbSize). The width and height of ibcBuf is wIbcBuf and ctbSize accordingly.

If refreshIbcBuf is equal to 1, the following applies

- ibcBuf[x % wIbcBuf][y % ctbSize]=−1, for x=x0 . . . x0+wIbcBuf−1 and y=y0 . . . y0+ctbSize−1
- resetIbcBuf=0

When (x0% vSize) is equal to 0 and (y0% vSize) is equal to 0, for x=x0 . . . x0+vSize−1 and y=y0 . . . y0+vSize−1, the following applies

- ibcBuf[x % wIbcBuf][y % ctbSize]=−1
  
  8.6.2 Derivation Process for Motion Vector Components for IBC Blocks
  
  8.6.2.1 General

Inputs to this process are:

- a luma location (xCb, yCb) of the top-left sample of the current luma coding block relative to the top-left luma sample of the current picture,
- a variable cbWidth specifying the width of the current coding block in luma samples,
- a variable cbHeight specifying the height of the current coding block in luma samples.

Outputs of this process are:

- the luma motion vector in 1/16 fractional-sample accuracy mvL.

The luma motion vector mvL is derived as follows:

- The derivation process for IBC luma motion vector prediction as specified in clause 8.6.2.2 is invoked with the luma location (xCb, yCb), the variables cbWidth and cbHeight inputs, and the output being the luma motion vector mvL.
- When general_merge_flag[xCb][yCb] is equal to 0, the following applies:
  - 1. The variable mvd is derived as follows:
    
    mvd[0]=MvdL0[xCb][yCb][0] (8-883)
    mvd[1]=MvdL0[xCb][yCb][1] (8-884)
  - 2. The rounding process for motion vectors as specified in clause 8.5.2.14 is invoked with mvX set equal to mvL, rightShift set equal to MvShift+2, and leftShift set equal to MvShift+2 as inputs and the rounded mvL as output.
  - 3. The luma motion vector mvL is modified as follows:
    
    u[0]=(mvL[0]+mvd[0]+2¹⁸)% 2¹⁸ (8-885)
    mvL[0]=(u[0]>=2¹⁷)?(u[0]−2¹⁸):u[0] (8-886)
    u[1]=(mvL[1]+mvd[1]+2¹⁸)%2¹⁸ (8-887)
    mvL[1]=(u[1]>=2¹⁷)?(u[1]−2¹⁸):u[1] (8-888)
    - NOTE 1 The resulting values of mvL[0] and mvL[1] as specified above will always be in the range of −2¹⁷to 2¹⁷−1, inclusive.

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.

It is a requirement of bitstream conformance that the luma block vector mvL shall obey the following constraints:

((yCb+(mvL[1]>>4))% wIbcBuf)+cbHeight is less than or equal to ctbSize

For x=xCb . . . xCb+cbWidth−1 and y=yCb . . . yCb+cbHeight−1, ibcBuff[(x+(myL[0]>>4))% wIbcBuf][(y+(mvL[1]>>4))% ctbSize] shall not be equal to −1.

8.7.5 Picture Reconstruction Process

8.7.5.1 General

Inputs to this process are:

- a location (xCurr, yCurr) specifying the top-left sample of the current block relative to the top-left sample of the current picture component,
- the variables nCurrSw and nCurrSh specifying the width and height, respectively, of the current block,
- a variable cIdx specifying the colour component of the current block,
- an (nCurrSw)×(nCurrSh) array predSamples specifying the predicted samples of the current block,
- an (nCurrSw)×(nCurrSh) array resSamples specifying the residual samples of the current block.

Output of this process are a reconstructed picture sample array recSamples and an IBC buffer array ibcBuf.

Depending on the value of the colour component cIdx, the following assignments are made:

- If cIdx is equal to 0, recSamples corresponds to the reconstructed picture sample array S_Land the function clipCidx1 corresponds to Clip1_Y.
- Otherwise, if cIdx is equal to 1, tuCbfChroma is set equal to tu_cbf_cb[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S_Cband the function clipCidx1 corresponds to Clip1_C.
- Otherwise (cIdx is equal to 2), tuCbfChroma is set equal to tu_cbf_cr[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S_Crand the function clipCidx1 corresponds to Clip1_C.

Depending on the value of slice_lmcs_enabled_flag, the following applies:

- If slice_lmcs_enabled_flag is equal to 0, the (nCurrSw)×(nCurrSh) block of the reconstructed samples recSamples at location (xCurr, yCurr) is derived as follows for i=0 . . . nCurrSw 1, j=0 . . . nCurrSh−1:
  
  recSamples[xCurr+i][yCurr+j]=clipCidx1(predSamples[i][j]+resSamples[i][j]) (8-992)
- Otherwise (slice_lmcs_enabled_flag is equal to 1), the following applies:
  - If cIdx is equal to 0, the following applies:
    - The picture reconstruction with mapping process for luma samples as specified in clause 8.7.5.2 is invoked with the luma location (xCurr, yCurr), the block width nCurrSw and height nCurrSh, the predicted luma sample array predSamples, and the residual luma sample array resSamples as inputs, and the output is the reconstructed luma sample array recSamples.
  - Otherwise (cIdx is greater than 0), the picture reconstruction with luma dependent chroma residual scaling process for chroma samples as specified in clause 8.7.5.3 is invoked with the chroma location (xCurr, yCurr), the transform block width nCurrSw and height nCurrSh, the coded block flag of the current chroma transform block tuCbfChroma, the predicted chroma sample array predSamples, and the residual chroma sample array resSamples as inputs, and the output is the reconstructed chroma sample array recSamples.

After decoding the current coding unit, the following applies:

ibcBuf[(xCurr+i) % wIbcBuf][yCurr+j) % ctbSize]=recSamples[xCurr+i][yCurr+j]

for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1.

5.18 Embodiment #18

The changes in some examples are indicated in bolded, underlined, italicized text in this document.

7.3.7 Slice Data Syntax

7.3.7.1 General Slice Data Syntax

slice_data( ) {
Descriptor

for( i = 0; i < NumBricksInCurrSlice; i++ ) {

CtbAddrInBs = FirstCtbAddrBs[ SliceBrickIdx[ i ] ]

for( j = 0; j < NumCtusInBrick[ SliceBrickIdx[ i ] ]; j++, CtbAddrInBs++

) {

if( ( j % BrickWidth[ SliceBrickIdx[ i ] ]) = = 0 ) {

NumHmvpCand = 0

NumHmvpIbcCand = 0

custom character

7.4.8.5 Coding Unit Semantics

- IsInSmr[x0][y0] is equal to TRUE.
- SmrX[x0][y0] is equal to x0.
- SmrY[x0][y0] is equal to y0.

Set vSize as min(ctbSize, 64) and wIbcBufY as (128*128/CtbSizeY).

ibcBuf_Lis a array with width being wIbcBufY and height being CtbSizeY.

ibcBuf_Cband ibcBuf_Crare arrays with width being wIbcBufC=(wIbcBufY/SubWidthC) and height being (CtbSizeY/SubHeightC), i.e. CtbSizeC.

If resetIbcBuf is equal to 1, the following applies

ibcBuf_L[x% wIbcBufY][y% CtbSizeY]=−1, for x=x0 . . . x0+wIbcBufY−1 and y=y0 . . . y0+CtbSizeY−1
ibcBuf_Cr[x% wIbcBufC][y% CtbSizeC]=−1, for x=x0 . . . x0+wIbcBufC−1 and y=y0 . . . y0+CtbSizeC−1
ibcBuf_Cr[x% wIbcBufC][y% CtbSizeC]=−1, for x=x0 . . . x0+wIbcBufC−1 and y=y0 . . . y0+CtbSizeC−1

- resetIbcBuf=0

When (x0% vSizeY) is equal to 0 and (y0% vSizeY) is equal to 0, the following applies

ibcBuf_L[x% wIbcBufY][y% CtbSizeY]=−1, for x=x0 . . . x0+vSize−1 and y=y0 . . . y0+vSize−1
ibcBuf_Cb[x% wIbcBufC][y% CtbSizeC]=−1, for x=x0/SubWidthC . . . x0/SubWidthC+vSize/SubWidthC−1 and y=y0/SubHeightC . . . y0/SubHeightC+vSize/SubHeightC−1
ibcBuf_Cr[x% wIbcBufC][y% CtbSizeC]=−1, for x=x0/SubWidthC . . . x0/SubWidthC+vSize/SubWidthC−1 and y=y0/SubHeightC . . . y0/SubHeightC+vSize/SubHeightC−1

8.6.2 Derivation Process for Motion Vector Components for IBC Blocks

8.6.2.1 General

Inputs to this process are:

- a luma location (xCb, yCb) of the top-left sample of the current luma coding block relative to the top-left luma sample of the current picture,
- a variable cbWidth specifying the width of the current coding block in luma samples,
- a variable cbHeight specifying the height of the current coding block in luma samples.

Outputs of this process are:

- the luma motion vector in 1/16 fractional-sample accuracy mvL.

The luma motion vector mvL is derived as follows:

- The derivation process for IBC luma motion vector prediction as specified in clause 8.6.2.2 is invoked with the luma location (xCb, yCb), the variables cbWidth and cbHeight inputs, and the output being the luma motion vector mvL.
- When general_merge_flag[xCb][yCb] is equal to 0, the following applies:
  - 4. The variable mvd is derived as follows:
    
    mvd[0]=MvdL0[xCb][yCb][0] (8-883)
    mvd[1]=MvdL0[xCb][yCb][1] (8-884)
  - 5. The rounding process for motion vectors as specified in clause 8.5.2.14 is invoked with mvX set equal to mvL, rightShift set equal to MvShift+2, and leftShift set equal to MvShift+2 as inputs and the rounded mvL as output.
  - 6. The luma motion vector mvL is modified as follows:
    
    u[0]=(mvL[0]+mvd[0]+2¹⁸)% 2¹⁸ (8-885)
    mvL[0]=(u[0]>=2¹⁷)?(u[0]−2¹⁸): u[0] (8-886)
    u[1]=(mvL[1]+mvd[1]+2¹⁸)% 2¹⁸ (8-887)
    mvL[1]=(u[1]>=2¹⁷)?(u[1]−2¹⁸): u[1] (8-888)
    - NOTE 1—The resulting values of mvL[0] and mvL[1] as specified above will always be in the range of −2¹⁷to 2¹⁷−1, inclusive.

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.

Clause 8.6.2.5 is invoked with mvL as input and mvC as output.

It is a requirement of bitstream conformance that the luma block vector mvL shall obey the following constraints:

((yCb+(mvL[1]>>4))% CtbSizeY)+cbHeight is less than or equal to CtbSizeY

- For x=xCb . . . xCb+cbWidth−1 and y=yCb . . . vCb+cbHeight−1, ibcBuf_L[(x+(myL[0]>>4))% wIbcBufY][(y+(mYL[1]>>4))% CtbSizeY] shall not be equal to −1.
- If treeType is equal to SINGLE_TREE, for x=xCb . . . xCb+cbWidth−1 and y=yCb . . . vCb+cbHeight−1, ibcBuf_Cb[(x+(myC[0]>>5))% wIbcBufC][(y+(mvC[1]>>5))% CtbSizeC]] shall not be equal to −1.
  
  8.6.3 Decoding Process for Ibc Blocks
  
  8.6.3.1 General

This process is invoked when decoding a coding unit coded in ibc prediction mode.

Inputs to this process are:

- a luma location (xCb, yCb) specifying the top-left sample of the current coding block relative to the top-left luma sample of the current picture,
- a variable cbWidth specifying the width of the current coding block in luma samples,
- a variable cbHeight specifying the height of the current coding block in luma samples,
- colour component index of the current block.
- the motion vector my,
- an (wIbcBufY)×(CtbSizeY) array ibcBuf_L, an (wIbcBufC)×(CtbSizeC) array ibcBuf_Cb, an (wIbcBufC)×(CtbSizeC) array ibcBuf_Cr.

Outputs of this process are:

- an array predSamples of prediction samples.

For x=xCb . . . xCb+Width−1 and y=yCb . . . yCb+Height−1, the following applies

If cIdx is qual to 0

predSamples[x][y]=ibcBuf_L[(x+mv[0]>>4))% wIbcBufY][(y+(mv[1]>>4))% CtbSizeY]

if cIdx is equal to 1

predSamples[x][y]=ibcBuf_Cb[(x+mv[0]>>5))% wIbcBufC][(y+(mv[1]>>5))% CtbSizeC]

if cIdx is equal to 2

predSamples[x][y]=ibcBuf_Cr[(x+mv[0]>>5))% wIbcBufC][(y+(mv[1]>>5))% CtbSizeC]

8.7.5 Picture Reconstruction Process

8.7.5.1 General

Inputs to this process are:

- a location (xCurr, yCurr) specifying the top-left sample of the current block relative to the top-left sample of the current picture component,
- the variables nCurrSw and nCurrSh specifying the width and height, respectively, of the current block,
- a variable cIdx specifying the colour component of the current block,
- an (nCurrSw)×(nCurrSh) array predSamples specifying the predicted samples of the current block,
- an (nCurrSw)×(nCurrSh) array resSamples specifying the residual samples of the current block.

Output of this process are a reconstructed picture sample array recSamples and IBC buffer arrays ibcBuf_L, ibcBuf_Cb, ibcBuf_Cr.

Depending on the value of the colour component cIdx, the following assignments are made:

- If cIdx is equal to 0, recSamples corresponds to the reconstructed picture sample array S_Land the function clipCidx1 corresponds to Clip1_Y.
- Otherwise, if cIdx is equal to 1, tuCbfChroma is set equal to tu_cbf_cb[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S_Cband the function clipCidx1 corresponds to Clip1_C.
- Otherwise (cIdx is equal to 2), tuCbfChroma is set equal to tu_cbf_cr[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S_Crand the function clipCidx1 corresponds to Clip1_C.

Depending on the value of slice_lmcs_enabled_flag, the following applies:

- If slice_lmcs_enabled_flag is equal to 0, the (nCurrSw)×(nCurrSh) block of the reconstructed samples recSamples at location (xCurr, yCurr) is derived as follows for i=0 . . . nCurrSw 1, j=0 . . . nCurrSh−1:
  
  recSamples[xCurr+i][yCurr+j]=clipCidx1(predSamples[i][j]+resSamples[i][j]) (8-992)
- Otherwise (slice_lmcs_enabled_flag is equal to 1), the following applies:
  - If cIdx is equal to 0, the following applies:
    - The picture reconstruction with mapping process for luma samples as specified in clause 8.7.5.2 is invoked with the luma location (xCurr, yCurr), the block width nCurrSw and height nCurrSh, the predicted luma sample array predSamples, and the residual luma sample array resSamples as inputs, and the output is the reconstructed luma sample array recSamples.
  - Otherwise (cIdx is greater than 0), the picture reconstruction with luma dependent chroma residual scaling process for chroma samples as specified in clause 8.7.5.3 is invoked with the chroma location (xCurr, yCurr), the transform block width nCurrSw and height nCurrSh, the coded block flag of the current chroma transform block tuCbfChroma, the predicted chroma sample array predSamples, and the residual chroma sample array resSamples as inputs, and the output is the reconstructed chroma sample array recSamples.

After decoding the current coding unit, the following may apply:

If cIdx is equal to 0, and if treeType is equal to SINGLE_TREE or DUAL_TREE_LUMA, the following applies

ibcBuf_L[(xCurr+i) % wIbcBufY][(yCurr+j) % CtbSizeY]=recSamples[xCurr+i][yCurr+j]

- for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1.

If cIdx is equal to 1, and if treeType is equal to SINGLE_TREE or DUAL_TREE_CHROMA, the following applies

ibcBuf_Cb[(xCurr+i) % wIbcBufC][(yCurr+j) % CtbSizeC]=recSamples[xCurr+i][yCurr+j]

- for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1.

If cIdx is equal to 2, and if treeType is equal to SINGLE_TREE or DUAL_TREE_CHROMA, the following applies

ibcBuf_Cr[(xCurr+i) % wIbcBufC][(yCurr+j) % CtbSizeC]=recSamples[xCurr+i][yCurr+i]

- for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1.

5.19 Embodiment #19

The changes in some examples are indicated in bolded, underlined, text in this document.

7.3.7 Slice Data Syntax

7.3.7.1 General Slice Data Syntax

slice_data( ) {
Descriptor

for( i = 0; i < NumBricksInCurrSlice; i++ ) {

CtbAddrInBs = FirstCtbAddrBs[ SliceBrickIdx[ i ] ]

for( j = 0; j < NumCtusInBrick[ SliceBrickIdx[ i ] ]; j++, CtbAddrInBs++

) {

if( ( j % BrickWidth[ SliceBrickIdx[ i ] ] ) = = 0 ) {

NumHmvpCand = 0

NumHmvpIbcCand = 0

custom character

7.4.8.5 Coding Unit Semantics

IsInSmr[x0][y0] is equal to TRUE.

SmrX[x0][y0] is equal to x0.

SmrY[x0][y0] is equal to y0.

Set vSize as min(ctbSize, 64) and wIbcBufY as (128*128/CtbSizeY).

ibcBuf_Lis a array with width being wIbcBufY and height being CtbSizeY.

ibcBuf_Cband ibcBuf_Crare arrays with width being wIbcBufC=(wIbcBufY/SubWidthC) and height (CtbSizeY/SubHeightC), i.e. CtbSizeC.

If resetIbcBuf is equal to 1, the following applies

ibcBuf_L[x% wIbcBufY][y% CtbSizeY]=−1, for x=x0 . . . x0+wIbcBufY−1 and y=y0 . . . y0+CtbSizeY−1
ibcBuf_Cb[x% wIbcBufC][y% CtbSizeC]=−1, for x=x0 . . . x0+wIbcBufC−1 and y=y0 . . . y0+CtbSizeC−1
ibcBuf_Cr[x% wIbcBufC][y% CtbSizeC]=−1, for x=x0 . . . x0+wIbcBufC−1 and y=y0 . . . y0+CtbSizeC−1

- resetIbcBuf=0

When (x0% vSizeY) is equal to 0 and (v0% vSizeY) is equal to 0, the following applies

ibcBuf_L[x% wIbcBufY][y% CtbSizeY]=−1, for x=x0 . . . x0+min(vSize,cbWidth)−1 and y=y0 . . . v0+min(vSize,cbHeight)−1
ibcBuf_Cb[x% wIbcBufC][y% CtbSizeC]=−1, for x=x0/SubWidthC . . . x0/SubWidthC+min(vSize/SubWidthC, cbWidth)−1 and
y=y0/SubHeightC . . . y0/SubHeightC+min(vSize/SubHeightC,cbHeight)−1
ibcBuf_Cr[x% wIbcBufC][y% CtbSizeC]=−1, for x=x0/SubWidthC . . . x0/SubWidthC+min(vSize/SubWidthC,cbWidth)−1 and
y=y0/SubHeightC . . . y0/SubHeightC+min(vSize/SubHeightC,cbHeight)−1

8.6.2 Derivation Process for Motion Vector Components for IBC Blocks

8.6.2.1 General

Inputs to this process are:

- a luma location (xCb, yCb) of the top-left sample of the current luma coding block relative to the top-left luma sample of the current picture,
- a variable cbWidth specifying the width of the current coding block in luma samples,
- a variable cbHeight specifying the height of the current coding block in luma samples.

Outputs of this process are:

- the luma motion vector in 1/16 fractional-sample accuracy mvL.

The luma motion vector mvL is derived as follows:

- The derivation process for IBC luma motion vector prediction as specified in clause 8.6.2.2 is invoked with the luma location (xCb, yCb), the variables cbWidth and cbHeight inputs, and the output being the luma motion vector mvL.
- When general_merge_flag[xCb][yCb] is equal to 0, the following applies:
  - 7. The variable mvd is derived as follows:
    
    mvd[0]=MvdL0[xCb][yCb][0] (8-883)
    mvd[1]=MvdL0[xCb][yCb][1] (8-884)
- 8. The rounding process for motion vectors as specified in clause 8.5.2.14 is invoked with mvX set equal to mvL, rightShift set equal to MvShift+2, and leftShift set equal to MvShift+2 as inputs and the rounded mvL as output.
- 9. The luma motion vector mvL is modified as follows:
  
  u[0]=(mvL[0]+mvd[0]+2¹⁸)% 2¹⁸ (8-885)
  mvL[0]=(u[0]>=2¹⁷)?(u[0]−2¹⁸): u[0] (8-886)
  u[1]=(mvL[1]+mvd[1]+2¹⁸)% 2¹⁸ (8-887)
  mvL[1]=(u[1]>=2¹⁷)?(u[1]−2¹⁸): u[1] (8-888)
  - NOTE 1 The resulting values of mvL[0] and mvL[1] as specified above will always be in the range of −2¹⁷to 2¹⁷−1, inclusive.

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.

Clause 8.6.2.5 is invoked with mvL as input and mvC as output.

It is a requirement of bitstream conformance that the luma block vector mvL shall obey the following constraints:

((yCb+(mvL[1]>>4))% CtbSizeY)+cbHeight is less than or equal to CtbSizeY

- For x=xCb . . . xCb+cbWidth−1 and y=yCb . . . yCb+cbHeight−1, ibcBuf_L[(x+(myL[0]>>4))% wIbcBufY][(y+(mvL[1]>>4))% CtbSizeY] shall not be equal to −1.
- If treeType is equal to SINGLE_TREE, for x=xCb . . . xCb+cbWidth−1 and y=yCb . . . yCb+cbHeight−1, ibcBuf_Cb[(x+(myC[0]>>5))% wIbcBufC][(y+(mvC[1]>>5))% CtbSizeC]] shall not be equal to −1.
  
  8.6.3 Decoding Process for Ibc Blocks
  
  8.6.3.1 General

This process is invoked when decoding a coding unit coded in ibc prediction mode.

Inputs to this process are:

- a luma location (xCb, yCb) specifying the top-left sample of the current coding block relative to the top-left luma sample of the current picture,
- a variable cbWidth specifying the width of the current coding block in luma samples,
- a variable cbHeight specifying the height of the current coding block in luma samples,
- a variable cIdx specifying the colour component index of the current block.
- the motion vector my,
- an (wIbcBufY)×(CtbSizeY) array ibcBuf_L, an (wIbcBufC)×(CtbSizeC) array ibcBuf_Cb, an (wIbcBufC)×(CtbSizeC) array ibcBuf_Cr.

Outputs of this process are:

- an array predSamples of prediction samples.

For x=xCb . . . xCb+Width−1 and y=yCb . . . yCb+Height−1, the following applies

If cIdx is qual to 0

predSamples[x][y]=ibcBuf_L[(x+mv[0]>>4))% wIbcBufY][(y+(mv[1]>>4))% CtbSizeY]

if cIdx is equal to 1

predSamples[x][y]=ibcBuf_Cb(x+mv[0]>>5))% wIhcBufC][(y+(mv[1]>>5))% CtbSizeC]

if cIdx is equal to 2

predSamples[x][y]=ibcBuf_Cr[(x+mv[0]>>5))% wThcBufC][(y+(mv[1]>>5))% CtbSizeC]

8.7.5 Picture Reconstruction Process

8.7.5.1 General

Inputs to this process are:

- a location (xCurr, yCurr) specifying the top-left sample of the current block relative to the top-left sample of the current picture component,
- the variables nCurrSw and nCurrSh specifying the width and height, respectively, of the current block,
- a variable cIdx specifying the colour component of the current block,
- an (nCurrSw)×(nCurrSh) array predSamples specifying the predicted samples of the current block,
- an (nCurrSw)×(nCurrSh) array resSamples specifying the residual samples of the current block.

Output of this process are a reconstructed picture sample array recSamples and IBC buffer arrays ibcBuf_L, ibcBuf_Cb, ibcBuf_Cr.

Depending on the value of the colour component cIdx, the following assignments are made:

- If cIdx is equal to 0, recSamples corresponds to the reconstructed picture sample array S_Land the function clipCidx1 corresponds to Clip1_Y.
- Otherwise, if cIdx is equal to 1, tuCbfChroma is set equal to tu_cbf_cb[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S_Cband the function clipCidx1 corresponds to Clip1_C.
- Otherwise (cIdx is equal to 2), tuCbfChroma is set equal to tu_cbf_cr[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S_Crand the function clipCidx1 corresponds to Clip1_C.

Depending on the value of slice_lmcs_enabled_flag, the following applies:

- If slice_lmcs_enabled_flag is equal to 0, the (nCurrSw)×(nCurrSh) block of the reconstructed samples recSamples at location (xCurr, yCurr) is derived as follows for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1:
  
  recSamples[xCurr+i][yCurr+j]=clipCidx1(predSamples[i][j]+resSamples[i][j]) (8-992)
- Otherwise (slice_lmcs_enabled_flag is equal to 1), the following applies:
  - If cIdx is equal to 0, the following applies:
    - The picture reconstruction with mapping process for luma samples as specified in clause 8.7.5.2 is invoked with the luma location (xCurr, yCurr), the block width nCurrSw and height nCurrSh, the predicted luma sample array predSamples, and the residual luma sample array resSamples as inputs, and the output is the reconstructed luma sample array recSamples.
  - Otherwise (cIdx is greater than 0), the picture reconstruction with luma dependent chroma residual scaling process for chroma samples as specified in clause 8.7.5.3 is invoked with the chroma location (xCurr, yCurr), the transform block width nCurrSw and height nCurrSh, the coded block flag of the current chroma transform block tuCbfChroma, the predicted chroma sample array predSamples, and the residual chroma sample array resSamples as inputs, and the output is the reconstructed chroma sample array recSamples.

After decoding the current coding unit, the following may apply:

If cIdx is equal to 0, and if treeType is equal to SINGLE_TREE or DUAL_TREE_LUMA, the following applies

ibcBuf_L[(xCurr+i) % wIbcBufY][(yCurr+j) % CtbSizeY]=recSamples[xCurr+i][yCurr+j]

- for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1.

If cIdx is equal to 1, and if treeType is equal to SINGLE_TREE or DUAL_TREE_CHROMA, the following applies

ibcBuf_Cb[(xCurr+i) % wIbcBufC][(yCurr+j) % CtbSizeC]=recSamples[xCurr+i][yCurr+j]

- for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1.

If cIdx is equal to 2, and if treeType is equal to SINGLE_TREE or DUAL_TREE_CHROMA, the following applies

ibcBuf_Cr[(xCurr+i) % wIbcBufC][(yCurr+j) % CtbSizeC]=recSamples[xCurr+i][yCurr+j]

- for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1.

5.20 Embodiment #20

The changes in some examples are indicated in bolded, underlined, italicized text in this document.

7.3.7 Slice Data Syntax

7.3.7.1 General Slice Data Syntax

slice_data( ) {
Descriptor

for( i = 0; i < NumBricksInCurrSlice; i++) {

CtbAddrInBs = FirstCtbAddrBs[ SliceBrickIdx[ i ] ]

for( j = 0; j < NumCtusInBrick[ SliceBrickIdx[ i ] ]; j++, CtbAddrInBs++

) {

if( ( j % BrickWidth[ SliceBrickIdx[ i ] ] ) = = 0) {

NumHmvpCand = 0

NumHmvpIbcCand = 0

custom character

}

CtbAddrInRs = CtbAddrBsToRs[ CtbAddrInBs ]

coding_tree_unit( )

if( entropy_coding_sync_enabled_flag &&

( ( j + 1) % BrickWidth[ SliceBrickIdx[ i ] ] = = 0 ) ) {

end_of_subset_one_bit /* equal to 1 */
ae(v)

if( j < NumCtusInBrick[ SliceBrickIdx[ i ] ] − 1 )

byte_alignment( )

}

}

if( !entropy_coding_sync_enabled_flag ) {

end_of_brick_one_bit /* equal to 1 */
ae(v)

if( i < NumBricksInCurrSlice − 1 )

byte_alignment( )

}

}

}

7.4.8.5 Coding Unit Semantics

- IsInSmr[x0][y0] is equal to TRUE.
- SmrX[x0][y0] is equal to x0.
- SmrY[x0][y0] is equal to y0.

Set vSize as min(ctbSize, 64) and wIbcBufY as (128*128/CtbSizeY).

ibcBuf_Lis a array with width being wIbcBufY and height being CtbSizeY.

ibcBuf_Cband ibcBuf_Crare arrays with width being wIbcBufC=(wIbcBufY/SubWidthC) and height being (CtbSizeY/SubHeightC), i.e. CtbSizeC.

- resetIbcBuf=0

When (x0% vSizeY) is equal to 0 and (y0% vSizeY) is equal to 0, the following applies

ibcBuf_L[x% wIbcBufY][y% CtbSizeY]=−1, for x=x0 . . . x0+max(vSize,cbWidth)−1 and y=y0 . . . y0+max(vSize,cbHeight)−1
ibcBuf_Cb[x% wIbcBufC][y% CtbSizeC]=−1, for x=x0/SubWidthC . . . x0/SubWidthC+max(vSize/SubWidthC,cbWidth)−1 and
y=y0/SubHeightC . . . y0/SubHeightC+max(vSize/SubHeightC,cbHeight)−1
ibcBuf_Cr[x% wIbcBufC][y% CtbSizeC]=−1, for x=x0/SubWidthC . . . x0/SubWidthC+max(vSize/SubWidthC,cbWidth)−1 and
y=y0/SubHeightC . . . y0/SubHeightC+max(vSize/SubHeightC,cbHeight)−1

8.6.2 Derivation Process for Motion Vector Components for IBC Blocks

8.6.2.1 General

Inputs to this process are:

- a luma location (xCb, yCb) of the top-left sample of the current luma coding block relative to the top-left luma sample of the current picture,
- a variable cbWidth specifying the width of the current coding block in luma samples,
- a variable cbHeight specifying the height of the current coding block in luma samples.

Outputs of this process are:

- the luma motion vector in 1/16 fractional-sample accuracy mvL.

The luma motion vector mvL is derived as follows:

- The derivation process for IBC luma motion vector prediction as specified in clause 8.6.2.2 is invoked with the luma location (xCb, yCb), the variables cbWidth and cbHeight inputs, and the output being the luma motion vector mvL.
- When general_merge_flag[xCb][yCb] is equal to 0, the following applies:
  - 10. The variable mvd is derived as follows:
    
    mvd[0]=MvdL0[xCb][yCb][0] (8-883)
    mvd[1]=MvdL0[xCb][yCb][1] (8-884)
  - 11. The rounding process for motion vectors as specified in clause 8.5.2.14 is invoked with mvX set equal to mvL, rightShift set equal to MvShift+2, and leftShift set equal to MvShift+2 as inputs and the rounded mvL as output.
  - 12. The luma motion vector mvL is modified as follows:
    
    u[0]=(mvL[0]+mvd[0]+2¹⁸)% 2¹⁸ (8-885)
    mvL[0]=(u[0]>=2¹⁷)?(u[0]−2¹⁸): u[0] (8-886)
    u[1]=(mvL[1]+mvd[1]+2¹⁸)% 2¹⁸ (8-887)
    mvL[1]=(u[1]>=2¹⁷)?(u[1]−2¹⁸): u[1] (8-888)
    - NOTE 1 The resulting values of mvL[0] and mvL[1] as specified above will always be in the range of −2¹⁷to 2¹⁷−1, inclusive.

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.

Clause 8.6.2.5 is invoked with mvL as input and mvC as output.

It is a requirement of bitstream conformance that the luma block vector mvL shall obey the following constraints:

((yCb+(mvL[1]>>4))% CtbSizeY)+cbHeight is less than or equal to CtbSizeY

- For x=xCb . . . xCb+cbWidth−1 and y=yCb . . . yCb+cbHeight−1, ibcBuf_L(x+(mvL[0]>>4))% wIbcBuf[Y][(y+(mvL[1]>>4))% CtbSizeY] shall not be equal to −1.
  
  8.6.3 Decoding Process for Ibc Blocks
  
  8.6.3.1 General

This process is invoked when decoding a coding unit coded in ibc prediction mode.

Inputs to this process are:

- a luma location (xCb, yCb) specifying the top-left sample of the current coding block relative to the top-left luma sample of the current picture,
- a variable cbWidth specifying the width of the current coding block in luma samples,
- a variable cbHeight specifying the height of the current coding block in luma samples,
- a variable cIdx specifying the colour component index of the current block.
- the motion vector my,
- an (wIbcBufY)×(CtbSizeY) array ibcBuf_L, an (wIbcBufC)×(CtbSizeC) array ibcBuf_Cb, an (wIbcBufC)×(CtbSizeC) array ibcBuf_Cr.

Outputs of this process are:

- an array predSamples of prediction samples.

For x=xCb . . . xCb+Width−1 and y=yCb . . . yCb+Height−1, the following applies

If cIdx is equal to 0

predSamples[x][y]=ibcBuf_L(x+mv[0]>>4))% wIbcBuf[Y][(y+(mv[1]>>4))% CtbSizeY]

if cIdx is equal to 1

predSamples[x][y]=ibcBuf_Cb[(x+mv[0]>>5))% wIbcBufC][(y+(mv[1]>>5))% CtbSizeC]

if cIdx is equal to 2

predSamples[x][y]=ibcBuf_Cr[(x+mv[0]>>5))% wIbcBufC][(y+(mv[1]>>5))% CtbSizeC]

8.7.5 Picture Reconstruction Process

8.7.5.1 General

Inputs to this process are:

- a location (xCurr, yCurr) specifying the top-left sample of the current block relative to the top-left sample of the current picture component,
- the variables nCurrSw and nCurrSh specifying the width and height, respectively, of the current block,
- a variable cIdx specifying the colour component of the current block,
- an (nCurrSw)×(nCurrSh) array predSamples specifying the predicted samples of the current block,
- an (nCurrSw)×(nCurrSh) array resSamples specifying the residual samples of the current block.

Output of this process are a reconstructed picture sample array recSamples and IBC buffer arrays ibcBuf_L, ibcBuf_Cb, ibcBuf_Cr.

Depending on the value of the colour component cIdx, the following assignments are made:

- If cIdx is equal to 0, recSamples corresponds to the reconstructed picture sample array S_Land the function clipCidx1 corresponds to Clip1_Y.
- Otherwise, if cIdx is equal to 1, tuCbfChroma is set equal to tu_cbf_cb[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S_Cband the function clipCidx1 corresponds to Clip1_C.
- Otherwise (cIdx is equal to 2), tuCbfChroma is set equal to tu_cbf_cr[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S_Crand the function clipCidx1 corresponds to Clip1_C.

Depending on the value of slice_lmcs_enabled_flag, the following applies:

- If slice_lmcs_enabled_flag is equal to 0, the (nCurrSw)×(nCurrSh) block of the reconstructed samples recSamples at location (xCurr, yCurr) is derived as follows for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1:
  
  recSamples[xCurr+i][yCurr+j]=clipCidx1(predSamples[i][j]+resSamples[i][j]) (8-992)
- Otherwise (slice_lmcs_enabled_flag is equal to 1), the following applies:
  - If cIdx is equal to 0, the following applies:
    - The picture reconstruction with mapping process for luma samples as specified in clause 8.7.5.2 is invoked with the luma location (xCurr, yCurr), the block width nCurrSw and height nCurrSh, the predicted luma sample array predSamples, and the residual luma sample array resSamples as inputs, and the output is the reconstructed luma sample array recSamples.
  - Otherwise (cIdx is greater than 0), the picture reconstruction with luma dependent chroma residual scaling process for chroma samples as specified in clause 8.7.5.3 is invoked with the chroma location (xCurr, yCurr), the transform block width nCurrSw and height nCurrSh, the coded block flag of the current chroma transform block tuCbfChroma, the predicted chroma sample array predSamples, and the residual chroma sample array resSamples as inputs, and the output is the reconstructed chroma sample array recSamples.

After decoding the current coding unit, the following may apply:

If cIdx is equal to 0, and if treeType is equal to SINGLE_TREE or DUAL_TREE_LUMA, the following applies

ibcBuf_L(xCurr+i) % wIbcBuf[Y][(yCurr+j) % CtbSizeY]=recSamples[xCurr+i][yCurr+i]

- for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1.

If cIdx is equal to 1, and if treeType is equal to SINGLE_TREE or DUAL_TREE_CHROMA, the following applies

ibcBuf_Cb[(xCurr+i) % wIbcBufC][(yCurr+j) % CtbSizeC]=recSamples[xCurr+i][yCurr+j]

- for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1.

If cIdx is equal to 2, and if treeType is equal to SINGLE_TREE or DUAL_TREE_CHROMA, the following applies

ibcBuf_Cr[(xCurr+i) % wIbcBufC][(yCurr+j) % CtbSizeC]=recSamples[xCurr+i][yCurr+j]

- for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1.

FIG. 6 is a flowchart of an example method 600 of visual media (video or image) processing. The method 600 includes determining (602), 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 (604) the conversion using the reference samples stored in the buffer.

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 document.

- 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 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 signaled 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 43, 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 Item 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 MxM, 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. FIGS. 8 and 9 show additional example embodiments.

- 46. The method of claim 3, 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 claim 3, 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 claim 3, 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 claims 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+Chroma_CTU_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.

FIG. 7 is a block diagram of a hardware platform of a video/image processing apparatus 700. The apparatus 700 may be used to implement one or more of the methods described herein. The apparatus 700 may be embodied in a smartphone, tablet, computer, Internet of Things (IoT) receiver, and so on. The apparatus 700 may include one or more processors 702, one or more memories 704 and video processing hardware 706. The processor(s) 702 may be configured to implement one or more methods (including, but not limited to, method 600) described in the present document. The memory (memories) 704 may be used for storing data and code used for implementing the methods and techniques described herein. The video processing hardware 706 may be used to implement, in hardware circuitry, some techniques described in the present document.

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.

Section a: Another Additional Example Embodiment

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 techniques described in the present document.

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.

A1. Introduction

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 FIG. 2.

In the current draft (VVC draft 4), the area is defined as

The following conditions shall be true:

( yCb + ( mvL[ 1 ] >> 4 ) ) >> CtbLog2SizeY = yCb >> CtbLog2SizeY
(8-972)

( yCb + ( mvL[ 1 ] >> 4 ) + cbHeight − 1) >> CtbLog2SizeY = yCb >>
(8-973)

CtbLog2SizeY

( xCb + ( mvL[ 0 ] >> 4 ) ) >> CtbLog2SizeY >= ( xCb >> CtbLog2SizeY
(8-974)

) −1

( xCb + ( mvL[ 0 ] >> 4) + cbWidth − 1) >> CtbLog2SizeY <= ( xCb >>
(8-975)

CtbLog2SizeY )

[Ed. (SL): conditions (8-218) and (8-216) might have been checked by 6.4.X.]

When ( xCb + ( mvL[ 0 ] >> 4 ) ) >> CtbLog2SizeY is equal to ( xCb >> CtbLog2SizeY

) −1, the derivation process for block availability as specified in clause 6.4.X [Ed. (BB):

Neighbouring blocks availability checking process tbd] is invoked with the current luma

location( xCurr, yCurr ) set equal to ( xCb, yCb ) and the neighbouring luma location ( ( (

xCb + ( mvL[ 0 ] >> 4 ) + CtbSizeY ) >> ( CtbLog2SizeY −1 ) ) << ( CtbLog2SizeY −1

), ( ( yCb + ( mvL[ 1 ] >> 4 ) ) >> ( CtbLog2SizeY − 1 ) ) << ( CtbLog2SizeY − 1 ) ) as

inputs, and the output shall be equal to FALSE.

Thus, the total reference size is a CTU.

A2. Potential Issues of the Current Design

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:

- 1. To handle smaller CTU size might be an issue. Suppose that CTU size is 32×32, it is not clear whether the current 64×64 memory for decoding the current VPDU can support 32×32 level memory reuse efficiently in different architectures.
- 2. The reference area varies significantly. Accordingly, too many bitstream conformance constrains are introduced. It places extra burden to encoder to exploit reference area efficiently and avoid generating legal bitstreams. It also increases the possibility to have invalid BVs in different modules, e.g. merge list. To handle those invalid BVs may introduce extra logics or extra conformance constrains. It not only introduces burdens to encoder or decoder, it may also create divergence between BV coding and MV coding.
- 3. The design does not scale well. Because VPDU decoding is mixed with IBC buffer, it is not easy to increase or decrease reference area relative to the current one 128×128 CTU design. It may limit the flexibility to exploit a better coding efficiency vs. on-chip memory trade-off in the later development, e.g. a lower or higher profile.
- 4. The bit-depth of IBC reference buffer is linked with decoding buffer. Even though screen contents usually have a lower bit-depth than internal decoding bit-depth, the buffer still needs to spend memory to store bits mostly representing rounding or quantization noises. The issue becomes even severe when considering higher decoding bit-depth configurations.

A3. A Clear IBC Buffer Design

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, FIG. 2 shows the buffer status.

FIG. 12 is an illustration of IBC reference buffer status, where a block denotes a 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 constrain 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 constrains can be removed.

A4. Experimental Results

In some embodiments, the disclosed methods can be implemented using VTM-4.0 software.

For a 10-bit buffer implementation and 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 a 8-bit buffer implementation, the results shown in Table II.

TABLE I

Performance with a 7-bit buffer. The anchor is VTM-4.0

with IBC on for all sequences.

Over VTM-4.0 w/IBC on

Y
U
V
EncT
DecT

All Intra

Class A1
−0.01%
−0.09%
−0.10%
132%
101%

Class A2
0.05%
0.00%
0.06%
135%
100%

Class B
0.00%
−0.02%
0.01%
135%
100%

Class C
−0.02%
0.01%
0.03%
130%
98%

Class E
−0.13%
−0.16%
−0.04%
135%
99%

Overall
−0.02%
−0.05%
0.00%
133%
100%

Class D
0.04%
0.04%
0.12%
127%
107%

Class F
−0.99%
−1.14%
−1.18%
115%
99%

4:2:0 TGM
−2.57%
−2.73%
−2.67%
104%
102%

Random Access

Class A1
0.02%
−0.01%
0.01%
109%
100%

Class A2
0.00%
−0.04%
0.03%
111%
100%

Class B
−0.01%
−0.10%
−0.22%
113%
101%

Class C
−0.01%
0.17%
0.12%
115%
100%

Class E

Overall
0.00%
0.00%
−0.04%
112%
100%

Class D
0.05%
0.16%
0.20%
117%
101%

Class F
−0.71%
−0.77%
−0.77%
109%
99%

4:2:0 TGM
−1.81%
−1.65%
−1.64%
107%
101%

Low delay B

Class A1

Class A2

Class B
0.01%
0.36%
0.30%
114%
95%

Class C
−0.01%
−0.12%
−0.10%
120%
98%

Class E
0.10%
0.20%
0.18%
107%
99%

Overall
0.03%
0.16%
0.13%
114%
97%

Class D
−0.01%
1.07%
0.18%
123%
104%

Class F
−0.79%
−0.89%
−1.01%
110%
100%

4:2:0 TGM
−1.36%
−1.30%
−1.26%
109%
102%

TABLE II

Performance with a 8-bit buffer. The anchor is VTM-

4.0 with IBC on for all sequences.

Over VTM-4.0 w/IBC on

Y
U
V
EncT
DecT

All Intra

Class A1
−0.01%
0.02%
−0.10%
129%
102%

Class A2
0.02%
−0.06%
−0.02%
134%
102%

Class B
−0.04%
−0.02%
−0.07%
135%
101%

Class C
−0.03%
0.04%
0.00%
130%
98%

Class E
−0.16%
−0.14%
−0.08%
134%
100%

Overall
−0.04%
−0.03%
−0.05%
133%
100%

Class D
0.00%
0.04%
0.02%
126%
101%

Class F
−1.31%
−1.27%
−1.29%
114%
98%

4:2:0 TGM
−3.23%
−3.27%
−3.24%
101%
100%

Random Access

Class A1
−0.01%
−0.08%
0.04%
107%
99%

Class A2
−0.03%
−0.16%
0.06%
110%
99%

Class B
−0.01%
−0.14%
−0.22%
111%
99%

Class C
−0.01%
0.15%
0.09%
115%
100%

Class E

Overall
−0.01%
−0.05%
−0.03%
111%
99%

Class D
0.01%
0.19%
0.22%
116%
101%

Class F
−1.01%
−0.99%
−1.01%
108%
99%

4:2:0 TGM
−2.33%
−2.14%
−2.19%
105%
100%

Low delay B

Class A1

Class A2

Class B
0.00%
0.04%
−0.14%
113%
#NUM!

Class C
−0.05%
−0.28%
−0.15%
119%
98%

Class E
0.04%
−0.16%
0.43%
107%
#NUM!

Overall
0.00%
−0.11%
0.00%
113%
#NUM!

Class D
−0.07%
1.14%
0.13%
122%
99%

Class F
−0.81%
−0.92%
−0.96%
111%
99%

4:2:0 TGM
−1.71%
−1.67%
−1.71%
106%
95%

FIG. 17 is a block diagram showing an example video processing system 1700 in which various techniques disclosed herein may be implemented. Various implementations may include some or all of the components of the system 1700. The system 1700 may include input 1702 for receiving video content. The video content may be received in a raw or uncompressed format, e.g., 8 or 10 bit multi-component pixel values, or may be in a compressed or encoded format. The input 1702 may represent a network interface, a peripheral bus interface, or a storage interface. Examples of network interface include wired interfaces such as Ethernet, passive optical network (PON), etc. and wireless interfaces such as Wi-Fi or cellular interfaces.

The system 1700 may include a coding component 1704 that may implement the various coding or encoding methods described in the present document. 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 SATA (serial advanced technology attachment), PCI, IDE interface, and the like. The techniques described in the present document 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.

FIG. 18 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 1 in Section 4 of this document. At step 1802, the process determines a size of a buffer to store reference samples for prediction in an intra block copy mode. At step 1804, the process performs a conversion between a current video block of visual media data and a bitstream representation of the current video block, using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture.

FIG. 19 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 4 in Section 4 of this document. At step 1902, the process determines, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reconstructed samples for prediction in an intra block copy mode, wherein the buffer is used for storing the reconstructed samples before a loop filtering step. At step 1904, the process performs the conversion using the reconstructed samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture.

FIG. 20 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 5 in Section 4 of this document. At step 2002, the process determines, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reconstructed samples for prediction in an intra block copy mode, wherein the buffer is used for storing the reconstructed samples after a loop filtering step. At step 2004, the process performs the conversion using the reconstructed samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in a same video region with the current video block without referring to a reference picture.

FIG. 21 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 6 in Section 4 of this document. At step 2102, the process determines, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reconstructed samples for prediction in an intra block copy mode, wherein the buffer is used for storing the reconstructed samples both before a loop filtering step and after the loop filtering step. At step 2104, the process performs the conversion using the reconstructed samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture.

FIG. 22 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 7 in Section 4 of this document. At step 2202, the process uses a buffer to store reference samples for prediction in an intra block copy mode, wherein a first bit-depth of the buffer is different than a second bit-depth used to represent visual media data in the bitstream representation. At step 2204, the process performs a conversion between a current video block of the visual media data and a bitstream representation of the current video block, using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture.

FIG. 23 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 8 in Section 4 of this document. At step 2302, the process initializes a buffer to store reference samples for prediction in an intra block copy mode, wherein the buffer is initialized with a first value. At step 2304, the process performs a conversion between a current video block of visual media data and a bitstream representation of the current video block using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture.

FIG. 24 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 9 in Section 4 of this document. At step 2402, the process initializes a buffer to store reference samples for prediction in an intra block copy mode, wherein, based on availability of one or more video blocks in visual media data, the buffer is initialized with pixel values of the one or more video blocks in the visual media data. At step 2404, the process performs a conversion between a current video block that does not belong to the one or more video blocks of the visual media data and a bitstream representation of the current video block, using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture.

FIG. 25 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 14c in Section 4 of this document. At step 2502, the process determines, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reference samples for prediction in an intra block copy mode. At step 2504, the process performs the conversion using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture. At step 2506, the process computes a corresponding reference in the buffer based on a reference location (P mod M, Q mod N) where “mod” is modulo operation and M and N are integers representing x and y dimensions of the buffer, wherein the reference location (P, Q) is determined using the block vector (BVx, BVy) and the location (x0, y0), for a pixel spatially located at location (x0, y0) and having a block vector (BVx, BVy) included in the motion information.

FIG. 26 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 14a-14b in Section 4 of this document. At step 2602, the process determines, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reference samples for prediction in an intra block copy mode. At step 2604, the process performs the conversion using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture. At step 2606, the process computes a corresponding reference in the buffer based on a reference location (P, Q), wherein the reference location (P, Q) is determined using the block vector (BVx, BVy) and the location (x0, y0), for a pixel spatially located at location (x0, y0) and having a block vector (BVx, BVy) included in the motion information.

FIG. 27 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 10 in Section 4 of this document. At step 2702, the process determines, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reference samples for prediction in an intra block copy mode, wherein pixel locations within the buffer are addressed using x and y numbers. At step 2704, the process performs, based on the x and y numbers, the conversion using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture.

FIG. 28 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 15 in Section 4 of this document. At step 2802, the process determines, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reference samples for prediction in an intra block copy mode, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture. At step 2804, the process computes a corresponding reference in the buffer at a reference location (P, Q), wherein the reference location (P, Q) is determined using the block vector (BVx, BVy) and the location (x0, y0), for a pixel spatially located at location (x0, y0) of the current video block and having a block vector (BVx, BVy). At step 2806, the process re-computes the reference location using a sample in the buffer, upon determining that the reference location (P, Q) lies outside the buffer.

FIG. 29 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 16 in Section 4 of this document. At step 2902, the process determines, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reference samples for prediction in an intra block copy mode, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture. At step 2904, the process computes a corresponding reference in the buffer at a reference location (P, Q), wherein the reference location (P, Q) is determined using the block vector (BVx, BVy) and the location (x0, y0), for a pixel spatially located at location (x0, y0) of the current video block relative to an upper-left position of a coding tree unit including the current video block and having a block vector (BVx, BVy). At step 2906, the process constrains at least a portion of the reference location to lie within a pre-defined range, upon determining that the reference location (P, Q) lies outside the buffer.

FIG. 30 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 17 in Section 4 of this document. At step 3002, the process determines, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reference samples for prediction in an intra block copy mode, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture. At step 3004, the process computes a corresponding reference in the buffer at a reference location (P, Q), wherein the reference location (P, Q) is determined using the block vector (BVx, BVy) and the location (x0, y0), for a pixel spatially located at location (x0, y0) of the current video block relative to an upper-left position of a coding tree unit including the current video block and having a block vector (BVx, BVy). At step 1706, the process pads the block vector (BVx, BVy) according to a block vector of a sample value inside the buffer, upon determining that the block vector (BVx, BVy) lies outside the buffer.

FIG. 31 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 30 in Section 4 of this document. At step 3102, the process resets, during a conversion between a video and a bitstream representation of the video, a buffer that stores reference samples for prediction in an intra block copy mode at a video boundary. At step 3104, the process performs the conversion using the reference samples stored in the buffer, wherein the conversion of a video block of the video is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the video block without referring to a reference picture.

FIG. 32 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 34 in Section 4 of this document. At step 3202, the process performs a conversion between a current video block and a bitstream representation of the current video block. At step 3204, the process updates a buffer which is used to store reference samples for prediction in an intra-block copy mode, wherein the buffer is used for a conversion between a subsequent video block and a bitstream representation of the subsequent video block, wherein the conversion between the subsequent video block and a bitstream representation of the subsequent video block is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the subsequent video block without referring to a reference picture.

FIG. 33 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 39 in Section 4 of this document. At step 3302, the process determines, for a conversion between a current video block and a bitstream representation of the current video block, a buffer that is used to store reconstructed samples for prediction in an intra block copy mode, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture. At step 3304, the process applies a pre-processing operation to the reconstructed samples stored in the buffer, in response to determining that the reconstructed samples stored in the buffer are to be used for predicting sample values during the conversation.

FIG. 34 is a flowchart of an example method of visual data processing. Steps of this flowchart are discussed in connection with Example embodiment 42 in Section 4 of this document. At step 3402, the process determines, 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, whether to use K1 previously processed VPDUs from an even-numbered row of the video region and/or K2 previously processed VPDUs from an odd-numbered row of the video region. At step 3404, the process performs the conversion, wherein the conversion excludes using remaining of the current VPDU, wherein the conversion is performed in an intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the video block without referring to a reference picture.

Some embodiments of the present document are now presented in clause-based format.

1. A method of visual media processing, comprising:

- determining, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reference samples for prediction in an intra block copy mode;
- performing the conversion using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture; and
- for a pixel spatially located at location (x0, y0) and having a block vector (BVx, BVy) included in the motion information, computing a corresponding reference in the buffer based on a reference location (P mod M, Q mod N) where “mod” is modulo operation and M and N are integers representing x and y dimensions of the buffer, wherein the reference location (P, Q) is determined using the block vector (BVx, BVy) and the location (x0, y0).

2. The method of 1, wherein the reference location (P, Q) is determined as P=x0+BVx and Q=y0+BVy.

3. A method of visual media processing, comprising:

- determining, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reference samples for prediction in an intra block copy mode;
- performing the conversion using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture; and
- for a pixel spatially located at location (x0, y0) and having a block vector (BVx, BVy) included in the motion information, computing a corresponding reference in the buffer based on a reference location (P, Q), wherein the reference location (P, Q) is determined using the block vector (BVx, BVy) and the location (x0, y0).

4. The method of clause 3, wherein the reference location (P, Q) is determined as P=x0+BVx, and Q=y0+BVy.

5. The method of any one or more of clauses 3-4, further comprising:

- in an event when the reference location (P, Q) is outside the buffer, computing the corresponding reference in the buffer by clipping the reference location (P, Q) at a boundary of the buffer.

6. The method of any one or more of clauses 3-4, further comprising:

- in an event when the reference location (P, Q) is outside the buffer, computing the corresponding reference in the buffer as a predetermined value.

7. The method of clause 6, wherein the predetermined value corresponds to a mid-grey value.

8. A method of visual media processing, comprising:

- determining, for a conversion between a current video block of visual media data and a bitstream representation of the current video block, a buffer that stores reference samples for prediction in an intra block copy mode, wherein pixel locations within the buffer are addressed using x and y numbers; and
- performing, based on the x and y numbers, the conversion using the reference samples stored in the buffer, wherein the conversion is performed in the intra block copy mode which is based on motion information related to a reconstructed block located in same video region with the current video block without referring to a reference picture.

9. The method of clause 8, wherein the x and y numbers vary as follows:

- x=0, 1, 2, . . . , M−1; wherein the size of the buffer is expressed as M×N, wherein M and N are pixel width and pixel height of the buffer.

10. The method of clause 8, wherein the pixel locations within the buffer are addressed using a single number denoted 1 such that 1=y*M+x, 1=0, 1, . . . , M*N−1, wherein M and N are pixel width and pixel height of the buffer.

11. The method of any one or more of clauses 8-10, 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) in the buffer, wherein (x0, y0) correspond to an upper-left position of a coding tree unit including the current video block.

12. The method of any one or more of clauses 8-10, 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) in the buffer, where (x0, y0) correspond to an upper-left position of a coding tree unit including the current video block and wherein Tx and Ty are offset values.

13. The method of clause 12, wherein Tx and Ty are pre-defined offset values.

14. The method of any of clauses 1-13, wherein the conversion includes generating the bitstream representation from the current video block.

15. The method of any of clauses 1-13, wherein the conversion includes generating pixel values of the current video block from the bitstream representation.

16. A video encoder apparatus comprising a processor configured to implement a method recited in any one or more of clauses 1-13.

17. A video decoder apparatus comprising a processor configured to implement a method recited in any one or more of clauses 1-13.

18. 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-13.

In the present document, 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 presently disclosed technology have been described herein for purposes of illustration, but that various modifications may be made without deviating from the scope of the invention. Accordingly, the presently disclosed technology is not limited except as by the appended claims.

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

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

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

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

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

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

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

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

Claims

1. A method of processing video data, comprising: determining, for a conversion between a current video block of visual media data and a bitstream of the current video block, that a first coding mode is applied to the current video block;deriving a first block vector (BVx, BVy) for the current video block;generating, based on the first block vector and a buffer, a first prediction sample for a first sample (x0, y0) in the current video block, wherein in the first coding mode, prediction samples of the current video block are derived from a same picture including the current video block;computing a corresponding reference in the buffer for the first prediction sample based on a reference location (P, Q), wherein the reference location (P, Q) is determined using the first block vector (BVx, BVy) and a location (x0, y0); andperforming the conversion based on the prediction samples,wherein at least part of reconstructed samples of previous coded video blocks after a loop filtering operation are stored in the buffer for the first coding mode.
2. The method of claim 1, wherein the reconstructed samples of the previous coded video blocks after the loop filtering operation and the reconstructed samples of the previous coded video blocks without the loop filtering operation are both stored in the buffer.
3. The method of claim 2, wherein whether samples from a current picture including the current video block and samples from other pictures are both stored in the buffer or not depends on an availability of the samples.
4. The method of claim 1, wherein the reference location (P, Q) is determined as P=x0+BVx, and Q=y0+BVy.
5. The method of claim 1, wherein, in a case where the reference location (P, Q) is outside the buffer, the corresponding reference in the buffer is computed by clipping the reference location (P, Q) to a boundary of the buffer.
6. The method of claim 1, wherein, in a case where the reference location (P, Q) is outside the buffer, the corresponding reference in the buffer is a predetermined value.
7. The method of claim 6, wherein the predetermined value corresponds to a mid-grey value.
8. The method of claim 1, wherein a position of a reference sample in the buffer is represented as (x, y), and a size of the buffer is M×N, wherein x=0, 1, 2, . . . , M−1, y=0, 1, 2, . . . , N−1, and M and N are integers.
9. The method of claim 1, wherein a position of a reference sample in the buffer is represented as a single number 1, 1=y*M+x, and a size of the buffer is M×N, wherein 1=0, 1, . . . , M*N−1, x=0, 1, 2, . . . , M−1, y=0, 1, 2, . . . , N−1, and M and N are integers.
10. The method of claim 1, wherein the bitstream of the current video block includes the first block vector (BVx, BVy) for the conversion, wherein (BVx,BVy) is equal to (x−x1,y−y1), wherein (x1, y1) corresponds to an upper-left position of a coding tree unit including the current video block, and (x, y) corresponds to a position in the buffer.
11. The method of claim 1, wherein the bitstream of the current video block includes the first block vector (BVx, BVy) for the conversion, wherein (BVx,BVy) is equal to (x−x1+Tx,y−y1+Ty), wherein (x1, y1) corresponds to an upper-left position of a coding tree unit including the current video block, (x, y) corresponds to a position in the buffer, and Tx and Ty are offset values.
12. The method of claim 11 wherein Tx and Ty are pre-defined offset values.
13. The method of claim 1, wherein the loop filtering operation includes a deblocking filtering, a sample adaptive offset filtering, or an adaptive loop filtering.
14. The method of claim 1, parts of the previous coded video blocks are located in a coding tree block different from a current coding tree block including the current video block.
15. The method of claim 1, parts of the previous coded video blocks are located in a picture different from a current picture including the current video block.
16. The method of claim 1, wherein the conversion includes encoding the current video block into the bitstream.
17. The method of claim 1, wherein the conversion includes decoding the current video block from the bitstream.
18. An apparatus for processing video data comprising a processor and a non-transitory memory with instructions thereon, wherein the instructions upon execution by the processor, cause the processor to: determine, for a conversion between a current video block of visual media data and a bitstream of the current video block, that a first coding mode is applied to the current video block;derive a first block vector (BVx, BVy) for the current video block;generate, based on the first block vector and a buffer, a first prediction sample for a first sample (x0, y0) in the current video block, wherein in the first coding mode, prediction samples of the current video block are derived from a same picture including the current video block;compute a corresponding reference in the buffer for the first prediction sample based on a reference location (P, Q), wherein the reference location (P, Q) is determined using the first block vector (BVx, BVy) and a location (x0, y0); andperform the conversion based on the prediction samples, wherein at least part of reconstructed samples of previous coded video blocks after a filtering operation are stored in the buffer for the first coding mode.
19. A method for storing a bitstream of a video, comprising: determining that a first coding mode is applied to a current video block;deriving a first block vector (BVx, BVy) for the current video block;generating, based on the first block vector and a buffer, a first prediction sample for a first sample (x0, y0) in the current video block, wherein in the first coding mode, prediction samples of the current video block are derived from a same picture including the current video block;computing a corresponding reference in the buffer for the first prediction sample based on a reference location (P, Q), wherein the reference location (P, Q) is determined using the first block vector (BVx, BVy) and a location (x0, y0);generating the bitstream based on the prediction samples; andstoring the bitstream in a non-transitory computer-readable recoding medium,wherein at least part of reconstructed samples of previous coded video blocks after a loop filtering operation are stored in the buffer for the first coding mode.

Priority Claims (15)

Number	Date	Country	Kind
PCT/CN2019/074598	Feb 2019	WO	international
PCT/CN2019/076695	Mar 2019	WO	international
PCT/CN2019/076848	Mar 2019	WO	international
PCT/CN2019/077725	Mar 2019	WO	international
PCT/CN2019/079151	Mar 2019	WO	international
PCT/CN2019/085862	May 2019	WO	international
PCT/CN2019/088129	May 2019	WO	international
PCT/CN2019/091691	Jun 2019	WO	international
PCT/CN2019/093552	Jun 2019	WO	international
PCT/CN2019/094957	Jul 2019	WO	international
PCT/CN2019/095297	Jul 2019	WO	international
PCT/CN2019/095504	Jul 2019	WO	international
PCT/CN2019/095656	Jul 2019	WO	international
PCT/CN2019/095913	Jul 2019	WO	international
PCT/CN2019/096048	Jul 2019	WO	international

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No. PCT/CN2020/074160 filed on Feb. 2, 2020, which claims the priority to and benefits of International Patent Application No. PCT/CN2019/074598, filed on Feb. 2, 2019, International Patent Application No. PCT/CN2019/076695, filed on Mar. 1, 2019, International Patent Application No. PCT/CN2019/076848, filed on Mar. 4, 2019, International Patent Application No. PCT/CN2019/077725, filed on Mar. 11, 2019, International Patent Application No. PCT/CN2019/079151, filed on Mar. 21, 2019, International Patent Application No. PCT/CN2019/085862, filed on May 7, 2019, International Patent Application No. PCT/CN2019/088129, filed on May 23, 2019, International Patent Application No. PCT/CN2019/091691, filed on Jun. 18, 2019, International Patent Application No. PCT/CN2019/093552, filed on Jun. 28, 2019, International Patent Application No. PCT/CN2019/094957, filed on Jul. 6, 2019, International Patent Application No. PCT/CN2019/095297, filed on Jul. 9, 2019, International Patent Application No. PCT/CN2019/095504, filed on Jul. 10, 2019, International Patent Application No. PCT/CN2019/095656, filed on Jul. 11, 2019, International Patent Application No. PCT/CN2019/095913, filed on Jul. 13, 2019, and International Patent Application No. PCT/CN2019/096048, filed on Jul. 15, 2019. The entire disclosures of the aforementioned applications are incorporated by reference as part of the disclosure of this application.

US Referenced Citations (188)

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
10567754	Li et al.	Feb 2020	B2
10582213	Li et al.	Mar 2020	B2
10728552	Tsukuba	Jul 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
11375217	Xu et al.	Jun 2022	B2
11438613	Xu et al.	Sep 2022	B2
11523107	Xu et al.	Dec 2022	B2
11528476	Xu et al.	Dec 2022	B2
11546581	Xu et al.	Jan 2023	B2
11570753	Xue et al.	Jan 2023	B2
11575888	Xu et al.	Feb 2023	B2
11729414	Park et al.	Aug 2023	B2
11876957	Jang et al.	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 et al.	Oct 2006	A1
20060244748	Long et al.	Nov 2006	A1
20080025407	Winger	Jan 2008	A1
20080043845	Nakaishi	Feb 2008	A1
20080181300	Hosaka et al.	Jul 2008	A1
20080219352	Tokumitsu et al.	Sep 2008	A1
20080260034	Wang et al.	Oct 2008	A1
20100014584	Feder et al.	Jan 2010	A1
20100054329	Bronstein et al.	Mar 2010	A1
20100228957	Rabinovitch et al.	Sep 2010	A1
20110122950	Ji et al.	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. et al.	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 et al.	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 et al.	Jun 2015	A1
20150195559	Chen et al.	Jul 2015	A1
20150264348	Zou et al.	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 et al.	Sep 2015	A1
20150296213	Hellman	Oct 2015	A1
20150334405	Rosewarne et al.	Nov 2015	A1
20150373357	Pang et al.	Dec 2015	A1
20150373358	Pang et al.	Dec 2015	A1
20150373359	He et al.	Dec 2015	A1
20160100163	Rapaka et al.	Apr 2016	A1
20160100189	Pang	Apr 2016	A1
20160104457	Wu et al.	Apr 2016	A1
20160105682	Rapaka et al.	Apr 2016	A1
20160219298	Li et al.	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 et al.	Dec 2016	A1
20160360234	Tourapis et al.	Dec 2016	A1
20170054996	Xu et al.	Feb 2017	A1
20170070748	Li et al.	Mar 2017	A1
20170076419	Fries et al.	Mar 2017	A1
20170094271	Liu et al.	Mar 2017	A1
20170094299	Damudi et al.	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 et al.	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 et al.	Oct 2017	A1
20170295379	Sun et al.	Oct 2017	A1
20170302936	Li et al.	Oct 2017	A1
20170372494	Zhu et al.	Dec 2017	A1
20170374369	Chuang et al.	Dec 2017	A1
20180048909	Liu et al.	Feb 2018	A1
20180101708	Gao	Apr 2018	A1
20180103260	Chuang et al.	Apr 2018	A1
20180115787	Koo et al.	Apr 2018	A1
20180152727	Chuang et al.	Apr 2018	A1
20180124411	Nakagami	May 2018	A1
20180160122	Xu et al.	Jun 2018	A1
20180184093	Xu et al.	Jun 2018	A1
20180205966	Kang et al.	Jul 2018	A1
20180220130	Zhang et al.	Aug 2018	A1
20180255304	Jeon et al.	Sep 2018	A1
20180302645	Laroche et al.	Oct 2018	A1
20180343471	Jacobson et al.	Nov 2018	A1
20180376165	Alshin et al.	Dec 2018	A1
20190007705	Zhao et al.	Jan 2019	A1
20190031194	Kim et al.	Jan 2019	A1
20190068992	Tourapis et al.	Feb 2019	A1
20190089975	Liu et al.	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 et al.	Jul 2019	A1
20190238864	Xiu et al.	Aug 2019	A1
20190246143	Zhang et al.	Aug 2019	A1
20200007877	Zhou	Jan 2020	A1
20200036997	Li et al.	Jan 2020	A1
20200037002	Xu et al.	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 et al.	Jun 2020	A1
20200177910	Li et al.	Jun 2020	A1
20200177911	Aono et al.	Jun 2020	A1
20200204819	Hsieh et al.	Jun 2020	A1
20200213608	Chen et al.	Jul 2020	A1
20200213610	Kondo	Jul 2020	A1
20200244991	Li et al.	Jul 2020	A1
20200260072	Park et al.	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	Jan 2021	A1
20210120261	Lim et al.	Apr 2021	A1
20210136405	Chen et al.	May 2021	A1
20210152833	Gao et al.	May 2021	A1
20210258598	Hendry et al.	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 et al.	Oct 2021	A1
20210321127	Zhao et al.	Oct 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
20220132106	Xu et al.	Apr 2022	A1
20220150474	Xu et al.	May 2022	A1
20220150540	Xu et al.	May 2022	A1
20220166993	Xu et al.	May 2022	A1
20220174310	Xu et al.	Jun 2022	A1
20220210444	Xu et al.	Jun 2022	A1
20220353494	Xu et al.	Nov 2022	A1
20230007273	Gao et al.	Jan 2023	A1
20230019459	Xu et al.	Jan 2023	A1

Foreign Referenced Citations (114)

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
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
3981148	Apr 2022	EP
3900349	Aug 2023	EP
2533905	Jul 2016	GB
106416250	Feb 2017	IN
201847033775	Oct 2018	IN
4360093	Nov 2009	JP
2016534660	Nov 2016	JP
2016539542	Dec 2016	JP
2017130938	Jul 2017	JP
2017519460	Jul 2017	JP
2017522789	Aug 2017	JP
2017535148	Nov 2017	JP
2017535150	Nov 2017	JP
6324590	May 2018	JP
2018521539	Aug 2018	JP
2018524872	Aug 2018	JP
2020017970	Jan 2020	JP
2021521728	Aug 2021	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
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
2016150343	Sep 2019	WO
2020113156	Jun 2020	WO
2020156540	Aug 2020	WO
2020228744	Nov 2020	WO
2020259677	Dec 2020	WO
2021004495	Jan 2021	WO

Non-Patent Literature Citations (106)

Entry
US 11,412,213 B2, 08/2022, Xu et al. (withdrawn)
Gao et al. “Bitstram 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.
Hannuksela et al. “Versatile Video Coding (Draft 6),” 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-O2001, 2019.
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.
Rapaka 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, document JVET-V0050, 2015.
Xu 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.
Xu 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-01161, 2019.
Xu et al. “Bitstram 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.
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).
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).
Notice of Allowance from U.S. Appl. No. 17/362,341 dated Jul. 7, 2022.
Pham Van 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, document JVET-M0474, 2018.
Non Final Office Action from U.S. Appl. No. 17/978,263 dated Mar. 10, 2023.
Chen 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, document JVET-M0890, 2019.
Tsai 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, document JVET-M0888, 2019.
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/362,341 dated Nov. 19, 2021.
Non Final Office Action from U.S. Appl. No. 17/384,246 dated Nov. 26, 2021.
Bross et al. “Versatile Video Coding (Draft 3),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC ITC 1/SC 29/WG 11, 12th Meeting, Macao, CN, Oct. 3-12, 2018, document JVET-L1001, 2018.
Bross et al. “Versatile Video Coding (Draft 4),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC ITC 1/SC 29/WG 11, 13th Meeting, Marrakech, MA, Jan. 9-18, 2019, document JVET-M1001, 2019.
Bross et al. “Versatile Video Coding (Draft 5),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 14th Meeting, Geneva, CH, Mar. 19-27, 2019, document JVET-N1001, 2019.
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.
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.
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.
Chen et al. “CE4: Separate List for Sub-Block Merge Candidates (Test 4.2.8),” 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-L0369, 2018.
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-00248, 2019.
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.
“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.
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-00127, 2019.
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.
Lu et al. “CE12: Mapping Functions (Test CE12-1 and CE12-2),” Joint Video Experts Team (JVET) of ITU-t SG 16 WP B and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting, Marrakech, MA, Jan. 9-18, 2019, document JVET-M0427, 2019.
Nam et al. “Non-CE8: Block Vector Predictor for IBC,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 12th Meeting, Macau, CN, Oct. 8-12, 2018, document JVET-L0159, 2018.
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, Mar. 27-Apr. 4, 2014, document JCTVC-Q0139, 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.
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, 25th Meeting, Chengdu, CN, Oct. 14-21, 2019, document JCTVC-Y1002, 2016.
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.
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.
Xu 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.
Xu et al. “CE8: CPR Reference Memory Reuse Without Reduced Memory Requirement (CE8.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.
Xu 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.
Xu 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, document JVET-N0251, 2019.
Xu 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.
Xu 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, document JVET-N0472, 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.
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.
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 Juy 12, 2021.
Non Final Office Action from U.S. Appl. No. 17/319,994 dated Juy 26, 2021.
Non Final Office Action from U.S. Appl. No. 17/320,033 dated Juy 27, 2021.
Alshin 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 1116th Meeting: San Jose, US, Jan. 9-17, 2014, document ICTVC-P0211, 2014.
Hannuksela et al. “AHG12: 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.
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 ITC 1/SC 29/WG 11 15th Meeting: Geneva, CH, Oct. 23-Nov. 1, 2013, document JCTVC-00183, 2013.
Wang 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, document JCTVC-R0141, 2014.
Xu 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, document JVET-L1028, 2018.
Xu 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 1113th Meeting: Marrakesh, MA, Jan. 9-18, 2019, document JVET-M0028, 2019.
Extended European Search Report from European Patent Application No. 20748417.1 dated Oct. 25, 2022 (11 pages).
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.
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-00352, 2013.
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.
Xu et al. “Intra Block Copy in HEVC Screen Content Coding Extensions,” IEEE Journal on Emerging and Selected Topics in Circuits and Systems, Dec. 2016, 6(4):409-419, XP011636923.
Xu 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, 12th Meeting, Macao, CN, Oct. 3-12, 2018, document JVET-L0297, 2018.
“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.
Extended European Search Report from European Patent Application No. 20766750.2 dated Feb. 18, 2022 (21 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.
“High Efficiency Video Coding,” ITU-T Telecommunication Standardization Sector of ITU, Series H: Audiovisual and Multimedia Systems, Infrastructure of Audiovisual Services—Coding of Moving Video, H.265, Apr. 2013.
Huang et al. “Fast Intra Prediction for HEVC Screen Content,” Journal of Optoelectronics—Laser, Jun. 2018, 29 (6):604-609.
Joshi et al. “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, document JCTVC-W1005, 2016.
Rosewarne et al. “HEVC Range Extensions Test Model 6 Encoder Description,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG16 WP3 and ISO/IEC JTC1/SC29/WG11 16th Meeting: San José, US, Jan. 9-17, 2014, document JCTVC-P1013, 2014.
Zuo et al. “Intra Block Copy for Intra-Frame Coding,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 10th Meeting: San Diego, US, Apr. 10-20, 2018, document JVET-J0042, 2018.
Office Action from Canadian Patent Application No. 3127848 dated Jun. 29, 2023 (5 pages).
Office Action from Canadian Patent Application No. 3146391 dated Jun. 27, 2023 (5 pages).
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/571,748 dated Sep. 14, 2023.
Non Final Office Action from U.S. Appl. No. 17/461,150 dated Sep. 15, 2023.
Non Final Office Action from U.S. Appl. No. 17/896,761 dated Aug. 4, 2023.
Non Final Office Action from U.S. Appl. No. 17/386,519 dated Oct. 5, 2023.
Final Office Action from U.S. Appl. No. 17/571,748 dated Jan. 11, 2024.
Non Final Office Action from U.S. Appl. No. 17/386,510 dated Jan. 16, 2024.
Final Office Action from U.S. Appl. No. 17/386,430 dated Feb. 22, 2024.
Non Final Office Action from U.S. Appl. No. 18/076,031 dated Feb. 26, 2024.
Office Action from Chinese Patent Application No. 202080011726.9 mailed Apr. 4, 2024.
Notice of Reasons for Refusal from Japanese Patent Application No. 2023-082519 mailed Jun. 18, 2024.

Related Publications (1)

	Number	Date	Country
	20210352279 A1	Nov 2021	US

Continuations (1)

	Number	Date	Country
Parent	PCT/CN2020/074160	Feb 2020	WO
Child	17386403		US

Prediction using intra-buffer samples for intra block copy in video coding

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Term Extension

Abstract

Description

Claims

Priority Claims (15)

CROSS REFERENCE TO RELATED APPLICATIONS

US Referenced Citations (188)

Foreign Referenced Citations (114)

Non-Patent Literature Citations (106)

Related Publications (1)

Continuations (1)