Designing IP Broadcast Systems: Part 2 - IT Philosophies, Cloud Infrastructure, & Addressing
Welcome to the second part of ‘Designing IP Broadcast Systems’ - a major 18 article exploration of the technology needed to create practical IP based broadcast production systems. Part 2 discusses the different philosophies of IT & Broadcast, the advantages and challenges of integrating cloud infrastructure, hybrid systems, and the role of layer 2 & layer 3 packet addressing.
About 'Designing IP Broadcast Systems'
This series builds on the foundations of the huge body of work already published by The Broadcast Bridge on IP. The 18 article collection delves deeper into various aspects of how IP based systems work, with detailed technical explorations of key themes including; design philosophies, discoverability, hybrid systems, remote production, cloud infrastructure and software control layers.
IP for broadcasting is no longer a theoretical concept. It is proving its worth in television stations throughout the world. But transitioning to IP has its challenges, even for those lucky enough to work on greenfield sites. The abstraction of the video and audio essence from the underlying timing plane is presenting many issues whose solutions were often taken for granted in SDI and AES infrastructures, but the learning curve needed to make IP systems work for broadcasting is well worth the investment.
Fundamentally, we’re distributing synchronous video and audio over an asynchronous network, and in doing so, we’re effectively destroying the timing plane. To reconstruct the video and audio signals at the destination we must synthesize a timing system that operates over an asynchronous packet switched network. Switch buffers with indeterminate latencies conspire against this goal so packet jitter and loss become something we have to work with.
To achieve the promise of scalability, flexibility, and resilience, a change in mindset is required as broadcast engineers expect video and audio signals to be delivered with near perfection, but IT engineers and the vendors who manufacture routing and switching equipment assume there will be some packet loss due to the dynamic nature of IP networks. Once this has been accepted, then designing IP broadcast systems becomes more achievable.
Designing IP Broadcast Systems picks up the story where ' Understanding IP Broadcast Production Networks- The Book' left it, and assumes the reader has read this earlier work.
Designing IP Broadcast systems will publish in four parts. Details of all four parts can be found HERE.
About Part 2. IT Philosophies, Integrating Cloud Infrastructure, Addressing & Packet Delivery
Part 2 is a free PDF download containing 4 articles:
Article 1 : Where Broadcast Meets IT
Broadcast and IT engineers have historically approached their professions from two different places, but as technology is more reliable, they are moving closer.
Article 2 : Integrating Cloud Infrastructure
Connecting on-prem broadcast infrastructures to the public cloud leads to a hybrid system which requires reliable secure high value media exchange and delivery..
Article 3 : With ST2110, You’ve Got The Power
Our partner Lawo discuss how a hybrid infrastructure that combines SDI and server based processing technologies, connected by an ST 2110 IP core offers the best of all worlds.
Article 4 : Addressing & Packet Delivery
Layer-3 and layer-2 addresses work together to deliver data link layer packets and frames across networks to improve efficiency and reduce congestion.
Part of a series supported by
You might also like...
Designing IP Broadcast Systems - The Book
Designing IP Broadcast Systems is another massive body of research driven work - with over 27,000 words in 18 articles, in a free 84 page eBook. It provides extensive insight into the technology and engineering methodology required to create practical IP based broadcast…
Demands On Production With HDR & WCG
The adoption of HDR requires adjustments in workflow that place different requirements on both people and technology, especially when multiple formats are required simultaneously.
If It Ain’t Broke Still Fix It: Part 2 - Security
The old broadcasting adage: ‘if it ain’t broke don’t fix it’ is no longer relevant and potentially highly dangerous, especially when we consider the security implications of not updating software and operating systems.
Standards: Part 21 - The MPEG, AES & Other Containers
Here we discuss how raw essence data needs to be serialized so it can be stored in media container files. We also describe the various media container file formats and their evolution.
NDI For Broadcast: Part 3 – Bridging The Gap
This third and for now, final part of our mini-series exploring NDI and its place in broadcast infrastructure moves on to a trio of tools released with NDI 5.0 which are all aimed at facilitating remote and collaborative workflows; NDI Audio,…