ISO/IEC 13818-1:2000/Amd 1:2003

INTERNATIONAL ISO/IEC
STANDARD 13818-1
Second edition
2000-12-01
AMENDMENT 1
2003-08-01
Corrected version
2003-10-15
Information technology — Generic
coding of moving pictures and
associated audio information: Systems
AMENDMENT 1: Carriage of metadata over
ITU-T Rec. H.222.0ISO/IEC 13818-1
streams
Technologies de l'information — Codage générique des images
animées et du son associé: Systèmes
AMENDEMENT 1: Transport de métadonnées sur «streams»
ITU-T Rec. H.222.0ISO/CEI 13818-1

Reference number
ISO/IEC 13818-1:2000/Amd.1:2003(E)
©
ISO/IEC 2003
ISO/IEC 13818-1:2000/Amd.1:2003(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO/IEC 2003
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing 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 2003 — All rights reserved

ISO/IEC 13818-1:2000/Amd.1:2003(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.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
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.
Amendment 1 to ISO/IEC 13818-1:2000 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia
information, in collaboration with ITU-T. The identical text is published as ITU-T Rec. H.222.0.
In this corrected version of ISO/IEC 13818-1:2000/Amd.1:2003 a “reserved” field has been inserted in
Table AMD1-13.
© ISO/IEC 2003 — All rights reserved iii

ISO/IEC 13818-1:2000/Amd.1:2003 (E)
INTERNATIONAL STANDARD
ITU-T RECOMMENDATION
Information technology – Generic coding of moving pictures and
associated audio information: Systems
Amendment 1
Carriage of metadata over ITU-T Rec. H.222.0 | ISO/IEC 13818-1 streams
1) Subclause 2.1
Insert the following new definitions and renumber existing ones accordingly:
2.1.28 metadata: Information to describe audiovisual content and data essence in a format defined by ISO or any
other authority.
2.1.29 metadata access unit: A global structure within metadata that defines the fraction of metadata that is
intended to be decoded at a specific instant in time. The internal structure of a metadata Access Unit is defined by the
format of the metadata.
2.1.30 metadata application format: Identifies the format of the application that uses the metadata; signals
application specific information for transport of metadata.
2.1.31 metadata decoder configuration information: Data needed by a receiver to decode a specific metadata
service. Depending on the format of the metadata, decoder configuration information may or may not be needed.
2.1.32 metadata format: Identifies the coding format of metadata.
2.1.33 metadata service: Coherent set of metadata of the same format delivered to a receiver for a specific purpose.
2.1.34 metadata service id: Identifier of a specific metadata service; used for some transport methods of the
metadata.
2.1.35 metadata stream: The concatenation or collection of metadata Access Units from one or more metadata
services.
ITU-T Rec. H.222.0 (2000)/Amd.1 (12/2002) 1

ISO/IEC 13818-1:2000/Amd.1:2003 (E)
2) Table 2-18
Define a tag for a metadata stream by replacing Table 2-18 in clause 2:
Table 2-18 – Stream_id assignments
Stream_id Note Stream coding
1011 1100 (1) program_stream_map
1011 1101 (2) private_stream_1
1011 1110 padding_stream
1011 1111 (3) private_stream_2
110x xxxx ISO/IEC 13818-3 or ISO/IEC 11172-3 or ISO/IEC 13818-7 or ISO/IEC 14496-3 audio stream
number x xxxx
1110 xxxx ITU-T Rec. H.262 | ISO/IEC 13818-2 or ISO/IEC 11172-2 or ISO/IEC 14496-2 video stream
number xxxx
1111 0000 (3) ECM_stream
1111 0001 (3) EMM_stream
1111 0010 (5) ITU-T Rec. H.222.0 | ISO/IEC 13818-1 Annex A or ISO/IEC 13818-6_DSM-CC_stream
1111 0011 (2) ISO/IEC_13522_stream
1111 0100 (6) ITU-T Rec. H.222.1 type A
1111 0101 (6) ITU-T Rec. H.222.1 type B
1111 0110 (6) ITU-T Rec. H.222.1 type C
1111 0111 (6) ITU-T Rec. H.222.1 type D
1111 1000 (6) ITU-T Rec. H.222.1 type E
1111 1001 (7) ancillary_stream
1111 1010 ISO/IEC14496-1_SL-packetized_stream
1111 1011 ISO/IEC14496-1_FlexMux_stream
1111 1100 metadata stream
1111 1101 reserved data stream
1111 1110 reserved data stream
1111 1111 (4) program_stream_directory
The notation x means that the values '0' or '1' are both permitted and results in the same stream type. The stream number is given
by the values taken by the x's.
NOTE 1 – PES packets of type program_stream_map have unique syntax specified in 2.5.4.1.
NOTE 2 – PES packets of type private_stream_1 and ISO/IEC_13552_stream follow the same PES packet syntax as those for
ITU-T Rec. H.262 | ISO/IEC 13818-2 video and ISO/IEC 13818-3 audio streams.
NOTE 3 – PES packets of type private_stream_2, ECM_stream and EMM_stream are similar to private_stream_1 except no
syntax is specified after PES_packet_length field.
NOTE 4 – PES packets of type program_stream_directory have a unique syntax specified in 2.5.5.
NOTE 5 – PES packets of type DSM-CC_stream have a unique syntax specified in ISO/IEC 13818-6.
NOTE 6 – This stream_id is associated with stream_type 0x09 in Table 2-29.
NOTE 7 – This stream_id is only used in PES packets, which carry data from a Program Stream or an ISO/IEC 11172-1 System
Stream, in a Transport Stream (refer to 2.4.3.7).

2 ITU-T Rec. H.222.0 (2000)/Amd.1 (12/2002)

ISO/IEC 13818-1:2000/Amd.1:2003 (E)
3) Table 2-26
Define a metadata_section tag by replacing Table 2-26 in clause 2:
Table 2-26 – table_id assignment values
Value Description
0x00 Program_association_section
0x01 Conditional_access_section (CA_section)
0x02 TS_program_map_section
0x03 TS_description_section
0x04 ISO_IEC_14496_scene_description_section
0x05 ISO_IEC_14496_object_descriptor_section
0x06 Metadata_section
0x07-0x37 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 Reserved
0x38-0x3F Defined in ISO/IEC 13818-6
0x40-0xFE User private
0xFF Forbidden
4) Table 2-29
Define tags for a metadata carried in PES packets, metadata_sections and DSM-CC by replacing Table 2-29 in
clause 2:
Table 2-29 – Stream type assignments
Value Description
0x00 ITU-T | ISO/IEC Reserved
0x01 ISO/IEC 11172 Video
ITU-T Rec. H.262 | ISO/IEC 13818-2 Video or ISO/IEC
0x02
11172-2 constrained parameter video stream
0x03 ISO/IEC 11172 Audio
0x04 ISO/IEC 13818-3 Audio
0x05 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 private_sections
0x06 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 PES packets
containing private data
0x07 ISO/IEC 13522 MHEG
0x08 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 Annex A DSM-CC
0x09 ITU-T Rec. H.222.1
0x0A ISO/IEC 13818-6 type A
0x0B ISO/IEC 13818-6 type B
0x0C ISO/IEC 13818-6 type C
0x0D ISO/IEC 13818-6 type D
0x0E ITU-T Rec. H.222.0 | ISO/IEC 13818-1 auxiliary
0x0F ISO/IEC 13818-7 Audio with ADTS transport syntax
0x10 ISO/IEC 14496-2 Visual
0x11 ISO/IEC 14496-3 Audio with the LATM transport syntax
as defined in ISO/IEC 14496-3/Amd.1
0x12 ISO/IEC 14496-1 SL-packetized stream or FlexMux stream
carried in PES packets
0x13 ISO/IEC 14496-1 SL-packetized stream or FlexMux stream
carried in ISO/IEC14496_sections.
0x14 ISO/IEC 13818-6 Synchronized Download Protocol
ITU-T Rec. H.222.0 (2000)/Amd.1 (12/2002) 3

ISO/IEC 13818-1:2000/Amd.1:2003 (E)
Table 2-29 – Stream type assignments
Value Description
0x15 Metadata carried in PES packets using the Metadata Access
Unit Wrapper defined in 2.12.4.1
0x16 Metadata carried in metadata_sections
0x17 Metadata carried in ISO/IEC 13818-6 (DSM-CC) Data
Carousel
0x18 Metadata carried in ISO/IEC 13818-6 (DSM-CC) Object
Carousel
0x19 Metadata carried in ISO/IEC 13818-6 Synchronized
Download Protocol using the Metadata Access Unit
Wrapper defined in 2.12.4.1
0x1A-0x7F ITU-T Rec. H.222.0 | ISO/IEC 13818-1 Reserved
0x80-0xFF User Private
5) Table 2-39
Define tags for a metadata related descriptors by replacing Table 2-39 in clause 2:
Table 2-39 – Program and program element descriptors
descriptor_tag TS PS Identification
0 n/a n/a Reserved
1 n/a n/a Reserved
2 X X video_stream_descriptor
3 X X audio_stream_descriptor
4 X X hierarchy_descriptor
5 X X registration_descriptor
6 X X data_stream_alignment_descriptor
7 X X target_background_grid_descriptor
8 X X Video_window_descriptor
9 X X CA_descriptor
10 X X ISO_639_language_descriptor
11 X X System_clock_descriptor
12 X X Multiplex_buffer_utilization_descriptor
13 X X Copyright_descriptor
14 X Maximum_bitrate_descriptor
15 X X Private_data_indicator_descriptor
16 X X Smoothing_buffer_descriptor
17 X STD_descriptor
18 X X IBP_descriptor
19-26 X Defined in ISO/IEC 13818-6
27 X X MPEG-4_video_descriptor
28 X X MPEG-4_audio_descriptor
29 X X IOD_descriptor
30 X SL_descriptor
31 X X FMC_descriptor
32 X X External_ES_ID_descriptor
33 X X MuxCode_descriptor
34 X X FmxBufferSize_descriptor
4 ITU-T Rec. H.222.0 (2000)/Amd.1 (12/2002)

ISO/IEC 13818-1:2000/Amd.1:2003 (E)
Table 2-39 – Program and program element descriptors
descriptor_tag TS PS Identification
35 X MultiplexBuffer_descriptor
36 X X Content_labeling_descriptor
37 X X Metadata_pointer_descriptor
38 X X Metadata_descriptor
39 X X Metadata_STD_descriptor
40-63 n/a n/a ITU-T Rec. H.222.0 | ISO/IEC 13818-1 Reserved
64-255 n/a n/a User Private
6) New subclauses after subclause 2.6.55
Add the following subclauses after subclause 2.6.55:
2.6.56 Content labelling descriptor
The content labelling descriptor assigns a label to content; the label can be used by metadata to reference the associated
content. This label, the content_reference_id_record, is metadata application format specific. The content labelling
descriptor is associated with a content segment. For the purpose of this clause, a content segment is defined as a portion
in time of a program, an elementary stream (such as audio or video) or any combination of programs or elementary
streams. The descriptor may be included in the PMT in the descriptor loop for either the program or an elementary
stream, but may also be contained in tables not defined in this Specification, for example tables to describe segments of
programs or elementary streams. The content labelling descriptor also provides information on which content time base
is used and on the offset between the content time base and the metadata time base. When the Normal Play Time (NPT)
concept of DSM-CC, as specified in IEC/ISO 13818-6, is used as the content time base, the ID of the NPT time base is
provided. The descriptor allows for carriage of private data.
ITU-T Rec. H.222.0 (2000)/Amd.1 (12/2002) 5

ISO/IEC 13818-1:2000/Amd.1:2003 (E)
Table Amd.1-1 – Content labelling descriptor
Syntax No. of bits Mnemonic
Content_labeling_descriptor () {
descriptor_tag 8 uimsbf
descriptor_length 8 uimsbf
metadata_application_format 16 uimsbf
if (metadata_application_format== 0xFFFF){
metadata_application_format_identifier 32 uimsbf
}
content_reference_id_record_flag 1 bslbf
content_time_base_indicator 4 uimsbf
reserved 3 bslbf
if (content_reference_id_record_flag == ‘1’){
content_reference_id_record_length 8 uimsbf
for (i=0; i content_reference_id_byte 8 bslbf
}
}
if (content_time_base_indicator== 1|2){
reserved 7 bslbf
content_time_base_value 33 uimsbf
reserved 7 bslbf
metadata_time_base_value 33 uimsbf
}
if (content_time_base_indicator== 2){
reserved 1 bslbf
contentId 7 uimsbf
}
if (content_time_base_indicator==3|4|5|6|7){
time_base_association_data_length 8 uimsbf
for (i=0; i< time_base_association_data_length;i++){
reserved 8 bslbf
}
}
for (i=0; i private_data_byte 8 bslbf
}
}
2.6.57 Semantic definition of fields in content labelling descriptor
metadata_application_format: The metadata_application_format is a 16-bit field, coded as defined in Table Amd.1-2,
that specifies the application responsible for defining usage, syntax and semantics of the content_reference_id record
and of any other privately defined fields in this descriptor. See also subclause 2.12.1. The value 0xFFFF indicates that
the format is signalled by the value carried in the metadata_application_format_identifier field.
Table Amd.1-2 – metadata_application_format
Value Description
0x0000-0x00FF Reserved
0x0100-0xFFFE User defined
0xFFFF Defined by the
metadata_application_format_identifier field

metadata_application_format_identifier: The coding of this 32-bit field is fully equivalent to the coding of the
format_identifier field in the registration_descriptor, as defined in subclause 2.6.8.
NOTE – The assigned Registration Authority for the format_identifier field is SMPTE.
content_reference_id_record_flag: The content_reference_id_record_flag is a 1-bit flag that signals the presence of a
content_reference_id_record in this descriptor.
content_time_base_indicator: The content_time_base_indicator is a 4-bit field which specifies the used content time
base. If the descriptor is associated with a program, then the content time base applies to all streams that are part of that
program. A value of 1 indicates usage of the STC, while a value of 2 indicates usage of NPT, the Normal Play Time as
defined in ISO/IEC 13818-6. The values between 8 and 15 indicate usage of a privately defined content time base. If
coded with a value of 0, no content time base is defined in this descriptor. If no content time base is specified for a
6 ITU-T Rec. H.222.0 (2000)/Amd.1 (12/2002)

ISO/IEC 13818-1:2000/Amd.1:2003 (E)
program or stream, then the mapping of time references in the metadata to the content is not defined in this
Specification.
Table Amd.1-3 – Content_time_base_indicator values
Value Description
0 No content time base defined in this descriptor
1 Use of STC
2 Use of NPT
3-7 Reserved
8-15 Use of privately defined content time base

content_reference_id_record_length: The content_reference_id_record_length is an 8-bit field that specifies the
number of content_reference_id_bytes immediately following this field. This field shall not be coded with the value 0.
content_reference_id_byte: The content_reference_id_byte is part of a string of one or more contiguous bytes that
assigns one or more reference identifications (labels) to the content to which this descriptor is associated. The format of
this byte string is defined by the body indicated by the coded value in the metadata_application_format field.
content_time_base_value: The content_time_base_value is a 33-bit field that specifies a value in units of 90 kHz of the
content time base indicated by the content_time_base_indicator field.
metadata_time_base_value: The metadata_time_base_value is a 33-bit field that is coded in units of 90 kHz. The field
is coded with the value of the metadata time base at the instant in time in which the time base indicated by
content_time_base_indicator reaches the value encoded in the content_time_base_value field. Note that the metadata
time base may use any time scale, but that its value is to be coded in units of 90 kHz. For example, if a SMPTE type of
time code is used, then the number of hours, minutes, seconds and frames is expressed in the corresponding number of
90 kHz units.
contentId: The contentId is a 7-bit field that specifies the value of the content_Id field in the NPT Reference Descriptor
for the applied NPT time base.
time_base_association_data_length: The time_base_association_data_length is an 8-bit field that specifies the number
of reserved bytes immediately following this field. The reserved bytes can be used to carry time base association data
for time bases defined in future.
private_data_byte: The private_data_byte is an 8-bit field. The private_data_bytes represent data, the format of which
is defined privately. These bytes can be used to provide additional information as deemed appropriate. The use of these
bytes is defined by the metadata application format.
2.6.58 Metadata pointer descriptor
The metadata pointer descriptor points to a single metadata service and associates this metadata service with
audiovisual content in an ITU-T Rec. H.222.0 | ISO/IEC 13818-1 stream. The metadata is associated with the content
within the context of the descriptor. The context is defined by the location of the descriptor. In a transport stream, the
descriptor may be located in the PMT in the descriptor loop for either the program or an elementary stream, but may
also be located in tables not defined in this Specification, such as tables describing bouquets of broadcast services. The
metadata may be located in an ITU-T Rec. H.222.0 | ISO/IEC 13818-1 stream, but the same metadata may also be
provided on alternative locations, such as the Internet.
The descriptor may contain location information of metadata that is not carried in an ITU-T Rec. H.222.0 | ISO/IEC
13818-1 stream; the coding of the location information is metadata application format specific. The descriptor allows
for carriage of private data.
For metadata carried in an ITU-T Rec. H.222.0 | ISO/IEC 13818-1 stream, the descriptor specifies the tools used for
such carriage. If the metadata is carried in PES packets, metadata sections, or ISO/IEC 13818-6 synchronized
download sections, the metadata_service_id field identifies the metadata service in the referenced metadata stream. If a
ISO/IEC 13818-6 carousel is used to carry the metadata, then the private data may provide information to signal the
metadata service, such as the applied value of the module_id for carriage of the metadata in a data carousel, and the file
name of the metadata when the object carousel is used.
Receivers should be aware that multiple metadata services may be pointed to from the same program or audiovisual
stream (as defined by the context of the descriptor). A unique metadata pointer descriptor shall be used to point to each
ITU-T Rec. H.222.0 (2000)/Amd.1 (12/2002) 7

ISO/IEC 13818-1:2000/Amd.1:2003 (E)
metadata service used by the program or audiovisual stream. Similarly, the same metadata service can be pointed to
from several programs or audiovisual streams by using a separate metadata pointer descriptors for each association.
Table Amd.1-4 – Metadata pointer descriptor
Syntax No. of bits Mnemonic
Metadata_pointer_descriptor () {
descriptor_tag 8 uimsbf
descriptor_length 8 uimsbf
metadata_application_format 16 uimsbf
if (metadata_application_format== 0xFFFF){
metadata_application_format_identifier 32 uimsbf
}
metadata_format 8 uimsbf
if (metadata_format== 0xFF){
metadata_format_identifier 32 uimsbf
}
metadata_service_id 8 uimsbf
metadata_locator_record_flag 1 bslbf
MPEG_carriage_flags 2 uimsbf
reserved 5 bslbf
if (metadata_locator_record_flag == ‘1’){
metadata_locator_record_length 8 uimsbf
for (i=0; i< metadata_locator_record_length;i++){
metadata_locator_record_byte 8 bslbf
}
}
if (MPEG_carriage_flags == 0|1|2){
program_number 16 uimsbf
}
if (MPEG_carriage_flags == 1){
transport_stream_location 16 uimsbf
transport_stream_id 16 uimsbf
}
for (i=0; i private_data_byte 8 bslbf
}
}
2.6.59 Semantic definition of fields in metadata pointer descriptor
metadata_application_format: The metadata_application_format is a 16-bit field that specifies the application
responsible for defining usage, syntax and semantics of the metadata_locator_record record and any other privately
defined fields in this descriptor. The coding of this field is defined in Table Amd.1-2 in subclause 2.6.57.
metadata_application_format_identifier: The coding of this field is defined in subclause 2.6.57.
metadata_format: The metadata_format is an 8-bit field that indicates the format and coding of the metadata. The
coding of this field is specified in Table Amd.1-5.
Table Amd.1-5 – Metadata format values
Value Description
0x00-0x0F Reserved
0x10 ISO/IEC 15938-1 TeM
0x11 ISO/IEC 15938-1 BiM
0x12-0x3E Reserved
0x3F Defined by metadata application format
0x40-0xFE Private use
0xFF Defined by metadata_format_identifier field

The values 0x10 and 0x11 identify ISO/IEC 15938-1 defined data. The value 0x3F indicates that the format is defined
by the body indicated by the metadata_application_format field. The values in the inclusive range of 0x40 up to 0xFE
8 ITU-T Rec. H.222.0 (2000)/Amd.1 (12/2002)

ISO/IEC 13818-1:2000/Amd.1:2003 (E)
are available to signal use of private formats. The value 0xFF indicates that the format is signalled by the
metadata_format_identifier field.
metadata_format_identifier: The coding of this 32-bit field is fully equivalent to the coding of the format_identifier
field in the registration_descriptor, as defined in subclause 2.6.8.
NOTE – SMPTE is assigned as Registration Authority for the format_identifier field.
metadata_service_id: This 8-bit field references the metadata service. It is used for retrieving a metadata service from
within a metadata stream.
metadata_locator_record_flag: The metadata_locator_record_flag is a 1-bit field which, when set to '1' indicates that
associated metadata is available on a location outside of an ITU-T Rec. H.222.0 | ISO/IEC 13818-1 stream, specified in
a metadata_locator_record.
MPEG_carriage_flags: The MPEG_carriage_flags is a 2-bit field which specifies if the metadata stream containing the
associated metadata service is carried in an ITU-T Rec. H.222.0 | ISO/IEC 13818-1 stream, and if so, whether the
associated metadata is carried in a Transport Stream or Program Stream. The coding of this field is defined in
Table Amd.1-6.
Table Amd.1-6 – MPEG_carriage_flags
Value Description
0 Carriage in the same Transport Stream where this metadata pointer descriptor is carried.
1 Carriage in a different Transport Stream from where this metadata pointer descriptor is
carried.
2 Carriage in a Program Stream. This may or may not be the same Program Stream in which
this metadata pointer descriptor is carried.
3 None of the above.
metadata_locator_record_length: The metadata_locator_record_length is an 8-bit field that specifies the number of
metadata_locator_record_bytes immediately following. This field shall not be coded with the value 0.
metadata_locator_record_byte: The metadata_locator_record_byte is part of a string of one or more contiguous bytes
that form the metadata locator record. This record specifies one or more locations outside of an ITU-T Rec. H.222.0 |
ISO/IEC 13818-1 stream. The format of the metadata locator record is defined by the metadata application signalled by
the metadata_application_format field. The record may for example contain Internet URLs that specify where the
metadata can be found, possibly in addition to their location(s) in the Transport Stream. If the MPEG_carriage_flags is
coded with the value 0, 1 or 2 and the metadata locator record is present, then this signals alternative locations for the
same metadata.
program_number: The program_number is a 16-bit field that identifies the program_number of the MPEG-2 program
in the ITU-T Rec. H.222.0 | ISO/IEC 13818-1 stream in which associated metadata is carried. If the
MPEG_carriage_flags have the value 0, then the transport stream is the current one, and if the MPEG_carriage_flags
have the value 1, it is the transport stream signalled by the fields transport_stream_location and transport_stream_id.
transport_stream_location: The transport_stream_location is a 16-bit field that is defined privately. For example, this
field may be used by applications to signal the original_network_id defined by ETSI.
transport_stream_id: The transport_stream_id is a 16-bit field that identifies the Transport Stream in which associated
metadata is carried.
private_data_byte: The private_data_byte is an 8-bit field. The private_data_bytes represent data, the format of which
is defined privately. These bytes can be used to provide additional information as deemed appropriate.
2.6.60 Metadata descriptor
The metadata descriptor specifies parameters of a metadata service carried in an MPEG-2 TS or PS. In an MPEG-2 TS,
the descriptor is included in the PMT in the descriptor loop for the elementary stream that carries the metadata service.
The descriptor specifies the format of the associated metadata, and contains the value of the metadata_service_id to
identify the metadata service to which the metadata descriptor applies. As needed, the descriptor can convey
information to identify the metadata service from a collection of metadata transmitted in a DSM-CC carousel.
Optionally metadata application format specific private data can be carried.
ITU-T Rec. H.222.0 (2000)/Amd.1 (12/2002) 9

ISO/IEC 13818-1:2000/Amd.1:2003 (E)
The metadata descriptor also signals whether decoder configuration is required and is able to carry the decoder
configuration bytes, but this is only practical if the number of these bytes is small. If the decoder configuration
information is too large to be carried by the descriptor, it shall be contained in a metadata service. This may be within
the metadata service itself, or in another metadata service within the same program. Identification of the metadata
service that contains the decoder configuration is provided by the metadata descriptor. If a DSM-CC carousel is used to
carry the decoder configuration, then information can be provided how to retrieve the decoder configuration from the
carousel.
Table Amd.1-7 – Metadata descriptor
Syntax No. of bits Mnemonic
Metadata_descriptor () {
descriptor_tag 8 uimsbf
descriptor_length 8 uimsbf
metadata_application_format 16 uimsbf
if (metadata_application_format == 0xFFFF) {
metadata_application_format_identifier 32 uimsbf
}
metadata_format 8 uimsbf
if (metadata_format== 0xFF){
metadata_format_identifier 32 uimsbf
}
metadata_service_id 8 uimsbf
decoder_config_flags 3 bslbf
DSM-CC_flag 1 bslbf
reserved 4 bslbf
if (DSM-CC_flag == ‘1’){
service_identification_length 8 uimsbf
for(i=0; i service_identification_record_byte 8 bslbf
}
}
if (decoder_config_flags == ‘001’) {
decoder_config_length 8 uimsbf
for(i=0; i decoder_config_byte 8 bslbf
}
}
if (decoder_config_flags == ‘011’) {
dec_config_identification_record_length 8 uimsbf
for(i=0;i dec_config_identification_record_byte 8 bslbf
}
}
if (decoder_config_flags == ‘100’) {
decoder_config_metadata_service_id 8 uimsbf
}
if (decoder_config_flags == ‘101’|’110’) {
reserved_data_length 8 uimsbf
for(i=0;i reserved 8 bslbf
}
}
for (i=0; i private_data_byte 8 bslbf
}
}
2.6.61 Semantic definition of fields in metadata descriptor
metadata_application_format: The metadata_application_format is a 16-bit field that specifies the application
responsible for defining usage, syntax and semantics of the service_identification_record and any privately defined
bytes in this descriptor. The coding of this field is defined in Table Amd.1-2 in subclause 2.6.57.
metadata_application_format_identifier: The coding of this field is defined in subclause 2.6.57.
metadata_format: The coding of this field is defined in subclause 2.6.59.
metadata_format_identifier: The coding of this field is defined in subclause 2.6.59.
10 ITU-T Rec. H.222.0 (2000)/Amd.1 (12/2002)

ISO/IEC 13818-1:2000/Amd.1:2003 (E)
metadata_service_id. This 8-bit field identifies the metadata service to which this metadata descriptor applies.
decoder_config_flags: The decoder_config_flags is a 3-bit field which indicates whether and how decoder
configuration information is conveyed.
Table Amd.1-8 – decoder_config_flags
Value Description
000 No decoder configuration is needed.
001 The decoder configuration is carried in this descriptor in the decoder_config_byte field.
010 The decoder configuration is carried in the same metadata service as to which this
metadata descriptor applies.
011 The decoder configuration is carried in a DSM-CC carousel. This value shall only be
used if the metadata service to which this descriptor applies is using the same type of
DSM-CC carousel.
100 The decoder configuration is carried in another metadata service within the same
program, as identified by the decoder_config_metadata_service_id field in this
metadata descriptor.
101, 110 Reserved.
111 Privately defined.
DSM-CC_flag: This is a one-bit flag that is set to '1' if the stream with which this descriptor is associated is carried in
an ISO/IEC 13818-6 data or object carousel.
NOTE 1 – The use of the object or data carousel is indicated by the applied stream-type value for this metadata stream.
service_identification length: This field specifies the number of service_identification_record_bytes immediately
following.
service_identification_record_byte: This byte is part of a string of one or more contiguous bytes that specify the
service_identification_record. This record contains data on retrieval of the metadata service from a DSM-CC carousel.
The format of the metadata locator record is defined by the application indicated by the metadata application format.
When a DSM-CC object carousel is used, the record may for example comprise the unique object identifier (the
IOP:IOR() from ISO/IEC 13818-6 DSM-CC, subclauses 11.3.1 and 5.7.2.3) for the metadata service. Similarly, in case
of a DSM-CC data carousel, the record can for example provide the transaction_id and the module_id of the metadata
service.
decoder_config_length: This field specifies the number of decoder_config_bytes immediately following.
decoder_config_byte: These bytes comprise the decoder configuration information. This sequence of bytes comprises
the configuration information needed by the receiver to decode this service. It is intended that carriage in the metadata
descriptor is only used when the configuration information is very small.
decoder_config_DSM-CC_id: This is the download identifier of the decoder configuration information when it is
transmitted in a DSM-CC data carousel, or the object identifier of the decoder configuration information if it is carried
in a DSM-CC object carousel.
NOTE 2 – The use of the object or data carousel is indicated by the applied stream-type value for this metadata stream.
dec_config_identification_record_length: This field specifies the immediately following number of
dec_config_identification_record_bytes.
dec_config_identification_record_byte: This byte is part of a string of one or more contiguous bytes that specify the
dec_config_identification_record. This record specifies how to retrieve the required decoder configuration from a
DSM-CC carousel. The format of the metadata locator record is defined by the metadata application format. When a
DSM-CC object carousel is used, the record may for example comprise the unique object identifier (the IOP:IOR() from
ISO/IEC 13818-6 DSM-CC, subclauses 11.3.1 and 5.7.2.3) for the decoder configuration. Similarly, in case of a DSM-
CC data carousel, the record may for example provide the transaction_id and the module_id of the decoder
configuration.
decoder_config_metadata_service_id: This is the value of the metadata_service_id that is assigned to the metadata
service that contains the decoder configuration. The metadata service indicated by the
decoder_config_metadata_service_id and the metadata service that uses that decoder configuration shall be in the same
program. Hence in a Transport Stream, the metadata descriptors for both these metadata services shall be in the same
ITU-T Rec. H.222.0 (2000)/Amd.1 (12/2002) 11

ISO/IEC 13818-1:2000/Amd.1:2003 (E)
PMT. The metadata descriptor of the metadata service indicated by the decoder_config_metadata_service_id shall have
a decoder_config_flag field with a value of either '001', '010' or '011'.
reserved_data_length: This field specifies the number of reserved bytes immediately following.
private_data_byte: The private_data_byte is an 8-bit field. The private_data_bytes represent data, the format of which
is defined privately. These bytes can be used to provide additional information as deemed appropriate.
2.6.62 Metadata STD descriptor
This descriptor defines parameters of the STD model (defined in 2.12.10) for the processing of the metadata stream to
which this descriptor is associated.
Table Amd.1-9 – Metadata STD descriptor
Syntax No. of bits Mnemonic
Metadata_STD_descriptor () {
descriptor_tag 8 uimsbf
descriptor_length 8 uimsbf
reserved 2 bslbf
metadata_input_leak_rate 22 uimsbf
reserved 2 bslbf
metadata_buffer_size 22 uimsbf
reserved 2 bslbf
metadata_output_leak_rate 22 uimsbf
}
2.6.63 Semantic definition of fields in metadata STD descriptor
metadata_input_leak_rate: The metadata_input_leak_rate is a 22-bit field that specifies the leak rate for the associated
metadata stream in the T-STD model out of the buffer TB into buffer B . The leak rate is specified in units of
n n
400 bits/s. For metadata carried in a program stream, the coding of the metadata_input_leak_rate field is not specified,
as the rate into B equals the rate of the program stream.
n
metadata_buffer_size: The metadata_buffer_size is a 22-bit field that specifies the size of buffer B in the STD model
n
for the associated metadata stream. The size of B is specified in units of 1024 bytes.
n
metadata_output_leak_rate: The metadata_output_leak_rate is a 22-bit field that specifies for the associated metadata
service the leak rate in the STD model out of buffer B to the decoder. The leak rate is specified in units of 400 bits/s.
n
For metadata streams transported synchronously (stream-type 0x15 or 0x19), the metadata access units are
instantaneously removed from B under the control of PTS timestamps and in that case the coding of the
n
metadata_output_leak_rate field is not specified .
7) New subclauses after subclause 2.11
Add subclause 2.12 immediately after subclause 2.11:
2.12 Carriage of Metadata
2.12.1 Introduction
An ITU-T Rec. H.222.0 | ISO/IEC 13818-1 stream can carry metadata. The format of the metadata may be defined by
ISO or by any other authority. This subclause defines how to carry the metadata; transport mechanisms are defined as
well as metadata related signalling, the applied metadata timing model and extensions of the STD model for decoding
of metadata.
A metadata service is defined to be a coherent set of metadata of the same format delivered to a receiver for a specific
purpose. Metadata services are contained in metadata streams; each metadata stream carries one or more metadata
services. This Specification assumes the notion of metadata Access Units within a metadata service. The definition of a
Metadata Access Unit is metadata format specific, but each metadata service is assumed to represent a concatenation (or
a collection) of metadata Access Units.
When transporting a metadata service over an ITU-T Rec. H.222.0 | ISO/IEC 13818-1 stream, a unique metadata
service id is assigned to each such service. A metadata service id references uniquely a metadata service among all the
12 ITU-T Rec. H.222.0 (2000)/Amd.1 (12/2002)

ISO/IEC 13818-1:2000/Amd.1:2003 (E)
metadata services available on the same Transport or Program Stream, and not unique solely within a metadata stream.
The metadata service identifier is used to retrieve the metadata service and all the information needed to decode it.
Decoding of metadata may require the availability of decoder configuration data. If a metadata service carried in an
ITU-T Rec. H.222.0 | ISO/IEC 13818-1 stream requires decoder configuration data for decoding, then this metadata
decoder configuration data shall be carried within the same program of the same ITU-T Rec. H.222.0 |
ISO/IEC 13818-1 stream.
Subclause 2.12.2 discusses metadata timing, while subclause 2.12.3 provides an overview of tools that are defined for
transport of metadata over an ITU-T Rec. H.222.0 | ISO/IEC 13818-1 stream. The use of available transport tools is
specified in 2.12.4 up to 2.12.8, and subclause 2.12.9 specifies metadata related signalling. Finally, the STD model for
metadata decoding is specified in 2.12.10.
Since many forms of metadata may be carried, it is essential to signal both the precise format and encoding of the
metadata, and the semantic meaning the metadata conveys. The former is signalled by the metadata format, while the
latter is signalled by the metadata application format. In other words, the metadata format conveys how the metadata
shall be decoded, while the metadata application format conveys how to use the metadata, essentially which application
uses the metadata. This division is important since it separates the encoding or representation of the metadata from its
meaning, thereby allowing an application to be agnostic of the means by which its metadata is conveyed.
2.12.2 Metadata time-line model
Metadata may refer to time codes associated to the content, for example to indicate the beginning of a content segment.
Each time indication made in the metadata refers to a certain metadata content time line specific to the actual metadata
format and/or metadata application format. For example, one metadata (application) format may use UTC, while
another metadata application format may use SMPTE time codes. To allow for transport of the content at any time over
any media, the metadata content time line is expected but not required to be transport agnostic.
When transporting content and the associated metadata over ITU-T Rec. H.222.0 | ISO/IEC 13818-1 streams, accurate
time references from the metadata to the content are to be maintained. The same is needed if the metadata is delivered
over other means. To achieve this, the time line model of Figure Amd.1-1 is assumed in this Specification.
Content time line as
Metadata timing,
specified in the
transport agnostic
MT
Metadata (format is
metadata specific:
A/V Content
UTC, SMPTE, …)
production
transport
A/V Content (1)
A/V Content (2)
Delivery time
line (STC)
Receiver Content
RT
time line (single
format)
H.222.0_FAMD1-1
Figure Amd.1-1 – Timing model for delivery of content and metadata
Metadata is associated to the audiovisual content, usually in a transport agnostic way, at production or any other stage
prior to transport. Where needed, time information is embedded in the metadata to indicate for example specific
segments within the content, using the metadata content time line used in the metadata. For example UTC or SMPTE
time codes may be used. The time line format is independent of any time code that may or may not be embedded in the
audiovisual stream itself. For example, the metadata time line may utilize UTC, while SMPTE time codes are
embedded in the video stream.
The following requirements shall be met for each metadata stream:
• no time discontinuities shall occur in the metadata content time line;
• the metadata content time line shall be locked to the sampling clock of the content;
• each time reference in the metadata stream refers to the same metadata content time line.
At transport, a transport specific timing is associated with the content; this is the delivery time line. In the case of
transport over an ITU-T Rec. H.222.0 | ISO/IEC 13818-1 stream, the delivery time line is provided by the System Time
Clock, the STC. The content may be delivered as a contiguous piece of information, but it is also possible to interrupt
ITU-T Rec. H.222.0 (2000)/Amd.1 (12/2002) 13

ISO/IEC 13818-1:2000/Amd.1:2003 (E)
the delivery of the content, for example in the case of news-flash interruptions of a program; in such and other cases
time line discontinuities may occur.
When time references are used in the metadata, in the System Target Decoder (STD) these time references are to be
associated unambiguously with time values in the received content. To achieve this, a receiver content time line is
required. The STC can be used as the receiver content time line, but due to STC discontinuities that may occur, the STC
does not necessarily offer an unambiguous time association. Therefore the NPT (Normal Play Time) concept from
ISO/IEC 13818-6 DSM-CC is also available for use as the receiver content time line. In any playback mode, such as
normal, reverse, slow motion, fast forward, fast backward and still picture, the NPT provides an unambiguous time
association, independent of STC discontinuities, and independent of insertions of other content. Note that a new
NPT_reference_descriptor needs to be transmitted when the STC rolls over.
To maintain the accurate time references from metadata to the content, information is needed how to map a metadata
time, MT, defined on the metadata content time line to the corresponding receiver time, RT, of the receiver content time
line. This is achieved by providing the offset in time (in 90 kHz units) between the metadata content time line and the
receiver content time line. The offset is provided in the content labelling descriptor. The offset conveys the value of the
metadata time base at the instant in time at which the
...