AMWA NEWS
- AMWA
- Sep 29
- 4 min read
Releases, Publications, Updates
September 2025
NMOS Support for IPMX/USB, NMOS Support for IPMX/HKEP, and NMOS Support for IPMX/PEP are underway! Stay tuned for updates.
## New NMOS Publication: BCP-008 NMOS Minimum Status Reporting
A persistent challenge in IP media systems is that monitoring and control tools often receive inconsistent or incomplete status information from devices. Vendors may expose data differently, rely on varying models, or require manual configuration before systems can interpret the information. This fragmentation makes it difficult for end-users to validate streams, confirm synchronization, and troubleshoot connectivity in multi-vendor environments.
The BCP-008 initiative tackles this by defining a clear baseline for minimum status reporting across NMOS receivers and senders. The goal is to ensure that all NMOS-enabled devices provide a common set of status information covering three key areas identified in the white paper “Standardised Status Monitoring on NMOS Systems” (SRF): stream validation, synchronization, and connectivity.
BCP-008 (NMOS Minimum Status Reporting) adds a simple, standardized way to check if NMOS devices are truly working after they’re connected. It uses a “traffic light” system—green for good, yellow for “check later,” and red for service impact now—so users can quickly see device health at a glance. Status is reported across four domains: connectivity, packets, synchronization, and stream level, with the overall state reflecting the most serious issue. This helps operators spot problems quickly, understand whether they need immediate action, and know who to call if something goes wrong.
By completing consultation, aligning on scope, and selecting the technical framework, AMWA has laid the groundwork for consistent minimum status reporting. The activity is now entering the wider adoption and certification stage with further workshops and events planned.
New NMOS Publication: BCP-006-04 MPEG Transport Stream
Although NMOS specifications are widely used for uncompressed IP-based workflows, many facilities and services rely on compressed MPEG Transport Streams (MPEG-TS) as part of their infrastructure. A persistent challenge has been ensuring that NMOS controllers can configure and manage connections between TS senders and receivers in a reliable, interoperable way. Without standardization, end-users face uncertainty around stream compatibility, while vendors must implement ad hoc methods to represent capabilities.
The BCP-006-04 initiative addresses this by defining how NMOS can support configuration and interoperability for MPEG-TS devices, particularly for SMPTE ST 2022-2 streams including for VSF TR-01 (JPEG 2000) and TR-07 (JPEG XS). The first phase focuses on describing sender and receiver capabilities in a manner that controllers can use to automatically determine interoperability.
AMWA progress includes:
- Release of BCP-006-04, which enables registration, discovery, and connection management of MPEG TS endpoints using the AMWA IS-04 and IS-05 NMOS specifications.
- Refined the BCP-006-04 documentation to define the model for MPEG-TS support.
- Designing and beginning implementation of a dedicated test plan within the NMOS testing framework.
- Securing commitments from multiple implementers, including Pebble Control (controller), Appear (node), nmos-cpp, and additional vendors, to ensure a diverse test base.
- Planning an interop remote workshop (via VPN) to validate implementations and confirm interoperability across real-world devices.
Through this work, AMWA is enabling MPEG-TS devices to be managed consistently alongside other NMOS-enabled equipment. For users, this means simplified configuration and greater confidence in interoperability. For vendors, it reduces the need for custom integration while ensuring alignment with the broader NMOS ecosystem.
AMWA Publishes IS-14: NMOS Device Configuration
Configuring IP-based media devices is often complex, with each vendor offering unique approaches to saving, restoring, or automating device settings. This fragmentation creates challenges for system integrators and engineers who need reliable ways to back up configurations, roll them back, or deploy them consistently at scale. Without a common method, operators face added effort in both day-to-day operations and long-term system maintenance.
The IS-14 specification, recently published by AMWA, addresses this need by defining a standard mechanism for saving and restoring the configuration of NMOS Devices. The goal is to give system configurators and engineers a simple, consistent, and API-driven way to manage device states. User needs range from basic backup and versioning to advanced CI/CD integration, where configuration data can be delivered automatically to multiple systems in large-scale environments and Dynamic Media Facilities (DMF).
IS-14 builds on MS-05-02 models, exposing them via an HTTP-based API with emphasis on efficient bulk Get and Set operations. It also considers context-dependent configurations, ensuring that fragments requiring specific device states can still be restored safely and intuitively.
AMWA progress includes:
Publishing the IS-14 specification with reviewed and confirmed conformance language.
Adding nmos-testing coverage, so IS-14 can be validated as part of the broader NMOS Test Suite.
With IS-14 now available, the industry gains a standardized, interoperable approach to device configuration—simplifying operations, enabling automation, and strengthening system resilience.
Open Source Sender Receiver Framework (OSSRF) Released
One of the key challenges for vendors developing NMOS-enabled devices is bridging the gap between the control plane and the media/transport plane. Many vendors already have proprietary control protocols and data planes, but it is not obvious how integration with NMOS can be achieved, leading to increased development cost and slower time to market.
The Open Source Sender Receiver Framework (OSSRF) addresses this challenge, providing an open-source reference sender/receiver with NMOS control (IS-04, IS-05) and media plane integration.
Built on the widely adopted nmos-cpp project, OSSRF exposes both a bare media API and GStreamer plugins, enabling real-time streaming with low-resolution ST 2110-20 (video) and ST 2110-30 (audio) flows.
The framework demonstrates seamless NMOS operation on both commodity and cloud-based hardware platforms. OSSRF serves multiple purposes: as a foundation for NMOS integration in commercial products, as a test target for interoperability, and as a development tool for control application testing. By reducing barriers to entry and promoting open development, OSSRF aims to accelerate adoption, foster innovation, and deliver a flexible, community-driven alternative to proprietary systems. ##
Comments