This session is a case study of a new IP production studio for a major broadcast in the US and will present the architecture, best practices and lessons learned from a real live studio production using an IP infrastructure.

File Type: pdf
Categories: Case Study
Presenters : Ammar Latif - Cisco
Year : 2019
dlp_document_download : I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 C U R A T E D B Y The Good and The Ugly IP Studio Production Case Study Ammar Latif Principal Architect Media team – Cisco Systems I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 Live Studio Production Infrastructure 2 REST REST REST Cisco IP Fabric for Media REST • Open Scalable SMPTE 2110 Network • SDI -to -IP Network Infrastructure • Fully Non -Blocking Multicast Architecture • Open APIs • Multicast Flow Visibility • Realtime Telemetry & Analytics Broadcast Controller Cisco’s Media Controller I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 IP Fabric for Media 3 Single Spine, Multi -Leaf Uplinks to Spine Design Considerations: • The total bandwidth between each leaf and spine must be equal or greater than the bandwidth between leaf and endpoints to ensure a true, non -blocking fabric. • This model provides a symmetrical I/O count (sender BW = receiver BW) • Traffic between senders and receivers on the same leaf does not hit the spine, but this should not play into BW calculations for non - blocking Senders Receivers I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 IP Fabric for Media 4 Multi -Spine, Multi -Leaf Uplinks to Spine Senders Receivers I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 IP Fabric for Media 5 Multi -Spine, Multi -Leaf, Redundant Networks with 2022 -7 Senders Receivers IPFM X IPFM Y A SMPTE 2022 -7-enabled transmitter duplicates the input stream and sends it via two different paths to the destination receiver. The receiver (also SMPTE 2022 -7 enabled) combines the streams from both paths and reconstructs the original stream. If a packet was lost on path 1, the packet is taken from path 2. In case path 1 is completely gone, the entire stream is taken from path 2 and vice versa. Note: 2022 -7 can apply to various RTP streams, including SMPTE 2022 -6, AES -67, SMPTE ST -2110 and TR -01 based environments. I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 Cisco’s Non Blocking Multicast (NBM) 6 • NBM brings bandwidth awareness to PIM • Traffic load balanced using flow bandwidth as a parameter • Prevents link oversubscription by ensuring flows more than link capacity is not sent I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 IP Fabric for Media – Remote Leaf 7 Remote site Senders Receivers Receivers Senders I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 Media Controller : Streaming Telemetry 8 IPFM X IPFM Y Management LAN Connection to all IPFM switch management ports (out of band) Use DCNM’s Media Controller to: • Set host and flow policies • View network topology and link saturation of ports I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 9 I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 Media Controller: Multicast Flow Visualization 10 I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 Flow Statistics 11 I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 IP Fabric for Media : Diagnostics 12 IPFM X IPFM Y Diagnostics LAN Nexus Data Broker I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 Timing and PTP Distribution 13 Design Considerations: • What profile(s) do you need to support? • Do you need PTP outside of your IPF networks (ex: Corp or Production LAN)? • Both X & Y fabrics must be fed with the same PTP sources and priorities • Transparent vs. Boundary Clock modes for switches • Black Burst and Tri -level considerations • Line buffers, frame buffers and asynchronous signals GM 1 GM 2 PTP leaf PTP PTP Leaf Spine 1x Spine 2x Boundary Boundary Leaf 1 -n Y Boundary -> Spine 1y Spine 2y Leaf 1 -n Y I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 IP Fabric for Media : Multiple PTP Profiles 14 GM Leaf Spine Leaf Boundary Clock SyncDelay RequestDelay Response 1588v2 ST2059 AES67 1588v2 I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 IP Fabric for Media : PTP monitoring • PTP monitoring is a challenge ‒ Correction ranges ‒ Changes in GMs ‒ Rogue GMs • Switch level monitoring : ‒ Scripting to monitor and alert on PTP • Fabric wide monitoring ‒ PTP Streaming telemetry to Media Controller 15 I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 Timing and Latency in a Hybrid Plant 16 SDI Source 2110 Gateway Leaf Switch Spine Switch Leaf Switch 2110 Gateway SDI Switcher Ref -1 Ref -2 Timing Considerations: • PTP resiliency • A typical SDI switcher has +/ -½ line tolerance • What is my IPFM propagation delay? • What is my Gateway latency? • Does my gateway, or IP end -point have a frame buffer? • What is my total acceptable end -end latency? I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 The Broadcast Engineering Experience • 3 rd party native IP senders can integrate without concern for control • Clean , quiet and vertical accurate switching: Make before Break vs. Break before Make • Switch/Route performance • IP addressing for 2022 -7 • Managing audio in TR -04 and TR -03 designs • AMWA NMOS IS -04 and IS -05 • Moving 2022 -6 and ST -2110 inter -facility 17 I P S H O W C A S E T H E AT R E AT I B C 2 0 1 9 : 1 3 –1 7 S E P T 2 0 1 9 Thank you Thank you to our Media Partners Presenter Name, Organization Email and phone number (recommended) 18
Downloads: 3