Nevion has announced that its flagship orchestration and SDN control software VideoIPath now supports the NMOS (Network Media Open Specifications) IS-04 and IS-05 standards. This new VideoIPath feature is already being deployed by Swiss broadcast service provider, Technology and Production Center Switzerland AG (tpc).
Defined by the Advanced Media Workflow Association, Inc. (AMWA), the NMOS standards are designed to enable open, multi-vendor interoperability in professional media networks, such as those used by broadcasters. NMOS IS-04 offers a way to register, discover and find broadcast resources (typically equipment and functionality) automatically in a network. NMOS IS-05 allows a management system to establish connections between senders (such as cameras) and receivers (such as video mixers), and also supports a way to establish ad-hoc connections directly between devices without the presence of a management solution. Support for these standards is beginning to appear on various suppliers’ equipment and roadmaps.
Nevion VideoIPath is now able to act as an IS-04 registry for compliant equipment, meaning it can detect when new devices are connected to the IP media network, and understand their capabilities. VideoIPath can also use that information to control these devices through IS-05, to establish media flows between senders and receivers. Nevion VideoIPath can also handle mixed environments, enabling NMOS senders or receivers to connect with non-compliant devices.
In addition, Nevion is committed to following the JT-NM TR1001-1 recommendation, which describes the expected registration and connection management behaviour of systems and devices in a SMPTE ST 2110 media network.
Johnny Dolvik, Chief Product and Development Officer, Nevion, said: “From the beginning, we have designed VideoIPath to handle a multi-vendor environment. We have developed large number of drivers to control a variety of equipment, including IP gateways, multi-viewers, measuring equipment, intercom systems, and graphics systems. We have also adopted standard interfaces where they exist, such as OpenFlow and OpenConfig for IP network equipment control. Adding the NMOS standards was therefore a logical move for us, and of course we are really pleased this feature is already being deployed in the tpc project.”