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: Building A Studio

The fundamentals of building a studio are the same whether for TV or Radio. You want to keep sound out…and in. This has forever been a challenge which doesn’t stop when the room’s built. Before it’s pressed into use, you have to lay it out correctly, considering the equipment, acoustic treatments and keep it cool.

Fortunately, experts from the BBC and Global are here to talk us through it at this Masterclass from Radio TechCon. Dave Walters from the BBC kicks off explaining how the aim of isolating your studio from physical vibration both through the structure and through gaps in the walls, floor or ceiling. Once isolated from the outside, the task is to manage the sound in the room and that calls for acoustic treatment. Dave goes through the options for lining the ceiling and walls showing that there’s acoustic treatment at all budgets. Dave finishes by highlighting that the aim is to dissipate sound and not let it bounce around. This means reflective surfaces such as glass windows need to be angled so they don’t directly point at any other hard surface.

With a deadened acoustic and a quiet atmosphere, your studio is ready to be occupied. Stephen Clarke from Global talks through laying out the studio taking into account what people do and don’t want to see. The presenter, for instance, will want to see through to the control room for visual cues during the programme, but it’s best to keep guests pointed away without distraction. This can also extend to the placement of TVs, computers and other equipment. Equipment, of course, is a concern in itself. As it generates heat and, often noise, it’s best to minimise in-studio equipment which can be done with a KVM system. Stephen talks us through a photo of the Today studio to see these principles in action.

To finish up, Global’s Simon Price talks about making holes in the studio that Dave managed to isolate. The inconvenient truth is that people need oxygen, generate heat and generate odour. Any one of those three is a good reason to put air con into the studio so Simon explains the use of baffles in ducting used to introduce the air. This absorbs sound from the air’s movement and also any external sounds that happen to come in. Simon concludes by explaining safe electrical distribution for studios keeping wiring to a minimum and reducing fire risk.

Before leaving, the team have just enough time to answer a question about studios with large amounts of glass and how to choose how ‘dead’ you want the reverb in the studio to be asking ‘can you go too far’ in minimising sound.

Watch now!
Speakers

Dave Walters Dave Walters
Head of Systems and Services: TV, Radio & Archive
BBC
Stephen Clarke Stephen Clarke
Broadcast Engineer,
Global Radio
Simon Price Simon Price
Broadcast Engineering Manager,
Global Radio

Video: Security for Discovery and Connection management of ST 2110 Media Devices

We all know you can’t prove a system is secure and you can’t eliminate bugs. What you can do, is implement the Best Current Practice for security in your IP facility. AMWA are working on defining two BCP-003 specifications to help you do just that.

Arne Bönninghoff from Riedel is our man to take us through what these two BCP specifications mean. He sets the scene by explaining the difference between confidentiality and integrity, between authentication and authorisation. BCP-003-01 deals with establishing trust (identification, integrity and authentication) as well as confidentiality. Whereas BCO-003-02 defines the best practices for authorisation.

Taking these in turn, Arne looks at how TLS works (sometimes synonymous with the old SSL technology). He shows how the certificates are exchanged and identified, highlighting the need for DNS which is recommended as part of EBU TR 1001-1. TLS is all about encryption, so we look at the encryption methods available, also known as HTTPS ciphers. Arne makes the point that out of the possibilities there are only 4 ciphers which are widely supported by all vendors. In summary, BCP-003-01 needs certificates, DNS and internet access to connect to certificate authorities.

BCP-003-02 talks to ensuring that only permitted right computers can interface with the system, for instance to use NMOS IS-04 and IS-05. It describes how tokens can be retrieved, used for access and be validated. Also called IS-10, Arne talks us through the information exchanges in the system and explains how OAuth2 + JWT come in to play. Arne cautions about being anything but ardent about implementing security best practice and concludes saying that the IS- specifications are based on IT standards like HTTP and JSON which are widely used across the IT industry.

Watch now!
Download the presentation

Speakers

Arne Bönninghoff Arne Bönninghoff
Head of IP Research,
Riedel Communications GmbH & Co. KG