SIST ISO/IEC 13818-1:2010

SLOVENSKI STANDARD
SIST ISO/IEC 13818-1:2010
01-oktober-2010
1DGRPHãþD
SIST ISO/IEC 13818-1:2005
,QIRUPDFLMVNDWHKQRORJLMD6SORãQRNRGLUDQMHJLEOMLYLKVOLNLQSULSDGDMRþLKDYGLR
LQIRUPDFLM6LVWHPL
Information technology - Generic coding of moving pictures and associated audio
information: Systems
Technologies de l'information - Codage générique des images animées et du son
associé: Systèmes
Ta slovenski standard je istoveten z: ISO/IEC 13818-1:2007
ICS:
35.040 Nabori znakov in kodiranje Character sets and
informacij information coding
SIST ISO/IEC 13818-1:2010 en,fr
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ISO/IEC 13818-1:2010

---------------------- Page: 2 ----------------------

SIST ISO/IEC 13818-1:2010

INTERNATIONAL ISO/IEC
STANDARD 13818-1
Third edition
2007-10-15

Information technology — Generic coding
of moving pictures and associated audio
information: Systems
Technologies de l'information — Codage générique des images
animées et des informations sonores associées: Systèmes




Reference number
ISO/IEC 13818-1:2007(E)
©
ISO/IEC 2007

---------------------- Page: 3 ----------------------

SIST ISO/IEC 13818-1:2010
ISO/IEC 13818-1:2007(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.


COPYRIGHT PROTECTED DOCUMENT


©  ISO/IEC 2007
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 2007 – All rights reserved

---------------------- Page: 4 ----------------------

SIST ISO/IEC 13818-1:2010
ISO/IEC 13818-1:2007(E)

CONTENTS
Page
SECTION 1 – GENERAL . 1
1.1 Scope. 1
1.2 Normative references. 1

SECTION 2 – TECHNICAL ELEMENTS. 2
2.1 Definitions. 2
2.2 Symbols and abbreviations. 6
2.3 Method of describing bit stream syntax . 7
2.4 Transport Stream bitstream requirements. 8
2.5 Program Stream bitstream requirements . 51
2.6 Program and program element descriptors. 63
2.7 Restrictions on the multiplexed stream semantics . 94
2.8 Compatibility with ISO/IEC 11172. 98
2.9 Registration of copyright identifiers. 98
2.10 Registration of private data format. 99
2.11 Carriage of ISO/IEC 14496 data. 99
2.12 Carriage of metadata. 111
2.13 Carriage of ISO 15938 data. 120
2.14 Carriage of ITU-T Rec. H.264 | ISO/IEC 14496-10 video . 120
Annex A – CRC decoder model . 124
A.0 CRC decoder model . 124
Annex B – Digital Storage Medium Command and Control (DSM-CC). 125
B.0 Introduction . 125
B.1 General elements . 126
B.2 Technical elements. 128
Annex C – Program Specific Information . 133
C.0 Explanation of Program Specific Information in Transport Streams . 133
C.1 Introduction . 133
C.2 Functional mechanism . 134
C.3 The Mapping of Sections into Transport Stream Packets. 135
C.4 Repetition rates and random access. 135
C.5 What is a program?. 135
C.6 Allocation of program_number . 136
C.7 Usage of PSI in a typical system . 136
C.8 The relationships of PSI structures. 137
C.9 Bandwidth utilization and signal acquisition time . 139
Annex D – Systems timing model and application implications of this Recommendation | International
Standard. 141
D.0 Introduction . 141
Annex E – Data transmission applications. 149
E.0 General considerations . 149
E.1 Suggestion. 150
Annex F – Graphics of syntax for this Recommendation | International Standard. 151
F.0 Introduction . 151
Annex G – General information . 156
G.0 General information. 156
Annex H – Private data . 157
H.0 Private data. 157
Annex I – Systems conformance and real-time interface . 158
I.0 Systems conformance and real-time interface . 158
© ISO/IEC 2007 – All rights reserved iii

---------------------- Page: 5 ----------------------

SIST ISO/IEC 13818-1:2010
ISO/IEC 13818-1:2007(E)
Page

Annex J – Interfacing jitter-inducing networks to MPEG-2 decoders. 158
J.0 Introduction . 158
J.1 Network compliance models . 159
J.2 Network specification for jitter smoothing . 159
J.3 Example decoder implementations . 160
Annex K – Splicing Transport Streams. 161
K.0 Introduction . 161
K.1 The different types of splicing point. 162
K.2 Decoder behaviour on splices . 162
Annex L – Registration procedure (see 2.9). 164
L.1 Procedure for the request of a Registered Identifier (RID) . 164
L.2 Responsibilities of the Registration Authority. 164
L.3 Responsibilities of parties requesting an RID. 164
L.4 Appeal procedure for denied applications. 165
Annex M – Registration application form (see 2.9). 165
M.1 Contact information of organization requesting a Registered Identifier (RID). 165
M.2 Statement of an intention to apply the assigned RID. 165
M.3 Date of intended implementation of the RID. 165
M.4 Authorized representative . 165
M.5 For official use only of the Registration Authority . 166
Annex N . 166
Annex O – Registration procedure (see 2.10). 167
O.1 Procedure for the request of an RID. 167
O.2 Responsibilities of the Registration Authority. 167
O.3 Contact information for the Registration Authority . 167
O.4 Responsibilities of parties requesting an RID. 167
O.5 Appeal procedure for denied applications. 167
Annex P – Registration application form . 168
P.1 Contact information of organization requesting an RID . 168
P.2 Request for a specific RID . 168
P.3 Short description of RID that is in use and date system that was implemented. 168
P.4 Statement of an intention to apply the assigned RID. 168
P.5 Date of intended implementation of the RID. 168
P.6 Authorized representative . 168
P.7 For official use of the Registration Authority. 168
Annex Q – T-STD and P-STD buffer models for ISO/IEC 13818-7 ADTS. 169
Q.1 Introduction . 169
Q.2 Leak rate from Transport Buffer. 169
Q.3 Buffer size. 169
Q.4 Conclusion. 171
Annex R – Carriage of ISO/IEC 14496 scenes in ITU-T Rec. H.222.0 | ISO/IEC 13818- . 172
R.1 Content access procedure for ISO/IEC 14496 program components within a Program Stream. 172
R.2 Content access procedure for ISO/IEC 14496 program components within a Transport
Stream . 173

iv © ISO/IEC 2007 – All rights reserved

---------------------- Page: 6 ----------------------

SIST ISO/IEC 13818-1:2010
ISO/IEC 13818-1:2007(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.
ISO/IEC 13818-1 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 (05/2006).
This third edition cancels and replaces the second edition (ISO/IEC 13818-1:2000), which has been
technically revised. It also incorporates the Amendments ISO/IEC 13818-1:2000/Amd.1:2003,
ISO/IEC 13818-1:2000/Amd.2:2004, ISO/IEC 13818-1:2000/Amd.3:2004, ISO/IEC 13818-1:2000/Amd.4:2005
and ISO/IEC 13818-1:2000/Amd.5:2005, and the Technical Corrigenda ISO/IEC 13818-1:2000/Cor.1:2002,
ISO/IEC 13818-1:2000/Cor.2:2002, ISO/IEC 13818-1:2000/Cor.3:2005, ISO/IEC 13818-1:2000/Cor.4:2007.
ISO/IEC 13818 consists of the following parts, under the general title Information technology — Generic
coding of moving pictures and associated audio information:
⎯ Part 1: Systems
⎯ Part 2: Video
⎯ Part 3: Audio
⎯ Part 4: Conformance testing
⎯ Part 5: Software simulation [Technical Report]
⎯ Part 6: Extensions for DSM-CC
⎯ Part 7: Advanced Audio Coding (AAC)
⎯ Part 9: Extension for real time interface for systems decoders
⎯ Part 10: Conformance extensions for Digital Storage Media Command and Control (DSM-CC)
⎯ Part 11: IPMP on MPEG-2 systems

© ISO/IEC 2007 – All rights reserved v

---------------------- Page: 7 ----------------------

SIST ISO/IEC 13818-1:2010
ISO/IEC 13818-1:2007(E)
Introduction
The systems part of this Recommendation | International Standard addresses the combining of one or more elementary
streams of video and audio, as well as other data, into single or multiple streams which are suitable for storage or
transmission. Systems coding follows the syntactical and semantic rules imposed by this Specification and provides
information to enable synchronized decoding of decoder buffers over a wide range of retrieval or receipt conditions.

System coding shall be specified in two forms: the Transport Stream and the Program Stream. Each is optimized for
a different set of applications. Both the Transport Stream and Program Stream defined in this Recommendation |
International Standard provide coding syntax which is necessary and sufficient to synchronize the decoding and
presentation of the video and audio information, while ensuring that data buffers in the decoders do not overflow or
underflow. Information is coded in the syntax using time stamps concerning the decoding and presentation of coded
audio and visual data and time stamps concerning the delivery of the data stream itself. Both stream definitions are
packet-oriented multiplexes.
The basic multiplexing approach for single video and audio elementary streams is illustrated in Figure Intro. 1. The
video and audio data is encoded as described in ITU-T Rec. H.262 | ISO/IEC 13818-2 and ISO/IEC 13818-3. The
resulting compressed elementary streams are packetized to produce PES packets. Information needed to use PES
packets independently of either Transport Streams or Program Streams may be added when PES packets are formed.
This information is not needed and need not be added when PES packets are further combined with system level
information to form Transport Streams or Program Streams. This systems standard covers those processes to the
right of the vertical dashed line.
Video PES
Video Video
Packetizer
data encoder
PS
Program
Stream
mux
Audio PES
Audio Audio
Packetizer
data encoder
TS
Transport
Stream
mux
Extent of systems specification
TISO5760-95/d01
Figure Intro. 1 – Simplified overview of the scope of this Recommendation | International Standard

The Program Stream is analogous and similar to ISO/IEC 11172 Systems layer. It results from combining one or more
streams of PES packets, which have a common time base, into a single stream.
For applications that require the elementary streams which comprise a single program to be in separate streams which
are not multiplexed, the elementary streams can also be encoded as separate Program Streams, one per elementary
stream, with a common time base. In this case the values encoded in the SCR fields of the various streams shall be
consistent.
Like the single Program Stream, all elementary streams can be decoded with synchronization.
The Program Stream is designed for use in relatively error-free environments and is suitable for applications which may
involve software processing of system information such as interactive multi-media applications. Program Stream
packets may be of variable and relatively great length.
The Transport Stream combines one or more programs with one or more independent time bases into a single stream.
PES packets made up of elementary streams that form a program share a common timebase. The Transport Stream is
designed for use in environments where errors are likely, such as storage or transmission in lossy or noisy media.
Transport Stream packets are 188 bytes in length.
vi © ISO/IEC 2007 – All rights reserved

---------------------- Page: 8 ----------------------

SIST ISO/IEC 13818-1:2010
ISO/IEC 13818-1:2007(E)

Program and Transport Streams are designed for different applications and their definitions do not strictly follow a
layered model. It is possible and reasonable to convert from one to the other; however, one is not a subset or superset of
the other. In particular, extracting the contents of a program from a Transport Stream and creating a valid Program
Stream is possible and is accomplished through the common interchange format of PES packets, but not all of the fields
needed in a Program Stream are contained within the Transport Stream; some must be derived. The Transport Stream
may be used to span a range of layers in a layered model, and is designed for efficiency and ease of implementation in
high bandwidth applications.
The scope of syntactical and semantic rules set forth in the systems specification differ: the syntactical rules apply to
systems layer coding only, and do not extend to the compression layer coding of the video and audio specifications; by
contrast, the semantic rules apply to the combined stream in its entirety.
The systems specification does not specify the architecture or implementation of encoders or decoders, nor those of
multiplexors or demultiplexors. However, bit stream properties do impose functional and performance requirements on
encoders, decoders, multiplexors and demultiplexors. For instance, encoders must meet minimum clock tolerance
requirements. Notwithstanding this and other requirements, a considerable degree of freedom exists in the design and
implementation of encoders, decoders, multiplexors, and demultiplexors.
Intro. 1  Transport Stream
The Transport Stream is a stream definition which is tailored for communicating or storing one or more programs of
coded data according to ITU-T Rec. H.262 | ISO/IEC 13818-2 and ISO/IEC 13818-3 and other data in environments in
which significant errors may occur. Such errors may be manifested as bit value errors or loss of packets.
Transport Streams may be either fixed or variable rate. In either case the constituent elementary streams may either be
fixed or variable rate. The syntax and semantic constraints on the stream are identical in each of these cases. The
Transport Stream rate is defined by the values and locations of Program Clock Reference (PCR) fields, which in general
are separate PCR fields for each program.
There are some difficulties with constructing and delivering a Transport Stream containing multiple programs with
independent time bases such that the overall bit rate is variable. Refer to 2.4.2.2.
The Transport Stream may be constructed by any method that results in a valid stream. It is possible to construct
Transport Streams containing one or more programs from elementary coded data streams, from Program Streams, or
from other Transport Streams which may themselves contain one or more programs.
The Transport Stream is designed in such a way that several operations on a Transport Stream are possible with
minimum effort. Among these are:
1) Retrieve the coded data from one program within the Transport Stream, decode it and present the
decoded results as shown in Figure Intro. 2.
2) Extract the Transport Stream packets from one program within the Transport Stream and produce as
output a different Transport Stream with only that one program as shown in Figure Intro. 3.
3) Extract the Transport Stream packets of one or more programs from one or more Transport Streams and
produce as output a different Transport Stream (not illustrated).
4) Extract the contents of one program from the Transport Stream and produce as output a Program Stream
containing that one program as shown in Figure Intro. 4.
5) Take a Program Stream, convert it into a Transport Stream to carry it over a lossy environment, and then
recover a valid, and in certain cases, identical Program Stream.
Figure Intro. 2 and Figure Intro. 3 illustrate prototypical demultiplexing and decoding systems which take as input a
Transport Stream. Figure Intro. 2 illustrates the first case, where a Transport Stream is directly demultiplexed and
decoded. Transport Streams are constructed in two layers:
– a system layer; and
– a compression layer.
The input stream to the Transport Stream decoder has a system layer wrapped about a compression layer. Input streams
to the Video and Audio decoders have only the compression layer.
Operations performed by the prototypical decoder which accepts Transport Streams either apply to the entire Transport
Stream ("multiplex-wide operations"), or to individual elementary streams ("stream-specific operations"). The
Transport Stream system layer is divided into two sub-layers, one for multiplex-wide operations (the Transport Stream
packet layer), and one for stream-specific operations (the PES packet layer).
A prototypical decoder for Transport Streams, including audio and video, is also depicted in Figure Intro. 2 to illustrate
the function of a decoder. The architecture is not unique – some system decoder functions, such as decoder timing
© ISO/IEC 2007 – All rights reserved vii

---------------------- Page: 9 ----------------------

SIST ISO/IEC 13818-1:2010
ISO/IEC 13818-1:2007(E)

control, might equally well be distributed among elementary stream decoders and the channel-specific decoder – but
this figure is useful for discussion. Likewise, indication of errors detected by the channel-specific decoder to the
individual audio and video decoders may be performed in various ways and such communication paths are not shown in
the diagram. The prototypical decoder design does not imply any normative requirement for the design of a Transport
Stream decoder. Indeed non-audio/video data is also allowed, but not shown.
Video Decoded
decoder video
Transport Stream
Channel Channel specific Clock
demultiplex
decoder control
and decoder
Transport Stream Audio Decoded
containing one or multiple programs decoder audio
TISO5770-95/d02
Figure Intro. 2 – Prototypical transport demultiplexing and decoding example

Figure Intro. 3 illustrates the second case, where a Transport Stream containing multiple programs is converted into a
Transport Stream containing a single program. In this case the re-multiplexing operation may necessitate the correction
of Program Clock Reference (PCR) values to account for changes in the PCR locations in the bit stream.
Transport Stream
Channel Channel specific
demultiplex
decoder
and decoder
TISO5780-95/d03
Transport Stream Transport Stream
containing multiple programs with single program
Figure Intro. 3 – Prototypical transport multiplexing example

Figure Intro. 4 illustrates a case in which a multi-program Transport Stream is first demultiplexed and then converted
into a Program Stream.
Figures Intro. 3 and Intro. 4 indicate that it is possible and reasonable to convert between different types and
configurations of Transport Streams. There are specific fields defined in the Transport Stream and Program Stream
syntax which facilitate the conversions illustrated. There is no requirement that specific implementations of
demultiplexors or decoders include all of these functions.
Transport Stream
Channel
Channel specific demultiplex and
decoder Program Stream
multiplexor
TISO5790-95/d04
Transport Stream
Program Stream
containing multiple programs
Figure Intro. 4 – Prototypical Transport Stream to Program Stream conversion

Intro. 2  Program Stream
The Program Stream is a stream definition which is tailored for communicating or storing one program of coded data
and other data in environments where errors are very unlikely, and where processing of system coding, e.g., by
software, is a major consideration.
viii © ISO/IEC 2007 – All rights reserved

---------------------- Page: 10 ----------------------

SIST ISO/IEC 13818-1:2010
ISO/IEC 13818-1:2007(E)

Program Streams may be either fixed or variable rate. In either case, the constituent elementary streams may be either
fixed or variable rate. The syntax and semantics constraints on the stream are identical
...

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Technologies de l'information - Codage générique des images animées et du son associé: SystèmesInformation technology - Generic coding of moving pictures and associated audio information: Systems35.040Nabori znakov in kodiranje informacijCharacter sets and information codingICS:Ta slovenski standard je istoveten z:ISO/IEC 13818-1:2007oSIST ISO/IEC 13818-1:2010en,fr01-julij-2010oSIST ISO/IEC 13818-1:2010SLOVENSKI
STANDARD



oSIST ISO/IEC 13818-1:2010



Reference numberISO/IEC 13818-1:2007(E)© ISO/IEC 2007
INTERNATIONAL STANDARD ISO/IEC13818-1Third edition2007-10-15Information technology — Generic coding of moving pictures and associated audio information: Systems Technologies de l'information — Codage générique des images animées et des informations sonores associées: Systèmes
oSIST ISO/IEC 13818-1:2010



ISO/IEC 13818-1:2007(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.
COPYRIGHT PROTECTED DOCUMENT
©
ISO/IEC 2007 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 2007 – All rights reserved
oSIST ISO/IEC 13818-1:2010



ISO/IEC 13818-1:2007(E) © ISO/IEC 2007 – All rights reserved
iii
CONTENTS
Page SECTION 1 – GENERAL. 1 1.1 Scope. 1 1.2 Normative references. 1 SECTION 2 – TECHNICAL ELEMENTS. 2 2.1 Definitions. 2 2.2 Symbols and abbreviations. 6 2.3 Method of describing bit stream syntax. 7 2.4 Transport Stream bitstream requirements. 8 2.5 Program Stream bitstream requirements. 51 2.6 Program and program element descriptors. 63 2.7 Restrictions on the multiplexed stream semantics. 94 2.8 Compatibility with ISO/IEC 11172. 98 2.9 Registration of copyright identifiers. 98 2.10 Registration of private data format. 99 2.11 Carriage of ISO/IEC 14496 data. 99 2.12 Carriage of metadata. 111 2.13 Carriage of ISO 15938 data. 120 2.14 Carriage of ITU-T Rec. H.264 | ISO/IEC 14496-10 video. 120 Annex A – CRC decoder model . 124 A.0 CRC decoder model. 124 Annex B – Digital Storage Medium Command and Control (DSM-CC). 125 B.0 Introduction. 125 B.1 General elements. 126 B.2 Technical elements. 128 Annex C – Program Specific Information. 133 C.0 Explanation of Program Specific Information in Transport Streams. 133 C.1 Introduction. 133 C.2 Functional mechanism. 134 C.3 The Mapping of Sections into Transport Stream Packets. 135 C.4 Repetition rates and random access. 135 C.5 What is a program?. 135 C.6 Allocation of program_number. 136 C.7 Usage of PSI in a typical system. 136 C.8 The relationships of PSI structures. 137 C.9 Bandwidth utilization and signal acquisition time. 139 Annex D – Systems timing model and application implications of this Recommendation | International Standard. 141 D.0 Introduction. 141 Annex E – Data transmission applications. 149 E.0 General considerations. 149 E.1 Suggestion. 150 Annex F – Graphics of syntax for this Recommendation | International Standard. 151 F.0 Introduction. 151 Annex G – General information. 156 G.0 General information. 156 Annex H – Private data. 157 H.0 Private data. 157 Annex I – Systems conformance and real-time interface . 158 I.0 Systems conformance and real-time interface. 158 oSIST ISO/IEC 13818-1:2010



ISO/IEC 13818-1:2007(E) iv
© ISO/IEC 2007 – All rights reserved
Page Annex J – Interfacing jitter-inducing networks to MPEG-2 decoders. 158 J.0 Introduction. 158 J.1 Network compliance models. 159 J.2 Network specification for jitter smoothing. 159 J.3 Example decoder implementations. 160 Annex K – Splicing Transport Streams. 161 K.0 Introduction. 161 K.1 The different types of splicing point. 162 K.2 Decoder behaviour on splices. 162 Annex L – Registration procedure (see 2.9). 164 L.1 Procedure for the request of a Registered Identifier (RID). 164 L.2 Responsibilities of the Registration Authority. 164 L.3 Responsibilities of parties requesting an RID. 164 L.4 Appeal procedure for denied applications. 165 Annex M – Registration application form (see 2.9). 165 M.1 Contact information of organization requesting a Registered Identifier (RID). 165 M.2 Statement of an intention to apply the assigned RID. 165 M.3 Date of intended implementation of the RID. 165 M.4 Authorized representative. 165 M.5 For official use only of the Registration Authority. 166 Annex N . 166 Annex O – Registration procedure (see 2.10). 167 O.1 Procedure for the request of an RID. 167 O.2 Responsibilities of the Registration Authority. 167 O.3 Contact information for the Registration Authority. 167 O.4 Responsibilities of parties requesting an RID. 167 O.5 Appeal procedure for denied applications. 167 Annex P – Registration application form. 168 P.1 Contact information of organization requesting an RID. 168 P.2 Request for a specific RID. 168 P.3 Short description of RID that is in use and date system that was implemented. 168 P.4 Statement of an intention to apply the assigned RID. 168 P.5 Date of intended implementation of the RID. 168 P.6 Authorized representative. 168 P.7 For official use of the Registration Authority. 168 Annex Q – T-STD and P-STD buffer models for ISO/IEC 13818-7 ADTS. 169 Q.1 Introduction. 169 Q.2 Leak rate from Transport Buffer. 169 Q.3 Buffer size. 169 Q.4 Conclusion. 171 Annex R – Carriage of ISO/IEC 14496 scenes in ITU-T Rec. H.222.0 | ISO/IEC 13818-. 172 R.1 Content access procedure for ISO/IEC 14496 program components within a Program Stream. 172 R.2 Content access procedure for ISO/IEC 14496 program components within a Transport Stream. 173
oSIST ISO/IEC 13818-1:2010



ISO/IEC 13818-1:2007(E) © ISO/IEC 2007 – All rights reserved
vForeword 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. ISO/IEC 13818-1 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 (05/2006). This third edition cancels and replaces the second edition (ISO/IEC 13818-1:2000), which has been technically revised. It also incorporates the Amendments ISO/IEC 13818-1:2000/Amd.1:2003, ISO/IEC 13818-1:2000/Amd.2:2004, ISO/IEC 13818-1:2000/Amd.3:2004, ISO/IEC 13818-1:2000/Amd.4:2005 and ISO/IEC 13818-1:2000/Amd.5:2005, and the Technical Corrigenda ISO/IEC 13818-1:2000/Cor.1:2002, ISO/IEC 13818-1:2000/Cor.2:2002, ISO/IEC 13818-1:2000/Cor.3:2005, ISO/IEC 13818-1:2000/Cor.4:2007. ISO/IEC 13818 consists of the following parts, under the general title Information technology — Generic coding of moving pictures and associated audio information: ⎯ Part 1: Systems ⎯ Part 2: Video ⎯ Part 3: Audio ⎯ Part 4: Conformance testing ⎯ Part 5: Software simulation [Technical Report] ⎯ Part 6: Extensions for DSM-CC ⎯ Part 7: Advanced Audio Coding (AAC) ⎯ Part 9: Extension for real time interface for systems decoders ⎯ Part 10: Conformance extensions for Digital Storage Media Command and Control (DSM-CC) ⎯ Part 11: IPMP on MPEG-2 systems
oSIST ISO/IEC 13818-1:2010



ISO/IEC 13818-1:2007(E) vi
© ISO/IEC 2007 – All rights reserved
Introduction The systems part of this Recommendation | International Standard addresses the combining of one or more elementary streams of video and audio, as well as other data, into single or multiple streams which are suitable for storage or transmission. Systems coding follows the syntactical and semantic rules imposed by this Specification and provides information to enable synchronized decoding of decoder buffers over a wide range of retrieval or receipt conditions. System coding shall be specified in two forms: the Transport Stream and the Program Stream. Each is optimized for a different set of applications. Both the Transport Stream and Program Stream defined in this Recommendation | International Standard provide coding syntax which is necessary and sufficient to synchronize the decoding and presentation of the video and audio information, while ensuring that data buffers in the decoders do not overflow or underflow. Information is coded in the syntax using time stamps concerning the decoding and presentation of coded audio and visual data and time stamps concerning the delivery of the data stream itself. Both stream definitions are packet-oriented multiplexes. The basic multiplexing approach for single video and audio elementary streams is illustrated in Figure Intro. 1. The video and audio data is encoded as described in ITU-T Rec. H.262 | ISO/IEC 13818-2 and ISO/IEC 13818-3. The resulting compressed elementary streams are packetized to produce PES packets. Information needed to use PES packets independently of either Transport Streams or Program Streams may be added when PES packets are formed. This information is not needed and need not be added when PES packets are further combined with system level information to form Transport Streams or Program Streams. This systems standard covers those processes to the right of the vertical dashed line. TISO5760-95/d01VideoencoderAudioencoderPacketizerPacketizerVideodataAudiodataProgramStreamTransportStreamVideo PESAudio PESPSmuxTSmuxExtent of systems specificationFigure Intro. 1 – Simplified overview of the scope of this Recommendation | International Standard The Program Stream is analogous and similar to ISO/IEC 11172 Systems layer. It results from combining one or more streams of PES packets, which have a common time base, into a single stream. For applications that require the elementary streams which comprise a single program to be in separate streams which are not multiplexed, the elementary streams can also be encoded as separate Program Streams, one per elementary stream, with a common time base. In this case the values encoded in the SCR fields of the various streams shall be consistent. Like the single Program Stream, all elementary streams can be decoded with synchronization. The Program Stream is designed for use in relatively error-free environments and is suitable for applications which may involve software processing of system information such as interactive multi-media applications. Program Stream packets may be of variable and relatively great length. The Transport Stream combines one or more programs with one or more independent time bases into a single stream. PES packets made up of elementary streams that form a program share a common timebase. The Transport Stream is designed for use in environments where errors are likely, such as storage or transmission in lossy or noisy media. Transport Stream packets are 188 bytes in length. oSIST ISO/IEC 13818-1:2010



ISO/IEC 13818-1:2007(E) © ISO/IEC 2007 – All rights reserved
vii Program and Transport Streams are designed for different applications and their definitions do not strictly follow a layered model. It is possible and reasonable to convert from one to the other; however, one is not a subset or superset of the other. In particular, extracting the contents of a program from a Transport Stream and creating a valid Program Stream is possible and is accomplished through the common interchange format of PES packets, but not all of the fields needed in a Program Stream are contained within the Transport Stream; some must be derived. The Transport Stream may be used to span a range of layers in a layered model, and is designed for efficiency and ease of implementation in high bandwidth applications. The scope of syntactical and semantic rules set forth in the systems specification differ: the syntactical rules apply to systems layer coding only, and do not extend to the compression layer coding of the video and audio specifications; by contrast, the semantic rules apply to the combined stream in its entirety. The systems specification does not specify the architecture or implementation of encoders or decoders, nor those of multiplexors or demultiplexors. However, bit stream properties do impose functional and performance requirements on encoders, decoders, multiplexors and demultiplexors. For instance, encoders must meet minimum clock tolerance requirements. Notwithstanding this and other requirements, a considerable degree of freedom exists in the design and implementation of encoders, decoders, multiplexors, and demultiplexors. Intro. 1
Transport Stream The Transport Stream is a stream definition which is tailored for communicating or storing one or more programs of coded data according to ITU-T Rec. H.262 | ISO/IEC 13818-2 and ISO/IEC 13818-3 and other data in environments in which significant errors may occur. Such errors may be manifested as bit value errors or loss of packets. Transport Streams may be either fixed or variable rate. In either case the constituent elementary streams may either be fixed or variable rate. The syntax and semantic constraints on the stream are identical in each of these cases. The Transport Stream rate is defined by the values and locations of Program Clock Reference (PCR) fields, which in general are separate PCR fields for each program. There are some difficulties with constructing and delivering a Transport Stream containing multiple programs with independent time bases such that the overall bit rate is variable. Refer to 2.4.2.2. The Transport Stream may be constructed by any method that results in a valid stream. It is possible to construct Transport Streams containing one or more programs from elementary coded data streams, from Program Streams, or from other Transport Streams which may themselves contain one or more programs. The Transport Stream is designed in such a way that several operations on a Transport Stream are possible with minimum effort. Among these are: 1) Retrieve the coded data from one program within the Transport Stream, decode it and present the decoded results as shown in Figure Intro. 2. 2) Extract the Transport Stream packets from one program within the Transport Stream and produce as output a different Transport Stream with only that one program as shown in Figure Intro. 3. 3) Extract the Transport Stream packets of one or more programs from one or more Transport Streams and produce as output a different Transport Stream (not illustrated). 4) Extract the contents of one program from the Transport Stream and produce as output a Program Stream containing that one program as shown in Figure Intro. 4. 5) Take a Program Stream, convert it into a Transport Stream to carry it over a lossy environment, and then recover a valid, and in certain cases, identical Program Stream. Figure Intro. 2 and Figure Intro. 3 illustrate prototypical demultiplexing and decoding systems which take as input a Transport Stream. Figure Intro. 2 illustrates the first case, where a Transport Stream is directly demultiplexed and decoded. Transport Streams are constructed in two layers: – a system layer; and – a compression layer. The input stream to the Transport Stream decoder has a system layer wrapped about a compression layer. Input streams to the Video and Audio decoders have only the compression layer. Operations performed by the prototypical decoder which accepts Transport Streams either apply to the entire Transport Stream ("multiplex-wide operations"), or to individual elementary streams ("stream-specific operations"). The Transport Stream system layer is divided into two sub-layers, one for multiplex-wide operations (the Transport Stream packet layer), and one for stream-specific operations (the PES packet layer). A prototypical decoder for Transport Streams, including audio and video, is also depicted in Figure Intro. 2 to illustrate the function of a decoder. The architecture is not unique – some system decoder functions, such as decoder timing oSIST ISO/IEC 13818-1:2010



ISO/IEC 13818-1:2007(E) viii
© ISO/IEC 2007 – All rights reserved
control, might equally well be distributed among elementary stream decoders and the channel-specific decoder – but this figure is useful for discussion. Likewise, indication of errors detected by the channel-specific decoder to the individual audio and video decoders may be performed in various ways and such communication paths are not shown in the diagram. The prototypical decoder design does not imply any normative requirement for the design of a Transport Stream decoder. Indeed non-audio/video data is also allowed, but not shown. TISO5770-95/d02Channel specificdecoderTransport Streamdemultiplexand decoderVideodecoderClockcontrolAudiodecoderChannelDecodedvideoDecodedaudioTransport Streamcontaining one or multiple programsFigure Intro. 2 – Prototypical transport demultiplexing and decoding example Figure Intro. 3 illustrates the second case, where a Transport Stream containing multiple programs is converted into a Transport Stream containing a single program. In this case the re-multiplexing operation may necessitate the correction of Program Clock Reference (PCR) values to account for changes in the PCR locations in the bit stream. TISO5780-95/d03Channel specificdecoderTransport Streamdemultiplexand decoderTransport Streamcontaining multiple programsTransport Streamwith single programFigure Intro. 3 – Prototypical transport multiplexing exampleChannel Figure Intro. 4 illustrates a case in which a multi-program Transport Stream is first demultiplexed and then converted into a Program Stream. Figures Intro. 3 and Intro. 4 indicate that it is possible and reasonable to convert between different types and configurations of Transport Streams. There are specific fields defined in the Transport Stream and Program Stream syntax which facilitate the conversions illustrated. There is no requirement that specific implementations of demultiplexors or decoders include all of these functions. TISO5790-95/d04Channel specificdecoderTransport Streamdemultiplex andProgram StreammultiplexorChannelTransport Streamcontaining multiple programsProgram StreamFigure Intro. 4 – Prototypical Transport Stream to Program Stream conversion Intro. 2
Program Stream The Program Stream is a stream definition which is tailored for communicating or storing one program of coded data and other data in environments where errors are very unlikely, and where processing of system coding, e.g., by software, is a major consideration. oSIST ISO/IEC 13818-1:2010



ISO/IEC 13818-1:2007(E) © ISO/IEC 2007 – All rights reserved
ix Program Streams may be either fixed or variable rate. In either case, the constituent elementary streams may be either fixed or variable rate. The syntax and semantics constraints on the stream are identical in each case. The Program Stream rate is defined by the values and locations of the System Clock Reference (SCR) and mux_rate fields. A prototypical audio/video Program Stream decoder system is depicted in Figure Intro. 5. The architecture is not unique – system decoder functions including decoder timing control might as equally well be distributed among elementary stream decoders and the channel-specific decoder – but this figure is useful for discussion. The prototypical decoder design does not imply any normative requirement for the design of an Program Stream decoder. Indeed non-audio/video data is also allowed, but not shown. TISO5800-95/d05Channel specificdecoderProgram StreamdecoderVideodecoderClockcontrolAudiodecoderDecodedvideoDecodedaudioProgramStreamFigure Intro. 5 – Prototypical decoder for Program StreamsChannel The prototypical decoder for Program Streams shown in Figure Intro. 5 is composed of System, Video and Audio decoders conforming to Parts 1, 2 and 3, respectively, of ISO/IEC 13818. In this decoder, the multiplexed coded representation of one or more audio and/or video streams is assumed to be stored or communica
...

NORME ISO/CEI
INTERNATIONALE 13818-1
Troisième édition
2007-10-15


Technologies de l'information — Codage
générique des images animées et du son
associé: Systèmes
Information technology — Generic coding of moving pictures and
associated audio information: Systems



Numéro de référence
ISO/CEI 13818-1:2007(F)
©
ISO/CEI 2007

---------------------- Page: 1 ----------------------
ISO/CEI 13818-1:2007(F)
PDF – Exonération de responsabilité
Le présent fichier PDF peut contenir des polices de caractères intégrées. Conformément aux conditions de licence d'Adobe, ce fichier
peut être imprimé ou visualisé, mais ne doit pas être modifié à moins que l'ordinateur employé à cet effet ne bénéficie d'une licence
autorisant l'utilisation de ces polices et que celles-ci y soient installées. Lors du téléchargement de ce fichier, les parties concernées
acceptent de fait la responsabilité de ne pas enfreindre les conditions de licence d'Adobe. Le Secrétariat central de l'ISO décline toute
responsabilité en la matière.
Adobe est une marque déposée d'Adobe Systems Incorporated.
Les détails relatifs aux produits logiciels utilisés pour la création du présent fichier PDF sont disponibles dans la rubrique General Info
du fichier; les paramètres de création PDF ont été optimisés pour l'impression. Toutes les mesures ont été prises pour garantir
l'exploitation de ce fichier par les comités membres de l'ISO. Dans le cas peu probable où surviendrait un problème d'utilisation,
veuillez en informer le Secrétariat central à l'adresse donnée ci-dessous.


DOCUMENT PROTÉGÉ PAR COPYRIGHT


©  ISO/CEI 2007
Droits de reproduction réservés. Sauf prescription différente, aucune partie de cette publication ne peut être reproduite ni utilisée sous
quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie et les microfilms, sans l'accord écrit
de l'ISO à l'adresse ci-après ou du comité membre de l'ISO dans le pays du demandeur.
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
Version française parue en 2008
Publié en Suisse

ii © ISO/CEI 2007 – Tous droits réservés

---------------------- Page: 2 ----------------------
ISO/CEI 13818-1:2007(F)
Sommaire Page
SECTION 1 – GÉNÉRALITÉS. 1
1.1 Domaine d'application. 1

1.2 Références normatives . 1


SECTION 2 – ÉLÉMENTS TECHNIQUES . 2

2.1 Définitions. 2


2.2 Symboles et abréviations . 6


2.3 Méthode de description de la syntaxe des flux binaires . 8

2.4 Prescriptions applicables au flux binaire de transport. 9


2.5 Prescriptions applicables au flux binaire de programme . 55

2.6 Descripteurs de programme et d'élément de programme. 68


2.7 Restrictions appliquées à la sémantique des flux binaires multiplexés. 99

2.8 Compatibilité avec l'ISO/CEI 11172 . 104


2.9 Enregistrement des identificateurs de droits d'auteur . 104

2.10 Enregistrement du format de données privées . 105


2.11 Acheminement de données ISO/CEI 14496. 105

2.12 Acheminement des métadonnées. 118

2.13 Acheminement des données ISO 15938. 128


2.14 Acheminement de données vidéo Rec. UIT-T H.264 | ISO/CEI 14496-10 . 128

Annexe A – Modèle de décodeur pour le contrôle CRC . 133


A.0 Décodeur modèle de contrôle CRC. 133


Annexe B – Commande et contrôle des supports d'enregistrement numérique (DSM-CC) . 134

B.0 Introduction . 134


B.1 Eléments généraux . 135

B.2 Eléments techniques . 137


Annexe C – Informations spécifiques du programme. 143

C.0 Explications relatives aux informations spécifiques du programme (PSI) contenues dans un


flux de transport. 143
C.1 Introduction . 143


C.2 Mécanisme fonctionnel . 143


C.3 Mappage de sections dans des paquets du flux de transport . 144

C.4 Fréquences de répétition et accès aléatoire . 145


C.5 En quoi consiste un programme?. 145

C.6 Affectation du numéro de programme . 145


C.7 Utilisation des informations PSI dans un système type. 146

C.8 Relations entre structures d'informations PSI . 146


C.9 Affectation spectrale et temps d'acquisition du signal . 149

Ann exe D – Implications de la présente Recommandation | Norme internationale (systèmes) quant au

modèle de synchronisation et à ses applications . 152

D.0 Introduction . 152

Annexe E – Applications de transmission de données. 162


E.0 Généralités. 162

E.1 Suggestion. 162

Annexe F – Présentation graphique de la syntaxe pour la présente Recommandation | Norme internationale . 163


F.0 Introduction . 163

Annexe G – Informations générales . 169


G.0 Informations générales . 169

Annexe H – Données privées. 170

H.0 Données privées. 170

Annexe I – Conformité des systèmes et interface en temps réel . 172

I.0 Conformité des systèmes et interface en temps réel. 172


© ISO/CEI 2007 – Tous droits réservés iii

---------------------- Page: 3 ----------------------
ISO/CEI 13818-1:2007(F)

Page

Annexe J – Interfaçage entre réseaux générateurs de gigue et décodeurs MPEG-2. 173
J.0 Introduction . 173

J.1 Modèle de conformité de réseau. 173
J.2 Spécification de réseau pour le lissage de gigue. 174

J.3 Exemples d'implémentations de décodeur . 175
Annexe K – Combinaison des flux de transport. 177

K.0 Introduction . 177

K.1 Les différents types de points de combinaison. 177
K.2 Comportement des décodeurs en présence de combinaisons . 178
Annexe L – Procédure d'enregistrement (voir 2.9) . 180
L.1 Procédure de demande d'un identificateur enregistré (RID, registered identifier) . 180
L.2 Responsabilités de l'organisme d'enregistrement. 180
L.3 Responsabilités des parties demandant un identificateur RID. 180
L.4 Procédure d'appel en cas de refus de demande . 181
Annexe M – Formulaire de demande d'enregistrement (voir 2.9) . 182
M.1 Renseignements de contact sur l'organisation demandant un identificateur enregistré (RID). 182
M.2 Déclaration d'intention d'appliquer l'identificateur RID assigné . 182
M.3 Date d'implémentation prévue de l'identificateur RID. 182
M.4 Représentant autorisé. 182
M.5 Cadre réservé à l'usage officiel de l'organisme d'enregistrement . 182
Annexe N . 183
Annexe O – Procédure d'enregistrement (voir 2.10) . 184
O.1 Procédure de demande d'un identificateur enregistré (RID). 184
O.2 Responsabilités de l'organisme d'enregistrement. 184
O.3 Renseignements de contact de l'organisme d'enregistrement . 184
O.4 Responsabilités des parties demandant un identificateur RID. 184
O.5 Procédure d'appel en cas de refus de demande . 184
Annexe P – Formulaire de demande d'enregistrement. 186
P.1 Renseignements de contact sur l'organisation demandant un identificateur enregistré (RID). 186
P.2 Demande d'identificateur RID spécifique. 186
P.3 Brève description de l'identificateur RID qui est en usage et date de l'implémentation du
système. 186
P.4 Déclaration d'intention d'appliquer l'identificateur RID assigné . 186
P.5 Date d'implémentation prévue de l'identificateur RID. 186
P.6 Représentant autorisé. 186
P.7 Cadre réservé à l'usage officiel de l'organisme d'enregistrement . 186
Annexe Q – Modèles de mémoires tampons T-STD et P-STD pour données audio ADTS ISO/CEI
13818-7 . 187
Q.1 Introduction . 187
Q.2 Débit de débordement de la mémoire tampon de transport. 187
Q.3 Capacité de mémoire tampon. 187
Q.4 Conclusion. 189
Annexe R – Acheminement de scènes ISO/CEI 14496 dans un flux selon la Rec. UIT-T H.222.0 | ISO/CEI
13818-1 . 190
R.1 Procédure d'accès au contenu pour des éléments de programme ISO/CEI 14496 dans un flux
de programme . 190
R.2 Procédure d'accès au contenu pour des éléments de programme ISO/CEI 14496 dans un flux
de transport. 191
iv © ISO/CEI 2007 – Tous droits réservés

---------------------- Page: 4 ----------------------
ISO/CEI 13818-1:2007(F)
Avant-propos
L'ISO (Organisation internationale de normalisation) et la CEI (Commission électrotechnique internationale)
forment le système spécialisé de la normalisation mondiale. Les organismes nationaux membres de l'ISO ou
de la CEI participent au développement de Normes internationales par l'intermédiaire des comités techniques
créés par l'organisation concernée afin de s'occuper des domaines particuliers de l'activité technique. Les
comités techniques de l'ISO et de la CEI collaborent dans des domaines d'intérêt commun. D'autres
organisations internationales, gouvernementales et non gouvernementales, en liaison avec l'ISO et la CEI
participent également aux travaux. Dans le domaine des technologies de l'information, l'ISO et la CEI ont créé
un comité technique mixte, l'ISO/CEI JTC 1.
Les Normes internationales sont rédigées conformément aux règles données dans les Directives ISO/CEI,
Partie 2.
La tâche principale du comité technique mixte est d'élaborer les Normes internationales. Les projets de
Normes internationales adoptés par le comité technique mixte sont soumis aux organismes nationaux pour
vote. Leur publication comme Normes internationales requiert l'approbation de 75 % au moins des
organismes nationaux votants.
L'attention est appelée sur le fait que certains des éléments du présent document peuvent faire l'objet de
droits de propriété intellectuelle ou de droits analogues. L'ISO et la CEI ne sauraient être tenues pour
responsables de ne pas avoir identifié de tels droits de propriété et averti de leur existence.
L'ISO/CEI 13818-1 a été élaborée par le comité technique mixte ISO/CEI JTC 1, Technologies de
l'information, sous-comité SC SC 29, Codage du son, de l'image, de l'information multimédia et hypermédia,
en collaboration avec l’UIT-T. Le texte identique est publié en tant que Rec. UIT-T H.222.0 (05/2006).
Cette troisième édition annule et remplace la deuxième édition (ISO/CEI 13818-1:2000), qui a fait l'objet d'une
révision technique. Elle incorpore aussi les Amendements ISO/CEI 13818-1:2000/Amd.1:2003,
ISO/CEI 13818-1:2000/Amd.2:2004, ISO/CEI 13818-1:2000/Amd.3:2004, ISO/CEI 13818-1:2000/Amd.4:2005
et ISO/CEI 13818-1:2000/Amd.5:2005, et les Rectificatifs techniques ISO/CEI 13818-1:2000/Cor.1:2002,
ISO/CEI 13818-1:2000/Cor.2:2002, ISO/CEI 13818-1:2000/Cor.3:2005, ISO/CEI 13818-1:2000/Cor.4:2007.
L'ISO/CEI 13818 comprend les parties suivantes, présentées sous le titre général Technologies de
l'information — Codage générique des images animées et du son associé: Systèmes:
⎯ Partie 1: Systèmes
⎯ Partie 2: Données vidéo
⎯ Partie 3: Son
⎯ Partie 4: Essais de conformité
⎯ Partie 5: Simulation de logiciel
⎯ Partie 6: Extensions pour DSM-CC
⎯ Partie 7: Codage du son avancé (AAC)
⎯ Partie 9: Extension pour interface temps réel pour systèmes décodeur
⎯ Partie 10: Extensions de conformité pour commande et contrôle de supports de mémoire numérique
(DSM-CC)
⎯ Partie 11: IPMP sur les systèmes MPEG-2
© ISO/CEI 2007 – Tous droits réservés v

---------------------- Page: 5 ----------------------
ISO/CEI 13818-1:2007(F)

Introduction
La partie relative aux systèmes de la présente Recommandation | Norme internationale traite de la combinaison d'un ou
de plusieurs flux élémentaires de données vidéo et audio, ainsi que d'autres types, pour former des flux isolés ou
multiples se prêtant à l'enregistrement ou à la transmission. Le codage de ces systèmes suit les règles syntaxiques et
sémantiques qui sont imposées par la présente Spécification. Ce codage contient des informations qui permettent un

décodage synchronisé du contenu des mémoires des décodeurs, dans une large gamme de conditions d'extraction ou de
réception.

Le codage d'un système doit être spécifié sous deux formes: le flux de transport et le flux de programme. Chacun
d'eux est optimisé pour un ensemble d'applications différentes. Ces deux flux, définis dans la présente Recommandation

| Norme internationale, acheminent les éléments syntaxiques qui sont nécessaires et suffisants pour synchroniser le
décodage et la présentation des informations vidéo et audio, tout en garantissant que les mémoires tampons contenues

dans les décodeurs ne subiront ni surremplissage ni sous-remplissage de données. Les informations sont codées sous
forme d'éléments syntaxiques faisant appel à des pointeurs temporels (horodateurs) régissant, d'une part, le décodage et

la présentation des données codées pour signaux audio et vidéo, d'autre part, l'acheminement du flux de données
proprement dit. Les définitions relatives à ces deux flux s'assimilent à des multiplex en mode paquet.

La Figure Intro. 1 illustre la démarche fondamentale – celle du multiplexage – pour les flux élémentaires de données
vidéo et audio. Celles-ci sont codées conformément à la Rec. UIT-T H.262 | ISO/CEI 13818-2 et à l'ISO/CEI 13818-3.

Les flux élémentaires résultants sont, après compression, mis en paquets de flux PES. Les informations nécessaires
pour utiliser les paquets de flux PES peuvent être ajoutées au moment de la formation des paquets de flux PES, qu'il

s'agisse de flux de transport ou de flux de programme. Ces informations ne sont pas requises et n'ont pas besoin d'être
ajoutées si les paquets de flux PES sont recombinés avec des informations de niveau système pour former des flux de

transport ou des flux de programme. La présente norme relative aux systèmes traite des processus situés à droite du
trait pointillé vertical de la figure ci-après.


PES vidéo
Données
Codeur
Empaqueteur
vidéo
vidéo
Mux
Flux de

programme
PS
PES audio
Données
Codeur

Empaqueteur
audio
audio


Mux
Flux de

transport
TS


PES Flux élémentaire empaqueté
Domaine d'application de la spécification systèmes
PS Flux de programme
TS Flux de transport

TISO5760-95/d01

Figure Intro. 1 – Synoptique simplifié du domaine d'application de la présente

Recommandation | Norme internationale


Le flux de programme est analogue à la couche système de l'ISO/CEI 11172. Il est le résultat de la combinaison, en un

seul flux d'un ou de plusieurs flux élémentaires de paquets PES ayant la même base de temps.
Pour les applications qui exigent des flux élémentaires séparés et non multiplexés pour un même programme, on peut

également coder ces flux élémentaires sous forme de flux de programme distincts (un par flux élémentaire), possédant
la même base de temps. Dans ce cas, les valeurs codées dans les champs de référence temporelle système des divers

flux doivent être cohérentes.

De même que le flux de programme isolé, tous les flux élémentaires peuvent être décodés en synchronisme.
Le flux de programme est conçu pour être utilisé dans des environnements relativement exempts d'erreurs. Il convient à
des applications pouvant comporter un traitement informatique d'informations du système, comme les applications
vi © ISO/CEI 2007 – Tous droits réservés

---------------------- Page: 6 ----------------------
ISO/CEI 13818-1:2007(F)

multimédias interactives. Les paquets contenus dans le flux de programme peuvent avoir une longueur variable et
relativement grande.

Le flux de transport, en revanche, combine un ou plusieurs programmes possédant une ou plusieurs bases de temps

indépendantes, pour former un flux unique. Les paquets de flux PES contenus dans des flux élémentaires qui forment
un programme partagent une base de temps commune. Le flux de transport est conçu pour être utilisé dans des

environnements exposés aux erreurs, comme l'enregistrement ou la transmission sur des supports exposés aux erreurs
ou aux bruits. Les paquets d'un flux de transport ont une longueur de 188 octets.

Les flux de programme et de transport sont conçus pour différentes applications et leurs définitions ne suivent pas
strictement un modèle stratifié. Il est possible et logique de les convertir les uns les autres sans toutefois que l'un soit un

sous-ensemble ou un surensemble de l'autre. En particulier, l'extraction du contenu d'un programme dans un flux de
transport et la création d'un flux de programme valide sont possibles, grâce au format intermédiaire commun (CIF,

common interchange format) des paquets de flux PES. Mais le flux de transport ne contient pas tous les champs
nécessaires dans un flux de programme et certains doivent être calculés. On peut utiliser le flux de transport pour

rassembler une série de couches dans un modèle stratifié. Ce flux est conçu pour être efficace et d'implémentation aisée
dans les applications à large bande.

Le domaine d'application des règles exposées dans la présente spécification des systèmes est différent selon qu'elles

sont syntaxiques ou sémantiques: les règles syntaxiques ne s'appliquent qu'au codage de la couche système; elles ne
s'étendent pas au codage de la couche de compression des données vidéo et audio. En revanche, les règles sémantiques

s'appliquent aux combinaisons de flux dans leur ensemble.
La présente spécification des systèmes ne précise pas l'architecture ni l'implémentation des codeurs ou décodeurs, ni

celles des multiplexeurs ou démultiplexeurs. Les caractéristiques des flux binaires imposent cependant des exigences
relatives au fonctionnement et à la qualité des codeurs, des décodeurs, des multiplexeurs et des démultiplexeurs. Par

exemple, les codeurs doivent toujours satisfaire à des exigences minimales en termes de tolérance sur la référence
temporelle. Cela, ainsi que d'autres prescriptions, étant mis à part, il existe un degré de liberté considérable pour la

conception et l'implémentation des codeurs, décodeurs, multiplexeurs et démultiplexeurs.

Intro. 1  Flux de transport
Le f lux de transport est défini de manière à convenir pour la communication ou l'enregistrement d'un ou de plusieurs
programmes de données codées, conformément à la Rec. UIT-T H.262 | ISO/CEI 13818-2 et à l'ISO/CEI 13818-3, ainsi
que d'autres données dans des environnements exposés à des erreurs notables. De telles erreurs peuvent se manifester

sous forme d'erreur sur la valeur d'un bit ou de perte de paquets.

Les flux de transport peuvent être à débit constant ou à débit variable. Dans un cas comme dans l'autre, les flux
élémentaires qui les constituent peuvent être à débit constant ou variable. Les contraintes syntaxiques et sémantiques sur

le flux sont identiques dans l'un et l'autre cas. Le débit du flux de transport est défini par les valeurs et par les
emplacements des champs de la référence temporelle du programme (PCR, program clock reference). En général, ces

champs sont distincts pour chaque programme.
La construction et l'acheminement d'un flux de transport contenant plusieurs programmes caractérisés par des bases de

temps indépendantes, et comportant donc un débit binaire global variable, présentent certaines difficultés. Voir 2.4.2.2.

Le flux de transport peut être construit selon toute méthode qui produit un flux conforme. A partir de flux élémentaires
de données codées, de flux de programme ou de flux de transport pouvant eux-mêmes contenir un ou plusieurs

programmes, il est possible de construire des flux de transport contenant un ou plusieurs programmes.
Le fl ux de transport est conçu de telle manière que l'on puisse effectuer sur lui plusieurs opérations avec le moins
d'effort possible. Il peut s'agir, par exemple:

1) d'extraire les données codées d'un programme contenu dans le flux de transport, de les décoder et de
présenter les résultats comme indiqué sur la Figure Intro. 2;

2) d'extraire, du flux de transport, les paquets de type flux de transport contenus dans un programme donné
et de produire, en sortie, un flux de transport différent, ne contenant que ce programme, comme indiqué

sur la Figure Intro. 3;
3) d'extraire, d'un ou de plusieurs flux de transport, les paquets de type flux de transport contenus dans un
ou plusieurs programmes et de produire, en sortie, un flux de transport différent (non illustré);

4) d'extraire, du flux de transport, le contenu d'un programme isolé et de produire, en sortie, un flux de
programme contenant ce programme isolé, comme indiqué sur la Figure Intro. 4;

5) de prendre un flux de programme, de le convertir en un flux de transport pour lui faire traverser un
environnement exposé aux pertes puis de récupérer un flux de programme valide et, dans certains cas,

identique.
© ISO/CEI 2007 – Tous droits réservés vii

---------------------- Page: 7 ----------------------
ISO/CEI 13818-1:2007(F)

La Figure Intro. 2 et la Figure Intro. 3 montrent des prototypes de systèmes de démultiplexage et de décodage dont

l'entrée est un flux de transport. La Figure Intro. 2 illustre le premier cas, dans lequel un flux de transport est
directement démultiplexé et décodé. Les flux de transport sont structurés en deux couches:

– une couche système;
– une couche de compression.

Le flux d'entrée dans le décodeur de flux de transport possède une couche système qui est imbriquée dans une couche

de compression. Les flux d'entrée dans les décodeurs de données vidéo et de données audio ne possèdent que la couche
de compression.

Les opérations effectuées par le décodeur prototype recevant des flux de transport sont applicables soit au flux de
transport total (ce sont alors des "opérations à l'échelle du multiplex") soit à des flux élémentaires distincts (ce sont alors

des "opérations particulières à un flux"). La couche système du flux de transport se subdivise en deux sous-couches,
l'une pour les opérations à l'échelle du multiplex (dite "couche paquet du flux de transport"), l'autre pour les opérations

particulières à un flux (dite "couche paquet de flux PES").

Un décodeur prototype pour flux de transport, recevant des données audio et vidéo, est décrit à la Figure Intro. 2 pour
montrer la fonction d'un décodeur. L'architecture de celui-ci n'est pas rigide: certaines fonctions de décodeur de couche

système, comme la gestion des temps d'un décodeur, peuvent tout aussi bien être réparties entre des décodeurs de flux
élémentaire et le décodeur propre au canal. Mais cette Figure Intro. 2 est utile pour poser le problème. De même, on

peut effectuer de diverses manières la fonction d'indication – aux décodeurs audio et vidéo particuliers – des erreurs
détectées par le décodeur propre au canal: de telles voies de communication ne sont pas représentées sur le schéma. Le

prototype de décodeur est conçu de façon à n'impliquer aucune prescription normative quant à la structure d'un
décodeur de flux de transport. Des données ni audio ni vidéo peuvent également être présentées en entrée, mais on ne

les a pas représentées.

Décodeur Données vidéo
vidéo
décodées


Démultiplexage
Décodeur
Canal et décodage Gestionnaire
propre au

du flux de d'ho
...