PMCP Extended Metadata Structure for Digital Data Broadcasting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The conventional Programming Metadata Communication Protocol (PMCP) lacks the necessary metadata structure to ensure inter-operability between digital broadcast emitting systems and data servers, particularly in transmitting data broadcasting content, leading to inefficiencies and increased costs in integrating data broadcasting capabilities.

Innovation Solution

An extended metadata structure is introduced, including channel type metadata, PSIP data event metadata, and data stream metadata, which provides system information, program guide, and encapsulation information for data events, enabling a data stream generating device to analyze, schedule, and encapsulate data broadcasting content for output as a transport stream.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional PMCP metadata structure is used, then inter-operability between digital broadcast emitting systems is maintained, but data broadcasting functionality cannot be implemented

Engineering Contradiction:
Improvedata broadcasting capabilityVSAvoidinter-operability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The PMCP metadata structure is segmented into conventional elements (maintaining inter-operability) and extended data broadcasting elements (enabling new functionality). The extension adds separate metadata fields for data event information, encapsulation parameters, and data stream identifiers without modifying the core PMCP structure, allowing both legacy and enhanced systems to coexist.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The extended PMCP metadata structure serves multiple functions: it maintains compatibility with conventional digital broadcast emitting systems while simultaneously enabling data broadcasting capabilities. The universal structure accommodates both traditional program guide information and new data event information through optional extended fields that can be activated based on system capabilities.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If interface is independently defined by each operator, then specific system requirements are met, but inter-operability between devices from various companies cannot be secured

Engineering Contradiction:
Improvesystem customizationVSAvoidinterface integration
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

A universal extended PMCP metadata structure is defined that can accommodate diverse system requirements through standardized optional fields. This allows different operators to utilize the same interface framework while customizing their use of available metadata fields, eliminating the need for operator-specific interface definitions and reducing integration complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The metadata structure allows parameter extension through standardized fields that can be activated or deactivated based on system requirements. Operators can customize their implementation by selecting which optional metadata fields to utilize, while maintaining compatibility with the standard interface structure, thus achieving both customization and ease of integration.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If PMCP only provides metadata for audio/video broadcast, then conventional broadcasting is supported, but data broadcasting content cannot be transmitted

Engineering Contradiction:
Improvebroadcasting type supportVSAvoiddata event information
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The metadata structure is segmented into distinct sections: conventional audio/video broadcast metadata (maintaining existing functionality) and extended data broadcasting metadata (enabling new functionality). The data broadcasting section includes separate fields for data event identifiers, encapsulation information, and data stream parameters, ensuring no information loss while expanding capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The extended PMCP structure embeds conventional metadata within a larger framework that includes additional data broadcasting layers. The nested structure allows conventional audio/video metadata to coexist with new data event metadata, where the extended fields are nested within the existing PMCP message structure, preserving all original information while adding new capabilities.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS7908633B2PMCP extension metadata, data stream generating device, digital data broadcasting emission system and digital data broadcasting emission method thereof
Publication Date: 2011.03.15 ELECTRONICS & TELECOMM RES INST
  • US7908633B2 patent drawing
  • US7908633B2 patent drawing
  • US7908633B2 patent drawing

AI summary

Provided are a data server, which is added to a digital broadcast emitting system to emit data broadcasting based on the Programming Metadata Communication Protocol (PMCP), a conventional international specification defined to secure inter-operability between devices of a digital broadcast emitting system; a metadata structure for securing inter-operability between devices of the conventional digital broadcast emitting system; a data stream generating device using the metadata structure; and a digital data broadcast emitting system and method thereof. The PMCP extended metadata of the present invention are formed to include channel type metadata which provide system information of a data event constituting a data broadcast program; and Program and System Information Protocol (PSIP) data event metadata which provide identification information, program guide, and encapsulation information of a data event.