IntraBC Encoding Efficiency Across Slices in HEVC

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

IntraBlockCopy (IntraBC) encoding efficiency is compromised in HEVC when images are divided into slices, as it cannot reference data from other slices, leading to poorer encoding performance due to restricted motion prediction across slices.

Innovation Solution

An image encoding device and method that sets control information for in-screen motion prediction across slices, including a reference permission flag and parameter indicating the number of previous slices that can be referenced, allowing for improved encoding efficiency by enabling reference to previous slice data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If images are divided into slices for low-delay processing, then processing delay is reduced, but encoding efficiency in IntraBC deteriorates due to inability to reference data across slices

Engineering Contradiction:
Improveprocessing delayVSAvoidencoding efficiency
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The patent applies segmentation by dividing the image into slices for parallel processing while introducing a mechanism to reference across slice boundaries. The control information structure is segmented to include flags and parameters that enable selective cross-slice referencing, allowing the system to maintain both slice-based parallelism and cross-slice prediction capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces control information as an intermediary between slices, including a reference permission flag and a parameter indicating the number of previous slices that can be referenced. This intermediary structure enables the decoder to understand and implement cross-slice referencing without requiring complex inter-slice communication mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If IntraBC is restricted to current slice only, then decoding complexity is reduced, but encoding performance deteriorates due to limited motion prediction

Engineering Contradiction:
Improvedecoding complexityVSAvoidencoding performance
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent applies dynamics by making the cross-slice referencing capability configurable rather than fixed. The reference permission flag and slice reference parameter allow the system to dynamically adjust the level of cross-slice referencing based on content requirements, enabling the decoder to switch between simple intra-slice prediction and more complex cross-slice prediction as needed.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes parameters by introducing a reference permission flag and a parameter indicating the number of previous slices that can be referenced. These parameters control the extent of cross-slice referencing, allowing the system to optimize between decoding complexity and encoding performance by adjusting the reference range based on the specific video content and application requirements.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20240372985A1Image encoding device and method, and image decoding device and method
Publication Date: 2024.11.07 SONY GROUP CORP
  • US20240372985A1 patent drawing
  • US20240372985A1 patent drawing
  • US20240372985A1 patent drawing

AI summary

An image encoding device and a method, and an image decoding device and a method that are designed to improve encoding efficiency in IntraBC. A screen is divided into four slices (Slices #0 through #3). In a case where reference to a different slice is prohibited, the range that can be referred to from the current CTU in Slice #2 is only the decoded portion in Slice #2, and therefore, any block in Slice #1 cannot be referred to, for example. In the case of the present technology, on the other hand, decoded different slices (Slice #0 and Slice #1) are included in the referable range, and accordingly, a block in Slice #1 can be referred to from the current CTU in Slice #2.