1 / 58

Nov 2018

IP Installs… So what have we learned?. Nov 2018. What have we learned?. It works! Hundreds of sites on the air Varying Technologies and Standards 2022-6 TR-04 2110. What have we learned?. It requires a whole new type of engineer SDI knowledge IP knowledge Switch configuration

bergen
Télécharger la présentation

Nov 2018

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IP Installs… So what have we learned? Nov 2018

  2. What have we learned? • It works! • Hundreds of sites on the air • Varying Technologies and Standards • 2022-6 • TR-04 • 2110

  3. What have we learned? • It requires a whole new type of engineer • SDI knowledge • IP knowledge • Switch configuration • Topology • Flow Controls • Standards Knowledge • SDN • IGMP • Proposed SMPTE 2110 • PTP SMPTE 2059

  4. What have we learned? • It requires a whole new type of engineer • Knowledge of the future • AMWA • IS-04 • IS-05 • IS-06 • IS-06 • JT-NM • IEEE • Streaming Video Alliance

  5. JT-NM Roadmap of Networked Media Open Interoperability * NAB14 IBC14 NAB15 IBC15 NAB16 IBC16 NAB17 IBC17 NAB18 IBC18 NAB19 IBC19 NAB20 IBC20 Cloud-fit Open, secure, public/private (on-premises) cloud solutions Non-media-specific IT Self-describing, open APIs suitable for virtualization IV. Dematerialized facilities** LEGEND: Standard / Specification Cloud Security for Media Companies EBU R146 Widely available Published Agile Media Machine Core AMWA Content Model and APIs Study / Activity “Top-Ten” Security Tests JT-NM Security Recommendations Recommended minimum Security Tests EBU R148 III. Network & Resource Management System-level management and automated provisioning for flexible and sharable infrastructure at scale AMWA IS-07 Including mapping to ST 2110 AMWA Timing and Identity Network Control AMWA IS-06 Connection management AMWA IS-05 Discovery & Registration AMWA IS-04 More flexible and efficient workflows New formats like UHD and mezzanine compression II. Elementary flows Transport of compressed video SMPTE ST 2110-nn✚ SMPTE ST 2022-6 Transport of separate essences VSF TR-03 SMPTE ST 2110 Timing profile SMPTE ST 2059 Bridging SDI over IP with Elementary flows SMPTE ST 2022-8 AES67 I. SDI over IP Current and mature technology 0. SDI ✚ Number not yet assigned. **See Dematerialized Facilities FAQ at JT-NM.org for more information. * JT-NM assumption as of March 2018 and will evolve over time. Visit JT-NM.org for the latest update. Feedback to jt-nm-info@videoservicesforum.org

  6. What have we learned? • Lots of work to do to refine it • JN-NM Full Stack • Security implications • Security best practices

  7. What have we learned? • Start to have fun with it! • Most existing builds emulate traditional workflows • Start designing new workflows leveraging new technology

  8. Studio Application WCAU Philadelphia

  9. The Challenge How do you design a facility for technology that does not even exist yet??

  10. The Challenge • Design a COTS based infrastructure solution for a Top 10 US market station. • Customers core requirements: • COTS based infrastructure - Cisco • Standards based –TR04 with ability to upgrade to ST-2110 • Mixed Reference Environment – Black Burst and PTP • Signal agnostic – HD 1080i 60, with ability to transport UHD • Future-ready - HDR (High Dynamic Range) and 1080p • Simplified wiring– multi-mode and single-mode fiber • TOR and EOR Design

  11. The Challenge • Studio technical requirements: • 3 Studios • As Much IP at the Edge as Possible • Traditional SDI switcher • Very large multi-viewer requirement • Master Control and Live Production • Extensive IP/SDI Connectivity with Video & Audio Processing • Remote Production Requirement • Large video Ingest and Playout requirement

  12. The Challenge • Studio technical requirements: • Distributed IP infrastructure • Spans multiple floors • Multiple sites around city • Uncompressed and compressed feeds • Multiple Codecs • J2k • H.264 • MPEG 2

  13. The Challenge Key that the users don’t know or care about the technology

  14. How did we do it? • Cisco Core • DCNM • Installed on Cisco UCS platform • Multiple VM’s for redundancy • Multi-Spine • Cisco 9236C • Multi-Leaf • Cisco 93180LC—EX • 2022-7 X-Y Design • Ties into broadcast LAN

  15. How did we do it? • Grass Valley Gear • IPG-3901 2x10G SDI-IP Gateways • Small failure block was key to high availability solution design • GV Node 12x40G used for vertically accurate IP switches • KMX-4901 IP Multi-viewers • LDX-86N IP Studio Cameras • GV Convergent SDN Control and Flow Management • iControl for unified facility monitoring and configuration

  16. Network Topology

  17. High Level Overview BLAN is Broadcast LAN • Management of all broadcast devices Media LAN is all TR-04 Media Transport

  18. IP Core X and Y Spines 11 + 11 Leaves Approx 150 IPG’s 10 GV Cameras 6 GV Nodes w KMX

  19. Remote Facility Requirements • Redundant 100G media trunks to remote facility • Remote facility uses third party switch • Interop was not an issue • GV Convergent controlling flows and managing bandwidth between the sites • Redundant 10G trunks to broadcast LAN for control and monitoring

  20. Modular IP I/O (2 x 10GbE SFP+)

  21. SDN • GV Convergent was used as SDN interface to DCNM • Used to configure all IP devices and end-points • High level topology view • Key to give quick and simple view of entire solution • With DCNM integration we simplified system diagnostics • Path view of media flows • Real-time data on system bandwidth • Security was key principle • Default deny ACL • Only flows that have been managed by GVC are allowed

  22. Topology View

  23. Path View Select destination to examine Source Destination Shows route through both X and Y networks

  24. So what did we learn

  25. PTP • Pick your Grand Master Clocks carefully • This GM was fixed to 1G SFP, Media Network switches only support 10G+ SFPs • Only one NIC on each GM • Required the use of extra switches to distributed PTP • PTP was distributed to Media Network, Broadcast LAN, and station operations network • On hindsight, PTP was built overly complicated • Extra PTP distribution switches added a lot to complexity

  26. PTP High Level Broadcast LAN PTP Distribution switches X-Y Media LAN

  27. PTP Distribution LAN

  28. PTP Media Network

  29. PTP into Broadcast LAN

  30. System timing (SMPTE 2059) PTP Grandmaster SMPTE ST 2059-1 and -2 Tektronix SPG8000A Camera BB / TL Slave PTP Slave * Slave Meinberg LANTIME M1000 Production Switcher 1. Multicast to Edge Devices 2. Unicast to PTP Grandmaster * Reduces multicast traffic, protects edge devices PTP Slave Ordinary or Boundary Clock (COTS dependent) IP Gateways

  31. Audio Interop was initially an issue • GV gear was using Level C • 125 packet timing • 16 channel trunks • Audio Console only supported Level A • 1ms packet timing • 8 channel trunks • Intercom was using Level C

  32. SMPTE ST 2110-30: Audio SMPTE ST 2110 – 30 (uncompressed audio – RFC 3190) Specifies the real-time, RTP-based transport of PCM digital audio streams over IP networks by reference to AES67. An SDP-based signalling method is defined for metadata necessary to receive and interpret the stream Uncompressed linear PCM audio only Relatively flexible 48kHz sampling 16 and 24-Bit depth Variable packet timing è 125us to 1ms Channel count based on packet timing è 8 channels @ 1ms vs 64 channels @ 125us Low bandwidth consumption è 8 channels x 24 bits x 48,000 samples x 1.5 (RTP) = 9.7Mbits/sec Published

  33. SMPTE ST 2110-30: Audio Levels SMPTE ST 2110 – 30 (Uncompressed Audio – RFC 3190)

  34. Lots of engineering programming errors • A lot of manual work went into programming the system • No IS-04 • No IS-05 • Static Unicast addresses • Static Multicast addresses • System had 1400 sources and 1700 destinations • Around 2000 unicast addresses had to be programmed • Along with gateways • Subnet masks • DNS • No DHCP 

  35. Lots of engineering programming errors • TR-04 System • Every source flow has 2 IP addresses • 1400 sources so 2800 Multi-cast IP’s • Mistakes were made! SMPTE 2022-6 Video Audio AES 67

  36. IP using new workflows NEP UK

  37. The Challenge • Customers core requirements: • COTS based infrastructure - Arista • Standards based –ST-2110 • Mixed Reference Environment – Black Burst and PTP • Signal agnostic – HD 1080i 60 and UHD • Future-ready - HDR (High Dynamic Range) and 1080p • Simplified wiring– multi-mode and single-mode fiber

  38. The Challenge • Technical requirements: • 8+ Simultaneous Productions • As Much IP at the Edge as Possible • IP Switchers • Very large IP multi-viewer requirement 960x80 • Extensive IP Connectivity with Video & Audio Processing • Remote Production Requirement • Flexible FPGA processing

  39. The Challenge The production will change in scale and quantity from production to production

  40. The Challenge Key that the users don’t know or care about the technology

  41. How did we do it? • COTS IP Core • Arista 7508R • Customer required COTS core • Large Single Chassis allows for simple non-blocking architecture

  42. How did we do it? • FPGA accelerated platform • Small failure block was key to high availability solution design • Flexible FPGA core • Changes based on workflow requirements

  43. How did we do it? • IP Multi-viewers • IP Switchers / Vision Mixers • SDN Control and Flow Management • Unified facility monitoring and configuration • As much IP at the edge as possible

  44. Solution Topology

  45. Solution Comprised of three designs • Broadcast Center • Remote Fly Packs • Mid-Sized Production Truck

  46. Broadcast Center Overview

  47. Broadcast Centre Configuration / Control Clients Broadcast Centre Control Panels Kahuna 4 (x2 Panels) Upstream Client Control Network IP Edge Control Servers 2x Arista 7508R IP Switches fitted with 6x line cards: 1x 36 40G ports 5x 36 100Gports Kahunas 1-3 PTP / Sync Generator PTP generation from TEK SPG8000A – use Meinberg Slave unit to circumvent high client count issues 40/50GbE links 40/50GbE links I/O Trunk 100GbE links 10GbE links 100GbE links MCR I/O MADI Conversion & Audio processing (IQAMD4010 x4 / AIPXS x2) 80x Multiviewer Head Ports (exp to 240) 960x Multiviewer Resize Engines MCR I/O SAM IP Gateways SDI I/O IQMIX25 x61, IQ Frames x7 20x MV-820 IP Multiviewers

  48. Remote Site Overview

More Related