We've heard a lot about NMOS. But what is it exactly, and what are the objectives. Is it widely adopted already?
You can find more information about NMOS and the SMPTE ST2022-6 and SMPTE ST2110-X ecosystem on our Dojo Exert Hub
There you will also find a collection of links pointing to other websites to learn all about the NMOS specifications as well as webinars from our tech partners presenting NMOS customer use cases.
NMOS IS-04 (Discovery & Registration) is part of DataMiner Infrastructure Discovery and Provisioning (IDP). DataMiner uses the IS-04 Query-API to connect to any third-party NMOS registry. With that DataMiner can automatically provision new nodes in DataMiner. Whenever there is a non NMOS-compliant device, DataMiner does a network scan to discover new devices within the network, it is also possible to connect with other third-party CMDBs or inventory databases to learn about new infrastructure. With that IDP supports both NMOS and non-NMOS compliant devices.
NMOS IS-05 (Connection Management) is part of the DataMiner SDN orchestration solution, also called SDMN (Software Defined Media Networking). Whenever destination-based switching is used to connect sources with destinations, DataMiner can interface with those nodes either via IS-05 or any other proprietary protocol. Similar to DataMiner IDP, this ensures that media flows can be switched in an IP-fabric independent of the protocol used by the source or destination device. DataMiner can control each destination device to set the receiving multicast-address either via IS-05 or any other API command.
Hi Ben,
A while ago I came across the following one page online article which nicely describes NMOS and its key objectives.
I'm at this moment not able to provide you with more insights on how widely adopted it is already. We do however see that the latest new ST2110 compliant media equipment appears to offer an NMOS (IS-04 / IS-05) or an Ember+ interface. Sometimes even both, but typically the vendors now appear to offer the choice at order time, whether the media equipment should expose an NMOS API or should expose an Ember+ API.)
Ember+ (brought to existence by Lawo but with the same plug and play type of behavior envisioned) appears to be competing with NMOS at the moment as this standard got adopted a bit sooner by already a range of broadcast equipment / controllers.
There's already some broadcast controllers out there which are compatible with both protocols. So they can handle a hybrid environment where part will be controlled over NMOS, part over Ember+ and partly vendor bespoke API's.
Personally I do believe that NMOS will eventually win over Ember+ in popularity as it offers many more advantages and standardization which Ember+ does not but only the future will tell us that.
There's a specific overview of Media Nodes supporting NMOS on the AMWA website.