SDI to IP 2110 Transition Part 1

Dr. Mohieddin Moradi
mohieddinmoradi@gmail.com
Dream
Idea
Plan
Implementation
1

− IP Technology Trend and Motivations
− IP Basics, Networks, OSI and TCP/IP Model
− MPEG-2 Transport Stream and ST 2022-x Standard
− Audio and Video Over IP Standardization
− SMPTE ST 2110 Suite of Standards
− NMOS (Network Media Open Specification)
− IP Infrastructure Interfaces Considerations
− Router Considerations for Audio and Video over IP
− Timing Issues in IP-based Systems
− Clean and Quite Switching for Audio and Video over IP
− Broadcast Controller and Orchestrator
− Compression for Video over IP
− A 12G-SDI or Full-IP OB Truck Equipment Selection
− A 12G-SDI OB Truck Designing and Integration
− A Full-IP OB Truck Designing and Integration
− Technical Challenges In All-IP Infrastructure, The Media Node Pyramid
− Some Case Studies
− Conclusion
Outline
2

https://www.slideshare.net/mohieddin.moradi/presentations
3

Most Important Technology Trend
Industry Global Trend Index
5

− The chart is visualized as a weighted index, not as a measure of the number of people that said which trend was most
important to them (a statistical weighting is applied to results, based on how research participants ranked).
− It is a measure of what research participants say is commercially important to their businesses in the future, not what they
are doing now, or where they are spending money today.
6

− The chart is visualized as a weighted index, not as a measure of the number of people that said which trend was most
important to them (a statistical weighting is applied to results, based on how research participants ranked).
− It is a measure of what research participants say is commercially important to their businesses in the future, not what they
are doing now, or where they are spending money today.
2020
Rank
2020 BBS Broadcast Global Trend
Index*
1 Multi-platform content delivery (2)
2 IP networking & content delivery (1)
3 4K / UHD (3)
4 5G (6)
5 Remote production (13)
6 Cloud computing / Virtualization (7)
7 Artificial Intelligence / Machine Learning (4)
8 Move to automated workflows (5)
9 Improvements in video compression efficiency (10)
10 Cyber Security (12)
11 High Dynamic Range (HDR) (11)
12 Centralized operations (playout, transmission etc.) (18)
13 Next generation broadcasting (ATSC 3.0, DVB T-2 etc)
(15)
14 File-based / tapeless workflows (9)
15 Targeted / Programmatic advertising (16)
16 Video on demand/SVOD (17)
17 Transition to multi-channel / immersive audio (8)
18 Virtual Reality (14)
19 Transition to HDTV / 3Gbps (1080p) operations (19)
20 Outsourced operations (playout, transmission etc.) (20)
*2019 rankings shown in parentheses
Source: Devoncroft 2020 Big Broadcast
Survey
7

− The evolution of the BBS Broadcast Industry Global Trend Index in each of the years 2011, 2015 and 2019 is shown in the
table below.
8

− The evolution of the BBS Broadcast Industry Global Trend Index in each of the years 2011, 2015 and 2020 is shown in the
table below.
9

BBS Broadcast Industry Global Project Index
− Unlike industry trend data, which highlights what respondents are thinking or talking about doing in the future, this
information provides direct feedback about what major capital projects are being implemented by broadcast
technology end-users around the world, and provides useful insight into the expenditure plans of the industry.
The result is the 2020 BBS Broadcast Industry
Global Project Index, shown below, which
measures the number of projects that BBS
participants are currently implementing or
have budgeted to implement.
10

BBS Broadcast Industry Global Project Index
− Unlike industry trend data, which highlights what respondents are thinking or talking about doing in the future, this
information provides direct feedback about what major capital projects are being implemented by broadcast
technology end-users around the world, and provides useful insight into the expenditure plans of the industry.
The result is the 2020 BBS Broadcast Industry
Global Project Index, shown below, which
measures the number of projects that BBS
participants are currently implementing or
have budgeted to implement.
11

12
5G and IP Network
5G can be significantly faster than 4G, delivering up to 20 Gbps peak data rates and 100+ Mbps average data rates.
5G is designed to support a 100x increase in traffic capacity and network efficiency.
Uplink Speed

IP Network
Direct To Home
Digital Subscriber Line
Content Delivery Network
Over-The-Top
Internet Protocol television
13

IP Motivations, Remote Production
OPerating Expenses (OPEX) 15

IP Motivations, Live Production Environment
16

IP Motivations, 40 GbE and 100 GbE Optics
*GbE – Gigabit Ethernet
17

SMPTE ST 2110 Suite, Business Benefits and Real World Rollout
3. Source:
IP in action. Updated for IBC2018.
SAMPLING OF GLOBAL ST
2110 DEPLOYMENTS
18

SMPTE ST 2110 Suite, Business Benefits and Real World Rollout
Reduced Bandwidth
Use bandwidth more efficiently when transporting
uncompressed video
Future-proof Investment
Maximize infrastructure lifespan with format-
agnostic technology
Assured Interoperability
Simplify deployment of multi-vendor IP
solutions
Maximum Efficiency
Increase resource utilization via efficient
distribution of dedicated workflows
Flexible Workflows
Route and work on video, audio and
data streams independently
19

SDI and IP Features
SDI IP
Guaranteed Bandwidth Best Effort/Prioritized
Static Circuit Connections Dynamic/Routed
Single Signal Multi-signal
Low Latency Variable Latency/Utilization
Error-free Packet Loss/Retransmission/FEC
Point To Point Any to Any
20

22
Standards Organizations
Open Standards
Internet Standards
Internet Corporation for Assigned Names and Numbers
(ICANN) Based in the United States, ICANN coordinates IP
address allocation, the management of domain names, and
assignment of other information used in TCP/IP protocols.
Internet Assigned Numbers Authority (IANA)
Responsible for overseeing and managing IP address
allocation, domain name management, and protocol
identifiers for ICANN.
The standards organizations involved with the
development and support of the Internet.
The standards organizations involved with the development
and support of TCP/IP and include IANA and ICANN.

Standards Organizations
Internet Society (ISOC)
• Responsible for promoting the open development and evolution of internet use throughout the world.
Internet Architecture Board (IAB)
• Responsible for the overall management and development of internet standards.
Internet Engineering Task Force (IETF)
• Develops, updates, and maintains internet and TCP/IP technologies.
• This includes the process and documents for developing new protocols and updating existing protocols,
which are known as Request for Comments (RFC) documents.
Internet Research Task Force (IRTF)
• Focused on long-term research related to internet and TCP/IP protocols such as Anti-Spam Research
Group (ASRG), Crypto Forum Research Group (CFRG), and Peer-to-Peer Research Group (P2PRG).
23

OSI (Open System Interconnection) Model
24

OSI (Open System Interconnection) Model
25

TCP/IP Model
Packets
(Datagrams)
Frames
Bits
Packets
(Datagrams)
OSI Basic Reference Model TCP/IP Model (Original)
Protocols in each Layrer
Link
(Network Access)
27

TCP/IP Model
28
Packets
(Datagrams)
Frames
Bits
Packets
(Datagrams)
OSI Basic Reference Model TCP/IP Model (Current)
Protocols in each Layrer
INTERNET
(NETWORK)

TCP/IP Protocol Example
29
Hypertext Transfer Protocol (HTTP): This protocol governs
the way a web server and a web client interact.
Transmission Control Protocol (TCP): This protocol
manages the individual conversations.
Internet Protocol (IP): This protocol is responsible for
delivering messages from the sender to the receiver.
Ethernet: This protocol is responsible for the delivery of
messages from one NIC to another NIC on the same
Ethernet Local Area Network

30
Hypertext Transfer Protocol (HTTP): This protocol governs
the way a web server and a web client interact.
Transmission Control Protocol (TCP): This protocol
manages the individual conversations.
Internet Protocol (IP): This protocol is responsible for
delivering messages from the sender to the receiver.
Ethernet: This protocol is responsible for the delivery of
messages from one NIC to another NIC on the same
Ethernet Local Area Network

Hypertext Transfer Protocol (HTTP)
• This protocol governs the way a web server and a web client interact.
• HTTP defines the content and formatting of the requests and responses that are exchanged between the client and server.
• Both the client and the web server software implement HTTP as part of the application. HTTP relies on other protocols to govern how the
messages are transported between the client and server.
Transmission Control Protocol (TCP)
• This protocol manages the individual conversations. TCP is responsible for guaranteeing the reliable delivery of the information and managing
flow control between the end devices.
31
Internet Protocol (IP)
• This protocol is responsible for delivering messages from the sender to
the receiver.
• IP is used by routers to forward the messages across multiple networks.
Ethernet
• This protocol is responsible for the delivery of messages from one NIC
to another NIC on the same Ethernet Local Area Network

32
Encapsulation and Decapsulation of TCP/IP Protocol
Data Link
Physical
Internet
Transport
Application
Data Link
Physical
Internet
Transport
Application

33
Data Link
Physical
Internet
Transport
Application
Data Link
Physical
Internet
Transport
Application

34
Data Link
Physical
Internet
Transport
Application
Data Link
Physical
Internet
Transport
Application

Comparison Between OSI and TCP/IP Model
Transmission
Control
Protocol/Internet
Protocol
Open
System
Interconnection
35

Link
(Network Access)
Internet
Transport
Application
Name
System
Host
Config.
Email File
Transfer
Web and
Web Server
Connection-Oriented Connectionless
Internet Protocols Routing Protocols
Messaging
Address Resolution Protocol Data Link Protocols
TCP/IP
Protocols
36
TCP/IP Protocol Suite

TCP/IP Protocol Suite, Application Layer (1)
Name System
• DNS - Domain Name System. Translates domain names such as cisco.com, into IP addresses.
Host Config.
• DHCPv4 - Dynamic Host Configuration Protocol for IPv4. A DHCPv4 server dynamically assigns IPv4 addressing information
to DHCPv4 clients at start-up and allows the addresses to be re-used when no longer needed.
• DHCPv6 - Dynamic Host Configuration Protocol for IPv6. DHCPv6 is similar to DHCPv4. A DHCPv6 server dynamically assigns
IPv6 addressing information to DHCPv6 clients at start-up.
• SLAAC - Stateless Address Autoconfiguration. A method that allows a device to obtain its IPv6 addressing information
without using a DHCPv6 server.
37

Email
• SMTP - Simple Mail Transfer Protocol. Enables clients to send email to a mail server and enables servers to send email to
other servers.
• POP3 - Post Office Protocol version 3. Enables clients to retrieve email from a mail server and download the email to the
client's local mail application.
• IMAP - Internet Message Access Protocol. Enables clients to access email stored on a mail server as well as maintaining
email on the server.
File Transfer
• FTP - File Transfer Protocol. Sets the rules that enable a user on one host to access and transfer files to and from another
host over a network. FTP is a reliable, connection-oriented, and acknowledged file delivery protocol.
• SFTP - SSH File Transfer Protocol. As an extension to Secure Shell (SSH) protocol, SFTP can be used to establish a secure file
transfer session in which the file transfer is encrypted. SSH is a method for secure remote login that is typically used for
accessing the command line of a device.
• TFTP - Trivial File Transfer Protocol. A simple, connectionless file transfer protocol with best-effort, unacknowledged file
delivery. It uses less overhead than FTP.
38

Web and Web Service
• HTTP - Hypertext Transfer Protocol. A set of rules for exchanging text, graphic images, sound, video, and other multimedia
files on the World Wide Web.
• HTTPS - HTTP Secure. A secure form of HTTP that encrypts the data that is exchanged over the World Wide Web.
• REST - Representational State Transfer. A web service that uses application programming interfaces (APIs) and HTTP
requests to create web applications.
39

TCP/IP Protocol Suite, Transport layer
Connection-Oriented
• TCP - Transmission Control Protocol.
 Enables reliable communication between processes running on separate hosts and provides reliable,
acknowledged transmissions that confirm successful delivery.
Connectionless
• UDP - User Datagram Protocol.
 Enables a process running on one host to send packets to a process running on another host.
 However, UDP does not confirm successful datagram transmission.
 Unlike the TCP, UDP adds no reliability, flow control, or error recovery functions to IP.
o Requires Upper Level Layers to provide Error Checking
 UDP headers contain fewer bytes and consume less network overhead than TCP.
40

TCP/IP Protocol Suite, Internet layer (1)
Internet Protocol
• IPv4 - Internet Protocol version 4. Receives message segments from the transport layer, packages messages into packets,
and addresses packets for end-to-end delivery over a network. IPv4 uses a 32-bit address.
• IPv6 - IP version 6. Similar to IPv4 but uses a 128-bit address.
• NAT - Network Address Translation. Translates IPv4 addresses from a private network into globally unique public IPv4
addresses.
Messaging
• ICMPv4 - Internet Control Message Protocol for IPv4. Provides feedback from a destination host to a source host about
errors in packet delivery.
• ICMPv6 - ICMP for IPv6. Similar functionality to ICMPv4 but is used for IPv6 packets.
• ICMPv6 ND - ICMPv6 Neighbor Discovery. Includes four protocol messages that are used for address resolution and
duplicate address detection.
41

TCP/IP Protocol Suite, Internet layer (2)
Routing Protocols
• OSPF - Open Shortest Path First. Link-state routing protocol that uses a hierarchical design based on areas. OSPF is an
open standard interior routing protocol.
• EIGRP - Enhanced Interior Gateway Routing Protocol. A Cisco proprietary routing protocol that uses a composite metric
based on bandwidth, delay, load and reliability.
• BGP - Border Gateway Protocol. An open standard exterior gateway routing protocol used between Internet Service
Providers (ISPs). BGP is also commonly used between ISPs and their large private clients to exchange routing information.
42

43
IP – Internet Protocol (– Layer 3)

TCP/IP Protocol Suite, Network Access Layer
Address Resolution
• ARP - Address Resolution Protocol. Provides dynamic address mapping between an IPv4 address and a hardware
address.
Data Link Protocols
• Ethernet - Defines the rules for wiring and signaling standards of the network access layer.
• WLAN - Wireless Local Area Network. Defines the rules for wireless signaling across the 2.4 GHz and 5 GHz radio
frequencies.
44

Comparison Between OSI and TCP/IP Model
45

– UDP is basically an interface between IP and upper layer processes.
– UDP is a connectionless Transport Layer
– Unlike the TCP, UDP adds no reliability, flow control, or error recovery functions to IP.
• Requires Upper Level Layers to provide Error Checking
– UDP headers contain fewer bytes and consume less network overhead than TCP.
– UDP is the transport protocol for several well known application layer protocols, including Network File
System (NFS), Simple Network Management Protocol (SNMP), Domain Name System (DNS), and Trivial File
Transfer Protocol (TFTP).
UDP – User Datagram Protocol– Layer 4
Ethernet IP UDP RTP Payload
IP UDP RTP Payload
UDP RTP Payload
RTP Payload
Payload
48

Real Time Protocol (RTP) – Layer 5
– A protocol for the transport of real-time data, including audio and video over multicast or unicast
network services (including timing reconstruction, loss detection, security and content identification).
– RTP consists of a data and a control part. The latter is called Real Time Control Protocol (RTCP).
– Applications typically run RTP on top of UDP to make use of its multiplexing and checksum services.
– RTP provides time stamping, sequence numbering, and other mechanisms to take care of timing issues.
– Through these mechanisms, RTP provides end-to-end transport for real-time data over datagram network.
– Real Time Control Protocol is used to get end-to-end monitoring, data delivery information and QoS.
IP UDP RTP Payload
UDP RTP Payload
RTP Payload
Payload
49

…bits bits bits ... Video, Audio and data Elementary Stream (ES)
PES Packet
Header Payload
Packetized Elementary Stream (PES)
Time stamps
TS Packet (188 bytes)
Header Payload
MPEG 2 Transport Stream (TS)
PID
TS Packet Header, contains PID and clock
PES Header
Rule: Every elementary stream (Audio, Video and Data) gets its own PID (Packet ID)
The MPEG-2 Transport Stream
52

Processing of The Streams in The STB
Tuner/Demod MPEG2
Demux
Video
Decomp.
Audio
Decomp.
System
Memory
Processor
• 6 TV
• 20 Radio
• Service Information
QAM
OFDM
D/A
D/A
MPEG2-TS : 40 Mbit/s, e.g..:
188
188
MPEG2-TS
PID Header Payload
DEMUX
queues
PID 1
PID 2
section
section
QPSK
Audio
Video
Data
53

− PES: Packetized Elementary Stream (Audio, Video, Subtitle, Subtitle)
− Two MPEG-2 container format: A file format that can contain data compressed by standard codecs. Two
file formats:
• PS: Program Stream (MPEG-2 PS)
• TS: Transport Stream (MPEG-2 TS)
MPEG-2 Video System Standard
Video
Audio
Elementary Streams
(Compressed Audio, Video and Data)
Video
Encoder
Audio
Encoder
Packetizer
Packetizer
ES
ES
Video
PES
Program
Stream
MUX
Transport
Stream
MUX
Audio
PES
PS: Program Stream
TS: Transport Stream
For noisier
environments such as
terrestrial broadcast
channels
For an error-free
environment such as
Digital Storage Media
(DSM)
ES Data
PES
Packetizer
Ancillary data
Control data
54

MPEG Transport Stream (TS)
– Encapsulates Packetized Elementary Streams (PES)
– Has error detection and stream synchronization
– 188 byte packets (or 204 with Reed-Solomon FEC)
– Every TS packet has a Payload ID (PID)
• Besides MPEG video: KLV Data, Dolby Vision, Camera Positioning Information, VC-1, VC-4, AES3,
Dolby TrueHD audio…etc
55

MPEG TS – Logical View
Program Association Table (PAT)
Program # 100 – PMT PID 1025
Program Map Table (PMT)
Program # 100
Video PID – 501 – MPEG-2 Video
Audio PID (English) – 502 – MPEG-2 Audio
Audio PID (Spanish) – 503 – MPEG-2 Audio
Program # 200
Video PID – 601 – AVC Video
Audio PID (English) – 602 – AAC Audio
56

− For each service in the multiplex, the PAT indicates the
location (the Packet Identifier (PID) values of the TS
packets) of the corresponding Program Map Table
(PMT).
− Contains a list of all programs in the transport multiplex
and points to the PIDs of the respective Program Map
Tables (PMT)
− It also gives the location of the Network Information
Table (NIT).
− Transmission in the actual TS is mandatory
Program Associate Table (PAT)
Other Packets
Audio Packet
Video Packet
51 51 51 66
64 0 150 101
Program # 100
Program # 200
57

Program Map Table (PMT))
− Every program is described by a PMT. It defines the set of PIDs
associated with a program, e.g. audio, video, ...
− The elementary streams associated with a program have
PIDs listed in the PMT. Another PID is associated with the PMT
itself.
− The PMTs provide information on each program present in
the transport stream, including the program_number, and list
the elementary streams that comprise the described
program.
− Program Descriptors (Protection systems, interactive apps …)
− Lists all streams
• PID: where stream data is carried in the multiplex
• Stream Type: type of media compression
• Stream Descriptors
− Language, coding parameters, demux parameters, …
Program Associate Table (PAT)
Other Packets
Audio Packet
Video Packet
51 51 51 66
64 0 150 101
Program # 100
Program # 200
58

ST 2022-x Standards Overview
– ST 2022-x standards take payloads from specialized electrical interfaces and puts them on IP using RTP
– The electrical interfaces are ASI and SDI (Over 75 of mappings into MPEG TS)
2007
2007
2010
2011
2012
2012
2013
Standard Scope Characteristics
ST2022-1
“Forward Error Correction for Real- Time Video/Audio Transport
Over IP Networks
• Point-to-Point IP stream transmission
ST2022-2
“Unidirectional Transport of Constant Bit Rate MPEG-2 Transport
Streams on IP Networks”
• Point-to-Point MPEG-2 Compressed Streams over IP packets
ST2022-3
“Unidirectional Transport of Variable Bit Rate MPEG-2 Transport
Streams on IP Networks”
• Point-to-Point MPEG-2 Compressed Streams over IP packets with
Piecewise-Constant Variable Bit Rate
ST2022-4
“Unidirectional Transport of Non- Piecewise Constant Variable Bit
Rate MPEG-2 Transport Streams on IP Networks”
• Point-to-Point MPEG-2 Compressed Streams over IP packets with
Non-Piecewise Constant Variable Bit Rate
ST2022-5
“Forward Error Correction for High Bit Rate Media Transport Over
IP Networks”
• Point-to-Point IP Stream Transmission
ST2022-6
“Transport of High Bit Rate Media Signals Over IP Networks”
(HBRMT) (ST 2022-6: SDI over RTP (Real-time Transport Protocol))
• A Point-to-Point IP transmission with a packaged mapping for
uncompressed SDI signals not encapsulated in MPEG-2 TS
• Use of video compression not permitted
ST2022-7 “Seamless Protection Switching of SMPTE ST 2022 IP Datagrams”
• Hitless Failover by transmission of two matching packet streams
over different paths 59

ST 2022-6: SDI over RTP (Real-time Transport Protocol)
IP UDP RTP Payload
UDP RTP Payload
RTP Payload
Payload
60

ST 2022-6: SDI over RTP (Real-time Transport Protocol)
– SMPTE 2022-6 is the most common uncompressed video format
– It contains all the elements of current SDI
– Video, Audio and Data must be embedded before being packetized
– For Audio processing, the audio must be de-embedded and then re-embedded
61

ST 2022-7: Seamless (Hitless) Protection Switching of IP Datagrams, Redundancy
– RTP packets replicated for transmission on multiple diverse paths
– Recoverable if at least one copy makes it through one path, within receiver buffer limitations
– SMPTE ST 2022-7 Seamless protection of ST 2022 IP Datagrams
– Originally for SMPTE ST 2022-6 streams.
Port 1
Port 2
Edge Device
Host Receiver
Packet
Merge/Arbitrate
Edge Device
Host Transmitter
Port 1
Port 2
Buffer / Delay
1 Frame / 20ms
62

Sender Receiver
Switches use IGMP
Clean Switch Using Frame Numbers
Stream
Sender A
Duplicate
Stream
Packet
Selection
(Output
Selector)
1 2 3
1 2 3
1 2 3
1 2 3
1 2 3
Generic Switch
(Main)
Generic Switch
(Redundant)
− A hitless sender transmits two identical packet streams over two separate network paths.
− At the receiver, the two streams are re-aligned using Alignment Buffers (Separately for each input)
− A single output is created using the good packets received from either one path or the other (Matching
packets numbers are sent to Output Selector to choose best of each sequence number and creates
steam)
63

Sender Receiver
Switches use IGMP
Clean Switch Using Frame Numbers
Stream
Sender A
Duplicate
Stream
Packet
Selection
1 2 3
1 2 3
1 2 3
1 2 3
1 2 3
1 2 3
1 2 3
1 x
2 x
3
Generic Switch
(Main)
Generic Switch
(Redundant)
− A hitless sender transmits two identical packet streams over two separate network paths.
− At the receiver, the two streams are re-aligned using Alignment Buffers (Separately for each input)
− A single output is created using the good packets received from either one path or the other (Matching
packets numbers are sent to Output Selector to choose best of each sequence number and creates
steam)
Packet
Selection
(Output
Selector)
64

Advanced Media Workflow Association (AMVA)
The AMWA AS-11 family of Specifications define constrained media file formats for the delivery of finished media assets to a broadcaster or publisher.
66
– NMOS is a family name for specifications
produced by the Advanced Media Workflow
Association (AMVA) related to networked
media for professional applications.
– A family of open, free of charge specifications
that enable interoperability between media
devices on an IP infrastructure.

AES67, Same Protocol Is Needed!!
– It is a bridging compliance mode common to all IP-Networks; an interoperability mode you can put an
AES67 compliant device into, on any participating network.
– AES67 could be a means of connecting different networks and systems together
– AES67 could even allow a system to be made up of items all using different protocols.
67

68

69

70
AES67 could be a means of
connecting different
networks and systems
together
– AES67 could be a means of connecting different
networks and systems together
– AES67 is a set of rules for existing and future
protocols to follow.
– A standard to enable high-performance audio-
over-IP streaming interoperability between the
various IP based audio networking products
currently available, based on existing standards
such as Dante, Livewire, Q-LAN and Ravenna.
– Dante, Ravenna and AVB use AES 67
• Uncompressed Audio adopted by the AES
• Prevalent in 1Gb/sec Ethernet fabric
• 48 KHz sampling
• Multiple channels (80 channels no problem)

DANTE –Digital Audio Network Through Ethernet
– An Audio over Ethernet (AoE) system developed in 2006 by Audinate, based in Sydney, Australia
71

Ember + (Embedded Basic Encoding Rules) Control Protocol
– Ember plus (Ember +) is an open control protocol originating
from work by Lawo and LSB Broadcast Technologies Gmbh.
– It offers a way for broadcast systems, hardware and software
to communicate control messages and is designed both to
be real-time and to be very flexible in the applications and
use-cases it can support.
– Ember+ is designed to allow the communication between two
endpoints, one being the data provider and the other being
the consumer.
– The data provider is usually a piece of hardware which offers
a set of controllable parameters, while the consumer may be
a control- or monitoring-system which provides access to
these parameters and can inspect or alter them.
72

Ember + (Embedded Basic Encoding Rules) Control Protocol
– Development aspirations include:
• Easy for programmers understand and implement
• Minimal hardware requirements for controlled devices
(Ember+ provider)
• Possible to implement on a wide range of hardware
platforms, from basic micro controllers all the way up
to powerful PCs
• Minimal development effort required to control new
unknown devices once Ember+ is implemented on a
product
73

Video Services Forum (VSF)
– Enabling Media Networking Solutions.
– The VSF is an international association comprised of service providers, users and
manufacturers dedicated to
• interoperability
• quality metrics
• education for media networking technologies
– The organization's activities include:
1. Providing forums to identify issues involving the development, deployment,
operation, and security of media networking technologies
2. Promoting interoperability by contributing towards the development of
Standards
74

EBU, SMPTE and AES
European Broadcasting Union (EBU)
– The European Broadcasting Union is an alliance of public service media organisations, established on 12 February 1950.
– The organisation is made up of 115 member organisations in 56 countries, and 34 associate members from a further 21
countries.
Society of Motion Picture and Television Engineers (SMPTE)
– The Society of Motion Picture and Television Engineers, founded in 1916 as the Society of Motion Picture Engineers or
SMPE, is a global professional association of engineers, technologists, and executives working in the media and
entertainment industry.
Audio Engineering Society (AES)
– The Audio Engineering Society is a professional body for engineers, scientists, other individuals with an interest or
involvement in the professional audio industry.
– The membership largely comprises engineers developing devices or products for audio, and persons working in audio
content production.
75

AIMS (Alliance for IP Media Solutions): A True Consortium of Today’s Best
The Role of AIMS: To faster adoption of the work of these organizations with regard to IP interoperability
Reference Architecture
Technical
Recommendations
AMWA
76
Over 55 AIMS Members!

77
AIMS (Alliance for IP Media Solutions): A True Consortium of Today’s Best
FULL ALLIANCE MEMBERS
AIMS has entered into liaison agreements with the follow organizations
ASSOCIATE ALLIANCE MEMBERS

JT-NM (Joint Task Force on Networked Media) – AMWA/EBU/SMPTE/VSF
– It was formed by the
• European Broadcasting Union (EBU)
• Society of Motion Picture and
Television Engineers (SMPTE)
• Video Services Forum (VSF)
– It was formed in the context of the
transition from purpose-built broadcast
equipment and interfaces (SDI, AES, cross
point switcher, etc.) to IT-based packet
networks (Ethernet, IP, servers, storage,
cloud, etc.).
78
IETF: Internet Engineering Task Force, Request for Comments-RFC
IEEE: Institute of Electrical and Electronics Engineers

– Which standards and specifications enable the JT-NM Reference Architecture
– How the range of underlying technologies is expected to evolve
– When it is expected that those standards and specifications be widely available to build interoperable
multi-vendor systems
• Note that timescales shown are approximate and may vary depending on the speed of industry
developments.
79

• Which standards and specifications enable the JT-NM Reference
Architecture
• How the range of underlying technologies is expected to evolve
• When it is expected that those standards and specifications be
widely available to build interoperable multi-vendor systems
• Timescales shown are approximate and may vary depending
on the speed of industry developments.
JT-NM: Joint Task Force on Networked Media Roadmap
80

Media Transport •SMPTE 2022-6, VSF TR-4,VSF TR-03, SMPTE RDD 37(ASPEN, Adaptive Sample Picture Encapsulation),…
Timing •IEEE1588 (PTP),SMPTE 2059 profile,AES67profile,…
Identity •UUID,URI, AMWANMOS,…
Discovery & Registration •mDNS,Bonjour, AMWA NMOS,Ravenna,…
Flow Control •IEEE AVB/TSN,Qos,SDNs,NFV
,MPLS,…
Flow Switching •Source,Switch,Destination,Make-before-break,Break-before-make,…
Compression •SMPTE VC-2(Dirac),SMPTE RDD 37(TICO),SMPTE RDD 34 (Sony LLVC)…
* JT
-NM Reference Architecture v1.0 ** JT
-NM Gap AnalysisReport plus latestdevelopment
The Key Planes of Interoperability* and the many standards**
81

JT-NM Tested Program Catalog
82

JT-NM Tested Program at IP Showcase 2019 NAB/IBC Show
83

84

PTP/IP Roadshow 85

TICO (Tiny Codec) Alliance: (intoPIX)
AIMS:
ST2022‐6, AES67, TR‐03/04
(Grassvalley)
Sandbox LiveIP:
ST2022‐6, AES67 (EBU, VRT)
Axon, Dwesam, EVS,
Genelec, Grassvalley,
Lawo, LSB, Nevion,
Tektronix, Trilogy
Imagine, Grassvalley, Lawo,
Nevion, s.a.m, EVS, Cisco, Arista
AMWA NMI (Networked Media
Incubator) Project:
ST2022‐6, TR‐03 (BBC, JTMN)
Atos, Avid, BBC, Embrionix,
Harmonic, InSync Technology,
Mellanox Technologies, Nevion,
Panasonic, s.a.m, Streampunk
Media and Suitcase TV
VSF: Propose New IP Format to SMPTE
AES67 Approach
ASPEN (Adaptive Sample Picture
Encapsulation) Community: (Evertz)
Correlation Chart of IP Format Related Bodies
Sony “IP Live”: (Sony)
86
SMPTE: Video Standard AES: Audio Standard EBU: JT‐NM project

SMPTE ST 2110 – 20 (Uncompressed Video – RFC 4175 (Contains the video data based on resolution and frame rate))
SMPTE ST 2110 – 21 (Traffic shaping uncompressed video, Performance of transmitters – packet pacing, bursts, gaps)
SMPTE ST 2110 – 22 (compressed Video Essence)
SMPTE RP 2110 - 23 (Video Essence Transport over Multiple ST 2110-20 Streams)
SMPTE ST 2110 – 30 (Uncompressed Audio (PCM Audio) – AES67)
SMPTE ST 2110 – 31 (AES Transparent Transform, Compressed Audio – non-PCM/AES3, Guardband aware, stereo)
SMPTE ST 2110 – 40 (Ancillary Data – VANC based on IETF ANC 291)
SMPTE ST 2110 – 50 (SMPTE ST 2022-6 Essence, Support for legacy SMPTE ST 2022-6 infrastructure)
SMPTE ST 2022 – 08 (Integration with ST 2022-06)
SMPTE ST 2110 – 10 (System Timing – RTP, SMPTE ST 2059, SDP)
SMPTE 2059-1 Generation and Alignment of Interface Signals to the SMPTE Epoch
SMPTE 2059-2 SMPTE Profile for Use of IEEE-1588 Precision Time Protocol in Professional Broadcast Applications
SMPTE 2022-7 (Seamless Protection Switching of SMPTE ST 2022 IP datagrams)
The SMPTE ST 2110, Suite of Standards Summary
88

The SMPTE ST 2110, Suite of Standards Summary
SMPTE: Society of Motion Picture and Television Engineers
IETF: Internet Engineering Task Force, Request for Comments-RFC
IEEE: Institute of Electrical and Electronics Engineers
Request for Comments
89

SMPTE ST 2110 Suite, Summary Version
90

SMPTE 2022-6 and SMPTE ST 2110 Suite
91

The SMPTE ST 2110, Suite of Standards
IETF: Internet Engineering Task
Force, Request for Comments-RFC
93

VSF (Video Service Forum) TR-04 (Technical Recommendation)
Video Services Forum TR-04
– Defines 2022-6 as video payload
– Integration of 2022-5 FEC and 2022-7
– Audio Streaming Embedded SDI or AES67
– Metadata via SDP (Session Description Protocol)
– Synchronization using IEEE1588 Default Profile
VSF (Video Service Forum)
TR-(Technical Recommendation)
94

SDP (Session Description Protocol), RFC 4566
– Describe the contents of the multicast transmission
• IP address
• Audio type
• Video type Resolution
– Should include the following metadata:
• Sender description
• Video and/or audio essence
• Raster size (in pixels)
• Frame-rate (video)
• Channel count (audio)
• Sampling structure (audio/video)
• Bit depth (audio/video)
• Colourimetry
• Source IP address and port
• RTP payload ID (audio/video)
• PTP grandmaster source and domain
• v=0
• o=- 243362948900865 0 IN IP4 192.168.20.112
• s=Snell IQMIX
• t=0 0
• a=ts-refclk:ptp=IEEE1588-2008:ec-46-70-ff-fe-00-bf-60:0
• a=mediaclk:direct=0
• a=clock-domain:PTPv2 0
• m=audio 50000 RTP/AVP 97
• i=RAVENNA Audio-strm0/0,RAVENNA Audio-strm0/1
• c=IN IP4 239.31.112.1/31
• a=source-filter: incl IN IP4 239.31.112.1 192.168.20.112
• a=rtpmap:97 L24/48000/2
• a=framecount:48
• a=ptime:1
• a=recvonly
• a=sync-time:0
95

Video Services Forum TR-03
– Video, Audio and Ancillary data carried as
separate elementary RTP streams
• Video Streaming per RFC 4715
• Audio Streaming per AES67
• IETF ST 291 RTP Payload Format for Ancillary
Data Packet
– SDP (Session Description Protocol) RFC4566 for
synchronous playout of streams (Describe the
contents of the multicast transmission)
– Synchronization using IEEE1588 Default Profile
VSF TR-03 IP Packet Formats. Dedicated IP Flows Carry
Video, Audio and Metadata Essence.
96

SMPTE ST 2110
– 2110 can be thought of as inter-facility much like we think of as baseband SDI in current broadcast,
satellite and cable facilities. Here all the signals are carried separately
– Video, Audio and Data are ALL separate streams using RTP
– For Audio processing, the audio is simply picked up, processed and sent outbound. Note that this doesn’t
require an inherent embedding and de-embedding
97

– 2110 can be thought of as inter-facility much like we think of as baseband SDI in current broadcast,
satellite and cable facilities. Here all the signals are carried separately
– Video, Audio and Data are ALL separate streams using RTP
– For Audio processing, the audio is simply picked up, processed and sent outbound. Note that this doesn’t
require an inherent embedding and de-embedding
SMPTE ST 2110
ST 2110-30
ST 2110-10
ST 2110-20
98

The SMPTE ST 2110, Suite of Standards-Details
– VSF (Video Service Forum) TR-04 (Technical Recommendation):
• For 2022-6 and AES67
• Support split video and audio routing
– SMPTE 2022-6: Transport of High Bit Rate Media Signals Over IP
Networks
– AES 67 Audio: A standard to enable high-performance audio-over-IP
streaming
– VSF (Video Service Forum) TR-03: For RFC (Request for Comments)
4175 Video Elementary Stream to replace 2022-6
• Video, Audio and Ancillary data carried as separate elementary
RTP streams
• TR-03 aka SMPTE 2110 Draft
– IETF RFC 4175 Video: RTP Payload Format for Uncompressed Video
• IETF: Internet Engineering Task Force, Request for Comments-RFC
– IETF ST 291: RTP Payload Format for Ancillary Data Packet
100

– SMPTE ST 2110 – 30:
• Uncompressed Audio (PCM Audio)
• AES67 (IETF RFC 3190 Audio)
– SMPTE ST 2110 – 31: AES Transparent Transform, Compressed Audio –
non-PCM/AES3, Guardband aware, stereo
– SMPTE ST 2110 – 20: Uncompressed Video – IETF RFC 4175
– SMPTE ST2110–21: Traffic shaping uncompressed video, Performance
of transmitters – packet pacing, bursts, gaps
– SMPTE ST 2110 – 40: Ancillary Data – VANC based on IETF ANC 291
– SMPTE ST 2110 – 10: System Timing – RTP, SMPTE ST 2059, SDP
SMPTE 2059-1
SMPTE 2059-2
• PTP Timing for A/V Sync and Genlock (Standard with roots to IEEE
1588)
101

102

103

104

105

106

107

SMPTE ST 2110 – 20 (Uncompressed Video – RFC 4175)
– Specifies the real-time, RTP-based transport of uncompressed active video essence over IP networks.
– An SDP-based signaling method is defined for image technical metadata necessary to receive and
interpret the stream
− Raster size independent  Up to 32K x 32K pixels
− Agnostic
• Colour sampling  4:1:1 to 4:4:4+
• Bit depth  8 to 16-Bit+
• Frame-rate  23.98 to 120 fps+
− Support for HDR  PQ & HLG
− Significant bandwidth efficiency  1080p50@ST 2022-6= 3,074Gbps vs 1080p50 @ ST 2110-20 = 2,143Gbps
108

SMPTE ST 2110 – 20 (Uncompressed Video – RFC 4175)
– Contains the video data based on resolution and frame rate
– Packet headers used to contain a given number of lines depending on the resolution
– Header Extensions can be used
– TIME STAMPS!!!
109

SMPTE ST 2110 – 30 (Uncompressed Audio – AES67)
– Specifies the real-time, RTP-based transport of PCM digital audio streams over IP networks by reference to
AES67.
– An SDP-based signaling 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
110

ST 2110-20 & 30 (Uncompressed Audio and Video)
111

112

113

114

115

116

117

• Only elements of interest need to be delivered
• Bandwidth saved by not sending empty elements of SDI
• Low Processing latency, few lines
− Essence Independent Transport based on RTP
• Advanced format from ST2022-6
• Currently, Uncompressed Video Only
118

Note: Evertz Aspen, VSF TR-01 based HD Uncompressed Mapping
• Only elements of interest need to be delivered
• Bandwidth saved by not sending empty elements of SDI
• Low Processing latency, few lines
– Essence Independent Transport based on ST2022-2
– ASPEN (Adaptive Sample Picture Encapsulation) is a standards-based, open format that moves uncompressed Ultra HD,
3G, HD, and SD signals over MPEG-2 transport streams (ISO/IEC 13818-1) (ASPEN Community is more than 30 industry
leading manufacturers).
119

– Separates Video (SD,HD,3G,UHD), Audio ST 302 and Metadata ST 2038
– Uses MPEG-2 Transport Stream for Uncompressed Video SMPTE 2022-2
– Uses Audio ST 302
– Uses ST2038 for ANC data
– Proposed as SMPTE RDD37 in progress
570IPG
– With direct conversion of up to 18 3G/HD/SD signals to IP, using SMPTE 2022-6 formatting, the 570IPG-
3G18-SFPP12 series delivers unparalleled processing densities.
– The 570IPG also supports up to 2 audio TDM ports for carrying discrete audio over IP in addition to the
primary video.
Note: Evertz Aspen, VSF TR-01 based HD Uncompressed Mapping
IP DST MPEG2 TS-
Header
Video Payload
SMPTE RDD37
IP DST MPEG2 TS-
Header
Audio Payload
SMPTE ST302
IP DST MPEG2 TS-
Header
Metadata Payload
SMPTE ST 2038
Dedicated Multicast IP Stream
IP SRC
IP SRC
IP SRC
120

API: Application Programming Interface
– API is a software intermediary that allows two applications to talk to each other.
– Each time you use an app like Facebook, send an instant message, or check the weather on your phone,
you’re using an API.
‫کاربردی‬ ‫نویسی‬‫برنامه‬ ‫رابط‬
122

JSON (JavaScript Object Notation)
– It is an open standard file format, and data
interchange format, that uses human-
readable text to store and transmit data
objects consisting of “attribute–value pairs”
and “array data types” (or any other
serializable value).
– JSON is a language-independent data format.
– It was derived from JavaScript, but many
modern programming languages include
code to generate and parse JSON-format
data.
– The official Internet media type for JSON is
application/json.
– JSON filenames use the extension .json.
‫اسکریپت‬ ‫جاوا‬ ‫در‬ ‫اشیا‬ ‫نمادگذاری‬
123

JSON (JavaScript Object Notation)
124

REST (REpresentational State Transfer) API
– It is an architectural style for designing decentralized systems.
It originated from an architectural analysis of the Web and
combines a client/server architecture with additional
constraints that define a uniform interface.
– It defines a set of constraints to be used for creating Web
services.
– Web services that conform to the REST architectural style,
called RESTful Web services, provide interoperability between
computer systems on the internet.
– RESTful Web services allow the requesting systems to access
and manipulate textual representations of Web resources by
using a uniform and predefined set of stateless operations.
– In a RESTful Web service, requests made to a resource's URI will
elicit a response with a payload formatted in HTML, XML,
JSON, or some other format.
‫انتقال‬ ‫نمایندگی‬
‫حالت‬
125

REST (REpresentational State Transfer) API
126

NMOS (Networked Media Open Specifications)
– NMOS is a family name for specifications produced by the Advanced Media Workflow Association (AMVA)
related to networked media for professional applications.
– A family of open, free of charge specifications that enable interoperability between media devices on an
IP infrastructure.
127

128
NMOS (Networked Media Open Specifications)
Interface Specification: IS
Best Current Practice: BCP

AMWA IS-04 NMOS Discovery and Registration Specification (Stable)
• Central Registry
• Resources: Nodes, Devices, Sources, Flows, Senders & Receivers
• Identity: Guide for every resource
What does it do?
• Allows control and monitoring applications to find the resources on a network (Nodes, Source, Devices, Flows, Senders &
Receivers,…)
• Providing a way for network-connected devices to become listed on a shared registry, and it provides a uniform way to query
the registry.
129
IS-04 NMOS
IS-05 NMOS
Why does it matter?
• Enables for automation and reducing manual overhead
• Essential for dynamic deployment
How does it work?
• Media Nodes locate IS-04 registry using DNS-SD (Domain
Name System Service Discovery) (unicast preferred)
• Media Nodes register their resource information with HTTP
+ JSON (JavaScript Object Notation)
• Applications query with HTTP and/or subscribe with
WebSockets (a full-duplex communication protocol).

IS-04 NMOS
IS-05 NMOS
What does it do?
• Enables a client or controller application to create or remove media stream connections between sending and receiving devices.
• Provides a transport-independent way of connecting Media Nodes
 Supports RTP, WebSocket and MQTT (Message Queuing Telemetry Transport Protocol) connections
• Supports single + bulk connections, immediate + delayed connections
AMWA IS-05 NMOS Device Connection Management Specification (Stable)
130
Why does it matter?
• ST 2110 does not specify how to do “Device Connection Management”
• So without IS-05 there is a danger of multiple proprietary approaches
• …and difficulty in adopting new stream formats.
• Provides support for new specifications, such as IS-07 event transport
How does it work?
• IS-04 provides information about Senders and Receivers
• Control application sends instructions to Media Nodes
• Transport file parameter conveys the connection information for ST 2110 streams
• Send Connection parameters to Receiver Device via IS-05
• Notification via IS-04 websocket

Application Logic
IS-04
Registry
Multicast subscribe
Flow Source
Receiver
Media Node
Sender
Flow Source
Sender
Media Node
Receiver
ST 2110 or other stream
IS-04 and IS-05 Working Together
131
SDP (Session Description Protocol): Describe
the contents of the multicast transmission
• IP address
• Audio type
• Video type Resolution
SDP
SDP

AMWA IS-04 & IS-05, Connectivity Management
AMWA IS-04 & IS-05
• Endpoint Real Time Identity & Capabilities
• Configurable Text for Relevancy
• Playout and Automation Integration
IS-04
Registration
& Discovery Service
Endpoint
Connection
Management
Endpoint Identity
and SDP
(IS-05: Control)
Control System
132

Live Production with IP Technology
Video Switcher
Multiviewer
Monitoring
Systems
Graphic Systems
Remote Source
Video Server
Relay and Clips
Playout
Cameras and
Microphones
Audio Mixer
Control System
Control System
133
(Broadcast Controller)

Live Production with IP Technology
Video Switcher
Multiviewer
Monitoring
Systems
Graphic Systems
Remote Source
Video Server
Relay and Clips
Control System
Playout
Cameras and
Microphones
Audio Mixer
IP Network
(SDN) Network Controller
Control System
134
IS-06
Network
Control API
Network
Interface
OF, NetConf/Yang, REST/JSON
REST, RESTCONF APIs
The broadcast controller is the
overall policy control point for all
media endpoints and sessions.

Broadcast Controller
Network Controller
Endpoint (Edge devices)
Switch (Network Device)
RDS: Registration and
Discovery Server
IS-04, Query API
IS-04, Registration API
IS-06
OpenFlow or Proprietary Protocol
LLDP (Link Layer Discovery Protocol)
AMWA IS-06 NMOS Network Control Specification
Network Control API
The API is between the broadcast
controller and the network controller
to modify and view network.
– The broadcast controller is the overall policy control point for all media endpoints and sessions.
– IS-06 NMOS Network Control enables a broadcast controller to modify and view network.
– AMWA IS-06 lets broadcast control applications manage what happens on the network itself.
– The network controller abstracts the details of the network from the broadcast controller and provides an
API for all required network services.
IS-05
(Connectivity Management)
135

AMWA IS-06 NMOS Network Control Specification
What does it do?
• IS-06 is an AMWA NMOS Specification for API control of a managed network.
• Lets broadcast control applications manage what happens on the network itself
Why does it matter?
• Ethernet switch output ports might only support a limited number of media flows before
they start dropping packets
 This is different to what happens in a typical SDI router
 Which means corrupted video and audio
How does it work?
• “Northbound” API from network fabric’s controller
• Provides topology discovery, flow authorization and assurances of flow bandwidth
Broadcast Controller
Network Controller
NetConf, OF (OpenFlow) and others
Network Control API
IS-06
Network Configuration Protocol (NetConf) is a network management protocol developed and standardized by the IETF.
• NetConf provides mechanisms to install, manipulate, and delete the configuration of network devices.
OpenFlow is a communications protocol that gives access to the forwarding plane of a network switch or router over the network.
• OpenFlow enables network controllers to determine the path of network packets across a network of switches. The controllers are distinct from the switches.
136
Cisco Open Daylight
Controller
with bandwidth manage

AMWA IS-07 NMOS Event & Tally Specification
What does it do?
• Provides an IP-friendly mechanism to carry time-sensitive information
 For example: camera tally information, audio levels, control panel button
presses and status
Why does it matter?
• ST 2110 does not provide an equivalent to GPI functionality
 This leads to the danger of multiple proprietary approaches
• Consistency with other NMOS specifications
How does it work?
• Media Nodes emit and consume state and state change info
• Lightweight messages sent using WebSockets or MQTT (MQ Telemetry Transport)
• Message flows connected using IS-05
An IS-07 message
137

AMWA IS-08 NMOS Audio Channel Mapping Specification (Stable)
What does it do?
• Allows channel-level operations within NMOS environments
 For example: muting channels, swapping languages, …
Why does it matter?
• Provides expected functionality for typical production/broadcast operations
• Extends usefulness of IS-05 and other NMOS specs.
How does it work?
• Controller gets channel information from sending Node
 …and sends mapping matrix to the receiving Node
• Can also do sender-side matrixing
138

AMWA IS-08 NMOS Audio Channel Mapping Specification (Stable)
139
The above Map is represented in JSON in the API as right.

What does it do?
• Allows an NMOS Node (also known as a "Media Node") to obtain global configuration parameters that are common across the system.
• Provide Media Nodes with “global” information about their environment
 e.g. PTP settings
Why does it matter?
• We need systems to start working asap after (re)connection or power-up
• DNS, DHCP, etc. provide a lot of what a Media Node needs… but not everything
• Enables the Node to start, or re-start, in a well defined way that is consistent with the environment it's running in.
How does it work?
• Defines the System API 'global configuration resource' and the expected behaviour for Nodes using it.
• Read-only JSON resource, compatible with TR-1001 System Resource
AMWA IS-09 NMOS System Parameters Specification
140

AMWA IS-10 NMOS Authorization Specification
What does it do?
• Allows an API server to accept or reject requests depending on what a client is authorized to do
Why does it matter?
• Security in the control plane is essential
• Best practice is to limit what clients can do
How does it work?
• Control client provides credentials and gets an access token
• Sends token with API requests
• Based on JSON Web Tokens and OAuth 2.0
• Encryption is a prerequisite (see BCP-003-01)
141

AMWA IS-11 NMOS Sink Metadata Processing [Work In Progress]
What does it do?
• Provides information about physical devices called Sinks associated with Receivers
• Allows to configure media parameters of Senders basing on information about Sinks
Why does it matter?
• State of a Sender can be tuned it’s configurable to be compatible with an according Receiver
How does it work?
• An endpoint on the side of Senders is introduced for media parameters control
• Receivers are followed with endpoints which list Sinks and describe them in detail
142
− The purpose is to explain how Sources, Flows and Senders within an NMOS compatible system can be reconfigured and
EDIDs of Sinks associated with Receivers can be obtained (EDS: Extended Display Identification Data).
• Sink: A media consuming unit associated with an IS-04 Receiver. Sink is a resource and based on Resource Core JSON Schema.
• Media Profile: Media description which describes a format acceptable for all Receivers implied to be a part of a connection. A
Media Profile consist of separate parameters required to set up Sender and such IS-04 resources behind it as Source and Flow.
Sink: A media consuming unit
associated with an IS-04 Receiver.

AMWA MS-04 Identity and Timing Model [Work in Progress]
What does it do?
• Documents a model for identity and timing that applies to AMWA NMOS specifications that apply to content
• Identity and Timing enables us to define workflows in terms of the content of business value rather than the systems processing it
• MS-04 Formalizes concepts such as Source, Flow, Time Value…
• Builds on models of the JT-NM Reference Archicture
‒ Re-examines the JT-NM reference architecture model taking into account many typical workflows
Why does it matter?
• Increased content reuse means, increased reliance on end-to-end models
• Provides a basis for future specifications (ST 2110’s RTP timestamps are insufficient, so we need a model for future extensions)
How does it work?
• Defines the main time-related entities used in NMOS specs
• Provides further explanation of their meaning
• Gives guidance on how they can be used for media operations
143
Identity: The ability to uniquely identify any resource in a
networked media architecture
Timing: Associating a unique time value with each video
frame, audio sample or data element

AMWA BCP-002 Recommendations for Grouping NMOS Resources
What do the recommendations do?
• Document best practice and recommendations for how to indicate and handle Groups of Resources in AMWA NMOS APIs.
Why do they matter?
• Provide a consistent way of referring to groups of related Resources (e.g. video and audio Senders of a camera)
• This helps with interoperability and integration.
What are the recommendations?
• BCP-002-01 addresses “Natural Groups”, i.e. those created by the default operation of a Node/Device, and not user- or automation-
defined Groups.
144
− Often it is helpful to work with related Resources (Devices, Senders, Flows, etc.) as a group.
• For example a camera might have produce video, audio and data Senders, which form a “natural group”.
• This is the subject of BCP-002-01.
− Further BCP-002-xx recommendations may cover other types of group, such as those created by a user.

AMWA BCP-002-01: Natural Grouping of NMOS Resources
What does it do?
• Documents best practice and recommendations for how to indicate and handle “Natural Groups” of Resources in AMWA NMOS APIs.
• These are those created by the default operation of a Node/Device, and not user- or automation-defined Groups.
• Defines best practice for tagging groups of resources based on the function of a device, for example:
 2110-20, -30, -40 senders within a camera and 2110-20 receivers for multiviewer panes
"tags": {
"urn:x-nmos:tag:grouphint/v1.0": ["MV PIP 1:Video"]
Dev: Device
145
Why does it matter?
• Provides a consistent way of referring to groups of
related Resources (e.g. video and audio Senders of
a camera).
• Avoid different vendors taking different approaches
• This helps with interoperability and integration.
How does it work?
• Nodes add a grouphint tag to the JSON
representation of each member of a Natural Group.

AMWA BCP-003 Security recommendations for NMOS APIs
What does it do?
• Document best practice and recommendations for securing AMWA NMOS APIs.
Why do they matter?
• A secure control plane is essential.
• These recommendations allow interoperability using widely adopted open technologies.
146
For NMOS this means that APIs need to provide:
• Confidentiality: Data passing between client and the APIs is unreadable to third
parties.
• Identification: The client can check whether the API it is interacting with is owned
by a trusted party.
• Integrity: It must be clear if data travelling to or from the API been tampered with.
• Authentication: The client can check if packets actually came from the API it is
interacting with, and vice versa.
• Authorisation: The API can determine whether the client interacting with it has
authorisation to carry out the operation requested.
What are the recommendations?
• BCP-003-01 recommends securing API
communication using TLS 1.2 or better.
• BCP-003-02 recommends using OAuth 2.0
authorisation using JWT (JSON Web Tokens (JWTs) ).
 IS-10 details how to do this.
• BCP-003-03 recommends using Enrollment over
Secure Transport for certificate provisioning.
• INFO-002 provides guidance for implementers.

AMWA BCP-003-01 Secure Communication in NMOS Systems
What does it do?
• Documents best practice for using secure transport for NMOS API communications.
Why does it matter?
 Need to ensure encryption is sufficient.
• Users don’t want our IP systems hacked so are demanding security in the control plane
• IS-04 etc can use HTTPS but don’t say enough about how to do that in an interoperable and secure way
How does it work?
• Recommends using TLS 1.2 or better for HTTP and WebSocket messages.
• Recommends cipher suites.
147

AMWA BCP-003-02 Authorization in NMOS Systems
148
What does it do?
• Documents best practice for an API server to accept or reject requests depending on
what a client is authorized to do.
• Enables API server to verify what client may access
• Based on OAuth 2.0
Why does it matter?
 Authorization limits what clients can do to what is allowed.
How does it work?
• Recommends using AMWA IS-10 Authorization Specification
 This specifies how client provides credentials and gets access tokens.
• Encryption is a prerequisite (see BCP-003-01).

What does it do?
• Documents best practice for automated provisioning of TLS (Transport Layer Security) Server
Certificates to NMOS APIs.
Why does it matter?
 Certificates are an important part of this, and automation makes their use practical.
How does it work?
• Recommends behaviour, based on Enrollment over Secure Transport (RFC 7030)
• Encryption is a prerequisite (see BCP-003-01).
AMWA BCP-003-03 Certificate Provisioning in NMOS Systems
149

What does it do?
• It’s a guide for implementers who want to add security to their NMOS Nodes and/or NMOS
Controllers, according to the IS-10, BCP-003-01, BCP-003-02 and BCP-003-03 specifications.
• Please note that this guide is informative and therefore is not a substitute for reading the
normative specifications.
Why does it matter?
• This guide makes the job of adding security to your NMOS implementations easier.
How does it work?
• It details what you need to know, and the steps you need to take when implementing security.
• It also mentions some tools to help in your implementation.
AMWA INFO-002: NMOS Security Implementation Guide
150

What does it do?
• Sink: A media consuming unit associated with an IS-04 Receiver.
• It introduces a common format choice approach of some physical interfaces into NMOS
Why does it matter?
• It shows how physical protocols of common format choice can be handled in the networked way
How does it work?
• Receivers expose information about their Capabilities based on Extended Display Identification Data (EDID)
• Senders get a control mechanism which allows to configure their actual media parameters described in Flows and Sources
AMWA INFO-003 NMOS Sink Metadata Processing Architecture [Work In Progress]
151

What does it do?
• Allows an IS-04 Receiver to express parametric constraints on the types of streams that it is capable of consuming
Why does it matter?
• Controllers need to know whether a Receiver is capable of handling a specific Sender’s stream before connecting the two
How does it work?
• Establishes an open Capabilities register in the NMOS Parameter Registers that lists specifications for parametric constraints (such as
width, height, frame rate, number of channels, etc.)
• Defines how a Receiver instantiates these Parameter Constraints to make up a list of acceptable Constraint Sets, within the IS-04
caps attribute
• Defines how Controllers evaluate whether an IS-04 Sender satisfies these constraints, based on the target parameters specified for
each constraint (such as IS-04 Flow attributes and SDP format-specific parameters)
AMWA BCP-004-01 NMOS Receiver Capabilities
152

What does it do?
• Provides a scheme and guidelines for expressing Extended Display Identification Data (EDID) information via Receiver Capabilities
Why does it matter?
• Receivers associated with physical devices providing EDID need to present their capabilities to Controllers
How does it work?
• Defines physical devices associated with Receivers as Sinks which may have EDID
• Describes how each EDID section is translated into Receiver Capabilities
• Gives recommendations regarding taking certain EDID sections into account
AMWA BCP-005-01 NMOS EDID to Receiver Capabilities Mapping [Work In Progress]
153
− Extended Display Identification Data (EDID) is a metadata format for an apparatus to describe its capabilities as a video source (e.g. graphics
card or set-top box).
• The data format is defined by a standard published by the Video Electronics Standards Association (VESA).
• This document is targeted against E-EDID A2 which consist of EDID 1.4 (and covers EDID 1.3) and is refered to as Base EDID and the CTA-861-G
Extension Block imposed by HDMI.
• The information present in the EDID is subject to the requirements of the Display Monitor Timing (DMT) specification Version 1 Rev 12.
• BCP-004-01 Receiver Capabilities defines a methodology for describing the Receivers with constraints on the properties of streams which related
to IS-04 Senders. This is used to populate Receiver Rapabilties for use with IS-11 Sink Metadata Processing.

*COTS – Commercial Off The Shelf
*VSF – Video Services Forum
Video
Audio
Data
Video + Audio + Data
Fiber
SFP*
10GbE SFP+
25GbE SFP28
QSFP+
QSFP28
*SFP – Small Form-factor Pluggable
40/100GbE
RJ45
Connectivity
Copper
SFP
(Copper)
Up to 10GbE*
COTS*
IP Router
Front View
*GbE – Gigabit Ethernet
SMPTE 2022-6/-7 IP wrapper for SDI
Video + Embedded Audio + Data
VSF* TR-04 SDI but video only
VSF TR-03 Video to RTP
Payload format (2110-20)
Map VANC separately
AES67 Digital Audio
High-performance
IP streaming for Production
Supported in (2110-30)
TCP-IP Ancillary
Data (2110-40)
IETF – Internet Engineering Task Force
IP World of Broadcast & Media Routing
155

SMF (Single Mode Fiber)
– The relatively small core found in singlemode fiber only allows one path of light directly down the center of the core.
⇒ This keeps the signal intact for up to 100 km and beyond.
MMF (Multi-Mode Fiber)
– The term multimode comes from the fact that light can travel in more than one path through the core of this fiber.
⇒ The relatively large core allows light to travel both straight down the center or to bounce from side to side in a zigzag pattern.
⇒ Up to 300m (at 10 Gb/s to 100 Gb/s data rates), Much less bandwidth, Easier to work with in terms of flexibility and robustness
Fiber Cables Types
MMF Grades (OM3 & OM4) (Optical Multi-mode)
• OM4 <3.0 dB/km (more widespread)
• OM3 <3.5 dB/km (more popular with the advent of 40 GbE and 100
GbE networks)
156

Fiber Cables Types
Input
multi-wavelength light
Single-wavelength light
Output
Dispersion
Dispersion
Dispersion
Unusable
Maximum Achievable
Light traveling from side to side takes longer going down the fiber than
light traveling straight so the signal at the end of the fiber is dispersed.
157

ST - Straight Tip Bayonet
• ST connectors have a key which prevents rotation of the ceramic ferrule, and a bayonet lock similar
to a BNC shell. Singlemode or Multimode.
LC - Lucent Connector
• Due to their small size; LC are often found on High-density connections, SFP and SFP+ transceivers
and XFP transceivers with a small form-factor. Singlemode or Multimode.
Neutrik OpticalCON Rugged LC
• In a broadcast environment, the opticalCON connector from Neutrik incorporates duo or quad
standard optical LC-Duplex connectors in a rugged metal housing. A shutter system protects the
connection from dirt, dust and damage. Single or Multimode.
SC - Subscriber Connector
• SC connectors offer excellent packing density, and their push-pull design reduces the chance of
fiber end face contact damage during connection. Singlemode or Multimode.
SMPTE Hybrid 304M Connector
• Developed by Lemo to meet the SMPTE 304M standard for HDTV camera fiber links in the broadcast
market, the connector incorporates two singlemode fibers, two power conductors and two low
voltage conductors in a single connector. Singlemode only.
Common Fiber Optic Connector Types
Lerno 3K.93C SMPTE 304M connector
158

Connectors for A/V IP Application
LC to LC Duplex (MMF or SMF cable)
• LC :Lucent Connector
• Duplex: Duplex (TX and RX path )
MPO (Multifiber-Push-On) and MTP Multicore (Multi-fiber Termination Push-on)
(MMF or SMF cable)
• The MPO/MTP is the specified connector for “short range” QSFP devices where the I/O
comprises four sets of TX/RX data streams.
• The MTP-12 and MTP-24 (12 & 24-way) are the designated sizes for the QSFP.
• MPO is a multifiber connector that is defined by IEC- 61754-7.
• MTP product is fully compliant with the MPO standard.
• MTP is a registered trademark of US Conec.
MTP to MTP Multicore Patch Cord
LC to LC Duplex Patch Cord
MTP-12 TX/RX MTP-24 TX/RX
QSFP 159

The SFP — Small Form-factor Pluggable (hot-pluggable transceiver)
SFP (100 Mb/s to 8 Gb/s)
SFP+ (10 Gb/s)
• Data rates up to 16 Gb/s (For broadcasting and media IP routing for 10 GbE connectivity)
• Multiple different variants (and vendors) that are not all interoperable
• It is wise to select products compliant with the SFP MSA (multisource agreement) and/or are IEEE 802.3ae designated types.
• Common types are
• SFP+10 GbE-SR (Short Range)
• SFP+10 GbE-LR (Long Range)
• SFP+10 GbE-ER (Extended Range)
• Typical maximum link lengths specified are 300m over OM4 MMF (SR), 10 km (LR) and 40 km (ER) over SMF.
SFP28 (25 Gb/s) [One 28 Gb/s lane: 25 Gb/s + error correction]
• SFP28 has the same common form factor as the SFP+, but supports 25Gb/s over a single lane.
QSFP (Quad-SFP) (QSFP-40G, QSFP-100G)
• Four standard SFP type devices integrated in a single “pluggable” package [4x (TX + RX)].
• 4x 1 GbE Channels = QSFP
• 4x 10 GbE Channels = QSFP+
• 4x 25 GbE Channels = QSFP28
160

The QSFP (Quad-SFP)
The QSFP is available in two basic forms:
First (MPO/MTP Connection)
• For short range multichannel transmission over
multicore OM3 & OM4 MMF (multimode) cable.
• More cost effective approach
• Typical maximum link: 100m for OM3 and 150m for
OM4.
Second (Duplex LC Connection)
• For longer links over duplex SMF (singlemode) cable.
• Typical maximum link: 1km to 40km for SMF
• By multiplexing and demultiplexing the four sets of
stream data using WDM (Wave Division Multiplex)
blocks incorporated within the QSFP itself (Different
optical wavelengths for each of the four transmitters)
Female-Female Type B MTP-12 cable for interconnecting two QSFP 100 GbE-SR4 modules.
(Type A: Straight-through, Type B: crossover cable, Type C: Crosspair )
Interconnection of 2x QSFP (WDM) using LC to LC Duplex SMF cable
TX
RX
QSFP+LC
RX
TX
QSFP+LC
161

Fiber Breakout Cables (QSFP 40 GbE & 100 GbE to 4x 10 GbE & 25 GbE)
The mode can be set independently for each 40 GbE/100 GbE port in the configuration file of the switch.
• 40 GbE and 100 GbE IP switch ports can be configured in normal and alternative modes.
• In each case the motherboard (or IP switch line card) presents the data to a QSFP in four lanes of 10 Gb/s or 25 Gb/s
respectively.
Break-out to 4x LC duplex (4x SFP+/SFP28)
MTP-4LC
MTP-12 MMF to IP switch QSFP+/QSFP28
162

Part No. Description List Price
QSFP-100G-SR4-S 100GBASE SR4 QSFP Transceiver, MPO, 100m over OM4 MMF $ 1,130.00 (43% OFF)
QSFP-100G-LR4-S 100GBASE LR4 QSFP Transceiver, LC, 10km over SMF $7,106.00 (76% OFF)
SFP-25G-SR-S 25GBASE-SR SFP Module $205.00 (79% OFF)
SFP-25G-SR-S 25GBASE-LR SFP Module $570.00 (79% OFF)
QSFP-40G-SR4 40GBASE-SR4 QSFP Transceiver Module with MPO Connector $925.00 (69% OFF)
QSFP-40G-LR4 QSFP 40GBASE-LR4 OTN Transceiver, LC, 10KM $2,780.00 (81% OFF)
SFP-10G-SR 10GBASE-SR SFP Module $225.00 (77% OFF)
SFP-10G-LR 10GBASE-LR SFP Module $980.00 (75% OFF)
Role of Single and Multi Mode Connectors
Metechno project by TPC and QVESTMEDIA (Start: NAB 2017)
BBC WALES (One of the four nations of the United Kingdom)
• SR (Short Range)
• LR (Long Range)
• ER (Extended Range)
SMF (Single Mode Fiber)
Up to 100 km and beyond
MMF (Multi Mode Fiber)
Up to 300m
Metechno and BBC WALES Projects
163

Edge Device (End-point Device)
− Any piece of equipment, software- or hardware-based, that is connected to a network but is not part of the
backbone infrastructure, which typically comprises the IP switch(es), cabling and network controllers.
− An Edge Device can be a “Source” (unicast or multicast) or a “Destination” (receiver) or both.
Third-Party Edge Device
− A company is able to write third-party drivers to allow inclusion of alternative vendors’ equipment in its IP
routing system.
− If a driver is not available within an existing library, a development charge may be requested for the
required work.
Edge Device and Third-Party Edge Device
165

− There are several kinds of network virtualization technology in use today.
− In core-edge-based networks, the network is divided into multiple VLANs at the edge IP switch which, in
turn, is connected to the core IP switch. This improves traffic accommodation efficiency.
− Other virtualization technologies have not been adopted at present, due to their lack of suitability in live
production network design.
− With IP Live, Sony adopts VLAN to improve traffic accommodation efficiency.
Network Virtualization Technology
166

IGMP: The Internet Group Management Protocol is used by clients & adjacent routers on IPv4 networks to establish multicast
group memberships (to leave and join).
• IGMP operates between a host and a local multicast router.
• IGMP can be used for one-to-many networking applications such as online streaming video and gaming, and allows
more efficient use of resources when supporting these types of applications.
PIM-SSM: Protocol Independent Multicast — Source Specific Multicast between routers & subnets.
• It is a family of multicast routing protocols for Internet Protocol (IP) networks that provide one-to-many and many-to-
many distribution of data over a LAN, WAN or the Internet.
IGMP and PIM-SSM Protocols
167
PIM-SSM IGMP IGMP

Software Defined Networks (SDN), What is it?
− SDN technology provides flexible network control that cannot be achieved with conventional IP switch
control. SDN networks divide IP switch functionality into a control plane and data plane.
− Separates network control from forwarding plane
− SDN can be implemented as it is often requested as a means of defining “secure paths” (connections) in
IP networks.
− Applications can control bandwidth in the network via API
− Open standards-based and vendor neutral
168

Two Main Ways of Routing in IP Networks
Automatically Routed IP Network
− Streams typically transported as multicast
− Connection thru control of edge device
• IGMP join message
Software Defined Network (SDN) Management
− Management layer takes control of IP routing
− SDN networks divide IP switch functionality into a control plane and data plane.
169
PIM-SSM IGMP IGMP

Media Service Management and Orchestration
Driver Driver
Rendevous Point
Multicast Group
Join Request
Routing via End-point Control
170

Driver Driver
Rendevous Point
Multicast Group
Join Request
Multicast
Group
Routing via End-point Control
171

SDN Control Protocol
SDN-based Routing Control
172

SDN-based Routing Redundancy
173

SDN-based Routing Redundancy
174

− OpenFlow is a programmable network protocol designed to manage and direct traffic among routers and
switches from various vendors. It separates the programming of routers and switches from underlying
hardware.
− Open-source communications interface between the control and forwarding layers within an SDN
architecture
1. Enables the Controller to interact with the forwarding plane and make adjustments to the network
2. Centralized management and control of flow-tables in networking devices from multiple vendors
OpenFlow- A Key Part of SDN
175

Switching
control
SRV
MON
IP
AGGREGATION
IP
CORE ROUTER
Generic IP
protocol Generic IP
protocol
Management of Switching
176

SRV
MON
IP
AGGREGATION
IP
CORE ROUTER
Switching
control
Generic IP
protocol
Driver A
Driver C
Driver E
Generic IP
protocol
Management of Switching, Edge Controlled
$
$ Driver B
$
$ Driver D
$
Link availability
MON
177

SRV
MON
IP
AGGREGATION
IP
CORE ROUTER
Bandwidth control
QoS visibility
(IGMP, VLAN , OpenFlow)
$
COST
&
TIME
SAVINGS!
Switching
control
Link availability
Generic IP
protocol
Driver A
Management of Switching, SDN Controlled
MON
178

SRV
MON
IP
AGGREGATION
IP
CORE ROUTER
Fixed IP
addresses
Driver A
(IGMP, VLAN , OpenFlow)
$ (IGMP, VLAN , OpenFlow)
Switching
control
$ Driver B
Path control
Management of Switching, SDN Controlled
Bandwidth control
QoS visibility
Link availability
MON
179

SDN (Software Defined Network):
• SDN can be implemented as it is often requested as a means
of defining “secure paths” (connections) in IP networks.
• For SDN deployments, a smaller subset of switches and their
control systems need to be designed into the IP fabric.
Ideally be non-blocking:
• A switch is said to be non-blocking if the switching fabric is
capable of handling the theoretical total of all ports, such
that any routing request to any free output port can be
established successfully “without interfering other traffics”.
• Router internal bandwidth must handle all the port
bandwidths at the same time & at full capacity.
The SDN can be used in cases where an IP switch does not meet
the above criteria.
COTS (Commercial Off The Shelf) Switches Considerations
180

Must be IGMPv3 compliant:
• The Internet Group Management Protocol is used by clients & adjacent routers on IPv4 networks to establish multicast
group memberships (to leave and join in switching).
• IGMP operates between a host and a local multicast router.
• IGMP can be used for one-to-many networking applications such as online streaming video and gaming, and allows
more efficient use of resources when supporting these types of applications.
Must support PIM-SSM:
• Protocol Independent Multicast — Source Specific Multicast between routers & subnets.
• It is a family of multicast routing protocols for Internet Protocol (IP) networks that provide one-to-many and many-to-
many distribution of data over a LAN, WAN or the Internet.
181

Must have very large bandwidth:
• Some of the largest enterprise-grade IP spine switches exhibit throughput capacity up to 115 Tb/s.
IP Switch Stream Capacity:
• The maximum stream capacities for each switch type and size.
Redundant IP Switches:
• It is possible to deploy different switches from alternative vendors.
• This approach hopes to avoid potential issues (affecting both switches) caused during a firmware
upgrade or such (It is unlikely two switch vendors would release upgrades at the same time).
182

Monolithic Switch
• Non Blocking Architecture
• No SDN Requirement to Manage Inter-Switch Links
• PTP Boundary Mode Considerations
• Mix and Match Spine and Leaf Options
• Increase East / West Traffic Flow Bandwidth
Spine / Leaf – Distributed
• Distributed Cabling
• Shared Uplink Bandwidth
• PTP Boundary Mode Considerations
• Mix and Match Spine and Leaf Options
• Inter-Switch Bandwidth Consideration
• Oversubscription Ratio
Leaf
Spine
Aggregation
Network Switch Topology Options
183

IP Audio and Video Router: Fixed Switches- Arista, Cisco, Juniper
High-performance and High-density Switches
7060CX2-32S
32-port QSFP switch.
A combination of speeds of 10, 25. 40, 50 and 100 GbE.
Nexus 9236C ($40,250)
36-port QSFP switch
A combination of speeds of 10, 25. 40, 50 and 100 GbE.
Nexus 9272Q ($35,000)
72-port QSFP switch housed
A combination of speeds of10 and 40 GbE.
QFX5200-32C
32-port QSFP switch
A combination of speeds of 10, 25. 40, 50 and 100 GbE. 184

IP Audio and Video Router: Fixed Switches-GV Fabric
Inputs/Outputs Quantity: 1280x1280 HD (3G, 50p) (320x320 UHD-1/4K, 50p)
Inputs/Outputs Quantity: 640x640 HD (3G,50p) (160x160 UHD-1/4K, 50p)
− The Grass Valley’s IP routing system can be based on a topology that inherently does not require SDN control.
− In such cases it uses IGMPv3 in a non-blocking multicast design only for communication with the switch fabric.
185

IP Audio and Video Router: Fixed Switches-GV Fabric
186

Modular Switches
CISCO Modular Switches
Arista Modular Switches
187

IP Audio and Video Router: Modular Switches-Arista
The 7500R Series of universal spine switches enable a full range of
port speeds from 1G to 100G.
188

IP Audio and Video Router: Modular Switches-Arista
Four, Eight or Twelve of any mix of the following line cards
DCS-7500R-48S2CQ-LC
• Up to 56 x 10 GbE ports or 48 x 10 GbE (SFP+) ports + 2 x 100
GbE (QSFP28) ports.
• QSFP28 ports can be configured as 2x 100 GbE or 4x 25 GbE
or 2x 40 GbE or 8x 10 GbE.
DCS-7500R-36Q-LC
• Up to 36 x 40 GbE (QSFP+) ports or 24 x 40 GbE (QSFP+) ports
+ 6 x 100 GbE (QSFP28) ports.
• 24x QSFP+ ports can be configured as 96x 10 GbE and/or 6x
QSFP28 ports can be configured as 24x 25 GbE ports.
DCS-7500R-36CQ-LC (Most flexible and highest density line card with
the greatest data throughput)
• 36 x 100 GbE (QSFP28) ports.
• All QSFP28 ports can be independently configured as 100
GbE or 2x 50 GbE or 4x 25 GbE or 40 GbE or 4x 10 GbE.
189

IP Audio and Video Router: Modular Switches-Cisco
Eight of any mix of the line cards below can be fitted in
the Nexus 9508 chassis.
N9K-X9636Q-R ($50,000)
• 36 x 40 GbE (QSFP+) ports.
• All QSFP+ ports can be independently configured as 40
GbE or 4x 10 GbE.
N9K-X9636C-R (Highest Data Capacity) ($75,000)
• 36 x 100 GbE (QSFP28) ports.
• This is the most flexible and highest density line card with
the greatest data throughput.
• All QSFP28 ports can be independently configured as
100 GbE or 4x 25 GbE or 40 GbE or 4x 10 GbE.
($21,306)
190

Notes for Calculating Values for ST 2022 and ST 2110 Stream Data Rates
− SDI signal data rates are stated in Mb/s for SD, HD, 3G and 4K UHD
− Each Ethernet port assumes a maximum utilization factor of 90%
− A packet overhead factor is applied to the SDI data rates to obtain the uncompressed SMPTE ST 2022 and
2110 rates in Mb/s. It includes headers for the Ethernet, IP, UDP & RTP layers, plus high level stream format for
SMPTE ST 2022.
− The data rate stated for compressed VC-2 HQ (SMPTE ST 2042) streams uses a nominal 2:1 compression
ratio.
− For each uncompressed SMPTE 2110 and each SMPTE ST 2042 compressed stream an additional 25Mb/s is
added representing 16 audio channels and metadata.
191

− Flow admission control
− Open switch APIs (Cisco DCNM, Arista, Openflow)
− Single Spine, Spine & Leaf, Distributed
− Flow agnostic (SMPTE 2110, SMPTE 2022-6, AES67, and more)
− Support for SMTPE 2022-7 hitless merge
− Endpoint management (NMOS and proprietary APIs)
− Real-time flow analysis via SCORE EDGE
− Clean-switching & Flow NATing as a service via SCORE EDGE
− Configuration and monitoring from a single web application
EVS Score Master
192

− With SMPTE ST 2110 streams, audio and ancillary data is streamed separately from the video data. Time stamping
of packets for these stream types is mandatory to allow realignment of the data types at the receiving host.
− Each receiver accumulates, de-encapsulates and then synchronizes all the streams to its internal clock which it
does by comparing all the packet timestamps with its own local time.
− All device clocks on a network (Senders, Receivers and, if desired the IP Switch itself) must be co-timed with
microsecond accuracy.
Why PTP (Precision-Timing-Protocol) is Needed?
Main language channel
Alternative language channels
Source
Video
TR-03 Sender
Group of
Elemental
RTP
Streams
Video
IP Network TR-03 Receiver 1
TR-03 Receiver 2
Audio
Video Video
Ancillary Ancillary Ancillary Ancillary
Audio Audio Audio Audio
Encapsulate,
Packetize
& Time Stamp
Accumulate,
Decapsulate &
Synchronize
Accumulate,
Decapsulate
&
Synchronize
Audio
195

Traditional SDI Systems
• The video and audio signals are synchronized to a continuous reference source and “delay blocks”
added to correct for lip-sync errors.
Packetized IP Systems
• The packets experience different delays through a network resulting in disruption of the packet
sequence.
• The data must be continually time-stamped for re-alignment downstream (to allow realignment of the
data types at the receiving host.)
The high level structure of a single SMPTE ST 2022-6 data packet
(The number of packets per second or packet rate is determined by the video format.)
Synchronization in Packetized IP Systems
196
“Epoch”
(reference start time and
date of the timescale), 16 bits
Second,
16 bits
Sub-second,
16 bits
Timestamp Format

SMPTE ST 2022-7 Redundancy Switching
• The argument for a packet timing mechanism is more apparent when considering redundant streams.
• A method of “hitless” or uninterrupted switching between two identical streams obviate the need to
have streams absolutely time-aligned which can only be achieved by individually time stamping
every packet.
Why PTP (Precision-Timing-Protocol) is Needed?
197

What is PTP (Precision-Timing-Protocol)?
198
− The goal of the PTP timing system is to synchronize all the clocks such that the absolute time difference
between any two clocks (i.e., their accuracy) is within a specified limit.
• This is typically about 1μs, which is more than adequate for broadcast and media applications that are
primarily interested in maintaining audio/ video lip-sync.

System Timing Standards
IEEE 1588-2008
• The IEEE 1588-2008 precision time protocol (specifically PTP v.2) provides a standard method to
synchronize multiple devices on a network.
• Standard for a Precision Clock Synchronization Protocol (Precision Time Protocol) for networked
measurement and control systems
SMPTE ST 2059-1 and SMPTE ST 2059-2
• They describe a specific media-based PTP profile required to use PTP-based equipment in the professional
broadcast and media industry.
o SMPTE ST 2059-1 2015: Generation and Alignment of interface signal to the SMPTE Epoch
o SMPTE ST 2059-2 2015: Profile for use of IEEE-1588 PTP in professional broadcast applications
IEEE 802.1AS
• Timing and Synchronization for time-sensitive applications in bridged local area networks.
AES 67
• Standard for audio applications of networks – High performance streaming audio-over-IP interoperability
199

SMPTE ST 2059-1
Defines SMPTE Epoch same as IEEE-1588
− Date 1970-01-01 Time 00:00:00 TAI (Epoch is 00:00, January 1, 1970 (This is the default epoch for PTP, but
can be changed to other scales))
− TAI (Temps Atomique International, French) International Atomic Time
Provides Alignment Points for:
− Analog Standard Definition Television
− SMPTE ST 318 Ten Field Sequence Identification
− Analog High Definition Television
− Digital High Definition Television
− Ultra High Definition Television (UHDTV)
− AES3 Digital Audio
− SMPTE ST 12-1 Timecode Generation
− SMPTE ST 309 Date
“Epoch” (reference start time and
date of the timescale), 16 bits
Second, 16 bits Sub-second, 16 bits
Timestamp Format
200

SMPTE ST 2059-2
PTP Profile Designed for:
− Slave to be synchronized within 5 seconds
− Maintain network-based time accuracy between two slave devices to master within 1μs
− To convey Synchronization Metadata (SM) required for synchronization and time labeling.
PTP Profile:
− Profile Identification
− Best Master Clock Algorithm (BMCA)
− Management Mechanism
− Path Delay Measurement Mechanism
− PTP Attribute Values
− Slave Clocks
− Clock Physical Requirements
− Node Types Required, Permitted or Prohibited
− Transport Mechanisms Permitted
− Communication Model
− PTP option
− Alternate Master
− Organization Extension TLV (Type Length Value) Synchronization Metadata Setting Dynamic SM (Synchronization Metadata)
− TLV (Type Length Value) Values
201

Grandmaster Clock
− Ultimate and primary source of time for clock synchronization using PTP
− It usually has a very precise time source, such as GPS but can “free-run” if
the GPS signal is lost.
Master Clock
− A clock that is the source of time to which all other clocks on that path or
domain are synchronized.
Slave Clock
− A clock that may synchronize to another clock
PTP Domain
− Logical grouping of clock that synchronize to each other using PTP, but
may not synchronized to other clocks in another domain.
PTP Terms and Definitions
PTP Domain 1 PTP Domain 2
Master
Clock
Slave
Clock
Slave
Clock
Master
Clock
Grandmaster
Clock
202

PTP Terms and Definitions
PTP
Grandmaster Clock
PTP
Slave
PTP
Slave
PTP
Slave
PTP
Slave
PTP
Slave
PTP
Slave
IP Switch
(Boundary Clock)
IP Switch
(Boundary Clock)
PTP
Slave
PTP
Slave
PTP
Master
PTP
Master
PTP
Master
PTP
Master
PTP
Master
PTP
Master
PTP Domain 1 PTP Domain 2
203

End Device on a network
(not a switch or router)
PTP Clock Types
1- Ordinary Clock
2- Boundary Clock
PTP Domain 2
PTP Domain 1
A PTP network: A network is made up of PTP-enabled devices.
204

1- Ordinary Clock
2- Boundary Clock
3-Transparent Clock
PTP Master - Boundary Clock
Sync Message
M
S
Camera – Ordinary Clock
(Slave)
PTP Clock Types
A PTP network: A network is made up of PTP-enabled devices.
PTP Domain 1
PTP Domain 2
Router – Transparent Clock
PTP Grand Master – Ordinary Clock
M
Sync Message
Sync Message (with correction)
S
Camera – Ordinary Clock
(Slave)
Sync Message (with correction)
S
205

1- Ordinary Clock
− A PTP clock with a single PTP port.
− It functions as a node in a PTP network and the BMCA (Best Master Clock Algorithm) determines whether it’s
a “master” or “slave” within a sub-domain.
 BMCA (Best Master Clock Algorithm) allows a clock to automatically take over the duties of Grandmaster when the
previous Grandmaster loses its GPS or gets disconnected.
− End Device on a network (not a switch or router)
− It is
 Slave only Clock (never acts as a Master)
 Preferred Grandmaster (never acts as a Slave)
 Master/Slave Clock (can be either)
PTP Clock Types
206

2- Boundary Clock
− A boundary clock has more than one PTP port.
− Each port provides access to a separate PTP
communication path (interface between PTP domains).
− Boundary clocks intercept and process all PTP
messages, and pass all other network traffic.
PTP Clock Types
− The boundary clock uses the BMCA to select the best clock seen by any port. The selected port is then set
as a slave to synchronize with the upstream master clock.
− All other ports are in master state, which synchronize the clocks connected downstream (e.g., edge
devices).
− Receives time from a Master on one Slave port
− Provides Multiple Master (not Grandmaster) ports to downstream Slaves in a domain
207

2- Boundary Clock
− An IP switch with a PTP boundary clock function can reduce network load as the data residence time in this
IP switch will not be counted.
• As a mechanism, the PTP master/slave function is assigned on each port of the IP switch.
• The PTP clock toward the end PTP slave device will be generated by a new PTP master port in the IP switch, which is
synchronized with the PTP clock from the slave port within the IP switch that originally synchronized with PTP grand
master.
• In addition, the boundary clock function facilitates building a large system as it can make a hierarchy structure to
reduce the load per PTP master.
PTP Clock Types
208

Example: Using Ordinary Clocks
GPS GPS
SUPPORTS UP TO 150 PTP SLAVES
VLAN 1
VLAN 1
VLAN 3 VLAN 4
VLAN 1
VLAN 1
GMA GMB
Layer 2
Layer 3
1 GbE 1 GbE
2x 1 GbE
10 GbE 10 GbE
Tektronix SPG8000A– BMCAPriority 1=1, 2=1 Tektronix SPG8000A– BMCAPriority 1=1, 2=2
PTPData Low
cost 10 GbE
(Copper/RJ45) Switch
PTPData
Low cost 10 GbE
PTP Data
GV Fabric
Media A
PTP Data
GV Fabric
Media B
25/50 GbE(ETH1) 25/50 GbE(ETH2)
End-points
− PTP communication between the Grandmaster and the IP End-points/Slaves (up to 150) is constrained to VLAN 1.
− Media data is confined to VLAN 3 (Main Switch) and VLAN 4 (Redundant Switch).
The BMCA is used to decide which Ordinary Clock assumes the role of “Grandmaster.”
209

Tektronix SPG8000A
1x PTP (RJ45), 1x PTP(SFP), free-run, genlock or GPS
GPS GPS
SUPPORTS UP TO 150 PTP SLAVES
VLAN 1
VLAN 1
VLAN 3 VLAN 4
VLAN 1
VLAN 1
GMA GMB
Layer 2
Layer 3
1 GbE 1 GbE
2x 1 GbE
10 GbE 10 GbE
Tektronix SPG8000A – BMCA Priority 1=1, 2=1 Tektronix SPG8000A – BMCA Priority 1=1, 2=2
PTPData
Low cost 10 GbE
PTPData
Low cost 10 GbE
PTPData
Media A
PTPData
Media B
25/50 GbE(ETH1) 25/50 GbE(ETH2)
End-points
Tektronix ECO8000
Blackburst / Tri-Level (Legacy)
BNC
BNC
Example: Using Ordinary Clocks
SPG & ECO:
PTP (IEEE 1588) support,
including SMPTE ST 2059-
2 and AES67 profiles
210

Example: Using Ordinary Clocks with Meinberg PTP boxes
GPS GPS
SUPPORTS UP TO 500+ PTP SLAVES
VLAN
1
VLAN 2
VLAN 2
Arista 7504R
VLAN 3
VLAN 4
VLAN
1
VLAN 2
GMA GMB
Layer 2
Layer3
1 GbE 1 GbE
1 GbE
1 GbE
PTP-Meinberg
1 GbE
PTP-Meinberg
1 GbE
2x 1 GbE
2x 1 GbE
10 GbE 10 GbE
Tektronix SPG8000A– BMCAPriority 1=1, 2=1
Meinberg L
TM1000 – BMCAPriority
1=4, 2=1
Meinberg L
TM1000 – BMCAPriority
1=4, 2=2
Tektronix SPG8000A – BMCAPriority 1=1, 2=2
PTP-Tek PTP-Tek
25/50 GbE
(ETH1)
Media A
Media B
25/50 GbE
(ETH2)
End-points
PTP-
Meinberg
− There is only a single modular media switch with redundancy covered using duplicate line cards.
− The system could be extended to dual media switches with VLAN 2 configured in both and with VLAN 3 (Media A) on one
switch and VLAN 4 (Media B) on the redundant switch.
Meinberg PTP boxes is used
to extend the edge device
capability to over 500.
PTP communication between
the Grandmasters and
Meinberg Slave ports are
confined to VLAN 1 and the
Meinberg downstream PTP
communications to VLAN 2.
211

SDI to IP 2110 Transition Part 1

SDI to IP 2110 Transition Part 1

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a SDI to IP 2110 Transition Part 1

Similar a SDI to IP 2110 Transition Part 1 (20)

Más de Dr. Mohieddin Moradi

Más de Dr. Mohieddin Moradi (9)

Último

Último (20)

SDI to IP 2110 Transition Part 1