NBMP Capability Description Format for Cross-Vendor Interoperability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current 3GPP FLUS protocol lacks standardization for describing network or cloud platform resources and media source/sink device capabilities, leading to vendor-specific interoperability issues and inability to recognize capabilities across different vendors.

Innovation Solution

Implementing a Network-Based Media Processing (NBMP) standard that defines a description format for network or cloud resource capabilities, including computational, storage, and power resources, using descriptors like JSON objects via REST APIs to manage media processing workflows across media sources, sinks, and processing entities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If vendor-specific URNs are used to describe capabilities, then vendor-specific functionality can be described, but cross-vendor interoperability cannot be achieved

Engineering Contradiction:

Improvecapability description flexibilityVSAvoidcross-vendor interoperability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies universality by creating a standardized capability description format that can universally describe capabilities across different vendors. The JSON-based descriptor structure with standardized fields (capability_id, name, description, parameters) allows any vendor's capability to be described using the same universal schema, enabling both vendor-specific functionality and cross-vendor interoperability simultaneously.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent changes the parameter representation from opaque vendor-specific URNs to structured JSON descriptors with explicit parameters. Each capability is described using standardized parameters (capability_id, name, description, parameters array) that can be systematically interpreted by different vendors, transforming the capability description system from vendor-specific to universally interoperable.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If no standard description format is used, then vendor-specific capabilities can be documented, but systematic capability management and workflow automation become difficult

Engineering Contradiction:

Improvecapability documentation flexibilityVSAvoidcapability management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent transforms capability documentation from unstructured vendor-specific formats to a standardized parameter-based JSON structure. The standardized parameters (capability_id, name, description, parameters array) provide systematic organization while maintaining the flexibility to document any vendor-specific capability, reducing management complexity through consistency.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The patent segments capability descriptions into distinct, standardized components (capability_id, name, description, parameters). This segmentation allows systematic management of individual capability attributes while maintaining overall flexibility, making it easier to query, compare, and automate workflow decisions based on specific capability parameters.

Inventive Principle:

Principle #1Segmentation

3Reliability

If detailed capability parameters are standardized, then interoperability is improved, but the description format complexity increases

Engineering Contradiction:

Improvecross-vendor interoperabilityVSAvoiddescription format structure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the capability description into a hierarchical structure with a standardized framework (capability_id, name, description, parameters) and flexible vendor-specific content within the parameters array. This segmentation provides a simple, consistent interface at the top level while allowing detailed parameter customization, reducing perceived complexity while maintaining interoperability.

Inventive Principle:

Principle #1Segmentation

4Productivity

If NBMP standard is implemented, then cross-vendor interoperability and workflow automation are enabled, but implementation complexity increases

Engineering Contradiction:

Improveworkflow automation capabilityVSAvoidsystem implementation complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The NBMP standard provides a universal JSON-based capability description format that can be applied across different vendors and media processing scenarios. This universality enables workflow automation through standardized capability queries and comparisons, as the same descriptor structure can be used regardless of the specific vendor or capability type, reducing implementation complexity through consistency.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11388067B2Systems and methods for network-based media processing (NBMP) for describing capabilities

Publication Date: 2022.07.12 TENCENT AMERICA LLC

AI summary

Systems and methods for media processing and streaming is provided, a method is performed by at least one processor that implements a workflow manager of a media system. The method includes obtaining a description that includes at least one descriptor that indicates capabilities of an entity of the media system, the entity being a media processing entity, a media source, or a media sink, and the entity including at least one processor; determining the capabilities of the entity based on the at least one descriptor; and managing a media processing workflow based on the determining.