没有合适的资源?快使用搜索试试~ 我知道了~
资源推荐
资源详情
资源评论
DASH Content Protection
using Microsoft PlayReady
Implementing Content Protection for Live and On-
Demand Profiles of Dynamic Adaptive Streaming
over HTTP (ISO/IEC 23009-1) using Common
Encryption (ISO/IEC 23001-7) and Microsoft
PlayReady
October 8, 2014
Version 1.2
Abstract:
The ISO/IEC 23009-1 ISO Base Media File Format On-Demand and Live DASH Profiles can be
used with the ISO/IEC 23001-7, “Common Encryption in ISO base media file format files”
specification. Microsoft PlayReady supports both ISO/IEC 23001-7 and ISO/IEC 23009-1. This
specification details how to create an ISO/IEC 23009-1 Media Presentation Description file
signaling the use of Microsoft PlayReady for ISO/IEC 14496-12 media representations for
both Live and On-Demand adaptive streaming scenarios.
8-Oct-14/1.2 i
Legal Notice
© 2014 Microsoft Corporation. All rights reserved. This document is provided "as-is." The Information
contained in this document, including URL and other Internet Web site references, may change without
notice. You bear the risk of using it.
This document does not provide you with any legal rights to any intellectual property in any Microsoft
product. You may copy and use this document for your internal, reference purposes. You may not
remove any notices from this document.
8-Oct-14/1.2 ii
Contents
1 Introduction ............................................................................. 1
1.1 Scope ......................................................................................................................... 1
1.2 Conventions ............................................................................................................. 1
1.3 Terminology, Abbreviations and Acronyms ...................................................... 2
1.4 References ................................................................................................................ 5
1.5 Change History ........................................................................................................ 6
2 PlayReady DASH Content Protection Scheme ....................... 6
2.1 DASH ContentProtection Descriptor Elements ............................................... 7
2.2 Implementation Recommendations and Requirements ................................. 12
3 Media Presentation Description Example ............................ 15
3.1 Correct PRO in Initialization Segment or Media Content ............................. 15
3.2 Including a PlayReady header Object in the MPD .......................................... 16
Tables
Table 1 – Track Encryption Box Fields .......................................................................................... 10
Table 2 – KID representation example ........................................................................................... 15
8-Oct-14/1.2 1
DA S H C O N T E N T P R OT E C T I O N
U S I N G M I C R O S O F T P L A Y R E A DY
VERSION 1.2
OCTOBER 8, 2014
1 INTRODUCTION
The MPEG’s Dynamic Adaptive Streaming over HTTP standard [DASH] specifies formats for the
delivery of media content from HTTP servers to HTTP clients. In DASH the presentation of
media content is described by a Media Presentation Description (MPD) file. The MPD provides
resource identifiers for Segments along with context for these resources within a Media
Presentation.
In DASH a Media Presentation consists of a time sequence of Periods ([DASH], section 5.3.2).
Within a Period, media content is arranged into a set of interchangeable encoded versions
called Adaptation Sets ([DASH], section 5.3.3). Each Adaptation Set consists of Representations
([DASH], section 5.3.5) - deliverable encoded versions of the media content components.
A ContentProtection Descriptor element may be associated with an Adaptation Set or a
Representation, to indicate the encryption scheme, and one or more ContentProtection
Descriptor elements may be added to enable DRM license acquisition ([DASH], section 5.8.4.1).
1.1 SCOPE
How to use Microsoft PlayReady as the Content Protection scheme in an ISO/IEC 23009-1 DASH
Media Presentation Description file.
1.2 CONVENTIONS
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”,
“SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be
interpreted as described in [RFC2119]. That is:
“MUST”, “REQUIRED” and “SHALL” mean that the definition is an absolute requirement
of the specification.
“MUST NOT” and “SHALL NOT” mean that the definition is an absolute prohibition of
the specification.
剩余19页未读,继续阅读
资源评论
yingmuliuchuan
- 粉丝: 29
- 资源: 8
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功