Annex E
(Informative.)
Data Transmission Applications
E.0 CONSIDERATIONS
ITU‑T Rec. H.222.0†|†ISO/IEC 13818-1 transport multiplex will be used to transmit data as well as video and audio.
Data elementary streams are not continuous as may appear video and audio streams in broadcast applications.
While it is already possible to identify the beginning of a PES packet, it is not always possible to identify the end of a PES packet by the beginning of the next PES packet, because it is possible for one or more Transport packet carrying PES packets to be lost.
A suitable solution is to transmit the following PES packet just after an associated PES packet,. A PES packet without payload may be sent when there are no further PES packet to send.
The following is an example of such a PES packet.:
Table E-1 -- PES packet header example
PES packet header fields
|
values
|
packet_start_code_prefix
|
0x000001
|
stream_id
|
assigned
|
PES_packet_length
|
0x0003
|
'10'
|
'10'
|
PES_scrambling_control
|
'00'
|
PES_priority
|
'0'
|
data_alignment_indicator
|
'0'
|
copyright
|
'0'
|
original_or_copy
|
'0'
|
PTS_DTS_flags
|
'00'
|
ESCR_flag
|
'0'
|
ES_rate_flag
|
'0'
|
DSM_trick_mode_flag
|
'0'
|
additonal_copy_info_flag
|
'0'
|
PES_CRC_flag
|
'0'
|
PES_extension_flag
|
'0'
|
PES_header_data_length
|
0x00
|
Annex F
(Informative.)
Graphics of Syntax for ITU‑T H.222.0†|†ISO/IEC 13818-1
This part of the standard is an informative annex presenting graphically the Transport Stream and Program Stream syntax . This part in no way replaces any normative clause(s).
In order to produce clear drawings, not all fields have been fully described or represented. Reserved fields may be omitted or indicated by areas with no detail. Fields length are indicated in bits.
Figure F-1 -- Transport Stream syntax diagram
Share with your friends: |
