Service Guide Decoding via Field Extraction

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing service guide decoding methods for video bitstreams in mobile broadcast systems face challenges in efficiently handling various fragment encoding and type fields, leading to complexities in processing and interpreting service guide data.

Innovation Solution

The method involves receiving and decoding service guide fragments within a video bitstream by processing specific fields such as the extension offset, fragment encoding, and fragment type fields, with specific rules for ignoring non-zero values or certain types to simplify the decoding process, ensuring compatibility with particular service guide delivery unit structures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If service guide fragments are encapsulated using the service guide delivery unit structure with extension offset field and fragment encoding field, then the service guide can be delivered within video bitstream, but the decoding complexity increases due to handling various field values and specifications

Engineering Contradiction:

Improveservice guide deliveryVSAvoiddecoding complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts and ignores specific fields (extension offset field when non-zero, fragment encoding field when non-zero, fragment type field when equal to or greater than 4) from the service guide delivery unit structure. By selectively removing or ignoring certain fields based on the specification version, the decoder simplifies processing while maintaining compatibility with the service guide delivery functionality.

Inventive Principle:

Principle #2Taking out (Extraction)

2Adaptability or versatility

If the extension offset field is processed according to all possible values, then all specification versions are supported, but processing time and computational resources increase

Engineering Contradiction:

Improvespecification compatibilityVSAvoidprocessing time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

Instead of processing all possible values of the extension offset field and fragment encoding field, the patent inverts the approach by defaulting to ignore these fields and only processing them when specifically required. The decoder assumes a simplified interpretation unless the field values indicate otherwise, thereby reducing default processing time while maintaining specification compatibility when needed.

Inventive Principle:

Principle #13The other way round (Inversion)

3Loss of information

If fragment type field values 4-9 are processed with full XML fragment data, then complete service information is available, but data transmission efficiency decreases

Engineering Contradiction:

Improveservice information completenessVSAvoiddata transmission efficiency

Core Design Contradiction:

Loss of informationVSProductivity

Solution Approach 1:

The patent extracts and ignores the XML fragment data when the fragment type field indicates types 4-9 (Access, PurchaseItem, PurchaseData, PurchaseChannel, PreviewData, InteractivityData). By removing these optional data elements from processing, the system improves data transmission efficiency while maintaining compatibility with specifications that may or may not include these fields.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS11044519B2Service guide encapsulation

Publication Date: 2021.06.22 SHARP KK

AI summary

A system for generating, providing and/or receiving an encapsulated service guide data.