MPEG-DASH Protocol
Prepared by:
Samsung
DASH (Dynamic Adaptive Streaming over HTTP)
The 3GPP Dynamic Adaptive Streaming over HTTP (3GP-DASH) specified in this
specification provides streaming services over HTTP.
The specification for 3GP-DASH primarily defines two formats:
The Media Presentation Description (MPD) describes a Media Presentation
The Segment formats specify the formats of the entity body of the HTTP response
to an HTTP GET request
DASH is not:
system, protocol, presentation, codec, interactivity, client specification
DASH is an enabler
It provides formats to enable efficient and high-quality delivery of streaming services over the
Internet
It is considered as one component in an e2e service
The MPD provides sufficient information for a client to provide a streaming
service to the user
3GP-DASH is intended to support a media-streaming model for delivery of
media content in which control of the delivery lies exclusively with the client.
Highlighted Features
It attempts to be very good in what is to be addressed by the standard
Enable reuse of existing technologies (containers, codecs, DRM etc.)
Enable deployment on top of HTTP-CDNs (Web Infrastructures, caching)
Enable selection based on network and device capability, user preferences
Enable seamless switching
Enable live and DVD-kind of experiences
Supports adaptive on demand and live streaming such as MPEG-4 file format
and MPEG-2TS.
DASH is codec-independent.
DASH supports both the ISO Base Media File Format (essentially the MP4
format) and MPEG-2 transport streams
Efficient and ease of use of existing CDNs, proxies, caches, NATs and firewalls.
Support of seamless switching of tracks.
Signaling, delivery, utilization of multiple DRM schemes.
Supports ad-insertion.
Segments with variable durations.
Sub-segment alignment indication to simplify switching and avoiding
overlapping fragments.
DASH Architecture
HTTP SERVER DASH CLIENT
MPD
MPD DASH Control Engine
MPD
MPD
MPD
MPD Delivery
MPD Parser
Segment
Segment Media
Segment Resources Player
Segment
Segment Segment located by
Segment
Segment
Segment HTTP-URLs Segment Parser
Segment
Segment
Segment
HTTP 1.1
Segment HTTP Client
Segment
Segment
Segment
Media Presentation Description
XML document containing metadata to construct Media Presentation Description (MPD)
appropriate HTTP-URLs to access media segment . <?xml version="1.0" encoding="UTF-8"?>
<xs:schema target
HTTP-URLs Namespace="urn:mpeg:mpegB:schema:DASH:MPD:DI
S2011"
Containing exactly one MPD element Attribute Form Default="unqualified"
Element Form Default="qualified"
Actual playback is not controlled xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xlink="http://www.w3.org/1999/xlink"
The MIME type of MPD is defined as xmlns="urn:mpeg:mpegB:schema:DASH:MPD:DIS2011
">
'application/dash+xml' <xs:import
namespace="http://www.w3.org/1999/xlink" schema
Segment availability start and end time . Location="xlink.xsd"/>
<xs:annotation>
Includes access and timing information <xs:appinfo>Media Presentation
Content addressing via HTTP-URLs Description</xs:appinfo>
</xs:annotation>
Byte range for each accessible segment ...
<!-- MPD: main element -->
Segment availability start and end time in wall- <xs:element name="MPD" type="MPDtype"/>
...
clock time </xs:schema>
Approximate media start time and duration
Instructions on starting playout (for live service)
Includes switching relations across representations
Media Presentation
The collection of encoded and deliverable versions of media content and the
appropriate description of these form a Media Presentation.
Media content is composed of a single or multiple contiguous media content
periods in time.
Each media content period is composed of one or multiple media content
components.
Each media content component may have several encoded versions, referred
to as media streams.
Media Presentation Description Data Model
System Info
Duration=240 sec
Initialization Segment
Period ID=2 Abstraction set 1 http://abc.com/il.mp4
Start=240Sec
Period ID=1 Base URL http://abc.com Representation 1 Representation 1
Start=0sec 5MB Media Segment 1
Abstraction set 0 Start sec=0
http://abc.com/vl.mp4
Representation 2
2MB Segment Info
Period ID=2
Abstraction set 1
Start=240 sec Media Segment 2
Representation 3 Start sec=0
500KB http://abc.com/v2.mp4
Abstraction set 2
Period=3 Representation 4
TM Media Segment 3
Start=300 sec Start sec=0
http://abc.com/v3.mp4
Media Segment 1
Start sec=0
http://abc.com/v4.mp4
URL Addressing
URLs at each level of the MPD are resolved with respect to the BaseURL
elements of levels above.
The base URL information may present on the following levels:
MPD, Period, Adaptation Set, Representation
Alternative base URLs may be are provided through the BaseURL element
the identical segments are accessible at multiple locations.
Adaptation Sets
Each Period consists of one or more Adaptation Sets, which each consists of one or
more Representations.
Representations in the same Adaptation sets are alternatives to each other and
typically contain different encoded versions of the same source:
Such as language, media component type, picture aspect ratio, role, accessibility, viewpoint,
rating.
Adaptation sets can be arranged using @group:
Either one Representation from group 0, or the combination of at most one Representation
from each non-zero group.
Adaptation set ID = grp 1
Representation ID = rep 1
Adaptation set by codec, language , resolution Bandwidth, views etc
....
Representation ID= rep 2 Range for @bandwidth , @width , @height , and @frame rate
Representation ID= rep n
Adaptation set ID = grp 2
Representation ID = rep 1
....
Representation ID= rep 2
Representation ID= rep n
Representations & Sub-representations
A Representation:
One of the alternative choices of the media content typically differing by encoding
parameters such as bitrate, resolution, language, codec, etc.
Aligned within the period‟s boundaries.
Consists of one or more Segments.
Contains an initialization segment or all segments are self-initialising.
May contain zero or more Sub Representations.
A Sub Representation:
Provide the ability for accessing a lower quality version of the Representation.
Examples:
Audio track in a multiplexed Representation.
Lower frame rate for efficient fast-forward.
Segment
A segment is an independent, viewable period of video/audio/timing data..
• Segment sizes of 2 seconds or 10 seconds are reasonable.
Segments are uniquely identified by an HTTP URL.
A client requests the segment, the bit rate, and optionally a specific byte range
in the segment.
• Clients can issue requests and receive segments over any number of concurrent
TCP connections.
The video segment is sent back by the HTTP server in a ‘burst’.
The implementation of the client determines how frequently segments are
requested, when bit rate adaptation occurs, and the overall ‘sensitivity’ of the
application to network congestion.
Segments
A Segment is a unit that can be referenced by an HTTP-URL included in the
MPD.
“http://” and optionally with a byte range.
Segments‟ availability duration: the time window at which the Segments can
be accessed by the HTTP-URL.
Each representation has at most one Segment Info element which provides:
Presence or absence of Initialization and Index Segment information.
HTTP-URL and byte range for each segment.
Segment availability start time and availability end time for live case.
Approximated media start time and duration of each segment.
Fixed or variable duration.
Segment Calculation Formula
End To End Live TV Call Flow
Service Schedule
Service Announcement
Call Flow
Dash Board :Push Service Schedule to BMSC 1/8
BMSC: Retrieve MPD & IS from CDN Edge 1/8
BM-SC: Broadcast Service Announcement 2/8
BMSC : MBMS Session Start 3/8
BMSC :Media Delivery 4/8
Device(M/W): Get service Announcement Metadata Envelope 5/8
Device: User request Live TV service 6/8
Device : Media Delivery to DASH Player 7/8
BMSC: MBMS Session Teardown 8/8
Getting Service Info & MPD
Service Announcement
MBMS Session Start
Launch of Jio Broadcast App
Launch of Jio Broadcast App
Playback Start
Change Channel
Playback Stop
Summary
Dynamic Adaptive Streaming over HTTP (DASH), is an adaptive bit rate
streaming technique that enables high quality streaming .
MPEG-DASH works by breaking the content into a sequence of small HTTP-
based file segments, each segment containing a short interval of playback time
of a content that is potentially many hours in duration.
The content is made available at a variety of different bit rates
The content exists on the server in two parts:
Media Presentation Description (MPD), which describes a manifest of the available
content, its various alternatives,
their URL addresses, and other characteristics;
and segments, which contain the actual multimedia bit streams
Overall Summary
Efficient Broadcast Delivery to a Large Number of Users by using MBSFN
Application layer FEC is used on eMBMS to improve the reliability of streaming
and download services delivery by increasing the amount of tolerable lost
packets for a given FEC overhead.
MPEG-DASH uses HTTP but HTTP can not be multicasted , so for DASH file
Delivery FLUTE is used .
Service ID can be used to identify each eMBMS service , and it is assigned by
Dash Board and Application in the device recognizes each eMBMS service by
Service ID .
Service announcement is used to inform devices about delivery sessions and
also about eMBMS sessions using a schedule description. UEs do not need to
monitor the radio interface for eMBMS sessions continuously.
FDT provides a mechanism transmitting various file related attributes
information in the file transfer session, the attributes include filename, file ID,
file type, file size, etc.
MPD is a XML document containing metadata to construct appropriate HTTP-URLs to
access media segment .
HTTP-URLs
Segment availability start and end time .
Quiz
What is full form of DASH and FLUTE?
Dynamic Adaptation Streaming over HTTP
File Delivery Over Unidirectional Transport
Which two middleware vendor RJIL is using ?
Expway
Qualcomm
File repair and reception report server information will be defined under_________________
description.
Associated Delivery Procedure Description
What is protocol on Sgimb interface and between which two entity?
Diameter between BMSC and MBMS-GW
Which node is responsible for FLUTE encoding of content in eMBMS Network ?
BMSC
MBMS-GW get the MME list from ___________ for session start procedure ?
BMSC
Service Bandwidth and Service area for a schedule will be dined by ____________ .
DASH Board
Which protocol is used for content synchronization between BMSC and eNB?
SYNC
THANK YOU
