Next&Genera-on&Networks& for Broadcast&Applica-ons& · MPLS Layer 3 IP-VPN MESH NETWORK Satellite Overlay & Backup Example&Hybrid&System&Architecture& PUBLIC INTERNET& Primary& NOC&

Crowe & Cli*on: Next Gen Broadcast Networks Page: 1

Next Genera-on Networks for

Broadcast Applica-ons


Objec-ve and Outline •  Objec-ve: provide an overview of next genera;on networks

being considered by PBS and others for professional broadcast applica;ons

•  Outline: –  The context –  Why MPLS IP-‐VPN technology ? –  Understanding Class of Service (COS/QOS) –  Applica;ons –  Lessons learned


The Context The viewing habits, technologies, plaCorms, demographics and business models are changing rapidly and the broadcast industry is moving to IP distribu-on and workflows

Falling costs are making terrestrial broadband IP connec-vity (such as MPLS) a viable alterna;ve to legacy satellite broadcast networks.


Produc-on Programming & Traffic

Automa-on Near-‐Line & Archive

Playout & Encode

Example Legacy Broadcast Network

Live events •  Linear broadcast from files and/or live events

•  Non-‐linear (files) for local playout

PUSH

Non-‐linear content (files)

Broadcast-‐quality content distribu-on/contribu-on for local sta-on free to air, cable and DTH satellite TV (i.e. not OTT delivery)

STATIONS

LOCAL CABLE Cable & Other

BROADCAST STATIONS

Point to mul-point (P2MP) Broadcast/Push

Free to Air (FTA/ATSC)


Tradi-onal Satellite OPEX Advantage for Broadcast

P2MP= Point to mul-point


The broadcast distribu-on bandwidth chain

SDI

Distribu-on Networks

Compression and Encoding

Decompression & Decoding

Produc-on

Playout & (re)Broadcast SDI

Uncompressed (Raw) video: •  Serial Digital Interface (SDI) standard -‐ typical live/linear bandwidths:

•  HD: 1.5 Gbps •  SD: 270 Mbps •  4K: 6 Gbps

•  Typical file sizes: 150-‐250 GB

•  MPEG 4 AVC and MPEG 2 for Linear/Live broadcast -‐typical live/linear bandwidths:

•  HD: 15 Mbps •  SD: 4 Mbps •  4K : 25-‐30 Mbps (HEVC)

•  Typical distribu;on profile file sizes: •  HD: 7-‐15 GB •  4K: TBD

Compressed video for distribu-on: Broadcast video: •  Local traffic management, automa;on & playout

•  Add-‐in local linear/live & non-‐linear content

•  SDI/Tape -‐> file based workflows

•  SD-‐>HD-‐>4KUHDTV •  MPEG 2 & 4 legacy playout •  & Mul;ple OTT formats


The broadcast distribu-on bandwidth chain

SDI

Distribu-on Networks

Compression and Encoding

Decompression & Decoding

Produc-on

Playout & (re)Broadcast SDI

Uncompressed (Raw) video: •  Serial Digital Interface (SDI) standard -‐ typical live/linear bandwidths:

•  HD: 1.5 Gbps •  SD: 270 Mbps •  4K: 6 Gbps

•  Typical file sizes: 150-‐250 GB

•  MPEG 4 AVC and MPEG 2 for Linear/Live broadcast -‐typical live/linear bandwidths:

•  HD: 15 Mbps •  SD: 4 Mbps •  4K : 25-‐30 Mbps (HEVC)

•  Typical distribu;on profile file sizes: •  HD: 7-‐15 GB •  4K: TBD

Compressed video for distribu-on: Broadcast video: •  Local traffic management, automa;on & playout

•  Add-‐in local linear/live & non-‐linear content

•  SDI/Tape -‐> file based workflows

•  SD-‐>HD-‐>4KUHDTV •  MPEG 2 & 4 legacy playout •  & Mul;ple OTT formats

1.5 Gbps 15 Mbps

1.5 Gbps

1 Mbps

5 Mbps

15 Mbps

7-‐15 GB 150 GB


One Approach: Internet Aggrega-on

SDI and/or IP Video

SDI and/or IP Video

SDI and/or IP Video PROVIDER APPLIANCE

Example service providers: LTN Global, VideoShip In use for broadcast today (e.g. NBC,CNN,FOX, PBS & others)

PUBLIC INTERNET


One Approach: Internet Aggrega-on

Output buffer at egress “smooths out” jiher & latency varia-ons (200-‐600 msecs typical latency)

In-‐network jiher and delay

Original input at ingress (e.g. linear video)

1 2 3 4 5 6 7 1 2 3 4 5 6 7

1 2 3 4 5 6 7

•  Latency excessive for most broadcast distribu-on applica-ons •  Unmanaged core network with NO COS/QOS traffic engineering •  Expensive for P2MP distribu-on & NOT IP mul-cast enabled


Mul--‐Protocol Label Switching

PE= Provider Edge CE=Customer Edge

Inherently fast, robust and secure (i.e. NOT the public Internet)


MPLS IP-‐VPN •  Mul- Protocol Label Switching (MPLS): –  Next-‐gen Wide Area Network (WAN) technology replacing legacy Layer 2 ATM & Frame Relay networks

•  IP-‐VPN: –  Internet Protocol (e.g. Layer 3 router-‐to-‐router) –  Virtual Private Networks on shared but dedicated/managed fiber infrastructure


Why MPLS IP-‐VPN? •  State-‐of-‐the-‐art for enterprise-‐class

WAN today with mul-ple topologies (e.g. mesh) available

•  100 Mbps & DS3 (45 Mbps) are common and most popular –  1 Gbps and 10 Gbps also readily available

•  Becoming increasingly affordable & very compe--ve

Mul-ple Tier 1 Vendors:

…+ others WAN= Wide Area Networks


Why MPLS IP-‐VPN (Layer 3)? •  Transparent private virtual networks using IP

•  IP mul-cast enabled for bandwidth efficiency •  Automa;c redundancy/DR in the core network

•  Class of Service (COS) provides ability to priori-ze traffic (e.g. linear video over non-‐linear file delivery). Typical performance: •  Low latency: e.g. 25-‐ 50 msecs RTT •  Low jifer: e.g. 2 -‐ 5 msecs •  Low Bit Error Rate (BER): “Near zero”

•  Variety of network topologies available including full-‐duplex (i.e. two-‐way) mesh interconnec-on

•  Alterna-ves (e.g. Layer 2 VPLS) over MPLS also available


Example Tier 1 Product Offerings Routing Transparency Protection CoS Network Billing Technology

Customer ControlledFull Layer 2 Transparency

Optional on local access.

Customer Controlled

Dedicated FlatEthernet over

DWDM

Customer ControlledFull Layer 2 Transparency

Fast Reroute in the core

All Traffic classified as Premium Data

Shared FlatEthernet over MPLS Core

Multipoint MAC switching Ethernet

VPN service

Tagged or Transparent options

Fast Reroute in the core

4 Classes of Service Shared FlatEthernet over MPLS core

IPv4, IPv6 Layer 3 ServiceFast Reroute in

the core

6 Classes of service with 10 Priority

Options.Shared Flat IP over MPLS

IPv4, IPv6 Layer 3 ServiceFast Reroute in

the core4 Classes of Service

Public Internet

Tiered and Burstable

IP over MPLS core

Source: Verizon 2014Source: Verizon


Example Tier 1 Product Offerings

Source: Level 3


Example MPLS IP-‐VPN Broadcast Network Approach

MPLS Network

Sta-on

((( )))

CE

PE= Provider Edge CE=Customer Edge

CE

CE

CE

CE

CE


Example “Generic” M&E Applica-on

Linear

Non-‐Linear

M&C

Content

Linear

Non-‐Linear

Content

M&C

M&C=Monitoring & Control


Understanding COS/QOS

•  Class of Service (COS) is a Traffic Engineering (TE) technique used to priori-ze traffic on a network •  used to implement Quality of Service (QOS) rules to

differen;ate and shape/police network traffic •  gives priority to higher value traffic in ;mes of network

conges;on (e.g. linear/live video over best effort file delivery)

•  MPLS-‐TE = Traffic engineering inside the MPLS core network


Understanding COS/QOS

For modern Layer 3 IP networks, Differen-ated Services (DiffServ) QOS (e.g. DSCP-‐x) replaces legacy IPv4 Type of Service (TOS)


Example “Generic” M&E Applica-on

COS is checked at ingress to the MPLS network and delivered over MPLS by priority assigned limits/queues (i.e. MPTS-‐TE)

VLAN-‐type COS is set by applica-on and priority

For example:

HI -‐-‐-‐-‐-‐-‐-‐ LOW -‐-‐-‐

MED -‐-‐-‐

Policing to bandwidth limits (e.g. 100 Mbps) and output priority by COS is done at the egress from the MPLS network

-‐-‐-‐-‐-‐ HI -‐-‐-‐-‐-‐ LOW

-‐-‐-‐-‐-‐ MED


Fully Duplex & Symmetric – Both ways

COS is checked at ingress to the MPLS network and delivered over MPLS by priority assigned limits/queues (i.e. MPLS-‐TE)

Policing to bandwidth limits (e.g. 100 Mbps) and output priority by COS is done at the egress from the MPLS network

HI -‐-‐-‐-‐-‐-‐-‐ LOW -‐-‐-‐

MED -‐-‐-‐

VLAN-‐type COS is set by applica-on and priority

For example:

-‐-‐-‐-‐-‐ HI -‐-‐-‐-‐-‐ LOW

-‐-‐-‐-‐-‐ MED




Playout & Encode

Example MPLS Broadcast Configura-on

Live events TSoIP

Man

aged

VLA

N Switch

Mul-cast Source *

Linear

TSoIP = Transport Stream over IP Non-‐linear

File Transfer (unicast

&mul-cast)

Monitoring & Control

M&C




Playout & Encode

Example MPLS Broadcast Configura-on

Live events TSoIP

Man

aged

VLA

N Switch

Mul-cast Source *

Linear

Non-‐linear

File Transfer (unicast

&mul-cast)

Monitoring & Control

M&C MED -‐>

HI -‐>

LO -‐>

Example Traffic priori-za-on using COS for a typical broadcast

applica-on

TSoIP = Transport Stream over IP


“IP” IRDs “IP” IRDs

Example “Sta-on-‐side” Configura-on

IRD = Integrated Receiver Decoder

“IP” IRDs

VLAN Switch

File Share

Cache

M&C

((( )))

Produc-on Programming

Traffic, Automa-on,

Master Control & Playout

HD-‐SDI STATION

FTP

Mul-cast video


“IP” IRDs “IP” IRDs

Example “Sta-on-‐side” Configura-on

IRD = Integrated Receiver Decoder

“IP” IRDs

VLAN Switch

File Share

Cache

M&C

((( )))

Produc-on Programming

Traffic, Automa-on,

Master Control & Playout

HD-‐SDI STATION

FTP

MED

HI

LO

COS: EXAMPLES ONLY

Mul-cast video


Example: using COS to Manage QOS

BEST EFFORT (COS=LOW)

•  5 GB @ 50 Mbps = 13.3 mins

•  5 GB @ 100 Mbps = 6.7 mins

•  5 GB @ 200 Mbps = 3.3 mins

BEST EFFORT

IP MULTICAST (COS=HI)

•  HD: 15 Mbps •  SD: 4 Mbps

IP MULTICAST

This IRD does mul-cast join


Example – Full Duplex Mesh Linear

IP MULTICAST (COS=HI)

•  HD: 15 Mbps •  SD: 4 Mbps

IP MULTICAST


COS/QOS = Auto Management of Priori-es

Time of Day

Band

width (M

bps)


Adding Diversity & Scaling Up

Secondary (Diversity, DR/BC & load

Balancing)

Primary


Other Features of MPLS IP-‐VPN

Direct internet Access (DIA)

Public Internet

Private & Hybrid Cloud Service Providers

(IaaS, PaaS, SaaS)


Hybrid Cloud??????


STATIONS LOCAL CABLE

GigE/10GigE 100 Mbps

POTENTIAL CLOUD SERVICES (PRIVATE and/or

HYBRID)

MPLS Layer 3 IP-VPN MESH

NETWORK

Satellite Overlay & Backup

Example Hybrid System Architecture

PUBLIC INTERNET

Primary NOC

Secondary NOC

Other


Some Lessons from Proof of Concept Work •  Ini-al IP connec-vity and ac-va-on of MPLS is easy but not quick

•  Industry norm = typical 60-‐90 days from order •  Service Level Agreements (SLAs) are typically Telco standard

•  Overall performance once a circuit is installed and accepted is great •  MPLS = inherently low jifer, low latency, very low BER + mesh full duplex! •  IP Mul;cast works and is a great bandwidth saver (use what you take)

•  However: •  IT language ≠ Broadcast Language (e.g. FEC ≠ FEC) •  Test equipment and processes needed to confirm performance must use broadcast

industry standards and metrics (e.g. Media Delivery Index/MDI) •  COS boundaries usually work alone (WOOB) but “fine tuning of network

configs” (especially tail circuits) is needed when boundaries are stressed •  System architecture has to account for some specific issues (e.g. “backhoe fade”)

Not vendor

specific


Example Future-Proofing via SOA

CyberSecurity Infrastructure ( “bed of nails”)

DAM MyPBS & Other PBS Services

CyberSecurity Service

NOC Playout & SOC

AS03 File Delivery Service

File Transfer Service

MOC

PBS Enterprise Service Bus (ESB)

PBS Digital

Service Oriented Architecture (SOA)

v6 Master Scheduling Service

v6 Network M&C Service

v6 System User Interface

Service

v6 Content Storage Service

Currently in Proof of Concept Tes-ng

STATIONS'LOCAL'CABLE'

GigE/10GigE 100 Mbps

POTENTIAL'CLOUD'SERVICES'(PRIVATE'and/or'

HYBRID)'

MPLS Layer 3 IP-VPN MESH

NETWORK

Satellite Overlay & Backup

PUBLIC'INTERNET'

Primary'NOC'

Secondary'NOC'

Other'


Ques-ons? Thank you for your -me!

Thomas A. Crowe III: PBS Vice President of Interconnec;on System Engineering [email protected], 703-‐739-‐5491

Ron W. Clivon: PBS v6 Solu;on Architect, Cli*onGroup Interna;onal Limited rcli*on@cli*ongroup.ca, 613-‐852-‐8833

Documents

Next&Genera-on&Networks& for Broadcast&Applica-ons& · MPLS Layer 3 IP-VPN MESH NETWORK Satellite Overlay & Backup Example&Hybrid&System&Architecture& PUBLIC INTERNET& Primary& NOC&