When ORF needed to build their FÜ22 OB truck, they chose to use IP technology and SMPTE ST 2110 for media transport. In this presentation, we explore the decisions that have been made and the reasons behind switching to IP. We also talk about some lessons learned while planning, integrating, and testing the system.

File Type: pdf
Categories: Case Study
Presenters : Harmut Opfermann - BFE/Median
Year : 2019
dlp_document_download : C U R A T E D B Y I P S H O W C A S E T H E AT E R AT N A B – A P R I L 8 -11 , 2 01 9 Building a large OB - Truck using SMPTE ST 2110 Hartmut Opfermann, Head of Division Broadcast IT BFE Studio und Medien Systeme Agenda • The Customer • The Task • The Decision • The Challenge • The Conclusion 2 The Customer Österreichischer Rundfunk - ORF • Public Broadcaster in Austria • 8 million Viewers in Austria • 4 TV Channels 24x7 • 9 Regional Channels • 12 Radio Channels 3 The Task Building a new OB -truck for sports, music and entertainment • Cost -effective solution • Some equipment needs to be reused • Workflows for operators shouldn‘t change • Needs to work with the existing infrastructure at ORF headquarters (which is still SDI -based) • The design and technologies need to be scalable to serve as a blueprint for larger systems • Use standard products, no custom development 4 The Decision • Three different designs were evaluated: ‒ Based on an SDI router ‒ Based on a proprietary network technology ‒ Based on IP • Decision Criteria ‒ Must be economically viable ‒ Functionality ‒ Must have a certain maturity ‒ Gaining experience with new technology (for upcoming larger projects) ‒ Flexibility (Ease of upgrade to UHD, ability to change/add functionality) 5 The Decision – Go for IP! • Three different designs were evaluated: ‒ Based on an SDI router ‒ Based on a proprietary network technology ‒ Based on IP • Decision Criteria ‒ Must be economically viable ‒ Functionality ‒ Must have a certain maturity ‒ Gaining experience with new technology (for upcoming larger projects) ‒ Flexibility (Ease of upgrade to UHD, ability to change/add functionality) 6 The Challenges You need SDI -IP -Converters • Converters often include needed processing equipment • As more and more devices add native IP interfaces, you will need less and less of Converters: Between "Contract Award" and "Design Freeze", the number of converters was reduced by 1/3 due to changing to newer devices with native IP interfaces. • A good broadcast control system can provide a seamless experience 7 The Challenges Devices keep evolving rapidly! • New IP -capable Boards • New IP -capable Device Generations • New Software Versions with new (required) features • New Control Interfaces (NMOS!) => You have to freeze your design at some point! 8 The Challenges Defining "Software defined Hardware" I • Several vendors have developed FPGA -based flexible processing hardware that can change its internal structure based on the software loaded on the box and/or the configuration applied. • There is a trade -off between flexibility and complexity of configuration. • Because flexibility was one of the decision criteria, the device chosen has complex configuration options. 9 The Challenges Defining "Software defined Hardware" II • Essentially you have a "Subsystem in a Box" with router(s), frame synchronizers, de -/embedders, delays, color correction etc. which you have to design in itself. • If you use a lot of these devices (37 in our case), you have to decide how many different designs you want/need to maintain. 10 The Challenges Defining "Software defined Hardware" III • We use 3 different designs: ‒ Multiviewer ‒ 18 in / 2 out ‒ 10 in / 10 out • Not all features (frame sync, delay, color correction) are used (and licensed) in every device 11 The Challenges IP Address Management • Currently a manual Task • Requires a lot of management and configuration effort • Needs to be automated for larger projects (ideally using DHCP and IS -05, see JT -NM TR -1001 -1) 12 The Challenges Audio Channel Management • How many audio channels per stream? • =1: Many multicast streams • >8: exceeds ST 2110 -30 Level A (minimum requirement for standard compliance) • Balance limits of stream receivers vs. channels on devices • Standard audio stream width was chosen to be 8 channels 13 Stream Receivers vs. Audio Channels 1 audio channel per stream 14 Device A1 16 Audio Channels Device B 16 Device An 16 Audio Channels 16 … Needs n x 16 Receivers, which can exceed the device‘s capabilities for relatively small n Stream Receivers vs. Audio Channels 16 audio channels per stream 15 Device A1 16 Audio Channels Device B 1 Device An 16 Audio Channels 1 … Needs n x 2 Receivers, making more efficient use of the receiver ressources Stream Receivers vs. Audio Channels 16 audio channels per stream 16 Device A1 2 Audio Channels 1 Device An 2 Audio Channels 1 … Has to allocate n x 16 audio input channels , which might waste limited ressources Device B Stream Receivers vs. Audio Channels 8 audio channels per stream 17 Device A1 2 Audio Channels Audio Shuffler 1 Device An 2 Audio Channels 1 … Optimum usage of receivers and audio input channels Device B ceil (2n/8) The Challenges How to switch on and off 18 How to Switch on and off 19 SDI Router … … How to Switch on and off 20 Controller Input Input Output Output Cross bar … … How to Switch on and off 21 SDN - Controller Sender Sender Receiver Receiver Switch … … The Challenges Training • New topics • Even some fundamentals are new • There is a lot of uncertainty because people are unfamiliar with the technology. • Troubleshooting procedures are different 22 The Challenges Synchronization • PTP requires more configuration effort than Blackburst ‒ JT -NM TR -1001 -1 addresses this to a certain extend through a central system resource • Syncing PTP and Blackburst ‒ Operation with external Blackburst is well defined (EG 2059 -10), but there are devices that operate differently ‒ Redundancy mechanisms for PTP and BB operate independently and might produce undesired results. 23 Syncing PTP and Blackburst 24 SPG/PTP 1 SPG/PTP 2 BB BB BB1 PTP PTP PTP1 GPS GPS Both BB signals are valid, I‘ll use the first one PTP 1 wins the BMCA, I‘ll stay quiet Syncing PTP and Blackburst Synchronization 25 SPG/PTP 1 SPG/PTP 2 BB BB BB2 PTP PTP PTP1 GPS GPS PTP 1 wins the BMCA, I‘ll stay quiet BB1 has failed, I‘ll use the other one Syncing PTP and Blackburst Synchronization 26 SPG/PTP 1 SPG/PTP 2 BB BB BB1 PTP PTP PTP2 GPS GPS I have a better clock class , I‘ll take over I don‘t have GPS – I‘ll change my clock class Both BB signals are valid, I‘ll use the first one Syncing PTP and Blackburst • Solution #1 (from vendor!): Buy two more SPGs and separate PTP generation from PTP to BB conversion (pair#2 will always generate the BB from the PTP GM) (additional money and space required) • Solution#2: Have an external control system manipulate PTP priority to follow BB change over unit. 27 The Conclusion • We are in a transitional period • IP based production systems are viable, however need careful design • Adaption and some work arounds are still needed while technology matures • It is essential to build knowledge of the new technology on all levels 28 C U R A T E D B Y I P S H O W C A S E T H E AT E R AT N A B – A P R I L 8 -11 , 2 01 9 Thank You Hartmut Opfermann, BFE Studio und Medien Systeme hopfermann@bfe.tv , +49 174 3299 040
Downloads: 10