Video: Introduction to IPMX

The Broadcast Knowledge has documented over 100 videos and webinars on SMPTE ST 2110. It’s a great suite of standards but it’s not always simple to implement. For smaller systems, many of the complications and nuances don’t occur so a lot of the deeper dives into ST 2110 and its associated specifications such as NMOS from AMWA focus on the work done in large systems in tier-1 broadcasters such as the BBC, tpc and FIS Skiing for SVT.

ProAV, the professional end of the AV market, is a different market. Very few companies have a large AV department if one at all. So the ProAV market needs technologies which are much more ‘plug and play’ particularly those in the events side of the market. To date, the ProAV market has been successful in adopting IP technology with quick deployments by using heavily proprietary solutions like ZeeVee, SDVoE and NDI to name a few. These achieve interoperability by having the same software or hardware in each and every implementation.

IPMX aims to change this by bringing together a mix of standards and open specifications: SMPTE ST 2110, NMOS specs and AES. Any individual or company can gain access and develop a service or product to meet them.

Andreas gives a brief history of IP to date outlining how AES67, ST 2110, ST 2059 and the IS specifications, his point being that the work is not yet done. ProAV has needs beyond, though complementary to, those of broadcast.

AES67 is already the answer to a previous interoperability challenge, explains Andreas, as the world of audio over IP was once a purely federated world of proprietary standards which had no, or limited, interoperability. AES67 defined a way to allow these standards to interoperate and has now become the main way audio is moved in SMPTE 2110 under ST 2110-30 (2110-31 allows for AES3). Andreas explains the basics of 2110, AES, as well as the NMOS specifications. He then shows how they fit together in a layered design.

Andreas brings the talk to a close looking at some of the extensions that are needed, he highlights the ability to be more flexible with the quality-bandwidth-latency trade-off. Some ProAV applications require pixel perfection, but some are dictated by lower bandwidth. The current ecosystem, if you include ST 2110-22’s ability to carry JPEG-XS instead of uncompressed video allows only very coarse control of this. HDMI, naturally, is of great importance for ProAV with so many HDMI interfaces in play but also the wide variety of resolutions and framerates that are found outside of broadcast. Work is ongoing to enable HDCP to be carried, suitably encrypted, in these systems. Finally, there is a plan to specify a way to reduce the highly strict PTP requirements.

Watch now!
Speaker

Andreas Hildebrand Andreas Hildebrand
Evangelist,
ALC NetworX

Video: What is NMOS? with a Secure Control Case Study

Once you’ve implemented SMPTE ST 2110‘s suite of standards on your network, you’ve still got all your work ahead of you in order to implement large-scale workflows. How are you doing to discover new devices? How will you make or change connections between devices? How will you associate audios to the video? Creating a functioning system requires an whole ecosystem of control protocols and information exchange which is exactly what AMWA, the Advanced Media Workflow Association has been working on for many years now.

Jed Deame from Nextera introduces the main specifications that have been developed to work hand-in-hand with uncompressed workflows. All prefixed with IS- which stands for ‘Interface Specificaion’, they are IS-04, IS-05, IS-08, IS-09 and IS-10. Between them they allow you to discover new devices, create connections between then, manage the association of audio with video as well as manage system-wide information. Each of these, Jed goes through in turn. The only relevant ones which are skipped are IS-06 which allows devices to communicate northbound to an SDN controller and IS-07 which manages GPI and tally information.

Jed sets the scene by describing an example ST-2110 setup with devices able to join a network, register their presence and be quickly involved in routing events. He then looks at the first specification in today’s talk, NMOS IS-04. IS-04’s job is to provide an API for nodes (cameras, monitors etc.) to use when they start up to talk to a central registry and lodge some details for further communication. The registry contains a GUID for every resource which covers nodes, devices, sources, flows, senders and receivers. IS-04 also provides a query API for controllers (for instance a control panel).

While IS-04 started off very basic, as it’s moved to version 1.4, it’s added HTTPS transport, paged queries and support for connection management with IS-05 and IS-06. IS-04 is a foundational part of the system allowing each element to have an identity, track when entities are changes and update clients accordingly.

IS-05 manages connections between senders and receivers allowing changes to be immediate or set for the future. It allows, for example, querying of a sender to get the multicast settings and provides for sending that to a receiver. Naturally, when a change has been made, it will update the IS-04 registry.

IS-08 helps manage the complexity which is wrought by allowing all audios to flow separately from the video. Whilst this is a boon for flexibility and reduces much unnecessary processing (in extracting and recombining audio) it also adds a burden of tracking which audios should be used where. IS-08 is the answer from AMWA on how to manage this complexity. This can be used in association with BCP-002 (Best Current Practice) which allows for essences in the IS-04 registry to be tagged showing how they were grouped when they were created.

Jed looks next at IS-09 which he explains provides a way for global facts of the system to be distributed to all devices. Examples of this would be whether HTTPS is in use in the facility, syslog servers, the registration server address and NMOS versions supported.

Security is the topic of the last part of talk. As we’ve seen, IS-04 already allows for encrypted API traffic, and this is mandated in the EBU’s TR-1001. However BCP 003 and IS-10 have also been created to improve this further. IS-10 deals with authorisation to make sure that only intended controllers, senders and receivers are allowed access to the system. And it’s the difference between encryption (confidentiality) and authorisation which Jed looks at next.

It’s no accident that security implementations in AMWA specifications shares a lot in common with widely deployed security practices already in use elsewhere. In fact, in security, if you can at all avoid developing your own system, you should avoid it. In use here is the PKI system and TLS encryption we use on every secure website. Jed steppes through how this works and the importance of the cipher suite which lives under TLS.

The final part of this talk is a case study where a customer required encrypted control, an authorisation server, 4K video over 1GbE, essence encryption, unified routing interface and KVM capabilities. Jed explains how this can all be achieved with the existing specifications or an extension non top of them. Extending the encryption methods for the API to essences allowed them to meet the encryption requirements and adding some other calls on top of the existing NMOS provided a unified routing interface which allowed setting modes on equipment.

Watch now!
For more information, download these slides from a SMPTE UK Section meeting on NMOS
Speakers

Jed Deame Jed Deame
CEO,
Nextera Video

Video: What’s New in NMOS? – A Tutorial on the Latest in Video over IP Control and Security

The Networked Media Open Specifications (NMOS) have been developed to provide a control and management layer along side the SMPTE ST 2110 transport layer. The idea behind NMOS was to deliver an open specification to provide the software layers that abstract a lot of complexities of ST 2110 and make it easy to interface with any control system.

The NMOS family of specifications began with projects for Discovery & Registration, Device Connection Management and Network Control, but has grown to include many other important subjects such as Event & Tally, Audio Channel Mapping and Interoperable Security.

In this video, Jed Deame discusses the latest advancements including IS-08, IS-09, BCP-002, BCP-003 and IS-10. These additions allows NMOS to surpass the level of control provided in SDI while also adding a layer of security.

The following Interface Specifications and Best Current Practices are presented:

  • IS-04 (Registration and Discovery) – new features: support for GPI over Ethernet (IS-07) and authorisation signalling for security layers BCP-003-02
  • IS-05 (Connection Management) – new features: MQ Telemetry Transport and WebSocket Transport, support for supplementary externally defined parameters
  • IS-08 (Audio Mapping) – audio routing / shuffling facility
  • IS-09 (System Resources) – System ID, server priority, security with HTTPS support, advertisement of system resources such as RDS (Registration and Discovery Server)
  • BCP-002 (Grouping) – uses tag resources in IS-04 in order to achieve a natural groups of senders and receivers (e.g. to tie audio, video and metadata)
  • BCP-003-01 (Security) – uses Transport Layer Security (TLS) in order to encrypt communications between API servers and their clients
  • BCP-003-02 (Security) – covers client authorization for the NMOS APIs
  • IS-10 (Authorisation API) – accompanies the BCP-003-02 specification to restrict what users are authorized to change in an NMOS system (core technologies: PKI, HTTPS, REST, JSON, Oauth 2.0 and JWT)

The presentation finishes with the customer case study – secure KVM all over an IP network.

You can download the slides from here.

Watch now!

You might also be interested in the following videos we have published on The Broadcast Knowledge:

Speaker

Jed Deame
CEO
Nextera Video

Video: ST 2110-30 and NMOS IS-08 — Audio Transport and Routing

Andreas Hildebrand starts by introducing 2110 and how it works in terms of sending the essences separately using multicast IP. This talk focusses on the ability of audio-only devices to subscribe to the audio streams without needing the video streams. Andreas then goes on to introduce AES67 which is a standard defining interoperability for audio defining timing, session description, encoding, QOS, transport and much more. Of all the things which are defined in AES67, discovery was deliberately not included and Andreas explains why.

Within SMPTE 2110, there are constraints added to AES67 under the sub-standard 2110-30. The different categories A, B and C (and their X counterparts) are explained in terms how how many audios are defined and the sample lengths with their implications detailed.

As for discovery and other aspects of creating a working system, Andreas looks towards AMWA’s NMOS suite summarising the specifications for Discovery & Registration, Connection Management, Network Control, Event & Tally, Audio Channel Mapping. It’s the latter which is the focus of the last part of this talk.

IS-08 defines a way of defining input and output blocks allowing a channel mapping to be defined. Using IS-05, we can determine which source stream should connect to which destination device. Then IS-08 gives the capability to determine which of the audios within this stream can be mapped to the output(s) of the receiving device and on top of this allows mapping from multiple received streams into the output(s) of one device. The talk then finishes with a deeper look at this process including where example code can be found.

Watch now!

Speaker

Andreas Hildebrand Andreas Hildebrand
Senior Product Manager,
ALC NetworX