SEI Message Referencing for Lower Bit Cost in Video Coding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing video coding standards like VVC and HEVC lack efficient mechanisms for referencing SEI messages, leading to repetitive transmission of these messages even when their application is not necessary for every picture, resulting in increased bit cost and reduced coding efficiency.

Innovation Solution

A mechanism is introduced to reference SEI messages using two types of packets, where a first packet contains the functionality information and an identifier, and a second packet, sent more frequently, references this information for specific segments, allowing flexible application without repeating the full functionality information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If SEI messages are transmitted for every picture to ensure functionality application, then reliability of functionality application is improved, but bit cost increases due to redundant transmission

Engineering Contradiction:
Improvereliability of functionality applicationVSAvoidbit cost
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The SEI message transmission is segmented into two types: full functionality SEI messages transmitted periodically or when changes occur, and lightweight reference SEI messages transmitted for each picture. This segmentation allows the system to maintain reliability through periodic full messages while reducing bit cost through reference messages that point to previously transmitted functionality information.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The full SEI message with complete functionality information is transmitted in advance (periodically or on change), and subsequent pictures reference this pre-transmitted information. This preliminary action ensures that the functionality information is available before it is needed, maintaining reliability while avoiding redundant transmission of the same data.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If full SEI messages are transmitted for each picture, then coding completeness is improved, but coding efficiency deteriorates due to redundancy

Engineering Contradiction:
Improvecoding completenessVSAvoidcoding efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Instead of transmitting the full SEI message for each picture, the system transmits a lightweight copy or reference (pointer/identifier) that points to the previously transmitted full SEI message. This copying approach maintains coding completeness by ensuring the functionality information is available while dramatically improving coding efficiency by avoiding redundant data transmission.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If SEI messages are transmitted frequently to apply functionality to all pictures, then adaptability is improved, but bit cost increases

Engineering Contradiction:
Improveflexibility in functionality applicationVSAvoidbit cost
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system dynamically adapts the SEI message transmission strategy based on the specific needs of each picture or segment. Full SEI messages are transmitted when functionality changes or periodically, while reference messages are used when the same functionality applies. This dynamic approach maintains adaptability and flexibility while optimizing bit cost by avoiding unnecessary redundant transmissions.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12513337B2Message referencing
Publication Date: 2025.12.30 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US12513337B2 patent drawing
  • US12513337B2 patent drawing
  • US12513337B2 patent drawing

AI summary

There is provided a referencing mechanism for messages (e.g., SEI messages) in order to reduce the bit cost when different versions of messages (e.g., SEI messages) are used in an arbitrary manner in the bitstream, e.g. in an alternating way in the bitstream. In embodiments, two SEI messages are used to express a functionality. In the first SEI message, syntax elements specifying the functionality is provided. The first SEI message may also have an identifier value, which uniquely identifies the instance of that particular SEI message. The second SEI message, typically much smaller and sent more frequently than the first SEI message, is used to reference the first SEI message in order to apply the functionality of the first SEI message to a part of the bitstream determined by the persistence scope of the second SEI message, e.g. for the picture or subpicture it was sent with.