Presenter Background
. Nomor Research (20 people company based in Munich in advanced R&D and prototyping for radio (LTE, LTE-A, MBMS) and Internet communication (DASH, IPTV), CEO
. Consultant (Technical Standards) for Qualcomm in R&D and standardization matters
. DASH-related activities . Editor of MPEG-DASH specifications (part 1, 2) . Editor and Rapporteur for 3GPP-DASH specs . Lead of DASH-IF Interoperability working group










HTTP Adaptive Streaming

Split the video into
1 small segments
Encode each segment

2 at multiple bitrates


Client splices together

Why HTTP?
. Why have we chosen to deliver continuous time-critical high-quality media sessions over an unmanaged stateless transaction-based protocol?
. Many answers
. HTTP is ubiquituous, highly scalable delivery is supported and does not require dedicated servers and distribution architectures
. Client-driven using GET requests
. It may not be optimal per se, but it works damn-well
Apple’s HTTP Live Streaming
. http://tools.ietf.org/html/draft-pantos-http-live-streaming-08

. HTTP Live Streaming . supports both live broadcasts and prerecorded content (video on demand). . supports multiple alternate streams at different bit rates, and the client
software can switch streams intelligently as network bandwidth changes. . provides for media encryption and user authentication over HTTPS, allowing publishers to protect their work. . in an Internet-Draft (I-D). I-Ds have no formal status, and are subject to change or removal at any time; therefore they should not be cited or quoted in any formal document. . based on ancient MPEG-2 TS, but heavily deployed today
Technologies based on ISO File Format

.Microsoft SmoothStreaming
. IIS Media Services extension that enables adaptive
streaming of media to clients over HTTP.

. Microsoft has successfully demonstrated delivery of both live and on-demand 1080p HD video
.Adobe HTTP Dynamic Streaming
. inherits technologies from Flash and RTMP
. similar to the HTTP-based solutions from Apple and
Microsoft



DASH Standardization
. MPEG-DASH ISO/IEC 23009 . Part 1*: Media presentation description and segment formats (published 04/2012)
. Corrigenda and Amendments issued for 2012: Improved live, metadata
. Part 2: Conformance and Reference SW (in progress)
. Part 3: Implementation Guidelines (in progress)

. Other relevant MPEG Specifications . ISO/IEC* 14496-12*: ISO Base Media File Format . ISO/IEC* 14496-14*: MP4 File Format . ISO/IEC* 14496-15*: Advanced Video Coding (AVC) file format . ISO/IEC* 23001-7*: Common encryption in ISO base media file format files
. Other Organizations . Organizations adopting DASH: 3GPP, DLNA, OIPF, HbbTV, DECE, DTG, W3C, … . Interoperability efforts in IMTC, DECE, HbbTV and DASH IF . Central point driving this is DASH IF Interop group
* may be accessed at http://www.iso.org/iso/home/standards.htm
What is specified . and what is not?

In words …
. ISO/IEC 23009-1 (MPEG-DASH) specifies formats:
. enabling provisioning and delivering media using existing HTTP-delivery networks and includes support for dynamic adaptation and seamless switching
. Media Presentation Description (MPD) defining XML-structured formats to
announce Segment-URLs and to provide context of Segments in the Media
Presentation for selection and switching

. Segment formats containing efficiently coded media data and metadata
according to or aligned with common media formats, in particular ISO BMFF

. ISO/IEC 23009-1 (MPEG-DASH) does NOT specify: . Codecs (only hooks to signal and encapsulate media streams) . DRM systems (only hooks to signal DRM) . Transport protocol details, i.e. how to use HTTP . Client behavior . Comprehensive auxiliary metadata (only basic common metadata)
. The latter is deferred to other SDOs and industry consortia
Media Presentation Data Model
. Media Presentation Description (MPD) describes


Switching Support Features
. Good switching opportunities: Sequential order for download, decode and present one Representation and then switch to other
. Segment Alignment . permits non-overlapping decoding and presentation of segments from different Representations
. Stream Access Points (SAPs) . presentation time and position in segments at which random access and switching can occur
. Bitstream Switching . concatenation of segments from different Representations results in conforming bitstream
. Media Stream Structure Similarity . permits switching at Open GOP boundaries
. Alignment and SAPs can also apply for Subsegments


Additional work considered in MPEG

.Core Experiments
. DASH formats for General Transport and Storage . Signalling of Quality-related information in DASH . Low-Latency Live Streaming . Cue-Ranges for Chaptering and other Timed
Metadata
.Extensions of File Format
. Inclusion of HEVC in File Format
. Common Encryption and Key Rotation
. Support for Timed Text

DASH Industry Forum
Addressing the dramatic growth of broadband video by recommending a universal delivery format that provides end users with the best possible media experience by dynamically adapting to changing network conditions.

DASH Industry Forum
. Kickoff
. Initiated from DASH Promoters Group
. Inaugural Reception at IBC in September 2012
. Currently 46 members
. Objectives:
. Promote and catalyze market adoption of MPEG-DASH
. Publish interoperability and deployment guidelines
. Facilitate interoperability tests
. Collaborate with standard bodies and industry consortia
in aligning ongoing DASH standards development
use of common profiles across industry organizations
. Please check and join at http://dashif.org

Members



DASH-IF Interoperability WG
. The DASH Interoperability Working Group provides technical guidelines for successful deployment of DASH-based services
. Technical guidelines include, but are not limited to: . developing and publishing interoperability and testing
procedures . support conformance and reference software development . coordination on technical matters with SDOs and other
industry consortia . generation of technical requirements based on deployment
experience to profile and/or improve (MPEG-)DASH
. technical white papers and deployment guidelines
. common repository for DASH-related code points


Interoperability Points (IOPs)
. Relevant collection of features that are considered for deployment scenarios
. Includes, but not limited to: . MPEG-DASH specific features . Codecs including levels and profiles . Subtitles and closed captioning . DRM baseline technologies . Transport-protocol specific aspects . Metadata


DASH264 Base IOP Overview

. ISO base media file format Segments . Video: H.264/AVC MP@3.0 . Audio: HE-AACv2 . Subtitles: SMPTE Timed Text . DRM baseline: ISO/IEC 23001-7 Common Encryption . DASH: Restricted Version of Combination ISO BMFF Live
and On-Demand profiles . Protocol Features

Next Steps
. continue collecting conforming test vectors for DASH264
. initiate informal interoperability efforts
. define technical descriptions for extensions
. support the additional efforts . MPEG standardization process . repository for metadata code points and profiles . development of reference client . deployment guidelines . coordinate with interop and testing organizations . demonstration and prototyping efforts . promotion of MPEG-DASH and DASH264



Getting DASH into <video>

. Great idea, but not (yet) adaptive . Under Development: Media Source Extensions . Allows JavaScript to dynamically construct media streams for <audio> and <video> . Objectives: . Allow JavaScript to construct media streams independent of how media is fetched . Define a splicing and buffering model that facilitates use cases like adaptive streaming, ad-insertion, time-shifting, and video editing. . Minimize the need for media parsing in JavaScript. . Leverage the browser cache as much as possible.
. Provide byte stream definitions for WebM & the ISO Base Media File Format . Google Chrome already supports DASH based on WebM . Support for ISO BMFF and additional browsers expected in near future



Hybrid Use Cases
. Delivery of certain components/media streams/Representations/Segments over broadcast and other components over unicast with synchronization at the client
. Use of unicast for optimized user experience, for example for reducing channel-switch times unicast may be used to enable an immediate switch until sufficient broadcast data is available to seamlessly switch back to the broadcast delivered Representation.
. Seamless transition of a broadcast-delivery into a time-shift mode, such that the same content is available for later consumption in the cloud.

Why DASH and DASH264?
. DASH:
. only universal open standard, developed and published by ISO
. adopted and referenced by many application standards
. addresses a multitude of simple and advanced use cases
. enables highest-quality for multiscreen distribution and dynamic adaptive
switching with maximum efficiency . enables reuse of existing content, devices and delivery infrastructure
. DASH264 . commitment from many vendors and service providers to support and enable deployment based on DASH264 . simple but powerful initial feature set of DASH, DRM and codecs to
address urgent deployment use cases . backed by rigorous testing and conformance . enables revenue generation and differentiation based on a solid grounds
WRAP-UP
. DASH is a standard: ISO/IEC 23009
. DASH is real . you can see it (IBC, Netflix)!
. DASH gets broadly adopted: 3GPP, HbbTV, W3C, DECE,

etc.
. DASH is alive . MPEG and DASH-IF are continuously working on bug fixes, optimizations and new use cases
. Isn’t it time to join the effort?


Thank you
For more information on Qualcomm, visit us at: www.qualcomm.com & www.qualcomm.com/blog
Follow us on:



ⓒ 2012 Qualcomm Technologies, Inc. All rights reserved. Qualcomm is a trademark of Qualcomm Incorporated, registered in the United States and other countries. Trademarks of Qualcomm Incorporated are used with permission. Other products and brand names may be trademarks or registered trademarks of their respective owners.
QUALCOMM, 5775 Morehouse Drive, San Diego, CA 92121-1714