Patent Description:
The present invention relates to Intra coding in image and video coding. In particular, the present invention discloses Intra prediction mode derivation for the Intra derived-mode (DM) coded chroma component of color images or color video to improve the coding efficiency.

The High Efficiency Video Coding (HEVC) standard is developed under the joint video project of the ITU-T Video Coding Experts Group (VCEG) and the ISO/IEC Moving Picture Experts Group (MPEG) standardization organizations, and is especially with partnership known as the Joint Collaborative Team on Video Coding (JCT-VC). In HEVC, one slice is partitioned into multiple coding tree units (CTU). In main profile, the minimum and the maximum sizes of CTU are specified by the syntax elements in the sequence parameter set (SPS). The allowed CTU size can be 8x8, 16x16, 32x32, or 64x64. For each slice, the CTUs within the slice are processed according to a raster scan order.

The CTU is further partitioned into multiple coding units (CU) to adapt to various local characteristics. A quadtree, denoted as the coding tree, is used to partition the CTU into multiple CUs. Let CTU size be MxM, where M is one of the values of <NUM>, <NUM>, or <NUM>. The CTU can be a single CU (i.e., no splitting) or can be split into four smaller units of equal sizes (i.e., M/2xM/<NUM> each), which correspond to the nodes of the coding tree. If units are leaf nodes of the coding tree, the units become CUs. Otherwise, the quadtree splitting process can be iterated until the size for a node reaches a minimum allowed CU size as specified in the SPS (Sequence Parameter Set).

Furthermore, according to HEVC, each CU can be partitioned into one or more prediction units (PU). Coupled with the CU, the PU works as a basic representative block for sharing the prediction information. Inside each PU, the same prediction process is applied and the relevant information is transmitted to the decoder on a PU basis. A CU can be split into one, two or four PUs according to the PU splitting type. HEVC defines eight shapes for splitting a CU into PU, including 2Nx2N, 2NxN, Nx2N, NxN, 2NxnU, 2NxnD, nLx2N and nRx2N partition types. Unlike the CU, the PU may only be split once according to HEVC. The partitions shown in the second row correspond to asymmetric partitions, where the two partitioned parts have different sizes.

The HEVC coding comprises Inter prediction and Intra prediction. For Intra prediction, the generation of Intra prediction includes three parts: Intra smoothing filter, Intra prediction, and Intra gradient filter. At first, a smoothing operation is applied to the reference samples as a pre-processing step before calculating the prediction. This smoothing operation corresponds to applying an FIR-filter with filter weights[<NUM>,<NUM>,<NUM>] >><NUM>, with low-pass characteristics to the samples belonging to the left column and the above row of the current TU (transform unit). The Intra prediction of each TU is produced with the reconstructed samples of neighboring TUs. The samples involved in Intra smoothing are indicated in <FIG>, where block <NUM> corresponds to the current block, line <NUM> corresponds to a horizontal boundary and line <NUM> corresponds to a vertical boundary. Whether this smoothing operation is used is determined by the TU size and the Intra prediction mode. Second, the Intra prediction of current block is derived from neighboring reference samples with a certain Intra prediction mode, and the Intra prediction mode is selected from DC mode, planar mode, and <NUM> directional modes by encoder and signaled in the bitstream. Third, if the Intra prediction mode is DC, horizontal or vertical mode, Intra gradient filter is further applied to the samples at the left and top boundaries of the current TU.

Out of all <NUM> Intra prediction modes in HEVC, three modes are considered as most probable modes (MPM) for predicting the Intra prediction mode in current prediction block. For example, the Intra prediction modes used in the left prediction block and in the above prediction block can be used as candidates of the MPM set. In the case that the Intra prediction modes in two neighboring blocks are identical and both directional, or only one of the two neighboring blocks is available and coded in Intra prediction and at the same time this Intra prediction mode is directional, two neighboring directions immediately next to this direction is also used in MPM. DC mode and Planar mode are also considered in MPM set to fill the available spot in the MPM, especially if the above or top neighboring blocks are not available or not coded in Intra prediction, or the Intra prediction modes in neighboring blocks are not directional. If the Intra prediction mode for current prediction block is one of the modes in the MPM set, <NUM> or <NUM> bins is used to signal which one it is. Otherwise, it is not the same as any entry in the MPM set, it will be coded as a non-MPM mode. There are all-together <NUM> such non-MPM modes and a (<NUM>-bit) fixed length coding method is applied to signal this mode. The <NUM> directions are illustrated in <FIG>. In <FIG>, there are all together <NUM> directional modes, i.e., H, H+<NUM>,. , H+<NUM>, H-<NUM>,. , H-<NUM>, V, V+<NUM>,. , V+<NUM>, V-<NUM>,. This system can be expanded to a general case, where horizontal and vertical modes are represented as H and V modes. For other directional modes, they can be represented either as H+k or V+k modes, where k=±<NUM>, ±<NUM>, etc. For example, if <NUM> directional modes are used as shown in <FIG>, k can be range from ±<NUM> to ±<NUM>.

In some recent development beyond HEVC, additional <NUM> directional modes are used in between the existing <NUM> directional modes, as shown in <FIG>. In this case, there are a total <NUM> modes including directional modes as well as some non-directional modes.

In HEVC, once a directional mode is decided, along the prediction direction, all the pixels in the current block will use the same predictor value. If the predictor falls in between two reconstructed reference sample, a bi-linear filter will be used to calculate the predictor as a weighted average of the two neighboring pixels. For example, the predictor signal P can be derived according to P= [P1*a + P2* (<NUM>-a)]/<NUM>, where P1 and P2 are the two neighboring reconstructed samples, integer a is the distance from the predictor P to P2 with a range between <NUM> and <NUM>, inclusively.

The concept of Intra gradient filter is to utilize the gradient information along the Intra prediction direction to improve the quality of Intra prediction. For the Intra prediction modes from vertical/horizontal directions (v/h) to vertical/horizontal +<NUM> directions (v+<NUM>/h+<NUM>) as shown in <FIG>, the left column/the above row neighboring samples can locate their corresponding references along the Intra prediction direction from the above row/the left column. The gradient calculated with the neighboring samples can be used to improve the Intra prediction. An example for the vertical directional mode is illustrated in <FIG>, where Pij denotes the predictor at row i and column j. AL represents the reconstructed sample at the left-above corner of the current block, while Li represents the reconstructed sample in the left column of the current block. A new predictor is calculated as <MAT> where α is a fraction from <NUM> to <NUM> and is selected according to j, such as α=<NUM>/<NUM> for j = <NUM>, and α=<NUM>/<NUM> for j=<NUM>. P'ij is used as the final predictor. As for the horizontal directional mode, the final predictor P'ij is calculated as <MAT>.

In the above equation, Aj is the reconstructed sample in the above row, which is shown in <FIG>. As for the directional modes v+<NUM>,. , v+<NUM> and h+<NUM>,. , h+<NUM>, Li or Aj first obtains its corresponding reference sample RLi or RAj along the direction of Intra prediction. When RLi or RAj is not located at the position of integer pixel, they are produced by interpolation of integer pixels in the above row or the left column of the current block. The example of v+<NUM>,. , v+<NUM> directional modes is shown in <FIG>. The final predictor P'ij is calculated as <MAT>.

Similar to the vertical directional mode, α is a fraction from <NUM> to <NUM> and is selected according to the direction of Intra prediction and j. As for h+<NUM>,. , h+<NUM> directional modes, the final predictor P'ij is calculated as <MAT> where α is a fraction from <NUM> to <NUM> and is selected according to the direction of Intra prediction and i.

The Intra gradient filter can be applied for all directional modes, i.e., v+<NUM>,. , v+<NUM> and h+<NUM>,. , h+<NUM> in HEVC. However, only when the Intra prediction mode is DC, horizontal or vertical mode, Intra gradient filter is used. If the Intra prediction is DC mode, the samples at the first row and first column are filtered by Intra gradient filter. If the Intra prediction is horizontal mode, then the samples at the first row are filtered by Intra gradient filter. If the Intra prediction is vertical mode, then the samples at the first column are further filtered by Intra gradient filter.

Besides Intra gradient filtering, another method called bi-directional Intra prediction is also proposed to improve the quality of Intra prediction in JCT-VC meetings. For diagonal Intra prediction modes, i.e. v+<NUM>,. , v+<NUM> and h+<NUM>,. , h+<NUM>, a weighted sum of the reconstructed samples of the above row and the reconstructed samples from the left column along the direction is used as the Intra predictor. For example, for v+<NUM>,. , v+<NUM> directional modes, as illustrated in <FIG>, Pij from the neighboring samples of above row has a corresponding reference sample Fij in the left column along the prediction direction. If Fij is not located at the integer pixel position, it can be generated by interpolating integer pixels in the left column. The final predictor P'ij is then calculated as the weighted sum of Pij and Fij as <MAT> where α is a fraction from <NUM> to <NUM> and is selected according to the direction of Intra prediction together with j (for v+<NUM>,. , v+<NUM> directional modes) or i (for h+<NUM>,. , h+<NUM> directional modes).

After generating Intra predictors, the prediction error is further processed by transform and quantization and encoded by entropy coding. For entropy coding, the quantized coefficients are divided into multiple 4x4 coefficient groups, first. The coding order of different coefficient groups and scan order of coefficients in one coefficient group is selected according to Intra prediction mode and transform size. If the transform size is smaller than or equal to 8x8, Intra-mode-dependent scan will be used for the coding order of different coefficient groups and scan order of coefficients in one coefficient group. Otherwise, diagonal scan is used for the coding order of different coefficient groups and scan order of coefficients in one coefficient group.

Also, it is possible to have weighted sum of several predictors to generate the final prediction signal for Intra prediction (namely multiple parameter Intra prediction or MPI). The final predictor PMPI[i, j] of position (i, j) is defined as follows: <MAT> where outside of the block PMPI[i, j] is equal to reconstructed signal as shown in <FIG>, <MAT>.

<FIG> illustrates an example of multiple parameter Intra prediction (MPI) process, where an input block is processed by Arbitrary Directional Intra (ADI) <NUM> followed by MPI <NUM>. The strength of this post-processing (i.e., parameters α + β + γ + δ = <NUM>) is controlled on the CU level and signaled with up to <NUM> bits.

In an ITU-T contribution C1046 (A. Said, etc., "Position dependent Intra prediction combination," ITU-T SG16 COM <NUM> - C1046 -E, Oct. <NUM>), a method is proposed to use a combination of filtered and unfiltered reference samples to form the final predictor p[x, y] as shown in <FIG> for unfiltered (<NUM>) and filtered (<NUM>) cases.

Signals r and s are used to represent the sequences with filtered and unfiltered references. The new prediction p[x, y] combines weighted values of boundary elements r[] with q[x, y] (i.e., predictor derived from filtered samples s[]) as following: <MAT> where <MAT> are stored prediction parameters, d = <NUM> for block sizes up to <NUM>×<NUM>, and d = <NUM> for larger blocks, and <MAT> is a normalization factor.

In the contribution JVET-C-<NUM> (X. Xiu, etc., "Decoder-side Intra mode derivation", JVET-C0061, May, <NUM>), interpolation for Intra prediction using the planar mode is disclosed. According to JVET-C-<NUM>, the sample at bottom-right corner current prediction block is either signaled or estimated using linear average of corresponding left reference sample and above reference sample). Accordingly, samples in the right most column and bottom row are bi-linearly interpolated using the top/bottom-right sample combination and the left/bottom-right sample combination (<NUM>) as shown in <FIG>. The remaining pixels in the prediction block are predicted using similar bi-linear interpolation (<NUM>), as is shown in <FIG>.

In contribution m37524/COM16-C966 (J. , "Block partitioning structure for next generation video coding," MPEG doc. m37524 and ITU-T SG16 Doc. COM16-C966, Oct. <NUM>), a quadtree plus binary tree (QTBT) block partitioning structure is disclosed. According to QTBT, a coding tree block (CTB) is firstly partitioned by a quadtree structure. The quadtree leaf nodes are further partitioned by a binary tree structure. The binary tree leaf nodes, namely coding blocks (CBs), are used for prediction and transform without any further partitioning. For P and B slices, the luma and chroma CTBs in one coding tree unit (CTU) share the same QTBT structure. For I slice, the luma CTB is partitioned into CBs by a QTBT structure, and two chroma CTBs are partitioned into chroma CBs by another QTBT structure.

A CTU (or CTB for I slice), which is the root node of a quadtree, is firstly partitioned by a quadtree, where the quadtree splitting of one node can be iterated until the node reaches the minimum allowed quadtree leaf node size (MinQTSize). If the quadtree leaf node size is not larger than the maximum allowed binary tree root node size (MaxBTSize), it can be further partitioned by a binary tree. The binary tree splitting of one node can be iterated until the node reaches the minimum allowed binary tree leaf node size (MinBTSize) or the maximum allowed binary tree depth (MaxBTDepth). The binary tree leaf node, namely CU (or CB for I slice), will be used for prediction (e.g. Intra-picture or inter-picture prediction) and transform without any further partitioning. There are two splitting types in the binary tree splitting: symmetric horizontal splitting and symmetric vertical splitting.

Block partitioning <NUM> and corresponding QTBT structure <NUM> of <FIG> illustrates an example of block partitioning by using QTBT. The solid lines indicate quadtree splitting and dotted lines indicate binary tree splitting. In each splitting (i.e., non-leaf) node of the binary tree, one flag is signaled to indicate which splitting type (i.e., horizontal or vertical) is used, where <NUM> indicates horizontal splitting and <NUM> indicates vertical splitting. For the quadtree splitting, there is no need to indicate the splitting type since it always splits a block horizontally and vertically into <NUM> sub-blocks of equal size.

In the above disclosure, JVET (joint video exploration team) refers to an international organization that has been established by both ITU-T VCEG and ISO/IEC MPEG to study the next generation video coding technologies. Reference software called JEM (joint exploration model) is built based on HEVC's reference software (HM). Some new video coding methods, including QTBT and <NUM> Intra prediction directions, are included in JEM software.

In the QTBT structure, for the I slice, when a chroma CU is coded using DM mode (derived mode from luma), the CU will use the top left chroma pixel to find the corresponding luma pixel. Accordingly, the Intra mode of the luma block containing that luma pixel is used as the chroma Intra mode.

<FIG> illustrates an example of the derived mode (DM) for a chroma block. In <FIG>, block <NUM> is a chroma block partitioned from a chroma CTB <NUM>. Block <NUM> is a corresponding luma block area within a luma CTB <NUM>. Black pixel <NUM> indicates the upper-left corner pixel of the corresponding luma block area. Since the luma and chroma components may use separate block partitions, there may be no co-located luma block e.g. a luma coding block) for a give chroma block (e.g. a chroma coding block). Therefore, the upper-left pixel <NUM> of the chroma CU will be used to find the corresponding luma CU area based on the upper-left pixel <NUM> of the corresponding luma CU. The corresponding luma CU area <NUM> covers equivalent luma pixel area in the luma image as the chroma block <NUM>. The corresponding luma CU area <NUM> may correspond to one or more luma CUs or partial luma CUs. The luma Intra mode associated with a minimum CU at the upper-left corner position (<NUM>) is used as the chroma Intra mode. In <FIG>, each small square corresponds to a minimum CU, which is the basic unit for encoding and decoding. A CU can be formed by <NUM> to M minimum CU, where M = (maximum CU width / minimum CU width)×( maximum CU height / minimum CU height).

According to the conventional approach, when the derived-mode (DM) is used for a chroma block, the luma Intra mode used by the upper-left minimum CU of the corresponding luma CU area is used as the Intra mode of the associated chroma CU. However, the upper-left minimum CU may not be Intra mode coded and the chroma DM Intra prediction cannot be used. Therefore, the DM coded chroma block may not have a valid luma Intra mode to use.

ZHANG LET AL: "Multiple Direct Modes for chroma intra coding",<NUM>. JVET MEETING; <NUM>-<NUM>-<NUM> - <NUM>-<NUM>-<NUM>; CHENGDU; (THE JOINT VIDEO EXPLORATION TEAM OF ISO/IEC JTC1/SC29/WG11 AND ITU-T SG. <NUM> ), no. JVET-D0111, <NUM> October <NUM> (<NUM>-<NUM>-<NUM>), XP030150356, teaches an extension of the conventional approach in that multiple sub-blocks of the corresponding luma area are checked for their Intra modes in order to build an enlarged list of candidates to be selected for the chroma CU. However, this is only proposed to be done for I slices (i.e. fully Intra coded slices) and there is no explicit teaching provided how to deal with non-intra coded luma sub-blocks for DM mode,.

One of the goals of the present invention is intended to solve this issue.

A method and an apparatus according to the present invention are defined in the independent claims, respectively. The dependent claims define preferred embodiments thereof. Enabling disclosure of the protected invention is provided in the following in the section titled "Chroma DM mode assignment for corresponding non-Intra mode luma block" with the indication of "embodiments of the protected invention". Any further elements, aspects, or embodiments are merely provided for illustrative purposes and do not define the scope of the protected invention.

A method and apparatus for video coding chroma derived-mode Intra prediction are disclosed. According to one method, if derived-mode (DM) Intra prediction is selected for a current chroma block, a corresponding luma block area is determined by locating a first upper-left pixel address of the corresponding luma block area corresponding to a second upper-left pixel address of the current chroma block, wherein the corresponding luma block area corresponds to a same area as the current chroma block in the current color image; one or more candidate luma coding modes are determined from a sub-block set consisting of one.

or more sub-blocks of the corresponding luma block area, and wherein if the sub-block set consists of only one sub-block, the sub-block set excludes a corner sub-block located at a top left (TL) corner of the corresponding luma block area; a current chroma Intra mode for the current chroma block is derived based on information comprising said one or more candidate luma coding modes; and Intra-prediction encoding or decoding is applied to the current chroma block using the current chroma Intra mode derived.

The current chroma block may correspond to one chroma coding unit (CU) and the corresponding luma block area corresponds to one luma coding unit (CU). Each sub-block of the corresponding luma block area may correspond to one smallest luma coding unit (CU).

The step of determining one or more candidate luma coding modes comprises checking one or more luma coding modes associated with n sub-blocks of the sub-block set one by one until a checked luma coding mode is Intra angular mode, DC mode or planar mode and using the checked luma coding mode as the current chroma Intra mode, where n is a positive integer. The n sub-blocks of the sub-block set can be checked one by one according to a selected order. In one embodiment, if none of the luma coding modes associated with the n sub-blocks of the sub-block set is the Intra angular mode, DC mode or planar mode, the step of determining one or more candidate luma coding modes comprises selecting a default Intra mode as the current chroma Intra mode. The default Intra mode can be signaled at Sequence Parameter Set (SPS), or Picture Parameter Set (PPS), or slice header. The default Intra mode may correspond to planar mode, DC mode, vertical mode or horizontal mode. The default Intra mode may also be derived from one or more candidate chroma Intra modes associated with one or more candidate neighboring chroma blocks of the current chroma block. For example, the candidate neighboring chroma blocks of the current chroma block consists of neighboring chroma blocks located at above left (AL), above (A), above right (AR), left (L) or below left (BL) of the current chroma block. A most frequently used mode among the candidate chroma Intra modes can be selected as the current chroma Intra mode. In another embodiment, if none of the luma coding modes associated with the n sub-blocks of the sub-block set is the Intra angular mode, DC mode or planar mode, the derived-mode (DM) Intra prediction can be considered as unavailable to the current chroma Intra mode.

In one embodiment, the sub-block set consists of four corner sub-blocks located at a top left (TL) corner, a top right (TR) corner, a bottom left (BL) corner and bottom right (BR) corner. In another embodiment, the sub-block set consists of four middle sub-blocks located adjacent to a middle position of the corresponding luma block area, and the four middle sub-blocks consist of an upper left middle sub-block (M1), an upper right middle sub-block (M2), a lower left middle sub-block (M3) and a lower right middle sub-block (M4). In yet another embodiment, the sub-block set consists of four corner sub-blocks and four middle sub-blocks of the corresponding luma block area.

As mentioned before, in the reference software called JEM (joint exploration model) based on HEVC reference software (HM), a chroma CU may use DM mode (derived mode from the corresponding luma component) by copying the Intra mode of a corresponding luma CU. However, it is possible that the corresponding luma block is non-Intra coded, such as IBC mode, palette mode, Inter mode or a mode rather than DC, planar or angular mode. Therefore, this would leave the chroma Intra mode undefined. Accordingly, various methods to overcome this issue are disclosed in the present invention.

In the embodiments of the protected invention, a chroma DM mode is specified when the corresponding luma block is non-Intra coded. The non-Intra mode refers to any mode other than an angular mode, DC mode or planar mode. Accordingly, the present invention is able to handle the case that chroma plane and luma plane are coded separately and have different block partitioning structures, and the corresponding luma block of the chroma block may be non-Intra coded, such as IBC mode, palette mode, PCM mode, Inter mode, etc..

According to this method, a corresponding luma block area for the chroma block will be identified first based on the top-left chroma pixel address. The meaning of the "corresponding luma block area" has been described in the background section of the present disclosure. This luma block address will be treated as the start of a luma block. When the video color format is <NUM>, the width of this luma block is <NUM>×width_chroma and the height of this luma CU is 2x height_chroma, where width_chroma is the width and height chroma is the height of the current chroma. In other words, the corresponding luma block area is twice as wide and twice as high as the chroma block when the video color format is <NUM>. When the video color format is <NUM>, the width of this luma block is <NUM>×width_chroma and the height of this luma block is equal to height_chroma. In other words, the corresponding luma block area is twice as wide and has the same height as the chroma block when the video color format is <NUM>. When the video color format is <NUM>, the width of this luma block is equal to width_chroma and the height of this luma block is equal to height_chroma. In other words, the corresponding luma block area has the same width and height as the chroma block when the video color format is <NUM>.

For each corresponding luma block area (e.g. luma CU/PU/TU), there are four corner luma minimum blocks, including the top left minimum luma block (TL), top right minimum luma block (TR), bottom left minimum luma block (BL) and bottom right minimum luma block (BR). The minimum block or smallest block is also referred as a sub-block in this disclosure. <FIG> illustrates an example of four luma minimum blocks in the four corners, where block <NUM> corresponds to a luma CTB and block <NUM> corresponds to a luma CU, PU or TU area.

There are four middle minimum blocks (i.e., sub-blocks) as indicated by M1, M2, M3 and M4 as shown in <FIG>. The upper left middle minimum block is designated as M1, the upper right minimum block is designated as M2, the lower left minimum block is designated as M3 and the lower right minimum block is designated as M4. There are N minimum blocks for each row and K minimum blocks for each column for the corresponding luma block, where N and K are determined according to:.

Mlis the minimum block that has a distance of (N/<NUM> -<NUM>) minimum blocks from the CB above boundary, and a distance of (M/<NUM> - <NUM>) minimum blocks from the CB left boundary.

M2 is the minimum block that has a distance of N/<NUM> minimum blocks from the CB above boundary, and a distance of (M/<NUM> - <NUM>) minimum blocks from the CB left boundary.

M3 is the minimum block that has a distance of (N/<NUM> -<NUM>) minimum blocks from the CB above boundary, and a distance of M/<NUM> minimum blocks from the CB left boundary.

M4 is the minimum block that has a distance of N/<NUM> minimum block from the CB above boundary, and a distance of M/<NUM> minimum block from the CB left boundary.

In one method, the encoder and decoder will check n positions among the <NUM> positions (i.e., TL, TR, BL, BR, M1, M2, M3, M4), where n can be <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>. After n is decided, the encoder and decoder can choose any n positions from those eight positions. For example, if n is <NUM>, the encoder, the decoder can choose the four positions corresponding to TL, TR, BL and BR. Alternatively, the encoder and decoder can choose the four positions corresponding to M1, M2, M3 and M4. The encoder and decoder can check these n positions one by one until one of them is Intra angular mode, DC mode or planar mode coded. If none of these modes is angular mode, DC mode, or planar mode, a default Intra mode is padded for this chroma block according to an embodiment of the present invention. The default Intra mode can be specified as described in a later part of this disclosure. The order of selecting these n modes can have many variants.

In another embodiment, when the chroma Intra mode is DM mode, the encoder and decoder will check TL, TR, BL, BR, M1, M2, M3, M4 positions one by one until one of them is Intra angular mode, DC mode, or planar mode coded. The Intra mode of the corresponding luma block will be used to for the chroma block. If none of them is Intra angular mode, DC mode, or planar mode coded, a default Intra mode will be used for the chroma block. The default Intra mode will be described in a later part of this disclosure. Note that the check order of these blocks can have many variants. For example, the encoder and decoder can check TL, M1, M2, M3, M4, TR, BL and BR positions in order. In another example, the encoder and decoder can check M4, TL, TR, BL, BR, M3, M2 and M1 positions in order.

In yet another embodiment, when the chroma Intra mode is DM mode, the encoder and decoder will check TL, M2, M3, M4 positions one by one until one of them is Intra angular mode, DC mode or planar mode coded. The Intra mode of the corresponding block will be used for the chroma block. If none of them is Intra angular mode, DC mode or planar mode coded, a default Intra mode will be used for the chroma block. The default Intra mode will be described in a later part of this disclosure. Note that the check order of these blocks can have many variants. For example, the encoder and decoder can check TL, M4, M2, M3 positions in order. In another example, the encoder and decoder can check M4, TL, M3 M2 positions in order.

In yet another embodiment, when the chroma Intra mode is DM mode, the encoder and decoder will check TL, TR, BL, BR and M4 positions one by one until one of them is Intra angular mode, DC mode, or planar mode coded. The Intra mode of the corresponding block will be used for the chroma block. If none of them is Intra angular mode, DC mode, or planar mode coded, a default Intra mode will be used for he chroma block. The default Intra mode will be described in a later part of this disclosure. Note that the check order of these blocks can have many variants.

In yet another method, when the chroma Intra mode is DM mode, the encoder and decoder will check n positions among the eight positions (i.e., TL, TR, BL, BR, M1, M2, M3, M4), where n can be <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> or <NUM>. After n is decided, the encoder and decoder can choose any n positions from those eight positions. For example, if n is <NUM>, the encoder and decoder can choose the four positions corresponding to TL, TR, BL and BR. Alternatively, the encoder and decoder can choose the four positions corresponding to M1, M2, M3 and M4. The encoder and decoder can check all these n positions one by one. The encoder and decoder can choose the most frequently used luma Intra mode for the chroma block coded in DM mode. When none of these positions is Intra angular mode, DC mode, or planar mode coded, a default Intra mode is padded for this chroma block. The default Intra mode will be described in a later part of this disclosure. The order of these n modes can have many variants.

In yet another method, when the chroma Intra mode is DM mode, the encoder and decoder will check n positions among the eight positions (i.e., TL, TR, BL, BR, M1, M2, M3, M4), n can be <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> or <NUM>. After n is decided, the encoder and decoder can choose any n positions from those eight positions. For example, if n is <NUM>, the encoder and decoder can choose the four positions corresponding to TL, TR, BL and BR. Alternatively, the encoder and decoder can choose the four positions corresponding to M1, M2, M3 and M4. The encoder and decoder can choose these n modes one by one until one of them is Intra angular mode, DC mode, or planar mode coded. If none of these positions is Intra angular mode, DC mode, or planar mode coded, the DM mode is treated ass unavailable for the current chroma block. The chroma Intra mode list can be shortened by <NUM>, and the corresponding code word will be changed. The order of these n modes can have many variants.

In yet another method, when the chroma Intra mode is DM mode, the encoder and decoder will check n positions among the eight positions (i.e., TL, TR, BL, BR, M1, M2, M3, M4), n can be <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> or <NUM>. After n is decided, the encoder and decoder can choose any n positions from those eight positions. For example, when n is <NUM>, the encoder and decoder can choose the four positions corresponding to TL, TR, BL and BR. Alternatively, the encoder and decoder can choose the four positions corresponding to M1, M2, M3 and M4. The encoder and decoder can check these n positions one by one. The encoder and decoder can choose the Intra angular mode, DC mode, or planar mode that is used most frequently as the luma Intra mode for the chroma block coded in DM mode. If none of these positions is Intra angular mode, DC mode, or planar mode coded, the DM mode is treated as unavailable for the current chroma block. The chroma Intra mode list can be shortened by <NUM>, and the corresponding code word will be changed.

In one method, the default mode can be a pre-defined Intra mode. This Intra mode can be hard coded for the encoder and decoder. This Intra mode can also be signaled at Sequence Parameter Set (SPS), or Picture Parameter Set (PPS), or slice header.

For example, the default mode can be planar mode, DC mode, vertical mode or horizontal mode.

In another method, that does not fall within the scope of the protected invention, the default mode can be derived for each chroma block from its neighboring blocks The chroma block can check the Intra mode of neighboring blocks located at above left (AL), above (A), above right (AR), left (L) or below left (BL) of the current block and find the most frequently used one as the Intra mode for current block. An example of the neighboring blocks of the current block is shown in <FIG>.

In a third method, that does not fall within the scope of the protected invention, the first available Intra angular mode, DC mode or planar mode from neighboring blocks is used as the Intra mode for current block. The ordering of candidate neighboring blocks can be different; some examples are listed as follows:.

In all the above, the order of L and A can be swapped or the order of AR and BL can be swapped. In another example, the same order of neighboring locations in inter mode motion vector predictor candidate list (spatial candidates) can be used. In yet another example, the same order of neighboring locations in inter mode merge candidate list (spatial candidates) can be used.

In the <NUM>nd VCEG meeting, Adaptive motion vector resolution (AMVR) is disclosed in VCEG-AZ07 (<NPL>). According to AMVR, Motion Vector Difference (MVD) between the current motion vector and a predicted motion vector of a PU can be coded with either quarter-pel resolution or integer-pel resolution. The MVD resolution is controlled at coding unit (CU) level and an integer MVD resolution flag is conditionally signaled for each CU that has at least one non-zero MVD components.

When the integer MVD resolution flag is false (i.e., indicating integer resolution not used) or not coded for a CU, the default quarter-pel MV resolution is used for all PUs belonging to the CU. Otherwise (i.e., the integer MV resolution flag being true for a CU), all PUs coded with AMVP (advanced motion vector prediction) mode belonging to the CU use integer MV resolution, while the PUs coded with merge mode still use quarter-pel MV resolution. When a PU uses integer MV resolution, the AMVP candidate list is filled with integer MV by rounding quarter-pel MVs to integer-pel MVs.

In the JEM3. <NUM>, QTBT structure is enabled so that CU is equal to PU and TU (i.e., CU=PU=TU). Also, AMVR is enabled for every CU. In this case, some of the sub-blocks may share the same MV resolution. However, these blocks have their individual flags to signal AMVR. This may introduce extra signaling overhead. In the following, various approaches to reduce the required signaling are disclosed.

In order to reduce the signaling overhead, the current invention propose to signal the AMVR_signal_BT_flag at a certain BT depth (e.g. MIN_BT_DEPTH_SIGNAL_AMVR) when the binary partition is used. The sub-blocks of that binary partition share the same AMVR flag from the parent binary partition. In other words, the binary block with a depth greater than MIN_BT_DEPTH_SIGNAL_AMVR shares the AMVR flag at MIN_BT_DEPTH_SIGNAL_AMVR. The binary block with a depth smaller than MIN_BT_DEPTH_SIGNAL_AMVR signals its own AMVR flag. When the AMVR flag at the MIN_BT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub blocks use integer MV resolution. When the AMVR flag at the MIN_BT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub blocks use quarter-pel MV resolution. An example if the binary table of this AMVR_signal_BT_flag is illustrated in Table <NUM>.

The MIN_BT_DEPTH_SIGNAL_AMVR is smaller than or equal to MaxBTSize. It can be <NUM>, <NUM>, <NUM>, <NUM>,. ,MaxBTSize. The MIN_BT_DEPTH_SIGNAL_AMVR can be defined in the encoder and decoder macro or signaled at SPS, PPS or slice header.

In one example, MIN_BT_DEPTH_SIGNAL_AMVR corresponds to BT depth <NUM>, which means a leaf of the QT and the sub-blocks are binary partition.

In another example, the MIN_BT_DEPTH_SIGNAL_AMVR corresponds to BT depth <NUM>, which means the first layer of binary partition. Therefore, when the current block is quad-tree partitioned, the flag will always be signaled. It is illustrated in <FIG>, where the AMVR flag is signaled when the BT depth is smaller than <NUM>.

In <FIG>, the dashed-lines block <NUM> is the BT with BT depth equal to <NUM>, so that the AMVR flag will be signaled for this level. When the BT depth is smaller than <NUM>, the MV resolution is indicated by the AMVR flag at BT depth <NUM>. In other words, the AMVR flag is only signaled for the CU without partition.

In another embodiment, an AMVR_signal_BT_flag is signaled at a certain BT depth (e.g. MIN_BT_DEPTH_SIGNAL_AMVR) when it is binary partitioned. When the AMVR_signal_BT_flag at the MIN_BT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks use integer MV resolution. When the AMVR_signal_BT_flag at the MIN_BT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks use quarter-pel MV resolution. When the AMVR_signal_BT_flag at the MIN_BT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks will signal its own AMVR flag. The AMVR_signa_BT_flag can use fixed-length binarization, variable length binarization, Exp-Golomb-k binarization or truncated binarization. Table <NUM> shows an example of Exp-Golomb-k code word, where k is equal to <NUM>.

For example, MIN_BT_DEPTH_SIGNAL_AMVR can be smaller than or equal to MaxBTSize. It can be <NUM>, <NUM>, <NUM>, <NUM>,. ,MaxBTSize. The MIN_BT_DEPTH_SIGNAL_AMVR can be defined in the encoder and decoder macro or signaled at SPS, PPS or slice header.

In one example, the MIN_BT_DEPTH_SIGNAL_AMVR corresponds to BT depth <NUM>, which means a leaf of the QT and the sub-blocks are binary partitioned.

In another example, the MIN_BT_DEPTH_SIGNAL_AMVR corresponds to BT depth <NUM>, which means the first layer of binary partitioned. Therefore, when the current block is quadtree partitioned, the flag will always be signaled.

In another embodiment, an AMVR_signal_BT_flag is signaled at a certain BT depth (e.g. MIN_BT_DEPTH_SIGNAL_AMVR ) when it is binary partitioned. When the AMVR_signal_BT_flag at the MIN_BT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks signal its own AMVR flag. When the AMVR_signal_BT_flag at the MIN_BT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks use quarter-pel MV resolution. An example of the binary table of this AMVR_signal_BT_flag is illustrated in Table <NUM>.

In one example, the MIN_BT_DEPTH_SIGNAL_AMVR_corresponds to BT depth <NUM>, which means a leaf of the QT, and the sub-blocks are binary partitioned.

In another example, the MIN_BT_DEPTH_SIGNAL_AMVR corresponds to BT depth <NUM>, which means the first layer of Binary partition. Therefore, when the current block is quadtree partitioned, the flag will always be signaled.

In another embodiment, an AMVR_signal_BT_flag is signaled at a certain BT depth (e.g. MIN_BT_DEPTH_SIGNAL_AMVR ) when it is binary partitioned. When the AMVR_signal_BT_flag at the MIN_BT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks signal its own AMVR flag. When the AMVR_signal_BT_flag at the MIN_BT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks use integer pel MV resolution. An example of the binary table of this AMVR_signal_BT_flag is illustrated in Table <NUM>.

In one example, the MIN_BT_DEPTH_SIGNAL_AMVR corresponds to BT depth <NUM>, which means a leaf of the QT and the sub-blocks are Binary partitioned.

In the proposed method, an AMVR_signal_QT_flag is signalled at a certain QT depth (e.g. MIN_QT_DEPTH_SIGNAL_AMVR ) when it is binary partitioned. When the AMVR_signal_QT_flag at the MIN_QT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks use integer MV resolution. When the AMVR_signal_QT_flag at the MIN_QT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks use quarter-pel MV resolution. When the AMVR_signal_QT_flag at the MIN_QT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks will signal its own AMVR flag. Table <NUM> illustrates an example of Exp-Golomb-k, where k is equal to <NUM>.

The MIN_QT_DEPTH_SIGNAL_AMVR is smaller than or equal to MaxQTSize. It can be <NUM>, <NUM>, <NUM>, <NUM>,. ,MaxQTSize. The MIN_QT_DEPTH_SIGNAL_AMVR can be defined in the encoder and decoder macro or signaled at SPS, PPS or slice header.

In another embodiment, an AMVR_signal_QT_flag is signaled at a certain QT depth (e. MIN_QT_DEPTH_SIGNAL_AMVR ) when it is binary partitioned. When the AMVR_signal_QT_flag at the MIN_QT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks use integer MV resolution. When the AMVR_signal_QT_flag at the MIN_QT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks use quarter-pel MV resolution. Table <NUM> shows an example of Exp-Golomb-k, where k is equal to <NUM>.

The MIN_QT_DEPTH_SIGNAL_AMVR is smaller than or equal to MaxQTSize. It can be <NUM>, <NUM>, <NUM>, <NUM>,. ,MaxQTSize. The MIN_QT_DEPTH_SIGNAL_AMVR can be defined in the encoder and decoder macro or signaled at SPS, PPS or slice header.

In another embodiment, an AMVR_signal_QT_flag is signaled at a certain QT depth (e. MIN_QT_DEPTH_SIGNAL_AMVR ) when it is binary partitioned. When the AMVR_signal_QT_flag at the MIN_QT_DEPTH_SIGNAL_AMVR_is <NUM>, all the sub-blocks signal its own AMVR flag. When the AMVR_signal_QT_flag at the MIN_QT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks use quarter-pel MV resolution. Table <NUM> shown an example of Exp-Golomb-k, where k is equal to <NUM>.

In another embodiment, an AMVR_signal_QT_flag is signaled at a certain QT depth (e. MIN_QT_DEPTH_SIGNAL_AMVR ) when it is binary partitioned. When the AMVR_signal_QT_flag at the MIN_QT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks use integer MV resolution. When the AMVR_signal_QT_flag at the MIN_QT_DEPTH_SIGNAL_AMVR is <NUM>, all the sub-blocks signal its own AMVR flag. Table <NUM> illustrates an example of Exp-Golomb-k, where k is equal to <NUM>.

The inventions disclosed above can be incorporated into various video encoding or decoding systems in various forms. For example, the inventions can be implemented using hardware-based approaches, such as dedicated integrated circuits (IC), field programmable logic array (FPGA), digital signal processor (DSP), central processing unit (CPU), etc. The inventions can also be implemented using software codes or firmware codes executable on a computer, laptop or mobile device such as smart phones. Furthermore, the software codes or firmware codes can be executable on a mixed-type platform such as a CPU with dedicated processors (e.g. video coding engine or co-processor).

Claim 1:
A method of video encoding or decoding used by a video encoding system or video decoding system respectively, the method comprising:
receiving input data associated with a current chroma block (<NUM>) in a current color image;
when deriving, in Intra derived-mode, DM, a current chroma Intra mode for the current chroma block (<NUM>)
determining a corresponding luma coding mode by locating at least one predefined pixel address (TL, TR, BL, BR, M1, M2, M3, M4) within a corresponding luma block area (<NUM>, <NUM>) based on an upper-left pixel address (<NUM>) of the current chroma block (<NUM>) and by using a luma coding mode at one of the at least one predefined pixel addresses within the corresponding luma block area (<NUM>, <NUM>) as the corresponding luma coding mode, wherein an upper-left pixel address (<NUM>) of the corresponding luma block area (<NUM>, <NUM>) refers to a same position as the upper-left pixel address (<NUM>) of the current chroma block (<NUM>); and
applying Intra-prediction encoding or decoding to the current chroma block (<NUM>) using the current chroma Intra mode derived by:
determining whether said luma coding mode is palette mode or Intra block copy, IBC, mode or any coding mode not using an Intra angular mode, DC mode or planar mode; and
specifying a default Intra mode as the current chroma Intra mode if said luma coding mode is palette mode or IBC mode or any coding mode not using an Intra angular mode, DC mode or planar mode.