ST 2110 • Routing Basics • JT-NM TR-1001-1

AIMS

• Who is AIMS? • Why IP? • SMPTE ST 2110 • Routing Basics • JT-NM TR-1001-1

Not for profit trade alliance Open to all

Funded by members

Common Goal

To foster the adoption of one set of common, ubiquitous,

standards-based protocols

for interoperability over IP in the media and entertainment industry

“…each Member agrees to publically endorse the AIMS Roadmap supported by the Alliance for IP Media Solutions as the preferred IP interoperability roadmap for the broadcast industry.” AIMS Bylaws Section 5.2

JT-NM

Reference Architecture

Technical Recommendations

Standards

To foster the adoption of the work of these organizations with regard to IP interoperability

Number and Market weight of Technical awareness companies robustness of practical adopting the implementations standard

Key advantages that make IP so desirable

10Base2 Network

Example video Standard Name Introduced Bitrates • SDI first standardized in 1989 formats

270 Mbit/s, 360 Mbit/s, SMPTE 259M SD-SDI 1989[2] 480i, 576i 143 Mbit/s, and 177 Mbit/s

• Used the same type of SMPTE 344M ED-SDI 540 Mbit/s 480p, 576p

1.485 Gbit/s, and SMPTE 292M HD-SDI 1998[2] 720p, 1080i connector technology as 1.485/1.001 Gbit/s

Dual Link HD- 2.970 Gbit/s, and 10Base2 (from 1985) SMPTE 372M 2002[2] 1080p60 SDI 2.970/1.001 Gbit/s

2.970 Gbit/s, and SMPTE 424M 3G-SDI 2006[2] 1080p60 2.970/1.001 Gbit/s SMPTE ST- 1080p120, 6G-SDI 2015[4] 6 Gbit/s 2081 2160p30 SMPTE ST- 12G-SDI 2015[5] 12 Gbit/s 2160p60 UHD 2082 SMPTE ST- 2160p120, 24G-SDI DEV 24 Gbit/s 2083* 4320p30

• A variety of speed choices and therefore cost choices exist: – 1 Gigabit Ethernet – 10 Gigabit Ethernet – 25 Gigabit Ethernet – 40 Gigabit Ethernet 400x – 50 Gigabit Ethernet performance in 12 years* – 100 Gigabit Ethernet – 200 Gigabit Ethernet – 400 Gigabit Ethernet

• Many Broadcasters want to use Ethernet to replace SDI

Flexible Multi-format COTS IT hardware Software media processing Virtualized Hybrid cloud

…really just a data center

One cable vs Many cables

One 10 GbE = 7 HDs

One 100 GbE = 79 HDs

One 400 GbE = 316 HDs

Converged Infrastructure Extensible Workflow

• No Bespoke / Proprietary Connectivity • Facilitate High and Low Bit Rate • Unified Transport for Ingest, Transports on Common Fabric Transcoding, Contribution and OTT • New Media Business via IP Transport • Broadcast, Post Production and • Ingest Direct to Consumer and Graphics on Common Infrastructure Streaming Services • Take Advantage of IT Technology • Second Screen and Targeted Media Economics Opportunities

Video Audio

Data We can how accomplish almost everything IP Routing/Distribution we need in IP over COTS networks that once needed proprietary interfaces, Control cabling and infrastructure to work Monitoring Management

Video

Audio Uncompressed media over IP is the last Data mainstream workflow requirement that is making the transition to IP IP Routing/Distribution Control The other capabilities have existed in one form or another for many years Monitoring Management

Video SMPTE ST 2022 SMPTE ST 2110 Audio SMPTE ST 2059 Data AES 67 IP Routing/Distribution IGMP, AMWA NMOS IS-04, IS-05, IS-06, IS-07 Control Proprietary protocols

Monitoring SNMP, sFlow, OpenConfig, Proprietary protocols

Management Proprietary protocols

Established Protocols, Emerging Protocols, Proprietary Protocols

IP Innovations Video SMPTE ST 2022 SMPTE ST 2110 Audio SMPTE ST 2059 Data AES 67 IP Routing/Distribution IGMP, AMWA NMOS IS-04, IS-05, IS-06, IS-07 Control Proprietary protocols

Monitoring SNMP, sFlow, OpenConfig, Proprietary protocols

Management Proprietary protocols

Established Protocols, Emerging Protocols, Proprietary Protocols

AIMS Standard / Spec Description Status Roadmap SMPTE ST 2110-10 Timing and definitions – SMPTE ST 2059 aka PTP Published P Uncompressed active video - RFC-4175 transport of SMPTE ST 2110-20 Published P video SMPTE ST 2110-30 Uncompressed PCM audio - AES-67 transport of audio Published P SMPTE ST 2110-40 Ancillary data - IETF ANC 291 Published P SMPTE ST 2110-21 Video Sender Traffic Shaping for uncompressed video Published P SMPTE ST 2110-22 Carriage for compressed video over IP Published P SMPTE ST 2110-31 Full AES3 transport Published P SMPTE ST 2022-6 SDI over IP – Video, audio and data interleaved Published P SMPTE ST 2022-7 Seamless Protection Switching – redundant flows Published P SMPTE ST 2022-8 SMPTE ST 2022-6 + AES67 audio Published High-performance streaming audio-over-IP AES67 Published P interoperability AMWA IS-04 Discovery and registration of media flows V1.2 approved P AMWA IS-05 APIs for managing connection between compatible flows V1.0 approved P

• SMPTE ST 2022-6 is established as the baseline for interoperability – Simple SDI over IP implementation

• SMPTE ST 2110 adds greater flexibility, separating video, audio and data into different flows – Greater flexibility in your workflow – Bandwidth efficiency

• SMPTE ST 2110-22 adds constant bit-rate compressed video

Promoted by: In association with:

• Multicast – Fast Joins & Leaves • Non Blocking Ethernet Switch & Fabric • PTP in Boundary Mode

• Large Buffers Ethernet SDI Router • Automation Fabric • Telemetry • Reliability • Industry Standard Protocols • Troubleshooting

• Cloud Economics Handy Facts 48 x100G = 1500x1500 @ 3G • Speed Innovation 144 x100G = 4600x4600 @ 3G 32 HD ~ 50G 16 3G ~ 50G Each way!

Elements can be independently produced and flexibly composed!

Video Flow Video Source

Source Audio Flow Device Audio Source

Data Flow

Timestamp Data Source Flow ID PTP Timebase (ns granularity) Payload

From the BBC “IP Studio” Model

Uncompressed and line based compression Uncompressed @ ~ 4:1 to 6:1 with JPEG-XS and VC-2 I-frame codec (JPEG 2000, AVC-I, ProRes)

Long-GOP Codec (MPEG-2, H.264, VP-9, HEVC, AV1)

* Curve is approximate…

• Network Interface Requirements – IP – RTP – UDP Packet size limits (both “normal” and “jumbo” packets) • System Timing Model – IEEE 1588 Precision Time Protocol (PTP) as a common sync clock – How PTP time relates to RTP timestamps – What an RTP timestamp “means”, e.g. camera “image capture time” • Session Description Protocol (SDP, RFC 4566) – How a flow can be described in a textual format

©2018 Harmonic Inc. All rights reserved worldwide. 31 SDP: What is it? v=0 o=- 123456 2 IN IP4 192.168.98.31 s=Harmonic 1080i video+audio+data SDP • SDP = Session Description i=Includes 1080i@25 Hz video, one stereo pair of PCM audio, and ANC t=0 0 Protocol a=group:DUP one other a=recvonly • It is one or multiple .sdp files m=video 30000 RTP/AVP 96 i=1080i25 video stream • One SDP per kind of stream c=IN IP4 239.98.10.211/64 a=rtpmap:96 raw/90000 a=mid:one • Contain multicast address a=fmtp:96 interlace; sampling=YCbCr-4:2:2; width=1920; height=1080; exactframerate=25; depth=10; TCS=SDR; colorimetry=BT709; PM=2110GPM; TP=2110TPW; SSN=ST2110-20:2017 – Video with port and payload a=ts-refclk:ptp=IEEE1588-2008:00-04-b3-ff-fe-f0-26-89:127 – Audio with port, payload, x tracks... a=mediaclk:direct=0 m=audio 50000 RTP/AVP 97 – Anc datas with port and payload i=PCM audio pair c=IN IP4 239.98.11.211/64 – PTP MacAddress:domain a=rtpmap:97 L24/48000/8 a=mid:one a=fmtp:97 channel-order=SMPTE2110.(ST,ST,ST,ST) • Created automatically when a Tx a=ptime:1 a=ts-refclk:ptp= IEEE1588-2008:00-04-b3-ff-fe-f0-26-89:127 starts a=mediaclk:direct=0 • Needed when joining multicast m=video 50040 RTP/AVP 100 i=Ancillary data stream address c=IN IP4 239.98.13.221/64 a=rtpmap:100 smpte291/90000 a=mid:one a=ts-refclk:ptp= IEEE1588-2008:00-04-b3-ff-fe-f0-26-89:127 a=mediaclk:direct=0

• Based on RFC 4175 • Only the “Active” image area is sent – no blanking • Image sizes: up to 32k x 32k • Colorimetries: Y’Cb’Cr’, RGB, XYZ, I’Ct’Cp’ • Sampling: 4:2:2/10-bit, 4:2:2/12-bit, 4:4:4/16-bit, and more • Supports High Dynamic Range aka HDR (PQ & HLG)

Vertical VANC Blanking Metadata

HANC Audio

Horizontal Blanking

Sync Signals Active Video

Line # & CRC

Samples per 10-bit 4:2:2 10-bit 4:4:4 12-bit 4:4:4 Lines fps Line Gbps Gbps Gbps

3840 2160 50 8.3 12.4 14.9 3840 2160 59.94 9.9 14.9 17.9 3840 2160 120 19.9 29.9 35.8 7680 4320 50 33.2 49.8 59.7 7680 4320 59.94 39.8 59.7 71.6 7680 4320 120 79.6 119.4 143.3

(Video Only) Ethernet Type: 10 GbE 25 GbE 50 GbE 100 GbE 200 GbE

• References AES67, which references RFC 3190 • Supports a range of bit depths and sampling rates • Typically 24-bit, 48 kHz • Use at least 8 channels per stream

• SMPTE Ancillary Data includes: • Time Code • Closed Captions • SCTE 104 Ad Triggers • Active Format Description (AFD) … and much more!

• References RFC 8331 RTP Payload for ANC data

• Routes for signals are made by direct control of the crosspoint matrix • Router tables help sub-divide the router

Routing Controller

• Edge devices make the switch – receiver device switch for frame alignment • The routing controller communicates with edge devices only – not with the router itself • The routing controller tells a receiver to switch to a different multicast source

Router n Local Multicast Router Source Device Receiver Device

PIM IGMP RTP Multicast Traffic

• Huge Bandwidth – e.g. Arista 7516R = 150Tbps, 69 Bpps • Non-Blocking – IP switches can handle all the ports combined bandwidth at the same time, and all full capacity • IGMPv3 (Internet Group Management Protocol) – Common protocol used by clients and adjacent routers to establish multicast group memberships (to join and leave data flows on a network) • PIM-SSM (Protocol Independent Multicast – Source Specific Multicast) – Creates connections between switches and subnets. Allows clients to receive multicast traffic from the source if it is multiple hops away

• Broadcast: One to all within the subnet

• Unicast: One to one, routable. Destination defined by sender.

• Multicast: One to none, one or many, routable. Destination defined by receiver!

• Multicast is a good fit for live uncompressed media – Typically there is a one to many fan out – The senders do not know who needs to consume their output – More efficient for sending endpoints, and network infrastructure – no traffic redundancy – Receiver redundancy is easy to achieve

• Spectrum X supports TR-1001-1 for smarter JT-NM TR-1001-1 connection to media networks

System Environment & • Plug into a compliant network and Spectrum X is Device Behaviors available to use in minutes without manual configuration* Network Environment – Video, audio and data flows are available as inputs PTP, DHCP, LLDP, DNS-SD and outputs automatically Discovery & Registration – Control systems can route I/Os without manual AMWA NMOS IS-04 configuration Connection Management AMWA NMOS IS-05 Critical System Parameters System Resource

“For the purposes of engineering, constructing and maintaining professional media facility infrastructures… the industry requires the ability to easily integrate equipment from multiple vendors into a coherent system”

JT-NM TR-1001-1 Testing at Riedel, Wuppertal, Germany

• Event took place week of 19 August • First event of its kind to test TR-1001-1 compliance

• http://jt-nm.org/jt-nm_tested/

http://jt-nm.org/documents/JT-NM_Tested_Catalog_ST2110_Full-Online-2019-09-10.pdf http://jt-nm.org/documents/JT-NM_Tested_Catalog_NMOS_TR1001_Full-Online-2019-09-10.pdf

IS-04 Discovery and Registration Evolving Technology • AWMA defined methods for device discovery by DNS on a network and registration of flows with a central registration server • Easy method to identify when flows are available or not as devices are connected and disconnected from a network

IS-05 Connection Management Evolving Technology • AMWA defined APIs for managing connection between compliant devices with compatible flows

IS-04 and IS-05 specifications enable Error free routing, automated the automation of routing flows monitoring, plug and play hardware

Endpoint Connection Management

IS-05

Endpoint Control Identity and System SDP

IS-04 Registration & Discovery Service

Nodes Devices Senders Receivers

Lawo Node 1 Lawo vMatrix Lawo Tx1 Lawo Rx1 AMWA IS-04 & IS-05 Lawo Node 2 Lawo Tx2 Lawo Rx2 • Endpoint Real Time Identity & Capabilities Harmonic 1 Harmonic Harmonic Tx1 Harmonic Rx1 • Configurable Text for Relevancy Harmonic 2 Harmonic Tx2 • Playout and Automation Integration Harmonic Tx3

• Devices “advertise” their presence on the network Discovery of Compliant • SDP file for each device defines flows available Flows • No longer a question whether a flow is present or not

• Flows are discovered via DNS and can be registered with a central registration server Registration of Flows • Control systems how have a central service to determine what flows are available and which ones can be connected to each other

• APIs for managing connection between compliant devices with Connection Management compatible flows • Standardizes the connection method for controlling flow I/O

• Routing can be automated: no more manual router tables Impact of IS-04 & IS-05 • Information such as resolution and frame rate known in advance, which removes the guesswork from knowing what input can go to what output

Protocols • VDCP Serial Control – 1x RS422 port per channel • Spectrum’s API is well established • Spectrum API • Modern networks enable reliable, – Player API – real time channel control predictable performance – Media API – data and management • Cabling and control infrastructure • GPI are simplified – Input and output triggers • 8 triggers per SDI card (assignable, average 4 per channel) • Conventional control is still there • 1 or 2 SDI cards per Chassis for systems in transition

API (IGMP underneath) • Supports leave and join of a multicast address • Supports 2x video flows per input * • Destination device controls the switch

Switching • Wait 4 to 5 frames after join to switch to a live input * – To record – To switch from File to Live, or Live to Live

IS-04 and IS-05 • A set of evolving specifications (also IS-06, which is not relevant to Harmonic) • Support for SDP files

• Open Source Software for AMWA IS-04 and IS-05 • Various NMOS implementations are available in different languages • All available under Apache 2.0 license

Creator Language Licence URL Description BBC R&D Python Apache 2.0 https://github.com/bbc/nmos- IS-04, IS-05, IS-10, apis BCP-002, BCP-003 Streampunk Javascript(NodeJS) Apache 2.0 https://github.com/Streampunk IS-04 v1.0 Registry Media /ledger and Node Sony Javascript Apache 2.0 https://github.com/sony/nmos- IS-04 and IS-05 (AngularJS) js Client Sony C++ Apache 2.0 https://github.com/sony/nmos- IS-04, IS-05, IS-07, cpp IS-09, BCP-002/003

• Technical Recommendation: TR-1001-1:2018 v1.0 http://www.jt-nm.org/documents/JT- NM_TR-1001-1:2018_v1.0.pdf • AIMS-Guidelines-for-IP (Alliance for IP Media Solutions Key Considerations for Design and Operations – Updated MARCH 2018) • EBU R 152: Strategy to accelerate adoption of an open discovery & connection protocol (NMOS) March 2019 • NMOS docs, API and tools: – https://github.com/AMWA-TV/ – https://amwa-tv.github.io/nmos/