JP7354610B2 - Image encoding device, image encoding method, and image encoding program - Google Patents

Description

The present invention relates to an image encoding and decoding technique that performs prediction by dividing an image into blocks.

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 processing is performed on a block-by-block basis. Encoding efficiency is improved by dividing into appropriate blocks and appropriately setting intra-frame prediction (intra prediction) and inter-frame prediction (inter prediction).

Patent Document 1 discloses an intra prediction technique that obtains a predicted image using decoded pixels adjacent to a block to be encoded/decoded.

Japanese Patent Application Publication No. 2009-246975

However, the technique disclosed in Patent Document 1 uses only decoded pixels adjacent to a block to be encoded/decoded for prediction, and has poor prediction efficiency.

An aspect of the present invention for solving the above problems includes a block vector candidate deriving unit that derives a block vector candidate for a block to be processed in a picture to be processed from encoding information stored in an encoding information storage memory; a selection unit that selects a selected block vector from candidates; and a selection unit that determines, from a plurality of referenceable areas, a referenceable area that includes a predetermined position of a reference block to be referenced by the selected block vector; For a first divided reference block included in the possible area, decoded pixels in the processing target picture are obtained from a decoded image memory unit as a predicted value of the processing target block based on the reference position of the reference block. However, for a second divided reference block included in a referenceable area that does not include the predetermined position of the reference block, a reference area boundary correction unit that uses a predetermined value as a predicted value of the processing target block is provided.

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

FIG. 1 is a block diagram of an image encoding 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. 12 is a flowchart for explaining the operation of dividing a tree block. FIG. 3 is a diagram showing how an input image is divided into tree blocks. FIG. 2 is a diagram illustrating z-scan. FIG. 3 is a diagram showing a divided shape of blocks. 3 is a flowchart for explaining the operation of dividing a block into four parts. 12 is a flowchart for explaining the operation of dividing a block into two or three. This is a syntax for expressing the shape of block division. FIG. 2 is a diagram for explaining intra prediction. FIG. 3 is a diagram for explaining a reference block for inter prediction. This is a syntax for expressing a coded block prediction mode. FIG. 3 is a diagram showing the correspondence between syntax elements and modes regarding inter prediction. FIG. 3 is a diagram for explaining affine transformation motion compensation for two control points. FIG. 3 is a diagram for explaining affine transformation motion compensation for three control points. 2 is a block diagram of a detailed configuration of an inter prediction unit 102 in FIG. 1. FIG. 17 is a block diagram of a detailed configuration of the normal predicted motion vector mode deriving unit 301 in FIG. 16. FIG. 17 is a block diagram of a detailed configuration of the normal merge mode deriving unit 302 in FIG. 16. FIG. 17 is a flowchart for explaining normal predicted motion vector mode derivation processing by the normal predicted motion vector mode derivation unit 301 of FIG. 16. FIG. 3 is a flowchart illustrating the processing procedure of normal predicted motion vector mode derivation processing. 3 is a flowchart illustrating the procedure of normal merge mode derivation processing. 3 is a block diagram of a detailed configuration of an inter prediction unit 203 in FIG. 2. FIG. 23 is a block diagram of a detailed configuration of a normal predicted motion vector mode deriving unit 401 in FIG. 22. FIG. 23 is a block diagram of a detailed configuration of the normal merge mode deriving unit 402 in FIG. 22. FIG. 23 is a flowchart for explaining normal predicted motion vector mode derivation processing by the normal predicted motion vector mode derivation unit 401 of FIG. 22. FIG. 12 is a flowchart illustrating a historical predicted motion vector candidate list initialization/update processing procedure. 12 is a flowchart of a same element confirmation process in a history predicted motion vector candidate update process. 12 is a flowchart of an element shift processing procedure in a historical predicted motion vector candidate update processing procedure. 3 is a flowchart illustrating a procedure for deriving historical predicted motion vector candidates. 3 is a flowchart illustrating a history merging candidate derivation processing procedure. FIG. 3 is a diagram illustrating an example of a history predicted motion vector candidate list update process. FIG. 3 is a diagram illustrating an effective reference area for intra block copy. FIG. 7 is a diagram for explaining motion compensated prediction in the case where the L0 reference picture (RefL0Pic) is at a time earlier than the processing target picture (CurPic) in L0 prediction. FIG. 7 is a diagram for explaining motion compensated prediction in a case where a reference picture for L0 prediction is at a later time than a processing target picture in L0 prediction. FIG. 7 is a diagram for explaining motion compensated prediction in the case where the reference picture for L0 prediction is at a time before the picture to be processed and the reference picture for L1 prediction is at a time after the picture to be processed in bi-prediction. . FIG. 7 is a diagram for explaining a prediction direction of motion compensation prediction when bi-prediction is performed and a reference picture for L0 prediction and a reference picture for L1 prediction are at a time earlier than a processing target picture. FIG. 7 is a diagram for explaining a prediction direction of motion compensation prediction when bi-prediction is used and a reference picture for L0 prediction and a reference picture for L1 prediction are located at a later time than the processing target picture. 3 is a flowchart illustrating an average merging candidate derivation processing procedure. 3 is a table showing information regarding merge difference motion vectors. FIG. 3 is a diagram illustrating derivation of a merge difference motion vector. FIG. 2 is a block diagram of a detailed configuration of an intra prediction unit 103 in FIG. 1. 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. 12 is a flowchart for explaining predicted intra block copy processing by an intra block copy prediction unit 352. FIG. 12 is a flowchart for explaining predicted intra block copy processing by an intra block copy prediction unit 362. FIG. 3 is a flowchart for explaining merge intra block copy processing. 12 is a flowchart illustrating a processing procedure for block vector mode derivation processing for predictive intra block copying. FIG. 4 is a diagram illustrating processing of a reference position correction unit 380 and a reference position correction unit 480. FIG. 3 is a diagram showing how a reference position is corrected. It is a figure explaining the position of the upper left and the lower right when a reference possible area|region is made into a rectangular shape. FIG. 6 is a diagram illustrating a process of correcting a reference position in a portion where the referenceable area is not rectangular. FIG. 3 is a diagram showing how a reference position is corrected. FIG. 4 is a diagram illustrating processing of a reference position correction unit 380 and a reference position correction unit 480. FIG. 3 is a diagram illustrating how a referenceable area is divided into two. FIG. 6 is a diagram illustrating a process of dividing a referenceable area into two parts and correcting the respective reference positions. FIG. 7 is a diagram for explaining a memory space of a reference area when a coded tree block unit is used as an intra block copy reference block. FIG. 7 is a diagram for explaining a memory space of a reference area when determining an effective reference area, using a unit obtained by dividing a coding tree block into four as an intra block copy reference block. 3 is a flowchart for explaining a reference area boundary correction procedure. FIG. 6 is a diagram for explaining division of a reference block in a memory space when a coded tree block unit is used as an intra block copy reference block. FIG. 4 is a diagram for explaining the division of a reference block in a memory space when determining an effective reference area by using a unit obtained by dividing a coding tree block into four as an intra block copy reference block.

The technology and technical terms used in this embodiment will be defined.

<Tree block>
In the embodiment, an image to be encoded/decoded is equally divided into predetermined sizes. This unit is defined as a tree block. In FIG. 4, the size of the tree block is 128x128 pixels, but the size of the tree block is not limited to this and may be set to any size. Tree blocks to be processed (corresponding to encoding targets in encoding processing and decoding targets in decoding processing) are 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 divided. A block to be encoded/decoded after recursively dividing a tree block is defined as an encoded block. Furthermore, tree blocks and encoded blocks are collectively defined as blocks. Efficient encoding becomes possible by performing appropriate block division. The size of the tree block may be a fixed value determined in advance by the encoding device and the decoding device, or a configuration may be adopted in which the size of the tree block determined by the encoding device is transmitted to the decoding device. Here, the maximum size of a tree block is 128x128 pixels, and the minimum size of a tree block is 16x16 pixels. Further, the maximum size of the encoded block is 64x64 pixels, and the minimum size of the encoded block is 4x4 pixels.

<Prediction mode>
Processed images of the target image are processed in units of encoded blocks (in the encoding process, signals that have been encoded are used as decoded images, image signals, tree blocks, blocks, encoded blocks, etc.; in the decoding process, Intra prediction (MODE_INTRA) that makes predictions from the surrounding image signals of decoded images, image signals, tree blocks, blocks, encoded blocks, etc.), and Inter prediction that makes predictions from the image signals of processed images. Switch (MODE_INTER). A mode for identifying this 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 target block by referring to decoded pixels in a target picture as a predicted value. The distance from the processing target block to the reference pixel is represented by a block vector. The block vector refers to the picture to be processed, and the reference picture is uniquely determined, so no reference index is required. The difference between a block vector and a motion vector is whether the referenced picture is a current picture or a processed picture. Additionally, block vectors can be selected with 1-pixel precision or 4-pixel precision using adaptive motion vector resolution (AMVR).

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

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 differential block vector. The predicted block vector is derived from a processed block adjacent to the block to be processed and an index for specifying the predicted block vector. The index for specifying the predicted block vector and the differential block vector are transmitted in a bitstream.

The merge intra block copy mode is a mode in which intra block copy prediction information of a block to be processed is derived from intra block copy prediction information of a processed block adjacent to the block to be processed, without transmitting a differential motion vector.

<Inter prediction>
In inter prediction in which prediction is performed from an image signal of a processed image, 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 each reference index. L0 prediction (Pred_L0) is available for P slices. In the B slice, L0 prediction (Pred_L0), L1 prediction (Pred_L1), and bi-prediction (Pred_BI) can be used. L0 prediction (Pred_L0) is inter prediction that refers to a reference picture managed in L0, and L1 prediction (Pred_L1) is inter prediction that refers to a reference picture managed in L1. Bi-prediction (Pred_BI) is inter prediction in which both L0 prediction and L1 prediction are performed and refers to one reference picture managed in each of L0 and L1. Information specifying L0 prediction, L1 prediction, and bi-prediction is defined as inter prediction mode. In the subsequent processing, it is assumed that constants and variables whose outputs have the subscript LX are processed for each L0 and L1.

<Predicted motion vector mode>
The predicted motion vector mode is a mode in which an index for specifying a predicted motion vector, a differential motion vector, an inter prediction mode, and a reference index are transmitted, and inter prediction information of a block to be processed is determined. The predicted motion vector is a predicted motion vector candidate derived from a processed block adjacent to the target block, or a block belonging to the processed image that is located at the same position as the target block (nearby), and a predicted motion vector 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 located at the same position as the target block or in the vicinity (nearby) of the target block, without transmitting the differential motion vector or reference index. This is a mode in which inter prediction information of the block to be processed is derived from inter prediction information of the block to be processed.

A processed block adjacent to the target block and inter prediction information of the processed block are defined as spatial merging candidates. A block belonging to the processed image that is located at the same position as the target block or in its vicinity (nearby), and inter prediction information derived from the inter prediction information of the block are defined as temporal merging 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 that are referred to in order to derive inter prediction information in the motion vector predictor mode and the 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 the same position as the encoding block to be processed in the image to be processed.

A1 and A2 are blocks located on the left side of the encoding block to be processed and adjacent to the encoding block to be processed. B1 and B3 are blocks located above the encoding block to be processed and adjacent to the encoding block to be processed. A0, B0, and B2 are blocks located 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 the motion vector predictor mode and merge mode will be described later.

<Affine transformation motion compensation>
In affine transformation motion compensation, a coded block is divided into subblocks of a predetermined unit, and a motion vector is individually set for each subblock 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 that is located at the same position as the target block or in the vicinity (nearby). Derived based on two or more control points. In this embodiment, the size of the sub-block is 4x4 pixels, but the size of the sub-block is not limited to this, and the motion vector may be derived on a pixel-by-pixel basis.

FIG. 14 shows an example of affine transformation motion compensation when there are two control points. In this case, since the two control points have two parameters, a horizontal component and a vertical component, the affine transformation when there are 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 transformation motion compensation when there are three control points. In this case, since the three control points have two parameters, a horizontal component and a vertical component, the affine transformation when there are three control points is called a six-parameter affine transformation. CP1, CP2, and CP3 in FIG. 15 are control points.

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

<Syntax of encoded block>
The syntax (syntax rules for encoded bit strings) for encoding/decoding the prediction mode of an encoded block will be explained using FIGS. 12(a), 12(b), and FIG. 13. pred_mode_flag in FIG. 12(a) is a flag indicating whether or not inter prediction is performed. If pred_mode_flag is 0, it will be inter prediction, and if pred_mode_flag is 1, it will be intra prediction. In the case of intra prediction, pred_mode_ibc_flag, which is a flag indicating whether it is intra block copy prediction, is encoded/decoded. If it is intra block copy prediction (pred_mode_ibc_flag=1), merge_flag is encoded/decoded. merge_flag is a flag indicating whether to use merge intra block copy mode or predictive intra block copy mode. If it is the merge intra block copy mode (merge_flag=1), the merge index merge_idx is encoded/decoded. If it is not intra block copy prediction (pred_mode_ibc_flag=0), it is normal intra prediction, and normal intra prediction information intra_pred_mode is encoded/decoded.

In the case of inter prediction, merge_flag is encoded/decoded. merge_flag is a flag indicating whether to use merge mode or predicted motion vector mode. In the case of motion vector predictor mode (merge_flag=0), a flag inter_affine_flag indicating whether to apply sub-block motion vector predictor mode is encoded/decoded. When applying sub-block predicted motion vector mode (inter_affine_flag=1), encode/decode cu_affine_type_flag. cu_affine_type_flag is a flag for determining the number of control points in sub-block predicted motion vector mode.

On the other hand, in the case of merge mode (merge_flag=1), regular_merge_flag in FIG. 12(b) is encoded/decoded. regular_merge_flag is a flag indicating whether or not to apply normal merge mode. In the case of regular merge mode (regular_merge_flag=1), encode/decode the merge index merge_idx of regular merge mode. On the other hand, if it is not the regular merge mode (regular_merge_flag=0), a flag merge_subblock_flag indicating whether or not to apply the subblock merge mode is encoded/decoded. In the case of subblock merge mode (merge_subblock_flag=1), encode/decode the merge index merge_subblock_idx. On the other hand, when it is not the subblock merge mode (merge_subblock_flag=0), the block dividing direction merge_triangle_split_dir and the merge triangle indexes merge_triangle_idx0 and merge_triangle_idx1 are encoded/decoded for each of the two divided partitions.

FIG. 13 shows the values of each syntax element 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 sub-block predicted motion vector mode (Inter Affine Mode). merge_flag=1, regular_merge_flag=1 corresponds to normal merge mode (Merge Mode). merge_flag=1, regular_merge_flag=0, merge_subblock_flag=0 corresponds to Triangle Merge Mode. merge_flag=1, regular_merge_flag=0, merge_subblock_flag=1 corresponds to subblock merge mode (Affine Merge Mode).

<POC>
POC (Picture Order Count) is a variable associated with pictures to be encoded, and is set to a value that increases by 1 in the output order of pictures. Depending on the POC value, it is possible to determine whether the pictures are the same, to determine the context between the pictures in the output order, and to 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 one to be output first, and the difference in POC between the two pictures determines the distance between the pictures in the time axis direction. show.

(First embodiment)
An image encoding device 100 and an image decoding device 200 according to a first embodiment of the present invention will be described.

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

The block dividing unit 101 recursively divides an input image to generate encoded blocks. The block division unit 101 includes a 4-division unit that divides the block to be divided into horizontal and vertical directions, and a 2-3 division unit to divide the block to be divided into either the horizontal direction or the vertical direction. . The generated image signal of the encoding block to be processed is supplied to the inter prediction unit 102, the intra prediction unit 103, and the residual signal generation unit 106. Further, information indicating the determined recursive partitioning structure is supplied to the bit string encoding unit 108. The detailed operation of block dividing section 101 will be described later.

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

The intra prediction unit 103 performs intra prediction of the processing target coded block. In intra prediction, a predicted image signal is created from a decoded area of the same image signal as the processing target coded block stored in the decoded image memory 104, and is supplied to the prediction method determining unit 105. The 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 section 110. Further, the decoded image stored in the decoded image memory is supplied to the inter prediction unit 102 and the intra prediction unit 103.

The prediction method determining unit 105 evaluates each prediction using the encoding information, the amount of code of the residual signal, the amount of distortion between the predicted image signal and the image signal to be processed, etc., and determines the optimal prediction. Decide on the mode (inter prediction or intra prediction). In the case of the inter-prediction merge mode, the encoding information of the merge index and information indicating whether or not the sub-block merge mode is selected (sub-block merge flag) is supplied to the bit string encoding unit 108, and the encoding information of the merge index and the information indicating whether or not the sub-block merge mode is selected (sub-block merge flag) is supplied to the bit string encoding unit 108, and In this case, the bit string encoding unit 108 encodes encoding information such as inter prediction mode, predicted motion vector index, reference index of L0 and L1, differential motion vector, and information indicating whether or not it is subblock mode (subblock predicted motion vector flag). supply to. The determined encoded information is supplied to the encoded information storage memory 111.

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

The orthogonal transformation/quantization unit 107 performs orthogonal transformation and quantization on the residual signal according to the quantization parameter, generates an orthogonal transformed/quantized residual signal, and performs orthogonal transformation and quantization on the residual signal, and performs orthogonal transformation and quantization on the residual signal. It is supplied to the conversion/inverse orthogonal transform section 109.

The bit string 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 information in sequence, picture, slice, and encoding block units. Specifically, the prediction mode PredMode and division mode PartMode for each encoding block are encoded. When the prediction mode is intra prediction (PRED_INTRA), a flag (pred_mode_ibc_flag) for determining whether or not it is an intra block copy is encoded. In the case of intra block copy, encoding information such as the merge index in merge mode, the predicted block vector index, differential block vector, etc. in non-merge mode is encoded according to the specified syntax (syntax rules for encoded bit strings), and Generate an encoded bit string of 1. In the case of inter prediction (PRED_INTER), a flag to determine whether or not it is merge mode, subblock merge flag, merge index if merge mode, information about inter prediction mode, predicted motion vector index, and differential motion vector if not merge mode. , a sub-block predicted motion vector flag, and the like are encoded according to a prescribed syntax (syntax rules for encoded bit strings) to be described later to generate a first encoded bit string. Further, the bit string encoding unit 108 entropy encodes the orthogonally transformed and quantized residual signal according to a prescribed syntax to generate a second encoded bit string. The first encoded bit string and the second encoded bit string are multiplexed according to a prescribed syntax, and a bit stream is output.

The inverse quantization/inverse orthogonal transform unit 109 performs inverse quantization and inverse orthogonal transform on the orthogonally transformed/quantized residual signal supplied from the orthogonal transform/quantization unit 107 to calculate a residual signal, and decodes the residual signal. The image signal is supplied to the image signal superimposing section 110.

The decoded image signal superimposing unit 110 superimposes the predicted image signal determined by the prediction method determining unit 105 and the residual signal that has been inversely quantized and inversely orthogonally transformed in the inversely quantized and inversely orthogonally transformed unit 109 to generate a decoded image. is generated and stored in the decoded image memory 104. Note that the decoded image may be stored in the decoded image memory 104 after being subjected to filtering processing to reduce distortion such as block distortion caused by encoding.

The encoding information storage memory 111 stores encoding information such as a prediction mode (inter prediction or intra prediction) determined by the prediction method determining unit 105. In the case of inter prediction, the coding information stored in the coding information storage memory 111 includes the determined motion vector, reference list, and reference index, and in the case of inter prediction merging mode, the merging index, subblock merging mode, etc. Encoding information of information indicating whether or not to merge (sub-block merge flag), in the case of inter-prediction predicted motion vector mode, inter-prediction mode, predicted motion vector index, L0, L1 reference index, differential motion vector, sub-block mode? In the case of intra prediction, information indicating whether or not the prediction is made (sub-block predicted motion vector flag), the determined intra prediction mode, etc. Construction of the history candidate list managed by the encoded information storage memory 111 will be described later.

FIG. 2 is a block diagram showing the configuration of a video decoding device according to an embodiment of the present invention, which corresponds to the video encoding device of FIG. The video decoding device of the embodiment includes a bit string decoding unit 201, a block dividing unit 202, an inter prediction unit 203, an intra prediction unit 204, an encoded information storage memory 205, an inverse quantization/inverse orthogonal transform unit 206, and a decoded image signal. It includes a superimposing section 207 and a decoded image memory 208.

The decoding process of the video decoding device in FIG. 2 corresponds to the decoding process provided inside the video encoding device in FIG. - Each configuration of the inverse orthogonal transform unit 206, decoded image signal superimposition unit 207, and decoded image memory 208 is the inverse quantization/inverse orthogonal transform unit 109, decoded image signal superimposition unit 110, It has functions corresponding to the configurations of encoded information storage memory 111 and decoded image memory 104, respectively.

The bitstream supplied to the bitstream decoding unit 201 is separated according to prescribed syntax rules. The separated first encoded bit string is decoded to obtain information in sequence, picture, slice, encoded block units, and encoding information in encoded block units. Specifically, the prediction mode PredMode and division mode PartMode are decoded to determine whether inter prediction (PRED_INTER) or intra prediction (PRED_INTRA) is performed in each encoded block. In the case of intra prediction (PRED_INTRA), a flag (pred_mode_ibc_flag) for determining whether or not it is an intra block copy is decoded. In the case of intra block copy, encoded information such as the merge index in merge mode and the predicted block vector index and differential block vector in non-merge mode is decoded according to the specified syntax (syntax rules for encoded bit strings) and encoded. The encoded information is supplied to the inter prediction unit 203 or the intra prediction unit 204 and the encoded information storage memory 205. In the case of inter prediction (PRED_INTER), a flag to determine whether or not it is merge mode, in the case of merge mode, the merge index, subblock merge flag, in the case of predicted motion vector mode, the inter prediction mode, predicted motion vector index, differential motion Encoded information regarding vectors, sub-block predicted motion vector flags, etc. is decoded according to a prescribed syntax to be described later, and the encoded information is supplied to inter prediction section 203 or intra prediction section 204 and encoded information storage memory 205. The separated second encoded bit string is decoded to calculate an orthogonally transformed and quantized residual signal, and the orthogonally transformed and quantized residual signal is supplied to the inverse quantization and inverse orthogonal transform section 206 .

When the prediction mode PredMode of the encoding block to be processed is inter prediction (PRED_INTER) and the predicted motion vector mode, the inter prediction unit 203 calculates the code of the already decoded image signal stored in the encoding information storage memory 205. Using this information, multiple motion vector predictor candidates are derived and registered in a motion vector predictor candidate list (described later), and bit string decoding is performed from among the multiple motion vector predictor candidates registered in the motion vector predictor candidate list. The bit string decoding section 201 selects a predicted motion vector according to the decoded and supplied predicted motion vector index, calculates a motion vector from the decoded difference vector and the selected motion vector predictor, and performs other encoding. It is stored in the encoded information storage memory 205 together with the information. The encoding information of the encoded block supplied and stored here includes flags predFlagL0[xP][yP] and predFlagL1[xP] indicating whether to use prediction mode PredMode, division mode PartMode, L0 prediction, and L1 prediction. [yP], reference index of L0, L1 refIdxL0[xP][yP], refIdxL1[xP][yP], motion vector of L0, L1 mvL0[xP][yP], mvL1[xP][yP], etc. . Here, xP and yP are indices indicating the position of the upper left pixel of the encoded block within the picture. If 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 encoded block to be processed is inter prediction (PRED_INTER) and is in the merge mode, merge candidates are derived. Using the encoding information of the already decoded encoded blocks stored in the encoding information storage memory 205, a plurality of merging candidates are derived and registered in a merging candidate list to be described later. A flag indicating whether or not to select a merging candidate corresponding to a merging index decoded and supplied by the bit string decoding unit 201 from among a plurality of merging candidates, and to use L0 prediction and L1 prediction of the selected merging candidate. predFlagL0[xP][yP], predFlagL1[xP][yP], reference index of L0, L1 refIdxL0[xP][yP], refIdxL1[xP][yP], motion vector of L0, L1 mvL0[xP][yP ], mvL1[xP][yP] and the like 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 encoded block within the picture. The detailed configuration and operation of the inter prediction unit 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 (PRED_INTRA). The encoded information decoded by the bit string decoding unit 201 includes an intra prediction mode, and according to the intra prediction mode, a predicted image signal is generated by intra prediction from the decoded image signal stored in the decoded image memory 208. is generated, and the predicted image signal is supplied to the decoded image signal superimposition 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 orthogonally transformed/quantized residual signal decoded by the bit string decoding unit 201, and Obtain the residual signal.

The decoded image signal superimposition unit 207 performs inverse orthogonal transformation and inverse quantization and inverse orthogonal transformation on the predicted image signal that has been inter-predicted by the inter-prediction unit 203 or the predicted image signal that has been intra-predicted in the intra-prediction unit 204 . By superimposing the dequantized residual signal, the decoded image signal is decoded and stored in the decoded image memory 208. When storing the image in the decoded image memory 208, the decoded image may be stored in the decoded image memory 208 after being subjected to filtering processing to reduce block distortion caused by encoding.

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

FIG. 7 is a flowchart showing detailed operations of the division process in step S1003. First, it is determined whether or not the block to be processed is divided into four (step S1101).

If 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 Z-scan order, that is, in the order of 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. 6 is an example in which the block to be processed is divided into four. Numbers 0 to 3 in 601 in FIG. 6 indicate the order of processing. Then, the division process shown in FIG. 7 is recursively performed for each block divided in step S1101 (step S1104).

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

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

If it is not determined that the block to be processed is to be divided into 2-3, that is, if it is determined not to be divided, the division is ended (step S1211) and the process returns to the upper layer block.

If it is determined that the block to be processed is to be divided into 2-3, it is further determined whether or not to divide the block to be processed into 2 (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 in the vertical direction (step S1203), and based on the result, the block to be processed is divided in the vertical direction (step S1204). Alternatively, the block to be processed is divided horizontally (step S1205). As a result of step S1204, the block to be processed is divided into two parts in the vertical direction, as shown in 602 in FIG. 6, and as a result of step S1205, the block to be processed is divided into two parts in the horizontal direction, as shown in 604 in FIG. be done.

In step S1202, if it is not determined that the block to be processed is to be divided into two, that is, if it is determined to be divided into three, it is determined whether or not to divide the block to be processed in the vertical direction (step S1206). Based on this, the block to be processed is divided vertically (step S1207) or the block to be processed is divided horizontally (step S1208). As a result of step S1207, the block to be processed is divided into three parts in the vertical direction, as shown in 603 in FIG. 6, and as a result of step S1208, the block to be processed is divided into three parts in the horizontal direction, as shown in 605 in FIG. be done.

After executing any of steps S1204 to S1205, 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 3 from 602 to 605 in FIG. 6 indicate the order of processing. For each divided block, the 2-3 division process in FIG. 8 is recursively executed (step S1210).

In the recursive block division described here, the necessity of division may be limited by the number of times of division, the size of the block to be processed, or the like. The information that limits the necessity of division may be realized in a configuration in which no information is transmitted by making a prior agreement between the encoding device and the decoding device, or the encoding device can limit the necessity of division. The information may be determined and recorded in an encoded bit string to be transmitted to the decoding device.

Here, 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 block dividing section 202 in image decoding device 200 will be explained. The block dividing unit 202 divides a tree block using the same processing procedure as the block dividing unit 101 of the image encoding device 100. However, while the block division unit 101 of the image encoding device 100 determines the optimal block division shape by applying optimization methods such as estimation of the optimal shape through image recognition and distortion rate optimization, 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 encoded bit string.

FIG. 9 shows the syntax (syntax rules for coded bit strings) regarding block division in the first embodiment. coding_quadtree() represents the syntax for dividing a block into four, and multi_type_tree() represents the syntax for dividing the block into two or three. qt_split is a flag indicating whether or not to divide the block into four. If the block is to be divided into four, qt_split=1, and if not, qt_split=0. When dividing into four (qt_split=1), each block divided into four is recursively processed into four (coding_quadtree(0), coding_quadtree(1), coding_quadtree(2), coding_quadtree(3)). When not dividing into four (qt_split=0), the subsequent division is determined according to multi_type_tree(). mtt_split is a flag indicating whether to further divide. When further dividing (mtt_split=1), refer to mtt_split_vertical, which is a flag indicating whether to divide vertically or horizontally, and mtt_split_binary, which is a flag determining whether to divide into two or three. 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 dividing into two, and mtt_split_binary=0 indicates dividing into three. Perform hierarchical block splitting by calling multi_type_tree recursively until mtt_split=0.

<Intra prediction>
The intra prediction method according to the embodiment is implemented in the intra prediction unit 103 of the video encoding device of FIG. 1 and the inter prediction unit 203 of the video decoding device of FIG. 2.

An intra prediction method according to an embodiment will be explained using the drawings. In the intra prediction method, both encoding and decoding processes are performed in units of encoded blocks.

<Description of the intra prediction unit 103 on the encoding side>
FIG. 41 is a diagram showing a detailed configuration of the intra prediction unit 103 of the video encoding device of FIG. 1. The normal intra prediction unit 351 generates a predicted image signal by normal intra prediction from decoded pixels adjacent to the encoded block to be processed, selects a suitable intra prediction mode from among a plurality of intra prediction modes, and selects The predicted image signal corresponding to the selected intra prediction mode and the selected intra prediction mode is supplied to the prediction method determining unit 105. FIG. 10 shows an example of normal intra prediction. FIG. 10A shows the correspondence between the prediction direction of normal intra prediction and the intra prediction mode number. For example, intra-prediction mode 50 generates an intra-predicted image by copying pixels in the vertical direction. Intra prediction mode 1 is a DC mode, and is a mode in which all pixel values of the processing target block are the average value of reference pixels. Intra prediction mode 0 is a Planar mode, which is a mode in which a two-dimensional intra prediction image is created from reference pixels in the vertical and horizontal directions. FIG. 10(b) is an example of generating an intra-predicted 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. If the reference pixel in intra prediction mode is not at an integer position, the reference pixel value is determined by interpolation from reference pixel values at surrounding integer positions.

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

<Description of the intra prediction unit 204 on the decoding side>
FIG. 42 is a diagram showing a detailed configuration of the intra prediction unit 204 of the video decoding device shown in FIG. 2.

The normal intra prediction unit 361 generates a predicted image signal by normal intra prediction from decoded pixels adjacent to the encoded block to be processed, selects a suitable intra prediction mode from a plurality of intra prediction modes, and selects A predicted image signal according 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 section 207 via the switch 364. The processing of the normal intra prediction unit 361 in FIG. 42 corresponds to the normal intra prediction unit 351 in FIG. 41, so a detailed explanation will be omitted.

The intra block copy prediction unit 362 acquires a decoded area of the same image signal as the encoded block to be processed from the decoded image memory 208, and obtains a predicted image signal by performing intra block copy processing. This predicted image signal is supplied to the decoded image signal superimposing section 207 via the switch 364. The 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 video encoding device of FIG. 1 and the inter prediction unit 203 of the video decoding device of FIG. 2.

An inter prediction method according to an embodiment will be explained using the drawings. In the inter prediction method, both encoding and decoding processes are performed in units of encoded blocks.

<Description of the 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 video encoding device of FIG. 1. The normal predicted motion vector mode derivation unit 301 derives a plurality of normal predicted motion vector candidates, selects a predicted motion vector, and calculates a difference vector from the detected motion vector. The detected inter prediction mode, reference index, motion vector, and calculated difference vector become inter prediction information of the normal predicted motion vector mode. This inter prediction information is supplied to inter prediction mode determination section 305. The detailed configuration and processing of the normal predicted motion vector mode derivation unit 301 will be described later.

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

The sub-block predicted motion vector mode derivation unit 303 derives a plurality of sub-block predicted motion vector candidates, selects a sub-block predicted motion vector, and calculates a difference vector from the detected motion vector. The detected inter prediction mode, reference index, motion vector, and calculated difference vector become inter prediction information of the normal predicted motion vector mode. This inter prediction information is supplied to inter prediction mode determination section 305. The detailed configuration and processing of the sub-block predicted motion vector mode deriving unit 303 will be described later.

The subblock merging mode deriving unit 304 derives a plurality of subblock merging candidates, selects a subblock merging candidate, and obtains inter prediction information of the subblock merging mode. This inter prediction information is supplied to inter prediction mode determination section 305. The detailed configuration and processing of the sub-block merge mode deriving unit 304 will be described later.

The inter prediction mode determining unit 305 uses the inter prediction information supplied from the normal predicted motion vector mode deriving unit 301, the normal merge mode deriving unit 302, the sub-block predicted motion vector mode deriving unit 303, and the sub-block merging mode deriving unit 304. , determine the inter prediction mode. 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 .

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

<Description of the inter prediction unit 203 on the decoding side>
FIG. 22 is a diagram showing a detailed configuration of the inter prediction unit 203 of the video decoding device shown in FIG. 2.

The normal predicted motion vector mode derivation unit 401 derives a plurality of normal predicted motion vector candidates, selects a predicted motion vector, and calculates a difference vector from the detected motion vector. The detected inter prediction mode, reference index, motion vector, and difference vector become inter prediction information of the normal predicted motion vector mode. This inter prediction information is supplied to the motion compensation prediction unit 406 via the switch 408. The detailed configuration and processing of the normal predicted motion vector mode deriving unit 401 will be described later.

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

The sub-block predicted motion vector mode derivation unit 403 derives a plurality of sub-block predicted motion vector candidates, selects a sub-block predicted motion vector, and calculates a difference vector from the detected motion vector. The detected inter prediction mode, reference index, motion vector, and calculated difference vector become inter prediction information of the normal predicted motion vector mode. This inter prediction information is supplied to the motion compensation prediction unit 406 via the switch 408.

The subblock merging mode deriving unit 404 derives a plurality of subblock merging candidates, selects a subblock merging candidate, and obtains inter prediction information of the subblock merging mode. This inter prediction information is supplied to the motion compensation prediction unit 406 via the switch 408. The motion compensation prediction unit 406 performs inter prediction on the reference image signal stored in the decoded image memory 208 based on the determined inter prediction information. The detailed configuration and processing are the same as those on the encoding side.

<Normal predicted motion vector mode derivation unit (normal AMVP)>
The normal predicted motion vector mode derivation unit 301 in FIG. It includes a vector detection section 326, a predicted motion vector candidate selection section 327, and a motion vector subtraction section 328.

The normal predicted motion vector mode deriving unit 401 in FIG. 23 includes a spatial predicted motion vector candidate deriving unit 421, a temporal predicted motion vector candidate deriving unit 422, a historical predicted motion vector candidate deriving unit 423, a predicted motion vector candidate supplementing unit 425, and a predicted motion vector candidate deriving unit 422. It includes a vector candidate selection section 426 and a motion vector addition section 427.

The 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 explained using 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 process by the normal motion vector mode derivation unit 401 on the decoding side. It is a flowchart showing a procedure.

<Normal predicted motion vector mode derivation unit (normal AMVP): Description of encoding side>
The normal predicted motion vector 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 "motion vector" in the specification and the term "normal motion vector" in FIG. 19 are assumed to correspond.

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 predicted motion vector candidate derivation unit 321, a temporal predicted motion vector candidate derivation unit 322, a historical predicted motion vector candidate derivation unit 323, a predicted motion vector candidate supplementation unit 325, a predicted motion vector candidate selection unit 327, and a motion vector subtraction unit At 328, a differential motion vector of the motion vectors used in inter prediction in the normal predicted motion vector mode is calculated for each of L0 and L1 (steps S101 to S106 in FIG. 19). Specifically, if 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), calculate the L0 predicted motion vector candidate list mvpListL0 and select the predicted motion vector mvpL0. Then, a differential motion vector mvdL0 of the motion vector mvL0 of L0 is calculated. If the inter prediction mode of the block to be processed is L1 prediction (Pred_L1), calculate the L1 motion vector predictor candidate list mvpListL1, select the motion vector predictor mvpL1, and calculate the differential motion vector mvdL1 of the L1 motion vector mvL1. . 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 predicted motion vector candidate list mvpListL0 is calculated, L0 predicted motion vector mvpL0 is selected, and L0 prediction is performed. Calculate the differential motion vector mvdL0 of the motion vector mvL0 of L1, calculate the predicted motion vector candidate list mvpListL1 of L1, calculate the predicted motion vector mvpL1 of L1, and calculate the differential motion vector mvdL1 of the motion vector mvL1 of L1, respectively. do.

Although differential motion vector calculation processing is performed for each of L0 and L1, the processing is common to both L0 and L1. Therefore, in the following description, L0 and L1 will be expressed as a common LX. In the process of calculating the differential motion vector of L0, X is 0, and in the process of calculating the differential motion vector of L1, X is 1. Furthermore, when referring to information in another list instead of LX during the process of calculating the differential motion vector of LX, the other list is expressed as LY.

When using the LX motion vector mvLX (step S102 in FIG. 19: YES), candidates for the LX motion vector predictor are calculated and an LX motion vector predictor candidate list mvpListLX is constructed (step S103 in FIG. 19). The spatial predicted motion vector candidate derivation unit 321, the temporal predicted motion vector candidate derivation unit 322, the historical predicted motion vector candidate derivation unit 323, and the predicted motion vector candidate supplementation unit 325 in the normal predicted motion vector mode derivation unit 301 generate a plurality of predicted motions. Derive vector candidates and construct a predicted motion vector candidate list mvpListLX. The detailed processing procedure of step S103 in FIG. 19 will be described later using the flowchart in FIG. 20.

Subsequently, the motion vector predictor candidate selection unit 327 selects the motion vector predictor mvpLX of LX from the motion vector predictor candidate list mvpListLX of LX (step S104 in FIG. 19). Each differential motion vector is calculated as the difference between the motion vector mvLX and each motion vector predictor candidate mvpListLX[i] stored in the motion vector predictor candidate list mvpListLX[i]. The amount of code when these differential motion vectors are encoded is calculated for each element 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] with the minimum code amount for each motion vector predictor candidate is selected as the motion vector predictor mvpLX, and Get index i. If there are multiple motion vector predictor candidates with the smallest generated code amount in the motion vector predictor candidate list mvpListLX, the motion vector predictor whose index i in the motion vector predictor candidate list mvpListLX is represented by a smaller number is used. Select candidate mvpListLX[i] as the optimal predicted motion vector mvpLX, and obtain its index i.

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

<Normal predicted motion vector mode derivation unit (normal AMVP): Description of decoding side>
Next, the normal predicted motion vector mode processing procedure on the decoding side will be described with reference to FIG. On the decoding side, a spatial predicted motion vector candidate derivation unit 421, a temporal predicted motion vector candidate derivation unit 422, a historical predicted motion vector candidate derivation unit 423, and a predicted motion vector candidate supplementation unit 425 use the predicted motion vector candidate for inter prediction in the normal predicted motion vector mode. Motion vectors are calculated for each of L0 and L1 (steps S201 to S206 in FIG. 25). Specifically, when the prediction mode PredMode of the target block is inter prediction (MODE_INTER) and the inter prediction mode of the target block is L0 prediction (Pred_L0), the predicted motion vector candidate list mvpListL0 of L0 is calculated and the predicted motion Select vector mvpL0 and calculate motion vector mvL0 of L0. When the inter prediction mode of the block to be processed is L1 prediction (Pred_L1), an L1 motion vector predictor candidate list mvpListL1 is calculated, the predicted motion vector 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 predicted motion vector candidate list mvpListL0 is calculated, L0 predicted motion vector mvpL0 is selected, and L0 prediction is performed. The motion vector mvL0 of L1 is calculated, the predicted motion vector candidate list mvpListL1 of L1 is calculated, the predicted motion vector mvpL1 of L1 is calculated, and the motion vector mvL1 of L1 is calculated, respectively.

Similar to the encoding side, motion vector calculation processing is performed for each of L0 and L1 on the decoding side, but the processing is common for both L0 and L1. Therefore, in the following description, L0 and L1 will be expressed as a common LX. LX represents an inter prediction mode used for inter prediction of the encoded block to be processed. In the process of calculating the motion vector of L0, X is 0, and in the process of calculating the motion vector of L1, X is 1. Further, during the process of calculating the motion vector of LX, when referring to information in another reference list instead of the same reference list as the LX to be calculated, the other reference list is expressed as LY.

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

Next, the motion vector predictor candidate selection unit 426 selects the 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. The predicted motion vector mvpLX is extracted (step S204 in FIG. 25).

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

<Normal predicted motion vector mode derivation unit (normal AMVP): Motion vector prediction method>
FIG. 20 shows a normal predicted motion vector having a function common to the normal predicted motion vector mode derivation unit 301 of the video encoding device and the normal predicted motion vector mode derivation unit 401 of the video decoding device according to the embodiment of the present invention. 3 is a flowchart illustrating the processing procedure of mode derivation processing.

The normal predicted motion vector mode deriving unit 301 and the normal predicted motion vector mode deriving unit 401 are provided with a predicted motion vector candidate list mvpListLX. The motion vector predictor candidate list mvpListLX has a list structure, and is provided with a motion vector predictor index indicating the location within the motion vector predictor candidate list and a storage area for storing the motion vector predictor candidate corresponding to the index as an element. The motion vector predictor index number 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, it is assumed that the motion vector predictor candidate list mvpListLX can register at least two motion vector predictor candidates (inter prediction information). Further, a variable numCurrMvpCand indicating the number of motion vector predictor candidates registered in the motion vector predictor candidate list mvpListLX is set to 0.

The spatial predictive motion vector candidate deriving units 321 and 421 derive predictive motion vector candidates from blocks adjacent to the left. In this process, a flag availableFlagLXA indicating whether a motion vector predictor candidate for the block adjacent to the left (A0 or A1) is available, a motion vector mvLXA, and a reference index refIdxA are derived, and mvLXA is a motion vector predictor candidate list mvpListLX (Step S301 in FIG. 20). Note that when L0, X is 0, and when L1, X is 1 (the same applies hereinafter). Subsequently, the spatial predicted motion vector candidate deriving units 321 and 421 derive a predicted motion vector candidate from the upper adjacent block (B0, B1, or B2). In this process, a flag availableFlagLXB indicating whether the motion vector predictor candidate of the upper adjacent block is available, a motion vector mvLXB, and a reference index refIdxB are derived, and if mvLXA and mvLXB are not equal, mvLXB is used as the motion vector predictor It is added to the candidate list mvpListLX (step S302 in FIG. 20). The processes in steps S301 and S302 in FIG. 20 are common except that the positions and numbers of adjacent blocks to be referenced are different, and include a flag availableFlagLXN indicating whether a motion vector predictor candidate for the encoded block is available, and a motion vector mvLXN. , a reference index refIdxN (N is A or B, hereinafter the same) is derived.

Subsequently, the temporal motion vector predictor candidate deriving units 322 and 422 derive motion vector predictor candidates from encoded blocks in a picture whose time is different from the current picture to be processed. In this process, a flag availableFlagLXCol indicating whether a motion vector predictor candidate for a coded block in a picture at a different time is available, a motion vector mvLXCol, a reference index refIdxCol, and a reference list listCol are derived, and mvLXCol is used as a motion vector predictor candidate. It is added to the list mvpListLX (step S303 in FIG. 20). A detailed explanation of the derivation processing procedure in step S303 will be omitted.

Note that the processing of the temporal motion vector predictor candidate derivation units 322 and 422 can be omitted in sequence (SPS), picture (PPS), or slice units.

Subsequently, the historical predicted motion vector candidate derivation units 323 and 423 add the historical predicted motion vector candidates registered in the historical predicted motion vector candidate list HmvpCandList to the predicted motion vector 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 replenishment units 325 and 425 add motion vectors 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 part (normal merge)>
The normal merge mode deriving unit 302 in FIG. 18 includes a spatial merge candidate deriving unit 341, a temporal merge candidate deriving unit 342, an average merge candidate deriving unit 344, a history merge candidate deriving unit 345, a merge candidate supplementing unit 346, and a merge candidate selecting unit 347. including.

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

FIG. 21 shows the procedure of a normal merge mode deriving process that has a common function in the normal merge mode deriving unit 302 of the video encoding device and the normal merge mode deriving unit 402 of the video decoding device according to the embodiment of the present invention. It is a flowchart explaining.

The various processes will be explained step by step below. Note that in the following description, unless otherwise specified, the case where the slice type slice_type is a B slice will be described, but it can also be applied to a case where the slice type is a P slice. However, if the slice type slice_type is 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 the processing related to L1 can be omitted.

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

The spatial merging candidate deriving unit 341 and the spatial merging candidate deriving unit 441 perform processing from the encoded information stored in the encoded information storage memory 111 of the video encoding device or the encoded information storage memory 205 of the video decoder. Spatial merging candidates A and B are derived from blocks adjacent to the left side and above the target block, and the derived spatial merging candidates are registered in the merging candidate list mergeCandList (step S401 in FIG. 21). Here, N indicating either the spatial merging candidates A, B or the temporal merging candidate Col is defined. A flag availableFlagN that indicates whether the inter prediction information of block N can be used as spatial merging candidate N, L0 reference index refIdxL0N and L1 reference index refIdxL1N of spatial merging candidate N, L0 that indicates whether L0 prediction is performed or not. A prediction flag predFlagL0N, an L1 prediction flag predFlagL1N indicating whether or not L1 prediction is performed, an L0 motion vector mvL0N, and an L1 motion vector mvL1N are derived. However, in this embodiment, merging candidates are derived without referring to other coded blocks included in the block including the coded block to be processed. It does not derive spatial merge candidates.

Next, the temporal merging candidate deriving unit 342 and the temporal merging candidate deriving unit 442 derive temporal merging candidates from pictures at different times, and register the derived temporal merging candidates in the merge candidate list mergeCandList (see FIG. 21). Step S402). A flag availableFlagCol indicating whether a temporal merging candidate is available, an L0 prediction flag predFlagL0Col indicating whether L0 prediction of the temporal merging candidate will be performed, an L1 prediction flag predFlagL1Col indicating whether L1 prediction will be performed, and L0 The motion vector mvL0Col of L1 and the motion vector mvL1Col of L1 are derived. A detailed description of the processing procedure in step S402 will be omitted.

Note that the processing of the temporal merging candidate deriving section 342 and the temporal merging candidate deriving section 442 can be omitted in units of sequence (SPS), picture (PPS), or slice.

Subsequently, the history merge candidate deriving unit 345 and the history merge candidate deriving unit 445 add the history predicted motion vector candidates registered in the history predicted motion vector candidate list HmvpCandList to the merge candidate list mergeCandList (step S403 in FIG. 21). . The detailed processing procedure of step S403 will be described later using the flowchart of FIG.

Subsequently, the average merge candidate deriving unit 344 and the average merge candidate deriving unit 444 derive average merge candidates from the merge candidate list mergeCandList, and register the derived average merge candidates in the merge candidate list mergeCandList (steps in FIG. 21). S404). The detailed processing procedure of step S404 will be described later using the flowchart of FIG. 29.

Next, in the merge candidate replenishment unit 346 and the merge candidate replenishment unit 446, 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 merge candidate replenishment unit 346 and the merge candidate replenishment unit 446 The number of merge candidates numCurrMergeCand is set to the maximum number of merge candidates MaxNumMergeCand as an upper limit, and additional merge candidates are derived and registered in the merge candidate list mergeCandList (step S405 in FIG. 21). With the maximum number of merging candidates MaxNumMergeCand as an upper limit, in P slices, merging candidates whose prediction mode is L0 prediction (Pred_L0) and whose motion vector has a value of (0,0) with different reference indexes are added. In the B slice, a merging candidate whose prediction mode is bi-prediction (Pred_BI) and whose motion vector has a value of (0, 0) with a different reference index is added.

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

<Update of historical predicted motion vector candidate list>
Next, a method for initializing and updating the history predicted motion vector 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 illustrating the history predicted motion vector candidate list initialization/update processing procedure.

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

The history predicted motion vector candidate list HmvpCandList is initialized at the beginning of the slice, and on the encoding side, the history predicted motion vector candidate list HmvpCandList is updated when the prediction method determining unit 105 selects the normal prediction vector mode or the normal merge mode. However, on the decoding side, when the inter prediction mode decoded by the bit string decoding unit 201 is the normal prediction vector mode or the normal merge mode, the history prediction motion vector candidate list HmvpCandList is updated.

Inter prediction information used when performing inter prediction in normal prediction vector mode or normal merge mode is registered as inter prediction information candidate hMvpCand in history prediction motion vector candidate list HmvpCandList. The inter prediction information candidate hMvpCand includes an L0 reference index refIdxL0, an L1 reference index refIdxL1, an L0 prediction flag predFlagL0 indicating whether L0 prediction is performed, and an 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. Among the elements (i.e., inter prediction information) registered in the historical predicted motion vector candidate list HmvpCandList provided in the encoded information storage memory 111 on the encoding side and the encoded information storage memory 205 on the decoding side, there are inter prediction information candidates. If inter prediction information with the same value as hMvpCand exists, that element is deleted from the history predicted motion vector 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 first element of the historical predicted motion vector candidate list HmvpCandList is deleted, and the inter prediction information candidate is added to the end of the historical predicted motion vector candidate list HmvpCandList. Add hMvpCand.

The number of elements of the historical predicted motion vector candidate list HmvpCandList provided in the encoded information storage memory 111 on the encoding side and the encoded information storage memory 205 on the decoder side of the present invention is assumed to be six.

First, a history predicted motion vector candidate list HmvpCandList is initialized in units of slices (step S2101 in FIG. 26). At the beginning of the slice, all elements of the historical predicted motion vector candidate list HmvpCandList are emptied, and the value of NumHmvpCand, the number of historical predicted motion vector candidates registered in the historical predicted motion vector candidate list HmvpCandList, is set to 0.

Note that although the history predicted motion vector candidate list HmvpCandList is initialized in units of slices (first encoded blocks of slices), it may be initialized in units of pictures, tiles, or tree block rows.

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

First, initial settings are performed for each encoded block. A value of FALSE is set for the flag identificationCandExist indicating whether or not the same candidate exists, and 0 is set for the deletion target index removeIdx (step S2103 in FIG. 26).

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

Next, it is determined whether the same element as the inter prediction information candidate hMvpCand to be registered exists in each element of the history predicted motion vector candidate list HmvpCandList (step S2105 in FIG. 26). FIG. 27 is a flowchart of this same element confirmation processing procedure. If the value of the number of history predicted motion vector candidates NumHmvpCand is 0 (step S2121 in FIG. 27: NO), the history prediction motion vector candidate list HmvpCandList is empty and there is no identical candidate, so steps S2122 to S2125 in FIG. 27 are skipped. , this identical element confirmation processing procedure ends. If the value of the number of historical predicted motion vector candidates NumHmvpCand is greater than 0 (step S2121 in FIG. 27: YES), the process in step S2123 is repeated until the historical predicted motion vector index hMvpIdx is from 0 to NumHmvpCand-1 (step S2121 in FIG. 27). S2122 to S2125). First, it is compared whether the hMvpIdx-th element HmvpCandList[hMvpIdx] counting from 0 in the history predicted motion vector 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), set a TRUE value to the flag identificationCandExist indicating whether the same candidate exists, set the value of hMVpIndex to the deletion target index removeIdx, and delete the same candidate. End element confirmation processing. If they are not the same (step S2123 in FIG. 27: NO), hMvpIdx is incremented by 1, and if the historical predicted motion vector index hMvpIdx is less than or equal to NumHmvpCand-1, the processes from step S2123 onward are performed (steps S2122 to S2125 in FIG. 27). .

Returning to the flowchart of FIG. 26 again, the elements of the historical predicted motion vector candidate list HmvpCandList are shifted and added (step S2106 of FIG. 26). FIG. 28 is a flowchart of the element shift/addition processing procedure for the history predicted motion vector candidate list HmvpCandList in step S2106 of FIG. 26. First, it is determined whether to add a new element after removing the elements stored in the history predicted motion vector candidate list HmvpCandList, or to add a new element without removing the elements. Specifically, it is compared whether the flag identificationCandExist indicating whether the same candidate exists is TRUE or NumHmvpCand is 6 (step S2141 in FIG. 28). If the flag identificationCandExist indicating whether the same candidate exists or not satisfies either the condition of TRUE or NumHmvpCand of 6 (step S2141 in FIG. 28: YES), the flag is stored in the history predicted motion vector candidate list HmvpCandList. Remove existing elements and add new elements. Set the initial value of index i to the value removeIdx + 1. The element shift process of step S2143 is repeated from this initial value to NumHmvpCand. (Steps S2142 to S2144 in FIG. 28). The elements of HMVPCandList[i] are copied to HMVPCandList[i - 1] to shift the elements forward (step S2143 in FIG. 28), and i is incremented by 1 (steps S2142 to S2144 in FIG. 28). When the index i becomes NumHmvpCand+1 and the element shift process in step S2143 is completed, the inter prediction information candidate hMvpCand is added to the end of the history predicted motion vector candidate list (step S2145 in FIG. 28). Here, the last of the history predicted motion vector candidate list is the (NumHmvpCand-1)th HMVPCandList[NumHmvpCand-1] counting from 0. This completes the element shift/addition process for the history predicted motion vector candidate list HMVPCandList. On the other hand, if the flag identificationCandExist indicating whether or not the same candidate exists does not satisfy either of the conditions of TRUE and NumHmvpCand of 6 (step S2141 in FIG. 28: NO), the flag is stored in the history predicted motion vector candidate list HmvpCandList. The inter prediction information candidate hMvpCand is added to the end of the history predicted motion vector candidate list without removing the elements that are currently displayed (step S2146 in FIG. 28). Here, the last of the history predicted motion vector candidate list is the NumHmvpCand-th HMVPCandList[NumHmvpCand] counting from 0. Furthermore, NumHmvpCand is incremented by 1, and the element shift/addition process of the history predicted motion vector candidate list HMVPCandList is completed.

FIG. 31 is a diagram illustrating an example of the process of updating the historical predicted motion vector list. When adding new inter prediction information when six elements (inter prediction information) are registered in the history prediction motion vector candidate list HMVPCandList, each element of the history prediction motion vector candidate list HMVPCandList and the new inter prediction information from the front are registered. Comparing the prediction information (FIG. 31(a)), if the new inter prediction information has the same value as the third element HMVP2 from the beginning of the history prediction motion vector candidate list HMVPCandList, the new inter prediction information is selected from the history prediction motion vector candidate list HMVPCandList. Delete element HMVP2, shift (copy) backward elements HMVP3 to HMVP5 forward one by one, and add new inter prediction information to the end of the history predicted motion vector candidate list HMVPCandList (Figure 31(b)) , the update of the history predicted motion vector candidate list HMVPCandList is completed (FIG. 31(c)).

<History predicted motion vector candidate derivation process>
Next, the history predicted motion vector candidate derivation unit 323 of the normal predicted motion vector mode derivation unit 301 on the encoding side and the history predicted motion vector candidate derivation unit 423 of the normal predicted motion vector mode derivation unit 401 on the decoding side perform a common process. A method for deriving historical predicted motion vector candidates from the historical predicted motion vector candidate list HMVPCandList, which is the processing procedure of step S304 in FIG. 20, will be described in detail. FIG. 29 is a flowchart illustrating the procedure for deriving historical predicted motion vector candidates.

If the current number of motion vector predictor candidates numCurrMvpCand is greater than or equal to the maximum number of elements (here, 2) of the motion vector predictor candidate list mvpListLX, or if the value of the number of historical motion vector predictor candidates NumHmvpCand is 0 (step S2201 in FIG. 29: NO), the processes from steps S2202 to S2209 in FIG. 29 are omitted, and the history predicted motion vector candidate derivation process procedure is ended. If the current number of motion vector predictor candidates numCurrMvpCand is smaller 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), steps S2202 to S2209 in FIG. 29 are performed.

Subsequently, the processes of steps S2203 to S2208 in FIG. 41 are repeated until the index i is from 1 to 4 or the number of historical predicted motion vector candidates NumHmvpCand, whichever is smaller (steps S2202 to S2209 in FIG. 29). If the current number of motion vector predictor candidates numCurrMvpCand is 2 or more, which is the maximum number of elements in the motion vector predictor candidate list mvpListLX (step S2203 in FIG. 29: NO), the processes from steps S2204 to S2209 in FIG. 29 are omitted, and the main The history predicted motion vector candidate derivation processing procedure ends. If the current number of motion vector predictor candidates numCurrMvpCand is smaller than 2, which is the maximum number of elements of the motion vector predictor candidate list mvpListLX (step S2203 in FIG. 29: YES), the processes from step S2204 in FIG. 29 are performed.

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

Next, if the reference index of LY in the historical motion vector predictor candidate list HmvpCandList[NumHmvpCand - i] is the same as the reference index refIdxLX of the motion vector to be encoded/decoded (step S2206 in FIG. 29: YES), the motion vector predictor candidates are As the last element of the list, the numCurrMvpCand element mvpListLX[numCurrMvpCand] counting from 0 in the motion vector predictor candidate list, and the (NumHmvpCand-i) th element counting from 0 in the historical motion vector predictor candidate list HmvpCandList[[NumHmvpCand - i] is added (step S2207 in FIG. 29), and the current number of motion vector predictor candidates numCurrMvpCand is incremented by one. If the reference index of LY in the historical predicted motion vector candidate list HmvpCandList[NumHmvpCand - i] is not the same as the reference index refIdxLX of the motion vector to be encoded/decoded (step S2206 in FIG. 29: NO), the additional process in step S2207 is performed. skip.

The above processing from steps S2205 to S2207 in FIG. 29 is performed in both L0 and L1 (steps S2204 to S2208 in FIG. 29).

The index i is incremented by 1, and if the index i is less than the smaller value of 4 or the number of history predicted motion vector candidates NumHmvpCand, the process from step S2203 onward is performed again (steps S2202 to S2209 in FIG. 29).

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

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

Subsequently, the initial value of the index hMvpIdx is set to 1, and the additional processing from step S2303 to step 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 (maximum number of merge candidates MaxNumMergeCand-1), merge candidates have been added to all elements in the merge candidate list, and this history merge candidate is derived. The process ends (step S2303 in FIG. 30: NO). If the number numCurrMergeCand of elements registered in the current merge candidate list is less than or equal to (maximum number of merge candidates MaxNumMergeCand-1) (step S2303 in FIG. 30: YES), the processes from step S2304 onward are performed.

First, a value of FALSE is set for sameMotion (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 1 (S2305 to S2308 in FIG. 30).

Next, check whether the (NumHmvpCand-hMvpIdx)th element HmvpCandList[NumHmvpCand-hMvpIdx] counting from 0 in the history motion vector prediction candidate list and mergeCandList[i] the i-th element counting from 0 in the merging candidate list have the same value. A comparison is made to determine whether or not (step S2306 in FIG. 30). Here, the merging candidates having the same value means that the values of all components (inter prediction mode, reference index, motion vector) of the merging candidates are the same. However, the process of step S2306 is limited to the case where hMvpIdx is larger than NumHmvpCand-2, mergeCandList[i] is a spatial merging candidate, and isPruned[i] is FALSE. If the values are the same (step S2306 in FIG. 30: YES), both sameMotion and isPruned[i] are set to TRUE (step S2307 in FIG. 30). If the values are not the same (step S2306 in FIG. 30: NO), the process in step S2307 is skipped. When the iterative processing from step S2305 to step S2308 in FIG. 30 is completed, it is compared whether or not sameMotion is FALSE (step S2309 in FIG. 30), and if sameMotion is FALSE (step S2309 in FIG. 30: YES), add the (NumHmvpCand - hMvpIdx)th element HmvpCandList[NumHmvpCand - hMvpIdx] of the history predicted motion vector candidate list to the numCurrMergeCand-th mergeCandList[numCurrMergeCand] of the merge candidate list, and increment numCurrMergeCand 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 confirmation of all the elements in the history predicted motion vector candidate list is completed, or when merging candidates are added to all the elements in the merging candidate list, this history merging candidate derivation process is completed.

<Average merge candidate derivation process>
Next, the processing of step S404 in FIG. 21, which is a common process in the average merging candidate deriving unit 344 of the normal merging mode deriving unit 302 on the encoding side and the average merging candidate deriving unit 444 of the normal merging mode deriving unit 402 on the decoding side The method of deriving the average merging candidates, which is a procedure, will be described in detail. FIG. 38 is a flowchart illustrating 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.

Next, the merging candidate list is sequentially scanned from the beginning 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 to S1303 in FIG. 38). If the number of elements registered in the current merge candidate list numCurrMergeCand is not less than (maximum number of merge candidates MaxNumMergeCand-1), merge candidates have been added to all elements in the merge candidate list, and this history merge candidate is derived. The process ends (step S1304 in FIG. 38). If the number numCurrMergeCand of elements registered in the current merge candidate list is less than or equal to (maximum number of merge candidates MaxNumMergeCand-1), processing from step S1305 onwards is performed.

It is determined whether the i-th motion information mergeCandList[i] of the merge candidate list and the j-th motion information mergeCandList[j] of the merge candidate list are both invalid (step S1305 in FIG. 38), and both are invalid. In this case, the average merge candidates for mergeCandList[i] and mergeCandList[j] are not derived and the process moves to the next element. If both mergeCandList[i] and mergeCandList[j] are not invalid, the following process 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 of mergeCandList[i] is valid, it is determined whether the LX prediction of mergeCandList[j] is valid (step S1308 in FIG. 38). If the LX prediction of mergeCandList[j] is valid, that is, if the LX prediction of mergeCandList[i] and the LX prediction of mergeCandList[j] are both valid, then the motion vector of the LX prediction of mergeCandList[i] and the mergeCandList Derive the average merging candidate of LX prediction that has the motion vector of LX prediction that is the average of the motion vector of LX prediction of [j] and the reference index of LX prediction of mergeCandList[i], set it to the LX prediction of averageCand, and set it to the LX prediction of averageCand. LX prediction is enabled (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] An average merging candidate for LX prediction having the motion vector and reference index for LX prediction is derived and set as the LX prediction for averageCand, and the LX prediction for averageCand is made valid (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 the LX prediction of mergeCandList[j] is valid (step S1311 of FIG. 38). If the LX prediction of mergeCandList[j] is valid, that is, if 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] An average merging candidate for LX prediction having a reference index is derived and set as the averageCand LX prediction, and the averageCand LX prediction is made valid (step S1312 in FIG. 38). In step S1311 of FIG. 38, if the LX prediction of mergeCandList[j] is not valid, that is, if the LX prediction of mergeCandList[i] and the LX prediction of mergeCandList[j] are both invalid, the LX prediction of 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 process of deriving average merging candidates.

Note that the average merging 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 during encoding. Further, 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 obtained inter prediction information, and the reference picture specified by the reference index in the decoded image memory is moved from the same position as the image signal of the prediction block by the amount of the motion vector. Generate a predicted signal after acquiring the signal.

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 used as the motion compensated 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 compensation prediction signal, and the motion compensation prediction signal is used to determine the prediction method. supply to the department. Although the weighted average ratio of bi-prediction is set to 1:1 here, the 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, the greater the weighting ratio. Further, the weighting ratio may be calculated using a correspondence table between 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 receives the inter prediction information from the normal predicted motion vector mode deriving unit 401 , the normal merge mode deriving unit 402 , the sub-block predicted motion vector mode deriving unit 403 , and the sub-block merge mode deriving unit 404 through the switch 408 . Get it through.

The motion compensation prediction unit 406 supplies the obtained motion compensation prediction signal to the decoded image signal superimposition unit 207.

<About inter prediction mode>
The process of making predictions from a single reference picture is defined as uni-prediction, and in the case of uni-prediction, one of the two reference pictures registered in reference lists L0 and L1, called L0 prediction or L1 prediction, is used. Make predictions. The L0 prediction and the L1 prediction may be forward prediction (prediction that refers to a forward reference image) or backward prediction (prediction that refers to a backward reference image). 33 to 34 are diagrams for explaining motion compensated prediction in L0 prediction (uniprediction).

FIG. 33 shows a case where the inter prediction mode is L0 prediction and the L0 reference picture (RefL0Pic) is at a time earlier than the processing target picture (CurPic). FIG. 33 shows L0 prediction in which the L0 reference picture is at a later time than the processing target picture. Similarly, uni-prediction can be performed by replacing the reference picture for L0 prediction in FIGS. 33 and 34 with the reference picture for L1 prediction (RefL1Pic).

A process of making predictions from two reference pictures is defined as bi-prediction, and in the case of bi-prediction, it is expressed as bi-prediction using both L0 prediction and L1 prediction. FIGS. 35 to 37 are diagrams for explaining motion compensated prediction in bi-prediction. FIG. 35 shows a case of bi-prediction in which the reference picture for L0 prediction is at a time before the picture to be processed, and the reference picture for L1 prediction is at a time after the picture to be processed. FIG. 36 shows a case where bi-prediction is used, and the reference picture for L0 prediction and the reference picture for L1 prediction are at a time earlier than the processing target picture. FIG. 37 shows a case where bi-prediction is used, and the reference picture for L0 prediction and the reference picture for L1 prediction are at a later time than the processing target picture.

In this way, the relationship between L0/L1 prediction types and time is limited to that L0 is forward prediction (prediction that refers to the forward reference image) and L1 is backward prediction (prediction that refers to the backward reference image). It can be used without being Furthermore, in the case of bi-prediction, the same reference picture may be used for each of L0 prediction and L1 prediction. Note that the determination of whether to perform motion compensation prediction using 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. Ru.

<About reference index>
In an embodiment of the present invention, in order to improve the accuracy of motion compensated prediction, it is possible to select an optimal reference picture from among a plurality of reference pictures in motion compensated prediction. Therefore, the reference picture used in motion compensation prediction is used as a reference index, and the reference index is encoded in the encoded stream together with the encoded vector.

<Motion compensation processing based on normal predicted motion vector mode>
As shown in the inter prediction unit 102 on the encoding side in FIG. acquires 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 determining section 105.

Similarly, as shown in the inter prediction unit 203 on the decoding side in FIG. 22, the motion compensation prediction unit 406 normally The predicted motion vector mode derivation unit 401 obtains inter prediction information, 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 decoded image signal superimposing section 207.

<Motion compensation processing based on normal merge mode>
As shown in the inter prediction unit 102 on the encoding side in FIG. 16, the motion compensation prediction unit 306, when the inter prediction information by the normal merge mode derivation unit 302 is selected in the inter prediction mode determination unit 305, This inter prediction information is acquired from the inter prediction mode determination unit 305, 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 prediction method determining section 105.

Similarly, as shown in the inter prediction unit 203 on the decoding side in FIG. The derivation unit 402 acquires inter prediction information, 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 decoded image signal superimposing section 207.

<Merge difference motion vector (MMVD)>
The differential motion vector can be added to the motion vectors of the top two merging candidates (merging candidates with merging indexes of 0 and 1 in the merging candidate list). This differential motion vector is called a merged differential motion vector.

When the merge candidate selection unit 347 on the encoding side adds the merge difference motion vector, the motion vector to which the merge difference motion vector has been added is supplied to the motion compensation prediction unit 306 via the inter prediction mode determination unit 305. Further, the bit string encoding unit 108 encodes information regarding the merged difference motion vector. The information regarding the merge difference motion vector is an index mmvd_distance_idx indicating the distance to be added to the motion vector, and an index mmvd_direction_idx indicating the direction to add the motion vector. These indexes are defined as shown in the tables shown in FIGS. 39(a) and 39(b). Then, if the x and y components of the merged difference motion vector offset MmvdOffset are expressed as MmvdOffset[0] and MmvdOffset[1], respectively,
MmvdOffset[0] = ( MmvdDistance << 2 ) * MmvdSign[0]
MmvdOffset[1] = ( MmvdDistance << 2 ) * MmvdSign[1]
becomes. The merge difference motion vector is derived from the merge difference motion vector offset MmvdOffset in the above equation. Details of deriving the merged difference motion vector will be explained in the case of the decoding side below.

On the decoding side, if a merged differential motion vector exists, information regarding the merged differential motion vector is separated from the bitstream supplied to the bit string decoding unit 201, and a merged differential motion vector offset MmvdOffset is derived. Furthermore, the merge candidate selection unit 447 derives a merge difference motion vector from the decoded merge difference motion vector offset. This merge difference motion vector is added to the motion vector, and then the motion vector is supplied to the motion compensation prediction unit 406.

Derivation of the merge difference motion vector mMvdLX in the merge candidate selection unit 447 will be explained with reference to the flowchart of FIG. 40. First, it is determined whether the inter prediction mode of the encoded block is bi-prediction (PRED_BI) (S4402). If it is not bi-prediction (S4402: No), it is determined whether it is L0 prediction (PRED_L0) (S4404). In the case of L0 prediction (S4404: Yes),
mmvdL0 = MmvdOffset
mmvdL1 = 0
(S4406), and the process of deriving the merged difference motion vector ends. In the case of L1 prediction (S4404: No),
mmvdL0 = 0
mmvdL1 = MmvdOffset
(S4408), and the process of deriving the merged difference motion vector ends.

On the other hand, in the case of bi-prediction (S4402: Yes), the difference between the POC of the processing target picture currPic and the reference picture is calculated for each reference list and set as currPocDiffL0 and currPocDiffL1, respectively (S4410). Here, the difference in POC between picA and picB, DiffPicOrderCnt(picA, picB), is
DiffPicOrderCnt( picA, picB ) = [POC of picA] - [POC of picB]
shows. Further, the reference picture RefPicList0[refIdxL0] is a picture indicated by the reference index refIdxL0 of the reference list L0. Similarly, reference picture RefPicList1[refIdxL1] is a picture indicated by reference index refIdxL1 of reference list L1.

Next, it is determined whether -currPocDiffL0 * currPocDiffL1 >= 0 (step S4412). If this determination is true (step S4412: Yes),
mmvdL0 = MmvdOffset
mmvdL1 = -MmvdOffset
(step S4414), and the process of deriving the merged difference motion vector ends. On the other hand, if this determination is false (step S4412: No),
mmvdL0 = MmvdOffset
mmvdL1 = MmvdOffset
(Step S4416). Next, it is determined whether the absolute value of the difference in POC with reference list L0 is greater than or equal to the absolute value of the difference in POC with reference list L1 (step S4418). If this determination is true (step S4418: Yes), set X=0, Y=1 (step S4420), and scale the merged difference motion vector mmvdL1 of L1 (step S4424). Here, mMvdLY indicates that when Y=0, it is mMvdL0, and when Y=1, it is mMvdL1. On the other hand, if this determination is false (step S4418: No), set X=1, Y=0 (step S4422), and scale the merged difference motion vector mmvdL0 of L0 (step S4424). The scaling of the merged difference motion vector mmvdLY is
td = Clip3( -128, 127, currPocDiffLX )
tb = Clip3( -128, 127, currPocDiffLY )
tx = ( 16384 + Abs( td ) >> 1 ) / td
distScaleFactor = Clip3( -4096, 4095, ( tb * tx + 32 ) >> 6 )
mMvdLY = Clip3( -131072, 131071, Sign( distScaleFactor * mMvdLY )
* ((Abs( distScaleFactor * mMvdLY ) + 127 ) >> 8 ) )
Derive it as Here, currPocDiffLX indicates currPocDiffL0 when X=0, and currPocDiffL1 when X=1. Similarly, currPocDiffLY indicates currPocDiffL0 when Y=0 and currPocDiffL1 when Y=1. Further, Clip3(x,y,z) is a function that limits the minimum value to x and the maximum value to y for the value z. Sign(x) is a function that returns the sign of the value x, which is 1 if the value x is positive, 0 if the value x is 0, and -1 if the value x is negative. Abs(x) is a function that returns the absolute value of the value x. >> is a bitwise operator that indicates bit-shifting the left operand to the right by the number of bits of the right operand. With the above steps, the process of deriving the merged difference motion vector is completed.

The merge difference motion vector may be added to the top two motion vectors of the sub-block merging candidates. In this case, the index mmvd_distance_idx indicating the distance to be added to the motion vector is defined as in the table shown in FIG. 39(c). The operation of the sub-block merging candidate selection unit 386 is the same as that of the merging candidate selection unit 347, so the explanation will be omitted. Furthermore, since the operation of the sub-block merging candidate selection unit 486 is the same as that of the merging candidate selection unit 447, a description thereof will be omitted.

As described above, MmvdDistance is defined as shown in the tables shown in FIGS. 39(a) and 39(c). Since these tables are defined with quarter pixel precision, the merged difference motion vectors that are generated may include fractional pixel precision. However, by encoding/decoding the flag indicating that the pixel precision in these tables is 1 in slice units, it is possible to change the generated merged difference motion vector so that it does not include fractional pixel precision. .

<Adaptive motion vector resolution (AMVR)>
The resolution of the differential motion vector can be adaptively changed in units of encoded blocks. This resolution is called adaptive motion vector resolution.

A case where adaptive motion vector resolution is used for the normal predicted motion vector mode will be described. In this case, the derived candidate motion vectors are calculated in the spatial predictor motion vector candidate deriving sections 321 and 421, the temporal motion vector predictor candidate deriving sections 322 and 422, and the historical motion vector predictor candidate deriving sections 323 and 423. It is rounded. The resolution can be selected from 1/4, 1, and 4 pixel precision, and if you do not change the resolution, it will be 1/4 pixel precision. The rounding process is performed in accordance with the resolution of the motion vector in the encoded block to be processed. In other words, the derived candidate motion vector mvX is
rightShift = leftShift = MvShift + 2
offset = ( 1 << ( rightShift - 1 ) )
mvX = ( ( mvX + offset - ( mvX >= 0 ) ) >> rightShift ) << leftShift
is rounded off. However, if rightShift=0, offset=0. Here, if the resolution of the motion vector in the encoded block to be processed is 1/4 pixel precision, MvShift=0. Similarly, when the motion vector resolution is 1 pixel precision, MvShift=2, and when the motion vector resolution is 4 pixel precision, MvShift=4. According to the above formula, each of the x and y components of mvX is processed.

Adaptive motion vector resolution can also be used for sub-block predicted motion vector modes. In this case, the resolution is different from the normal predicted motion vector mode described above. That is, in the affine inheritance predicted motion vector candidate deriving units 361 and 461, the affine construction predicted motion vector candidate deriving units 362 and 462, and the affine identical predicted motion vector candidate deriving units 363 and 463, the derived candidate motion vectors are calculated based on the resolution. rounded accordingly. The resolution can be selected from 1/16, 1/4, and 1 pixel precision, and if you do not change the resolution, it will be 1/4 pixel precision. The rounding process is performed in accordance with the resolution of the motion vector in the encoded block to be processed. That is, the derived candidate motion vector mvX is rounded according to the above formula. Here, if the resolution of the motion vector in the encoded block to be processed is 1/4 pixel precision, MvShift=0. Similarly, when the motion vector resolution is 1/16 pixel precision, MvShift=-2, and when the motion vector resolution is 1 pixel precision, MvShift=2. Each of the x and y components of mvX is processed by the above formula.

<Intra block copy (IBC)>
The effective reference area for intra block copy will be explained with reference to FIG. 32. FIG. 32(a) is an example of determining an effective reference area using a coding tree block unit as an intra block copy reference block. 32A, 500, 501, 502, 503, and 504 are encoding tree blocks, and 504 is the encoding tree block to be processed. 505 is a processing target encoding block. The processing order of the encoding tree blocks is 500, 501, 502, 503, and 504. In this case, three encoding tree blocks 501, 502, and 503 processed immediately before the encoding tree block 504 including the encoding block 505 to be processed are set as effective reference areas for the encoding block 505 to be processed. Encoding tree blocks that have been processed before the encoding tree block 501 and encoding tree blocks that include the target encoding block 505, regardless of whether processing has been completed before the target encoding block 505. All areas included in 504 are invalid reference areas.

FIG. 32(b) is an example in which an effective reference area is determined using a unit obtained by dividing a coding tree block into four parts as an intra block copy reference block. In FIG. 32(b), 515 and 516 are encoding tree blocks, and 516 is the encoding tree block to be processed. Encoding tree block 515 is divided into four parts 506, 507, 508, and 509, and 516 is divided into four parts 510, 511, 512, and 513. 514 is a coding block to be processed. The processing order of intra block copy reference blocks is 506, 507, 508, 509, 510, 511, 512, and 513. In this case, the three intra block copy reference blocks 508, 509, and 510 that were processed immediately before the intra block copy reference block 511 including the target encoded block 514 are set as the valid reference area of the target encoded block 514. Intra block copy Intra block copy including the coded tree block processed before the reference block 508 and the coded block to be processed 514, regardless of whether processing has been completed before the coded block to be processed 514 All areas included in the reference block 511 are assumed to be invalid reference areas.

<Reference area memory space>
The memory space that stores the processed image of the reference area will be explained. FIG. 57 is a diagram for explaining the memory space of the reference area when the encoded tree block unit is used as the intra block copy reference block. 500, 501, 502, 503, 504, and 505 in FIG. 57(a) are encoding tree blocks. The encoding tree block 503 is the encoding tree block to be processed. The encoded tree block 500, the encoded tree block 501, the encoded tree block 502, and the encoded tree block 502 are processed encoded tree blocks, and correspond to the reference area of the encoded tree block 503 to be processed. Encoding tree blocks 504 and 505 are unprocessed encoding tree blocks. 600, 601, 602, and 603 in FIG. 57(a) are memory spaces, and the memory space 600 stores the processed image of the encoded tree block 500. Similarly, memory space 601 stores the processed image of encoded tree block 501 and memory space 602 stores the processed image of encoded tree block 502. The memory space 603 sequentially stores processed images according to the processing of the encoding tree block 503 to be processed. When the processing of the encoding tree block 503 is completed, the processing of the encoding tree block 504 is started next.

Processing when the processing of the encoded tree block 503 is completed will be described using FIG. 57(b). At this time, the encoding tree block 504 becomes the encoding tree block to be processed. Furthermore, the encoding tree block 503 becomes a reference area, and the encoding tree block 500 ceases to be a reference area. At this time, the processed images of the encoded tree block 503 are stored in the memory space 603, which had sequentially stored the processed images of the encoded tree block 503. The processed image of the encoded tree block 500 stored in the memory space 600 is not a reference area of the encoded tree block 504, but becomes unnecessary information. Therefore, processed images of the encoding tree block 504 to be processed are sequentially stored in the memory space 600. When the processing of the encoding tree block 504 is completed, the processing of the encoding tree block 505 is started next.

The process when the process of the encoded tree block 503 is completed will be described using FIG. 57(c). At this time, the encoding tree block 505 becomes the encoding tree block to be processed. Furthermore, the encoding tree block 504 becomes a reference area, and the encoding tree block 501 ceases to be a reference area. Similar to the above example, processed images of the encoding tree block 505 to be processed are sequentially stored in the memory space 601.

FIG. 58 is a diagram for explaining the memory space of a reference area when determining an effective reference area, using a unit obtained by dividing a coding tree block into four as an intra block copy reference block. 510 and 511 in FIG. 58(a) are encoding tree blocks. A coding tree block 510 is a processed coding tree block, and a coding tree block 511 is a coding tree block to be processed. Encoding tree block 510 is composed of blocks 500, 501, 502, and 503, and encoding tree block 511 is composed of blocks 504, 505, 506, and 507. Block 504 is a block to be processed. 501, 502, and 503 are processed blocks, which correspond to the reference area of the block 504 to be processed. Blocks 505, 506, and 507 are unprocessed blocks. 600, 601, 602, and 603 in FIG. 58(a) are memory spaces, and the memory space 601 stores the processed image of the block 501. Similarly, memory space 602 stores the processed image of block 502 and memory space 603 stores the processed image of block 503. The memory space 600 sequentially stores processed images according to the processing of the block 504 to be processed. When the process of block 504 is completed, the process of block 505 is started next.

The process when the process of block 504 is completed will be described using FIG. 58(b). At this time, block 505 becomes the encoding tree block to be processed. Furthermore, block 504 becomes a reference area, and block 501 ceases to be a reference area. At this time, the processed image of block 504 is stored in the memory space 600 that had sequentially stored the processed image of block 504. The processed image of block 501 stored in memory space 601 is not a reference area of block 505 and becomes unnecessary information. Therefore, the processed images of the block 505 to be processed are sequentially stored in the memory space 601. Once the processing of block 505 is completed, processing of encoding tree block 506 begins next.

The process when the process of block 504 is completed will be described using FIG. 58(c). At this time, block 506 becomes the block to be processed. Furthermore, block 505 becomes a reference region and encoding tree block 502 ceases to be a reference region. Similar to the above example, processed images of the encoding tree block 506 to be processed are sequentially stored in the memory space 602.

The process when the process of block 505 is completed will be described using FIG. 58(d). At this time, block 507 becomes the block to be processed. Furthermore, block 506 becomes a reference region, and encoding tree block 503 ceases to be a reference region. Similar to the above example, processed images of the encoding tree block 507 to be processed are sequentially stored in the memory space 603.

<Predicted intra block copy: Explanation on the encoding side>
The predictive intra block copy processing procedure on the encoding side will be described with reference to FIG.

First, the block vector detection unit 375 detects the block vector mvL (step S4500 in FIG. 45).

Subsequently, the IBC spatial block vector candidate derivation unit 371, the IBC history predicted block vector candidate derivation unit 372, the IBC predicted block vector candidate supplementation unit 373, the IBC predicted block vector candidate selection unit 376, and the block vector subtraction unit 378 calculate the predicted block vector. A differential block vector of the block vectors used in the mode is calculated (steps S4501 to S4503 in FIG. 45).

Predicted block vector candidates are calculated to construct a block vector candidate list mvpList (step S4501 in FIG. 45). The IBC spatial block vector candidate deriving unit 371, the IBC history block vector candidate deriving unit 372, and the IBC predictive block vector candidate replenishing unit 373 in the intra block copy prediction unit 352 derive a plurality of predictive block vector candidates, and the predictive block vector Build candidate list mvpList. The detailed processing procedure of step S4501 in FIG. 45 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. 45). Each differential block vector that is the difference between the block vector mvL and each predictive block vector candidate mvpListL[i] stored in the predictive block vector candidate list mvpListL is calculated. The amount of code when these differential 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] with the minimum code amount for each predictive block vector candidate is selected as the predictive block vector mvpL, and Get index i. If there are multiple predictive block vector candidates with the minimum generated code amount in the predictive block vector candidate list mvpListL, the predictive block vector whose index i in the predictive block vector candidate list mvpListL is represented by a small number is used. Select candidate mvpListL[i] as the optimal predicted block vector mvpL, and obtain its index i.

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

<Intra block copy (prediction): Explanation on the decoding side>
Next, the predicted 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 to be used in the prediction block vector mode (from step S4600 in FIG. 46). 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.

A predictive block vector candidate list mvpListL is constructed by calculating predictive block vector candidates (step S4601 in FIG. 46). The IBC spatial block vector candidate deriving unit 471, the IBC history block vector candidate deriving unit 472, and the 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. Construct mvpListL. A detailed description of the processing procedure in step S4601 in FIG. 46 will be omitted.

Next, 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. The selected predictive block vector mvpL is extracted (step S4601 in FIG. 46).

Next, a block vector addition unit 478 adds the differential block vector mvdL decoded and supplied by the bit string decoding unit 201 and the predicted block vector mvpL,
mvL = mvpL + mvdL
The block vector mvL is calculated as (step S4602 in FIG. 46).

<Predicted block vector mode: block vector prediction method>
FIG. 48 shows predicted intra block copy mode derivation processing having a common function between 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 flowchart showing a processing procedure.

The intra block copy prediction unit 352 and the intra block copy prediction unit 362 are provided with a predicted block vector candidate list mvpListL. The predictive block vector candidate list mvpListL has a list structure, and is provided with a predictive block vector index indicating the location within the predictive block vector candidate list, and a storage area for storing the predictive block vector candidate corresponding to the index as an element. The predictive block vector index number starts from 0, and the predictive block vector candidates are stored in the storage area of the predictive 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. Further, a variable numCurrMvpIbcCand indicating the number of predictive block vector candidates registered in the predictive block vector candidate list mvpListL is set to 0.
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. 48). In this process, a flag availableFlagLA indicating whether a predictive block vector candidate for the block adjacent to the left (A0 or A1) is available and a block vector mvLA 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 prediction block vector candidates from the upper adjacent block (B0, B1, or B2) (step S4802 in FIG. 48). In this process, a flag availableFlagLB indicating whether the motion vector predictor candidate of the upper adjacent block is available and a block vector mvLB are derived, and if mvLA and mvLB are not equal, mvLB is added to the predicted block vector candidate list mvpListL. to add. The processes in steps S4801 and S4802 in FIG. 48 are common except that the positions and numbers of neighboring blocks to be referred to are different, and include a flag availableFlagLN indicating whether a predictive block vector candidate for the encoded block is available, and a motion vector mvLN. (N is A or B, the same applies hereafter).

Subsequently, the IBC history block vector candidate deriving units 372 and 472 add the history block vector candidates registered in the history block vector candidate list HmvpIbcCandList to the predicted block vector candidate list mvpListL. (Step S4803 in FIG. 48). For details of the registration processing procedure in step S4803, in the description of the operation shown in the flowchart of FIG. The explanation will be omitted since it is sufficient if the operation is the same as when using HmvpIbcCandList.

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

<Merge intra block copy mode derivation part>
The intra block copy prediction unit 352 in FIG. 43 includes an IBC spatial 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 It includes a merge candidate selection section 374 and an IBC prediction mode determination section 377.

The intra block copy prediction unit 362 in FIG. 44 includes an IBC spatial block vector candidate derivation unit 471, an IBC history block vector candidate derivation unit 472, an IBC block vector supplementation unit 473, an IBC merge candidate selection unit 474, a reference position correction unit 480, see It includes an area boundary correction section 481 and a block copy section 477.

FIG. 47 shows merge intra block copy mode derivation processing having a common function between 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 flowchart explaining a procedure.

The intra block copy prediction unit 352 and the intra block copy prediction unit 362 are provided with 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 merge index number 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, the merge candidate with the merge index i registered in the merge intra block copy candidate list mergeIbcCandList will be represented by mergeIbcCandList [i]. In this embodiment, it is assumed that the merge candidate list mergeCandList can register at least three merge intra block copy candidates. Further, a variable numCurrMergeIbcCand indicating the number of merge intra block copy candidates registered in the merge intra block copy candidate list mergeIbcCandList is set to 0.

The IBC spatial block vector candidate deriving unit 371 and the IBC spatial block vector candidate deriving unit 471 perform 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. From the information, derive spatial merging candidates A and B from blocks adjacent to the left and upper sides of the block to be processed, and register the derived spatial merging candidates in the merge intra block copy candidate list mergeIbcCandList (step S4701 in FIG. 47). ). Here, N indicating either spatial merging candidate A or B is defined. A flag availableFlagN indicating whether intra block copy prediction information of block N can be used as a spatial block vector merging candidate N and a block vector mvL are derived. However, in this embodiment, block vector merging candidates are derived without referring to other coded blocks included in the block containing the coded block to be processed. Spatial block vector merging candidates included in are not derived.

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. 47). In this embodiment, if a block vector already added to mergeIbcCandList and a block vector of a history predicted block vector candidate have the same value, they are not added to mergeIbcCandList.

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 IBC predicted block vector replenishment unit 373 and the IBC predicted block vector replenishment unit 473 The number of merge candidates numCurrMergeIbcCand registered in the merge intra block copy candidate list mergeIbcCandList is added up to the maximum number of merge candidates MaxNumMergeIbcCand. Intra block merge candidates are derived and registered in the merge intra block copy candidate list mergeIbcCandList (see Figure 47). Step S4703). With the maximum number of merge candidates MaxNumMergeIbcCand as the upper limit, block vectors with 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 of the intra block merge candidates registered in the merge intra block copy candidate list mergeIbcCandList (step S4704 in FIG. 47). 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 selects a merge index indicating the selected intra block merge candidate. It is supplied to the IBC prediction mode determination section 377. The IBC prediction mode determination unit 377 selects whether or not the merge mode is selected by calculating the code amount and distortion amount, and supplies the result to the prediction method determination unit 105. On the other hand, the IBC merging candidate selection unit 474 on the decoding side selects an intra block merging candidate based on the decoded merging index, and supplies the selected intra block merging candidate to the reference position correction unit 480.

Subsequently, the reference position correction unit 380 and the reference position correction unit 480 perform a process of correcting the reference position for the intra block merging candidate (step S4705 in FIG. 47). Details of the processing by the reference position correction unit 380 and the reference position correction unit 480 will be described later.

Subsequently, the reference area boundary correction unit 381 and the reference area boundary correction unit 481 perform a process of correcting the reference area boundary for the intra block merging candidate (step S4706 in FIG. 47). Details of the processing by 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 superimposition 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. The color difference block vector mvC is, when the color difference format is 420,
mvC = ( ( mvL >> ( 3 + 2 ) ) * 32
becomes. According to the above equation, each of the x and y components of mvC is processed.

<Reference position correction section>
FIG. 49 is a diagram illustrating the processing of the reference position correction unit 380 and the reference position correction unit 480. Now, assume that the unit of the intra block copy reference block is a coding tree block (CTU), and its size is not 128x128 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 referenced by a processing target encoding block using a block vector. If the upper left of the reference block is ( xRefTL, yRefTL ) and the lower right is ( xRefBR, yRefBR ), then
( xRefTL, yRefTL ) = ( xCb + ( mvL[ 0 ] >> 4 ), yCb + ( mvL[ 1 ] >> 4 ) )
( xRefBR, yRefBR ) = ( xRefTL + cbWidth - 1, yRefTL + cbHeight - 1 )
becomes. Here, it is assumed that 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 the size of CTU is 128x128 pixels (S6002). Now, since the size is not 128x128 pixels (S6002: NO), the upper left and lower right positions of the referenceable area are calculated (S6003). If the upper left of the referenceable area is ( xAvlTL, yAvlTL ) and the lower right is ( xAvlBR, yAvlBR ), then
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 size of CTU is assumed to be CtbLog2SizeY.

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

FIG. 50 is a diagram showing how the reference position is corrected. 6001 indicates a coding tree block to be processed, 6002 indicates a coding block to be processed, and 6003 indicates a referenceable area. Now, if the reference block r2 is located at 6011, the reference position in the x direction is smaller than the upper left of the referenceable area (S6004: YES). Therefore, the reference position is corrected to position 6012 by setting xRefTL=xAvlTL (S6005). Here, as shown in S6001, since xRefBR=xRefTL+cbWidth-1, xRefBR is also corrected as xRefTL is corrected. In correcting this reference position, the block vector mvL[0] may be corrected. In other words,
mvL[0] = (xAvlTL - xCb) << 4
and correct it. As a result, xRefTL=xAvlTL, so the reference position can be corrected.

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

Now, assume that some block vectors in the block vector candidate list constructed by the intra block copy prediction unit 352 are outside the referenceable area. If the reference position is not corrected, it is impossible to refer to those block vectors, so those block vectors cannot be used as 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 referenceable area. Therefore, all block vectors can be referred to, and all block vectors can be candidates for IBC merge mode. Therefore, the IBC merge mode selection unit 374 can select the optimal prediction mode from the IBC merge mode candidates corresponding to all block vectors, thereby improving coding efficiency.

Now, assume that some block vectors in the block vector candidate list constructed by the intra block copy prediction unit 362 are outside the referenceable area. If the reference position is not corrected, reference using those block vectors is impossible, and IBC merge mode using those block vectors cannot be decoded. In an encoding device other than the present invention, the merge index indicating the IBC merge mode using those block vectors operates as if it were not encoded. However, due to a malfunction or the like, such a merge index may be encoded to generate a bitstream. Alternatively, if a part of the bitstream is missing due to packet loss or the like, the decoding result may become such a merge index. When attempting to decode such an incomplete bitstream, there is a possibility that the decoded image memory at an incorrect position is accessed in an attempt to refer to an area outside the referenceable area. As a result, the decoding results may vary depending on the decoding device, or the decoding process may stop. 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 referenceable area. Therefore, even if such an incomplete bitstream is decoded, the reference position is corrected to be inside the referenceable area and reference becomes possible. In this way, by correcting the reference position, the memory access range is guaranteed. As a result, the decoding results are 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.

Furthermore, when a block vector is corrected in the reference position correction, the target is a luminance block vector. 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 will also be corrected. Therefore, there is no need to correct the reference position again for color difference. The amount of processing can be reduced compared to the case where it is necessary to determine whether reference is possible using both luminance and color difference when the block vector is not corrected.

In addition, when correcting a block vector in the reference position correction, the corrected block vector is stored in the coded information storage memory 111 or the coded information storage memory 205 as a block vector of the processing target coded block. In other words, the corrected reference position and the position pointed to by the block vector are the same. Here, deblock filter processing may be performed when storing 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. Compared to the case where the block vector is not corrected, where the corrected reference position and the position pointed to by the block vector are different, the strength of the filter becomes more appropriate, so that encoding efficiency can be improved.

Next, it is determined whether 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 advances 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 referenceable area (S6007).

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

Next, it is determined whether the reference position of the reference block in the x direction is larger than the lower right of the referenceable area (S6008). If the determination is false (S6008: NO), the process advances to the next process (S6010). On the other hand, if the determination is true (S6008: YES), the reference position in the x direction is corrected to match the lower right of the referenceable area (S6009).

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

Next, it is determined whether the reference position of the reference block in the y direction is larger than the lower right of the referenceable 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 to match the lower right of the referenceable area (S6011).

Now, if the reference block r5 is located at 6041, the reference position in the y direction is larger than the lower right of the referenceable area (S6010: YES). Therefore, the reference position is corrected to the position 6042 by setting yRefBR=yAvlBR (S6011). Here, as shown in S6001, since yRefBR=yRefTL+cbHeight-1, that is, yRefTL=yRefBR-(cbHeight-1), yRefTL is also corrected as yRefBR is corrected. In correcting this reference position, the block vector mvL[1] may be corrected. In other words,
mvL[1] = (yAvlBR - (yCb + cbHeitght - 1)) << 4
and correct it. As a result, yRefBR=yAvlBR, so the reference position can be corrected.

Here, a case where the reference block r1 is located at 6051 will be explained. In this case, the reference position in the x direction is corrected as in the case where the reference block is r2. Furthermore, as in the case where the reference block is r4, the reference position in the y direction is corrected. As a result, the reference block r1 is located at 6052, which is inside the referenceable area.

When reference block r3 is located at 6061, when reference block r6 is located at 6062, and when reference block r8 is located at 6063, the reference position in each x and y direction is determined in the same way as above. to correct. As a result, each reference block is located inside the referenceable area.

With the above steps, the process when the CTU size is not 128x128 pixels ends. On the other hand, if the size of the CTU is 128x128 pixels (S6002: YES), the upper left and lower right positions are calculated when the referenceable area is rectangular (S6012).

FIG. 51 is a diagram illustrating the upper left and lower right positions when the referenceable area is rectangular. In the case of FIG. 51(a), the encoding tree block 6101 to be processed is divided into four parts, and the encoding block 6102 to be processed is located at the upper left of the division. At this time, the referenceable area has an inverted L shape as shown by the diagonal line in 6103. When the referenceable area is rectangular, its range is the rectangular range 6103. If the referenceable 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 encoded block to be processed. If the encoding tree block to be processed is divided into four, and the encoding block to be processed is located at the upper left, blk_idx=0. Similarly, if the encoding blocks to be processed are located at the upper right, lower left, and lower right, respectively, blk_idx is set to 1, 2, and 3. FIG. 51(a) is a diagram showing the case where blk_idx=0. Similarly, FIGS. 51(b) to 51(d) are diagrams showing cases where blk_idx=1 to 3, respectively.

Next, the reference position of the portion where the referenceable area is not rectangular is corrected (S6013). FIG. 52 is a diagram illustrating a process of correcting a reference position in a portion where the referenceable area is not rectangular. First, the upper left position of the referenceable area is calculated (S6021). Since the referenceable area is the shaded area in FIG. 51, there are two upper left positions, 6111 and 6112, except in 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) = (xAvlTL, yAvlTL + 64)
(X2, Y2) = (xAvlTL + NL, yAvlTL)
becomes.

Next, it is determined whether the reference position is corrected to match the upper left of the referenceable area (S6022). This determination is determined to be true if blk_idx=3 and the reference block is located in an area smaller than X2 and Y1 (S6022: YES). If it is false (S6022: NO), proceed to the next process (S6026).

Next, it is determined whether the difference between the reference block and the referenceable area in the x direction is smaller than the difference between the reference block and the referenceable area in the y direction (S6023). If the determination is true (S6023: YES), the reference position in the x direction 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. 53(a) is a diagram showing how the reference position is corrected in S6024 and S6025. Now blk_idx=0. Assuming that 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). Further, the difference between the reference block and the referenceable area in the x direction is smaller than the difference between the reference block and the referenceable area in the y direction (S6023: YES). Therefore, the reference position in the x direction is corrected to the position 6202 by setting xRefTL=xAvlTL+NL (S6024). Here, as shown in S6001, since xRefBR=xRefTL+cbWidth-1, xRefBR is also corrected as xRefTL is corrected. In correcting this reference position, the block vector mvL[0] may be corrected. In other words,
mvL[0] = (xAvlTL + NL - xCb) << 4
and correct it. As a result, xRefTL=xAvlTL+NL, so the reference position can be corrected.

On the other hand, if 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). Further, the difference between the reference block and the referenceable area in the x direction is not smaller than the difference between the reference block and the referenceable area in the y direction (S6023: NO). Therefore, the reference position in the y direction is corrected to the position 6204 by setting yRefTL=yAvlTL+64 (S6025). Here, since yRefBR=yRefTL+cbHeight-1 as shown in S6001, yRefBR is also corrected as yRefTL is corrected. In correcting this reference position, the block vector mvL[0] may be corrected. In other words,
mvL[1] = (yAvlTL + 64 - yCb) << 4
and correct it. As a result, yRefTL=yAvlTL+64, so the reference position can be corrected.

Here, assume that the reference block r3 is located at 6205. In this case, the difference between the reference block and the referenceable area in the x direction is smaller than the difference between the reference block and the referenceable area in the y direction (S6023: YES). Therefore, by correcting the reference position in the x direction similarly to the reference block r1, it is located 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 processing in S6006 and S6007, which will be described later. Eventually, the reference block becomes inside the referenceable area.

Next, the lower right position of the referenceable area is calculated (S6026). Since the referenceable area is the shaded area in FIG. 51, there are two lower right positions, 6113 and 6114, except when 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 the reference position is corrected to match the lower right of the referenceable area (S6027). This determination is determined to be true if blk_idx=0 and the reference block is located in an area larger than X4 and Y3 (S6027: YES). If it is false (S6027: NO), the process ends.

Next, it is determined whether the difference between the reference block and the referenceable area in the x direction is smaller than the difference between the reference block and the referenceable area in the y direction (S6028). If the determination is true (S6028: YES), the reference position in the x direction 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. 53(b) is a diagram showing how the reference position is corrected in S6029 and S6030. Now, blk_idx=3. If 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). Further, the difference between the reference block and the referenceable area in the x direction is smaller than the difference between the reference block and the referenceable area in the y direction (S6028: YES). Therefore, the reference position in the x direction is corrected to the position 6212 by setting xRefBR=xAvlBR (S6029). Here, as shown in S6001, since xRefBR=xRefTL+cbWidth-1, that is, xRefTL=xRefBR-(cbWidth-1), xRefTL is also corrected along with the correction of xRefBR. In correcting this reference position, the block vector mvL[0] may be corrected. In other words,
mvL[0] = (xAvlBR - NR - (xCb + cbWitdh - 1)) << 4
and correct it. As a result, xRefBR=xAvlBR, so the reference position can be corrected.

On the other hand, if reference block r2 is located at 6213, 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). Further, the difference between the reference block and the referenceable area in the x direction is not smaller than the difference between the reference block and the referenceable area in the y direction (S6028: NO). Therefore, the reference position in the y direction is corrected to the position 6214 by setting yRefBR=yAvlBR (S6030). Here, as shown in S6001, since yRefBR=yRefTL+cbHeight-1, that is, yRefTL=yRefBR-(cbHeight-1), yRefTL is also corrected as yRefBR is corrected. In correcting this reference position, the block vector mvL[1] may be corrected. In other words,
mvL[1] = (yAvlBR - 64 - (yCb + cbHeight - 1)) << 4
and correct it. As a result, yRefBR=yAvlBR, so the reference position can be corrected.

Here, it is assumed that the reference block r3 is located at 6215. In this case, the difference between the reference block and the referenceable area in the x direction is not smaller than the difference between the reference block and the referenceable area in the y direction (S6028: NO). Therefore, by correcting the reference position in the y direction similarly to the reference block r2, it is located at 6216 (S6030). At this point, the reference block is outside the referenceable area. However, the reference position in the x direction is corrected by processing in S6008 and S6009, which will be described later. Eventually, the reference block becomes inside the referenceable area.

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

After the process of correcting the reference position of the portion where the referenceable area is not rectangular (S6013), processes from S6004 to S6011 are performed. With the above steps, the processing when the CTU size is 128x128 pixels is completed.

Now, suppose that in the process of correcting the reference position of a portion where the referenceable area is not rectangular (S6013), the process of correcting the reference position in the x direction to match the upper left of the referenceable area (S6024) 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 process of S6024 is performed, the processes of S6004 and S6005 may not be performed. Similarly, if S6025 is processed, S6006 and S6007 may not be processed, if S6029 is processed, S6008 and S6009 may not be processed, or if S6030 is processed, S6008 and S6009 may not be processed. In this case, the processing in S6010 and S6011 may be omitted.

Furthermore, in the flowchart of FIG. 52, a configuration may be adopted in which the comparison process in step S6023 is omitted and step S6024 is always executed, or a configuration in which step S6025 is always executed. Similarly, a configuration may be adopted in which the comparison process in step S6028 is omitted and step S6029 is always executed, or a configuration in which step S6030 is always executed. In such a configuration, it becomes possible to correct the reference position with simple processing.

In FIG. 49, when the CTU size is 128x128 pixels, the reference position is corrected using the processes of S6012, S6013, and S6004 to S6011. Alternatively, as shown in FIG. 54, this can also be achieved by dividing the referenceable area into two parts and correcting the respective reference positions (S6101).

FIG. 55 is a diagram illustrating how the referenceable area is divided into two. Unlike the referenceable area in FIG. 51, which has a rectangular shape, the referenceable area in FIG. 55 is divided into two. When the encoding tree block (6101) to be processed is divided into four, and the encoding block (6102) to be processed is located at the upper left, blk_idx=0. Similarly, if the encoding blocks to be processed are located at the upper right, lower left, and lower right, respectively, blk_idx is set to 1, 2, and 3. FIG. 55(a) is a diagram showing the case where blk_idx=0. Similarly, FIGS. 55(b) to 55(d) are diagrams showing cases where blk_idx=1 to 3, respectively. Furthermore, one referenceable area (6301) is referred to as referenceable area A, and the other referenceable area (6302) is referred to as referenceable area B.

FIG. 56 is a diagram illustrating a process (S6101) of dividing a referenceable area into two and correcting the respective reference positions. In FIG. 56, the same steps as those in FIG. 49 are given the same step numbers, and the description thereof will be omitted. First, the upper left and lower right positions of the referenceable area A are calculated (S6111). If the upper left of referenceable area A is ( xAvlTL, yAvlTL ) and the lower right is ( xAvlBR, yAvlBR ), then
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 the reference block is outside the referenceable 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 referenceable area B are calculated (S6113). If the upper left of referenceable area B is (xAvlTL, yAvlTL) and the lower right is (xAvlBR, yAvlBR), then
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 reference position of the reference block in the x direction is smaller than the upper left of the referenceable area A, and the reference position of the reference block in the x direction is smaller than the upper left of the referenceable area B (S6114). If the determination is false (S6114: NO), the process advances 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 to match the upper left of the referenceable area B (S6005). Since the process of S6005 has already been explained, the explanation will be omitted.

Next, it is determined whether the reference position of the reference block in the y direction is smaller than the upper left of the referenceable area A and the reference position of the reference block in the y direction is smaller than the upper left of the referenceable area B (S6116). If the determination is false (S6116: NO), the process advances 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 referenceable area B (S6007). Since the process of S6007 has already been explained, the explanation will be omitted.

Next, it is determined whether the reference position of the reference block in the x direction is larger than the lower right of the referenceable area A and the reference position of the reference block in the x direction is larger than the lower right of the referenceable area B (S6118). . If the determination is false (S6118: NO), the process advances 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 to match the lower right of the referenceable area B (S6009). Since the process of S6009 has already been explained, the explanation will be omitted.

Next, it is determined whether the reference position of the reference block in the y direction is larger than the lower right of the referenceable area A and the reference position of the reference block in the y direction is larger than the lower right of the referenceable 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 to match the lower right of the referenceable area B (S6011). Since the process of S6011 has already been explained, the explanation will be omitted.

As described above, when the size of the CTU is 128x128 pixels, even if the reference block is located outside the referenceable area, it can be referenced by correcting the reference position. Further, by dividing the referenceable area into two and correcting the reference positions of each, it is possible to simplify the process and reduce the amount of calculation. Here, one referenceable area (6301) is referred to as referenceable area A, and the other referenceable area (6302) is referred to as referenceable area B. Alternatively, the referenceable area A and the referenceable area B may be exchanged, and one referenceable area (6301) may be treated as the referenceable area B, and the other referenceable area (6302) may be processed as the referenceable area A. .

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

<Reference area boundary correction unit>
FIG. 59 is a flowchart for explaining the processing of the reference area boundary correction unit 381 and the reference area boundary correction unit 481.

First, set the top left position of the reference block to
( xRefTL, yRefTL ) = ( xCb + ( mvL[ 0 ] >> 4 ), yCb + ( mvL[ 1 ] >> 4 ) )
( xRefBR, yRefBR ) = ( xRefTL + cbWidth - 1, yRefTL + cbHeight - 1 )
(Step S1401). This procedure is the same as step S6001 in FIG. 49, so a description thereof will be omitted.

Next, the upper left and lower right positions of each of the referenceable areas A, B, and C are calculated (steps S1402 to S1403). Here, referenceable area A is an intrablock copy reference block processed immediately before the intra block copy reference block to be processed, and referenceable area B is an intrablock copy reference block processed immediately before referenceable area A. , referenceable area C is an intra block copy reference block processed immediately before referenceable area B. FIG. 57 is an example in which the encoded tree block unit is used as the intra block copy reference block. In the example of FIG. 57(a), the encoding tree block 503 is the encoding tree block to be processed. At this time, the encoding tree block 502 corresponds to the referenceable area A, the encoding tree block 501 corresponds to the referenceable area B, and the encoding tree block 500 corresponds to the referenceable area C. FIG. 58 is an example in which a unit obtained by dividing a coding tree block into four is used as an intra block copy reference block. In the example of FIG. 57(a), the encoded tree block 504 is the intra block copy reference block to be processed. At this time, the encoding tree block 503 corresponds to the referenceable area A, the encoding tree block 502 corresponds to the referenceable area B, and the encoding tree block 501 corresponds to the referenceable area C.

The upper left positions of referenceable areas A, B, and C are respectively (xAvlATL, yAvlATL), (xAvlBTL, yAvlBTL), and (xAvlCTL, yAvlCTL). Further, the lower right positions of referenceable areas A, B, and C are respectively (xAvlABR, yAvlABR), (xAvlBBR, yAvlBBR), and (xAvlCBR, yAvlCBR). When the encoding tree block unit is used as the intra block copy reference block, (xAvlATL, yAvlATL), (xAvlBTL, yAvlBTL), (xAvlCTL, yAvlCTL), (xAvlABR, yAvlABR), (xAvlBBR, yAvlBBR), (xAvlCBR, yAvlCBR ), respectively.
(xAvlATL, yAvlATL) = ( (xCb >> CtbLog2SizeY) << (CtbLog2SizeY) - (1 << CtbLog2SizeY),
(yCb >> CtbLog2SizeY) << (CtbLog2SizeY))
(xAvlABR, yAvlABR) = (xAvlATL + cbWidth - 1, yAvlATL + cbHeight - 1 )
(xAvlATL, yAvlATL) = ( (xCb >> CtbLog2SizeY) << (CtbLog2SizeY) - 2*(1 << CtbLog2SizeY)),
(yCb >> CtbLog2SizeY) << (CtbLog2SizeY))
(xAvlBBR, yAvlBBR) = (xAvlBTL + cbWidth -1, yAvlBTL + cbHeight - 1 )
(xAvlATL, yAvlATL) = ( (xCb >> CtbLog2SizeY) << (CtbLog2SizeY) - 3*(1 << CtbLog2SizeY),
(yCb >> CtbLog2SizeY) << (CtbLog2SizeY))
(xAvlCBR, yAvlCBR) = (xAvlCTL + cbWidth -1, yAvlCTL + cbHeight - 1 )
shall be. When the intra block copy reference block is a unit obtained by dividing the encoded tree block into four, (xAvlATL, yAvlATL), (xAvlBTL, yAvlBTL), and (xAvlCTL, yAvlCTL) are respectively,
(xAvlATL, yAvlATL) = ( (xCb >> (CtbLog2SizeY-1)) << (CtbLog2SizeY-1) - (1 << (CtbLog2SizeY-1)),
(yCb >> (CtbLog2SizeY-1)) << ((CtbLog2SizeY-1))+ (1<<(CtbLog2SizeY-1)))
(xAvlABR, yAvlABR) = (xAvlATL + cbWidth - 1, yAvlATL + cbHeight - 1 )
(xAvlBTL, yAvlBTL) = ( (xCb >> (CtbLog2SizeY-1)) << (CtbLog2SizeY-1) - (1 << (CtbLog2SizeY)),
(yCb >> (CtbLog2SizeY-1)) << ((CtbLog2SizeY-1))+ (1<<(CtbLog2SizeY-1)))
(xAvlBBR, yAvlBBR) = (xAvlBTL + cbWidth -1, yAvlBTL + cbHeight - 1 )
(xAvlCTL, yAvlCTL) = ( (xCb >> (CtbLog2SizeY-1)) << (CtbLog2SizeY-1) - (1 << (CtbLog2SizeY-1)),
(yCb >> (CtbLog2SizeY-1)) << ((CtbLog2SizeY-1))+ (1<<(CtbLog2SizeY-1)))
(xAvlCBR, yAvlCBR) = (xAvlCTL + cbWidth -1, yAvlCTL + cbHeight - 1 )
shall be.

Next, a referenceable area including the upper left position of the reference block is determined. (Step S1405). Specifically, the upper left and lower right positions of referenceable areas A, B, and C are compared with the upper left position of the reference block, and the referenceable area that includes the upper left position of the reference block is determined as the referenceable area that includes the reference block. shall be.

Next, it is determined whether the referenceable area including the upper left position of the reference block includes the lower right position of the reference block (step S1406). If the referenceable area including the upper left position of the reference block includes the lower right position of the reference block, the flowchart of FIG. 59 ends.

If the referenceable area including the upper left position of the reference block does not include the lower right position of the reference block, the reference block is corrected (step S1407). Reference block correction will be explained using FIG. 60. FIG. 60 is an example in which the encoded tree block unit is used as the intra block copy reference block. FIG. 60(a) shows a case where a block vector 507 is set for the encoded block 505 to be processed. Referenceable area B (503) includes the upper left position of the reference block, but does not include the lower right position of the reference block. At this time, as shown in FIG. 60(b), the reference block 508 is divided and arranged into a divided reference block 509 and a divided reference block 510 in the memory space. The divided reference block 509 is an area included in the referenceable area B (503), which is a referenceable area including the upper left of the reference block, and the divided reference block 510 is a reference area different from the referenceable area B (503). This is a reference block included in . In this embodiment, when constructing the reference image of the reference block 510, different processing is performed on an area corresponding to the divided reference block 509 and an area corresponding to the divided reference block 510. Specifically, for the area corresponding to the divided reference block 509, a reference image is created based on the position indicated by the block vector. On the other hand, for the area corresponding to the divided reference block 510, a reference image is created by setting a predetermined value without referring to the memory space 600. Here, the predetermined value is MaxPixelValue/2, where the maximum value of pixel values is MaxPixelValue. However, for the region corresponding to the divided reference block 510, a configuration may be adopted in which a reference image is constructed from the memory space 603 including the divided reference block 509 instead of the predetermined value. For example, the reference image may be constructed by horizontally copying the rightmost pixel of the divided reference block 509.

FIG. 61 is an example in which a unit obtained by dividing a coding tree block into four is used as an intra block copy reference block. FIG. 61A shows a case where a block vector 508 is set for a coding block 509 to be processed. The referenceable area C (501) includes the upper left position of the reference block, but does not include the lower right position of the reference block. At this time, as shown in FIG. 61(b), the reference block 510 is divided and arranged into a divided reference block 511 and a divided reference block 512 in the memory space. The divided reference block 511 is an area included in the referenceable area C (501), which is a referenceable area including the upper left of the reference block, and the divided reference block 512 is a reference area different from the referenceable area C (501). This is a reference block included in . In this embodiment, when constructing the reference image of the reference block 510, different processing is performed on an area corresponding to the divided reference block 511 and an area corresponding to the divided reference block 512. Specifically, for the area corresponding to the divided reference block 511, a reference image is created based on the position indicated by the block vector. On the other hand, for the area corresponding to the divided reference block 511, a reference image is created by setting a predetermined value without referring to the memory space 602. Here, the predetermined value is MaxPixelValue/2, where the maximum value of pixel values is MaxPixelValue. However, for the region corresponding to the divided reference block 512, a configuration may be adopted in which a reference image is constructed from the memory space 601 including the divided reference block 511 instead of a predetermined value. For example, the reference image may be constructed by vertically copying the lowest pixel of the divided reference block 511.

By adopting this configuration, when determining a reference block for intra block copying, when a reference image is divided and arranged in a memory space, it is possible to avoid accessing the divided memory space multiple times. I can do it. Therefore, it is possible to reduce the amount of processing required to configure reference blocks for intra block copying.

In all the embodiments described above, the encoded 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. are doing. The encoded bitstream may be provided by being recorded on 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 encoded bitstream of this specific data format, regardless of the providing means.

When a wired or wireless network is used to exchange encoded bitstreams between an image encoding device and an image decoding device, the encoded bitstreams are converted into a data format suitable for the transmission form of the communication channel. May be transmitted. In that case, there is a transmitting device that converts the encoded bitstream output by the image encoding device into encoded data in a data format suitable for the transmission form of the communication channel and sends it to the network, and a transmitter that receives the encoded data from the network. A receiving device is provided that restores the encoded bitstream and supplies the encoded bitstream to an image decoding device. The transmitting device includes a memory that buffers the encoded bitstream output by the image encoding device, a packet processing unit that packetizes the encoded bitstream, and a transmitting unit that transmits the packetized encoded data via a network. including. The receiving device includes a receiving unit that receives packetized encoded data via a network, a memory that buffers the received encoded data, and performs packet processing on the encoded data to generate an encoded bitstream. and a packet processing unit provided to the image decoding device.

When a wired or wireless network is used to exchange encoded 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 A relay device may be provided for receiving and supplying the signal to the receiving device. The relay device includes a receiving unit that receives the packetized encoded data transmitted by the transmitting device, a memory that buffers the received encoded data, and a transmitting unit that transmits the packetized encoded data to the network. include. Furthermore, the relay device includes a reception packet processing unit that performs packet processing on the packetized encoded data to generate an encoded bitstream, a recording medium that stores the encoded bitstream, and a recording medium that packetizes the encoded bitstream. It may also include a transmission packet processing section.

Further, by adding a display section that displays images decoded by an image decoding device to the configuration, it may be used as a display device. In that case, the display section reads out the decoded image signal generated by the decoded image signal superimposing section 207 and stored in the decoded image memory 208 and displays it on the screen.

Alternatively, an imaging device may be used by adding an imaging section to the configuration and inputting the captured image to an image encoding device. In that case, the imaging unit inputs the captured image signal to the block dividing unit 101.

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

The present invention has been described above based on the embodiments. It will be understood by those skilled in the art that the embodiments are merely illustrative, and that various modifications can be made to the combinations of the constituent elements and processing processes, and that such modifications are also within the scope of the present invention. .

100 image encoding device, 101 block division unit, 102 inter prediction unit, 103 intra prediction unit, 104 decoded image memory, 105 prediction method determination unit, 106 residual signal generation unit, 107 orthogonal transformation/quantization unit, 108 bit string code 109 inverse quantization/inverse orthogonal transform unit 110 decoded image signal superimposition unit 111 encoded information storage memory 200 image decoding device 201 bit string decoding unit 202 block division unit 203 inter prediction unit 204 intra prediction unit , 205 encoded information storage memory, 206 inverse quantization/inverse orthogonal transform unit, 207 decoded image signal superimposition unit, 208 decoded image memory.

Claims (8)

a block vector candidate derivation unit that derives a block vector candidate for a block to be processed in a picture to be processed from encoding information stored in an encoding information storage memory;
a selection unit that selects a selected block vector from the block vector candidates;
determining a referenceable area including the upper left position of the reference block to be referenced by the selected block vector from the plurality of referenceable areas;
For the first divided reference block included in the referenceable area including the upper left position of the reference block, decoded pixels in the target picture are transferred to the target block based on the reference position of the reference block. obtained from the decoded image memory unit as the predicted value of
a reference area boundary correction unit that sets a predetermined value as a predicted value of the processing target block for a second divided reference block included in a reference possible area that does not include the upper left position of the reference block;
An image encoding device comprising: a block vector candidate deriving step of deriving a block vector candidate for a block to be processed in a picture to be processed from encoding information stored in an encoding information storage memory;
a selection step of selecting a selected block vector from the block vector candidates;
determining a referenceable area including the upper left position of the reference block to be referenced by the selected block vector from the plurality of referenceable areas;
For the first divided reference block included in the referenceable area including the upper left position of the reference block, decoded pixels in the target picture are transferred to the target block based on the reference position of the reference block. obtained from the decoded image memory step as the predicted value of
For a second divided reference block included in a referenceable area that does not include the upper left position of the reference block, a reference area boundary correction step of setting a predetermined value as a predicted value of the processing target block;
An image encoding method comprising: a block vector candidate deriving step of deriving a block vector candidate for a block to be processed in a picture to be processed from encoding information stored in an encoding information storage memory;
a selection step of selecting a selected block vector from the block vector candidates;
determining a referenceable area including the upper left position of the reference block to be referenced by the selected block vector from the plurality of referenceable areas;
For the first divided reference block included in the referenceable area including the upper left position of the reference block, decoded pixels in the target picture are transferred to the target block based on the reference position of the reference block. obtained from the decoded image memory step as the predicted value of
For a second divided reference block included in a referenceable area that does not include the upper left position of the reference block, a reference area boundary correction step of setting a predetermined value as a predicted value of the processing target block;
An image encoding program that causes a computer to execute. a block vector candidate derivation unit that derives a block vector candidate for a block to be processed in a picture to be processed from encoding information stored in an encoding information storage memory;
a selection unit that selects a selected block vector from the block vector candidates;
determining a referenceable area including the upper left position of the reference block to be referenced by the selected block vector from the plurality of referenceable areas;
For the first divided reference block included in the referenceable area including the upper left position of the reference block, decoded pixels in the target picture are transferred to the target block based on the reference position of the reference block. obtained from the decoded image memory unit as the predicted value of
a reference area boundary correction unit that sets a predetermined value as a predicted value of the processing target block for a second divided reference block included in a reference possible area that does not include the upper left position of the reference block;
An image decoding device comprising: a block vector candidate deriving step of deriving a block vector candidate for a block to be processed in a picture to be processed from encoding information stored in an encoding information storage memory;
a selection step of selecting a selected block vector from the block vector candidates;
determining a referenceable area including the upper left position of the reference block to be referenced by the selected block vector from the plurality of referenceable areas;
For the first divided reference block included in the referenceable area including the upper left position of the reference block, decoded pixels in the target picture are transferred to the target block based on the reference position of the reference block. obtained from the decoded image memory step as the predicted value of
For a second divided reference block included in a referenceable area that does not include the upper left position of the reference block, a reference area boundary correction step of setting a predetermined value as a predicted value of the processing target block;
An image decoding method comprising: a block vector candidate deriving step of deriving a block vector candidate for a block to be processed in a picture to be processed from encoding information stored in an encoding information storage memory;
a selection step of selecting a selected block vector from the block vector candidates;
determining a referenceable area including the upper left position of the reference block to be referenced by the selected block vector from the plurality of referenceable areas;
For the first divided reference block included in the referenceable area including the upper left position of the reference block, decoded pixels in the target picture are transferred to the target block based on the reference position of the reference block. obtained from the decoded image memory step as the predicted value of
For a second divided reference block included in a referenceable area that does not include the upper left position of the reference block, a reference area boundary correction step of setting a predetermined value as a predicted value of the processing target block;
An image decoding program that causes a computer to execute. A storage method for storing a bitstream encoded by an image encoding method in a recording medium, the image encoding method comprising:
a block vector candidate deriving step of deriving a block vector candidate for a block to be processed in a picture to be processed from encoding information stored in an encoding information storage memory;
a selection step of selecting a selected block vector from the block vector candidates;
determining a referenceable area including the upper left position of the reference block to be referenced by the selected block vector from the plurality of referenceable areas;
For the first divided reference block included in the referenceable area including the upper left position of the reference block, decoded pixels in the target picture are transferred to the target block based on the reference position of the reference block. obtained from the decoded image memory step as the predicted value of
For a second divided reference block included in a referenceable area that does not include the upper left position of the reference block, a reference area boundary correction step of setting a predetermined value as a predicted value of the processing target block;
A storage method comprising: A transmission method for transmitting a bitstream encoded by an image encoding method, the image encoding method comprising:
a block vector candidate deriving step of deriving a block vector candidate for a block to be processed in a picture to be processed from encoding information stored in an encoding information storage memory;
a selection step of selecting a selected block vector from the block vector candidates;
determining a referenceable area including the upper left position of the reference block to be referenced by the selected block vector from the plurality of referenceable areas;
For the first divided reference block included in the referenceable area including the upper left position of the reference block, decoded pixels in the target picture are transferred to the target block based on the reference position of the reference block. obtained from the decoded image memory step as the predicted value of
For a second divided reference block included in a referenceable area that does not include the upper left position of the reference block, a reference area boundary correction step of setting a predetermined value as a predicted value of the processing target block;
A transmission method comprising:

Images