JP7287433B2 - Video encoding device, video encoding method, video encoding program, video decoding device, video decoding method, and video decoding program - Google Patents

Description

The present invention relates to image encoding and decoding techniques for dividing an image into blocks and performing prediction.

In image encoding and decoding, an image to be processed is divided into blocks each of which is a set of a predetermined number of pixels, and each block is processed. Encoding efficiency is improved by dividing into appropriate blocks and appropriately setting intra-prediction and inter-prediction.

Patent Literature 1 discloses an intra-prediction technique for obtaining a predicted image using decoded pixels adjacent to a block to be encoded/decoded.

JP 2009-246975 A

However, the technique of Patent Literature 1 uses only decoded pixels adjacent to a block to be encoded/decoded for prediction, resulting in poor prediction efficiency.

In one aspect of the present invention for solving the above problems, a block vector candidate deriving unit for deriving a block vector candidate of a block to be processed in a picture to be processed from coding information stored in a coding information storage memory; a selection unit that selects a selected block vector from candidates; and a reference position correction unit that corrects the reference position of the reference block referenced by the selected block vector so that the reference block is referenced inside a referable area, Based on the reference position of the reference block, decoded pixels in the target picture are obtained from the decoded image memory unit as predicted values of the target block.

According to the present invention, highly efficient image encoding/decoding processing can be realized with a low load.

1 is a block diagram of an image coding device according to an embodiment of the present invention; FIG. 1 is a block diagram of an image decoding device according to an embodiment of the present invention; FIG. FIG. 11 is a flowchart for explaining an operation of dividing a treeblock; FIG. FIG. 4 is a diagram showing how an input image is divided into treeblocks; FIG. 4 is a diagram for explaining z-scan; It is a figure which shows the division|segmentation shape of a block. It is a figure which shows the division|segmentation shape of a block. It is a figure which shows the division|segmentation shape of a block. It is a figure which shows the division|segmentation shape of a block. It is a figure which shows the division|segmentation shape of a block. 4 is a flowchart for explaining an operation of dividing a block into four; 4 is a flowchart for explaining an operation of dividing a block into two or three; This is the syntax for expressing the shape of block division. It is a figure for demonstrating intra prediction. It is a figure for demonstrating intra prediction. FIG. 4 is a diagram for explaining reference blocks for inter prediction; A syntax for expressing coding block prediction modes. A syntax for expressing coding block prediction modes. FIG. 4 is a diagram showing the correspondence between syntax elements and modes related to inter-prediction; FIG. 4 is a diagram for explaining affine transformation motion compensation of two control points; FIG. 4 is a diagram for explaining affine transformation motion compensation of three control points; 2 is a block diagram of a detailed configuration of inter prediction section 102 in FIG. 1. FIG. FIG. 17 is a block diagram of a detailed configuration of a normal motion vector predictor mode derivation unit 301 of FIG. 16; FIG. 17 is a block diagram of a detailed configuration of a normal merge mode derivation unit 302 of FIG. 16; 17 is a flowchart for explaining normal predicted motion vector mode derivation processing of the normal predicted motion vector mode deriving unit 301 of FIG. 16; FIG. 10 is a flowchart showing a processing procedure of normal motion vector predictor mode derivation processing; FIG. FIG. 10 is a flowchart for explaining a processing procedure of normal merge mode derivation processing; FIG. 3 is a block diagram of a detailed configuration of an inter prediction unit 203 in FIG. 2; FIG. FIG. 23 is a block diagram of a detailed configuration of a normal motion vector predictor mode derivation unit 401 of FIG. 22; FIG. 23 is a block diagram of a detailed configuration of a normal merge mode derivation unit 402 of FIG. 22; 23 is a flowchart for explaining normal predicted motion vector mode derivation processing of the normal predicted motion vector mode deriving unit 401 of FIG. 22; FIG. 10 is a diagram for explaining a history motion vector predictor candidate list initialization/update processing procedure; FIG. 10 is a flow chart of the same element confirmation processing procedure in the history motion vector predictor candidate list initialization/update processing procedure; FIG. FIG. 10 is a flowchart of an element shift processing procedure in the historical motion vector predictor candidate list initialization/update processing procedure; FIG. FIG. 10 is a flowchart for explaining a history motion vector predictor candidate derivation processing procedure; FIG. FIG. 11 is a flowchart for explaining history merge candidate derivation processing procedures; FIG. FIG. 10 is a diagram for explaining an example of history motion vector predictor candidate list update processing; FIG. 10 is a diagram for explaining an example of history motion vector predictor candidate list update processing; FIG. 10 is a diagram for explaining an example of history motion vector predictor candidate list update processing; FIG. 10 is a diagram for explaining motion compensation prediction in the case of L0 prediction in which the reference picture (RefL0Pic) of L0 is before the picture to be processed (CurPic); FIG. 11 is a diagram for explaining motion compensation prediction when L0 prediction is performed and the reference picture for L0 prediction is at a time after the picture to be processed; For explaining the prediction direction of motion compensated prediction in the case of bi-prediction where the reference picture for L0 prediction is before the picture to be processed and the reference picture for L1 prediction is after the picture to be processed. It is a diagram. FIG. 10 is a diagram for explaining the prediction direction of motion compensation prediction when bi-prediction is performed and the reference picture for L0 prediction and the reference picture for L1 prediction are located before the picture to be processed; FIG. 10 is a diagram for explaining the prediction direction of motion compensation prediction when bi-prediction is performed and the reference picture for L0 prediction and the reference picture for L1 prediction are located after the picture to be processed. 1 is a diagram for explaining an example of a hardware configuration of an encoding/decoding device according to an embodiment of the present invention; FIG. FIG. 11 is a flowchart for explaining an average merge candidate derivation processing procedure; FIG. FIG. 10 is a diagram illustrating a valid reference area for intra block copy; FIG. 10 is a diagram illustrating a valid reference area for intra block copy; FIG. 2 is a block diagram of a detailed configuration of an intra prediction unit 103 in FIG. 1; FIG. FIG. 3 is a block diagram of a detailed configuration of an intra prediction unit 204 in FIG. 2; FIG. 3 is a block diagram of an intra block copy prediction unit 352; FIG. 3 is a block diagram of an intra block copy prediction unit 362; FIG. FIG. 11 is a flowchart for explaining prediction intra block copy processing of an intra block copy prediction unit 352; FIG. FIG. 11 is a flowchart for explaining prediction intra block copy processing of an intra block copy prediction unit 362; FIG. FIG. 11 is a flowchart for explaining merge intra block copy processing; FIG. FIG. 11 is a flowchart showing a processing procedure of block vector mode derivation processing for predictive intra block copy; FIG. FIG. 11 is a diagram for explaining processing of a reference position correction unit 380 and a reference position correction unit 480; It is a figure which shows a mode that a reference position is correct|amended. FIG. 10 is a diagram for explaining upper left and lower right positions when the referable area is rectangular; FIG. 10 is a diagram for explaining upper left and lower right positions when the referable area is rectangular; FIG. 10 is a diagram for explaining upper left and lower right positions when the referable area is rectangular; FIG. 10 is a diagram for explaining upper left and lower right positions when the referable area is rectangular; FIG. 10 is a diagram illustrating processing for correcting a reference position in a portion where the referable area is not rectangular; It is a figure which shows a mode that a reference position is correct|amended. It is a figure which shows a mode that a reference position is correct|amended. FIG. 11 is a diagram for explaining processing of a reference position correction unit 380 and a reference position correction unit 480; FIG. 10 is a diagram illustrating how a referable area is decomposed into two; FIG. 10 is a diagram illustrating how a referable area is decomposed into two; FIG. 10 is a diagram illustrating how a referable area is decomposed into two; FIG. 10 is a diagram illustrating how a referable area is decomposed into two; FIG. 10 is a diagram illustrating processing for dividing a referable area into two and correcting each reference position;

Techniques and technical terms used in this embodiment are defined.

<Tree Block>
In the embodiment, an image to be encoded/decoded is equally divided into a predetermined size. This unit is defined as a treeblock. Although the size of the treeblock is 128×128 pixels in FIG. 4, the size of the treeblock is not limited to this, and any size may be set. The treeblock to be processed (corresponding to the encoding target in the encoding process and the decoding target in the decoding process) is switched in raster scan order, that is, from left to right and from top to bottom. The interior of each treeblock can be further recursively split. A block to be coded/decoded after recursively dividing the treeblock is defined as a coded block. Also, tree blocks and coding blocks are collectively defined as blocks. Appropriate block division enables efficient encoding. The size of the treeblock can be a fixed value that is prearranged between the encoding device and the decoding device, or can be configured such that the treeblock size determined by the encoding device is transmitted to the decoding device. Here, the maximum treeblock size is 128×128 pixels, and the minimum treeblock size is 16×16 pixels. Also, the maximum size of an encoding block is 64×64 pixels, and the minimum size of an encoding block is 4×4 pixels.

<Prediction mode>
Intra prediction (MODE_INTRA), in which prediction is performed from the processed image signal of the processing target image, and inter prediction (MODE_INTER), in which prediction is performed from the image signal of the processed image, are switched for each encoding block to be processed.

The processed image is used for the decoded image, image signal, tree block, block, coding block, etc. of the encoded signal in the encoding process, and is used for the decoded image, image signal, Used for treeblocks, blocks, coding blocks, etc.

A mode for distinguishing between intra prediction (MODE_INTRA) and inter prediction (MODE_INTER) is defined as a prediction mode (PredMode). The prediction mode (PredMode) has intra prediction (MODE_INTRA) or inter prediction (MODE_INTER) as a value.

<Intra block copy prediction>
Intra block copy prediction is a process of encoding/decoding a block to be processed by referring to decoded pixels in a picture to be processed as prediction values. The distance from the block to be processed to the pixel to be referred to is represented by a block vector. Since the block vector refers to the picture to be processed and the reference picture is uniquely determined, no reference index is required. The difference between a block vector and a motion vector is whether the picture referred to is a picture to be processed or a picture that has been processed. In addition, block vectors can be selected from 1-pixel precision or 4-pixel precision using adaptive motion vector resolution (AMVR).

In intra-block copy, two modes of predictive intra-block copy mode and merge intra-block copy mode can be selected.

The predictive intra block copy mode is a mode in which a block vector of a block to be processed is determined from a predictive block vector derived from processed information and a difference block vector. A predictive block vector is derived from a processed block adjacent to the block to be processed and an index for specifying the predictive block vector. An index for specifying a predicted block vector and a differential block vector are transmitted in a bitstream.

The merge intra block copy mode is a mode for deriving intra block copy prediction information of a block to be processed from intra block copy prediction information of processed blocks adjacent to the block to be processed without transmitting differential motion vectors.

<Inter Prediction>
In inter prediction, in which prediction is performed from image signals of processed images, a plurality of processed images can be used as reference pictures. In order to manage a plurality of reference pictures, two types of reference lists, L0 (reference list 0) and L1 (reference list 1), are defined, and reference pictures are specified using reference indices. L0 prediction (Pred_L0) is available for P slices. L0 prediction (Pred_L0), L1 prediction (Pred_L1), and bi-prediction (Pred_BI) are available for B slices. L0 prediction (Pred_L0) is inter prediction that refers to reference pictures managed by L0, and L1 prediction (Pred_L1) is inter prediction that refers to reference pictures that are managed by L1. Bi-prediction (Pred_BI) is inter-prediction in which both L0 prediction and L1 prediction are performed and one reference picture managed by each of L0 and L1 is referred to. Information specifying L0 prediction, L1 prediction, and bi-prediction is defined as an inter-prediction mode. In the subsequent processing, it is assumed that the constants and variables with the suffix LX attached to the output are processed for each of L0 and L1.

<Predicted motion vector mode>
The motion vector predictor mode is a mode in which an index for specifying a motion vector predictor, a differential motion vector, an inter prediction mode, and a reference index are transmitted, and inter prediction information of the block to be processed is determined. The motion vector predictor is a motion vector predictor candidate derived from a processed block adjacent to the target block or a block belonging to the processed image and located in the same position or in the vicinity of the target block (neighborhood), and a motion vector predictor. Derived from the index to identify the vector.

<Merge mode>
Merge mode is a processed block adjacent to the target block, or a block belonging to the processed image and located at the same position as the target block or its vicinity (neighborhood) without transmitting the differential motion vector and the reference index. This mode derives the inter prediction information of the block to be processed from the inter prediction information of the target block.

A processed block adjacent to the block to be processed and the inter prediction information of the processed block are defined as spatial merge candidates. A block belonging to a processed image and located at the same position as or in the vicinity (neighborhood) of the block to be processed and inter prediction information derived from the inter prediction information of the block are defined as temporal merge candidates. Each merging candidate is registered in a merging candidate list, and a merging candidate to be used in prediction of a block to be processed is specified by a merging index.

<Adjacent block>
FIG. 11 is a diagram illustrating reference blocks referred to for deriving inter prediction information in motion vector predictor mode and merge mode. A0, A1, A2, B0, B1, B2, and B3 are processed blocks adjacent to the target block. T0 is a block belonging to the processed image, and is a block located at or near (near) the same position as the processing target block in the processing target image.

A1 and A2 are blocks located on the left side of the target encoding block and adjacent to the target encoding block. B1 and B3 are blocks positioned above the target encoding block and adjacent to the target encoding block. A0, B0, and B2 are blocks positioned at the lower left, upper right, and upper left of the encoding block to be processed, respectively.

Details of how adjacent blocks are handled in motion vector predictor mode and merge mode will be described later.

<Affine transformation motion compensation>
Affine transform motion compensation divides a coding block into predetermined units of sub-blocks and individually determines a motion vector for each divided sub-block to perform motion compensation. The motion vector of each sub-block is derived from the inter-prediction information of a processed block adjacent to the target block or a block belonging to the processed image and located at or near the same position as the target block (neighborhood)1 Based on one or more control points. In this embodiment, the size of the sub-block is 4×4 pixels, but the size of the sub-block is not limited to this, and the motion vector may be derived in units of pixels.

FIG. 14 shows an example of affine transform motion compensation when there are two control points. In this case, the two control points have two parameters, a horizontal component and a vertical component. Therefore, an affine transformation with two control points is called a four-parameter affine transformation. CP1 and CP2 in FIG. 14 are control points.

FIG. 15 shows an example of affine transform motion compensation with three control points. In this case, the three control points have two parameters, a horizontal component and a vertical component. Therefore, an affine transformation with three control points is called a 6-parameter affine transformation. CP1, CP2, and CP3 in FIG. 15 are control points.

Affine transform motion compensation can be used in both predictive motion vector mode and merge mode. A mode in which affine transform motion compensation is applied in motion vector predictor mode is defined as sub-block motion vector predictor mode, and a mode in which affine transform motion compensation is applied in merge mode is defined as sub-block merge mode.

<Syntax of encoding block>
Syntax for expressing prediction modes of coding blocks will be described with reference to FIGS. 12A, 12B, and 13 . pred_mode_flag in FIG. 12A is a flag indicating whether or not it is inter prediction. If pred_mode_flag is 0, inter prediction is performed, and if pred_mode_flag is 1, intra prediction is performed. In the case of intra prediction, pred_mode_ibc_flag, which is a flag indicating intra block copy prediction, is sent. Send merge_flag if intra block copy prediction (pred_mode_ibc_flag=1). merge_flag is a flag indicating whether to use the merge intra block copy mode or the predictive intra block copy mode. If merge intra-block copy mode (merge_flag=1), send merge index merge_idx. If it is not intra block copy prediction (pred_mode_ibc_flag=0), normal intra prediction is performed, and normal intra prediction information intra_pred_mode is sent.

Send merge_flag in case of inter prediction. merge_flag is a flag indicating whether to set the merge mode or the motion vector predictor mode. In the case of the motion vector predictor mode (merge_flag=0), a flag inter_affine_flag indicating whether to apply the sub-block motion vector predictor mode is sent. If sub-block predictive motion vector mode is applied (inter_affine_flag=1), send cu_affine_type_flag. cu_affine_type_flag is a flag for determining the number of control points in the sub-block predicted motion vector mode.

On the other hand, in merge mode (merge_flag=1), send merge_subblock_flag in FIG. 12B. merge_subblock_flag is a flag indicating whether to apply the subblock merge mode. For subblock merge mode (merge_subblock_flag=1), send merge index merge_subblock_idx. On the other hand, if it is not subblock merge mode (merge_subblock_flag=0), send flag merge_triangle_flag indicating whether to apply triangle merge mode. If the triangle merge mode is applied (merge_triangle_flag=1), send the block splitting direction merge_triangle_split_dir and the merge triangle indices merge_triangle_idx0, merge_triangle_idx1 for each of the two split partitions. On the other hand, if the triangle merge mode is not applied (merge_triangle_flag=0), send the merge index merge_idx.

FIG. 13 shows the value of each syntax element for inter prediction and the corresponding prediction mode. merge_flag=0,inter_affine_flag=0 corresponds to normal predicted motion vector mode (Inter Pred Mode). merge_flag=0, inter_affine_flag=1 corresponds to the sub-block prediction motion vector mode (Inter Affine Mode). merge_flag=1,merge_subblock_flag=0,merge_trianlge_flag=0 corresponds to Merge Mode. merge_flag=1,merge_subblock_flag=0,merge_trianlge_flag=1 corresponds to Triangle Merge Mode. merge_flag=1,merge_subblock_flag=1 corresponds to subblock merge mode (Affine Merge Mode).

<POC>
POC (Picture Order Count) is a variable associated with a picture to be encoded, and is set to a value that increases by one according to the output order of pictures. Based on the POC value, it is possible to determine whether the pictures are the same, determine the sequential relationship between the pictures in the output order, and derive the distance between the pictures. For example, if two pictures have the same POC value, it can be determined that they are the same picture. When two pictures have different POC values, it can be determined that the picture with the smaller POC value is the picture to be output first, and the difference between the POCs of the two pictures determines the inter-picture distance in the time axis direction. show.
(First embodiment)
An image encoding device 100 and an image decoding device 200 according to the first embodiment of the present invention will be described.

FIG. 1 is a block diagram of an image coding device 100 according to the first embodiment. The image coding apparatus 100 of the embodiment includes a block division unit 101, an inter prediction unit 102, an intra prediction unit 103, a decoded image memory 104, a prediction method determination unit 105, a residual generation unit 106, and an orthogonal transform/quantization unit 107. , a bit string encoder 108 , an inverse quantization/inverse orthogonal transform unit 109 , a decoded image signal superimposing unit 110 , and an encoded information storage memory 111 .

The block division unit 101 recursively divides an input image to generate coding blocks. The block division unit 101 divides a block to be divided into 4 division units in the horizontal direction and the vertical direction, respectively, and a 2-3 division unit to divide the block into the division object in either the horizontal direction or the vertical direction. include. The block division unit 101 sets the generated coding block as a processing target coding block, and supplies the image signal of the processing target coding block to the inter prediction unit 102 , the intra prediction unit 103 and the residual generation unit 106 . Also, the block division section 101 supplies information indicating the determined recursive division structure to the bit string encoding section 108 . A detailed operation of the block division unit 101 will be described later.

The inter prediction unit 102 performs inter prediction of the encoding block to be processed. The inter prediction unit 102 derives a plurality of inter prediction information candidates from the inter prediction information stored in the encoded information storage memory 111 and the decoded image signal stored in the decoded image memory 104, A suitable inter-prediction mode is selected from among the plurality of derived candidates, and the selected inter-prediction mode and the predicted image signal corresponding to the selected inter-prediction mode are supplied to the prediction method determination unit 105 . A detailed configuration and operation of the inter prediction unit 102 will be described later.

The intra prediction unit 103 performs intra prediction on the encoding block to be processed. The intra prediction unit 103 refers to the decoded image signal stored in the decoded image memory 104 as a reference pixel, and performs intra prediction based on coding information such as an intra prediction mode stored in the coding information storage memory 111. to generate a predicted image signal. In intra prediction, the intra prediction unit 103 selects a suitable intra prediction mode from among a plurality of intra prediction modes, and generates a prediction image signal according to the selected intra prediction mode and the selected intra prediction mode. It is supplied to the determination unit 105 . A detailed configuration and operation of the intra prediction unit 103 will be described later.

The decoded image memory 104 stores the decoded image generated by the decoded image signal superimposing unit 110 . The decoded image memory 104 supplies the stored decoded image to the inter prediction unit 102 and the intra prediction unit 103 .

The prediction method determination unit 105 evaluates each of intra prediction and inter prediction using the coding information and the code amount of the residual, the distortion amount between the predicted image signal and the processing target image signal, etc. , to determine the best prediction mode. In the case of intra prediction, the prediction method determination unit 105 supplies intra prediction information such as an intra prediction mode to the bit stream encoding unit 108 as encoding information. In the case of inter-prediction merge mode, prediction method determination section 105 uses inter-prediction information such as a merge index and information indicating whether sub-block merge mode is selected (sub-block merge flag) as encoding information to bitstream encoding section 108. supply to In the case of the inter-prediction motion vector predictor mode, the prediction method determination unit 105 uses the inter-prediction mode, the motion vector predictor index, the reference indices of L0 and L1, the difference motion vector, and information indicating whether or not it is the sub-block predictor motion vector mode. Inter prediction information such as (sub-block prediction motion vector flag) is supplied to the bit string encoding unit 108 as encoding information. Furthermore, the prediction method determination unit 105 supplies the determined encoded information to the encoded information storage memory 111 . The prediction method determination unit 105 supplies the residual generation unit 106 and the prediction image signal to the decoded image signal superimposition unit 110 .

The residual generation unit 106 generates a residual by subtracting the prediction image signal from the image signal to be processed, and supplies the residual to the orthogonal transformation/quantization unit 107 .

Orthogonal transformation/quantization section 107 performs orthogonal transformation and quantization on the residual according to the quantization parameter to generate an orthogonal transformation/quantized residual, and converts the generated residual to bit string coding section 108. and the inverse quantization/inverse orthogonal transform unit 109 .

The bit stream encoding unit 108 encodes encoding information according to the prediction method determined by the prediction method determination unit 105 for each encoding block, in addition to the information for each sequence, picture, slice, and encoding block. Specifically, the bit string encoding unit 108 encodes the prediction mode PredMode for each encoding block. When the prediction mode is inter prediction (MODE_INTER), the bit stream coding unit 108 generates a flag for determining whether or not the merge mode, a sub-block merge flag, a merge index in the case of the merge mode, an inter prediction mode in the case of not the merge mode, Encoding information (inter prediction information) such as a motion vector predictor index, information about a motion vector difference, and a sub-block predictive motion vector flag is encoded according to a prescribed syntax (syntax rules for bit strings) to generate a first bit string. When the prediction mode is intra prediction (MODE_INTRA), the bitstream encoding unit 108 encodes a flag for determining whether or not it is an intra block copy according to a prescribed syntax. In the case of intra block copy, coding information (intra prediction information) such as a merge index in the merge mode, a predicted block vector index, a difference block vector in the non-merge mode, etc. is coded according to a prescribed syntax. In the case of non-intra block copy, coding information (intra prediction information) such as intra prediction mode is coded according to a prescribed syntax. A first bit string is generated by the above encoding. Further, bit string encoding section 108 entropy-encodes the orthogonally transformed and quantized residual according to a prescribed syntax to generate a second bit string. A bit stream encoding unit 108 multiplexes the first bit stream and the second bit stream according to a prescribed syntax, and outputs a bit stream.

The inverse quantization/inverse orthogonal transform unit 109 performs inverse quantization and inverse orthogonal transform on the orthogonal transform/quantized residual supplied from the orthogonal transform/quantization unit 107 to calculate the residual, and calculates the residual. The difference is supplied to the decoded image signal superimposing unit 110 .

The decoded image signal superimposition unit 110 superimposes the prediction image signal determined by the prediction method determination unit 105 and the residuals inversely quantized and inverse orthogonally transformed by the inverse quantization/inverse orthogonal transformation unit 109 to generate a decoded image. It is generated and stored in the decoded image memory 104 . Note that the decoded image signal superimposing unit 110 may store the decoded image in the decoded image memory 104 after performing a filtering process for reducing distortion such as block distortion due to encoding on the decoded image.

The coding information storage memory 111 stores coding information such as the prediction mode (inter prediction or intra prediction) determined by the prediction method determination unit 105 . In the case of inter prediction, the coding information stored in the coding information storage memory 111 includes inter prediction information such as the determined motion vector, the reference indices of the reference lists L0 and L1, and the historical motion vector predictor candidate list. In the case of the inter-prediction merge mode, the encoding information stored in the encoding information storage memory 111 includes, in addition to the above-described information, a merge index and information indicating whether or not the sub-block merge mode (sub-block merge flag ) contains inter-prediction information. In the case of the inter-prediction motion vector prediction mode, the encoding information stored in the encoding information storage memory 111 includes the above-mentioned information, as well as the inter-prediction mode, the prediction motion vector index, the differential motion vector, and the sub-block prediction. Inter prediction information such as information (sub-block predicted motion vector flag) indicating whether or not the motion vector mode is set is included. In the case of intra prediction, the coding information stored in the coding information storage memory 111 includes intra prediction information such as the determined intra prediction mode.

FIG. 2 is a block diagram showing the configuration of an image decoding device according to an embodiment of the present invention corresponding to the image encoding device of FIG. The image decoding apparatus according to the embodiment includes a bit stream decoding unit 201, a block division unit 202, an inter prediction unit 203, an intra prediction unit 204, a coding information storage memory 205, an inverse quantization/inverse orthogonal transformation unit 206, a decoded image signal superimposition unit. A section 207 and a decoded image memory 208 are provided.

The decoding process of the image decoding apparatus in FIG. 2 corresponds to the decoding process provided inside the image encoding apparatus in FIG. Each configuration of the orthogonal transform unit 206, the decoded image signal superimposition unit 207, and the decoded image memory 208 includes the encoded information storage memory 111, the inverse quantization/inverse orthogonal transform unit 109, and the decoded image signal of the image encoding apparatus in FIG. It has a function corresponding to each configuration of the superimposing unit 110 and the decoded image memory 104 .

The bitstream supplied to the bitstream decoding unit 201 is separated according to a prescribed syntax rule. The bit stream decoding unit 201 decodes the separated first bit stream to obtain information in units of sequences, pictures, slices, coding blocks, and coding information in units of coding blocks. Specifically, the bit string decoding unit 201 decodes a prediction mode PredMode that determines whether inter prediction (MODE_INTER) or intra prediction (MODE_INTRA) is performed in units of coding blocks. When the prediction mode is inter prediction (MODE_INTER), the bitstream decoding unit 201 generates a flag for determining whether or not it is the merge mode, a merge index and a sub-block merge flag in the case of the merge mode, and inter prediction in the case of the predicted motion vector mode. The coded information (inter prediction information) related to the mode, the predicted motion vector index, the differential motion vector, the sub-block predicted motion vector flag, etc. is decoded according to a prescribed syntax, and the coded information (inter prediction information) is sent to the inter prediction unit 203 and supplied to the encoding information storage memory 205 via the block division unit 202 . When the prediction mode is intra prediction (MODE_INTRA), the bit string decoding unit 201 decodes a flag for determining whether intra block copy is performed. In the case of intra block copy, encoded information (intra prediction information) such as a merge index in the merge mode, a predicted block vector index, a difference block vector in the non-merge mode, etc. is decoded according to a prescribed syntax. If it is not an intra block copy, the encoded information (intra prediction information) such as the intra prediction mode is decoded according to the specified syntax. Through the above decoding, the encoded information (intra prediction information) is supplied to the encoded information storage memory 205 via the inter prediction section 203 or intra prediction section 204 and the block dividing section 202 . The bit string decoding unit 201 decodes the separated second bit string, calculates the orthogonally transformed and quantized residual, and supplies the orthogonally transformed and quantized residual to the inverse quantization and inverse orthogonal transformation unit 206. do.

When the prediction mode PredMode of the encoding block to be processed is inter prediction (MODE_INTER) and motion vector prediction mode, the inter prediction unit 203 predicts the code of the already decoded image signal stored in the encoding information storage memory 205. Using the transformation information, a plurality of motion vector predictor candidates are derived, and the derived multiple motion vector predictor candidates are registered in a motion vector predictor candidate list described later. The inter prediction unit 203 selects a motion vector predictor corresponding to the motion vector predictor index decoded and supplied by the bit string decoding unit 201 from among a plurality of motion vector predictor candidates registered in the motion vector predictor candidate list, A motion vector is calculated from the differential motion vector decoded by the bit string decoding unit 201 and the selected predicted motion vector, and the calculated motion vector is stored in the encoded information storage memory 205 together with other encoded information. The coding information of the coding block supplied and stored here includes flags predFlagL0[xP][yP], predFlagL1[xP][yP], predFlagL1[xP][yP], Reference indices refIdxL0[xP][yP] and refIdxL1[xP][yP] of L0 and L1, motion vectors mvL0[xP][yP] and mvL1[xP][yP] of L0 and L1, and the like. Here, xP and yP are indices indicating the position of the upper left pixel of the coding block in the picture. When the prediction mode PredMode is inter prediction (MODE_INTER) and the inter prediction mode is L0 prediction (Pred_L0), the flag predFlagL0 indicating whether to use L0 prediction is 1, and the flag predFlagL1 indicating whether to use L1 prediction. is 0. When the inter prediction mode is L1 prediction (Pred_L1), the flag predFlagL0 indicating whether to use L0 prediction is 0, and the flag predFlagL1 indicating whether to use L1 prediction is 1. When the inter prediction mode is bi-prediction (Pred_BI), the flag predFlagL0 indicating whether to use L0 prediction and the flag predFlagL1 indicating whether to use L1 prediction are both 1. Furthermore, when the prediction mode PredMode of the encoding block to be processed is inter prediction (MODE_INTER) and merge mode, merge candidates are derived. A plurality of merging candidates are derived using the coding information of already decoded coding blocks stored in the coding information storage memory 205 and registered in a merge candidate list, which will be described later. A merge candidate corresponding to the merge index decoded and supplied by the bit string decoding unit 201 is selected from among the plurality of merge candidates, and a flag indicating whether to use the L0 prediction and L1 prediction of the selected merge candidate. predFlagL0[xP][yP], predFlagL1[xP][yP], L0, L1 reference index refIdxL0[xP][yP], refIdxL1[xP][yP], L0, L1 motion vector mvL0[xP][yP ], mvL1[xP][yP], etc. are stored in the encoded information storage memory 205 . Here, xP and yP are indices indicating the position of the upper left pixel of the coding block in the picture. A detailed configuration and operation of the inter prediction unit 203 will be described later.

The intra prediction unit 204 performs intra prediction when the prediction mode PredMode of the encoding block to be processed is intra prediction (MODE_INTRA). The encoded information decoded by the bit stream decoding unit 201 includes an intra prediction mode. The intra prediction unit 204 generates a prediction image signal by intra prediction from the decoded image signal stored in the decoded image memory 208 according to the intra prediction mode included in the encoded information decoded by the bit string decoding unit 201. and supplies the generated predicted image signal to the decoded image signal superimposing unit 207 . Since the intra prediction unit 204 corresponds to the intra prediction unit 103 of the image encoding device 100, it performs the same processing as the intra prediction unit 103.

The inverse quantization/inverse orthogonal transform unit 206 performs inverse orthogonal transform and inverse quantization on the orthogonal transform/quantized residual decoded by the bit stream decoding unit 201, and the inverse orthogonal transform/inverse quantization is performed. get the residuals.

The decoded image signal superimposing unit 207 performs inverse orthogonal transform/transform/ The decoded image signal is decoded by superimposing it with the inverse quantized residual, and the decoded decoded image signal is stored in the decoded image memory 208 . When storing the decoded image in the decoded image memory 208, the decoded image signal superimposing unit 207 may store the decoded image in the decoded image memory 208 after performing a filtering process for reducing block distortion due to encoding on the decoded image. .

Next, the operation of the block dividing section 101 in the image encoding device 100 will be described. FIG. 3 is a flowchart illustrating the operation of dividing an image into treeblocks and subdividing each treeblock. First, an input image is divided into tree blocks of a predetermined size (step S1001). Each treeblock is scanned in a predetermined order, that is, in raster scan order (step S1002), and the inside of the treeblock to be processed is divided (step S1003).

FIG. 7 is a flow chart showing the detailed operation of the division processing in step S1003. First, it is determined whether or not to divide the block to be processed into four (step S1101).

When it is determined that the block to be processed is to be divided into four, the block to be processed is divided into four (step S1102). Each block obtained by dividing the block to be processed is scanned in the order of Z scanning, that is, upper left, upper right, lower left, and lower right (step S1103). FIG. 5 is an example of the Z scan order, and 601 in FIG. 6A is an example of dividing the block to be processed into four. Numbers 0 to 3 in 601 in FIG. 6A indicate the order of processing. Then, the division processing in FIG. 7 is recursively executed for each block divided in step S1101 (step S1104).

If it is determined that the block to be processed is not divided into 4, it is divided into 2-3 (step S1105).

FIG. 8 is a flow chart showing the detailed operation of the 2-3 division processing in step S1105. First, it is determined whether or not to divide the block to be processed into 2-3, that is, whether to divide into 2 or 3 (step S1201).

If it is determined not to divide the block to be processed into 2-3, that is, if it is determined not to divide, the division ends (step S1211). That is, no further recursive division processing is performed on the blocks divided by the recursive division processing.

If it is determined to divide the block to be processed into 2 or 3, it is determined whether to further divide the block to be processed into two (step S1202).

If it is determined that the block to be processed is to be divided into two, it is determined whether or not to divide the block to be processed vertically (vertically) (step S1203). It is divided into two (step S1204), or the block to be processed is horizontally divided into two (step S1205). As a result of step S1204, the block to be processed is divided into upper and lower (vertical direction) halves, as indicated by 602 in FIG. 6B. direction) is divided into two divisions.

If it is determined in step S1202 that the block to be processed is not to be divided into two, that is, if it is determined to be divided into three, it is determined whether to divide the block to be processed into upper, middle and lower (vertical) directions (step S1206). ), based on the result, divides the block to be processed into three parts (vertical direction) (step S1207), or divides the block to be processed into three parts (horizontal direction) (step S1208). As a result of step S1207, the block to be processed is divided into three parts (upper, middle and lower (vertical direction)) as indicated by 603 in FIG. 6C. Middle right (horizontal direction) is divided into three divisions.

After executing any one of steps S1204, S1205, S1207, and S1208, each block obtained by dividing the block to be processed is scanned from left to right and from top to bottom (step S1209). Numbers 0 to 2 of 602 to 605 in FIGS. 6B to 6E indicate the order of processing. The 2-3 division process of FIG. 8 is recursively executed for each divided block (step S1210).

In the recursive block division described here, necessity of division may be restricted by the number of divisions, the size of the block to be processed, or the like. Information that limits whether or not division is necessary may be implemented by a configuration in which information is not transmitted by prior agreement between the encoding device and the decoding device, or the coding device may limit whether or not division is necessary. It may be realized by a configuration in which the information to be used is determined, recorded in a bit string, and transmitted to the decoding device.

When a certain block is divided, the block before division is called a parent block, and each block after division is called a child block.

Next, the operation of the block dividing section 202 in the image decoding device 200 will be described. The block dividing unit 202 divides the treeblocks in the same processing procedure as the block dividing unit 101 of the image encoding device 100 . However, the block division unit 101 of the image encoding device 100 applies optimization techniques such as estimation of the optimum shape by image recognition and distortion rate optimization to determine the optimum block division shape, whereas the image decoding device The block division unit 202 in 200 is different in that the block division shape is determined by decoding the block division information recorded in the bit string.

FIG. 9 shows the syntax (syntax rules for bit strings) relating to block division in the first embodiment. coding_quadtree( ) represents the syntax for quartering blocks. multi_type_tree( ) represents the syntax for dividing a block into two or three. qt_split is a flag indicating whether to divide a block into four. Set qt_split=1 when dividing a block into four, and set qt_split=0 when not dividing a block into four. When dividing into 4 (qt_split=1), recursively divide each block into 4 (coding_quadtree(0), coding_quadtree(1), coding_quadtree(2), coding_quadtree(3), arguments 0 to 3 corresponds to the number 601 in FIG. 6A). When not splitting into 4 (qt_split=0), subsequent splitting is determined according to multi_type_tree(). mtt_split is a flag indicating whether or not to further split. When further splitting is performed (mtt_split=1), mtt_split_vertical, which is a flag indicating whether to split vertically or horizontally, and mtt_split_binary, which is a flag for determining whether to split into two or three, are transmitted. mtt_split_vertical=1 indicates splitting in the vertical direction, and mtt_split_vertical=0 indicates splitting in the horizontal direction. mtt_split_binary=1 indicates splitting into two, and mtt_split_binary=0 indicates splitting into three. When splitting into two (mtt_split_binary=1), each block split into two is recursively split (multi_type_tree(0), multi_type_tree(1), arguments 0 to 1 are 602 or 604 in FIGS. number.). When dividing into three (mtt_split_binary=0), each block divided into three is recursively divided (multi_type_tree(0), multi_type_tree(1), multi_type_tree(2), 0 to 2 are 603 in FIG. 6B or corresponding to the 605 number of 6E). Perform hierarchical block splitting by recursively calling multi_type_tree until mtt_split=0.

<Intra prediction>
The intra prediction method according to the embodiment is implemented in the intra prediction unit 103 of the image encoding device 100 in FIG. 1 and the intra prediction unit 204 of the image decoding device 200 in FIG.

An intra-prediction method according to an embodiment will be described with reference to the drawings. The intra-prediction method is implemented in both encoding and decoding processes in units of encoded blocks.

<Explanation of Intra Predictor 103 on Encoding Side>
FIG. 40 is a diagram showing the detailed configuration of the intra prediction unit 103 of the image encoding device 100 of FIG. The normal intra prediction unit 351 generates a predicted image signal by normal intra prediction from decoded pixels adjacent to the encoding block to be processed, selects a suitable intra prediction mode from among a plurality of intra prediction modes, and selects The selected intra prediction mode and the predicted image signal corresponding to the selected intra prediction mode are supplied to the prediction method determination unit 105 . An example of intra prediction is shown in FIGS. 10A and 10B. FIG. 10A shows the correspondence between prediction directions of normal intra prediction and intra prediction mode numbers. For example, intra-prediction mode 50 produces intra-predicted images by copying pixels vertically. Intra-prediction mode 1 is a DC mode, and is a mode in which all pixel values of a block to be processed are average values of reference pixels. Intra prediction mode 0 is a planar mode, and is a mode in which a two-dimensional intra prediction image is created from reference pixels in the vertical and horizontal directions. FIG. 10B is an example of generating an intra prediction image in intra prediction mode 40 . The value of the reference pixel in the direction indicated by the intra prediction mode is copied to each pixel of the block to be processed. When the reference pixel in the intra prediction mode is not at the integer position, the reference pixel value is determined by interpolation from the reference pixel values at the surrounding integer positions.

The intra-block copy prediction unit 352 acquires the decoded region of the same image signal as the encoding block to be processed from the decoded image memory 104, generates a prediction image signal by intra-block copy processing, and predicts the prediction method determination unit 105. supply to A detailed configuration and processing of the intra block copy prediction unit 352 will be described later.

<Description of Intra Predictor 204 on the Decoding Side>
FIG. 41 is a diagram showing the detailed configuration of the intra prediction section 204 of the image decoding device 200 of FIG.

The normal intra prediction unit 361 generates a predicted image signal by normal intra prediction from decoded pixels adjacent to the encoding block to be processed, selects a suitable intra prediction mode from among a plurality of intra prediction modes, and selects A predicted image signal corresponding to the selected intra prediction mode and the selected intra prediction mode is obtained. This predicted image signal is supplied to the decoded image signal superimposing unit 207 via the switch 364 . Since the processing of the normal intra prediction unit 361 in FIG. 41 corresponds to the normal intra prediction unit 351 in FIG. 40, detailed description thereof will be omitted.

The intra block copy prediction unit 362 acquires the decoded area of the same image signal as the encoding block to be processed from the decoded image memory 208, and obtains a predicted image signal by intra block copy processing. This predicted image signal is supplied to the decoded image signal superimposing unit 207 via the switch 364 . A detailed configuration and processing of the intra block copy prediction unit 362 will be described later.

<Inter Prediction>
The inter prediction method according to the embodiment is implemented in the inter prediction unit 102 of the image coding device in FIG. 1 and the inter prediction unit 203 of the image decoding device in FIG.

An inter-prediction method according to an embodiment will be described with reference to the drawings. The inter-prediction method is implemented in both encoding and decoding processes in units of encoded blocks.

<Description of inter prediction unit 102 on the encoding side>
FIG. 16 is a diagram showing a detailed configuration of the inter prediction unit 102 of the image coding apparatus of FIG. 1. As shown in FIG. The normal motion vector predictor mode deriving unit 301 derives a plurality of normal motion vector predictor candidates, selects a motion vector predictor, and calculates a differential motion vector between the selected motion vector predictor and the detected motion vector. The detected inter prediction mode, reference index, motion vector, and calculated differential motion vector are the inter prediction information of the normal predicted motion vector mode. This inter prediction information is supplied to the inter prediction mode determination unit 305 . The detailed configuration and processing of the normal motion vector predictor mode derivation unit 301 will be described later.

A normal merge mode derivation unit 302 derives a plurality of normal merge candidates, selects a normal merge candidate, and obtains inter prediction information in the normal merge mode. This inter prediction information is supplied to the inter prediction mode determination unit 305 . The detailed configuration and processing of the normal merge mode derivation unit 302 will be described later.

A sub-block predictor motion vector mode derivation unit 303 derives a plurality of sub-block predictor motion vector candidates, selects a sub-block predictor motion vector, and calculates a differential motion vector between the selected sub-block predictor motion vector and the detected motion vector. calculate. The detected inter prediction mode, reference index, motion vector, and calculated differential motion vector are inter prediction information for the sub-block prediction motion vector mode. This inter prediction information is supplied to the inter prediction mode determination unit 305 .

A sub-block merging mode derivation unit 304 derives a plurality of sub-block merging candidates, selects a sub-block merging candidate, and obtains inter-prediction information for the sub-block merging mode. This inter prediction information is supplied to the inter prediction mode determination unit 305 .

Based on the inter prediction information supplied from the normal prediction motion vector mode derivation unit 301, the normal merge mode derivation unit 302, the sub-block prediction motion vector mode derivation unit 303, and the sub-block merge mode derivation unit 304, the inter prediction mode determination unit 305 , to determine the inter-prediction information. Inter prediction information according to the determination result is supplied from the inter prediction mode determination unit 305 to the motion compensation prediction unit 306 .

Based on the determined inter prediction information, the motion compensation prediction unit 306 performs inter prediction on the reference image signal stored in the decoded image memory 104 . A detailed configuration and processing of the motion compensation prediction unit 306 will be described later.

<Description of Inter Predictor 203 on the Decoding Side>
FIG. 22 is a diagram showing the detailed configuration of the inter prediction unit 203 of the image decoding device in FIG.

The normal motion vector predictor mode derivation unit 401 derives a plurality of normal motion vector predictor candidates, selects a motion vector predictor, calculates the sum of the selected motion vector predictor and the decoded differential motion vector, and calculates the motion vector. do. The decoded inter prediction mode, reference index, and motion vector become inter prediction information for the normal predicted motion vector mode. This inter prediction information is supplied to the motion compensation prediction section 406 via the switch 408 . The detailed configuration and processing of the normal motion vector predictor mode derivation unit 401 will be described later.

A normal merge mode derivation unit 402 derives a plurality of normal merge candidates, selects a normal merge candidate, and obtains inter prediction information in the normal merge mode. This inter prediction information is supplied to the motion compensation prediction section 406 via the switch 408 . The detailed configuration and processing of the normal merge mode derivation unit 402 will be described later.

The sub-block predictor motion vector mode derivation unit 403 derives a plurality of sub-block predictor motion vector candidates, selects a sub-block predictor motion vector, and calculates the sum of the selected sub-block predictor motion vector and the decoded differential motion vector. It is calculated as a motion vector. The decoded inter prediction mode, reference index, and motion vector become inter prediction information for the sub-block prediction motion vector mode. This inter prediction information is supplied to the motion compensation prediction section 406 via the switch 408 .

A sub-block merging mode deriving unit 404 derives a plurality of sub-block merging candidates, selects a sub-block merging candidate, and obtains inter-prediction information for the sub-block merging mode. This inter prediction information is supplied to the motion compensation prediction section 406 via the switch 408 .

Based on the determined inter prediction information, the motion compensation prediction unit 406 performs inter prediction on the reference image signal stored in the decoded image memory 208 . The detailed configuration and processing of the motion compensation prediction unit 406 are the same as those of the motion compensation prediction unit 306 on the encoding side.

<Normal predicted motion vector mode derivation unit (normal AMVP)>
The normal motion vector predictor mode deriving unit 301 in FIG. A vector detection unit 326 , a motion vector predictor candidate selection unit 327 and a motion vector subtraction unit 328 are included.

The normal motion vector predictor mode deriving unit 401 in FIG. A vector candidate selection unit 426 and a motion vector addition unit 427 are included.

Processing procedures of the normal predicted motion vector mode deriving unit 301 on the encoding side and the normal predicted motion vector mode deriving unit 401 on the decoding side will be described with reference to the flowcharts of FIGS. 19 and 25, respectively. FIG. 19 is a flowchart showing the normal predicted motion vector mode derivation processing procedure by the normal motion vector mode derivation unit 301 on the encoding side, and FIG. 25 is the normal predicted motion vector mode derivation processing by the normal motion vector mode derivation unit 401 on the decoding side. It is a flow chart which shows a procedure.

<Normal predicted motion vector mode derivation unit (normal AMVP): description on the encoding side>
A normal motion vector prediction mode derivation processing procedure on the encoding side will be described with reference to FIG. In the description of the processing procedure in FIG. 19, the term "normal" shown in FIG. 19 may be omitted.

First, the normal motion vector detection unit 326 detects a normal motion vector for each inter prediction mode and reference index (step S100 in FIG. 19).

Subsequently, a spatial motion vector predictor candidate deriving unit 321, a temporal motion vector predictor candidate deriving unit 322, a historical motion vector predictor candidate deriving unit 323, a motion vector predictor candidate supplementing unit 325, a motion vector predictor candidate selecting unit 327, and a motion vector subtracting unit. At 328, differential motion vectors of motion vectors used for inter prediction in normal motion vector predictor mode are calculated for each of L0 and L1 (steps S101 to S106 in FIG. 19). Specifically, when the prediction mode PredMode of the block to be processed is inter prediction (MODE_INTER) and the inter prediction mode is L0 prediction (Pred_L0), the L0 motion vector predictor candidate list mvpListL0 is calculated and the motion vector predictor mvpL0 is selected. Then, the difference motion vector mvdL0 of the motion vector mvL0 of L0 is calculated. When the inter prediction mode of the block to be processed is L1 prediction (Pred_L1), the L1 motion vector predictor candidate list mvpListL1 is calculated, the motion vector predictor mvpL1 is selected, and the differential motion vector mvdL1 of the L1 motion vector mvL1 is calculated. . When the inter prediction mode of the block to be processed is bi-prediction (Pred_BI), both L0 prediction and L1 prediction are performed, L0 motion vector predictor candidate list mvpListL0 is calculated, L0 motion vector predictor mvpL0 is selected, and L0 Calculates the differential motion vector mvdL0 of the motion vector mvL0 of L1, calculates the motion vector predictor candidate list mvpListL1 of L1, calculates the predicted motion vector mvpL1 of L1, and calculates the differential motion vector mvdL1 of the motion vector mvL1 of L1. do.

Differential motion vector calculation processing is performed for each of L0 and L1, and the processing is common to both L0 and L1. Therefore, L0 and L1 are represented as common LX in the following description. X of LX is 0 in the process of calculating the differential motion vector of L0, and X of LX is 1 in the process of calculating the differential motion vector of L1. Also, when referring to the information of the other list instead of LX during the process of calculating the differential motion vector of LX, the other list is represented as LY.

If the LX motion vector mvLX is used (step S102 in FIG. 19: YES), the LX motion vector predictor candidates are calculated and the LX motion vector predictor candidate list mvpListLX is constructed (step S103 in FIG. 19). A spatial motion vector predictor candidate deriving unit 321, a temporal motion vector predictor candidate deriving unit 322, a historical motion vector predictor candidate deriving unit 323, and a motion vector predictor candidate supplementing unit 325 in the normal motion vector predictor mode deriving unit 301 generate multiple predicted motions. A motion vector predictor candidate list mvpListLX is constructed by deriving vector candidates. A detailed processing procedure of step S103 in FIG. 19 will be described later using the flowchart in FIG.

Subsequently, the motion vector predictor candidate selection unit 327 selects the LX motion vector predictor mvpLX from the LX motion vector predictor candidate list mvpListLX (step S104 in FIG. 19). Here, one element (i-th element counting from 0) in the motion vector predictor candidate list mvpListLX is represented as mvpListLX[i]. A motion vector difference between the motion vector mvLX and each motion vector predictor candidate mvpListLX[i] stored in the motion vector predictor candidate list mvpListLX is calculated. A code amount when the differential motion vectors are coded is calculated for each element (motion vector predictor candidate) of the motion vector predictor candidate list mvpListLX. Then, among the elements registered in the motion vector predictor candidate list mvpListLX, the motion vector predictor candidate mvpListLX[i] having the minimum code amount for each motion vector predictor candidate is selected as the motion vector predictor mvpLX. Get index i. If there are multiple motion vector predictor candidates with the smallest amount of generated code in the motion vector predictor candidate list mvpListLX, the motion vector predictor candidate list mvpListLX with a small index i is indicated by a small number. is selected as the optimal motion vector predictor mvpLX, and its index i is obtained.

Subsequently, the motion vector subtraction unit 328 subtracts the selected predicted motion vector mvpLX of LX from the motion vector mvLX of LX,
mvdLX = mvLX - mvpLX
, the differential motion vector mvdLX of LX is calculated (step S105 in FIG. 19).

<Normal predicted motion vector mode derivation unit (normal AMVP): description on the decoding side>
Next, the decoding-side normal predicted motion vector mode processing procedure will be described with reference to FIG. On the decoding side, the spatial motion vector predictor candidate deriving unit 421, the temporal motion vector predictor candidate deriving unit 422, the historical motion vector predictor candidate deriving unit 423, and the motion vector predictor candidate supplementing unit 425 use inter prediction in normal motion vector predictor mode. A motion vector is calculated for each of L0 and L1 (steps S201 to S206 in FIG. 25). Specifically, when the prediction mode PredMode of the block to be processed is inter prediction (MODE_INTER) and the inter prediction mode of the block to be processed is L0 prediction (Pred_L0), the L0 motion vector predictor candidate list mvpListL0 is calculated and the predicted motion Select the vector mvpL0 and calculate the motion vector mvL0 of L0. When the inter prediction mode of the block to be processed is L1 prediction (Pred_L1), the L1 motion vector predictor candidate list mvpListL1 is calculated, the motion vector predictor mvpL1 is selected, and the L1 motion vector mvL1 is calculated. When the inter prediction mode of the block to be processed is bi-prediction (Pred_BI), both L0 prediction and L1 prediction are performed, L0 motion vector predictor candidate list mvpListL0 is calculated, L0 motion vector predictor mvpL0 is selected, and L0 L1's motion vector mvL0 is calculated, L1's motion vector predictor candidate list mvpListL1 is calculated, L1's predicted motion vector mvpL1 is calculated, and L1's motion vector mvL1 is calculated.

Similar to the encoding side, the decoding side also performs motion vector calculation processing for each of L0 and L1, but the processing is common to both L0 and L1. Therefore, L0 and L1 are represented as common LX in the following description. LX represents an inter-prediction mode used for inter-prediction of a coding block to be processed. X is 0 in the process of calculating the motion vector of L0, and X is 1 in the process of calculating the motion vector of L1. Also, when referring to the information of another reference list instead of the same reference list as that of LX to be calculated during the process of calculating the motion vector of LX, the other reference list is represented as LY.

If the LX motion vector mvLX is to be used (step S202 in FIG. 25: YES), LX motion vector predictor candidates are calculated to construct the LX motion vector predictor candidate list mvpListLX (step S203 in FIG. 25). A spatial motion vector predictor candidate deriving unit 421, a temporal motion vector predictor candidate deriving unit 422, a historical motion vector predictor candidate deriving unit 423, and a motion vector predictor candidate supplementing unit 425 in the normal motion vector predictor mode deriving unit 401 generate a plurality of predicted motions. Vector candidates are calculated and a motion vector predictor candidate list mvpListLX is constructed. A detailed processing procedure of step S203 in FIG. 25 will be described later using the flowchart in FIG.

Subsequently, the motion vector predictor candidate selection unit 426 selects a motion vector predictor candidate mvpListLX[mvpIdxLX] corresponding to the motion vector predictor index mvpIdxLX decoded and supplied by the bit string decoding unit 201 from the motion vector predictor candidate list mvpListLX. fetched as the predicted motion vector mvpLX (step S204 in FIG. 25).

Subsequently, the motion vector addition unit 427 adds the differential motion vector mvdLX of LX and the predicted motion vector mvpLX of LX, which are decoded and supplied by the bit string decoding unit 201, and
mvLX = mvpLX + mvdLX
, the motion vector mvLX of LX is calculated (step S205 in FIG. 25).

<Normal Predictive Motion Vector Mode Derivation Unit (Normal AMVP): Motion Vector Prediction Method>
FIG. 20 shows normal predicted motion vector mode derivation having functions common to the normal predicted motion vector mode derivation unit 301 of the image coding device and the normal predicted motion vector mode derivation unit 401 of the image decoding device according to the embodiment of the present invention. 4 is a flowchart showing a processing procedure of processing;

The normal motion vector predictor mode deriving unit 301 and the normal motion vector predictor mode deriving unit 401 have a motion vector predictor candidate list mvpListLX. The motion vector predictor candidate list mvpListLX has a list structure, and is provided with a storage area for storing, as elements, motion vector predictor indexes indicating locations in the motion vector predictor candidate list and motion vector predictor candidates corresponding to the indexes. . The number of the motion vector predictor index starts from 0, and the motion vector predictor candidates are stored in the storage area of the motion vector predictor candidate list mvpListLX. In this embodiment, the motion vector predictor candidate list mvpListLX can register at least two motion vector predictor candidates (inter prediction information). Furthermore, 0 is set to a variable numCurrMvpCand indicating the number of motion vector predictor candidates registered in the motion vector predictor candidate list mvpListLX.

Spatial motion vector predictor candidate deriving units 321 and 421 derive a motion vector predictor candidate from the left adjacent block. In this process, the inter prediction information of the left adjacent block (A0 or A1 in FIG. 11), that is, the flag indicating whether or not the motion vector predictor candidate can be used, the motion vector, the reference index, etc., are referred to. A vector mvLXA is derived, and the derived mvLXA is added to the motion vector predictor candidate list mvpListLX (step S301 in FIG. 20). Note that X is 0 for L0 prediction, and X is 1 for L1 prediction (same below). Subsequently, the spatial motion vector predictor candidate deriving units 321 and 421 derive motion vector predictor candidates from the upper adjacent block. In this process, the inter prediction information of the upper adjacent block (B0, B1, or B2 in FIG. 11), that is, the flag indicating whether or not the motion vector predictor candidate can be used, the motion vector, the reference index, etc. are referred to. If mvLXA and mvLXB thus derived are not equal, mvLXB is added to the motion vector predictor candidate list mvpListLX (step S302 in FIG. 20). The processes of steps S301 and S302 in FIG. 20 are common except that the positions and numbers of adjacent blocks to be referred to are different, and flag availableFlagLXN indicating whether or not the motion vector predictor candidate of the coding block is available, and motion vector mvLXN. , reference indices refIdxN (N indicates A or B, and so on).

Subsequently, the temporal motion vector predictor candidate deriving units 322 and 422 derive candidate motion vector predictors from blocks in a picture whose time is different from that of the current picture to be processed. In this process, a flag availableFlagLXCol, which indicates whether or not motion vector predictor candidates for coding blocks in pictures at different times are available, motion vector mvLXCol, reference index refIdxCol, and reference list listCol are derived. Add to list mvpListLX (step S303 in FIG. 20).

Note that the processing of the temporal motion vector predictor candidate deriving units 322 and 422 can be omitted in units of sequences (SPS), pictures (PPS), or slices.

Subsequently, the historical motion vector predictor candidate deriving units 323 and 423 add the historical motion vector predictor candidates registered in the historical motion vector predictor candidate list HmvpCandList to the motion vector predictor candidate list mvpListLX. (Step S304 in FIG. 20). Details of the registration processing procedure in step S304 will be described later using the flowchart of FIG.

Subsequently, the motion vector predictor candidate supplementing units 325 and 425 add motion vector predictor candidates of predetermined values such as (0, 0) until the motion vector predictor candidate list mvpListLX is filled (S305 in FIG. 20).

<Normal merge mode derivation unit (normal merge)>
The normal merge mode derivation unit 302 in FIG. including.

The normal merge mode derivation unit 402 in FIG. 24 includes a spatial merge candidate derivation unit 441, a temporal merge candidate derivation unit 442, an average merge candidate derivation unit 444, a history merge candidate derivation unit 445, a merge candidate supplement unit 446, and a merge candidate selection unit 447. including.

FIG. 21 illustrates the procedure of normal merge mode derivation processing having functions common to the normal merge mode derivation unit 302 of the image coding device and the normal merge mode derivation unit 402 of the image decoding device according to the embodiment of the present invention. It is a flow chart.

The various processes will be described below in order. In the following description, unless otherwise specified, the slice type slice_type is B slice, but it can also be applied to P slice. However, when the slice type slice_type is a P slice, there is only L0 prediction (Pred_L0) as an inter prediction mode, and there is no L1 prediction (Pred_L1) or bi-prediction (Pred_BI), so processing related to L1 can be omitted.

The normal merge mode derivation unit 302 and the normal merge mode derivation unit 402 have a merge candidate list mergeCandList. The merge candidate list mergeCandList has a list structure, and is provided with a merge index indicating the location in the merge candidate list and a storage area for storing the merge candidate corresponding to the index as an element. The number of the merge index starts from 0, and the merge candidates are stored in the storage area of the merge candidate list mergeCandList. In the subsequent processing, merge candidates with merge index i registered in the merge candidate list mergeCandList are represented by mergeCandList[i]. In this embodiment, the merge candidate list mergeCandList can register at least six merge candidates (inter prediction information). Furthermore, 0 is set to the variable numCurrMergeCand indicating the number of merge candidates registered in the merge candidate list mergeCandList.

The spatial merging candidate deriving unit 341 and the spatial merging candidate deriving unit 441 extract the block to be processed from the encoding information stored in the encoding information storage memory 111 of the image encoding device or the encoding information storage memory 205 of the image decoding device. (B1, A1, B0, A0, B2 in FIG. 11) are derived in the order of B1, A1, B0, A0, B2, and the derived spatial merge candidates are referred to as merge candidates It is registered in the list mergeCandList (step S401 in FIG. 21). Here we define N to denote either B1, A1, B0, A0, B2 or a temporal merge candidate Col. Flag availableFlagN indicating whether or not inter prediction information of block N can be used as a spatial merge candidate, L0 reference index refIdxL0N and L1 reference index refIdxL1N of spatial merge candidate N, L0 prediction indicating whether or not L0 prediction is performed A flag predFlagL0N and an L1 prediction flag predFlagL1N indicating whether L1 prediction is performed, a motion vector mvL0N of L0, and a motion vector mvL1N of L1 are derived. However, in the present embodiment, merging candidates are derived without referring to the inter prediction information of the blocks included in the encoding block to be processed, so the inter prediction information of the blocks included in the encoding block to be processed We do not derive spatial merge candidates using

Subsequently, the temporal merge candidate derivation unit 342 and the temporal merge candidate derivation unit 442 derive temporal merge candidates from pictures at different times, and register the derived temporal merge candidates in the merge candidate list mergeCandList (see FIG. 21). step S402). A flag availableFlagCol indicating whether the temporal merge candidate is available, an L0 prediction flag predFlagL0Col indicating whether L0 prediction of the temporal merge candidate is performed, and an L1 prediction flag predFlagL1Col indicating whether L1 prediction is performed, and L0 motion vector mvL0Col of L1 and motion vector mvL1Col of L1 are derived.

It is assumed that the processing of the temporal merge candidate derivation unit 342 and the temporal merge candidate derivation unit 442 can be omitted for each sequence (SPS), picture (PPS), or slice.

Subsequently, the history merge candidate derivation unit 345 and the history merge candidate derivation unit 445 register the history motion vector predictor candidates registered in the history motion vector predictor candidate list HmvpCandList in the merge candidate list mergeCandList (step S403 in FIG. 21). .

Note that if the number of merge candidates numCurrMergeCand registered in the merge candidate list mergeCandList is smaller than the maximum number of merge candidates MaxNumMergeCand, the number of merge candidates numCurrMergeCand registered in the merge candidate list mergeCandList does not exceed the maximum number of merge candidates MaxNumMergeCand. History merge candidates are derived and registered in the merge candidate list mergeCandList.

Subsequently, the average merge candidate derivation unit 344 and the average merge candidate derivation unit 444 derive average merge candidates from the merge candidate list mergeCandList and add the derived average merge candidates to the merge candidate list mergeCandList (step in FIG. 21). S404).

Note that if the number of merge candidates numCurrMergeCand registered in the merge candidate list mergeCandList is smaller than the maximum number of merge candidates MaxNumMergeCand, the number of merge candidates numCurrMergeCand registered in the merge candidate list mergeCandList does not exceed the maximum number of merge candidates MaxNumMergeCand. Average merge candidates are derived and registered in the merge candidate list mergeCandList.

Here, the average merge candidate is a new motion vector obtained by averaging the motion vectors of the first merge candidate and the second merge candidate registered in the merge candidate list mergeCandList for each of L0 prediction and L1 prediction. is a good merge candidate.

Subsequently, in the merge candidate supplementing unit 346 and the merge candidate supplementing unit 446, when the number of merge candidates numCurrMergeCand registered in the merge candidate list mergeCandList is smaller than the maximum number of merge candidates MaxNumMergeCand, the merge candidates are not registered in the merge candidate list mergeCandList. With the maximum number of merge candidates MaxNumMergeCand as the upper limit, additional merge candidates are derived and registered in the merge candidate list mergeCandList (step S405 in FIG. 21). With the maximum number of merge candidates MaxNumMergeCand as the upper limit, in the P slice, merge candidates whose prediction mode is L0 prediction (Pred_L0) and whose motion vector has a value of (0, 0) are added. In the B slice, a merging candidate whose prediction mode is bi-prediction (Pred_BI) whose motion vector has a value of (0, 0) is added. The reference index when adding a merge candidate is different from the reference index already added.

Subsequently, the merge candidate selection unit 347 and the merge candidate selection unit 447 select merge candidates from the merge candidates registered in the merge candidate list mergeCandList. A merge candidate selection unit 347 on the encoding side selects a merge candidate by calculating a code amount and a distortion amount, and sends a merge index indicating the selected merge candidate and inter prediction information of the merge candidate to an inter prediction mode determination unit. 305 to the motion compensation prediction unit 306 . On the other hand, the decoding-side merge candidate selection unit 447 selects a merge candidate based on the decoded merge index, and supplies the selected merge candidate to the motion compensation prediction unit 406 .

<Update history motion vector predictor candidate list>
Next, a method for initializing and updating the history motion vector predictor candidate list HmvpCandList provided in the encoding information storage memory 111 on the encoding side and the encoding information storage memory 205 on the decoding side will be described in detail. FIG. 26 is a flowchart for explaining a history motion vector predictor candidate list initialization/update processing procedure.

In this embodiment, it is assumed that the history motion vector predictor candidate list HmvpCandList is updated by the encoding information storage memory 111 and the encoding information storage memory 205 . A historical motion vector predictor candidate list update unit may be installed in the inter prediction unit 102 and the inter prediction unit 203 to update the historical motion vector predictor candidate list HmvpCandList.

The historical motion vector predictor candidate list HmvpCandList is initialized at the beginning of the slice, and the historical motion vector predictor candidate list HmvpCandList is initialized on the encoding side when the prediction method determination unit 105 selects the normal motion vector predictor mode or the normal merge mode. On the decoding side, the historical motion vector predictor candidate list HmvpCandList is updated when the prediction information decoded by the bitstream decoding unit 201 is in the normal motion vector predictor mode or the normal merge mode.

Inter prediction information used when performing inter prediction in the normal motion vector predictor mode or normal merge mode is registered in the historical motion vector predictor candidate list HmvpCandList as an inter prediction information candidate hMvpCand. Inter prediction information candidate hMvpCand includes L0 reference index refIdxL0 and L1 reference index refIdxL1, L0 prediction flag predFlagL0 indicating whether L0 prediction is performed, L1 prediction flag predFlagL1 indicating whether L1 prediction is performed, A motion vector mvL0 of L0 and a motion vector mvL1 of L1 are included.

Inter prediction information candidate If inter prediction information with the same value as hMvpCand exists, that element is deleted from the historical motion vector predictor candidate list HmvpCandList. On the other hand, if there is no inter prediction information with the same value as the inter prediction information candidate hMvpCand, the leading element of the historical motion vector predictor candidate list HmvpCandList is deleted, and the inter prediction information candidate Add hMvpCand.

The number of elements of the history motion vector predictor candidate list HmvpCandList provided in the encoding information storage memory 111 on the encoding side and the encoding information storage memory 205 on the decoding side of the present invention is six.

First, the history motion vector predictor candidate list HmvpCandList is initialized for each slice (step S2101 in FIG. 26). At the beginning of the slice, all elements of the historical motion vector predictor candidate list HmvpCandList are emptied, and the number of historical motion vector predictor candidates registered in the historical motion vector predictor candidate list HmvpCandList (current number of candidates) NumHmvpCand value becomes 0 set.

Although the historical motion vector predictor candidate list HmvpCandList is initialized in units of slices (first coded blocks in slices), it may be initialized in units of pictures, tiles, or treeblock rows.

Subsequently, the following updating process of the history motion vector predictor candidate list HmvpCandList is repeatedly performed for each encoded block in the slice (steps S2102 to S2107 in FIG. 26).

First, initialization is performed for each encoding block. A flag identicalCandExist indicating whether or not the same candidate exists is set to FALSE (false), and a deletion target index removeIdx indicating a candidate to be deleted is set to 0 (step S2103 in FIG. 26).

It is determined whether or not there is an inter-prediction information candidate hMvpCand to be registered (step S2104 in FIG. 26). When the prediction method determination unit 105 on the encoding side determines the normal motion vector prediction mode or the normal merge mode, or when the bit stream decoding unit 201 on the decoding side decodes as the normal motion vector prediction mode or the normal merge mode, Let the inter prediction information be an inter prediction information candidate hMvpCand to be registered. When the prediction method determination unit 105 on the encoding side determines the intra prediction mode, the sub-block motion vector prediction mode, or the sub-block merge mode, or when the bitstream decoding unit 201 on the decoding side selects the intra prediction mode or the sub-block prediction motion vector mode. Alternatively, when decoding is performed in the sub-block merge mode, the history motion vector predictor candidate list HmvpCandList is not updated, and there is no inter prediction information candidate hMvpCand to be registered. If there is no inter prediction information candidate hMvpCand to be registered, steps S2105 and S2106 are skipped (step S2104 in FIG. 26: NO). If there is an inter-prediction information candidate hMvpCand to be registered, the process from step S2105 is performed (step S2104 in FIG. 26: YES).

Subsequently, it is determined whether an element (inter prediction information) having the same value as the inter prediction information candidate hMvpCand to be registered, that is, the same element exists in each element of the historical motion vector predictor candidate list HmvpCandList (Fig. 26 step S2105). FIG. 27 is a flow chart of this identical element confirmation processing procedure. If the value of the number of historical motion vector predictor candidates NumHmvpCand is 0 (step S2121 in FIG. 27: NO), the historical motion vector predictor candidate list HmvpCandList is empty and the same candidate does not exist, so steps S2122 to S2125 in FIG. 27 are skipped. Then, the identical element confirmation processing procedure ends. If the value of the number of historical motion vector predictor candidates NumHmvpCand is greater than 0 (YES in step S2121 of FIG. 27), the process of step S2123 is repeated until the historical motion vector predictor index hMvpIdx is from 0 to NumHmvpCand-1 (step S2123 of FIG. 27). S2122-S2125). First, it is compared whether or not the hMvpIdx-th element HmvpCandList[hMvpIdx] counting from 0 in the historical motion vector predictor candidate list is the same as the inter prediction information candidate hMvpCand (step S2123 in FIG. 27). If they are the same (step S2123 in FIG. 27: YES), the flag identicalCandExist indicating whether or not the same candidate exists is set to TRUE, and the deletion target index removeIdx indicating the position of the element to be deleted is set to the current , set the value of the historical motion vector prediction index hMvpIdx, and terminate this identical element confirmation processing. If they are not the same (step S2123 in FIG. 27: NO), hMvpIdx is incremented by 1, and if the historical motion vector prediction index hMvpIdx is less than or equal to NumHmvpCand-1, the processing from step S2123 is performed.

Returning to the flowchart of FIG. 26 again, shift and addition processing of the elements of the history motion vector predictor candidate list HmvpCandList is performed (step S2106 of FIG. 26). FIG. 28 is a flowchart of the element shift/addition processing procedure of the history motion vector predictor candidate list HmvpCandList in step S2106 of FIG. First, it is determined whether to add a new element after removing the elements stored in the history motion vector predictor candidate list HmvpCandList or to add a new element without removing the element. Specifically, it compares whether the flag identicalCandExist indicating whether or not the same candidate exists is TRUE (true) or NumHmvpCand is 6 (step S2141 in FIG. 28). If the flag identicalCandExist indicating whether or not the same candidate exists is TRUE (true) or the number of current candidates NumHmvpCand satisfies either condition of 6 (step S2141 in FIG. 28: YES), the historical motion vector predictor candidate list HmvpCandList Add new elements after removing the elements stored in . Set the initial value of index i to the value of removeIdx + 1. The element shift processing in step S2143 is repeated from this initial value to NumHmvpCand. (Steps S2142 to S2144 in FIG. 28). By copying the element of HmvpCandList[i] to HmvpCandList[i-1], the element is shifted forward (step S2143 in FIG. 28), and i is incremented by 1 (steps S2142 to S2144 in FIG. 28). Subsequently, the inter prediction information candidate hMvpCand is added to the (NumHmvpCand-1)-th HmvpCandList[NumHmvpCand-1] counting from 0 corresponding to the end of the historical motion vector predictor candidate list (step S2145 in FIG. 28), and this historical prediction is performed. End the element shift/addition processing of the motion vector candidate list HmvpCandList. On the other hand, if the flag identicalCandExist indicating whether or not the same candidate exists is TRUE (true) and NumHmvpCand does not satisfy the conditions of 6 (step S2141 in FIG. 28: NO), it is stored in the historical motion vector predictor candidate list HmvpCandList. The inter-prediction information candidate hMvpCand is added to the end of the historical motion vector predictor candidate list without removing the elements that are indicated (step S2146 in FIG. 28). Here, the end of the historical motion vector predictor candidate list is the NumHmvpCand-th HmvpCandList[NumHmvpCand] counted from 0. Also, NumHmvpCand is incremented by 1, and the element shift and addition processing of this history motion vector predictor candidate list HmvpCandList ends.

FIG. 31 is a diagram illustrating an example of update processing of the historical motion vector predictor candidate list. When adding a new element to the historical motion vector predictor candidate list HmvpCandList in which six elements (inter prediction information) have been registered, the elements in the historical motion vector predictor candidate list HmvpCandList are sequentially compared with the new inter prediction information. (FIG. 31A), if the new element has the same value as the third element HMVP2 from the top of the historical motion vector predictor candidate list HmvpCandList, the element HMVP2 is deleted from the historical motion vector predictor candidate list HmvpCandList, and the subsequent elements HMVP3 to Shift (copy) HMVP5 forward one by one, add a new element to the end of the historical motion vector predictor candidate list HmvpCandList (Fig. 31B), and complete the update of the historical motion vector predictor candidate list HmvpCandList (Fig. 31C). ).

<Historical Motion Vector Predictor Candidate Derivation Processing>
Next, the historical motion vector predictor candidate deriving unit 323 of the normal predictive motion vector mode deriving unit 301 on the encoding side and the historical motion vector predictor candidate deriving unit 423 of the normal predictive motion vector mode deriving unit 401 on the decoding side perform common processing. A method for deriving historical motion vector predictor candidates from the historical motion vector predictor candidate list HmvpCandList, which is the processing procedure of step S304 in FIG. 20, will be described in detail. FIG. 29 is a flowchart for explaining the historical motion vector predictor candidate derivation processing procedure.

If the number of current motion vector predictor candidates numCurrMvpCand is greater than or equal to the maximum number of elements (2 in this case) in the motion vector predictor candidate list mvpListLX, or if the number of historical motion vector predictor candidates is 0 (step S2201 in FIG. 29) NO), the processing of steps S2202 to S2209 in FIG. 29 is omitted, and the history motion vector predictor candidate derivation processing procedure ends. If the number of current motion vector predictor candidates numCurrMvpCand is less than 2, which is the maximum number of elements in the motion vector predictor candidate list mvpListLX, and if the value of the number of historical motion vector predictor candidates NumHmvpCand is greater than 0 (step S2201 in FIG. 29) YES), the processing of steps S2202 to S2209 in FIG. 29 is performed.

Subsequently, the processing from steps S2203 to S2208 in FIG. 29 is repeated until the index i is from 1 to 4 or the number of historical motion vector predictor candidates numCheckedHMVPCand, whichever is smaller (steps S2202 to S2209 in FIG. 29). If the number of current motion vector predictor candidates numCurrMvpCand is equal to or greater than 2, which is the maximum number of elements in the motion vector predictor candidate list mvpListLX (step S2203 in FIG. 29: NO), the processing from steps S2204 to S2209 in FIG. The historical motion vector predictor candidate derivation processing procedure is ended. If the current number of motion vector predictor candidates numCurrMvpCand is less than 2, which is the maximum number of elements in the motion vector predictor candidate list mvpListLX (step S2203 in FIG. 29: YES), the processing from step S2204 in FIG. 29 onward is performed.

Subsequently, steps S2205 to S2207 are performed for Y=0 and 1 (L0 and L1) respectively (steps S2204 to S2208 in FIG. 29). If the number of current motion vector predictor candidates numCurrMvpCand is equal to or greater than 2, which is the maximum number of elements in the motion vector predictor candidate list mvpListLX (step S2205 in FIG. 29: NO), the processing from steps S2206 to S2209 in FIG. The historical motion vector predictor candidate derivation processing procedure is ended. If the number of current motion vector predictor candidates numCurrMvpCand is less than 2, which is the maximum number of elements in the motion vector predictor candidate list mvpListLX (step S2205 in FIG. 29: YES), the processing from step S2206 onward in FIG. 29 is performed.

Subsequently, if the historical motion vector predictor candidate list HmvpCandList has an element with the same reference index as the reference index refIdxLX of the motion vector to be encoded/decoded and is different from any element in the motion vector predictor list mvpListLX (Fig. 29 step S2206: YES), the LY motion vector of the historical motion vector predictor candidate HmvpCandList[NumHmvpCand-i] is added to the numCurrMvpCand-th element mvpListLX[numCurrMvpCand] counting from 0 of the motion vector predictor candidate list (step of FIG. 29 S2207), the current number of motion vector predictor candidates numCurrMvpCand is incremented by one. If there is no element in the history motion vector predictor candidate list HmvpCandList that has an element with the same reference index as the reference index refIdxLX of the motion vector to be encoded/decoded and is different from any element in the motion vector predictor list mvpListLX (step S2206: NO), skip the addition process of step S2207.

The processes from steps S2205 to S2207 in FIG. 29 are performed for both L0 and L1 (steps S2204 to S2208 in FIG. 29). The index i is incremented by 1, and if the index i is equal to or smaller than 4 or the number of historical motion vector predictor candidates NumHmvpCand, whichever is smaller, the processing from step S2203 onward is performed again (steps S2202 to S2209 in FIG. 29).

<History Merge Candidate Derivation Processing>
Next, the process of step S404 in FIG. 21, which is common to the history merge candidate derivation unit 345 of the normal merge mode derivation unit 302 on the encoding side and the history merge candidate derivation unit 445 of the normal merge mode derivation unit 402 on the decoding side. A method for deriving history merge candidates from the history merge candidate list HmvpCandList, which is a procedure, will be described in detail. FIG. 30 is a flowchart for explaining the history merging candidate derivation processing procedure.

First, initialization processing is performed (step S2301 in FIG. 30). Sets each element from 0 to (numCurrMergeCand -1) of isPruned[i] to the value FALSE, and sets the variable numOrigMergeCand to the number of elements registered in the current merge candidate list, numCurrMergeCand.

Subsequently, the initial value of the index hMvpIdx is set to 1, and the additional processing from steps S2303 to S2310 in FIG. 30 is repeated from this initial value to NumHmvpCand (steps S2302 to S2311 in FIG. 30). If the number of elements registered in the current merge candidate list, numCurrMergeCand, is not less than (the maximum number of merge candidates, MaxNumMergeCand-1), merge candidates have been added to all the elements in the merge candidate list, so this history merge candidate derivation The process ends (NO in step S2303 of FIG. 30). If the number of elements registered in the current merge candidate list, numCurrMergeCand, is less than (the maximum number of merge candidates, MaxNumMergeCand-1), the process from step S2304 is performed. SameMotion is set to FALSE (step S2304 in FIG. 30). Subsequently, the initial value of index i is set to 0, and steps S2306 and S2307 in FIG. 30 are performed from this initial value to numOrigMergeCand-1 (S2305 to S2308 in FIG. 30). Compare whether the (NumHmvpCand - hMvpIdx)th element HmvpCandList[NumHmvpCand-hMvpIdx] of the history motion vector prediction candidate list counting from 0 is the same value as the ith element mergeCandList[i] counting from 0 of the merge candidate list (step S2306 in FIG. 30).

A merge candidate with the same value is defined as a merge candidate with the same value when all components (inter prediction mode, reference index, motion vector) of the merge candidate have the same value. If the merge candidates have the same value and isPruned[i] is FALSE (YES in step S2306 in FIG. 30), both sameMotion and isPruned[i] are set to TRUE (step S2307 in FIG. 30). If the values are not the same (NO in step S2306 of FIG. 30), the process of step S2307 is skipped. When the repeated processing from step S2305 to step S2308 in FIG. 30 is completed, it is compared whether sameMotion is FALSE (step S2309 in FIG. 30), and if sameMotion is FALSE (step S2309 in FIG. 30) YES), that is, since the (NumHmvpCand - hMvpIdx)-th element HmvpCandList[NumHmvpCand-hMvpIdx] of the history motion vector predictor candidate list does not exist in the mergeCandList, the history prediction The (NumHmvpCand-hMvpIdx)th element HmvpCandList[NumHmvpCand-hMvpIdx] counting from 0 of the motion vector candidate list is added, and numCurrMergeCand is incremented by 1 (step S2310 in FIG. 30). The index hMvpIdx is incremented by 1 (step S2302 in FIG. 30), and steps S2302 to S2311 in FIG. 30 are repeated.

When all elements of the history motion vector predictor candidate list have been confirmed or merge candidates have been added to all elements of the merge candidate list, this history merge candidate derivation process is completed.

<Average merge candidate derivation process>
Next, the processing of step S403 in FIG. 21, which is the processing common to the average merge candidate derivation unit 344 of the normal merge mode derivation unit 302 on the encoding side and the average merge candidate derivation unit 444 of the normal merge mode derivation unit 402 on the decoding side. The procedure for deriving average merge candidates will be described in detail. FIG. 38 is a flowchart for explaining the average merging candidate derivation processing procedure.

First, initialization processing is performed (step S1301 in FIG. 38). Set the number of elements registered in the current merge candidate list, numCurrMergeCand, to the variable numOrigMergeCand.

Subsequently, the merge candidate list is sequentially scanned from the top to determine two pieces of motion information. Let index i=0 indicating the first motion information and index j=1 indicating the second motion information. (Steps S1302 and S1303 in FIG. 38). If the number of elements registered in the current merge candidate list, numCurrMergeCand, is not less than (the maximum number of merge candidates, MaxNumMergeCand-1), merge candidates have been added to all the elements in the merge candidate list, so this history merge candidate derivation The process ends (step S1304 in FIG. 38). If the number of elements registered in the current merge candidate list, numCurrMergeCand, is less than (the maximum number of merge candidates, MaxNumMergeCand-1), the process from step S1305 is performed.

It is determined whether the i-th motion information mergeCandList[i] in the merge candidate list and the j-th motion information mergeCandList[j] in the merge candidate list are both invalid (step S1305 in FIG. 38), and both are invalid. If so, do not derive the average merge candidate for mergeCandList[i] and mergeCandList[j] and move on to the next element. If both mergeCandList[i] and mergeCandList[j] are not invalid, the following processing is repeated with X set to 0 and 1 (steps S1306 to S1314 in FIG. 38).

It is determined whether the LX prediction of mergeCandList[i] is valid (step S1307 in FIG. 38). If the LX prediction for mergeCandList[i] is valid, it is determined whether the LX prediction for mergeCandList[j] is valid (step S1308 in FIG. 38). If the LX prediction for mergeCandList[j] is valid, i.e. if both the LX prediction for mergeCandList[i] and the LX prediction for mergeCandList[j] are valid, then the motion vector for the LX prediction for mergeCandList[i] and mergeCandList Derive the average merge candidate for the LX prediction with the motion vector for the LX prediction that averaged the motion vector for the LX prediction in [j] and the reference index for the LX prediction in mergeCandList[i] and set it to the LX prediction for averageCand, LX prediction is validated (step S1309 in FIG. 38). In step S1308 of FIG. 38, if the LX prediction of mergeCandList[j] is not valid, that is, if the LX prediction of mergeCandList[i] is valid and the LX prediction of mergeCandList[j] is invalid, mergeCandList[i] LX prediction average merge candidate having a motion vector of LX prediction and reference index is derived, set to LX prediction of averageCand, and LX prediction of averageCand is validated (step S1310 in FIG. 38). If the LX prediction of mergeCandList[i] is not valid in step S1307 of FIG. 38, it is determined whether or not the LX prediction of mergeCandList[j] is valid (step S1311 of FIG. 38). If the LX prediction of mergeCandList[j] is valid, i.e. the LX prediction of mergeCandList[i] is invalid and the LX prediction of mergeCandList[j] is valid, then the motion vector of the LX prediction of mergeCandList[j] and The average merging candidate for the LX prediction with reference index is derived and set to the LX prediction of averageCand, and the LX prediction of averageCand is validated (step S1312 in FIG. 38). In step S1311 of FIG. 38, if the LX prediction for mergeCandList[j] is invalid, that is, if both the LX prediction for mergeCandList[i] and mergeCandList[j] are invalid, the LX prediction for averageCand is invalidated. (step S1312 in FIG. 38).

The average merge candidate averageCand of the L0 prediction, L1 prediction or BI prediction generated as described above is added to the numCurrMergeCand-th mergeCandList[numCurrMergeCand] of the merge candidate list, and numCurrMergeCand is incremented by 1 (step S1315 in FIG. 38). This completes the average merging candidate derivation process.

Note that the average merge candidate is averaged for each of the horizontal component of the motion vector and the vertical component of the motion vector.

<Motion Compensation Prediction Processing>
The motion compensation prediction unit 306 acquires the position and size of the block currently being subjected to prediction processing in encoding. Also, the motion compensation prediction unit 306 acquires inter prediction information from the inter prediction mode determination unit 305 . A reference index and a motion vector are derived from the acquired inter prediction information, and the reference picture specified by the reference index in the decoded image memory 104 is moved from the same position as the image signal of the prediction block by the amount of the motion vector. A predicted signal is generated after the image signal is acquired.

When the inter prediction mode in inter prediction is prediction from a single reference picture such as L0 prediction or L1 prediction, the prediction signal obtained from one reference picture is the motion compensation prediction signal, and the inter prediction mode is BI When the prediction mode is prediction from two reference pictures, such as prediction, the weighted average of the prediction signals obtained from the two reference pictures is used as the motion-compensated prediction signal, and the motion-compensated prediction signal is used to determine the prediction method. 105. Here, the weighted average ratio of bi-prediction is set to 1:1, but weighted average may be performed using other ratios. For example, the closer the picture interval between the picture to be predicted and the reference picture is, the higher the weighting ratio may be. Alternatively, the weighting ratio may be calculated using a correspondence table of combinations of picture intervals and weighting ratios.

The motion compensation prediction unit 406 has the same function as the motion compensation prediction unit 306 on the encoding side. The motion compensation prediction unit 406 passes the inter prediction information from the normal prediction motion vector mode derivation unit 401, the normal merge mode derivation unit 402, the sub-block prediction motion vector mode derivation unit 403, and the sub-block merge mode derivation unit 404 to switch 408. to get through. The motion compensation prediction unit 406 supplies the obtained motion compensation prediction signal to the decoded image signal superimposing unit 207 .

<About inter-prediction mode>
The process of performing prediction from a single reference picture is defined as uniprediction, and in the case of uniprediction, either one of the two reference pictures registered in the reference lists L0 and L1, called L0 prediction or L1 prediction, is used. make predictions.

FIG. 32 shows a case of uni-prediction in which the L0 reference picture (RefL0Pic) is at a time before the processing target picture (CurPic). FIG. 33 shows a case where the uni-prediction is performed and the reference picture of L0 prediction is at a time after the picture to be processed. Similarly, uni-prediction can be performed by replacing the reference picture for L0 prediction in FIGS. 32 and 33 with the reference picture for L1 prediction (RefL1Pic).

A process of performing prediction from two reference pictures is defined as bi-prediction, and bi-prediction is expressed as BI prediction using both L0 prediction and L1 prediction. FIG. 34 shows a bi-prediction case where the reference picture for L0 prediction is before the picture to be processed and the reference picture for L1 prediction is after the picture to be processed. FIG. 35 shows a bi-prediction case where the reference picture for L0 prediction and the reference picture for L1 prediction are located before the picture to be processed. FIG. 36 shows a bi-prediction case where the reference picture for L0 prediction and the reference picture for L1 prediction are located after the picture to be processed.

In this way, the relationship between the prediction type of L0/L1 and time can be used without being limited to the past direction for L0 and the future direction for L1. In the case of bi-prediction, L0 prediction and L1 prediction may be performed using the same reference picture. It should be noted that the determination of whether motion compensation prediction is performed by uni-prediction or bi-prediction is made based on information (for example, a flag) indicating whether to use L0 prediction and whether to use L1 prediction, for example. be.

<About reference index>
In the embodiments of the present invention, it is possible to select an optimum reference picture from among a plurality of reference pictures in motion compensation prediction in order to improve the accuracy of motion compensation prediction. Therefore, the reference picture used in motion compensation prediction is used as a reference index, and the reference index is coded in the bitstream together with the differential motion vector.

<Motion Compensation Processing Based on Normal Predicted Motion Vector Mode>
Motion compensation prediction section 306, as also shown in inter prediction section 102 on the encoding side in FIG. obtains this inter prediction information from the inter prediction mode determination unit 305, derives the inter prediction mode, reference index, and motion vector of the block currently being processed, and generates a motion compensated prediction signal. The generated motion-compensated prediction signal is supplied to the prediction method determination unit 105 .

Similarly, motion compensation prediction section 406, as shown in inter prediction section 203 on the decoding side in FIG. Inter prediction information is obtained by the predicted motion vector mode derivation unit 401, and the inter prediction mode, reference index, and motion vector of the block currently being processed are derived, and a motion compensated prediction signal is generated. The generated motion-compensated prediction signal is supplied to the decoded image signal superimposing unit 207 .

<Motion Compensation Processing Based on Normal Merge Mode>
As shown in the inter prediction unit 102 on the encoding side in FIG. This inter-prediction information is acquired from the inter-prediction mode determination unit 305, the inter-prediction mode, reference index, and motion vector of the block currently being processed are derived, and a motion compensated prediction signal is generated. The generated motion-compensated prediction signal is supplied to the prediction method determination unit 105 .

Similarly, as shown in the inter prediction unit 203 on the decoding side in FIG. Inter prediction information is obtained by the derivation unit 402, the inter prediction mode, reference index, and motion vector of the block currently being processed are derived, and a motion compensated prediction signal is generated. The generated motion-compensated prediction signal is supplied to the decoded image signal superimposing unit 207 .

<Motion compensation processing based on sub-block prediction motion vector mode>
When the inter prediction mode determination unit 305 selects the inter prediction information by the sub-block prediction motion vector mode derivation unit 303, the motion compensation prediction unit 306 selects the inter prediction information by the inter prediction unit 102 on the encoding side in FIG. , this inter prediction information is obtained from the inter prediction mode determination unit 305, the inter prediction mode, reference index, and motion vector of the block currently being processed are derived, and a motion compensated prediction signal is generated. The generated motion-compensated prediction signal is supplied to the prediction method determination unit 105 .

Similarly, motion compensation prediction section 406, as shown in inter prediction section 203 on the decoding side in FIG. The sub-block prediction motion vector mode derivation unit 403 acquires inter prediction information, derives the inter prediction mode, reference index, and motion vector of the block currently being processed, and generates a motion compensation prediction signal. The generated motion-compensated prediction signal is supplied to the decoded image signal superimposing unit 207 .

<Motion Compensation Processing Based on Sub-Block Merge Mode>
As shown in the inter prediction unit 102 on the encoding side in FIG. 16 , the motion compensation prediction unit 306 performs , this inter prediction information is obtained from the inter prediction mode determination unit 305, the inter prediction mode, reference index, and motion vector of the block currently being processed are derived, and a motion compensated prediction signal is generated. The generated motion-compensated prediction signal is supplied to the prediction method determination unit 105 .

Similarly, as shown in inter prediction section 203 on the decoding side in FIG. Inter prediction information is obtained by the merge mode derivation unit 404, the inter prediction mode, reference index, and motion vector of the block currently being processed are derived, and a motion compensated prediction signal is generated. The generated motion-compensated prediction signal is supplied to the decoded image signal superimposing unit 207 .

<Motion Compensation Processing Based on Affine Transform Prediction>
In normal motion vector prediction mode and normal merge mode, motion compensation by affine model can be used based on the following flags. The following flags are reflected in the following flags based on the inter prediction conditions determined by the inter prediction mode determination unit 305 in the encoding process, and encoded in the bitstream. In the decoding process, whether or not to perform motion compensation by the affine model is specified based on the following flags in the bitstream.

sps_affine_enabled_flag indicates whether motion compensation by an affine model can be used in inter prediction. If sps_affine_enabled_flag is 0, motion compensation by the affine model is suppressed on a per-sequence basis. Also, inter_affine_flag and cu_affine_type_flag are not transmitted in the CU (coded block) syntax of the coded video sequence. If sps_affine_enabled_flag is 1, affine model motion compensation can be used in the encoded video sequence.

sps_affine_type_flag indicates whether motion compensation by a 6-parameter affine model can be used in inter prediction. If sps_affine_type_flag is 0, motion compensation is not performed by the 6-parameter affine model. Also, cu_affine_type_flag is not transmitted in the CU syntax of the encoded video sequence. If sps_affine_type_flag is 1, motion compensation with a 6-parameter affine model can be used in the encoded video sequence. If sps_affine_type_flag is not present, it shall be 0.

When decoding a P or B slice, if inter_affine_flag is 1 in the CU currently being processed, the affine model is used to generate the motion-compensated prediction signal of the CU currently being processed. Motion compensation is used. If inter_affine_flag is 0, the affine model is not used for the CU currently being processed. If inter_affine_flag is not present, it shall be 0.

When decoding a P or B slice, if cu_affine_type_flag is 1 in the CU currently being processed, 6-parameter affine Motion compensation by model is used. If cu_affine_type_flag is 0, then motion compensation with a 4-parameter affine model is used to generate a motion compensated prediction signal for the CU currently being processed.

In motion compensation using an affine model, a reference index and a motion vector are derived for each subblock, so a motion compensation prediction signal is generated using the reference index and motion vector to be processed for each subblock.

The 4-parameter affine model is a mode in which a sub-block motion vector is derived from four parameters, ie, horizontal and vertical components of motion vectors of two control points, and motion compensation is performed on a sub-block basis.

<Intra block copy (IBC)>
A valid reference area for intra block copy will be described with reference to FIG. FIG. 39A is an example of determining a valid reference area using a coding tree block unit as an intra block copy reference block. 500, 501, 502, 503, and 504 in FIG. 39A are coding tree blocks, and 504 is the coding tree block to be processed. 505 is an encoding block to be processed. The processing order of the coding tree blocks is 500, 501, 502, 503, 504. In this case, the three coding tree blocks 501, 502, and 503 processed immediately before the coding tree block 504 including the coding block 505 to be processed are set as the effective reference regions of the coding block 505 to be processed. Coding treeblocks processed before coding treeblock 501, and coding treeblocks including target codingblock 505, regardless of whether processing was completed prior to target codingblock 505. All areas included in 504 are invalid reference areas.

FIG. 39B is an example of determining a valid reference area by using a unit obtained by dividing a coding tree block into four as an intra block copy reference block. 515 and 516 in FIG. 39B are coding tree blocks, and 516 is a coding tree block to be processed. Coding tree block 515 is quadranted into 506, 507, 508 and 509, and 516 is quadrant into 510, 511, 512 and 513. 514 is an encoding block to be processed. The processing order of intra block copy reference blocks is 506, 507, 508, 509, 510, 511, 512, and 513. FIG. In this case, the three intra block copy reference blocks 508 , 509 , and 510 processed immediately before the intra block copy reference block 511 including the target encoding block 514 are used as valid reference regions for the target encoding block 514 . Coding tree blocks processed before intra block copy reference block 508 and intra block copy including current coding block 514 regardless of whether processing was completed before current coding block 514 All areas included in the reference block 511 are invalid reference areas.

<Predicted Intra Block Copy: Explanation on Encoding Side>
A predictive intra block copy processing procedure on the encoding side will be described with reference to FIG.

First, block vector mvL is detected by block vector detection unit 375 (step S4500 in FIG. 44). Subsequently, an IBC spatial block vector candidate derivation unit 371, an IBC history prediction block vector candidate derivation unit 372, an IBC prediction block vector candidate supplementation unit 373, an IBC prediction block vector candidate selection unit 376, and a block vector subtraction unit 378 perform prediction block vector A difference block vector of the block vectors used in the mode is calculated (steps S4501 to S4503 in FIG. 44).

Prediction block vector candidates are calculated to construct a block vector candidate list mvpList (step S4501 in FIG. 44). An IBC spatial block vector candidate derivation unit 371, an IBC history block vector candidate derivation unit 372, and an IBC prediction block vector candidate supplementation unit 373 in the intra block copy prediction unit 352 derive a plurality of prediction block vector candidates to obtain a prediction block vector. Construct the candidate list mvpList. A detailed processing procedure of step S4501 in FIG. 44 will be described later using the flowchart in FIG.

Subsequently, the IBC predictive block vector candidate selection unit 376 selects the predictive block vector mvpL from the predictive block vector candidate list mvpListL (step S4502 in FIG. 44). Differential block vectors, which are the differences between the block vector mvL and each predictive block vector candidate mvpListL[i] stored in the predictive block vector candidate list mvpListL, are calculated. A code amount when the difference block vectors are encoded is calculated for each element of the predictive block vector candidate list mvpListL. Then, among the elements registered in the predictive block vector candidate list mvpListL, the predictive block vector candidate mvpListL[i] having the smallest code amount for each predictive block vector candidate is selected as the predictive block vector mvpL. Get index i. If there are multiple predictive block vector candidates with the smallest generated code amount in the block vector predictor candidate list mvpListL, the predictive block vector whose index i in the block vector predictor candidate list mvpListL is represented by a small number. is selected as the optimal predictive block vector mvpL, and its index i is obtained.

Subsequently, the block vector subtraction unit 378 subtracts the selected predicted block vector mvpL from the block vector mvL,
mvdL = mvL - mvpL
, the differential block vector mvdL is calculated (step S4503 in FIG. 44).

<Predicted Intra Block Copy: Explanation on Decoding Side>
Next, the predictive block vector mode processing procedure on the decoding side will be described with reference to FIG. On the decoding side, the IBC spatial prediction block vector candidate derivation unit 471, the IBC history block vector candidate derivation unit 472, and the IBC prediction block vector supplementation unit 473 calculate block vectors used in the prediction block vector mode (steps S4600 to S4600 in FIG. 45). S4602). Specifically, a predictive block vector candidate list mvpListL is calculated, a predictive block vector mvpL is selected, and a block vector mvL is calculated.

Predictive block vector candidates are calculated to construct a predictive block vector candidate list mvpListL (step S4601 in FIG. 45). An IBC spatial block vector candidate deriving unit 471, an IBC history block vector candidate deriving unit 472, and an IBC block vector supplementing unit 473 in the intra block copy prediction unit 362 calculate a plurality of predictive block vector candidates, and create a predictive block vector candidate list. Build mvpListL. Description of the detailed processing procedure of step S4601 in FIG. 45 is omitted. Subsequently, the IBC predictive block vector candidate selection unit 476 selects a predictive block vector candidate mvpListL[mvpIdxL] corresponding to the predictive block vector index mvpIdxL decoded and supplied by the bit string decoding unit 201 from the predictive block vector candidate list mvpListL. It is taken out as the selected predictive block vector mvpL (step S4601 in FIG. 45). Subsequently, the block vector addition unit 478 adds the differential block vector mvdL and the predicted block vector mvpL decoded and supplied by the bit string decoding unit 201,
mvL = mvpL + mvdL
to calculate the block vector mvL (step S4602 in FIG. 45).

<Prediction Block Vector Mode: Block Vector Prediction Method>
FIG. 47 shows prediction intra block copy mode derivation processing having functions common to the intra block copy prediction unit 352 of the video encoding device and the intra block copy prediction unit 362 of the video decoding device according to the embodiment of the present invention. It is a flow chart showing a processing procedure.

The intra block copy prediction unit 352 and the intra block copy prediction unit 362 are provided with a prediction block vector candidate list mvpListL. The block vector predictor candidate list mvpListL has a list structure, and is provided with a block vector predictor index indicating the location inside the block vector predictor candidate list and a storage area for storing the block vector predictor candidate corresponding to the index as an element. The prediction block vector index number starts from 0, and the prediction block vector candidates are stored in the storage area of the prediction block vector candidate list mvpListL. In this embodiment, it is assumed that the predictive block vector candidate list mvpListL can register three predictive block vector candidates. Furthermore, 0 is set to a variable numCurrMvpIbcCand indicating the number of predictive block vector candidates registered in the predictive block vector candidate list mvpListL.

The IBC spatial block vector candidate deriving units 371 and 471 derive predictive block vector candidates from the left adjacent block (step S4801 in FIG. 47). In this process, a block vector mvLA and a flag availableFlagLA indicating whether or not the predictive block vector candidate of the left adjacent block (A0 or A1) is available are derived, and mvLA is added to the predictive block vector candidate list mvpListL. Subsequently, the IBC spatial block vector candidate deriving units 371 and 471 derive predictive block vector candidates from the upper adjacent block (B0, B1 or B2) (step S4802 in FIG. 47). In this process, a flag availableFlagLB indicating whether or not the motion vector predictor candidate of the block adjacent to the upper side is available, and a block vector mvLB are derived. to add. The processes in steps S4801 and S4802 in FIG. 47 are common except that the position and number of adjacent blocks to be referred to are different, and flag availableFlagLN indicating whether or not the prediction block vector candidate of the coding block is available, and motion vector mvLN. (N is A or B, and so on) is derived.

Subsequently, the IBC history block vector candidate derivation units 372 and 472 add the history block vector candidates registered in the history block vector candidate list HmvpIbcCandList to the predictive block vector candidate list mvpListL. (Step S4803 in FIG. 47). Details of the registration processing procedure in step S4803 are described in the description of the operation shown in the flowchart of FIG. Since it is sufficient if the operation is the same as the case of HmvpIbcCandList, the explanation is omitted.

Subsequently, the IBC predictive block vector supplementing units 373 and 473 add block vectors of predetermined values such as (0, 0) until the predictive block vector candidate list mvpListL is satisfied (S4804 in FIG. 47).

<Merging intra-block copy mode derivation unit>
The intra block copy prediction unit 352 in FIG. 42 includes an IBC space block vector candidate derivation unit 371, an IBC history block vector candidate derivation unit 372, an IBC block vector supplementation unit 373, a reference position correction unit 380, a reference area boundary correction unit 381, an IBC A merge candidate selection unit 374 and an IBC prediction mode determination unit 377 are included.

The intra block copy prediction unit 362 of FIG. A region boundary correction unit 481 and a block copy unit 477 are included.

FIG. 46 shows a merge intra block copy mode derivation process having functions common to the intra block copy prediction unit 352 of the video encoding device and the intra block copy prediction unit 362 of the video decoding device according to the embodiment of the present invention. It is a flow chart explaining a procedure.

The intra block copy prediction unit 352 and the intra block copy prediction unit 362 have a merge intra block copy candidate list mergeIbcCandList. The merge intra block copy candidate list mergeIbcCandList has a list structure, and is provided with a merge index indicating the location inside the merge intra block copy candidate and a storage area for storing the merge intra block copy candidate corresponding to the index as an element. The number of the merge index starts from 0, and the merge intra block copy candidates are stored in the storage area of the merge intra block copy candidate list mergeIbcCandList. In the subsequent processing, merge candidates with merge index i registered in the merge intra block copy candidate list mergeIbcCandList are represented by mergeIbcCandList[i]. In this embodiment, the merge candidate list mergeCandList can register at least three merge intra block copy candidates. Furthermore, 0 is set to a variable numCurrMergeIbcCand indicating the number of merge intra block copy candidates registered in the merge intra block copy candidate list mergeIbcCandList.

In the IBC spatial block vector candidate derivation unit 371 and the IBC spatial block vector candidate derivation unit 471, the encoding stored in the encoding information storage memory 111 of the video encoding device or the encoding information storage memory 205 of the video decoding device. Spatial merge candidates A and B are derived from the blocks adjacent to the left and upper sides of the block to be processed from the information, and the derived spatial merge candidates are registered in the merge intra block copy candidate list mergeIbcCandList (step S4701 in FIG. 46). ). Here, N is defined to indicate either spatial merge candidate A or B. A flag availableFlagN and a block vector mvL indicating whether intra block copy prediction information of block N can be used as a spatial block vector merging candidate N are derived. However, in the present embodiment, block vector merging candidates are derived without referring to other encoding blocks included in the block including the encoding block to be processed. does not derive spatial block vector merge candidates contained in .

Subsequently, the IBC history block vector candidate derivation unit 372 and the IBC history block vector candidate derivation unit 472 add the history prediction block vector candidates registered in the history prediction block vector candidate list HmvpIbcCandList to the merge intra block copy candidate list mergeIbcCandList. (Step S4702 in FIG. 46). In this embodiment, if the block vector already added to mergeIbcCandList and the block vector of the historical prediction block vector candidate have the same value, addition to mergeIbcCandList is not performed.

Subsequently, when the number of merge candidates numCurrMergeIbcCand registered in the merge intra block copy candidate list mergeIbcCandList is smaller than the maximum number of intra block merge candidates MaxNumMergeIbcCand, The number of merge candidates numCurrMergeIbcCand registered in the merge intra block copy candidate list mergeIbcCandList derives additional intra block merge candidates up to the maximum number of merge candidates MaxNumMergeIbcCand, and registers them in the merge intra block copy candidate list mergeIbcCandList (see FIG. 46). step S4703). With the maximum number of merge candidates MaxNumMergeIbcCand as the upper limit, block vectors having values of (0, 0) are added to the merge intra block copy candidate list mergeIbcCandList.

Subsequently, the IBC merge candidate selection unit 374 and the IBC merge candidate selection unit 474 select one intra block merge candidate registered in the merge intra block copy candidate list mergeIbcCandList (step S4704 in FIG. 46). The IBC merge candidate selection unit 374 acquires the decoded image at the reference position from the decoded image memory 104, calculates the code amount and distortion amount, selects a merge candidate, and sets a merge index indicating the selected intra block merge candidate. It is supplied to the IBC prediction mode determination unit 377 . The IBC prediction mode determination unit 377 selects whether or not it is the merge mode by calculating the code amount and the distortion amount, and supplies the result to the prediction method determination unit 105 . On the other hand, the decoding-side IBC merge candidate selection unit 474 selects an intra block merge candidate based on the decoded merge index, and supplies the selected intra block merge candidate to the reference position correction unit 480 .

Subsequently, the reference position correcting unit 380 and the reference position correcting unit 480 perform processing for correcting the reference position for the intra block merge candidate (step S4705 in FIG. 46). Details of the processing of the reference position correction section 380 and the reference position correction section 480 will be described later.

Subsequently, the reference area boundary correction unit 381 and the reference area boundary correction unit 481 perform processing for correcting the reference area boundary for the intra block merge candidate (step S4706 in FIG. 46). Details of the processing of the reference position correction unit 381 and the reference position correction unit 481 will be described later.

The block copy unit 477 acquires the decoded image at the reference position from the decoded image memory 208 and supplies it to the decoded image signal superimposing unit 207 . Here, the block copy unit 477 copies the luminance component and the color difference component.

The above block vector mvL indicates a luminance block vector. When the chrominance format is 420, the chrominance block vector mvC is
mvC = ( ( mvL >> ( 3 + 2 ) ) * 32
becomes. The above formula handles each x,y component of mvC.

<Reference position corrector>
FIG. 48 is a flowchart for explaining the processing of the reference position correction section 380 and the reference position correction section 480. FIG. Now, assume that the intra block copy reference block unit is a coding tree block (CTU) and its size is not 128×128 pixels.

First, the upper left and lower right positions of the reference block are calculated (S6001). A reference block refers to a block that is referred to by an encoding block to be processed using a block vector. If the upper left of the reference block is ( xRefTL, yRefTL ) and the lower right is ( xRefBR, yRefBR ),
( xRefTL, yRefTL ) = ( xCb + ( mvL[ 0 ] >> 4 ), yCb + ( mvL[ 1 ] >> 4 ) )
( xRefBR, yRefBR ) = ( xRefTL + cbWidth - 1, yRefTL + cbHeight - 1 )
becomes. Here, the position of the encoding block to be processed is (xCb, yCb), the block vector is (mvL[0], mvL[1]), the width of the encoding block to be processed is cbWidth, and the height is cbHeight.

Next, it is determined whether or not the size of the CTU is 128×128 pixels (S6002). Since the size is not 128×128 pixels (S6002: NO), the upper left and lower right positions of the referable area are calculated (S6003). Let the upper left of the referable area be ( xAvlTL, yAvlTL ) and the lower right be ( xAvlBR, yAvlBR ),
NL = Min( 1, 7 - CtbLog2SizeY ) - ( 1 << ((7 - CtbLog2SizeY) << 1) )
( xAvlTL, yAvlTL ) = ( ((xCb >> CtbLog2SizeY) + NL) << CtbLog2SizeY,
(yCb >> CtbLog2SizeY) << CtbLog2SizeY )
( xAvlBR, yAvlBR ) = ( ((xCb >> CtbLog2SizeY) << CtbLog2SizeY) - 1,
(((yCb >> CtbLog2SizeY) + 1) << CtbLog2SizeY) - 1 )
becomes. Here, the CTU size is CtbLog2SizeY.

Next, it is determined whether or not the reference position in the x direction of the reference block is smaller than the upper left of the referenceable area (S6004). If the determination is false (S6004: NO), the process proceeds to the next process (S6006). On the other hand, if the determination is true (S6004: YES), the x-direction reference position is corrected so as to match the upper left of the referable area (S6005).

FIG. 49 is a diagram showing how the reference position is corrected. Reference numeral 6001 denotes a coding tree block to be processed, 6002 denotes a coding block to be processed, and 6003 denotes a referable region. Now, assuming that the reference block r2 is located at 6011, the x-direction reference position is smaller than the upper left of the referable area (S6004: YES). Therefore, xRefTL=xAvlTL and the reference position is corrected to the position of 6012 (S6005). Here, since xRefBR=xRefTL+cbWidth-1 as in S6001, xRefBR is also corrected along with the correction of xRefTL. In correcting this reference position, the block vector mvL[0] may be corrected. in short,
mvL[0] = (xAvlTL - xCb) << 4
and correct. As a result, xRefTL=xAvlTL, so the reference position can be corrected.

In this way, when the reference block is located outside the referable area, it becomes referable by correcting the reference position.

Assume that some block vectors in the block vector candidate list constructed by the intra block copy prediction unit 352 are outside the referable area. If the reference position is not corrected, reference by those block vectors is impossible, so those block vectors cannot be candidates for the IBC merge mode. On the other hand, when correcting the reference position in the present invention, all block vectors in the constructed block vector candidate list are inside the referable area. Therefore, all block vectors can be referenced, and all block vectors can be candidates for the IBC merge mode. Therefore, the IBC merge mode selection unit 374 can select the optimum prediction mode from the IBC merge mode candidates corresponding to all block vectors, thereby improving the coding efficiency.

Assume that some block vectors in the block vector candidate list constructed by the intra block copy prediction unit 362 are outside the referable area. If the reference position is not corrected, reference by those block vectors is impossible, so decoding in IBC merge mode using those block vectors is impossible. In a non-inventive coding apparatus, the merge index indicating the IBC merge mode using those block vectors behaves as if they were not coded. However, due to malfunctions, etc., such a merge index may be encoded to generate a bitstream. Alternatively, part of the bitstream may be lost due to packet loss or the like, and the decoded result may become such a merge index. When trying to decode such an incomplete bitstream, there is a possibility of accessing the decoded image memory at an incorrect position by trying to refer to the outside of the referenceable area. As a result, the decoding result differs depending on the decoding device, or the decoding process stops. On the other hand, when the reference position is corrected in the present invention, all block vectors in the constructed block vector candidate list are inside the referable area. Therefore, even if such an incomplete bitstream is decoded, the reference position is corrected to the inside of the referenceable area and the reference can be made. By correcting the reference position in this way, the memory access range is guaranteed. As a result, the decoding result becomes the same depending on the decoding device, and the decoding process can be continued, so that the robustness of the decoding device can be improved.

Further, when correcting a block vector in correcting a reference position, the target is a block vector of luminance. Here, the chrominance block vector is calculated from the luminance block vector. In other words, if the luminance block vector is corrected, the chrominance block vector is also corrected. Therefore, there is no need to correct the reference position again for the color difference. The amount of processing can be reduced compared to the need to determine whether or not the block vector can be referenced using both luminance and color difference when the block vector is not corrected.

In addition, when the block vector is corrected in correcting the reference position, the corrected block vector is stored in the encoding information storage memory 111 or the encoding information storage memory 205 as the block vector of the encoding block to be processed. That is, the corrected reference position and the position indicated by the block vector are the same. Here, deblocking filter processing may be performed when saving the decoded result in the decoded image memory. In this filtering process, the strength of the filter is controlled by the difference between the block vectors of two blocks facing the block boundary. When the block vector is not corrected, the corrected reference position and the position indicated by the block vector are different. Compared to this, the strength of the filter is more appropriate, so that the coding efficiency can be improved.

Subsequently, it is determined whether or not the reference position of the reference block in the y direction is smaller than the upper left of the referenceable area (S6006). If the determination is false (S6006: NO), the process proceeds to the next process (S6008). On the other hand, if the determination is true (S6006: YES), the reference position in the y direction is corrected to match the upper left of the referable area (S6007).

Now, assuming that the reference block r4 is located at 6021, the reference position in the y direction is smaller than the upper left of the referable area (S6006: YES). Therefore, yRefTL=yAvlTL and the reference position is corrected to the position of 6022 (S6007). Here, since yRefBR=yRefTL+cbHeight-1 as in S6001, yRefBR is also corrected as yRefTL is corrected. In correcting this reference position, the block vector mvL[1] may be corrected. in short,
mvL[1] = (yAvlTL - yCb) << 4
and correct. As a result, yRefTL=yAvlTL, so the reference position can be corrected.

Subsequently, it is determined whether or not the reference position of the reference block in the x direction is larger than the lower right of the referable area (S6008). If the determination is false (S6008: NO), proceed to the next process (S6010). On the other hand, if the determination is true (S6008: YES), the x-direction reference position is corrected so as to match the bottom right of the referable area (S6009).

Now, assuming that the reference block r7 is located at 6031, the x-direction reference position is greater than the bottom right of the referable area (S6008: YES). Therefore, xRefBR=xAvlBR and the reference position is corrected to the position of 6032 (S6009). Here, since xRefBR=xRefTL+cbWidth-1, that is, xRefTL=xRefBR-(cbWidth-1) as in S6001, xRefTL is also corrected along with the correction of xRefBR. In correcting this reference position, the block vector mvL[0] may be corrected. in short,
mvL[0] = (xAvlBR - (xCb + cbWidth - 1)) << 4
and correct. As a result, xRefBR=xAvlBR, so the reference position can be corrected.

Subsequently, it is determined whether or not the y-direction reference position of the reference block is larger than the lower right of the referable area (S6010). If the determination is false (S6010: NO), the process ends. On the other hand, if the determination is true (S6010: YES), the reference position in the y direction is corrected so as to match the bottom right of the referable area (S6011).

Now, assuming that the reference block r5 is located at 6041, the reference position in the y direction is greater than the bottom right of the referable area (S6010: YES). Therefore, yRefBR=yAvlBR and the reference position is corrected to the position of 6042 (S6011). Here, as in S6001, yRefBR=yRefTL+cbHeight-1, that is, yRefTL=yRefBR-(cbHeight-1), so yRefTL is also corrected along with the correction of yRefBR. In correcting this reference position, the block vector mvL[1] may be corrected. in short,
mvL[1] = (yAvlBR - (yCb + cbHeitght - 1)) << 4
and correct. As a result, yRefBR=yAvlBR, so the reference position can be corrected.

Here, the case where the reference block r1 is positioned at 6051 will be described. In this case, the reference position in the x direction is corrected in the same way as when the reference block is r2. Furthermore, the reference position in the y direction is corrected in the same way as when the reference block is r4. As a result, the reference block r1 is located at 6052 inside the referable area.

When the reference block r3 is located at 6061, the reference block r6 is located at 6062, and the reference block r8 is located at 6063, the reference positions in the x and y directions are changed in the same manner as above. to correct. As a result, each reference block is located inside the referenceable area.

The above completes the processing when the size of the CTU is not 128×128 pixels. On the other hand, if the size of the CTU is 128×128 pixels (S6002: YES), the upper left and lower right positions of the rectangular referable area are calculated (S6012).

FIG. 50 is a diagram for explaining the upper left and lower right positions when the referable area is rectangular. In the case of FIG. 50A, the encoding tree block 6101 to be processed is divided into four, and the encoding block 6102 to be processed is positioned on the upper left of the division. At this time, the referable area becomes an inverted L shape as indicated by the hatched area in 6103 . If the referable area is rectangular, its range is the rectangular range 6103 . If the referable area is rectangular, and the upper left of the reference block is ( xRefTL, yRefTL ) and the lower right is ( xRefBR, yRefBR ),
offset[4] = {0, 64, 128, 128}
NL = -offset[3 - blk_idx], NR = offset[blk_idx]
( xAvlTL, yAvlTL ) = ( (xCb >> CtbLog2SizeY) << CtbLog2SizeY + NL,
(yCb >> CtbLog2SizeY) << CtbLog2SizeY )
( xAvlBR, yAvlBR ) = ( ((xCb >> CtbLog2SizeY) << CtbLog2SizeY) - 1 + NR,
(((yCb >> CtbLog2SizeY) + 1) << CtbLog2SizeY) - 1 )
becomes. Here, blk_idx is an index indicating the position of the encoding block to be processed. When the encoding tree block to be processed is divided into four and the encoding block to be processed is located in the upper left, blk_idx=0. Similarly, blk_idx is set to 1, 2, and 3 when the encoding blocks to be processed are positioned at the upper right, lower left, and lower right, respectively. FIG. 50A is a diagram showing the case of blk_idx=0. Similarly, FIGS. 50B to 50D are diagrams showing cases where blk_idx=1 to 3, respectively.

Next, the reference position of the portion where the referable area is not rectangular is corrected (S6013). FIG. 51 is a flowchart for explaining the process of correcting the reference position of a portion where the referable area is not rectangular. First, the upper left position of the referable area is calculated (S6021). Since the referenceable area is the shaded area in FIG. 50, there are two points 6111 and 6112 in the upper left position except for the case of blk_idx=3. Assuming (X1, Y1) and (X2, Y2) respectively,
offset[4] = {64, 128, 64, 0}, NL = offset[blk_idx]
(X1, Y1) = (xAvTL, yAvTL + 64)
(X2, Y2) = (xAvlTL + NL, yAvlTL)
becomes.

Next, it is determined whether or not to correct the reference position so as to match the upper left of the referable area (S6022). This determination is true if blk_idx=3 and the reference block is located in an area smaller than X2 and Y1 (S6022: YES). If false (S6022: NO), the process proceeds to the next process (S6026).

Next, it is determined whether or not the difference between the reference block and the referable area in the x direction is smaller than the difference between the reference block and the referable area in the y direction (S6023). If the determination is true (S6023: YES), the x-direction reference position is corrected (S6024). On the other hand, if the determination is false (S6023: NO), the reference position in the y direction is corrected (S6025).

FIG. 52A is a diagram showing how the reference position is corrected in S6024 and S6025. Now blk_idx=0. Assuming that the reference block r1 is located at 6201, blk_idx=3 and the upper left of the reference block is located in an area smaller than X2 (x direction of 6112) and Y1 (y direction of 6111) (S6022: YES). Also, the difference between the reference block and the referable area in the x direction is smaller than the difference between the reference block and the referable area in the y direction (S6023: YES). Therefore, xRefTL=xAvlTL+NL and the x-direction reference position is corrected to the position 6202 (S6024). Here, since xRefBR=xRefTL+cbWidth-1 as in S6001, xRefBR is also corrected along with the correction of xRefTL. In correcting this reference position, the block vector mvL[0] may be corrected. in short,
mvL[0] = (xAvlTL + NL - xCb) << 4
and correct. As a result, xRefTL=xAvlTL+NL, so the reference position can be corrected.

On the other hand, if the reference block r2 is located at 6203, blk_idx=3 and the upper left of the reference block is located in an area smaller than X2 (x direction of 6112) and Y1 (y direction of 6111) ( S6022: YES). Also, the difference between the reference block and the referable area in the x direction is not smaller than the difference between the reference block and the referable area in the y direction (S6023: NO). Therefore, yRefTL=yAvlTL+64 and the reference position in the y direction is corrected to the position of 6204 (S6025). Here, since yRefBR=yRefTL+cbHeight-1 as in S6001, yRefBR is also corrected as yRefTL is corrected. In correcting this reference position, the block vector mvL[0] may be corrected. in short,
mvL[1] = (yAvlTL + 64 - yCb) << 4
and correct. As a result, yRefTL=yAvlTL+64, so the reference position can be corrected.

Assume here that the reference block r3 is located at 6205 . In this case, the difference between the reference block and the referable area in the x direction is smaller than the difference between the reference block and the referable area in the y direction (S6023: YES). Therefore, by correcting the reference position in the x direction in the same manner as the reference block r1, it is positioned at 6206 (S6024). At this point, the reference block is outside the referenceable area. However, the reference position in the y direction is corrected by the processing of S6006 and S6007, which will be described later. After all, the reference block is inside the referable area.

Subsequently, the lower right position of the referable area is calculated (S6026). Since the referable area is the shaded area in FIG. 50, there are two points 6113 and 6114 in the lower right position except for the case of blk_idx=0. Assuming (X3, Y3) and (X4, Y4) respectively,
offset[4] = {0, 64, 128, 64}, NR = offset[blk_idx]
(X3, Y3) = (xAvlBR, yAvlBR - 64)
(X4, Y4) = (xAvlBR - NR, yAvlBR)
becomes.

Next, it is determined whether or not the reference position is to be corrected according to the lower right of the referable area (S6027). This determination is true if blk_idx=0 and the reference block is located in an area larger than X4 and Y3 (S6027: YES). If false (S6027: NO), the process ends.

Next, it is determined whether or not the difference between the reference block and the referable area in the x direction is smaller than the difference between the reference block and the referable area in the y direction (S6028). If the determination is true (S6028: YES), the x-direction reference position is corrected (S6029). On the other hand, if the determination is false (S6028: NO), the reference position in the y direction is corrected (S6030).

FIG. 52B is a diagram showing how the reference position is corrected in S6029 and S6030. Now blk_idx=3. Assuming that the reference block r1 is located at 6211, blk_idx=0 and the lower right of the reference block is located in an area larger than X4 (x direction of 6114) and Y3 (y direction of 6113) (S6027 : YES). Also, the difference between the reference block and the referable area in the x direction is smaller than the difference between the reference block and the referable area in the y direction (S6028: YES). Therefore, xRefBR=xAvlBR and the x-direction reference position is corrected to the position of 6212 (S6029). Here, since xRefBR=xRefTL+cbWidth-1, that is, xRefTL=xRefBR-(cbWidth-1) as in S6001, xRefTL is also corrected along with the correction of xRefBR. In correcting this reference position, the block vector mvL[0] may be corrected. in short,
mvL[0] = (xAvlBR - NR - (xCb + cbWitdh - 1)) << 4
and correct. As a result, xRefBR=xAvlBR, so the reference position can be corrected.

On the other hand, if the reference block r2 is located at 6213, blk_idx=0 is not set and the lower right of the reference block is located in an area larger than X4 (x direction of 6114) and Y3 (y direction of 6113). (S6027: YES). Also, the difference between the reference block and the referable area in the x direction is not smaller than the difference between the reference block and the referable area in the y direction (S6028: NO). Therefore, yRefBR=yAvlBR and the reference position in the y direction is corrected to the position of 6214 (S6030). Here, as in S6001, yRefBR=yRefTL+cbHeight-1, that is, yRefTL=yRefBR-(cbHeight-1), so yRefTL is also corrected along with the correction of yRefBR. In correcting this reference position, the block vector mvL[1] may be corrected. in short,
mvL[1] = (yAvlBR - 64 - (yCb + cbHeight - 1)) << 4
and correct. As a result, yRefBR=yAvlBR, so the reference position can be corrected.

Assume that the reference block r3 is located at 6215. In this case, the difference between the reference block and the referable area in the x direction is not smaller than the difference between the reference block and the referable area in the y direction (S6028: NO). Therefore, by correcting the reference position in the y direction in the same manner as the reference block r2, it is positioned at 6216 (S6030). At this point, the reference block is outside the referenceable area. However, the x-direction reference position is corrected by the processing of S6008 and S6009, which will be described later. After all, the reference block is inside the referable area.

In FIG. 52, the process of correcting the reference position has been described using blk_idx=0 and 3 as examples. In the case of blk_idx=1 or 2, the reference position is corrected in the same way as in the case of blk_idx=0 and 3.

After the processing (S6013) for correcting the reference position of the portion where the referable area is not rectangular, the processing from S6004 to S6011 is performed. The above completes the processing when the size of the CTU is 128×128 pixels.

Assume that in the process of correcting the reference position of the non-rectangular referable area (S6013), the process of correcting the reference position in the x direction (S6024) so as to match the upper left of the referable area is performed. Then, since the reference position of the reference block in the x direction is never smaller than the upper left of the referenceable area, the determination in S6004 is always false (S6004: NO). Therefore, when the processing of S6024 is performed, the processing of S6004 and S6005 may not be performed. Similarly, when S6025 is processed, S6006 and S6007 may be skipped, when S6029 is processed, S6008 and S6009 may be skipped, or when S6030 is processed. In this case, the processing of S6010 and S6011 may be skipped.

Further, in the flowchart of FIG. 51, the comparison processing in step S6023 may be omitted and step S6024 may be always executed, or step S6025 may be always executed. Similarly, the comparison processing in step S6028 may be omitted and step S6029 may be always executed, or step S6030 may be always executed. With such a configuration, it is possible to correct the reference position with simple processing.

In FIG. 48, when the CTU size is 128×128 pixels, the reference position is corrected using the processes of S6012, S6013, and S6004 to S6011. Alternatively, as shown in FIG. 53, it can also be realized by dividing the referable area into two and correcting the respective reference positions (S6101).

FIG. 54 is a diagram for explaining how the referable area is decomposed into two. Unlike FIG. 50 in which the referable area is rectangular, in FIG. 54 the referable area is divided into two. When the coding tree block to be processed (6101) is divided into four and the coding block to be processed (6102) is positioned at the upper left, blk_idx=0. Similarly, blk_idx is set to 1, 2, and 3 when the encoding blocks to be processed are positioned at the upper right, lower left, and lower right, respectively. FIG. 54A is a diagram showing the case of blk_idx=0. Similarly, FIGS. 54B to 54D are diagrams showing cases where blk_idx=1 to 3, respectively. Also, one of the referable areas (6301) is referred to as a referable area A, and the other referable area (6302) is referred to as a referable area B. FIG.

FIG. 55 is a flowchart for explaining processing (S6101) for decomposing the referable area into two and correcting the respective reference positions. In FIG. 55, the same step numbers are assigned to the same processes as in FIG. 48, and the description thereof is omitted. First, the upper left and lower right positions of the referable area A are calculated (S6111). If the upper left of the referable area A is (xAvlTL, yAvlTL) and the lower right is (xAvlBR, yAvlBR),
xOffsetTL[4] = {-128, -128, -64, 0}, yOffsetTL[4] = {64, 64, 64, 0}
xOffsetBR[4] = {0, 0, 0, 128}, yOffsetBR[4] = {128, 128, 128, 64}
( xAvlTL, yAvlTL ) = ( (xCb >> CtbLog2SizeY) << CtbLog2SizeY
+ xOffsetTL[blk_idx],
(yCb >> CtbLog2SizeY) << CtbLog2SizeY + yOffsetTL[blk_idx])
( xAvlBR, yAvlBR ) = ( ((xCb >> CtbLog2SizeY) << CtbLog2SizeY) - 1
+ xOffsetBR[blk_idx],
(((yCb >> CtbLog2SizeY) + 1) << CtbLog2SizeY) - 1 + yOffsetBR[blk_idx] ).

Next, regarding whether or not the reference block is outside the referable area A,
out_xRefTL = xRefTL < xAvlTL
out_yRefTL = yRefTL < yAvlTL
out_xRefBR = xRefBR > xAvlBR
out_yRefBR = yRefBR > yAvlBR
(S6112).

Next, the upper left and lower right positions of the referable area B are calculated (S6113). Let the upper left of the referable area B be ( xAvlTL, yAvlTL ) and the lower right be ( xAvlBR, yAvlBR ),
xOffsetTL[4] = {-64, 0, 0, 0}, yOffsetTL[4] = {0, 0, 0, 0}
xOffsetBR[4] = {0, 64, 128, 64}, yOffsetBR[4] = {128, 64, 64, 128}
( xAvlTL, yAvlTL ) = ( (xCb >> CtbLog2SizeY) << CtbLog2SizeY
+ xOffsetTL[blk_idx],
(yCb >> CtbLog2SizeY) << CtbLog2SizeY + yOffsetTL[blk_idx])
( xAvlBR, yAvlBR ) = ( ((xCb >> CtbLog2SizeY) << CtbLog2SizeY) - 1
+ xOffsetBR[blk_idx],
(((yCb >> CtbLog2SizeY) + 1) << CtbLog2SizeY) - 1 + yOffsetBR[blk_idx] )
becomes.

Next, it is determined whether the x-direction reference position of the reference block is smaller than the upper left of the referable area A and whether the x-direction reference position of the reference block is smaller than the upper left of the referable area B (S6114). If the determination is false (S6114: NO), the process proceeds to the next process (S6116). On the other hand, if the determination is true (S6114: YES), the reference position in the x direction is corrected so as to match the upper left of the referable area B (S6005). Since the process of S6005 has already been explained, the explanation is omitted.

Subsequently, it is determined whether or not the y-direction reference position of the reference block is smaller than the upper left of the referable area A and the y-direction reference position of the reference block is smaller than the upper left of the referable area B (S6116). If the determination is false (S6116: NO), the process proceeds to the next process (S6118). On the other hand, if the determination is true (S6116: YES), the reference position in the y direction is corrected to match the upper left of the referable area B (S6007). Since the processing of S6007 has already been explained, the explanation is omitted.

Next, it is determined whether the x-direction reference position of the reference block is greater than the lower right of the referable area A and whether the x-direction reference position of the reference block is greater than the lower right of the referable area B (S6118). . If the determination is false (S6118: NO), proceed to the next process (S6120). On the other hand, if the determination is true (S6118: YES), the reference position in the x direction is corrected so as to match the bottom right of the referable area B (S6009). Since the processing of S6009 has already been explained, the explanation is omitted.

Next, it is determined whether the y-direction reference position of the reference block is greater than the lower right of the referable area A and whether the y-direction reference position of the reference block is greater than the lower right of the referable area B (S6120). . If the determination is false (S6120: NO), the process ends. On the other hand, if the determination is true (S6120: YES), the reference position in the y direction is corrected so as to match the bottom right of the referable area B (S6011). Since the process of S6011 has already been explained, the explanation is omitted.

As described above, when the size of the CTU is 128×128 pixels, even if the reference block is positioned outside the referable area, the reference position can be corrected and referenced. Further, by dividing the referable area into two and correcting the respective reference positions, the processing can be simplified and the amount of calculation can be reduced. Here, one referable area (6301) is referred to as a referable area A, and the other referable area (6302) is referred to as a referable area B. FIG. Alternatively, the referable area A and the referable area B may be exchanged, and one referable area (6301) may be treated as the referable area B and the other referable area (6302) may be treated as the referable area A. .

In this embodiment, it is determined whether or not the size of the CTU is 128×128 pixels (S6002), and the process is switched. This may be done by judging whether or not the intra block copy reference block is a unit obtained by dividing the coding tree block into four, or by judging whether or not the size of the CTU is larger than the maximum size of the coding block. You can do it.

All the embodiments described above may be combined in plural.

In all the embodiments described above, the bitstream output by the image encoding device has a specific data format so that it can be decoded according to the encoding method used in the embodiment. there is The bitstream may be provided by being recorded in a computer-readable recording medium such as an HDD, SSD, flash memory, or optical disk, or may be provided from a server through a wired or wireless network. Therefore, an image decoding device corresponding to this image encoding device can decode the bitstream of this specific data format regardless of the providing means.

When a wired or wireless network is used to exchange a bitstream between an image encoding device and an image decoding device, the bitstream may be converted to a data format suitable for the transmission mode of the communication channel and transmitted. good. In that case, a transmitting device that converts a bitstream output from an image coding device into coded data in a data format suitable for the transmission form of a communication channel and transmits the data to a network, and a bitstream that receives the coded data from the network and a receiving device for restoring the image to the image decoding device. The transmission device includes a memory that buffers the bitstream output from the image encoding device, a packet processing unit that packetizes the bitstream, and a transmission unit that transmits the packetized encoded data via the network. The receiving device includes a receiving unit that receives packetized encoded data via a network, a memory that buffers the received encoded data, packet processing of the encoded data to generate a bitstream, and image decoding. and a packet processor for providing to the device.

When a wired or wireless network is used to exchange bitstreams between an image encoding device and an image decoding device, in addition to the transmitting device and the receiving device, the encoded data transmitted by the transmitting device is received. , a relay device may be provided that feeds the receiving device. The relay device includes a receiver that receives packetized encoded data transmitted by the transmitter, a memory that buffers the received encoded data, and a transmitter that transmits the packetized encoded data and the network. include. Further, the relay device includes a reception packet processing unit that packetizes packetized encoded data to generate a bitstream, a recording medium that stores the bitstream, and a transmission packet processing unit that packetizes the bitstream. But it's okay.

Further, the display device may be configured by adding a display unit for displaying an image decoded by the image decoding device. In this case, the display unit reads the decoded image signal generated by the decoded image signal superimposition unit 207 and stored in the decoded image memory 208 and displays it on the screen.

Further, an imaging device may be configured by adding an imaging unit to the configuration and inputting a captured image to an image encoding device. In that case, the imaging unit inputs the image signal of the imaged image to the block dividing unit 101 .

FIG. 37 shows an example of the hardware configuration of the encoding/decoding device of this embodiment. The encoding/decoding device includes the configurations of the image encoding device and the image decoding device according to the embodiment of the present invention. The encoding/decoding device 9000 has a CPU 9001 , a codec IC 9002 , an I/O interface 9003 , a memory 9004 , an optical disk drive 9005 , a network interface 9006 and a video interface 9009 .

An image encoding unit 9007 and an image decoding unit 9008 are typically implemented as a codec IC 9002 . Image encoding processing of the image encoding device according to the embodiment of the present invention is performed by the image encoding unit 9007, and image decoding processing in the image decoding device according to the embodiment of the present invention is performed by the image decoding unit 9008. executed. The I/O interface 9003 is realized by, for example, a USB interface, and connects with an external keyboard 9104, mouse 9105, and the like. The CPU 9001 controls the encoding/decoding device 9000 to execute the operation desired by the user based on the user's operation input via the I/O interface 9003 . User operations using the keyboard 9104, mouse 9105, etc. include selection of which function to execute, encoding or decoding, setting of encoding quality, bitstream input/output destination, image input/output destination, and the like.

When the user desires to reproduce the image recorded on the disc recording medium 9100, the optical disc drive 9005 reads the bitstream from the inserted disc recording medium 9100 and transmits the read bitstream via the bus 9010. It is sent to the image decoding unit 9008 of the codec IC 9002 . The image decoding unit 9008 executes image decoding processing in the image decoding apparatus according to the embodiment of the present invention on the input bitstream, and sends the decoded image to the external monitor 9103 via the video interface 9009 . The encoding/decoding device 9000 also has a network interface 9006 and can be connected to an external distribution server 9106 and a mobile terminal 9107 via a network 9101 . If the user desires to reproduce the image recorded in the distribution server 9106 or portable terminal 9107 instead of the image recorded in the disk recording medium 9100, the network interface 9006 receives the image from the input disk recording medium 9100. Instead of reading the bitstream, the bitstream is obtained from the network 9101 . Further, when the user desires to reproduce the image recorded in the memory 9004, the bitstream recorded in the memory 9004 is subjected to image decoding processing in the image decoding apparatus according to the embodiment of the present invention. do.

When the user desires an operation to encode an image captured by the external camera 9102 and record it in the memory 9004, the video interface 9009 inputs the image from the camera 9102 and transmits the image to the image encoding unit 9007 of the codec IC 9002 via the bus 9010. send to The image coding unit 9007 executes image coding processing in the image coding apparatus according to the embodiment of the present invention on the image input via the video interface 9009 to create a bitstream. The bitstream is then sent to memory 9004 via bus 9010 . When the user desires to record a bitstream on the disk recording medium 9100 instead of the memory 9004, the optical disk drive 9005 writes the bitstream to the inserted disk recording medium 9100. FIG.

It is also possible to realize a hardware configuration having an image encoding device but not having an image decoding device, or a hardware configuration having an image decoding device but not having an image encoding device. Such a hardware configuration is realized, for example, by replacing the codec IC 9002 with the image encoding unit 9007 or the image decoding unit 9008, respectively.

The above encoding and decoding processes may of course be implemented as transmission, storage, and reception devices using hardware, and are stored in ROM (read only memory), flash memory, or the like. It may be implemented by firmware or software such as a computer. The firmware program and software program may be recorded in a computer-readable recording medium and provided, may be provided from a server through a wired or wireless network, or may be provided from a terrestrial or satellite digital broadcasting data broadcast. may be provided as

The present invention has been described above based on the embodiments. It should be understood by those skilled in the art that the embodiment is an example, and that various modifications are possible in the combination of each component and each treatment process, and that such modifications are within the scope of the present invention. .

100 image coding device, 101 block division unit, 102 inter prediction unit, 103 intra prediction unit, 104 decoded image memory, 105 prediction method determination unit, 106 residual generation unit, 107 orthogonal transformation/quantization unit, 108 bit string coding Section 109 Inverse Quantization/Inverse Orthogonal Transformation Section 110 Decoded Image Signal Superposition Section 111 Encoded Information Storage Memory 200 Image Decoding Device 201 Bit String Decoding Section 202 Block Division Section 203 Inter Prediction Section 204 Intra Prediction Section , 205 encoded information storage memory, 206 inverse quantization/inverse orthogonal transform unit, 207 decoded image signal superimposition unit, 208 decoded image memory.

Claims (6)

An image encoding device that encodes in units of intra block copy reference blocks,
a block vector candidate list generator for generating a block vector candidate list by deriving block vector candidates of a block to be processed in a picture to be processed from the coding information stored in the coding information storage memory;
a filling unit that fills the block vector candidate list with (0, 0) so as to fill the block vector candidate list;
a selection unit that selects a selected block vector from the block vector candidate list;
an encoding unit that encodes a block vector index indicating the position of the selected block vector in the block vector candidate list;
a reference position correction unit that corrects the reference position of the reference block referenced by the selected block vector so as to refer to the inside of the referable area;
a prediction unit that acquires, from a decoded image memory, decoded pixels in the target picture as prediction values of the target block based on the reference position of the reference block;
The reference position correcting unit determines whether or not the encoding process is completed with a fixed number of intra block copy reference blocks encoded immediately before the intra block copy reference block including the target block as a referenceable area. irrespectively, an intra block copy reference block preceding the referable area and an intra block copy reference block including the target block are set as invalid reference areas. An image encoding method for encoding in units of intra block copy reference blocks,
a block vector candidate list generation step of generating a block vector candidate list by deriving block vector candidates of a block to be processed in a picture to be processed from the coding information stored in the coding information storage memory;
a filling step of filling the block vector candidate list with (0, 0) to fill the block vector candidate list;
a selecting step of selecting a selected block vector from the block vector candidate list;
an encoding step of encoding a block vector index indicating the position of the selected block vector in the block vector candidate list;
a reference position correcting step of correcting the reference position of the reference block referenced by the selected block vector so as to refer to the inside of the referable area;
a prediction step of obtaining a decoded pixel in the target picture as a predicted value of the target block from a decoded image memory based on the reference position of the reference block;
In the reference position correcting step, a fixed number of intra block copy reference blocks encoded immediately before the intra block copy reference block including the target block is set as a referenceable area, and whether or not the encoding process is completed. An image coding method, wherein an intra block copy reference block preceding said referable area and an intra block copy reference block including said block to be processed are set as invalid reference areas. An image encoding program for encoding in units of intra block copy reference blocks,
a block vector candidate list generation step of generating a block vector candidate list by deriving block vector candidates of a block to be processed in a picture to be processed from the coding information stored in the coding information storage memory;
a filling step of filling the block vector candidate list with (0, 0) to fill the block vector candidate list;
a selecting step of selecting a selected block vector from the block vector candidate list;
an encoding step of encoding a block vector index indicating the position of the selected block vector in the block vector candidate list;
a reference position correcting step of correcting the reference position of the reference block referenced by the selected block vector so as to refer to the inside of the referable area;
causing a computer to execute a prediction step of obtaining, from a decoded image memory, decoded pixels in the target picture as predicted values of the target block, based on the reference position of the reference block;
In the reference position correcting step, a fixed number of intra block copy reference blocks encoded immediately before the intra block copy reference block including the target block is set as a referenceable area, and whether or not the encoding process is completed. 1. An image encoding program, wherein an intra block copy reference block preceding said referable area and an intra block copy reference block including said block to be processed are set as invalid reference areas regardless of the above. An image decoding device for decoding in units of intra block copy reference blocks,
a block vector candidate list generator for generating a block vector candidate list by deriving block vector candidates of a block to be processed in a picture to be processed from the coding information stored in the coding information storage memory;
a filling unit that fills the block vector candidate list with (0, 0) so as to fill the block vector candidate list;
a decoding unit that decodes a block vector index indicating the position of the selected block vector in the block vector candidate list;
a selection unit that selects the selected block vector from the block vector candidate list based on the block vector index;
a reference position correction unit that corrects the reference position of the reference block referenced by the selected block vector so as to refer to the inside of the referable area;
a prediction unit that acquires, from a decoded image memory, decoded pixels in the target picture as prediction values of the target block based on the reference position of the reference block;
The reference position correction unit sets a fixed number of intra block copy reference blocks decoded immediately before the intra block copy reference block including the target block as a referenceable area, regardless of whether or not the decoding process is completed. First, an intra block copy reference block preceding the referable area and an intra block copy reference block including the target block are set as invalid reference areas. An image decoding method for decoding in units of intra block copy reference blocks,
a block vector candidate list generation step of generating a block vector candidate list by deriving block vector candidates of a block to be processed in a picture to be processed from the coding information stored in the coding information storage memory;
a filling step of filling the block vector candidate list with (0, 0) to fill the block vector candidate list;
a decoding step of decoding a block vector index indicating the position of the selected block vector in the block vector candidate list;
a selecting step of selecting the selected block vector from the block vector candidate list based on the block vector index ;
a reference position correcting step of correcting the reference position of the reference block referenced by the selected block vector so as to refer to the inside of the referable area;
a prediction step of obtaining a decoded pixel in the target picture as a predicted value of the target block from a decoded image memory based on the reference position of the reference block;
In the reference position correcting step, a fixed number of intra block copy reference blocks decoded immediately before the intra block copy reference block including the target block is set as a referenceable area, regardless of whether or not the decoding process is completed. First, an intra block copy reference block preceding the referable area and an intra block copy reference block including the target block are set as invalid reference areas. An image decoding program for decoding in units of intra block copy reference blocks,
a block vector candidate list generation step of generating a block vector candidate list by deriving block vector candidates of a block to be processed in a picture to be processed from the coding information stored in the coding information storage memory;
a filling step of filling the block vector candidate list with (0, 0) to fill the block vector candidate list;
a decoding step of decoding a block vector index indicating the position of the selected block vector in the block vector candidate list;
a selecting step of selecting the selected block vector from the block vector candidate list based on the block vector index;
a reference position correcting step of correcting the reference position of the reference block referenced by the selected block vector so as to refer to the inside of the referable area;
causing a computer to execute a prediction step of obtaining, from a decoded image memory, decoded pixels in the target picture as predicted values of the target block, based on the reference position of the reference block;
In the reference position correcting step, a fixed number of intra block copy reference blocks decoded immediately before the intra block copy reference block including the target block is set as a referenceable area, regardless of whether or not the decoding process is completed. An image decoding program characterized by first setting an intra block copy reference block preceding said referable area and an intra block copy reference block including said block to be processed as an invalid reference area.

Images