Designing an 4K/UHD1 HDR OB Truck as 12G-SDI or IP-based

1
MOHIEDDIN MORADI
mohieddinmoradi@gmail.com
Dream
Idea
Plan
Implementation

OSI (Open System Interconnection) Model
3

Comparison Between OSI and TCP/IP Model
4
TransmissionControlProtocol/InternetProtocol
OpenSystemInterconnection

Comparison Between OSI and TCP/IP Model
5

6
IP – Internet Protocol (– Layer 3)

7
IP – Internet Protocol (– Layer 3)

– TCP is a standard that defines how to establish and maintain a network conversation via which application programs can exchange
data. TCP works with the Internet Protocol (IP), which defines how computers send packets of data to each other.
– TCP is Reliable
– Each Correct TCP-PDU is acknowledged by the receiver, acknowledgement must indicate which TCP-PDU is being acknowledged
– Heavyweight Protocol
• Full error correction
• Flow control
• Needs open, close processes
• Must acknowledge each TCP-PDU
• Places heavy load on sending and receiving hosts
• Adds to network traffic overhead
• Creates latency in delivering application PDUs to application programs
8
Transmission Control Protocol (TCP) – Layer 4

– Alternative to TCP at transport layer, Lightweight Transport Layer Protocol
– Connectionless datagram
• Connectionless (Like IP)
• No open, close, acknowledgement
• No error correction
• No flow control
• Low processing load on hosts
• Low network traffic overhead
• Low latency in delivering application PDU
– When to Use UDP
• Occasional loss of data is rarely a problem
• Low traffic overhead is crucial to avoid overloading the network
9
UDP Datagram Format
UDP – User Datagram Protocol– Layer 4

Internet Group Management Protocol (IGMP)
– The Internet Group Management Protocol (IGMP) is a communications protocol used by hosts and adjacent
routers on IPv4 networks to establish multicast group memberships. IGMP is an integral part of IP multicast.
– 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.
– IGMP is used on IPv4 networks. Multicast management on IPv6 networks is handled by Multicast Listener Discovery
(MLD) which is a part of ICMPv6 in contrast to IGMP's bare IP encapsulation.
11

• RTP is defined in IETF RFCs 3550 and 3551 and actually consists of two closely-
linked parts:
• Real Time Protocol; 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.
Real Time Protocol (RTP) – Layer 5
12

• Method for finding a host's hardware address when only its IP address is known. ARP is primarily
used to translate 32 bit IP addresses to 48 bit Ethernet MAC addresses
• A host with an IP address of 192.168.10.10 andMAC address of 00:01:f8:12:3f:54 wants to
send to 192.168.10.121 but does not know its MAC address.
• An ARP request is broadcast to thenetwork
• If the host at 192.168.10.121 is running, it will receive the ARP request and reply with its IP and
MAC addresses
• Any other hosts on the same network will receive the request and cache the results.
• Type arp – a on WindowsPC.
Address Resolution Protocol (ARP)
13

MPEG Transport Stream (TS)
– ISO/IEC 13818-1 and ITU-T Rec. H.222.0
– 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)
– Over 75 of mappings into MPEG TS
• SMPTE Registration Authority, LLC is the registration authority for ISO/IEC 13818-1
• Besides MPEG video: KLV Data, Dolby Vision, Camera Positioning Information, VC-1, VC-4, Dirac, AES3,
Dolby TrueHD audio…etc
14

MPEG TS – Logical View
15
Program Association Table (PAT)
Program # 100 – PMT PID 1025
Program # 200 – PMT PID 1026
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 Map Table (PMT)
Program # 200
Video PID – 601 – AVC Video
Audio PID (English) – 602 – AAC Audio

MPEG TS – Packet View
16
Example Transport Stream Packet
188 Bytes
Header
Flags
• Transport Error Indicator
• Payload Unit Start Indicator
• Transport Priority
• Transport Scrambling Control
Important PIDs
• 0x0000 – PAT PID
• 0x1FFF – “Null PID” gives
space for VBR
Continuity Counter (CC)
• 4-bit per-PID sequence #
• Helps detect packet loss
Adaptation Field (optional)
• Can carry range of other info
• PCR, splice point flags
• Transport of private data
Example Transport Stream
0x47
(sync) Flags
PID
(Payload ID)
More
Flags
CC Adaptation
Field
Data Payload
PID
0
CC
3
PAT
Data
PID
601
CC
11
PID
602
CC
7
PID
0x1FFF
NULL PID
601
CC
12
PID
602
CC
8

Asynchronous Serial Interface (ASI)
– Asynchronous -> no clock line, just self-clocked data
– European Standard EN 50083-9 Annex B
– Bottom layers Fibre Channel physical & signaling interface (FC-PH)
– Data transmission rate 270 Mbps on 75Ω coax or fiber
– 8-bit data converted to 10-bit for transmission for “DC-balance”
– Don’t have to use all 270 Mbps
• “Comma” 10-bit symbol inserted when no data ready to transmit
• Ignored by receivers
• Allows any bit rate <270 Mbps
17

Asynchronous Serial Interface (ASI)
18
Connector
Coupling/
Impedance
Matching
Amplifier/
Buffer
Clock/Data
Recovery &
Serial/Parallel
Conversion
Sync Byte
(FC Comma)
Deletion
8B/10B
Decoding
Packet- Synchronous
MPEG-2 TS
Coaxial
Cable
Connector
Coupling/
Impedance
Matching
Amplifier/
Buffer
Parallel/Serial
Conversion
Sync Byte
(FC Comma)
Insertion
8B/10B
Coding
Packet- Synchronous
MPEG2 TS
Layer-0Layer-1Layer-2

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)
19
2007
2007
2010
2011
2012
2012
2013

ST 2022-6: SDI over RTP
– SMPTE 2022-6 is the most common uncompressed video format and is included at the
beginning of the AIMS roadmap
– 2022-6 can be thought of as intra-facility or transport from one broadcast core to
another. Think of 2022-6 as an SDI Embedded snapshot converted to IP. It contains all
the elements of current SDI
• FEC (2022-5) is one reason why it’s a good choice for long haul
• Hitless switching feature in 2022-7 for backup and redundant schemes
21

22
ST 2022-6: SDI over RTP
– Video, Audio and Data must be embedded before being packetized
– For Audio processing, the audio must be de-embedded and then re-embedded
SMPTE ST 2022-6

ST 2022-7: Seamless Protection Switching (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.
23
Port 1
Port 2
Edge Device
Host Receiver
Packet
Merge /
Arbitrate
Edge Device
Host Transmitter
Port 1
Port 2
Buffer / Delay
1 Frame / 20ms

Design considerations for an IP infrastructure
– Standards – Which ones ? Do we care ?
– IP Conversion (to/from SDI) – Amount ? Formats ?
– IP Conversion (to/from MADI) - Amount ? Formats ? Processing ?
– Native IP Devices – Amount ? Format ? Control ?
– Signal Processing – Video ? Audio ? Transportation ?
– Multi-viewers – Amount ? Formats ? Layouts ? Tally ? Control ?
– Connectivity – 1.5, 3 or 12Gbps ? 10, 25, 40, 50 or 100Gbps ?
– Network Design – Singular switch ? Spine/Leaf ? Modular ? L2 or L3 ?
– Control & Monitoring System – Topology ? Performance ? Licensing ? SNMP ?
– Timing – Legacy BB/TL ? PTP ? Ordinary ? Boundary ?
– System redundancy – All or Core Components ?
24

Correlation chart of IP format related bodies
25

AIMS (Alliance for IP Media Solutions): A True Consortium of Today’s Best
26
The Role of AIMS: To foster adoption of the work of these organizations with regard to IP interoperability
Utah Scientific and over 55 AIMS Members!

• Member of all relevant Standards organizations
• One of five Founding members of AIMS*
• One of ten Principal members of AMWA*
AIMS Roadmap
Standards
To foster the
adoption of the
work of these
organizations
with regard to
IP
interoperability
Reference Architecture
The Role of AIMS
Technical
Recommendations
*AIMS – Alliance for IP Media Solutions *AMWA – Advanced Media Workflow Association
AMWA
AIMS (Alliance for IP Media Solutions) Roadmap

SMPTE 2110 (TR-03/04)
– 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
29
SMPTE ST 2110
ST 2110-30
ST 2110-10
ST 2110-20

Video Services Forum TR-03
• Video, Audio and Ancillary data carried as separateelementary
RTP streams
• Video Streaming per RFC 4715
• Audio Streaming per AES67
• Synchronization using IEEE1588 Default Profile
• Session Description Protocol RFC4566 for synchronous playout of streams
• Session Announce ProtocolRFC2974
Video Services Forum TR-04
• Builds up on TR-03
• Defines 2022-6 as video payload
• Integration of 2022-5 FEC and 2022-7
• Audio Streaming Embedded SDI or AES67
• Metadata via SDP (Session DescriptionProtocol)
48
Video Services Forum TR-03/04
30

SMPTE ST 2110 Professional Media over IP Infrastructure
32

33

34

35

36

37

38

The SMPTE ST 2110 suite of standards!
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 ST 2110 – 20 (Uncompressed Video – RFC 4175)
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 – 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 – 40 (Ancillary Data – VANC based on IETF ANC 291)
SMPTE 2022-7 (Seamless Protection Switching of SMPTE ST 2022 IP datagrams)
39

– SMPTE 2022-6 (The start)
– AIMS uses VSF TR-03/04, an Open Standards Initiative
– TR-04 for 2022-6 and AES67
– TR-03 for RFC 4175 Video Elementary Stream to replace 2022-6 (TR-03 aka SMPTE 2110 Draft)
– RFC 4175 Video : RTP Payload Format for Uncompressed Video
– RFC 3190 Audio: RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled Audio
– AES 67 Audio: A standard to enable high-performance audio-over-IP streaming
– SMPTE 2059: PTP Timing for A/V Sync and Genlock (Standard with roots to IEEE 1588)
– NMOS IS-04: For Discovery & Registration
– ST 291: RTP Payload Format for Ancillary Data Packet
– SDP (Session Description Protocol): describes the contents of the multicast transmission
40
The SMPTE ST 2110 suite of standards!

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
48

AES67? Same protocol is needed!!
49
– AES67 is a set of rules for existing and future protocols to follow.
– 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.
– 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
– 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.

50
AES67? Same protocol is needed!!
–Uncompressed Audio adopted by the AES/ Prevalent in 1Gb/sec Ethernet fabric/ 48 Khz sampling/ Multiple
channels (80 channels no problem)/ TIME STAMPS!!!

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

Ember (Embedded Basic Encoding Rules)+ control protocol
• mber 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. 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
52

Advanced Media Workflow Association (AMVA)
53

NMOS (Network Media Open Specification)
– NMOS is a family name for specifications produced by the
Advanced Media Workflow Association (AMVA) related to
networked media for professional applications.
54
Id Name Status Repository
IS-04
Discovery and
Registration
AMWA Specification
(Stable)
nmos-discovery-
registration
IS-05
Device Connection
Management
AMWA Specification
(Stable)
nmos-device-
connection-
management
IS-06 Network Control AMWA Specification nmos-network-control
IS-07 Event & Tally AMWA Specification nmos-event-tally
IS-08 Audio Channel Mapping AMWA Specification
nmos-audio-channel-
mapping
IS-09 System Work In Progress nmos-system
IS-10 Authorization Work In Progress nmos-authorization
MS-04 ID & Timing Model Work In Progress nmos-id-timing-model
BCP-002-01 Natural Grouping AMWA Specification nmos-grouping
BCP-003-01
API Security:
Communications
AMWA Specification nmos-api-security
BCP-003-02
API Security:
Authorization
Work In Progress nmos-api-security
n/a Parameter Registers Continuing
nmos-parameter-
registers

The NMOS Discovery and Registration API is documented in AMWA Specification IS-04 providing a way for network-
connected devices to become listed on a shared registry, and it provides a uniform way to query the registry. It also describes
a method for peer-to-peer discovery in order to permit operation on a link-local only or smaller network deployment.
• AMWA IS-04 NMOS Discovery and Registration Specification (Stable) (Oct. 2017)
• Defines a methodology to register a device’s services (available outputs and inputs and configuration) and discover
other devices on a network that it is compatible with and can connect to. IS-04 is part of the Network Media Open
Specification (NMOS) project within AMWA.
• HTTP Registration API that Nodes use to register their resources with a Registry.
• HTTP Query API that applications use to find a list of available resources of a particular type (Device, Sender, Rec.) in
the Registry.
• HTTP Node API that applications use to find further resources on the Node.
• How to announce the APIs using DNS-SD, so the API endpoints don’t have to be known by Nodes or Applications.
• How to achieve “peer-to-peer” discovery using DNS-SD and the Node API, where no Registry is available.
• AMWA IS-05 NMOS Device Connection Management Specification (Stable) (Oct. 2017)
• Enables a client or controller application to create or remove media stream connections between sending and receiving devices.
55
NMOS (Network Media Open Specification)/(AMVA) Advanced Media Workflow
Association

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

NMOS IS-04 Discovery and Registration
• Central Registry
• Resources: Nodes, Devices, Sources, Flows, Senders & Receivers
• Identity: GUID for every resource
57

NMOS IS-05 Connection Management
58
• Send Connection parameters to Receiver
Device via IS-05
• Notification via IS-04 websocket

59
(AMVA) Advanced Media Workflow Association
• AMWA IS-07 NMOS Event & Tally Specification [Work in progress]
• Provides an IP-friendly mechanism to carry time-sensitive information
• For example: camera tally information, audio levels, control panel button presses and status
• ST 2110 does not provide an equivalent to GPI functionality
• Danger of multiple proprietary approaches
• Consistency with other NMOS specifications
• Media Nodes emit and consume state and state change info
• Lightweight messages sent using WebSockets or MQTT
• Message flows connected using IS-05

60
(AMVA) Advanced Media Workflow Association
• AMWA IS-08 v1.0 Audio Channel Mapping
•Allows channel-level operations within NMOS environments
•For example: muting channels, swapping languages…
•Expected functionality for real world use
•Not included in IS-05’s functionality
•Controller gets channel information from sending Node
…and sends mapping matrix to the receiving Node
•Can also do sender-side matrixing

61
Tektronix SPG8000A
Meinberg LANTIME M1000
BB / TL
Slave
PTP
Grandmaster
PTP
Slave
PTP
Slave
IP Gateways
Production
Switcher
Camera
Target ΔT between all devices:
≤ 1.0 microsecond (Lock time < 5s)
M1000
• Up to 4 PTP ports/modules
• Free run or Genlock GPS option
• It can be slaved to SPG8000A to
circumvent high client count issues
* Slave
* Reduces multicast traffic, protects
edge devices
Ordinary or Boundary Clock
(COTS dependent)
2-Unicast to PTP Grandmaster
1.Multicast to Edge Devices
“Epoch”
(reference start time and
date of the timescale), 16 bits
Second,
16 bits
Sub-second,
16 bits
Timestamp Format
Precision-Timing-Protocol (SMPTE ST 2059-1 and -2) for synchronization

PTP Terms and Definitions
• Grandmaster Clock
◦ Ultimate source of time for clock synchronization using PTP
• Master Clock
◦ A clock that is the source of time to which all other clocks on that
path 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
62
PTP Domain 1 PTP Domain 2
Master
Clock
Slave
Clock
Slave
Clock
Master
Clock
Grandmaster
Clock

IP-based Networks System Timing
In 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.
In “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.)
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.
63
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.)

Precision-Timing-Protocol (PTPv.2)
64
Main language channel
• 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.
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
Encapsula
te,
Packetize
& Time
Stamp
Accumulate
,
Decapsulat
e &
Synchroniz
e
Accumulate,
Decapsulate
&
Synchronize
Audio

• The IEEE 1588-2008 precision time protocol (specifically PTP v.2) provides a standard method to synchronize multiple
devices on a network.
• SMPTE ST 2059-1 and SMPTE ST 2059-2 describe a specific media-based PTP profile required to use PTP-based
equipment in the professional broadcast and media industry.
• 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 one microsecond, which is more than adequate for broadcast and media applications that are
primarily interested in maintaining audio/ video lip-sync.
65

• A “Master” Sync Pulse Generator multicasts sync packets across the network.
• Each “Slave” (Edge) device communicates periodically with the master to best determine the transmission delay associated with the
sync data.
• Each “Slave” (Edge) device then re-aligns its local clock accordingly.
• Each multicast source can now timestamp all transmitted data packets with the exact time they exit the device.
• Likewise a receiving host can buffer and synchronize the time-stamped packets to its local clock.
Master SPG Failure
• One advantage of PTP over other network timing systems (such as NTP) is that it has built-in support for redundancy and failover.
• If a PTP grandmaster node fails, the next-best node will automatically take over as grandmaster.
Timestamp Format
• Epoch is 00:00, January 1, 1970 (This is the default epoch for PTP, but can be changed to other scales).
66
“Epoch” (reference start time and date of
the timescale), 16 bits
Second, 16 bits Sub-second, 16 bits

PTP Clock Types
A PTP network: It is made up of PTP-enabled devices.
Grandmaster Clock:
• The 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.
Ordinary Clock:
• A PTP clock with a single PTP port. It functions as a node in a PTP network and the BMCA determines whether it’s a “master” or
“slave” within a sub-domain.
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.
• 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).
Transparent Clock:
• This clock type in a PTP network updates the time-interval field in the PTP event message. It compensates for switch delay with an
accuracy of less than one picosecond.
67

PTP boundary clock
• PTP boundary clock is one of the
countermeasure technologies defined as
IEEE1588.
• 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.
68

Best Master Clock Algorithm (BMCA)
69
• It allows a clock to automatically take over the duties of Grandmaster when the previous Grandmaster loses its GPS or gets
disconnected. In essence a clock “makes announcements” and “listens for announcements” from other clocks.
• The first thing a clock does after power up is listen for announce messages from the PTP general multicast address. An announce
message contains the properties of the clock which sent it.
• If the Ordinary Clock sees an announce message from a better clock, it goes into a slave state (or passive if not slave capable).
• If the Ordinary Clock does not see an announce message from a better clock within the “Announce Time Out Interval,” then it takes
over the role of Grandmaster.
• Master capable devices are constantly on the lookout for the loss of the current master clock.
• It’s important that the “Announce Time Out Interval” is set longer than the “Announce Interval” in the network!
What makes one master better than another?
• The decision is based on a number of parameters (with defined precedence) including “Clock Class,” “Clock Accuracy,” etc.
There are two “Priority Fields.”
• Priority 1 is an 8-bit user-settable value where the lowest number wins! It can be used to establish any pecking order required.
• Priority 2 is at the low end of the decision tree, allowing system integrators to identify primary and backup clocks among identical
redundant Grandmasters.

Examples Using Ordinary Clocks
• The BMCA is used to decide which Ordinary Clock assumes the role of “Grandmaster.”
• 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).
70
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

Examples Using Ordinary Clocks with Meinberg PTP boxes
• 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.
• 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.
71
GPS GPSSUPPORTS 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
Layer 3
1 GbE 1 GbE
1 GbE1 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 LTM1000 – BMCAPriority
1=4, 2=1
Meinberg LTM1000 – BMCAPriority
1=4, 2=2
PTP-Tek PTP-Tek
25/50 GbE
(ETH1)
Media A
Media B
25/50 GbE
(ETH2)
End-points
PTP-
Meinberg

Examples using Boundary Clocks
• Utilizes the boundary clocks contained within the Media switches for synchronizing end-point timing.
• Each switch can accommodate up to 400 end-point slaves. The BMCA in each switch detects the higher priority grandmaster PTP
multicast and sets the associated receiving port as a slave to synchronize with the upstream master clock .
• Its remaining ports become “masters” for synchronizing the end-point slaves. Note the priority 1 and priority 2 BMCA settings for PTP
hierarchy.
72
GPS GPS
VLAN
1
VLAN 1 VLAN 1
VLAN 3 VLAN 4
VLAN
1
GMA GMB
Layer2
1 GbE 1 GbE
2x 1 GbE
Virtual Chassis Link
Arista 7504R (Main)
Boundary Clock
BMCA:
Priority 1=4
Priority 2=1
Arista 7504R (Redundant)
Boundary Clock
BMCA:
Priority 1=4
Priority 2=2
PTPData PTPData
Low cost 10 GbE
Media A Media B
25/50 GbE(ETH1) 25/50 GbE(ETH2)
End-points
10 GbE 10 GbE
Layer 3
PTP Data PTP Data

Introduction to Network Synchronization
Network synchronization is realized by the combination of:
• IEEE 1588 PTP for time synchronization
• SMPTE draft ST 2059 for AV signal synchronization
The Sync, Delay_Req and Delay_Res are typical PTP messages.
t1: the time that a sync message is sent from grandmaster
t2: the time that a sync message is received by slave
t3: the slave then sends a Delay_Req message back to the
grandmaster registering this time as t3.
t4: the grandmaster registers the time that the message is
received as t4 abd sends Delay_Res message with t4 to the
slave.
This messages-exchange cycle is repeated periodically and the slave
obtains a set of timestamps (t1, t2, t3 and t4 in each cycle) which it
uses to synchronize its time with that of the grandmaster.
73

Introduction to Network Synchronization
• Using the diagram above as a reference, the
Slave is now able to calculate the difference
between its own clock and that of the
Grandmaster using the Master-to-Slave sync
packet delay (T2- T1) and Slave-to-Master delay
request packet-delay (T4-T3). The Offset (Slave
Time – Master Time) = [(T2-T1)-(T4-T3)]/2 and the
Oneway delay = [(T2-T1)+(T4-T3)]/2. For the slave
time to be now correct, the propagation delay in
both directions must be equal.
• If the propagation delay in both directions is in
fact different, then the slave is offset to “correct”
for this by adjusting its clock to a value of half the
asymmetry. The clock’s control loop adjusts the
slave time to make the Master-to-Slave and
Slave-to-Master propagation delays appear to be
equal. That is, the control loop adjusts the slave
time such that T2-T1 = T4-T3.
74

The JT-NM (Joint Task Force on Networked Media) Roadmap
– 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.
75

JT-NM (Joint Task Force on Networked Media) – AMWA/EBU/SMPTE/VSF
76
– It was formed by the European
Broadcasting Union, the Society of
Motion Picture and Television
Engineers and the Video Services
Forum 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.) that is currently
taking place in the professional
media industry.

JT-NM Interoperability planes
Media Transport •SMPTE 2022-6, VSF TR-4,VSF TR-03, SMPTE RDD 37(ASPEN),…
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**
77

JT-NM Tested Program Catalog for NAB and IBC 2019
79

Minimum user requirements to build and manage an IP-based media facility
80Ref: TECH 3371, December 2018

A 12G-SDI or Full-IP OB Truck Design
82

83

VDR / Engineering / 2nd Production Area
Main Production Area / Slo-Mo
Audio Area
84

85

Audio Area
Rear Speakers
Main Entrance
Centre Speaker
Side Expansions
Audio Area Entrance
Audio Mixer
Lockable Cupboard
Front R Speaker Front L Speaker
Lobby
Subwoofer
Audio Equipment Racks
86

Audio Area
87

88
• STAGETEC NEXUS supports various IP-based
technologies ranging from multichannel audio
transmission to Dante or AES67 to numerous
control methods.
Stagetec CRESCENDO platinum
Audio Mixer
Dante Board for NEXUS

89
SSL System T - S300
A comprehensive range of interfaces for Dante, AES67
and SMPTE 2110 audio networks.
Audio Mixer
AES to Dante conversion

90
Dante Avio AES IO
Adapter 2x2
Denon, DN-900R
Network SD/USB Solid State Recorder (Dante 2-in/2-out interface)
Audio Player/recorder and Convertors
YAMAHA RO8-D
DANTE interface 8 line output
TASCAM
DANTE interface 4 line output

91

Main Production Area / Slo-MoRear
Speakers Slo-Mo Remote Controllers
Centre Speaker
Side
Expansions
Character Generator
and Graphic System
Vision Mixer
Multiviewer
92

Main Production Area / Slo-Mo
93

Main Production Area / Slo-MoRear
Speakers
Slo-Mo Remote Controllers
(EVS XT-VIA)
Centre Speaker
Side
Expansions
Character Generator
and Graphic System
(VZRT, Viz Trio)
Vision Mixer
(Sony XVS-9000)
Multiviewer
(Grass valley MV-820- IP or MV-821
12G-SDI)
94

95
VZRT, Viz Trio with Matrox X.mio3 12G
• Half-length PCI Express card
• Up to two 12G SDI inputs, Up to two 12G SDI outputs
• Analog blackburst reference input (tri-level or bi-level)
• Onboard 4K scaler
• Onboard 4K compositor
• Up to 16 channels of AES/EBU inputs and outputs
Character Generator (CG)
VZRT, Viz Trio CG

96
Character Generator (CG)
Matrox X.mio3 IP / DSX LE 4 IP
• Dual SFP+ cages for a total of four video inputs and four video outputs
• IP (SMPTE ST 2059 PTP) and analog blackburst timing reference
• Guaranteed non-bursty packet transmission
• Onboard multi-channel Up/Down/Cross scaler
• Onboard multi-layer compositor
VZRT, Viz Trio CG

97
Live Production Server (Slow Motion Server)
EVS XT-VIA + XFile3
(XFile3 is connected archive and transcoding solution)
EVS XT-VIA + XFile3
• 12+ch FHD and HD (720p, 1080i, 1080p)
• 6ch UHD-4K (2160p) including integrated upscale from 1080p
• 2ch UHD-8K Supported on special edition (4320p)
• 10G Ethernet SFP+ (ST2022-6, ST2110 (-10, -20, -30, -40), NMOS IS-04, IS-05,
EMBER+, PTP)
• 3G-SDI and 12G-SDI selectable in software settings
• 192 uncompressed audio tracks (Embedded and MADI support)
• Internal storage of 9TB (Expandable to 40TB)
• Recording capacity of up to 130 hours of UHD-4K

IP Live switcher
• The core supports the SMPTE ST 2110
• A mixed IP and SDI production environment.
• 40G: 16 HD or 4 4K signals
• 100G: 16 HD or 8 4K signals
12G-SDI based live switcher
• Greater options for applications such as in-house
studios, OB vehicles and flypacks.
98
Video Production Switcher
Sony XVS-9000 Video Production Switcher

Start with only SDI and then replace SDI I/O card to IP
99
Low risk migration path from SDI to IP

HVS-6000IP-8IO IP Interface Card
• The SFP28 (25 GbE) × 8 modules installable (pairs for
redundancy)
• With a broadband architecture, 8 uncompressed 4K UHD
I/O streams can be processed per card
• Bandwidth and stream format can be set per SFP+ port
• SMPTE ST 2022 and ST 2110 support
• Ember+ support (planned for future support)
• AMWA NMOS IS-04/05 support (planned for future
support)
100
For-A HVS-6000 Video Production Switcher
HVS-6000
• 2 M/E standard, expandable 3 M/E
• Up to 80 In/32 Out or 64 In/48 Out in 12G-SDI
• 12RU
HVS-6000M
• 2 M/E standard, expandable 3 M/E
• Up to 32n/24 Out or 64 In/48 Out in 12G-SDI
• 7RU

Phabrix Qx
• HD/3G SDI as standard and options for UHD 12G-SDI,
HD/3G 2110 and 2022-6 payloads on 10G SFP+ interfaces.
Phabrix QxL
• HD/3G 2110 and 2022-6 payloads on 10G/25G SFP28
interfaces as standard, with options for IP to SDI gateway
101
Tektronix PRISM, MPX2-10
Measurement Equipment
Phabrix, Qx and QxL

102
For-A ESG-4200 12G-SDI and IP 4K/HD Test Signal Generator
Test Signal Generator
Phabrix, Qx and QxL

103
KudosPro UHD1200: 12G UHD Video & Audio Processor (12G-SDI)
FA-9600 For-A (12G-SDI)
Selenio™ Network Processor (SNP) (12G-SDI and IP SMPTE-2110)
• Number of Inputs/Outputs: 32 (bi-directional port shared with output) (8 are 12G-capable)
• 4 independent processing blocks for various operations (synchronization, conversion, UHD remap of SQD/2SI)
• IP Gateway, PTP synchronization of all video, audio and data streams
• SNP makes a “proxy” signal from every UHD signal it touches, and EPIC MV uses these proxy signals — which
are full-color, full-frame-rate, and typically HD resolution — rather than the UHD original
Audio and Video Processor

104
Multiviewers (12G-SDI)
Grass valley MV-821
48 12G-SDI inputs, Up to 12 outputs
Output SFP: 12G/6G/3G/HD/SD-SDI UHD video SFP (emSFP) coaxial,
dual transmitter, medium reach, non-MSA, HD-BNC, reclocked
For-A MV-4320
Up to 17 inputs for 12G-SDI

105
Multiviewers (IP)
R&S IP-based PRISMON multiviewer solutionGrass valley MV-820- IP
Inputs – 48 (from IP backbone), Up to 12 Output
• Support for IP based signal types (SMPTE 2022-1/2,
SMPTE 2022-6/7, SMPTE 2110-20/30, AIMS, AMWA NMOS
IS-04/05)
• Support for classic signal types (SDI, ASI) Selenio™ Network Processor (SNP)
• SNP makes a “proxy” signal from every UHD signal it
touches, and EPIC MV uses these proxy signals —
which are full-color, full-frame-rate, and typically
HD resolution — rather than the UHD original
Imagine’s EPIC™ MV multiviewer
Up to 48x SD/HD/3G over SDI inputs
Up to 24x SD/HD/3G over ST 2110 inputs)
Imagine’s EPIC™ MV multiviewer with the SNP Unit

106

Fold-down Steps
2nd Production Desk
Video Recorders/Players
Technical Manager Position
Camera Remote
Control Panels
Main Equipment Racks
Highest Quality “Grade 1” Monitors
Measurement Tools
107

2nd Production AreaEngineering AreaVDR Area
108

Fold-down Steps 2nd ProductionDesk
Video Recorders/Players
(HyperDeck Extreme 8K HDR
+ emVIEW-U-7-SDI
+ emFUSION-7-SDI)
Technical Manager Position
Camera Remote
Control Panels
(Sony RCP-1500)
Main Equipment Racks
(HDC-3500/5500 with 12G-SDI I/O or SMPTE-2110 I/O)
Highest Quality “Grade 1” Monitors
(Postium OBM-X310 + SFP module ST 2110)
Measurement Tools
(Tektronix PRISM, MPX2-10)
109

110
Postium OBM-X310 + SFP module ST 2110
Reference Grade 1 Monitor
Sony BVM-HX310
31-inch 4K TRIMASTER HX™ Professional Master Monitor
emVIEW-U-7-SDI

111
HyperDeck Extreme 8K HDR+ emVIEW-U-7-SDI + emFUSION-7-SDI
emVIEW-U-7-SDI emFUSION-U-7-SDI
Video Recorder/Player

112
Video Recorder/Player
For-A MBP-1000VS-12G and MBP-1000VS-IP

113
Normal, Super Slow Motion and Wireless Cameras
Normal Speed Camera: HDC-3500+HDCU-3500 + HKCU-SDI30 12G-SDI Extension Kit or HKCU-SFP50 ST 2110 Interface Kit
Super Slow Motion: HDC-5500+HDCU-5500 + HKCU-SDI30 12G-SDI Extension Kit or HKCU-SFP50 ST 2110 Interface Kit
Wireless Camera : HDC-3500+HDCU-3500 + HKCU-SDI30 12G-SDI Extension Kit or HKCU-SFP50 ST 2110 Interface Kit HKC-WL50
UA14x4.5BE, UA24x7.8BE, UA46x9.5BE
UA80x9 1.2x EXT
UA14x4.5BE, UA24x7.8BE, UA46x9.5BE

114
Tektronix SPG8000A
1x PTP (RJ45), 1x PTP(SFP), free-run, genlock or GPS
SPG & ECO: PTP (IEEE 1588) support, including SMPTE ST 2059-2 and AES67 profiles
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)
BNCBNC

115
Up to 4 PTP ports/modules, free-run, genlock or GPS
SPG & ECO: PTP (IEEE 1588) support, including SMPTE ST 2059-2 and AES67 profiles
GPS GPS
SUPPORTS UP TO 500+ PTP SLAVES
VLAN 1
VLAN 2
VLAN 2
VLAN 1
VLAN 2
GMA GMB
Layer 2
Layer 3
1 GbE 1 GbE
1 GbE1 GbE
PTP-Meinberg
1 GbE
PTP-Meinberg
1 GbE
2x 1 GbE
2x 1 GbE
10 GbE 10 GbE
Tektronix SPG8000A – BMCA Priority 1=1, 2=1
Meinberg LT M1000 – BMCA Priority 1=4, 2=1 Meinberg LT M1000 – BMCA Priority 1=4, 2=2
Tektronix SPG8000A – BMCA Priority 1=1, 2=2
PTP-Tek PTP-Tek
25/50 GbE(ETH1)
Media B
25/50 GbE(ETH2)
End-points
PTP-Meinberg
Media AVLAN 3
Arista 7504R
Arista 7504R
PTP-Meinberg
Tektronix ECO8000
Blackburst / Tri-Level (Legacy)
BNCBNC
VLAN 4
VLAN 2

116
Evertz EQXUHD–10 HD/3G/12G SDI
Up to 160x160 12G–SDI video crosspoint, Multiviewer Processor Integration
12G-SDI Audio and Video Router
Ross Ultrix: HD/3G/12G SDI
Up to 160x160 12G–SDI video crosspoint, Multiviewer
Processor Integration ($200,000)

IP Video Routers: A little about COTS Switch (Commercial Off The Shelf )
COTS Switches Considerations
Must have very large bandwidth:
• Some of the largest enterprise-grade IP spine switches exhibit throughput capacity up to 115 Tb/s.
Ideally be non-blocking:
• Router internal bandwidth must handle all the port bandwidths at the same time & at full capacity.
The SDN (Software Defined Networking) can be used in cases where an IP switch does not meet the above criteria.
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).
Must support PIM-SSM:
• Protocol Independent Multicast — Source Specific Multicast between routers & subnets.
117
RTP – Real-Time Protocol

Additional Considerations
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.
• 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.
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).
IP Switch Stream Capacity:
• The maximum stream capacities for each switch type and size. 118
IP Video Routers: A little about COTS Switch (Commercial Off The Shelf )

Ex: GV Fabric — Fixed Switches
119
1280x1280 HD (3G) (320x320 UHD-1) signal , 50p
640x640 HD (3G) (160x160 UHD-1) signal, 50p

Ex: GV Fabric — Fixed Switches
120

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
Network Switch Topology Options
121
Leaf
Spine
Aggregation

122
Modular Switches
CISCO Modular Switches
Leaf
Spine
Aggregation
Monolithic Switch
Arista Modular Switches

Ex: Arista Modular Switches
123
The 7500R Series of universal spine switches enable a full range of
port speeds from 1G to 100G.

Ex: Arista Modular Switches, Line Cards
124
Four, Eight or Twelve of any mix of the following line cards
DCS-7500R-48S2CQ-LC
• Up to 56x 10 GbE ports or 48x 10 GbE (SFP+) ports + 2x 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)
• 36x 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.

Ex: Cisco Modular Switches, Line Cards
125
Eight of any mix of the line cards below can be fitted in the
Nexus 9508 chassis.
N9K-X9636Q-R ($50,000)
• 36x 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)
• 36x 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)

Fixed Switches
126
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
Nexus 9272Q ($35,000)
72-port QSFP switch housed
A combination of speeds of10 and 40 GbE.
QFX5200-32C
32-port QSFP switch

Video
Audio
Data
Video + Audio + Data
Fiber (SM/MM)
SFP*
12G/3G/HD/SD-SDI
Dual Transmitters (2x Tx)
Dual Receiver (2x Rx)
Transceiver (Tx/Rx)
AES MADI 100Mb/s (Tx/Rx)
SFP* – ‘Small Form-factor Pluggable’
Connectivity
Copper
Traditional
SDI & AES Router
Rear View
Video
Audio
Multi-way ‘D’ type for
Analog & AES Digital.
BNC for MADI
BNC HD-BNC
SDI Video + Embedded Audio (x16)
+ User data (270Mb/s, 1.5/3 12/ Gb/s)
SDI Video
(270Mb/s, 1.5/3Gb/s, 12Gb/s)
AES Digital Audio
(3Mb/s – 48kHz sampling)
Balanced - Differential
Unbalanced - Single Ended
RS485 Serial - Older systems!
(Separate or integrated)
Currently more likely separate
100MbE or GbE IP Switch
Traditional Broadcast and Media routing
128

129
SDI Cables and Connectors
-
5.0
10.0
15.0
20.0
25.0
30.0
FULL HD
1920× 1080, 50i
FULL HD
1920×1080, 50p
FULL HD
1920×1080, 50p
(HDR+WCG)
4K/UHD1
(HDR+WCG)
8K/UHD2
(HDR+WCG)
1.5Gb/s
3Gb/s
3Gb/s
12Gb/s
24Gb/s
Gb/s
Belden 1855
52m
Belden 1855
52m
Belden 1855
87m
Belden 1855
46m
Belden 4731R/4731ANH
117m
CANARE L-8CUHD
148m
PERCON VK 90 Silver+
173m

130
Features & Benefits
• Screen and cable jacket crimp instead of
screen crimp only. Grooved inner surface holds
the cable jacket to prevent tearing braids.
• High frequency optimized insulator design for
UHD-transmissions.
• Reduced pin crimp diameter for performance
improvement (return loss values).
• Swiss antraloy plating rearTWIST boot for easy
access in high density applications.
Neutrik BNCs – Excellent return loss!
CANARE 12G-SDI Video
Patchbay (32MCK-ST)

132
Maximum length = 30 dB loss at 1/2 the clock frequency
(SMPTE ST 259, 143,177, 270 ,360 Mb/s)
(SMPTE ST 292 (1.5 Gb/s) & ST 424 (3 Gb/s) )
(SMPTE ST 425 (3Gb/s - stereo) , ST 2081 (6 Gb/s), ST 2082 (12 Gb/s) & ST 2083 (24 Gb/s))

133
CANARE 12G-SDI Video Patchbay (32MCK-ST)
CANARE 12G-SDI Video Patchbay (32MCK-ST)
• 1RU, 32ch Across
• Return Loss of 4dB or greater @ 12.0GHz
• Isolation: 45dB or greater @ 6.0GHz
• Touch spring type switch
• Front connector: Canare original micro video port
• Dust proof shutter design within the front patch
• Standard BNC rear connections
• Normal Through 32MCK-ST Panel Loaded with MCVJK-STW
• Straight Through 32MCK-STS Panel Loaded with MCVJK-STS
• MCVPCxxx Series Patch Cords available in standard and
custom lengths.

134
Imagine Selenio™ Network Processor
Gateway, IP-IP Processing, Sync, NAT
13×Sony HDC-3500/5500
XVX-9000
EVS-XT-via
Stagetec CRESCENDO platinum Denon, DN-900R Postium OBM-X310 Tektronix PRISM, MPX2-10
Blackmagic HyperDeck
Extreme 8K HDRI For-A ESG-4200 TPG
VIZRT CG
Display
Ultrix: 12G-SDI (96×96) with Multiviewer
Tektronix
2×SPG8000A+ECO8000

135
13×Sony HDC-3500/5500
XVX-9000
EVS-XT-via
Stagetec CRESCENDO platinum Denon, DN-900R Postium OBM-X310 Tektronix PRISM, MPX2-10
VIZRT CG
Display
Ultrix: 12G-SDI (96×96) with Multiviewer
Tektronix
2×SPG8000A+ECO8000
LAWO VSM (Virtual Studio Manager) Overall Controller
[vsmStudio : Router, UMD & Tally Control System]

Lawo VSM (Virtual Studio Manager): IP broadcast control and monitoring system
136

Mobile Production
vsm Studio: Heart of the VSM family of products
– To handle all configuration, administration and central
control
– Configuration changes occur in real-time with no download
or need for the system to be offline
– Offline configuration possible
– Remote access, control and support with standard secure IT
solutions
– Multiple server redundancy synchronization and seamless
change-over
– True real-time status monitoring of attached devices
– Virtual matrix view allows all router layers to be combined,
organized and controlled in custom XY views
– Redundant 3rd party driver connection engine for peace of
mind
– Monitoring and control can be combined into a single
workflow maximizing response times
137

*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
139

Fiber cables
SMF (Single Mode Fiber)
• Up to 100 km and beyond
MMF (Multi Mode Fiber)
• Up to 300m
• Much less bandwidth (greater modal dispersion over distance ).
• Easier to work with in terms of flexibility and robustness
• Useful up to 300m at 10 Gb/s to 100 Gb/s data rates.
• MMF Grades (OM3 & OM4) (Optical attention)
• OM4 <3.0 dB/km (more widespread)
• OM3 <3.5 dB/km (more popular with the advent of 40 GbE and 100 GbE networks)
140

Connectors
LC to LC Duplex (MMF or SMF cable)
• LC :Lucent Connector
• Duplex: Duplex (TX and RX path )
MPO (Multifiber-Push-On) anf 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.
141
MTP to MTP Multicore Patch Cord
LC to LC Duplex Patch Cord
MTP-12 TX/RX MTP-24 TX/RX
QSFP

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; SFP+ 10 GbE-LR; SFP+ 10 GbE-ER “ (“Short Range,” “Long Range” and
“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]
• It is a 25 GbE interface having evolved from 100 GbE, which is typically implemented with 4 × 25 Gb/s data lanes.
QSFP (Quad-SFP) (QSFP-40G, QSFP-100G)
• Four standard SFP type devices integrated in a single “pluggable” package) [4x (TX + RX)]. (4x 10 GbE Channels =
QSFP+ and 4x 25 GbE Channels = QSFP28)
142

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)
143
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

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.
144
MTP-12 MMF to IP switch QSFP+/QSFP28 Break-out to 4x LC duplex (4x SFP+/SFP28)
MTP-4LC

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)
Metechno and BBC WALES Projects (Role of Single and Multi Mode Connectors)
145
Metechno project by TPC and QVESTMEDIA (Start: NAB 2017)BBC WALES (One of the four nations of the United Kingdom)

PTP Terms and Definitions
• Grandmaster Clock
◦ Ultimate source of time for clock synchronization using PTP
• Master Clock
◦ A clock that is the source of time to which all other clocks on that
path 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
146
PTP Domain 1 PTP Domain 2
Master
Clock
Slave
Clock
Slave
Clock
Master
Clock
Grandmaster
Clock

147
Tektronix SPG8000A
BB / TL
Slave
PTP
Grandmaster
PTP
Slave
PTP
Slave
IP Gateways
Production
Switcher
Camera
Target ΔT between all devices:
≤ 1.0 microsecond (Lock time < 5s)
M1000
• Up to 4 PTP ports/modules
• Free run or Genlock GPS option
• It can be slaved to SPG8000A to
circumvent high client count issues
* Slave
* Reduces multicast traffic, protects
edge devices
Ordinary or Boundary Clock
(COTS dependent)
2-Unicast to PTP Grandmaster
1.Multicast to Edge Devices
“Epoch”
(reference start time and
date of the timescale), 16 bits
Second,
16 bits
Sub-second,
16 bits
Timestamp Format

Switch
Router
Router
Router
Switch
Switch
Switch
Who is
Grandmaster ?
Who is
Grandmaster ?
Who is
Grandmaster ?
148
Priority 1 defaultDS.priority1 Default Value 128
Lowest value wins (Range 0-255)

Switch
Router
Router
Router
Switch
Switch
Switch
defaultDS.priority1 = 128
I am
Grandmaster
149

Switch
Router
Router
Router
Switch
Switch
Switch
I am
Grandmaster
150

Switch
Router
Router
Switch
Switch
Switch
Router
System Powered ON
PTP Devices Listen Gather Announce Messages
Use BMCA to determine Grandmaster
151

Switch
Router
Router
Router
Switch
Switch
Switch
defaultDS.priority1 = 128 defaultDS.priority1 = 128
Domain 5
Domain 5
I am
Grandmaster
For Domain5
Domain 1
I am
Grandmaster
For Domain1
Domains
152
Domain 1

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
153
• 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)
Generic Switch
(Main)
Generic Switch
(Redundant)
ST 2022-7: Seamless (hitless) Protection Switching of SMPTE ST 2022 IP Datagrams

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
154
1 2 3
1 2 3
1 x2 x3
• 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)
Generic Switch
(Main)
Generic Switch
(Redundant)
ST 2022-7: Seamless (hitless) Protection Switching of SMPTE ST 2022 IP Datagrams

Overview of video switching methodologies
155

Overview of video switching methodologies
156
Non-clean video switching Clean video switching
Source-
timed
switching
Registers expected flow entry
in the IP switch. (Requires a
flow-control-capable SDN
switch.)
Controller changes the
destination addresses for the
stream in each source.
Updates the flow information of both source devices at exactly the same
time.
Pros: The IP switch does not need to sync over the network. No double
bandwidth penalty.
Cons: Complicated exception handling due to the requirement for
synchronous processing of two source devices with respect to one
destination device. Limited network topology since buffering is required in
the IP switch, if there is a delay between source and destination devices.
Switch-
timed
switching
Switching video updates the
flow table in the IP switch.
(Requires a flow-control-
capable SDN switch.)
The SDN controller switches the address of the stream to update the flow
table during the vertical blanking period.
Pros: No double bandwidth penalty
Cons: The IP switch is required to find the vertical blanking period. Limited
network topology since buffering is required in the IP switch, if there is a
delay between the source and destination devices.
Destination-
timed
switching
Switching video commanded,
generally using IP multicast,
from destination device to
conventional IP switch.
Temporarily receives a double stream at the destination device, finds the
vertical blanking period, and then switches inside the destination device.
Pros: No limitation for network topology. This can use COTS IP switches. Easy
exception handling since one destination device can handle everything.
Cons: Double bandwidth penalty.

157
Stream A
Stream E
Stream D
Stream C
Spare BW
Break-before-Make (static switching) Clean, Very fast & Visibly undetectable (One frame repeat)
Good for 95%+ of applications!
Make-before-Break (dynamic switching) ‘Clean’ (Switches on frame boundary)
Bandwidth burden for switch duration
Stream B
Stream E
Stream D
Stream E
Stream D
Stream A
Stream B
Stream C
Stream D
Stream A
Stream B
Stream C
Stream D
New
Break!
Stream A
Stream C
Make!
Stream A
Stream C
New
Break!
Stream A
Stream B
Stream C
Stream D
New
Tx
Rx
Tx
Rx
Tx
Rx
Tx
Rx
Tx
Rx
Tx
Rx
Preferred mode
set for each
Destination
Make!
Switch Mechanisms

IP port stream capacities
Option 1 : Usable with static switching or break-before-make (constant bandwidth) switching.
Option 2 : Usable with static switching or break-before-make (constant bandwidth) switching and with dynamic switching or true-
clean make-before-break, with a maximum of one destination changed at a time.
158

IP port stream capacities
Option 3: Channel capacity using no more than half the Ethernet bandwidth, leaving 50% spare bandwidth for clean
switching. Usable with static switching, or break-before- make (constant bandwidth) switching; or true-clean make-
before-break switching, with every destination able to be changed on the same frame.
159

Industry Challenges and Requirements
160
Unchanged Operator Workflow
Deterministic Low Latency and Jitter
Deterministic Quality of Service
Zero Packet Loss
Reservation of network resources across redundant paths for zero congestion loss
Video/ Audio End Point Sync and Lock with Micro-sec Accuracy
Precision Timing and Synchronization
Fast and Clean Switching
Switching streams with minimal delay and on frame boundary
System Availability
Same or better than SDI-based system
Network Security
Protect network operations from any malicious attacks
Traditional
SDI & AES Router

Live Studio Production with IP Technology
161
Video Switcher
Multiviewer
Monitoring
Systems
Graphic Systems
Remote Source
Video Server
Relay and Clips
Control System
Playout
Cameras and
Microphones
Audio Mixer

Live Studio Production with IP Technology
162
Video Switcher
Multiviewer
Monitoring
Systems
Graphic Systems
Remote Source
Video Server
Relay and Clips
Control System
Playout
Cameras and
Microphones
Audio Mixer
IP Network
REST, RESTCONF APIs
OF, Netconf/Yang, REST/JSON
(SDN)Network Controller
Standard and Open API
Network Interface

NMOS(Network Media Open Specification)/(AMVA) Advanced Media Workflow Association
• The broadcast controller is the overall policy control point for all media endpoints and sessions.
• The network controller abstracts the details of the network from the broadcast controller and provides an API for all required
network services.
• IS-06 NMOS Network Control API enables a broadcast controller to modify and view network.
163
AMWA IS-06 NMOS Network Control API Specification
Broadcast Controller
Network Controller
NetConf, OF and others
Network Control API
Broadcast Controller
Network Controller
Endpoint (Edge devices)
Switch (Network Device)
RDS
(Registration and
Discovery Server)
IS-05
(ConnectionManagement)
IS-05
Query API
IS-05
Registration API
IS-06
OpenFlow or proprietary protocol
LLDP
(Link Layer Discovery Protocol)

Classical broadcast studio infrastructure
MCR
CONTROL
CCONTTRRLOL
164

Smooth migration to IP studio infrastructure
CONTROL ROOM
STUDIO STUDIO
AV
STUDIO
STUDIO
MANAGEMENT AND ORCHESTRATION
165

166
Media Service Management and Orchestration

Orchestrator glues the entire operation together and set up the
workflows as you want
• Multiple possible connections
• Edge equipment control
• Bandwidth control
• Redundancy
• Security
• Enabling virtualization
Two Approaches
• Using a broadcast controller with orchestration capability
• Using individual broadcast controller and orchestrator
167
Media Service Management and Orchestration

Orchestration versus Control
168
ORCHESTRATOR
Monitors, Controls and Manages one or multiple Physical, Logical
and Virtual “Devices or Functions” in such a way that
the orchestrator is aware of the availability, capability, capacity,
utilization and connectivity of each resource at any given point in time
DETERMINISTIC:
guaranteed capacity and resource availability
TEMPORAL:
orchestrators book and guarantee capacity ahead of time
SPATIAL:
full stack management of applications
&underlying VNI and physical layers
there is no guarantee that the actions
can or will happen
controllers operate in real time within
assigned capacity constraints (live production)
controllers only operate on the application level
(usually tailored to technology vendor)
CONTROLLER
sends Commands to one or more physical or logical
devices to execute single or multiple actions using of
manual or automated processes
thoughtful decision-making
(non-live production)
fast execution for defined scenarios
(live production)

169
• SDI system: A broadcast controller had to talk to one or more SDI
router
• IP systems: A broadcast controllers need to interface with the
network switch and, in most cases, with all edge devices as well.
• SDN controller: The switch manufacturers offer their own SDN
controller.
So, A multi-vendor orchestrator is therefore a true necessity.
• Media flow is orchestrated in all imaginable manners, by
controlling sources, switch fabrics and endpoints directly, by using
multiple vendor-optimized SDN controllers, or a mixture of the two.
• Orchestrator glues the entire operation together and sets up the
workflows as you want (dynamic). Multi-vendor orchestration is
therefor a true necessity
Broadcast
Controller 1
Broadcast
Controller 2
PeripheralSystems
(Edgedevices)
SDN Controller
Orchestrator
Orchestration Layer
Orchestrator Layer

DataMiner: Media over IP Monitoring and SDN Orchestration
170

171
Arista 7500R SeriesArista 7500R Series
Tektronix SPG8000A
Sony HDC-3500/5500
XVX-9000
EVS-XT-via
Stagetec
CRESCENDO platinum
Denon, DN-900R
Postium OBM-X310
VIZRT CG
Grass valley MV-820- IP
Main
Redundant
Arista 7060CX2-32SArista 7060CX2-32S
Leaf switches with 1GE ports for audio devices
IP Spine Switches (2x 100GbE line cards,
72 QSFP28 ports per switch)

Grass valley GV Convergent Broadcast Controllers (Main & Redundant)
172
Tektronix SPG8000A
Sony HDC-3500/5500
XVX-9000
EVS-XT-via
Stagetec
CRESCENDO platinum
Denon, DN-900R
Postium OBM-X310
VIZRT CG
Main
Redundant

173
Tektronix SPG8000A
Sony HDC-3500/5500
XVX-9000
EVS-XT-via
Stagetec
CRESCENDO platinum
Denon, DN-900R
Postium OBM-X310
VIZRT CG
Main
Redundant

174
Tektronix SPG8000A
Sony HDC-3500/5500
XVX-9000
EVS-XT-via
Stagetec
CRESCENDO platinum
Denon, DN-900R
Postium OBM-X310
VIZRT CG
Main
Redundant
Skyline DataMiner Media over IP Monitoring and SDN Orchestration

175
$90,000
($29,000+$61,000)
$290,000
13 Cameras OB Truck using GV Convergent Broadcast Controller
Client Control
Network
Edge
Devices
Downstream Edge
Device Control
Main
Backup
Main & Redundant
Leaf Switches
Edge
Devices
Edge
Devices
Edge
Devices
Nexus 29160C
Nexus 9236C Nexus 9236C
Main and Redundant
Spine switches
GV Convergent
Controller 1
GV Convergent
Controller 2
GV Convergent
Clients
Control Panels
Upstream to Control Clients
Nexus 29160C

177
GVC-ALIAS Text alias interface license € 1,350.00
GVC-CONTROLLER-800 GV-CONVERGENT enterprise control system w/redundant
PSU and core software
€ 11,720.00
GVC-CTRL-GUI Graphical control user interface license € 1,350.00
GVC-CTRL-GUI-50 Graphical control user interface (50 panels) € 27,050.00
GVC-RTR-ETL-1024 Router control interface license to ETL (1024 dest) € 4,510.00
GVC-RTR-EVERTZ-1024 Router control interface license to EVERTZ (1024 dest) € 4,510.00
GVC-RTR-GV-1024 Router control interface license to TRINIX (1024 dest) Not Offered
GVC-RTR-IMAGINE-1024 Router control interface license to IMAGINE (1024 dest) € 4,510.00
GVC-RTR-NEVION-1024 Router control interface license to NEVION (1024 dest) € 4,510.00
GVC-RTR-PESA-1024 Router control interface license to PESA (1024 dest) € 4,510.00
GVC-RTR-QUINTECH-1024 Router control interface license to QUINTECH (1024 dest) € 4,510.00
GVC-RTR-SNELL-1024 Router control interface license to SNELL (1024 dest) € 4,510.00
GVC-RTR-SONY-1024 Router control interface license to SONY (1024 dest) € 4,510.00
GVC-RTR-UTAH-1024 Router control interface license to UTAH (1024 dest) € 4,510.00
GVC-SDN-0.5T Software defined networking license (0.5 T capacity) € 6,310.00
GVC-SDN-10T Software defined networking license (10T capacity) € 29,750.00

For-A IP/SDI Solution area SOM-100 (media orchestration platform)
178
USF-10IP series IP Gateway

179

180
SOM-100 (media orchestration platform )
• A software solution for centralized control
and monitoring
• An integrated baseband/IP control and
monitoring system
• SDI and IP routing switchers are managed
as one routing switcher in a virtual group.
• It offers seamless operation, with no need
to distinguish between baseband and IP
• Cloud-based operation, with an
architecture that easily adapts to products
• Web interface can be accessed from
multiple computers. Redundant server
configurations

Magellan™ SDN Orchestrator Dashboard
181
SDN Orchestrator Controller
Multi-vendor orchestration
is therefor a true necessity
Broadcast
Controller 1
Broadcast
Controller 2
PeripheralSystems
(Edgedevices)
SDN Controller
Orchestrator
Orchestration Layer

Magellan™ SDN Orchestrator Dashboard
182
SDN Orchestrator Controller
Multi-vendor orchestration
is therefor a true necessity
Broadcast
Controller 1
Broadcast
Controller 2
PeripheralSystems
(Edgedevices)
SDN Controller
Orchestrator
Orchestration Layer

Sony IP LSM (Live System Manager) workstation and Live Element
Orchestrator (PWS-110NM1)
A Variety of Software Licenses ($ 87000 for 5 yeras)*
• 1. PWSL-NM10 IP Live System Manager License: Basic license. Up to 128 I/O. Up to 20 simultaneous user access
• 2. PWSL-NM11 128 I/O Port License: Additional NMI 128 I/O
• 3. PWSL-NM12 Redundant System License: Necessary for redundant LSM configuration
• 4. PWSL-NM13 10 User License: Additional 10 simultaneous user access
• 5. PWSL-NM14 UHD License: Enables 4K/8K
• 6. PWSL-NM15 Audio Control License: Provides Audio over IP control
• 7. PWSL-NM16 Gateway License for Ember+:Enables controller’s with Ember+ protocol such as VSM to control LSM.
*All licenses are valid for 5 years. One-year extension licenses are available which can be installed any time the original licenses
are effective.
185

Grass valley GV Orbit controller
The GV Orbit Controller is supplied with all system software pre-installed. Optional functions are license enabled.
The system software consists of two main elements:
• Standard Router Controller, based on Grass Valley traditional SDI router control software, allowing control using existing PC clients
and/or hardware control panels.
• IP Router Adapter package that maps and interfaces all the IP Edge Devices to the Standard Router Controller. All the transmitted and
received signals (audio, video and data) to and from all ports on the IP Edge Devices are mapped to source and destination ports
named (in the normal way) in the controller.
• A third component, the IP Network Monitor, provides configuration (and mapping) of the IP Router Adapter.
Standard Router Control Clients
• The GV Orbit Controller can accommodate a virtually unlimited number of PC control clients and is fully compatible with Grass Valley’s
extensive range of control panels. These are configured in the normal way and connect to the GV Orbit Controller over Ethernet.
Third-Party Control
• The GV Orbit Controller exposes SW-P-02 and SW-P-08 router control protocols over Ethernet for control by third-party clients.
186

Grass valley GV Orbit controller
Standard Router Controller
• It is allowing control using existing PC
clients and/or hardware control panels
(based on traditional SDI router control
software).
IP Router Adapter
• It maps and interfaces all the IP Edge
Devices to the Standard Router
Controller. All the to /from all ports on
the IP Edge Devices are mapped to
source and destination ports named in
the controller.
IP Network Monitor
• It provides configuration and mapping
of the IP Router Adapter.
187

190
vsmSOUL: Seamless orchestration & unification layer

vsmSOUL: Seamless orchestration & unification layer
191

Lawo VSM (Virtual Studio Manager): IP broadcast control and monitoring system
192

Arena TV World’s First All-IP, 4K UHD OB Fleet
199

200

201
Benefits
• Makes IP network look like SDI – Easy to manage/operate
• Works within existing workflow – No operational disruptions
• Delivers scalability, efficiency of IP-based systems – Maximizes infrastructure investments
• Utilizes COTS IP switching – Leverages latest generation of IP routers
• Manages new IP and legacy SDI devices – Protects existing investment while transitioning
• Provides an easy, viable transition path – Enables a phased approach to an all-IP future
Features
• Supports IP/SDI hybrid networks
• Features a mix of physical and virtual processing functions
• Provides control framework for hybrid SDI/ASI/IP facilities
• Utilizes current routing protocols and control panels
• Controls and monitors the virtual plant, providing operational visibility
• Presents a unified control environment for operations
• Offers compatibility with automation, tally, multiviewer, other devices in the facility
• Manages IP switching and connectivity
• Supports switching of compressed and uncompressed signals per SMPTE 2022 standards
• Delivers high availability through 1+1 redundant configuration
• Enables clean switching of uncompressed IP sources
• Facilitates seamless redundancy switching in main and backup network configuration (SMPTE 2022-7)

TV Globo 4K OB Truck ,Brazil
202

Hybrid Concept: 4K Production over IP & HD Monitoring with SDI
203

Full IP Redundancy
・Controller, IP Switch & Cables, 2x XVS-8000 for 2x Productions or Main/Backup
4K Matrix Size: 69x67 (3G-SDI: 276x268)
- 3RU, 87 optical cables (double in redundant system)
204

205

206

Audio Issues
• ST2110-30 and AES67 are almost compatible but there are
differences.
• There are a lot of different profiles and details that hinder
interoperability (16 channel C 125μs, 1-8 channel A 1ms)
• Video vendors are adopting NMOS control but Radio
vendors already have LiveWire, Dante & EMBER+
• Our media network is dual presented via 2022-7 but a lot of
audio kit uses a different resilience model
• We also have to deal with Dante for much of our post
production audio.
• Dante needs a different PTP profile
• MADI may offer a natural bridge but GV’s approach to using
MADI has a number of control constraints
• We need to consider latency between systems
207

IP motivations Alternative for 3G-SDI in 4K
209
12G-SDI, 24G-SDI!!!

SMPTE ST 2110 suite, Business benefits and Real world rollout
210
3. Source: IP in action. Updated for IBC2018.
SAMPLING OF GLOBAL ST 2110
DEPLOYMENTS

SMPTE ST 2110 suite, Business benefits and Real world rollout
211
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

IP motivations, Remote Production
212

IP motivations, Live production environment
213

214
HYBRID AUDIO
ROUTING/ MANIPULATION
VERTICAL ACCURACY SMPTE 2110
LOW LATENCY
(< 2.4 LINES)
SMPTE 2022-7
(FUTURE RELEASE)
BROADCAST-
CENTRIC
IP
MADI
IP
SDI
FLEXIBLE
DOWNSTREAM
I/O
STANDARDS-
BASED
Process IP Data Center Broadcast Data Center
Agility of Service Deployment ✔ ✔
Scalability (ease of upgrading) ✔ ✔
Non-Blocking ✔ ✔
Graceful Fault Tolerance ✔ ✔
Ease of Upgrade ✔ ✔
High Bandwidth (uncompressed video) ✔ ✔
Format Agnostic ✔ ✔
Vertically Accurate Video-over-IP Switching
(edge- or destination-based)
✘ ✔
Native SDI Connections Supported ✘ ✔
Low Latency (less than 1 video frame) ▲ ✔
Computational Intensity for Encoding (i.e., HEVC) ▲ ✔
Programmable FPGA Blades ✘ ✔
IP Data Center vs Broadcast Data Center

Conclusion
Is IP better than 12G-SDI or not? (Simple 3G-SDI to 12G-SDI upgrade!)
• IP for HD or UHD (?)
• The manufacturing of 12G-SDI and IP Equipment (?)
• Expandability, Flexibility, Format Agnostic, Agility …(?) (Short Term)
• Router size (?) (Studio, OB Truck, Production/Master Control Room)
• Remote Production, Studio Production, Production/Master Control Room (?)
• MMF or SMF Consideration (?) (New Building!)
• Hybrid or full-IP (?) (Gateways and other extra facilities)
• $ Infrastructure (?), $ Audio & Video Equipment (?)
• IP leverages cutting-edge technology
• The future seems to be headed toward IP based system
• IP-based System Problems (Cost!, Staff!, Multi Vendors!, Standards Maturity!, Complexity, Security, Reliability …)
• Orchestration and monitoring software's issues
• Broadcast controller licenses issues
• ………. 215
SMPTE-2110
Pilot Project

Questions??
Discussion!!
Suggestions!!
216

Designing an 4K/UHD1 HDR OB Truck as 12G-SDI or IP-based

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Designing an 4K/UHD1 HDR OB Truck as 12G-SDI or IP-based

Similar to Designing an 4K/UHD1 HDR OB Truck as 12G-SDI or IP-based (20)

More from Dr. Mohieddin Moradi

More from Dr. Mohieddin Moradi (13)

Recently uploaded

Recently uploaded (20)

Designing an 4K/UHD1 HDR OB Truck as 12G-SDI or IP-based