Emulation Prevention Byte Remover for H.264 Video Decoder

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing H.264 video codec systems face limitations in efficiently eliminating emulation prevention bytes from stream data, especially when processing high image resolution and high frequency data using software alone.

Innovation Solution

An emulation prevention byte remover system comprising buffers, a checker, and a shifter is used to identify and remove emulation prevention bytes from stream data, generating output stream data without delays, even when multiple bytes are present, by shifting and storing data in a structured manner.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software is used to eliminate emulation prevention bytes from stream data, then the system can handle high image resolution and high frequency data, but the processing efficiency is limited and cannot keep up with high-speed decoding requirements

Engineering Contradiction:
Improveaccuracy of emulation prevention byte eliminationVSAvoidprocessing speed of stream data
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent replaces the software-based elimination method with a hardware-based circuit implementation. The circuit includes a buffer for storing stream data, a checker for detecting emulation prevention bytes, and a shifter for removing detected bytes. This hardware substitution enables parallel processing and significantly increases processing speed while maintaining accurate elimination of emulation prevention bytes from H.264 stream data.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If emulation prevention bytes are removed using traditional methods, then the stream data can be decoded, but processing delays occur especially with high-resolution data

Engineering Contradiction:
Improvecorrectness of stream data decodingVSAvoidprocessing delay in eliminating emulation prevention bytes
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements a buffer that stores stream data before processing, allowing the checker and shifter to operate in advance on incoming data. This preliminary action enables the system to detect and remove emulation prevention bytes proactively before they interfere with decoding operations, eliminating processing delays while ensuring correct decoding of the stream data.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If multiple emulation prevention bytes are present in stream data, then complete removal is required for proper decoding, but traditional software methods become increasingly inefficient

Engineering Contradiction:
Improvecompleteness of emulation prevention byte removalVSAvoidprocessing efficiency with multiple bytes
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements a continuous hardware processing pipeline where the buffer continuously feeds data to the checker, which continuously detects emulation prevention bytes, and the shifter continuously removes detected bytes. This continuous operation ensures that multiple emulation prevention bytes are removed completely and efficiently without the intermittent processing bottlenecks of software methods, maintaining high productivity regardless of the number of bytes present.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS8867900B2Emulation prevention byte removers for video decoder
Publication Date: 2014.10.21 SAMSUNG ELECTRONICS CO LTD
  • US8867900B2 patent drawing
  • US8867900B2 patent drawing
  • US8867900B2 patent drawing

AI summary

An emulation prevention byte remover may include one or more of a first buffer, a second buffer, a checker, and a shifter. The first buffer may store first stream data. The second buffer may store second stream data. The checker may determine whether one or more emulation prevention bytes are included in the first, second, or first and second stream data. If the checker determines that the one or more emulation prevention bytes are included in the first, second, or first and second stream data, the checker may output a check signal. In response to the check signal, the shifter may remove at least one of the one or more emulation prevention bytes from the first, second, or first and second stream data. The shifter may generate output stream data based on the first, second, or first and second stream data.