Moving to IP can be difficult. For some, it’s about knowing where to even start. For others, it’s a matter of understanding some of the details which is the purpose of this talk from Leader US which looks at the top questions that Leader’s heard from its customer base:
How do we look at it?
How do we test it?
How is the data sent?
What is PTP?
How do we control it?
What is NMOS?
What are the standards involved?
These questions, and more, are covered in this webinar.
Steve Holmes from Lader Us details the IP relevant basics starting with the motivations: weight, cost, scale, density, and independent essences. We can then move on to the next questions covering RTP itself and how 2022-6 was built upon it. SMPTE ST 2022-6 splits up a regular SDI signal into sections and encapsulates them, uncompressed. This is one big difference from SMPTE ST 2110 where all essences are sent separately. For some, this is not a benefit, but for general broadcast workflows, it can sometimes be tricky getting them into alignment and some workflows are aimed at delivering an incoming bundle of PIDs so being able to separate them is a backward step.
With this groundwork laid, Steve explains how seamless redundancy works with SMPTE 2022-7 going on to then describe the difficulty of keeping jitter low and the importance of sender profiles in ST 2110. Steve finishes this section with a discussion of NMOS specifications such as IS-05 and IS-06. The session ends with a Q&A.
For a long time now, broadcasters have been using dark fibre and CWDM (Coarse Wavelength Division Multiplexing) for transmission of multiple SDI feeds to and from remote sites. As an analogue process, WDM is based on a concept called Frequency Division Multiplexing (FDM). The bandwidth of a fibre is divided into multiple channels and each channel occupies a part of the large frequency spectrum. Each channel operates at a different frequency and at a different optical wavelength. All these wavelengths (i.e., colours) of laser light are combined and de-combined using a passive prism and optical filters.
In this presentation Roy Folkman from Embrionix shows what advantages can be achieved by moving from CWDM technology to real-time media-over-IP system. The recent project for CPAC (Cable Public Affairs Channel) in Canada has been used as an example. The scope of this project was to replace an aging CWDM system connecting government buildings and CPAC Studios which could carry 8 SDI signals in each direction with a single dark fibre pair. The first idea was to use a newer CWDM system which would allow up to 18 SDI signals, but quite quickly it became apparent that an IP system could be implemented at similar cost.
As this was an SDI replacement, SMPTE ST 2022-6 was used in this project with a upgrade path to ST 2110 possible. Roy explains that, from CPAC point of view, using ST 2022-6 was a comfortable first step into real-time media-over-IP which allowed for cost reduction and simplification (no PTP generation and distribution required, re-use of existing SDI frame syncs and routing with audio breakaway capability). The benefits of using IP were: increased capacity, integrated routing (in-band control) and ease of future expansion.
A single 1RU 48-port switch on each side and a single dark fibre pair gave the system a capacity of 48 HD SDI signals in each direction. SFP gateways with small Embronix enclosures have been used to convert SDI outs of cameras to IP fibre – that also allowed to extend the distance between the cameras and the switch above SDI cabling limit of 100 meters. SFP gateway modules converting IP to SDI have been installed directly in the switches in both sites.
Roy finishes his presentation with possible future expansion of the system, such as migration to ST 2110 (firmware upgrade for SFP modules), increased capacity (by adding additional dark fibres ands switches), SDI and IP routing integration with unified control system (NMOS), remote camera control and addition of processing functions to SFP modules (Multiviewers, Up/Down/CrossConversion, Compression).
Leaf & spine networks have started taking over data centres in the last few years. It’s no secret that people prefer scale-out over scale-up solutions and you can see a similar approach in ST 2110 networks, when large monolithic video switches are replaced with smaller leaf and spine switches.
Leaf and spine refers to networks where a number of main, high throughput switches link to a number of smaller switches. These smaller switches tend to be aggregators and offer the promise of cheaper ports delivered closer to your equipment. The alternative to leaf & spine is monolithic switches which do have their merits, but are certainly not always the right choice.
To provide non-blocking switching in leaf & spine networks you need an SDN controller that orchestrates media flows. Advances in SDN capabilities have led to the emergence of “Purple” network architectures. In this video Gerard Phillips from Arista shows how it differs from a “Red/Blue” architecture, how path diversity is maintained and how ST 2110 IP live production or playout applications could benefit from it.
It’s important to be aware of the different uses of Layer 2 vs Layer 3:
• Layer 2 devices are typically used for audio networks like Dante and RAVENNA. A layer 2 network is a simple, scalable and affordable choice for audio flows where there are no challenges in terms of bandwidth. However, this type of network doesn’t really work for high bit rate live production video multicast since all multicasts need to be delivered to the IGMP querier which isn’t scalable.
• Layer 3 have distributed IGMP management since PIM is used on each router to route multicast traffic, so there is no more flooding network with unnecessary traffic. This type of network works well with high bit rate video multicasts, but as IGMP is not bandwidth aware, it’s best to use an SDN system for flow orchestration.
Gerard then looks at resilience:
Using 2022-7 seamless switching (plus a robust monitoring system that can provide quick, accurate information to resolve the issue)
Providing redundancy (redundant PSU, fans, fabric modules etc., redundant links between switches, ensuring that routing protocol or SDN can use these “spares”)
Dividing up failure domains
Using leaf and spine architecture (routing around failed components with SDN)
Using resilient IP protocols (BGP, ECMP)
The talk finishes up discussing the pros and cons of the different architectures available:
Monolithic systems which are non-blocking, but have a wide failure domain
Monolithic – expansion toward spine and leaf with SDN for non-blocking switching
Leaf & spine with air-gapped Red and Blue networks
Leaf & spine hybrid with Purple switches connected to both Red and Blue spines to support single homed devices
Leaf & spine Purple. Here, red and blue flows are connected to physically separate switches, but the switches are not identified as red and blue anymore. This is a converged network and an SDN controller is required to provide diverse paths flows to go to two different spines.
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)
Views and opinions expressed on this website are those of the author(s) and do not necessarily reflect those of SMPTE or SMPTE Members.
This website is presented for informational purposes only. Any reference to specific companies, products or services does not represent promotion, recommendation, or endorsement by SMPTE