NMOS API Mirroring for IP Receiver Flow State Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In media production environments, there is a need for standardized communication protocols to enable efficient interaction and mirroring of receiver nodes, particularly for testing and maintenance purposes, as existing systems lack seamless integration and automation capabilities.

Innovation Solution

The implementation of Networked Media Open Specifications (NMOS) APIs allows for IP-based communication between nodes, enabling a mirror node to replicate the flow state of a receiver node through polling mechanisms or connection manager control, ensuring synchronized data transmission and reception.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If standardized communication protocols are implemented, then interoperability and ease of operation are improved, but device complexity increases due to integration of multiple protocols and interfaces

Engineering Contradiction:
ImproveinteroperabilityVSAvoidintegration complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a standardized API layer as an intermediary between diverse media production equipment and control systems. This API acts as a mediator that translates various equipment-specific protocols into a common interface, enabling seamless interoperability without requiring complex point-to-point integrations between each device pair.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If receiver node mirroring is implemented for testing purposes, then measurement precision and reliability are improved, but loss of time occurs due to configuration setup and synchronization overhead

Engineering Contradiction:
Improvetesting accuracyVSAvoidconfiguration time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent implements a receiver node mirroring capability that creates a virtual copy of the target receiver's flow configuration and state. This copy can be used for testing and verification purposes without affecting the original receiver, allowing precise measurement of flow states and configuration validation while reducing setup time through template-based replication.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary configuration actions by pre-setting up mirror receiver nodes with identical flow states and configurations before actual testing begins. This advance preparation allows testing to start immediately with accurate baseline data, eliminating the need for time-consuming configuration during test execution.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If automated interactivity is implemented through standardized protocols, then productivity is improved, but device complexity increases due to automation infrastructure requirements

Engineering Contradiction:
Improveautomation efficiencyVSAvoidautomation infrastructure
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements self-service automation where the standardized API enables equipment to automatically discover, register, and configure themselves within the media production network. Devices can autonomously manage their own connections, flow states, and mirror relationships without requiring manual configuration or complex centralized control infrastructure, thereby improving productivity while keeping the automation infrastructure simple.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10581965B2Mirroring flow configurations for internet protocol receivers
Publication Date: 2020.03.03 PROJECT GIANTS LLC
  • US10581965B2 patent drawing
  • US10581965B2 patent drawing
  • US10581965B2 patent drawing

AI summary

Disclosed is a mechanism of operating a Networked Media Open Specifications (NMOS) Application Programming Interface (API) at a node controlling a local device including a local receiver. A flow message is received via the NMOS API. The flow message contains a flow state of a target receiver at a remote node. A local receiver at the local device is configured to mirror the flow state of the target receiver at the remote node. The NMOS API then notifies a registry with an updated flow state of the local receiver at the local device.