AMWA NMOS Core Integration
Production
Recommended for normal production use.
Caution
Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.
Minimum hi Version: v2.5.0
Overview
The NMOS Core Integration discovers IS-04 resources through a selected registry and controls supported sender and receiver connections through IS-05. It makes discovered NMOS Nodes and their IP media Ports available to hi routing workflows.
NMOS Nodes register with the IS-04 registry, which is an external registry or the hi NMOS Registry. hi finds the registry through Auto Discovery or the Registry URL, and reads its resources through the Query API. hi changes connections on the NMOS Nodes directly through IS-05, so it needs network access to both the registry and the Nodes.
Network Requirements
-
Connection Model: hi connects to the selected IS-04 registry and to advertised NMOS Node control endpoints.
-
Multicast / Unicast: Control traffic is unicast. Media flows may be unicast or multicast according to the NMOS resources.
-
VLAN / IGMP: Configure multicast handling for the media flows used by the installation.
-
Bandwidth: Control-plane traffic only; media does not pass through the integration service.
-
IP Version: Validate against the connected NMOS infrastructure.
-
Firewall: Permit outbound HTTP and WebSocket connections from hi to the registry and advertised Node APIs.
Standards Conformance
|
Standard |
Conformance |
Notes |
|---|---|---|
|
AMWA NMOS IS-04 |
Implemented |
Registry discovery
|
|
AMWA NMOS IS-05 |
Implemented |
Sender and receiver connection management for v1.0 and v1.1 |
Operator Workflow
The following example shows a selected multicast network with separate Video and Audio address ranges. The addresses are illustrative; plan the allocation for your installation.
-
Selected multicast network.
-
Video and audio address ranges assigned to the network.
-
UI Surface in hi: Routing Matrix, Topology, Inventory, IP, and Multicast Addresses
-
Resources Controlled: Discovered Nodes, devices, Sources, flows, senders, and receivers
-
Routing Semantics: IS-05 senders and receivers are mapped to hi Sources and Destinations.
Connection Methods
Connection: IS-04 Query API
|
Property |
Value |
|---|---|
|
Protocol |
AMWA NMOS IS-04 v1.2 and v1.3 Query API |
|
Transport |
HTTP or HTTPS |
|
Default Port |
Service-discovered from the selected registry |
|
Authentication |
Depends on the advertised registry endpoint |
|
Encryption in Transit |
Depends on whether the advertised endpoint uses HTTPS |
|
Connection Model |
Outbound registry queries |
|
Required License |
hiNMOS |
|
Traffic Flow |
Outbound requests with inbound resource data |
Connection: IS-04 Query Subscriptions
|
Property |
Value |
|---|---|
|
Protocol |
AMWA NMOS IS-04 v1.2 and v1.3 Query subscriptions |
|
Transport |
WebSocket or secure WebSocket |
|
Default Port |
Service-discovered from the selected registry |
|
Authentication |
Depends on the advertised registry endpoint |
|
Encryption in Transit |
Depends on whether the advertised endpoint uses secure WebSocket |
|
Connection Model |
Outbound subscription maintained by hi |
|
Required License |
hiNMOS |
|
Traffic Flow |
Resource-change updates from the registry to hi |
Connection: IS-05 Connection API
|
Property |
Value |
|---|---|
|
Protocol |
AMWA NMOS IS-05 v1.0 and v1.1 Connection API |
|
Transport |
HTTP or HTTPS |
|
Default Port |
Service-discovered from each NMOS Node |
|
Authentication |
Depends on the advertised Node endpoint |
|
Encryption in Transit |
Depends on whether the advertised endpoint uses HTTPS |
|
Connection Model |
Outbound sender and receiver control requests |
|
Required License |
hiNMOS |
|
Traffic Flow |
Bidirectional connection management |
Required Configuration
|
Parameter |
Description |
Default |
|---|---|---|
|
Create NMOS Registry |
Create the hi NMOS Registry together with the Core Integration |
No |
|
Auto Discovery |
Discover a registry automatically and ignore the manual Registry URL |
Yes |
|
Registry URL |
Full |
- |
|
Automatic RTP and Master Enable Management |
Allow hi to manage NMOS Master Enable and primary or secondary RTP Enable states |
Yes |
When Automatic RTP and Master Enable Management is enabled, eligible NMOS Nodes expose independent settings for Manage Master Enable, Manage Primary RTP Enable, and Manage Secondary RTP Enable. Set the global option to No when the connected devices or media network require external control of these states. hi then leaves the states unchanged and hides the Node-level management settings.
Device-Side Setup
Follow AMWA NMOS Core Integration Configuration for the device-side and hi-side configuration steps.
Supported Features
|
Feature |
Access |
Exposed Operation and Scope |
|---|---|---|
|
IS-04 Discovery |
Read-only |
Synchronize supported NMOS resources from the selected registry. |
|
IS-04 Subscriptions |
Read-only updates |
Receive resource changes without a full manual refresh. |
|
IS-05 Connection Management |
Read/write |
Read and change supported sender/receiver connections. |
|
ST 2022-7 Handling |
Read/write management |
Represent redundant flow legs and manage secondary RTP state when that option is enabled. |
|
Receiver Format Updates |
Read-only updates |
Update receiver representation when the connected sender format changes. |
|
Multicast Address Management |
hi-side configuration and write actions |
Manage multicast ranges for supported managed NMOS Nodes. |
|
Managed Node Workflow |
hi-side configuration and write actions |
Convert supported non-managed Nodes to managed operation and change a managed Node's configured multicast range. |
|
API Endpoint Information |
Read-only |
Show the highest advertised Connection (IS-05), Event (IS-07), Channel Mapping (IS-08), and Manifest API URLs of each NMOS Node in its API URLs group. |
Device Coverage
Tested With identifies devices that have been tested with hi. Potentially Compatible (Not Yet Verified) identifies devices that use the same protocol or connection method but have not been tested with hi. Device-specific configuration, firmware, and feature support can affect results.
Tested With
-
NMOS IS-04:
-
Riedel 1200 Series SmartPanel, including RSP-1232HL
-
Riedel Artist-1024 (AES67 SIC)
-
Riedel MediorNet IP, including MediorNet FusioN and MediorNet MuoN
-
Riedel MediorNet TDM
-
Arkona Technologies AT300 BLADE//runner
-
Matrox ConvertIP DSH
-
Matrox ConvertIP DSS
-
Panasonic KAIROS
-
Sony HDCE-TX30
-
-
NMOS IS-05:
-
Bridge Technologies VB440
-
Arkona Technologies AT300 BLADE//runner
-
Grass Valley LDX Series
-
Imagine Communications Magellan SDNO
-
Imagine Communications Selenio Network Processor (SNP)
-
Matrox ConvertIP DSH
-
Matrox ConvertIP DSS
-
Panasonic KAIROS
-
Providius Broadcast Media Guard (BMG)
-
Riedel 1200 Series SmartPanel, including RSP-1232HL
-
Riedel Artist-1024 (AES67 SIC)
-
Riedel MediorNet IP, including MediorNet FusioN and MediorNet MuoN
-
Riedel MediorNet TDM
-
Sony HDCU-5500
-
Sony HDCE-TX30
-
Sony XVS-8000 (IP I/O boards)
-
Telestream PRISM
-
Potentially Compatible (Not Yet Verified)
-
Other devices and services that implement the supported AMWA NMOS IS-04 and IS-05 APIs and advertise reachable endpoints.
Known Limitations
-
Validate the advertised IS-04 and IS-05 API versions and transport parameters for every connected vendor implementation.
-
Available media formats and connection controls depend on the resources exposed by each NMOS Node.
What's Not Supported
-
Firmware updates and low-level vendor device configuration.
-
Media encoding or essence creation.
-
Control of USB-over-IP fields (AMWA BCP-007-02) and Matrox USB extension fields.
-
IS-08 audio channel mapping, IS-11 stream compatibility, and IS-12 device control. hi shows an advertised IS-08 API URL but does not control it.
-
IS-10 authorization. hi does not send authorization tokens to NMOS APIs.
Trademarks
Note
NMOS is an open specification developed by the Advanced Media Workflow Association (AMWA).
All product names, logos, and brands are property of their respective owners. Copyright in third-party software and materials remains with the respective owners. Use of these names does not imply endorsement.
RIEDEL Communications is not affiliated with, endorsed by, or officially partnered with AMWA unless explicitly stated.