CMS manages: pload

● Job scheduling and profile

management

● Asset library

● Web page content

● Ad insertion (optional)

CONTENT MANAGEMENT SYSTEM (CMS)

starnerdz

starnerdz

ON-PREMISES

Control M

ethods

EDGE DISTRIBUTION

DATA TIER

DEVICES

Encoders

INTERNET

MICROSOFT AZURE

Video and Metadata

Stream Preview

Program(s)

Europe

Asia

AmericaCHANNEL

Dynamic

Packaging

ASSET STORAGE

Preview URL

(Private)

LIVE STREAMING

200 Mbps per Streaming Unit

STREAMING ENDPOINT

Ingest URL

REST

Signal breaks

for commercials

Video/Audio

Blob Storage

Metadata Storage

as requested

DASHHLSSmooth

HDS

Archive video

Smooth & metadata

when requested

CONTENT

DISTRIBUTIONNETWORK(CDN)

Live events such as sports or performances are viewed all over the world on different devices. The bandwidth of each device varies depending on proximity to a tower, etc. Adaptive rate streaming means bit rates vary for every device, from low-res to hi-res. A streaming endpoint in the cloud reaches all.

A Content Management System (CMS), such as Ooyala, controls functions of the live broadcast. The system manages all the elements of the live workflow such as encoder configuration, asset management, ad signals, subclips for highlight reels. It also can manage telemetry and system health.

Live stream content is encoded at multiple bit rates into Smooth or Real Time Messaging Protocol (RTMP) using a hardware encoder. Operators mark breaks in the action for later ad insertion.

Live stream content is streamed to the channel via HTTP. Optionally use ExpressRoute for fast private transport.

Preview URL monitors the health of the stream before and during broadcast.

Programs act on a stream to record it. Different programs can create different recordings of the same stream.

Streams and associated metadata are saved to Assets in blob storage and an SQL database.

Devices attempt to consume streaming content via a device specific URL. Devices contain apps built with specific frame-works which can consume the stream.

If the proper streaming file already exists on the CDN, it’s sent to the device. If not, the request is sent to the Streaming Endpoint. The device may be sent a lower quality stream if bandwidth is low.

Content is dynamically encoded to the specific streaming format required by the device making the request.

Content is processed using scalable Reserved Units. Each unit can deliver up to 200 Mbps. Additional units start up or shut down based on load.

The Streaming Endpoint delivers the request stream to the CDN, which propagates it to all geographic regions.

Devices consume streaming content. Devices run apps built from player framework SDKs.

Live Media Streaming

© 2015 Microsoft Corporation. All rights reserved. Created by the Azure poster team Email: AzurePoster@microsoft.com

1

2

3

5

6

4

7

8

9

10

11

12

14

8

11

2

3

4

5

6

7

8

9

10

12