ISO/IEC 23008-1:2014/Amd 1:2015
(Amendment)Information technology — High efficiency coding and media delivery in heterogeneous environments — Part 1: MPEG media transport (MMT) — Amendment 1: Additional technologies for MPEG Media Transport (MMT)
Information technology — High efficiency coding and media delivery in heterogeneous environments — Part 1: MPEG media transport (MMT) — Amendment 1: Additional technologies for MPEG Media Transport (MMT)
Technologies de l'information — Codage à haute efficacité et livraison des medias dans des environnements hétérogènes — Partie 1: Transport des médias MPEG — Amendement 1: Technologies supplémentaires pour le transport des médias MPEG
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 23008-1
First edition
2014-06-01
AMENDMENT 1
2015-04-01
Information technology — High
efficiency coding and media delivery
in heterogeneous environments —
Part 1:
MPEG media transport (MMT)
AMENDMENT 1: Additional technologies
for MPEG Media Transport (MMT)
Technologies de l’information — Codage à haute efficacité et livraison
des medias dans des environnements hétérogènes —
Partie 1: Transport des médias MPEG
AMENDEMENT 1: Technologies supplémentaires pour le transport
des médias MPEG
Reference number
ISO/IEC 23008-1:2014/Amd.1:2015(E)
©
ISO/IEC 2015
---------------------- Page: 1 ----------------------
ISO/IEC 23008-1:2014/Amd.1:2015(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2015
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
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2015 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 23008-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.
ISO/IEC 23008 consists of the following parts, under the general title Information technology — High
efficiency coding and media delivery in heterogeneous environments:
— Part 1: MPEG media transport (MMT)
— Part 2: High efficiency video coding (HEVC)
— Part 3: 3D Audio
— Part 5: HEVC Conformance testing and reference software
— Part 8: Conformance Specification for HEVC
— Part 10: MPEG Media Transport Forward Error Correction (FEC) codes
— Part 11: MPEG Media Transport Composition Information
— Part 12: Image file format
— Part 13: MMT Implementation Guidelines
© ISO/IEC 2015 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 23008-1:2014/Amd.1:2015(E)
Information technology — High efficiency coding and
media delivery in heterogeneous environments —
Part 1:
MPEG media transport (MMT)
AMENDMENT 1: Additional technologies for MPEG Media
Transport (MMT)
The following instructions apply to the (re-organized) first edition of ISO 23008-1.
Add the following definitions to 3.1, suitably numbered.
3.1.33
asset delivery characteristics
description about required Quality of Service (QoS) for delivery of Assets. ADC is represented by the
parameters agnostic to specific delivery environment.
Add the following abbreviated terms to 3.2, suitably numbered
ADC asset delivery characteristics
ARQ automatic repeat request
In 5.2, amend the 1st paragraph to read as follows.
As shown in Figure 4, a Package is a logical entity. A Package shall contain one or more presentation
information documents such as one specified in ISO 23008-11, one or more Assets and for each Asset an
associated Asset Delivery Characteristics (ADC). In other words, as processing of a Package is applied
per MPU basis and an Asset is a collection of one or more MPUs that share the same Asset ID. It can be
also considered that one Package is composed of one Presentation Information, one or more MPUs and
associated ADC for each Asset.
© ISO 2015 – All rights reserved 1
---------------------- Page: 4 ----------------------
ISO/IEC 23008-1:2014/Amd.1:2015(E)
In 5.2.1, replace Figure 4 with the following figure.
Figure — AMD1.1 — Overview of package
In 5.2, insert the following paragraph after the one beginning in “Presentation Information (PI) document
specify . ”.
Asset Delivery Characteristics (ADC) shall provide the required QoS information for transmission of
Assets. Multiple Assets can be associated with a single ADC. However a single Asset shall not be associated
with multiple ADCs. This information can be used by the entity packetizing the Package to configure the
fields of the MMTP payload header and MMTP packet header for efficient delivery of the Assets.
Add the following sub-clause as 5.5.
5.5 Asset delivery characteristics
5.5.1 Introduction
The Asset Delivery Characteristics (ADC) describes the QoS requirements and statistics of Assets for
delivery. Each Asset in a Package shall be associated with an ADC. The ADC for each Asset is used by
an MMT sending entity to derive the appropriate QoS parameters and the transmission parameters
to which a resource reservation and a delivery policy may apply. The ADC is represented in a
protocol agnostic format to be generally used by QoS control service entity defined by other standard
development organizations, such as IETF, 3GPP, IEEE, etc. It consists of a QoS_descriptor element
and a bitstream_descriptor element. ADC is an XML file that conforms to the schema in section
5.5.3. The MIME type of ADC is defined as Annex H.
5.5.2 ADC Descriptors
5.5.2.1 QoS descriptor
The QoS_descriptor element defines required QoS levels on delay and loss for Asset delivery. It
consists of loss_tolerance attribute, jitter_sensitivity attribute, class_of_service
attribute and bidirection_indicator attribute.
5.5.2.2 Bitstream descriptor
2 © ISO 2015 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC 23008-1:2014/Amd.1:2015(E)
The bitstream_descriptor element provides the statistics of Asset. It provides the parameters to
implement token bucket traffic shaping such as sustainable rate and buffer size. In addition, peak rate
and maximum MFU size represent burstiness of Asset as shown in Figure AMD1. 2., where burstiness is
defined as a ratio between a peak_rate and sustainable_rate.
Figure — AMD1.2 — The bitstream_descriptor depicted for a variable bit-rate of Asset
5.5.3 Syntax
© ISO 2015 – All rights reserved 3
---------------------- Page: 6 ----------------------
ISO/IEC 23008-1:2014/Amd.1:2015(E)
5.5.4 Semantics
loss_tolerance — indicates required loss tolerance of the Asset for the delivery. The value of loss_
tolerance attribute is listed in Table AMD1.1.
Table — AMD1.1 — Value of loss_tolerance attribute
Value Description
0 This Asset requires lossless delivery
1 This Asset allows lossy delivery
jitter_sensitivity — indicates required jitter level of underlying delivery network for the Asset
delivery between end-to-end. The value of jitter_sensitivity attribute is listed in Table AMD1.2.
Table — AMD1.2 — Value of jitter_sensitivity attribute
Value Description
This Asset requires the preserve time variation between MMTP pack-
0
ets
This Asset doesn’t require the preserve time variation between MMTP
1
packets.
class_of_service — classifies the services in different classes and manage each type of bitstream
with a particular way. For example, Media Aware Network Element (MANE) can manage each type
of bitstream with a particular way. This field indicates the type of bitstream attribute as listed in
Table AMD1.3.
Table — AMD1.3 — Value of class_of_service attribute
Value Description
The Constant Bit Rate (CBR) service class shall guarantee peak bitrate
at any time to be dedicated for transmission of the Asset. This class is
0
appropriate for realtime services which require fixed bitrate such as
VoIP without silence suppression.
The Variable Bit Rate (VBR) service class shall guarantee sustainable
birate and allow peak bitrate for the Asset with delay constraints over
1
shared channel. This class is appropriate for most realtime services
such as video telephony, video conferencing, streaming service, etc.
Bidirection_indicator — If set to ‘1’, bidirectional delivery is required. If set to ‘0’, bidirectional
delivery is not required.
Bitstream_descriptorVBRType — when class_of_service is ’1’, “Bitstream_
descriptorVBRType” shall be used for “Bitstream_descriptorType”.
Bitstream_descriptorCBRType — when class_of_service is ’0’, “Bitstream_
descriptorCBRType” shall be used for “Bitstream_descriptorType”.
sustainable_rate — defines the minimum bitrate that shall be guaranteed for continuous
delivery of the Asset. The sustainable_rate corresponds to drain rate in token bucket model. The
sustainable_rate is expressed in bits per second.
4 © ISO 2015 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 23008-1:2014/Amd.1:2015(E)
buffer_size — defines the maximum buffer size for delivery of the Asset. The buffer absorbs excess
instantaneous bitrate higher than the sustainable_rate and the buffer_size shall be large
enough to avoid overflow. The buffer_size corresponds to bucket depth in token bucket model.
Buffer_size of a CBR (constant bit rate) Asset shall be zero. The buffer_size is expressed in bytes.
peak_rate — defines peak bitrate during continuous delivery of the Asset. The peak_rate is the
highest bitrate during every MFU_period. The peak_rate is expressed in bits per second.
MFU_period — defines period of MFUs during continuous delivery of the Asset. The MFU_period
is measured as the time interval of sending time between the first byte of two consecutive MFUs. The
MFU_period is expressed in millisecond.
max_MFU_size — indicates the maximum size of MFU, which is MFU_period*peak_rate. The max_
MFU_size is expressed in byte.
Add the following subclause as 5.6.
5.6 Bundle delivery characteristics
5.6.1 Introduction
The Bundle Delivery Characteristics (BDC) describes the QoS requirements and statistics of Bundle
for delivery. Each Bundle in a Package shall be associated with an BDC. The BDC for each Bundle is
used by an MMT sending entity to derive the appropriate QoS parameters and the transmission
parameters to which a resource reservation and a delivery policy may apply. The BDC is represented in
a protocol agnostic format to be generally used by QoS control service entity defined by other standard
development organizations, such as IETF, 3GPP, IEEE, etc. It consists of a QoS_descriptor element
and a bitstream_descriptor element as defined in ADC.
5.6.2 BDC descriptors
5.6.2.1 QoS descriptor
The QoS_descriptor element defines required QoS levels on delay and loss for Bundle delivery. It
consists of loss_tolerance attribute, jitter_sensitivity attribute, class_of_serivce
attribute and bidirection_indicator attribute.
5.6.2.2 Bitstream descriptor
The bitstream_descriptor element provides the statistics of Bundle. It provides the parameters to
implement token bucket traffic shaping such as sustainable rate and buffer size. In addition, peak rate
and maximum MFU size represent burstiness of Bundle where burstiness is defined as a ratio between
a peak_rate and sustainable_rate.
5.6.3 Syntax
type=”mmt:BundleDeliveryCharacteristicType”>
minOccurs=”1” maxOccurs=”unbounded”/>
© ISO 2015 – All rights reserved 5
---------------------- Page: 8 ----------------------
ISO/IEC 23008-1:2014/Amd.1:2015(E)
descriptorType”/>
5.6.4 Semantics
loss_tolerance — indicates required loss tolerance of the Bundle for the delivery. The value of loss_
tolerance attribute is listed in Table AMD1.1.
Table — AMD1.4 — Value of loss_tolerance attribute
Value Description
0 This Bundle requires lossless delivery
1 This Bundle allows lossy delivery
jitter_sensitivity — indicates required jitter level of underlying delivery network for the Bundle
delivery between end-to-end. The value of jitter_sensitivity attribute is listed in Table AMD1.2.
Table — AMD1.5 — Value of jitter_sensitivity attribute
Value Description
This Bundle requires the preserve time variation between MMT protocol
0
packets
This Bundle doesn’t require the preserve time variation between MMT
1
protocol packets.
class_of_service — classifies the services in different classes and manage each type of bitstream
with a particular way. For example, MANE can manage each type of bitstream with a particular way.
This field indicates the type of bitstream attribute as listed in Table AMD1.3.
6 © ISO 2015 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 23008-1:2014/Amd.1:2015(E)
Table — AMD1.6 — Value of class_of_service attribute
Value Description
The Constant Bit Rate (CBR) service class shall guarantee peak bitrate
at any time to be dedicated for transmission of the Bundle. This class is
0
appropriate for realtime services which require fixed bitrate such as VoIP
without silence suppression.
The Variable Bit Rate (VBR) service class shall guarantee sustainable
birate and allow peak bitrate for the Bundle with delay constraints over
1
shared channel. This class is appropriate for most realtime services such
as video telephony, videoconferencing, streaming service, etc.
Bidirection_indicator — If set to ‘1’, bidirectional delivery is required. If set to ‘0’, bidirectional
delivery is not required.
Bitstream_descriptorVBRType — when class_of_service is ’1’, “Bitstream_
descriptorVBRType” shall be used for “Bitstream_descriptorType”.
Bitstream_descriptorCBRType — when class_of_service is ’0’, “Bitstream_
descriptorCBRType” shall be used for “Bitstream_descriptorType”.
sustainable_rate — defines the minimum bitrate that shall be guaranteed for continuous
delivery of the Asset. The sustainable_rate corresponds to drain rate in token bucket model. The
sustainable_rate is expressed in bytes per second.
buffer_size — defines the maximum buffer size for delivery of the Bundle. The buffer absorbs excess
instantaneous bitrate higher than the sustainable_rate and the buffer_size shall be large enough
to avoid overflow. The buffer_size corresponds to bucket depth in token bucket model. Buffer_
size of a CBR (constant bit rate) Bundle shall be zero. The buffer_size is expressed in bytes
peak_rate — defines peak bitrate during continuous delivery of the Bundle. The peak_rate is the
highest bitrate during every MFU_period. The peak_rate is expressed in bytes per second.
MFU_period — defines period of MFUs during continuous delivery of the Bundle. The MFU_period
measured as the time interval of sending time between the first byte of two consecutive MFUs. The
MFU_period is expressed in millisecond
max_MFU_size — indicates the maximum size of MFU, which is MFU_period*peak_rate. The max_
MFU_size is expressed in byte.
MMT_package_id — this field is a unique identifier of the Package. This BDC describes
delivery characteristics of all the possible Bundles within the scope of this package.
Element_Asset_id — identifier of asset which is an element of current bundle
Bundle_id — identifier of bundle which distinguish bundles within the package.
Intra_Bundle_Priority — defines the relative priority level among assets within a bundle, which
ranges from 0(highest) to 12(lowest).
Inter_Bundle_Priority — defines the relative priority level among bundles, which ranges from
0(highest) to 12(lowest).
In 6.3.1, insert the following sentence in last sentence of the paragraph.
When it is required to store the ADC together with MPU, it shall be stored in the ‘meta’ box at the file
level and its presence shall be indicated through the ‘is_adc_present’ flag and the MIME type of the
item that stores the ADC.
© ISO 2015 – All rights reserved 7
---------------------- Page: 10 ----------------------
ISO/IEC 23008-1:2014/Amd.1:2015(E)
Replace the following syntax in 6.3.2.
aligned(8) class MPUBox
extends FullBox(‘mmpu’, version, 0){
unsigned int(1) is_complete;
unsigned int(1) is_adc_present;
unsigned int(6) reserved;
unsigned int(32) mpu_sequence_number;
AssetIdentifierBox();
}
Add the following semantics in 6.3.3.
is_adc_present — indicates whether the ADC is present as an XML box in a ‘meta’ box. The MIME
type of the ADC file as defined Annex H shall be indicated in an item informaiton box ‘iinf’.
Replace the following sentence in the 2nd paragraph in 8.1
The MMT protocol is an application layer transport protocol supporting delivery of Packages over
heterogeneous packet-switched delivery networks, including IP-based network environments. The
MMT protocol provides enhanced features for delivery of Packages such as protocol level multiplexing,
which for example enables various Assets to be delivered over a single MMTP packet flow, and delivery
timing model independent of presentation time to adapt to a wide range of network jitters
with the following sentence:
The MMT protocol is an application layer transport protocol supporting delivery of Packages over
heterogeneous packet-switched delivery networks, including IP-based network environments. The MMT
protocol provides enhanced features for delivery of Packages such as protocol level multiplexing, which
for example enables various Assets to be delivered over a single MMTP packet flow, and delivery timing
model independent of presentation time to adapt to a wide range of network jitters, and information to
support Quality of Service (QoS).
In 8.2.1, replace the following sentence in the first paragraph
It supports several enhanced features, such as media multiplexing and network jitter calculation.
with the following sentence:
It supports several enhanced features, such as media multiplexing, network jitter calculation, and
QoS indication.
In 8.2.1, add the following paragraph after the last paragraph.
MMT protocol provides priority related information to enable underlying network layers or the
intermediate network entities to map the priority information in MMTP packet header such as type_
of_bitrate, delay_sentivity, transmission_priority and flow_label to the network protocol according to
predetermined priority mapping policy. When DiffServ [RFC2474] is used, this priority information
may be used to set the 6-bit DSCP value of the DS field in the IP header. The underlying network entity
supporting Diffserv shall then process the IP packets according to the mapping defined by the priority
related information in MMTP packet header.
8 © ISO 2015 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 23008-1:2014/Amd.1:2015(E)
Insert the following figure after Figure 7.
Figure — AMD1.3 — MMTP packet header, payload and footer
Add the following semantics in 8.2.3.
Version (V:2bit) — indicates the version number of the MMTP protocol. This field shall be set to
‘01’ to comply with this specification.
QoS_classifier_flag (Q:1bit) — When set to ‘1’, it indicates that QoS classifier information is used.
QoS classifier contains delay_sensitivity field, reliability_flag field, and tranmission_
priority field. It indicates the QoS class property. The application can perform per-class QoS operations
according to the particular value of one property. The class values are universal to all independent sessions.
flow_identifier_flag (F:1bit) — When set to ‘1’, it indicate that flow identifier information is
used. flow identifier contains flow_label field, and flow_extension_flag field. It indicates the
flow identifier. The application can perform per-flow QoS operations in which network resources are
temporarily reserved during the session. A flow is defined to be a bitsream or a group of bitstreams
whose network resources are reserved according to transport characteristics or ADC in Package.
reliability_flag (r: 1bit) — When “reliability_flag” is set to ‘0’, it shall indicate that the
data is loss tolerant (e.g. media data), and that the following “transmission_priority” field shall be
used to indicate relative priority of loss. When “reliability_flag” is set to ‘1’, the “transmission_
priority” field will be ignored, and shall indicate that the data is not loss tolerant (e.g., signaling data,
service data, or program data).
flow_extension_flag (E: 1bit) — If there are more than 127 individual flows, this bit is set to ‘1’
and one more byte can be used in extension_header.
type_of_bitrate (TB: 3bits) — indicates the type of bitrate as listed in Table AMD1.4.
Table — AMD1.4 — Value of type_of_bitrate
Value Description
000 Constant Bit Rate (CBR)
001 Non-Constant Bit Rate (nCBR)
010 ~ 111 reserved
delay_sensitivity (DS: 3bits) — indicates the delay sensitivity of the data between end-to-
end delivery for the given service as listed in Table AMD1.5. This field is derived from the application
as the same content may have different delay requirements in different applications.
© ISO 2015 – All rights reserved 9
---------------------- Page: 12 ----------------------
ISO/IEC 23008-1:2014/Amd.1:2015(E)
Table — AMD1.5 — Value of delay_sensitivity
Value Description
111 conversational service (~100ms)
110 live-streaming service (~1sec)
101 delay-sensitive interactive service (~2sec)
100 interactive service (~5sec)
011 streaming service (~10sec)
010 non-realtime service
001 reserved
000 reserved
transmission_priority (TP: 3bits) — provides the transmission_priority for the
media packet, and it may be mapped to the NRI of NAL, DSCP of IETF, or other loss priority field in
another network protocol. This field shall take values from ‘7’ (‘1112’) to ‘0’ (‘0002‘), where 7 is the
highest priority, and ‘0’ is the lowest priority.
flow_label (7bits ) — indicates the flow identifier. The application can perform per-flow QoS
operations in which network resources are temporarily reserved during the session. A flow is defined
to be a bitsream or a group of bitstreams whose network resources are reserved according to transport
characteristics or ADC in Package. It is an implicit serial number from ‘0’ to ‘127’. An arbitrary number is
assigned temporarily during a session and refers to every individual flow for whom a decoder (processor)
is assigned and network resource could be reserved.
Change the second paragraph of 9.1 to the following:
Six types of signalling messages are defined for the consumption of Packages;
Add the following sentence after the one beginning in “Device Capability Information (DCI) message: .”,
suitably numbered:
— Security Software Request (SSWR) message: it is used to request security software for comsuming
Package or Asset by an MMT receiving entity. It can also include PA table or MP table (see 9.3.7).
Change the third paragraph of 9.1 to the following:
Six signaling messages are defined that relate to the delivery of the Package:
Add the following sentence after the one beginning in “HRBM: .”, suitably numbered:
— Automatic Repeat-Request(ARQ) Configuration (AC) message: It provides information required for
ARQ configuration (see 9.4.3);
— Automatic Repeat-Request(ARQ) Feedback (AF) message: It provides information required for ARQ
feedback (see 9.4.4);
— Measurement Configuration (MC) message: This message type is used for providing information to
configure measurement of delivery quality (see 9.4.5);
— Reception Quality Feedback (RQF) message: This message type is used for measurement reporting
by an MMT receiving entity (see 9.4.6);
— Asset Delivery Characteristic (ADC) message: This message type is used for providing information
to configure the network delivery resource (see 9.4.7);
10 © ISO 2015 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/IEC 23008-1:2014/Amd.1:2015(E)
Replace Figure 16 with the following figure:
Figure — AMD1.4 — Structure of the signaling messages and tables for Package consumption
Change the last sentence in 9.3.1 to the following:
The relationship between a message and a table is shown in Figure AMD1.4.
Add the following subclause and change the following chapter numbers from 9.3.12.
6.3.12 Security Software Request (SSWR) Message
6.3.12.1 Introduction
The overall operation of downloadable DRM and CAS for MMT is described in Annex D. There are 5 steps in
Annex D. Among them, the message for the security software request is sent from a receiving MMT entity
to downloadable DRM/CAS server. The message for DRM and CAS SW request is defined in this subclause.
6.3.12.2 Syntax
The syntax of SSWR message is defined in Table AMD1. 6.
Table — AMD1.6 —SSWR Message syntax
Syntax Values No. of bits Mnemonic
SSWR_me
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.