Information technology — Dynamic adaptive streaming over HTTP (DASH) — Part 1: Media presentation description and segment formats — Amendment 1: High Profile and Availability Time Synchronization

Technologies de l'information — Diffusion en flux adaptatif dynamique sur HTTP (DASH) — Partie 1: Description de la présentation et formats de remise des médias — Amendement 1: .

General Information

Status
Withdrawn
Publication Date
02-Jun-2015
Withdrawal Date
02-Jun-2015
Current Stage
9599 - Withdrawal of International Standard
Completion Date
13-Aug-2019
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 23009-1:2014/Amd 1:2015 - High Profile and Availability Time Synchronization
English language
17 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 23009-1
Second edition
2014-05-15
AMENDMENT 1
2015-06-15
Information technology — Dynamic
adaptive streaming over HTTP
(DASH) —
Part 1:
Media presentation description and
segment formats
AMENDMENT 1: High Profile and
Availability Time Synchronization
Technologies de l’information — Diffusion en flux adaptatif
dynamique sur HTTP (DASH) —
Partie 1: Description de la présentation et formats de remise des médias
AMENDEMENT 1
Reference number
ISO/IEC 23009-1:2014/Amd.1:2015(E)
©
 ISO/IEC 2015

---------------------- Page: 1 ----------------------
ISO/IEC 23009-1:2014/Amd.1:2015(E)

COPYRIGHT PROTECTED DOCUMENT
©  ISO/IEC 2015, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2015 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 23009-1:2014/Amd.1:2015(E)
Contents Page
Foreword . iv
7.3.1 General . 9
8.7 ISO base Media File Format Extended Live profile . 14
8.7.1 General . 14
8.7.2 Media Presentation Description constraints . 14
8.7.3 Segment format constraints . 15
8.7.4 Inband Events . 15
8.8 ISO Base Media File Format Extended On Demand profile . 15
8.8.1 General . 15
8.8.2 Media Presentation Description constraints . 16
8.8.3 Segment format constraints . 17
8.9 ISO Base Media File Format Common profile . 17
8.9.1 General . 17
8.9.2 Media Presentation Description constraints . 17
8.9.3 Segment format constraints . 17
© ISO/IEC 2015 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 23009-1:2014/Amd.1:2015(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of
document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any
patent rights identified during the development of the document will be in the Introduction and/or on the ISO
list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment,
as well as information about ISO's adherence to the WTO principles in the Technical Barriers to Trade (TBT)
see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/IEC JTC 1, Information technology, SC 29, Coding of
audio, picture, multimedia and hypermedia information.
iv © ISO/IEC 2015 – All rights reserved

---------------------- Page: 4 ----------------------
Error! Reference source not found. ISO/IEC 23009-1:2014/Amd.1:2015(E)

Information technology — Dynamic adaptive streaming over
HTTP (DASH) — Part 1: Media presentation description and
segment formats, AMENDMENT 1: High Profile and Availability
Time Synchronization
Replace
5.2.3.2 Elements and Attributes added in this Revision
with
nd
5.2.3.2 Elements and Attributes added in ISO/IEC 23009-1:2014 2 edition
© ISO/IEC 2015 – All rights reserved 1

---------------------- Page: 5 ----------------------
ISO/IEC 23009-1:2014/Amd.1:2015(E)
Add
5.2.3.3 Elements and Attributes added in this Revision
This revision adds the following elements and attributes to the schema defined in Annex B compared to the
2014 revision (ISO/IEC 23009-1:2014) of this part of the standard:
 MPD.UTCTiming
2 © ISO/IEC 2015 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC 23009-1:2014/Amd.1:2015(E)
In Table 3 add UTCTiming row at the end after Metrics
UTCTiming
0 . N specifies information on ways to obtain a
synchronization to wall-clock time as used in this Media
Presentation. The order of the elements expresses a
preference of choice by the Media Presentation author.
For more details refer to 5.8.4.10.

© ISO/IEC 2015 – All rights reserved 3

---------------------- Page: 7 ----------------------
ISO/IEC 23009-1:2014/Amd.1:2015(E)
In 5.3.1.3 Replace
 
 
  
    maxOccurs="unbounded"/>
   
   
   
   
   
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
 

 
 
  
   
   
  
 

with
 
 
  
    maxOccurs="unbounded"/>
   
   
   
   
   
   
  
  
  
  
  
  
  
  
  
  
  
  
  
  
 

 
 
  
   
   
  
 
4 © ISO/IEC 2015 – All rights reserved

---------------------- Page: 8 ----------------------
ISO/IEC 23009-1:2014/Amd.1:2015(E)

Add the following section
5.8.4.10 UTC Timing Descriptor
Using the UTCTiming element, the Media Presentation author provides additional information for the client to
optionally obtain wall-clock time to be used in Media Presentation. If multiple schemes are specified by the
Media Presentation author, their order indicates their relative preference, first having the highest, and the last
having the least priority. However, the client may choose any method, potentially having to deal with reduced
accuracy.
© ISO/IEC 2015 – All rights reserved 5

---------------------- Page: 9 ----------------------
ISO/IEC 23009-1:2014/Amd.1:2015(E)
Add the following section
5.8.5.X DASH UTC Timing Schemes
This part of the Standard defines several methods, specified in Table X, by which DASH clients can obtain
wall-clock times as used by the Media Presentation. Specifically this clock is synchronized to the one used to
generate the MPD.
6 © ISO/IEC 2015 – All rights reserved

---------------------- Page: 10 ----------------------
ISO/IEC 23009-1:2014/Amd.1:2015(E)
Table X — Different UTC timing Methods
@schemeIdURI
Description
urn:mpeg:dash:utc:ntp:2014
The identifier indicates that the @value contains a white-space
separated list of servers that are recommended to be used in
combination with the NTP protocol as defined in IETF RFC 5905
for getting the appropriate time.
urn:mpeg:dash:utc:sntp:2014
The identifier indicates that the @value contains a white-space
separated list of servers that are recommended to be used in
combination with the SNTP protocol as defined in IETF RFC 5905
for getting the appropriate time.
urn:mpeg:dash:utc:http-
The identifier indicates that the @value contains a white-space
head:2014
separated list of HTTP URLs that are recommended to be used in
combination with the HTTP protocol as defined in IETF RFC 2616
for getting the appropriate time.
The value of the @value attribute contains a white-space
separated list of HTTP URLs to which HTTP HEAD requests can
be made to obtain the Date information in the HTTP Header
providing the wall-clock time for this Media Presentation
urn:mpeg:dash:utc:http-
The identifier indicates that the @value contains a white-space
xsdate:2014
separated list of HTTP URLs that are recommended to be used in
combination with the HTTP protocol as defined in IETF RFC 2616
for getting the appropriate time.
The value of the @value attribute contains a white-space
separated list of HTTP URLs to which HTTP GET requests can
be made to obtain the timing information. The timing information
is contained in the message body of the HTTP response to the
above HTTP GET request and contains time value formatted
according to xs:dateTime as defined in W3C XML Schema Part 2:
Datatypes specification. This value is based on a wall clock
synchronized to the one used to generate the MPD.
urn:mpeg:dash:utc:http-
The identifier indicates that the @value contains a white-space
iso:2014
separated list of HTTP URLs that are recommended to be used in
combination with the HTTP protocol as defined in IETF RFC 2616
for getting the appropriate time.
The value of the @value attribute contains a white-space
separated list of HTTP URLs to which HTTP GET requests can
be made to obtain the timing information. The timing information
is contained in the message body of the HTTP response to the
above HTTP GET request and contains time value formatted
according to ISO time code as defined in ISO/IEC 8601. This
value is based on a wall clock synchronized to the one used to
generate the MPD.
urn:mpeg:dash:utc:http-
The identifier indicates that the @value contains a white-space
ntp:2014
separated list of HTTP URLs that are recommended to be used in
combination with the HTTP protocol as defined in IETF RFC 2616
© ISO/IEC 2015 – All rights reserved 7

---------------------- Page: 11 ----------------------
ISO/IEC 23009-1:2014/Amd.1:2015(E)
for getting the appropriate time.
The value of the @value attribute contains a white-space
separated list of HTTP URLs to which HTTP GET requests can
be made to obtain the timing information. The timing information
is contained in the message body of the HTTP response to the
above HTTP GET request and contains time value formatted
according to formatted according to NTP timestamp format in
IETF RFC 5905. This value is based on a wall clock synchronized
to the one used to generate the MPD.
urn:mpeg:dash:utc:direct:2014
The identifier indicates that the @value field, contains a time
formatted according to xs:dateTime as defined in W3C XML
Schema Part 2: Datatypes specification. This value is based on a
wall clock synchronized to the one used to generate the MPD
8 © ISO/IEC 2015 – All rights reserved

---------------------- Page: 12 ----------------------
ISO/IEC 23009-1:2014/Amd.1:2015(E)
Replace 7.3.1 with the following:
7.3.1 General
The Media Presentation as introduced in 5 and 6 is instantiated in this subclause using the ISO base media
file format as defined in ISO/IEC 14496-12 as Segment formats.
An ISOBMFF-based DASH Media Presentation is described by an MPD as specified in 5.1. The MIME type of
the MPD shall be as defined in Annex C.
The general rules defined in 7.2 shall apply.
The @mimeType attribute of each Representation shall be provided according to RFC 4337. Additional
parameters may be added according to RFC 6381.
If present, the @SegmentProfiles shall provide a comma-separated list of the individual Segment profile
i
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.