“OTT over the air” – ATSC 3.0 deployment has started in the US and has been deployed in Korea. Promising to bring interactivity and ‘internet-style’ services to broadcast TV, moreover allowing ‘TV’ to transition to mobile devices. To help understand what ATSC 3.0 enables, NABShow Live brings together Sinclair’s Mark Aitken, Bill Hayes from Iowa Public Television and SMPTE’s Thomas Bause Mason all of which are deeply involved in the development of ATSC 3.0.
The panelists dive in to what ATSC 1 was and how we get to 3.0, outlining the big things that have changed. One key thing is that broadcasters can now choose how robust the stream is, balanced against bandwidth. Not only that but multiple streams with different robustnesses are possible for the same channel. This allows ATSC 3.0 to be tailored to your market and support different business models.
ATSC 3.0, as Bill Hayes says was ‘built to evolve’ and to deal with new standards as they come along and was at pains to point out that all these advancements came without any extra spectrum allocations. Thomas outlined that not only is SMPTE on the board of ATSC, but the broadcast standards upstream of distribution now need to work and communicate with downstream. HDR, for instance, needs metadata and the movement of that is one of the standards SMPTE has formed. As Mark Aitken says ‘the lines are blurring’ with devices at the beginning of the end of the chain both being responsible for correct results on the TV.
The session ends by asking what the response has been from broadcasters. Are they embracing the standard? After all, they are not obliged to use ATSC 3.0.
Thomas say that interest has picked up and that large and small networks are now showing more interest with 50 broadcasters already having committed to it.
The transition from point-to-point SDI based infrastructure to IP essence flows requires a very different approach to fault-finding. Although new IP diagnostic tools are already available on the market, engineers need combined broadcast and IT knowledge to fully understand the flow of video, audio and data across the switching fabric – including packet jitter, latency, and buffer over/underflows causing dropped packets.
In this video Michael Waidson from Tektronix presents methodologies involved in monitoring IP media networks. The following topics are covered:
Strategies for choosing IP Address, Port Number and Payload Type for easier identification of the streams
Troubleshooting basics (fibres and SFPs types, checking switch ports)
Here to kill the idea of SDNs – Spreadsheet Defined Networks – is TR-1001 which defines ways to implement IP-based media facilities avoiding some typical mistakes and easing the support burden.
From the JT-NM (Joint Taskforce – Networked Media), TR-1001 promises to be a very useful document for companies implementing ST-2110 or any video-over-IP network Explaining what’s in it is EEG’s Bill McLaughlin at the VSF’s IP Showcase at NAB.
This isn’t the first time we’ve written about TR-1001 at The Broadcast Knowledge. Previously, Imagine’s John Mailhot has dived in deep as part of a SMPTE standards webcast. Here, Bill takes a lighter approach to get over the main aims of the document and adds details about recent testing which happened across several vendors.
Bill looks at the typical issues that people find when initially implementing a system with ST-2110 devices and summarises the ways in which TR-1001 mitigates these problems. The aim here is to enable, at least in theory, many nodes to be configured in an automatic and self-documenting way.
Bill explains that TR-1001 covers timing, discovery and connection of devices plus some of configuration and monitoring. As we would expect, ST-2110 itself defines the media transport and also some of the timing. Work is still to be done to help TR-1001 address security aspects.
VP Product Development,
Building security into your infrastructure is more and more important for broadcasters with many now taking very seriously a topic which, only 6 years ago, was only just being discussed. Attacks on broadcasters like TV5 Monde have brought into focus that it’s not just copmanies who have high value rights who are ripe for breach – attacking a broadcaster is a high impact way of getting your message accross.
We have seen how the internet, which was built on very open and trusting protocols, has struggled in recent times to keep abuse to a minimum and to implement security to keep data safe and to keep out unauthorised persons.
And so AMWA is looking at its recent specifcations to ensure there is a clear and interoperable way of implementing security. The benefit of IP should be that that as an industry we can benefit from the work of other industries before us and here, having based these specifications on HTTP interfaces, we can do exactly that. Just like sites on the internet can implemnt HTTPS, we, too use the same mechanism of security certificates and TLS (colloquially known as SSL) encryption to ensure that not only is our data encrypted but also that no one can impersonate anyone else on the network.
Simon Rankine from BBC R&D explains the work he has been part of in defining this secure interface which not only protects from mal-intentioned actors, but also offers some protection from accidental mistakes by staff.
Simon gives a good intorduction to not only how this is a benefit but also how the underlying mechanisms work which are just as applicable to the NMOS APIs as they are to general websites.