Over-the-Top Video Delivery using HTTP Adaptive

(1)

Over-the-Top Video Delivery

p

y

using HTTP Adaptive

Bit R t St

i

Bit Rate Streaming

CCSA – Mont Tremblant – QC – September 22 2013

CCBE

Horseshoe Resort ON

September 26 2013

CCBE – Horseshoe Resort - ON – September 26 2013

Louis Sebastiani, IPTV Project Director

(2)

Our Know-How

Our Markets

MPEG 2/4 C

i

d t

t

i

t

• MPEG-2/4 Compression and test equipment

• DTV headend (live), VOD, EPG (guide), PVR

• DTV, IPTV and OTT delivery

IPTV

Satellite

,

y

•

PSIP / PSI-SI (Metadata and Guide)

Digital TV headend design

Fiber Transport

• Digital TV headend design

• RF distribution (QPSK, QAM, 8VSB)

• Carrier Ethernet / DWDM solutions

p

Cable TV and

RF distribution

• RF Test and Measurement

• CATV Network Powering

• Wireless Point-to-Point and Multipoint

RF distribution

TV and FM

Broadcast

p

• HFC and PON distribution design

• Network Management

• L Band Signal Management and transport

(3)

Agenda

1.

Video delivery on managed and unmanaged networks

a)

Differences between Broadcast TV, Cable TV, IPTV and Over the Top

delivery (OTT) using the Internet

b)

Difference between MPEG2-Transport Stream delivery and HTTP

streaming

2

Li

D

(IPTV

d M lti

Vid

D li

)

2.

Live Demo (IPTV and Multiscreen Video Delivery)

3.

Adaptive Bit Rate streaming technology overview

4

Comparing HTTP streaming technologies

4.

5.

Multiscreen video delivery from the Cable/Telco operator’s perspective

6

Overview of the multiscreen video delivery ecosystem (from content to

6.

consumer devices)

(4)

1. Video Delivery on Managed and Unmanaged Networks

Broadcast TV / Cable TV / IPTV / Satellite

Internet

(5)

MPEG-2-TS on Managed Network

IP Video Streaming (unmanaged)

0110011010110101001101…

MPEG-2 TS

video video audio

ASI IP

(or)

QAM

(Cable)

QPSK/8PSK

(S t llit )

DSL

(Telco)

GPON/EPON

TCP/IP

8VSB

(Broadcast)

(Satellite)

GPON/EPON

(FTTH)

“Direct” Connection from

“Packet-Switched”

Headend to Customer

Best Effort Network

(6)

ff

Difference between Managed and Unmanaged Networks

•

Managed Network (ATSC, HFC, DSL, FTTH, Satellite)

– Bandwidth is controlled and constant

Bandwidth is controlled and constant

– Jitter is controlled

– Network Engineering allows stable conditions (QoS is assured)

– MPEG-TS is the preferred mechanism to deliver video (QAM IPTV

video video

audio

MPEG-TS is the preferred mechanism to deliver video (QAM, IPTV,

Satellite).

– Because MPEG-TS requires stable network conditions and no packet loss:

need Managed Network

•

Unmanaged Network (Internet)

– Bandwidth varies / Conditions are not stable

Q

li

f S

i

d (“B

Eff

”)

– Quality of Service is not guaranteed (“Best Effort”)

– MPEG-TS is not a good solution…

– So, need to use IP video streaming techniques… to deliver video

over-the-top (OTT)

(7)

What is OTT Video Streaming?

For the purpose of this presentation:

p p

p

- A toolkit of different

technologies

- Making Use of the

Public Internet

and its

S

d d

P

l

Standard

Protocols

- To deliver

multimedia

content

Either

Live

or

On

On Demand

Demand

(8)

Agenda

1.

Video delivery on managed and unmanaged networks

a)

Differences between Cable TV, IPTV and Over the Top delivery (OTT)

using the Internet

b)

streaming

2

Li

D

(IPTV

d M lti

Vid

D li

)

2.

3.

4

Comparing HTTP streaming technologies

4.

5.

Multiscreen video delivery from the Cable/Telco operator’s perspective

6

6.

consumer devices)

(9)

(10)

Agenda

1.

a)

using the Internet

b)

streaming

2

Li

D

(IPTV

d M lti

Vid

D li

)

2.

3.

4

4.

5.

6

6.

Overview of the multiscreen video delivery ecosystem (from content to

consumer devices)

(11)

3. Adaptive Bit Rate streaming technology overview

IP Stack – Standard Protocols “Key Words”

Application Laye r

SNMP

TELNET

FTP

DHCP

DNS

Clients/

TCP

(acknowledgement)

UDP

(no acknowledgement)

RTMP/

RTSP

a nsp o rt L aye r

RTP

Servers

HTTP

( g ) ( g )

IP

Tr a L Internet Laye r

IGMP

4 layer model (Internet Protocol Suite) From Wikipedia:

Ethernet (Media Access Control)

Link _Laye

r

“MAC address”

4 layer model (Internet Protocol Suite) From Wikipedia:

(12)

An example with MPEG-TS

Application

Laye

r

Clients/

TELNET

FTP

DHCP

DNS

SNMP

TCP

(acknowledgement)

UDP

RTMP/

RTSP

a nsp o rt L aye r

RTP

Servers

HTTP

( g ) ( g )

IP

Tr a L Internet Laye r

IGMP

Ethernet (Media Access Control)

Link _Laye

(13)

Vid

St

i

P t

l

Video Streaming Protocols

•

All streaming protocols are in the

application layer

A

pplication Laye

r

app ca o

aye

•

Clients and servers exchange

messages in a request-response

messaging pattern

Clients/

TELNET

FTP

DHCP

DNS

SNMP

TCP

(acknowledgement)

UDP

A n sp o rt a yer

RTP

HTTP

•

Streaming Protocols use the layers

below to transport content

C e ts/

Servers

RTMP/

RTSP

TCP

(acknowledgement)

UDP

IP

Tra n L a Internet Laye r

IGMP

HTTP RTSP/ RTMP TCP UDP IP

Ethernet (Media Access Control)

Link _Laye

r

Video streaming over the Internet

MAC

(14)

3. Adaptive Bit Rate streaming technology overview

Video Streaming Protocols Evolution

1. Progressive Download using HTTP

•

(eg Youtube)

(eg. Youtube)

2. RTSP/RTMP Streaming

•

RTMP (Flash Players)

(

y

)

•

RTSP (QuickTime, Android)

3. Adaptive HTTP Streaming

•

Microsoft Smooth Streaming,

•

Apple HLS,

(15)

Video Streaming Protocols Evolution

Hypertext Transfer Protocol

(

HTTP

) is the foundation of

data communication for the

W ld Wid W b

RTSP means

Real Time

Streaming Protocol

RTMP means

Real Time

M

i

P

t

l

1

HTTP

p lication L aye r

World Wide Web.

Messaging Protocol

2

RTSP/

RTMP

3

HTTP

TELNET

FTP

DHCP

DNS

SNMP

Ap p L or t r

RTP

HTTP

RTSP/

RTMP

1. Progressive Download uses

HTTP (eg. Youtube)

3

HTTP

Clients/

Servers

TCP

(acknowledgement)

UDP

IP

Transp Laye te rnet L aye r

IGMP

(eg

outube)

2. RTSP/RTMP Streaming

RTMP (Flash Players) RTSP

(QuickTime, Android)

Ethernet (Media Access Control)

In

t _L

Link _Laye

r

3. Adaptive HTTP Streaming

(Microsoft Smooth Streaming,

Apple HLS, Flash HDS)

(16)

Progressive Download principles

Progressive Download is supported by: • Flash,

• HTML5 browsers, • the iPad/iPhone and • the iPad/iPhone and On the server side:

• every regular webhoster supports downloads, • as does every Content Delivery Network (CDN)

Features and Characteristics

Youtube uses Progressive Download

Downsides Conclusion

• Simplest to implement

• HTTP protocol (using TCP/IP) • When hit “Play” – the media player

starts downloading the file until the whole file is received.

Pl b k h d t i

• A lot of bandwidth is wasted for data downloaded but unwatched

• Inhability to change the video quality at mid-stream

– Full screen looks bad (even if would have the bandwith for a higher

• Good solution for short clips and

when no live streaming • Simple to implement • Alternate solutions…

– RTMP/RTSP streaming • Playback as soon as enough data in

buffer

• Trick play (seeking in the video) if system is provisioned for pseudo-streaming

have the bandwith for a higher resolution); or

– Playback stutters upon network congestion

• Not possible to do live streaming

– Adaptive HTTP streaming

(17)

RTMP/RTSP Streaming principles

RTMP (Real Time Messaging Protocol) is what Flash uses RTSP was developed by the Multiparty Multimedia

Session Control Working Group (MMUSIC WG) and published as RFC2326 in 1998

RTMP (Flash) is the most widely used streaming protocol Almost all PCs have flash players

* Not supported by iPhones / iPads

Features and Characteristics

• RTMP/RTSP are “Stateful” protocol (vs HTTP which is a “Stateless” protocol)

Hulu uses RTMP Streaming

Downsides

• RTP(UDP) has no retransmit capability so packet loss will result in issues

Conclusion

• RTMP distribution is still widely and beneficially used by many HTTP which is a Stateless protocol)

• Requires a dedicated Streaming Server.

• The media player initiates a communication with a Streaming Servers

packet loss will result in issues

• RTMP/RTSP packets may be blocked by certain firewalls (because of ports 1935/554)

• RTMP packets can’t leverage standard HTTP caching mechanisms

• The required server may also limit scalability as

and beneficially used by many websites today.

• However, at this point if you’re considering implementing a streaming technology, the overwhelming sentiment is to • Uses RTP/UDP streaming with a

remote control protocol (TCP/IP to maintain end-to-end connection)

• RTMP uses port 1935; RTSP uses port 554

The required server may also limit scalability as compared to HTTP-based streaming, since there are many more HTTP servers than RTMP.

deliver via HTTP.

• For adaptive delivery to Apple devices (and Android 3.0 and higher ?), HLS is your only

option.

Info from http://www.longtailvideo.com/blog/19578/what-is-video-streamingand

(18)

Adaptive HTTP Streaming principles

Video is encoded in several resolutions to adapt for network conditions (different “Profiles”)

Cients play the video stream by requesting segments in a profile from a Web Server (via HTTP)

Profile A Profile B

Profile C

Adaptivedelivery enables a client to “adapt” to fluctuating network conditions by selecting video segments from different profiles (Intelligence in client) Objective: join the merits of RTMP/RTSP Streaming (bandwidth efficiency, quality switching) with those of

Profile C

Features and Characteristics

• Creation of fragments of encoded video (2 seconds or 10 seconds chunks)

Progressive Download (no special servers or protocol needed – simple HTTP). CDN Friendly.

Downsides

• Requires more overhead because of TCP which requires acknowledgement (vs (2 seconds or 10 seconds chunks)

hosted on regular HTTP server • HTTP is firewall friendly… (vs RTMP) • Support for different resolutions – i.e.

each fragment can be encoded in different quality levels

which requires acknowledgement (vs RTP/UDP transport)

• A lot of small files to manage (chunks) • No Single and Widely used implementation • Currently, some of the options are:

• Apple HLS q y

• IDR Frame alignement and equal duration of fragments to switch between resolutions during playback

• H.264 video Codec and AAC audio

– Note: see upcoming slide for di i W bM d VP8

• Apple HLS

• Microsoft Smooth Streaming • Adobe HDS

• Lack of standardization, except effort from: • MPEG-DASH (MPEG consortium)

The list of available profiles is called a manifest file or playlist. This is used by the client to know what to expect and download discussion on WebM and VP8

(19)

Client dynamically

3. Adaptive Bit Rate streaming technology overview

Adaptive HTTP

Streaming

H.264 Multi Bit Rate

Client dynamically selects best size chunk according to network conditions

* For HDS, a Flash Media Server is required; For MSS, a IIS-7 Server is required

Lower Bit Rate --- Higher Bit Rate

H.264

E

ncoder

Transport Streams

c

kaging /

g

menting

HTTP

S

erver*

High

Managed

Network

or

Lower Bit Rate Higher Bit Rate

E

Pa

c

Se

g

S

High Quality Video

Creation of several bit t / l ti f

+ Playlist/Manifest File

Creation of small chunks (2 or 10

Delivery to CDN Adaptive Streaming Client rates/resolutions for

delivery to different devices (STB, PC,Tablets, Phones, etc.)

(

seconds) for each resolution and

streaming format (HLS, HDS, MSS) The video files are published over the Network like any other HTTP file for delivery on the Internet High Bit Rate Network Congestion Low Bit g

(20)

Agenda

1.

a)

using the Internet

b)

streaming

2

Li

D

(IPTV

d M lti

Vid

D li

)

2.

3.

4

4.

5.

6

6.

Overview of the multiscreen video delivery ecosystem (from content to

consumer devices)

(21)

4. Comparing HTTP Streaming Technologies

HLS: HTTP Live Streaming (Apple) 2009

MSS: Smooth Streaming (Microsoft) 2009

HDS: HTTP Dynamic Streaming (Flash) 2010

• ISO Standard in order to provide a

Universal Delivery Format

HDS: HTTP Dynamic Streaming (Flash) 2010

Features Apple HLS Microsoft Smooth

Streaming Adobe HDS mpeg-DASH

Codec Used H.264 H.264 VC-1 H.264 VP-6 H.264(or other MPEG

f )

Codec Used H.264 H.264, VC 1 H.264, VP 6

codec family)

Open Standard No No No Yes

Subtitle Support Partial Yes Partial Yes

Multiple Audio Support V4 only Yes Yes Yes

Trick Mode Support Partial Yes Partial Yes

CDN-Friendly Requires Chunk

Carriage Optimization

Requries specific IIS-7 origin server

Requires specific Flash

Media Server(origin) Yes

Common Encryption No No No Yes

(22)

What about WebM and VP8?

•

WebM

is an media file format designed for the web

– Open and royalty-free

•

A WebM file (.webm) consists of :

– VP8 video codec (vs H.264 video codec)

– Vorbis audio codec (vs AAC audio vs)

I

t i

b

d

M t

k (

k )

– In a container based on Matroska (.mkv)

•

Embed video directly in HTML5 web page with simple tag

•

No need for plug-in in web page

Th

j

t' d

l

t i

d b G

l

•

The project's development is sponsored by Google

•

Type of Format: Media Container

•

Internet Media Type (MIME Type)

video/webm

– video/webm

– audio/webm

•

Native WebM support by Mozilla Firefox, Opera and Google Chrome

browsers

(23)

The State of HTML5 support

Information from:

http://www.longtailvideo.com/html5/

Last updated April 10, 2013

(24)

S

St

i

S

t

Summary: Streaming Support

This table sums up support for the various streaming methods across devices and servers.

Posted by

Jeroen Wijering

on April 27, 2011

Devices Progressive Download (only on demand)

RTMP/RTSP Streaming (live and on demand)

Adaptive HTTP Streaming (live and on demand)

Adobe Flash Player MP4, FLV RTMP HLS, HDS, Smooth

HTML5 (Safari & IE9) MP4 -

-HTML5 (Firefox & Chrome) WebM -

-iOS (iPad/iPhone) MP4 - HLS

Android Devices MP4, WebM RTSP HLS (as of 3.0)

CDNs (e.g. CloudFront) MP4, FLV, WebM RTMP HLS

Web Servers (e g S3) MP4 FLV WebM HLS

(25)

Agenda

1.

a)

using the Internet

b)

streaming

2

Li

D

(IPTV

d M lti

Vid

D li

)

2.

3.

4

4.

5.

Multiscreen video delivery from the Cable/Telco operator’s

perspective

6.

consumer devices)

7

Li e Demo

ith MPEG and OTT Test Eq ipment

(26)

5. Multiscreen Video Delivery from the Cable/Telco

Operator’s perspective

Broadcast TV / Cable TV / IPTV / Satellite

Internet

(27)

5. Multiscreen Video Delivery from the Cable/Telco

Operator’s perspective

The Threat…

• Content Providers, Consumer Electronics Manufacturers and new Aggregators can offer TV

services directly to consumers OTT

*HEVC should provide 40-50%

reduction in bitrate vs H.264

(28)

Agenda

1.

a)

using the Internet

b)

streaming

2

Li

D

(IPTV

d M lti

Vid

D li

)

2.

3.

4

4.

5.

Multiscreen video delivery from the Cable/Telco operator’s perspective

6

Overview of the multiscreen video delivery ecosystem (from

6.

Overview of the multiscreen video delivery ecosystem (from

content to consumer devices)

(29)

6. Overview of the multiscreen video delivery ecosystem

video video audio

Managed

Network

Internet

Un-Managed

g

Network

(30)

TV Everywhere challenges…

•

Authentication

•

Authentication

– This is the biggest hurdle to adoption of TV everywhere – needs to be

simple for all users

•

High reliability live streaming

•

High reliability live streaming

•

Multiplicity of devices and streaming formats makes the headend

more complicated…

iPads iPhones Android XBOX PCs Connected TVs STB etc

– iPads, iPhones, Android, XBOX, PCs, Connected TVs, STB, etc…

•

Security

– Complexity of Digital Rights Management

Ad

i i

•

Advertising

(31)

4 components to unify the

delivery of TV content on

managed/unmanaged

networks

MPEG-TS over

Managed

Networks

Internet

Over-The-Top Delivery (OTT)

(32)

Interactive TV service delivery platform (middleware for

IPTV

and

Multiscreen/Over-the-Top TV

)

http://www.beenius.tv/

Hardware MPEG-4 Transcoder (40 channels – 1RU) with integrated segmenter and publishing for HLS, MSS

http://www.mysticvideo.net

Edgeware provides the video delivery servers needed to offer video services across

managed

and

unmanaged

networks, with the ability to reach any screen, at any time, with any content.

These services include:

- video on demand (VOD),

- Live TV, time shift TV and network Personal Video Recorder (nPVR),

- as well as offering wholesale Content Delivery Network (CDN) management services

Edgeware is a hardware (server) manufacturer and software provider.

http://www.edgeware.tv/

Multiscreen (OTT)

adaptive bit rate streams

and

MPEG transport streams

monitoring probes

Multiscreen (OTT)

adaptive bit rate streams

and

MPEG transport streams

monitoring probes

(33)

6. Overview of the multiscreen video delivery ecosystem

IPTV/OTT middleware

Multiscreen support

Enables interactive TV on smartphones,

tablets, PCs and TVs

Same look and feel regardless if content is

coming from managed (IPTV) or

unmanged network (OTT).

Social TV and Interactive TV

Direct link on user interface to Facebook,

T itt

d Fli k

(34)

S

L

k

d F

l

Same Look and Feel…

iPh

iPhone

GUI

iPad

GUI

Television

(35)

Mystic One – MPEG Video Transcoding Platform

Transcoder Overview

•40 independent 1080i/p transcode channels.

•Up to 60 ABR or SD transcode channels.

•Any-to-Any or Any-to-Many modes including GOP aligned and aspect ratio matched

profile streams.

•All broadcast and film formats including progressive and interlaced at all applicable

frame rates.

(36)

Long tail: Very long tail:

•nPVR (> 10TB) •Central servers / logical clusters (~5‐10TB) •CDNs, OTT operators, telco/cable core networks

Network

Content/Service/ Server Management

Short to mid tail:

•Distributed servers (~1TB storage) •Telco/cable metro & access networks

Network

≥

80%

Edge Caches

≤

20%

Core N/W

Storage & streaming close to user:

•Most demanded closest: Short tail

•Frequently demanded between: Mid tail

•Least demanded at centre: Long tail

Short Tail Mid Tail Long Tail Deman d R ki Ranking

(37)

6. Overview of the multiscreen video delivery ecosystem

•

Simultaneous managed and unmanaged network support with hardware acceleration

g

pp

•

MTBF measured in decades

•

Up to 24TB of Flash Storage

•

Up to 20Gbps Transmission (up to 32 000 concurrent streams/users)

•

Up to 20Gbps Transmission (up to 32,000 concurrent streams/users)

(38)

SUPPORTS:

- Microsoft Smoothstream

- Apple HLS

- Adobe HDS

OTT monitoring probes

Alarm categories are:

- Transport errors (e.g bandwidth)

- HTTP errors (e.g missing files on servers)

(39)

Agenda

1.

a)

using the Internet

b)

Difference between MPEG2-Transport Stream delivery and HTTP

streaming

2

Li

D

(IPTV

d M lti

Vid

D li

)

2.

3.

4

4.

5.

6

6.

Overview of the multiscreen video delivery ecosystem (from content to

consumer devices)

(40)

(41)

(42)

(43)

Our Know-How

Our Markets

MPEG 2/4 C

i

d t

t

i

t

• MPEG-2/4 Compression and test equipment

• DTV headend (live), VOD, EPG (guide), PVR

• DTV, IPTV and OTT delivery

IPTV

Satellite

,

y

•

PSIP / PSI-SI (Metadata and Guide)

Digital TV headend design

Fiber Transport

• Digital TV headend design

• RF distribution (QPSK, QAM, 8VSB)

• Carrier Ethernet / DWDM solutions

p

Cable TV and

RF distribution

• RF Test and Measurement

• CATV Network Powering

• Wireless Point-to-Point and Multipoint

RF distribution

TV and FM

Broadcast

p

• HFC and PON distribution design

• Network Management

• L Band Signal Management and transport

(44)

Understanding TV Everywhere/

Multiscreen Video Delivery

Thank you / Merci

to the CCSA and CCBE members

Louis Sebastiani

[email protected]