WO2016008409A1 - Method of temporal derived bi-directional motion vector for motion vector prediction - Google Patents
Method of temporal derived bi-directional motion vector for motion vector prediction Download PDFInfo
- Publication number
- WO2016008409A1 WO2016008409A1 PCT/CN2015/084043 CN2015084043W WO2016008409A1 WO 2016008409 A1 WO2016008409 A1 WO 2016008409A1 CN 2015084043 W CN2015084043 W CN 2015084043W WO 2016008409 A1 WO2016008409 A1 WO 2016008409A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- motion vector
- temporal
- block
- temporal derived
- current block
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N19/00—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
- H04N19/50—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using predictive coding
- H04N19/503—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using predictive coding involving temporal prediction
- H04N19/51—Motion estimation or motion compensation
- H04N19/577—Motion compensation with bidirectional frame interpolation, i.e. using B-pictures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N19/00—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
- H04N19/50—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using predictive coding
- H04N19/503—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using predictive coding involving temporal prediction
- H04N19/51—Motion estimation or motion compensation
- H04N19/513—Processing of motion vectors
- H04N19/517—Processing of motion vectors by encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N19/00—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
- H04N19/50—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using predictive coding
- H04N19/503—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals using predictive coding involving temporal prediction
- H04N19/51—Motion estimation or motion compensation
- H04N19/513—Processing of motion vectors
- H04N19/517—Processing of motion vectors by encoding
- H04N19/52—Processing of motion vectors by encoding by predictive encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N19/00—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
- H04N19/70—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals characterised by syntax aspects related to video coding, e.g. related to compression standards
Definitions
- the present invention relates to video coding.
- the present invention relates to deriving bi-direction motion vector from a uni-directional motion vector for a motion vector prediction.
- Motion estimation is an effective inter-frame coding technique to exploit temporal redundancy in video sequences.
- Motion-compensated inter-frame coding has been widely used in various international video coding standards.
- the motion estimation adopted in various coding standards is often a block-based technique, where motion information such as coding mode and motion vector is determined for each macroblock or similar block configuration.
- MCP motion compensation prediction
- MV motion vector
- the motion vector is signaled to the decoder.
- two reference blocks i.e. bi-directional prediction
- two motion vectors are signaled.
- the inter-predicted or intra-predicted residues are usually further processed by transformation, quantization, and entropy coding to generate compressed video bitstream.
- MVP motion vector predictor
- HEVC High Efficiency Video Coding
- a method and apparatus of deriving a temporal derived motion vector in a second direction based on a given motion vector in a first direction for motion vector prediction are disclosed.
- a given motion vector for a current block is determined, where the given motion vector points from the current block in a first direction.
- a reference motion vector associated with a first reference block in a first reference frame is identified.
- a temporal derived motion vector is derived.
- the temporal derived motion vector points from the current block to a second reference block in a second reference frame in a second direction different from the first direction.
- the temporal derived motion vector is then used as one predictor for encoding or decoding of the motion vector of the current block.
- the first reference block in the first reference frame can be located by shifting a corresponding center, top-left or other position of the current block by the given motion vector.
- the given motion vector for the current block can be determined based on the motion vector of a spatial or temporal neighboring block of the current block.
- the temporal derived motion vector can be determined according to the sum of the given motion vector and the reference motion vector.
- the given motion vector points to another reference frame different from the first reference frame
- the given motion vector is scaled to point to the first reference frame.
- the reference motion vector points to another reference frame different from the second reference frame
- the reference motion vector can be scaled to point to the second reference frame.
- the temporal derived motion vector points to another reference frame different from the second reference frame
- the temporal derived motion vector can be scaled to point to the second reference frame.
- one or more coding parameters are checked to determine whether the reference motion vector is valid or not.
- the reference motion vector is used to derive the temporal derived motion vector only if the reference motion vector is valid. For example, the reference motion vector is invalid if the second reference block is skip mode or merge mode, or coded block flag (cbf) of the second reference block is zero.
- the temporal derived motion vector is used in merge mode.
- One or more temporal derived motion vectors can be generated for adding to the merge candidate list and each temporal derived motion vector is derived using one motion vector in an original merge candidate list as one given motion vector. Redundancy checking can be applied to the temporal derived motion vectors, and any redundant temporal derived motion vector is not added to the merge candidate list.
- the temporal derived motion vectors can be placed at a pre-defined position of the merge candidate list. For example, the temporal derived motion vectors can be placed in the merge candidate list after all spatial and temporal merge candidates and a number of said one or more temporal derived motion vectors allowed to add to the merge candidate list depends on a maximum size of the merge candidate list.
- the temporal derived motion vector is used in AMVP (advanced motion vector prediction) mode.
- AMVP advanced motion vector prediction
- one or more temporal derived motion vectors can be generated for adding to an AMVP merge candidate list and each temporal derived motion vector is derived using one motion vector in an original AMVP candidate list as one given motion vector.
- the temporal derived motion vector for motion vector prediction can be applied adaptively by using one or more syntax elements to indicate whether to enable the temporal derived motion vector for motion vector prediction.
- the syntax elements can be explicitly signaled in a sequence level, video level, picture level or slice level. Whether to use the temporal derived motion vector for motion vector prediction can also be determined at a decoder side implicitly. For example, the decision can be made according to mode selections, motion parameters of neighboring coded blocks of the current block, or motion parameters of the first reference block, the second reference block or both.
- Fig. 1 illustrates an example of temporal-derived bi-direction (TDB) motion vector predictor (MVP) , where MV0 represents a given motion vector of the current block in one direction, MV01 represents a reference motion vector, and MV1 represents the TDB MVP.
- TDB temporal-derived bi-direction
- Fig. 2 illustrates an exemplary flowchart for a video coding system incorporating temporal-derived bi-direction (TDB) motion vector predictor (MVP) according to an embodiment of the present invention.
- TDB temporal-derived bi-direction
- MVP motion vector predictor
- the present invention derives additional temporal motion vector (also referred to as “temporal derived motion vector (MV) ” ) based on a given motion vector to form bi-directional motion vector predictors (MVPs) for a current block.
- MVP may refer to motion vector prediction or motion vector predictor depending on related context.
- Fig. 1 illustrates an example of temporal-derived bi-direction (TDB) motion vector predictor (MVP) .
- Motion vector MV0 represents the motion vector of the current block (122) of the current frame (120) in one direction. As shown in Fig. 1, motion vector MV0 points to a reference block (112) in reference frame (110) .
- Motion vector MV01 of reference block (112) points to another reference block (132) in another reference frame (130) corresponding to another direction.
- Motion vector MV01 along with the motion vector MV0 is used to derive a new motion vector MV1 for current block in the other direction.
- the two MVs i.e., MV0 and MV1 form a bi-directional motion vector predictor for the current block.
- the location of the reference block (112) in the reference frame can be located by shifting the corresponding center, top-left or any other position of the current block (122) by the MV0.
- motion vector MV0 may correspond to the MV of a previously coded block. Therefore, motion vector MV0 may be derived from a spatial or temporal neighboring block of the current block (122) according to the present invention. Furthermore, in MVP-based coding, differential coding may be used to reduce required data for coding the motion vector, where the difference between the current MV and the MVP is coded. Accordingly, motion vector MV0 may be signaled by differential coding.
- the derived MV1 can be obtained by adding MV0 and MV01, i.e.
- MV1 MV0+MV01.
- motion vector MV0 points to a reference frame different from the first target reference frame (e.g. reference frame 110)
- motion vector MV0 can be scaled accordingly according to one embodiment of the present invention.
- Various motion vector scaling techniques are known in the art. For example, temporal motion vector scaling can be performed according to picture order count (POC) .
- POC picture order count
- motion vector MV1 points to a reference frame different from the second target reference frame (e.g. reference frame 130)
- motion vector MV1 can be scaled accordingly according to one embodiment of the present invention.
- motion vector MV01 points to a reference frame different from the second target reference frame (e.g. reference frame 130)
- motion vector MV01 can be scaled accordingly according to one embodiment of the present invention.
- the first and second target reference frames are, for example, the predetermined reference frames associated with the current block (122) .
- Some coding parameters or conditions may also be checked to determine whether the reference motion vector (i.e., MV01) is valid. If motion vector MV01 is not valid, the TDB MVP may be skipped or other alternative procedure is applied. For example, the condition corresponding to whether the reference block (132) is coded in skip mode or merge mode or whether the coded block flag (cbf) of the reference block (132) is zero can be checked to determine whether motion vector MV01 is valid. If any of the above condition is true, motion vector MV01 is invalid.
- the TDB motion vector predictor can be applied in different MVP scenario.
- the TDB MVP can be used as a candidate in the merge mode in HEVC.
- motion vector from each of the spatial candidate can be used as the given MV (i.e., MV0) .
- the TDB MVP can be added to the merge candidate list as an additional candidate, namely TDB merge candidate.
- motion vector from each of the temporal merge candidate can also be used as the given MV (i.e., MV0) .
- the TDB MVP is added to the merge candidate list as a TDB candidate.
- a redundancy checking process can be used to check whether the TDB merge candidate is the same as any candidate already in the merge candidate list. If so, the TDB merge candidate is redundant and is not added.
- the merge candidates in the merge candidate list are placed in the list according to certain orders.
- Each merge candidate can be identified by an index. If the TDB merge candidate is generated for each MV in the merge candidate list (i.e., the original merge candidate list before adding any the TDB merge candidate) , multiple TDB merge candidates may be generated for multiple MVs in the original merge candidate list.
- the TDB merge candidate or candidate are placed at a pre-defined position in the list. In another embodiment, the TDB merge candidate or candidate can be placed after the spatial and temporal merge candidate.
- the number of the TDB merge candidates that can be added to the merge candidate list can be determined by the maximum size of merge candidate list and the number of existing merge candidates.
- TDB MVP for a merge candidate is applied adaptively.
- a syntax element may be used to indicate whether uni-directional or bi-directional merge candidate is used for deriving the corresponding merge candidate.
- whether to add the TDB merge candidate may depend on the reference lists associated with the two reference frames (i.e., reference frames 110 and 130 in Fig. 1) . For example, if the two reference lists are the identical, the TDB merge candidate will not be added. Otherwise, the TDB merge candidate will be added.
- the TDB MVP can be used as a candidate in the AMVP (advanced motion vector prediction) mode in HEVC.
- motion vector MV0 can be derived from the MV in AMVP candidate list.
- the TDB MVP process can be used to derive motion vector MV1 and the TDB MVP is added to the AMVP candidate list in the other direction.
- the TDB MVP can be used as the MV in the other direction without signaling MVD.
- one or more syntax elements are used to signal whether the bi-directional motion vector predictor is used.
- the syntax elements can be explicitly transmitted in the sequence, video, picture or slice level, such as SPS (sequence parameter set) , VPS (video parameter set) , PPS (picture parameter set) , APS (adaptation parameter set) or slice header.
- the information regarding whether the bi-directional motion vector predictor is used for merge or AMVP candidate list can be derived implicitly at the decoder side. The information can be derived implicitly at the decoder side according to mode selections or motion parameters of the neighboring coded blocks of the current block (122) , or according to the motion parameters of the reference block (112) and/or the reference block (132) .
- Fig. 2 illustrates an exemplary flowchart for a video coding system incorporating temporal-derived bi-direction (TDB) motion vector predictor (MVP) according to an embodiment of the present invention.
- a given motion vector for a current block is determined, wherein the given motion vector points from the current block in a first direction as shown in step 210.
- a reference motion vector associated with a first reference block in a first reference frame is identified in step 220.
- a temporal derived motion vector is determined in step 230, where the temporal derived motion vector points from the current block to a second reference block in a second reference frame in a second direction different from the first direction.
- the temporal derived motion vector is then used as one predictor for encoding or decoding the current motion vector of the current block in step 240.
- Fig. 2 The exemplary flowchart shown in Fig. 2 is for illustration purpose. A skilled person in the art may re-arrange, combine steps or split a step to practice the present invention without departing from the spirit of the present invention.
- Embodiment of the present invention as described above may be implemented in various hardware, software codes, or a combination of both.
- an embodiment of the present invention can be one or more electronic circuits integrated into a video compression chip or program code integrated into video compression software to perform the processing described herein.
- An embodiment of the present invention may also be program code to be executed on a Digital Signal Processor (DSP) to perform the processing described herein.
- DSP Digital Signal Processor
- the invention may also involve a number of functions to be performed by a computer processor, a digital signal processor, a microprocessor, or field programmable gate array (FPGA) .
- These processors can be configured to perform particular tasks according to the invention, by executing machine-readable software code or firmware code that defines the particular methods embodied by the invention.
- the software code or firmware code may be developed in different programming languages and different formats or styles.
- the software code may also be compiled for different target platforms.
- different code formats, styles and languages of software codes and other means of configuring code to perform the tasks in accordance with the invention will not depart from the spirit and scope of the invention.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Compression Or Coding Systems Of Tv Signals (AREA)
Abstract
Description
Claims (21)
- A method of motion vector prediction, the method comprising:determining a given motion vector for a current block, wherein the given motion vector points from the current block in a first direction;identifying a reference motion vector associated with a first reference block in a first reference frame;deriving, based on the reference motion vector and the given motion vector, a temporal derived motion vector pointing from the current block to a second reference block in a second reference frame in a second direction different from the first direction; andencoding or decoding a current motion vector of the current block using the temporal derived motion vector as one predictor.
- The method of Claim 1, wherein the first reference block in the first reference frame is located by shifting a corresponding center, top-left or other position of the current block by the given motion vector.
- The method of Claim 1, wherein the given motion vector for the current block is determined based on a motion vector of a spatial or temporal neighboring block of the current block.
- The method of Claim 1, wherein the temporal derived motion vector corresponds to a sum of the given motion vector and the reference motion vector.
- The method of Claim 1, wherein if the given motion vector points to another reference frame different from the first reference frame, the given motion vector is scaled to point to the first reference frame.
- The method of Claim 1, wherein if the reference motion vector points to another reference frame different from the second reference frame, the reference motion vector is scaled to point to the second reference frame.
- The method of Claim 1, wherein if the temporal derived motion vector points to another reference frame different from the second reference frame, the temporal derived motion vector is scaled to point to the second reference frame.
- The method of Claim 1, wherein one or more coding parameters are checked to determine whether the reference motion vector is valid or not, and the reference motion vector is used to derive the temporal derived motion vector only if the reference motion vector is valid.
- The method of Claim 8, wherein the reference motion vector is invalid if the second reference block is skip mode or merge mode, or coded block flag (cbf) of the second reference block is zero.
- The method of Claim 1, wherein the temporal derived motion vector is used in merge mode.
- The method of Claim 10, wherein one or more temporal derived motion vectors are generated for adding to a merge candidate list and each temporal derived motion vector is derived using one motion vector in an original merge candidate list as one given motion vector.
- The method of Claim 11, wherein redundancy checking is applied to said one or more temporal derived motion vectors, and any redundant temporal derived motion vector is not added to the merge candidate list.
- The method of Claim 11, wherein said one or more temporal derived motion vectors are placed at a pre-defined position of the merge candidate list.
- The method of Claim 13, wherein said one or more temporal derived motion vectors are placed in the merge candidate list after all spatial and temporal merge candidates and a number of said one or more temporal derived motion vectors allowed to add to the merge candidate list depends on a maximum size of the merge candidate list.
- The method of Claim 1, wherein the temporal derived motion vector is used in AMVP (advanced motion vector prediction) mode.
- The method of Claim 15, wherein one or more temporal derived motion vectors are generated for adding to an AMVP merge candidate list and each temporal derived motion vector is derived using one motion vector in an original AMVP candidate list as one given motion vector.
- The method of Claim 1, wherein one or more syntax elements are used to indicate whether to enable the temporal derived motion vector for motion vector prediction.
- The method of Claim 17, wherein said one or more syntax elements are explicitly signaled in a sequence level, video level, picture level or slice level.
- The method of Claim 1, wherein whether to use the temporal derived motion vector for motion vector prediction is determined at a decoder side implicitly.
- The method of Claim 19, wherein whether to use the temporal derived motion vector for the motion vector prediction is determined at the decoder side according to mode selections, motion parameters of neighboring coded blocks of the current block, or motion parameters of the first reference block, the second reference block or both.
- An apparatus for motion vector prediction, the apparatus comprising one or more electronic circuits configured to:determine a given motion vector for a current block, wherein the given motion vector points from the current block in a first direction;identify a reference motion vector associated with a first reference block in a first reference frame;derive, based on the reference motion vector and the given motion vector, a temporal derived motion vector pointing from the current block to a second reference block in a second reference frame in a second direction different from the first direction; andencode or decode a current motion vector of the current block using the temporal derived motion vector as one predictor.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP15821408.0A EP3167614B1 (en) | 2014-07-18 | 2015-07-15 | Method of temporal derived bi-directional motion vector for motion vector prediction |
US15/323,809 US10257536B2 (en) | 2014-07-18 | 2015-07-15 | Method of temporal derived bi-directional motion vector for motion vector prediciton |
CN201580039196.8A CN106664419B (en) | 2014-07-18 | 2015-07-15 | The method of time export bidirectional motion vector for motion vector prediction |
BR112017001101-8A BR112017001101B1 (en) | 2014-07-18 | 2015-07-15 | METHOD FOR MOTION VECTOR PREDICTION AND APPARATUS FOR MOTION VECTOR PREDICTION |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNPCT/CN2014/082538 | 2014-07-18 | ||
PCT/CN2014/082538 WO2016008161A1 (en) | 2014-07-18 | 2014-07-18 | Temporal derived bi-directional motion vector predictor |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016008409A1 true WO2016008409A1 (en) | 2016-01-21 |
Family
ID=55077851
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/082538 WO2016008161A1 (en) | 2014-07-18 | 2014-07-18 | Temporal derived bi-directional motion vector predictor |
PCT/CN2015/084043 WO2016008409A1 (en) | 2014-07-18 | 2015-07-15 | Method of temporal derived bi-directional motion vector for motion vector prediction |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/082538 WO2016008161A1 (en) | 2014-07-18 | 2014-07-18 | Temporal derived bi-directional motion vector predictor |
Country Status (5)
Country | Link |
---|---|
US (1) | US10257536B2 (en) |
EP (1) | EP3167614B1 (en) |
CN (1) | CN106664419B (en) |
BR (1) | BR112017001101B1 (en) |
WO (2) | WO2016008161A1 (en) |
Cited By (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10778997B2 (en) | 2018-06-29 | 2020-09-15 | Beijing Bytedance Network Technology Co., Ltd. | Resetting of look up table per slice/tile/LCU row |
WO2020192611A1 (en) * | 2019-03-22 | 2020-10-01 | Beijing Bytedance Network Technology Co., Ltd. | Interaction between merge list construction and other tools |
US10873756B2 (en) | 2018-06-29 | 2020-12-22 | Beijing Bytedance Network Technology Co., Ltd. | Interaction between LUT and AMVP |
US20200413044A1 (en) | 2018-09-12 | 2020-12-31 | Beijing Bytedance Network Technology Co., Ltd. | Conditions for starting checking hmvp candidates depend on total number minus k |
US11134243B2 (en) | 2018-07-02 | 2021-09-28 | Beijing Bytedance Network Technology Co., Ltd. | Rules on updating luts |
US11134267B2 (en) | 2018-06-29 | 2021-09-28 | Beijing Bytedance Network Technology Co., Ltd. | Update of look up table: FIFO, constrained FIFO |
US11140385B2 (en) | 2018-06-29 | 2021-10-05 | Beijing Bytedance Network Technology Co., Ltd. | Checking order of motion candidates in LUT |
US11140383B2 (en) | 2019-01-13 | 2021-10-05 | Beijing Bytedance Network Technology Co., Ltd. | Interaction between look up table and shared merge list |
US11146785B2 (en) | 2018-06-29 | 2021-10-12 | Beijing Bytedance Network Technology Co., Ltd. | Selection of coded motion information for LUT updating |
US11159817B2 (en) | 2018-06-29 | 2021-10-26 | Beijing Bytedance Network Technology Co., Ltd. | Conditions for updating LUTS |
US11159807B2 (en) | 2018-06-29 | 2021-10-26 | Beijing Bytedance Network Technology Co., Ltd. | Number of motion candidates in a look up table to be checked according to mode |
US11356689B2 (en) * | 2018-07-06 | 2022-06-07 | Hfi Innovation Inc. | Inherited motion information for decoding a current coding unit in a video coding system |
US11528500B2 (en) | 2018-06-29 | 2022-12-13 | Beijing Bytedance Network Technology Co., Ltd. | Partial/full pruning when adding a HMVP candidate to merge/AMVP |
US11589071B2 (en) | 2019-01-10 | 2023-02-21 | Beijing Bytedance Network Technology Co., Ltd. | Invoke of LUT updating |
US11895318B2 (en) | 2018-06-29 | 2024-02-06 | Beijing Bytedance Network Technology Co., Ltd | Concept of using one or multiple look up tables to store motion information of previously coded in order and use them to code following blocks |
US11956464B2 (en) | 2019-01-16 | 2024-04-09 | Beijing Bytedance Network Technology Co., Ltd | Inserting order of motion candidates in LUT |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5368631B2 (en) | 2010-04-08 | 2013-12-18 | 株式会社東芝 | Image encoding method, apparatus, and program |
CN109029427B (en) * | 2018-06-26 | 2020-10-16 | 北京永安信通科技有限公司 | Object positioning method, object positioning device and electronic equipment |
WO2020069652A1 (en) * | 2018-10-06 | 2020-04-09 | Huawei Technologies Co., Ltd. | Candidate mv construction method for hmvp mode |
CN110475116B (en) * | 2019-08-19 | 2021-09-21 | 北京大学深圳研究生院 | Motion vector deriving method and device and electronic equipment |
US20230156218A1 (en) * | 2021-11-18 | 2023-05-18 | Tencent America LLC | Derived motion vector with single reference signaling |
WO2023132510A1 (en) * | 2022-01-04 | 2023-07-13 | 현대자동차주식회사 | Method and device for video coding using improved merge with motion vector difference |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1525762A (en) * | 2003-09-12 | 2004-09-01 | 中国科学院计算技术研究所 | A coding/decoding end bothway prediction method for video coding |
US20060256866A1 (en) * | 2005-05-13 | 2006-11-16 | Streaming Networks (Pvt.) Ltd. | Method and system for providing bi-directionally predicted video coding |
CN101031087A (en) * | 2003-12-31 | 2007-09-05 | 中国科学院计算技术研究所 | Method for obtaining image by decode |
CN101827269A (en) * | 2010-01-15 | 2010-09-08 | 香港应用科技研究院有限公司 | Method for video coding and device |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1668111A (en) * | 1997-12-01 | 2005-09-14 | 三星电子株式会社 | Motion vector prediction method |
CN102215389B (en) * | 2010-04-09 | 2013-04-17 | 华为技术有限公司 | Video coding and decoding methods and devices capable of realizing local luminance compensation |
US9247266B2 (en) * | 2011-04-18 | 2016-01-26 | Texas Instruments Incorporated | Temporal motion data candidate derivation in video coding |
KR102014332B1 (en) * | 2011-10-21 | 2019-08-26 | 노키아 테크놀로지스 오와이 | Method for video coding and an apparatus |
US9503720B2 (en) | 2012-03-16 | 2016-11-22 | Qualcomm Incorporated | Motion vector coding and bi-prediction in HEVC and its extensions |
CN104205838B (en) * | 2012-03-22 | 2018-05-18 | 联发科技股份有限公司 | The method and device of scalable video |
-
2014
- 2014-07-18 WO PCT/CN2014/082538 patent/WO2016008161A1/en active Application Filing
-
2015
- 2015-07-15 WO PCT/CN2015/084043 patent/WO2016008409A1/en active Application Filing
- 2015-07-15 EP EP15821408.0A patent/EP3167614B1/en active Active
- 2015-07-15 US US15/323,809 patent/US10257536B2/en active Active
- 2015-07-15 CN CN201580039196.8A patent/CN106664419B/en active Active
- 2015-07-15 BR BR112017001101-8A patent/BR112017001101B1/en active IP Right Grant
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1525762A (en) * | 2003-09-12 | 2004-09-01 | 中国科学院计算技术研究所 | A coding/decoding end bothway prediction method for video coding |
CN101031087A (en) * | 2003-12-31 | 2007-09-05 | 中国科学院计算技术研究所 | Method for obtaining image by decode |
US20060256866A1 (en) * | 2005-05-13 | 2006-11-16 | Streaming Networks (Pvt.) Ltd. | Method and system for providing bi-directionally predicted video coding |
CN101827269A (en) * | 2010-01-15 | 2010-09-08 | 香港应用科技研究院有限公司 | Method for video coding and device |
Cited By (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11146786B2 (en) | 2018-06-20 | 2021-10-12 | Beijing Bytedance Network Technology Co., Ltd. | Checking order of motion candidates in LUT |
US11140385B2 (en) | 2018-06-29 | 2021-10-05 | Beijing Bytedance Network Technology Co., Ltd. | Checking order of motion candidates in LUT |
US11706406B2 (en) | 2018-06-29 | 2023-07-18 | Beijing Bytedance Network Technology Co., Ltd | Selection of coded motion information for LUT updating |
US11877002B2 (en) | 2018-06-29 | 2024-01-16 | Beijing Bytedance Network Technology Co., Ltd | Update of look up table: FIFO, constrained FIFO |
US11895318B2 (en) | 2018-06-29 | 2024-02-06 | Beijing Bytedance Network Technology Co., Ltd | Concept of using one or multiple look up tables to store motion information of previously coded in order and use them to code following blocks |
US11146785B2 (en) | 2018-06-29 | 2021-10-12 | Beijing Bytedance Network Technology Co., Ltd. | Selection of coded motion information for LUT updating |
US11695921B2 (en) | 2018-06-29 | 2023-07-04 | Beijing Bytedance Network Technology Co., Ltd | Selection of coded motion information for LUT updating |
US11134267B2 (en) | 2018-06-29 | 2021-09-28 | Beijing Bytedance Network Technology Co., Ltd. | Update of look up table: FIFO, constrained FIFO |
US11973971B2 (en) | 2018-06-29 | 2024-04-30 | Beijing Bytedance Network Technology Co., Ltd | Conditions for updating LUTs |
US11909989B2 (en) | 2018-06-29 | 2024-02-20 | Beijing Bytedance Network Technology Co., Ltd | Number of motion candidates in a look up table to be checked according to mode |
US10873756B2 (en) | 2018-06-29 | 2020-12-22 | Beijing Bytedance Network Technology Co., Ltd. | Interaction between LUT and AMVP |
US11245892B2 (en) | 2018-06-29 | 2022-02-08 | Beijing Bytedance Network Technology Co., Ltd. | Checking order of motion candidates in LUT |
US11528500B2 (en) | 2018-06-29 | 2022-12-13 | Beijing Bytedance Network Technology Co., Ltd. | Partial/full pruning when adding a HMVP candidate to merge/AMVP |
US11153557B2 (en) | 2018-06-29 | 2021-10-19 | Beijing Bytedance Network Technology Co., Ltd. | Which LUT to be updated or no updating |
US11528501B2 (en) | 2018-06-29 | 2022-12-13 | Beijing Bytedance Network Technology Co., Ltd. | Interaction between LUT and AMVP |
US11159817B2 (en) | 2018-06-29 | 2021-10-26 | Beijing Bytedance Network Technology Co., Ltd. | Conditions for updating LUTS |
US10778997B2 (en) | 2018-06-29 | 2020-09-15 | Beijing Bytedance Network Technology Co., Ltd. | Resetting of look up table per slice/tile/LCU row |
US11159807B2 (en) | 2018-06-29 | 2021-10-26 | Beijing Bytedance Network Technology Co., Ltd. | Number of motion candidates in a look up table to be checked according to mode |
US11134244B2 (en) | 2018-07-02 | 2021-09-28 | Beijing Bytedance Network Technology Co., Ltd. | Order of rounding and pruning in LAMVR |
US11463685B2 (en) | 2018-07-02 | 2022-10-04 | Beijing Bytedance Network Technology Co., Ltd. | LUTS with intra prediction modes and intra mode prediction from non-adjacent blocks |
US11153559B2 (en) | 2018-07-02 | 2021-10-19 | Beijing Bytedance Network Technology Co., Ltd. | Usage of LUTs |
US11153558B2 (en) | 2018-07-02 | 2021-10-19 | Beijing Bytedance Network Technology Co., Ltd. | Update of look-up tables |
US11134243B2 (en) | 2018-07-02 | 2021-09-28 | Beijing Bytedance Network Technology Co., Ltd. | Rules on updating luts |
US11356689B2 (en) * | 2018-07-06 | 2022-06-07 | Hfi Innovation Inc. | Inherited motion information for decoding a current coding unit in a video coding system |
US11159787B2 (en) | 2018-09-12 | 2021-10-26 | Beijing Bytedance Network Technology Co., Ltd. | Conditions for starting checking HMVP candidates depend on total number minus K |
US20210297659A1 (en) | 2018-09-12 | 2021-09-23 | Beijing Bytedance Network Technology Co., Ltd. | Conditions for starting checking hmvp candidates depend on total number minus k |
US20200413044A1 (en) | 2018-09-12 | 2020-12-31 | Beijing Bytedance Network Technology Co., Ltd. | Conditions for starting checking hmvp candidates depend on total number minus k |
US11997253B2 (en) | 2018-09-12 | 2024-05-28 | Beijing Bytedance Network Technology Co., Ltd | Conditions for starting checking HMVP candidates depend on total number minus K |
US11589071B2 (en) | 2019-01-10 | 2023-02-21 | Beijing Bytedance Network Technology Co., Ltd. | Invoke of LUT updating |
US11140383B2 (en) | 2019-01-13 | 2021-10-05 | Beijing Bytedance Network Technology Co., Ltd. | Interaction between look up table and shared merge list |
US11909951B2 (en) | 2019-01-13 | 2024-02-20 | Beijing Bytedance Network Technology Co., Ltd | Interaction between lut and shared merge list |
US11956464B2 (en) | 2019-01-16 | 2024-04-09 | Beijing Bytedance Network Technology Co., Ltd | Inserting order of motion candidates in LUT |
US11962799B2 (en) | 2019-01-16 | 2024-04-16 | Beijing Bytedance Network Technology Co., Ltd | Motion candidates derivation |
US11641483B2 (en) | 2019-03-22 | 2023-05-02 | Beijing Bytedance Network Technology Co., Ltd. | Interaction between merge list construction and other tools |
WO2020192611A1 (en) * | 2019-03-22 | 2020-10-01 | Beijing Bytedance Network Technology Co., Ltd. | Interaction between merge list construction and other tools |
Also Published As
Publication number | Publication date |
---|---|
US20170171558A1 (en) | 2017-06-15 |
BR112017001101B1 (en) | 2024-01-02 |
BR112017001101A2 (en) | 2018-07-10 |
EP3167614B1 (en) | 2020-02-26 |
CN106664419A (en) | 2017-05-10 |
EP3167614A4 (en) | 2017-12-27 |
US10257536B2 (en) | 2019-04-09 |
EP3167614A1 (en) | 2017-05-17 |
CN106664419B (en) | 2019-08-23 |
WO2016008161A1 (en) | 2016-01-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10257536B2 (en) | Method of temporal derived bi-directional motion vector for motion vector prediciton | |
US10412406B2 (en) | Method and apparatus for deriving temporal motion vector prediction | |
US11109052B2 (en) | Method of motion vector derivation for video coding | |
US10511835B2 (en) | Method and apparatus of decoder side motion derivation for video coding | |
US10412407B2 (en) | Method and apparatus of inter prediction using average motion vector for video coding | |
US20210136400A1 (en) | Method and apparatus of merge mode derivation for video coding | |
US20190028731A1 (en) | Method and apparatus for affine inter prediction for video coding system | |
WO2017084512A1 (en) | Method and apparatus of motion vector prediction or merge candidate derivation for video coding | |
US10701392B2 (en) | Method and apparatus for motion vector sign prediction in video coding | |
US20170310988A1 (en) | Method of Motion Vector Predictor or Merge Candidate Derivation in Video Coding | |
WO2015169200A1 (en) | Method of block vector prediction for intra block copy mode coding | |
US10944983B2 (en) | Method of motion information coding | |
US10298951B2 (en) | Method and apparatus of motion vector prediction | |
JP2014527777A (en) | Method and apparatus for MV scaling using increased effective scaling ratio |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15821408 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15323809 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2015821408 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2015821408 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112017001101 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112017001101 Country of ref document: BR Kind code of ref document: A2 Effective date: 20170118 |