IEC 62328-3:2005
(Main)Multimedia home server systems - Interchangeable volume/file structure adaptation for broadcasting receivers - Part 3: Broadcasting system specific recording structure - ISDB
Multimedia home server systems - Interchangeable volume/file structure adaptation for broadcasting receivers - Part 3: Broadcasting system specific recording structure - ISDB
Defines the volume and file structure required for interchanging multimedia data of a home server/broadcasting receiver, which consists of an AV stream with multiple associated objects.specifies the broadcasting system specific recording structure for ISDB
General Information
- Status
- Published
- Publication Date
- 25-Jul-2005
- Technical Committee
- TA 18 - Multimedia home systems and applications for end-user networks
- Current Stage
- PPUB - Publication issued
- Start Date
- 15-Nov-2005
- Completion Date
- 26-Jul-2005
Overview
IEC 62328-3:2005 is part of the IEC 62328 series for multimedia home server systems and defines the interchangeable volume/file structure adaptation specifically for ISDB broadcasting receivers. The standard specifies how recorded audiovisual (AV) streams and their associated objects (metadata, component descriptors, program information) must be organized on storage volumes to enable reliable interchange between home servers and broadcasting receivers. It is the ISDB-specific recording structure complementing the general architecture (Part 1) and general recording rules (Part 2).
Key topics
- Volume and file structure: required directory and file layout for recorded programs to support interoperability between devices.
- Metadata handling: organization of MetaDataTable streams, MDE (meta data entry) formats and TYPE1/TYPE2 MDE interpretations.
- Program information files: PROGxxxx.PIF and associated structures for storing programme general information and descriptors.
- Component and component-group descriptions: formats for audio/video/data components, grouping, and search pointers.
- Stream-type dependent data: rules for video, audio and data modes and their associated stream descriptors.
- Partial TS / PSI‑SI mapping: guidance on partial transport stream format and mapping tables (Annex A).
- Country- or system-specific annexes: Japanese digital TV specifics (Annex B), D-VHS particulars (Annex C) and coexistence rules with domestic services (Annex D - normative).
- Character sets, notation and normative references: character set fields, notation conventions and referenced standards necessary for correct implementation.
Applications
- Enables interoperability between ISDB set‑top boxes, digital TV receivers and home media servers for recorded-program exchange, playback and content management.
- Provides a blueprint for firmware and middleware developers implementing recording, file-system layout and metadata handling in consumer electronics.
- Used by manufacturers of broadcasting receivers, home servers, and DVRs to ensure recorded content can be read/written across devices.
- Helps system integrators and test labs create conformance tests and validation procedures for ISDB recording implementations.
- Useful for broadcasters and service providers wanting consistent metadata packaging for recorded content distribution.
Who should use this standard
- Device manufacturers (set-top boxes, home servers, PVR/DVR vendors)
- Firmware and middleware developers
- Interoperability test labs and certification bodies
- Broadcasters and system integrators working with ISDB deployments
Related standards
- IEC 62328-1 - General description and architecture
- IEC 62328-2 - General recording structure
- Relevant ISDB technical specifications and PSI/SI standards referenced in the annexes
Keywords: IEC 62328-3, ISDB, multimedia home server systems, interchangeable volume/file structure, PROGxxxx.PIF, MDE, metadata, broadcasting receiver recording structure.
Frequently Asked Questions
IEC 62328-3:2005 is a standard published by the International Electrotechnical Commission (IEC). Its full title is "Multimedia home server systems - Interchangeable volume/file structure adaptation for broadcasting receivers - Part 3: Broadcasting system specific recording structure - ISDB". This standard covers: Defines the volume and file structure required for interchanging multimedia data of a home server/broadcasting receiver, which consists of an AV stream with multiple associated objects.specifies the broadcasting system specific recording structure for ISDB
Defines the volume and file structure required for interchanging multimedia data of a home server/broadcasting receiver, which consists of an AV stream with multiple associated objects.specifies the broadcasting system specific recording structure for ISDB
IEC 62328-3:2005 is classified under the following ICS (International Classification for Standards) categories: 33.160.60 - Multimedia systems and teleconferencing equipment; 35.040.40 - Coding of audio, video, multimedia and hypermedia information. The ICS classification helps identify the subject area and facilitates finding related standards.
IEC 62328-3:2005 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
INTERNATIONAL IEC
STANDARD 62328-3
First edition
2005-07
Multimedia home server systems –
Interchangeable volume/file structure
adaptation for broadcasting receivers –
Part 3:
Broadcasting system specific recording
structure – ISDB
Reference number
Publication numbering
As from 1 January 1997 all IEC publications are issued with a designation in the
60000 series. For example, IEC 34-1 is now referred to as IEC 60034-1.
Consolidated editions
The IEC is now publishing consolidated versions of its publications. For example,
edition numbers 1.0, 1.1 and 1.2 refer, respectively, to the base publication, the
base publication incorporating amendment 1 and the base publication incorporating
amendments 1 and 2.
Further information on IEC publications
The technical content of IEC publications is kept under constant review by the IEC,
thus ensuring that the content reflects current technology. Information relating to
this publication, including its validity, is available in the IEC Catalogue of
publications (see below) in addition to new editions, amendments and corrigenda.
Information on the subjects under consideration and work in progress undertaken
by the technical committee which has prepared this publication, as well as the list
of publications issued, is also available from the following:
• IEC Web Site (www.iec.ch)
• Catalogue of IEC publications
The on-line catalogue on the IEC web site (www.iec.ch/searchpub) enables you to
search by a variety of criteria including text searches, technical committees
and date of publication. On-line information is also available on recently issued
publications, withdrawn and replaced publications, as well as corrigenda.
• IEC Just Published
This summary of recently issued publications (www.iec.ch/online_news/ justpub)
is also available by email. Please contact the Customer Service Centre (see
below) for further information.
• Customer Service Centre
If you have any questions regarding this publication or need further assistance,
please contact the Customer Service Centre:
Email: custserv@iec.ch
Tel: +41 22 919 02 11
Fax: +41 22 919 03 00
INTERNATIONAL IEC
STANDARD 62328-3
First edition
2005-07
Multimedia home server systems –
Interchangeable volume/file structure
adaptation for broadcasting receivers –
Part 3:
Broadcasting system specific recording
structure – ISDB
IEC 2005 Copyright - all rights reserved
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 the publisher.
International Electrotechnical Commission, 3, rue de Varembé, PO Box 131, CH-1211 Geneva 20, Switzerland
Telephone: +41 22 919 02 11 Telefax: +41 22 919 03 00 E-mail: inmail@iec.ch Web: www.iec.ch
PRICE CODE
Commission Electrotechnique Internationale XA
International Electrotechnical Commission
МеждународнаяЭлектротехническаяКомиссия
For price, see current catalogue
– 2 – 62328-3 IEC:2005(E)
CONTENTS
FOREWORD.5
INTRODUCTION.7
1 Scope.8
2 Normative references .8
3 Terms and definitions.9
4 Abbreviations .10
5 Notation .11
5.1 Numerical values.11
6 General .11
6.1 Character set field in Dstring[n] .11
7 File and directory.12
7.1 TYPE1 each PGR specific area in structure PGR .12
7.2 Structure MDE (meta data entry) in MetaDataTable stream file .13
7.3 Programme information in PROGxxxx.PIF file .17
Annex A (informative) Partial TS format .34
Annex B (informative) Japanese digital TV specific information.37
Annex C (informative) D-VHS specific information .51
Annex D (normative) Coexistence with domestic services of individual countries .52
Bibliography.53
Figure 1 – Structure of programme information .18
Figure 2 – Structure of TYPE1 components information .24
Figure 3 – Structure of component group information.27
Table 1 – Structure Dstring[n] .11
Table 2 – Interpretation of character set .12
Table 3 – Structure of TYPE1 PGRSA .12
Table 4 – Structure of FL1 .13
Table 5 – Structure of MDE.13
Table 6 – MDE TYPE interpretation .13
Table 7 – Structure of TYPE 1 MDE.13
Table 8 – Structure of FLMDE.14
Table 9 – User ID type interpretation .15
Table 10 – Structure of programme general information.18
Table 11 – Programme identification type interpretation.18
Table 12 – Service type interpretation.19
Table 13 – Structure of broadcasting TV programme information .19
Table 14 – BTVPI TYPE interpretation .19
Table 15 – Structure of TYPE1 broadcasting TV programme information .20
Table 16 – Structure of descriptors in the case of D-VHS specific type .22
62328-3 IEC:2005(E) – 3 –
Table 17 – Structure of component information .23
Table 18 – COMPI TYPE interpretation.23
Table 19 – Structure of component information header .24
Table 20 – Structure of CFL.24
Table 21 – Structure of CC .25
Table 22 – Structure of PR .26
Table 23 – Structure of component group information search pointer .27
Table 24 – Structure of component group information header .27
Table 25 – Structure of component information .28
Table 26 – Stream type interpretation .28
Table 27 – Structure of CIFL.29
Table 28 – Structure of CC .29
Table 29 – Structure of stream type dependant data (video mode).30
Table 30 – Structure of stream type dependant data (audio mode).31
Table 31 – Structure of ESI.31
Table 32 – Structure of stream type dependant data (data mode) .32
Table 33 – Structure of stream type dependant data (additional data).32
Table 34 – Structure of TYPE2 component information .33
Table A.1 – PSI/SI tables.34
Table A.2 – PID and table ID mapping for PSI/SI .34
Table A.3 – Programme association section.35
Table A.4 – Programme map section .35
Table A.5 – Descriptors in PMT in partial TS.36
Table A.6 – Discontinuity information section.36
Table A.7 – Selection information section .37
Table A.8 – Descriptors in SIT .37
Table B.1 – Tag values of descriptors .38
Table B.2 – Structure of CA descriptor.39
Table B.3 – Structure of service list descriptor .39
Table B.4 – Structure of stuffing descriptor .39
Table B.5 – Structure of service descriptor .40
Table B.6 – Structure of short-event descriptor .40
Table B.7 – Structure of extended-event descriptor.40
Table B.8 – Structure of component descriptor .41
Table B.9 – Structure of stream identifier descriptor .41
Table B.10 – Structure of content descriptor .41
Table B.11 – Structure of parental rating descriptor .41
Table B.12 – Structure of partial transport stream descriptor.42
Table B.13 – Structure of broadcast id descriptor.42
Table B.14 – Structure of hierarchical transmission descriptor .42
Table B.15 – Structure of digital copy control descriptor .43
Table B.16 – Structure of network identification descriptor.43
Table B.17 – Structure of partial TS time descriptor .44
Table B.18 – Structure of audio component descriptor .44
– 4 – 62328-3 IEC:2005(E)
Table B.19 – Structure of hyperlink descriptor.44
Table B.20 – Structure of target region descriptor .45
Table B.21 – Structure of data content descriptor .45
Table B.22 – Structure of video decode control descriptor .45
Table B.23 – Structure of TS information descriptor.46
Table B.24 – Structure of extended broadcaster descriptor .46
Table B.25 – Structure of series descriptor .47
Table B.26 – Structure of event group descriptor .47
Table B.27 – Structure of broadcaster name descriptor.48
Table B.28 – Structure of component group descriptor.48
Table B.29 – Structure of content availability descriptor.48
Table B.30 – Structure of emergency information descriptor .49
Table B.31 – Structure of data component descriptor.49
Table B.32 – Structure of NIT .49
Table B.33 – Structure of EIT.50
Table C.1 – Tag values of descriptors.51
Table C.2 – Structure of DTCP descriptor .51
Table D.1 – Reserved directories .52
62328-3 IEC:2005(E) – 5 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
___________
MULTIMEDIA HOME SERVER SYSTEMS –
INTERCHANGEABLE VOLUME/FILE STRUCTURE ADAPTATION
FOR BROADCASTING RECEIVERS –
Part 3: Broadcasting system specific recording structure – ISDB
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 62328-3 has been prepared by IEC technical committee 100:
Audio, video and multimedia systems and equipment.
The text of this standard is based on the following documents:
FDIS Report on voting
100/965/FDIS 100/989/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
– 6 – 62328-3 IEC:2005(E)
IEC 62328 consists of the following parts, under the general title Multimedia home server
systems – Interchangeable volume/file structure adaptation for broadcasting receivers:
Part 1: General description and architecture
Part 2: General recording structure
Part 3: Broadcasting system specific recording structure – ISDB
The committee has decided that the contents of this publication will remain unchanged until
the maintenance result date indicated on the IEC web site under "http://webstore.iec.ch" in
the data related to the specific publication. At this date, the publication will be
• reconfirmed;
• withdrawn;
• replaced by a revised edition, or
• amended.
A bilingual version of this publication may be issued at a later date.
62328-3 IEC:2005(E) – 7 –
INTRODUCTION
Broadcast data in a transport stream can contain multiple associated objects. When that data
is distributed on interchangeable storage media, for example, optical disks, the associated
objects should be synchronized. Open distribution of the media requires that the data be
adapted to a standardized volume and file structure, which should conform to the existing
basic volume and file structure.
– 8 – 62328-3 IEC:2005(E)
MULTIMEDIA HOME SERVER SYSTEMS –
INTERCHANGEABLE VOLUME/FILE STRUCTURE ADAPTATION
FOR BROADCASTING RECEIVERS –
Part 3: Broadcasting system specific recording structure – ISDB
1 Scope
This part of IEC 62328 defines the volume and file structure required for interchanging
multimedia data of a home server/broadcasting receiver, which consists of an AV stream with
multiple associated objects.
This part of IEC 62328 specifies the broadcasting system specific recording structure for ISDB.
2 Normative references
The following referenced documents are indispensable for the application of this document.
For dated references, only the edition cited applies. For undated references, the latest edition
of the referenced document (including any amendments) applies.
IEC 62328-2, Multimedia home server systems – Interchangeable volume/file structure
adaptation for broadcasting receivers – Part 2: General recording structure
ISO/IEC 646, Information technology – ISO 7-bit coded character set for information
interchange
ISO/IEC 10646-1, Information technology – Universal Multiple-Octet Coded Character Set
(UCS) – Part 1: Architecture and Basic Multilingual Plane
ISO/IEC 13818-1:2000, Information technology – Generic coding of moving pictures and
associated audio information: Systems
ISO/IEC 13818-2:2000, Information technology – Generic coding of moving pictures and
associated audio information: Video
ISO/IEC 13818-6:1998, Information technology – Generic coding of moving pictures and
associated audio information – Par t6: Extensions for DSM-CC
ISO/IEC 13818-7:2003, Information technology – Generic coding of moving pictures and
associated audio information – Part 7: Advanced Audio Coding (AAC)
ISO/IEC 11172-2:1993, Information technology – Coding of moving pictures and associated
audio for digital storage media at up to about 1,5 Mbit/s – Part 2: Video
ISO 8859 (all parts), Information technology – 8-bit single-byte coded graphic character sets
62328-3 IEC:2005(E) – 9 –
3 Terms and definitions
For the purpose of this document, the following terms and definitions apply.
3.1
action
duration from start to end defined by a user or equipment
3.2
AV stream
recorded data in the MainTS stream file of PROGxxxx.PIF in this specification or the general
meaning as multiplexed digital audio and video
3.3
component
elementary stream contained in a TV programme
3.4
event
set of video and/or audio stream data and/or related objects, which together form a
broadcasting service in the duration defined by a broadcaster
3.5
partial TS
TS derived from broadcasting TS by modifying PSI/SI and/or removing one or more
elementary streams
3.6
programme
recorded TV programme compliant with this specification
3.7
programme reference
PGR
pointer which references all or a part of AV stream in a programme
3.8
programme reference group
PGRG
set of programme references or a set of programme reference groups
3.9
transport stream
TS
system stream for broadcasting defined in ISO/IEC 13818-1
3.10
TV programme
logical unit of TV broadcasting (event in digital TV service)
3.11
TVRS partial TS
partial TS recording format, which complies with this specification
– 10 – 62328-3 IEC:2005(E)
4 Abbreviations
For the purposes of this document, the following abbreviations apply.
ARIB Association of radio industries and businesses
ATSC Advanced television systems committee
BP Byte position within a file, starting with zero
BAT Bouquet association table
BIT Broadcaster information table
CBC Cipher block chaining
CCI Copy control information
DSM-CC Digital storage media command and control
DTCP Digital transmission content protection
DVB Digital video broadcasting
D-VHS Data video home system
EIT Event information table
ES Elementary stream
IRV International reference version
ISDB Integrated services digital broadcasting
MPEG Moving picture experts group
NIT Network information table
PAT Programme association table
PCR Programme clock reference
PES Packetized elementary stream
PGR Programme reference
PGRG Programme reference group
PID Packet identifier
PMT Program map table
PSI Programme specific information
RBP Relative byte position within a file, starting with zero
RP Recording packet
LSB Least significant bit
SDT Service information table
SI Service information
STB Set top box
TS Transport stream
TU Time unit
TVRS TV recording format specific
62328-3 IEC:2005(E) – 11 –
5 Notation
5.1 Numerical values
5.1.1 Decimal notation
A decimal number is represented as decimal digits 0 to 9.
5.1.2 Hexadecimal notation
A hexadecimal number is represented as hexadecimal digits 0 to 9 and A to F prefixed by the
symbol “0x”.
5.1.3 Binary notation
A binary number is represented as binary digits 0 to 1 suffixed by the symbol “b”.
5.1.4 Bit string
A bslbf shall be recorded as a bit string, left bit first.
5.1.5 Unsigned numerical value
A uimsbf shall be an unsigned integer, most significant bit first.
5.1.6 Remainder polynomial coefficients
A rpchof shall be the remainder polynomial coefficients, highest order first.
6 General
6.1 Character set field in Dstring[n]
A Dstring[n] is a field where a string can be recorded. The character string field size shall be
equal to n. The character set of the string is defined in the character set field. The structure
of the Dstring[n] is described in Table 1.
Table 1 – Structure Dstring[n]
RBP Length
Field name Contents
in bytes
0 1 Character set uimsbf
1 3 Reserved bslbf
4 2 Character string field size uimsbf
6 2 Length of character string uimsbf
8 n Character strings bslbf
6.1.1 Character set
The format of the character set is described in Table 2.
– 12 – 62328-3 IEC:2005(E)
Table 2 – Interpretation of character set
Value Character set
0x00
Reserved
0x01
ISO/IEC 10646-1 (Unicode)
0x02-0x0F Reserved
0x10 ISO/IEC 646 IRV(ASCII)
0x11
ISO 8859-1
0x12 ISO 8859-2
0x13 ISO 8859-3
0x14
ISO 8859-4
0x15
ISO 8859-5
0x16 ISO 8859-6
0x17
ISO 8859-7
0x18
ISO 8859-8
0x19 ISO 8859-9
0x1A ISO 8859-10
0x1B
ISO 8859-11
0x1C Reserved
0x1D ISO 8859-13
0x1E
ISO 8859-14
0x1F
ISO 8859-15
0x20 ISO 8859-16
0x21-0x7F
Reserved
0x80 Japanese character set defined in ARIB B24,
Volume 1, Part 2, Chapter 7, Section 7.1
0x81 Japanese character set defined in JIS X0208
(shift JIS)
0x82 Japanese character set defined in ARIB B24,
Volume 2, Chapter 4, Section 4.1.1 (EUC-JP)
0x83-0xFF Reserved
7 File and directory
7.1 TYPE1 each PGR specific area in structure PGR
The structure of TYPE1 PGRSA is described in Table 3.
Table 3 – Structure of TYPE1 PGRSA
RBP Length
Field name Contents
in bytes
0 1 PGR specific area TYPE uimsbf
1 1 Flag FL1
2 2 Reserved bslbf
4 8 Event start time GTS
12 4 Duration Duration
16 2 Network ID uimsbf
18 2 Service ID uimsbf
20 12 Reserved bslbf
62328-3 IEC:2005(E) – 13 –
7.1.1 Flag
The structure of FL1 is described in Table 4.
Table 4 – Structure of FL1
bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0
Reserved E/A CCI ECRYT
7.1.1.1 CCI (bit2-1)[bslbf]
If the value of PI_TYPE field in the program general information is equal to 0x01, which
means ISDB specific type, the value of DRCD bits in the copy control field in the TYPE1
component information shall be copied.
7.2 Structure MDE (meta data dntry) in MetaDataTable stream file
Table 5 – Structure of MDE
RBP Length
Field name Contents
in bytes
0 1 MDE TYPE uimsbf
1 1 Version VER
2 2 Length of MDE structure (=n) uimsbf
4 n MDE TYPE specific area
7.2.1 MDE TYPE
This field represents the MDE TYPE specific area. The interpretation of MDE TYPE is
described in Table 6.
Table 6 – MDE TYPE interpretation
MDE TYPE Interpretation
0x0 Shall mean that the following MDE TYPE specific
field has no meaning
0x1 Shall mean that the MDE TYPE is a TYPE 1
0x2-0xFF Reserved
7.2.2 TYPE 1 MDE TYPE specific area (Version1.0)
The TYPE 1 MDE TYPE specific area is defined in Table 7. TYPE 1 MDE is defined for storing
metadata of the Japanese digital broadcast services.
Table 7 – Structure of TYPE 1 MDE
RBP Length
Field name Contents
in bytes
0 1 MDE TYPE uimsbf
1 1 Version VER
2 2 Length of MDE structure uimsbf
4 4 PGR ID uimsbf
8 1 Flag FLMDE
9 1 User ID type uimsbf
– 14 – 62328-3 IEC:2005(E)
10 2 Network_ID uimsbf
12 2 Service_ID uimsbf
14 8 Start_Time GTS
22 88 Title Dstring[80]
110 48 Series_name Dstring[40]
158 2 Episode_number uimbf
160 2 Last episode number uimbf
162 1 Genre (1) uimbf
163 1 Genre (2) uimbf
164 1 Genre (3) uimbf
165 1 Reserved bslbf
166 28 Keyword(1) Dstring[20]
194 28 Keyword(2) Dstring[20]
222 28 Keyword(3) Dstring[20]
250 28 Keyword(4) Dstring[20]
278 28 Keyword(5) Dstring[20]
306 2 User ID uimsbf
7.2.2.1 MDE TYPE
This field shall be set to 0x01.
7.2.2.2 Version
This field shall be set to 0x10. This means Version 1.0.
7.2.2.3 Length of MDE structure
This field shall be set to 308.
7.2.2.4 PGR ID
The PGR ID corresponding to the following metadata shall be stored in this field.
7.2.2.5 Flag
The structure of FLMDE is described in Table 8.
Table 8 – Structure of FLMDE
bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0
Reserved E/A VNOK VNOG VS
7.2.2.5.1 Reserved (bit7)
These bits are reserved for future use and shall be 0b.
7.2.2.5.2 E/A (bit6) [bslbf]
If the unit of the programme is based on one event, the E/A bit shall be set to 1b. If the unit of
the programme is based on one action, the E/A bit shall be set to 0b. If the programme is
stored in the TVRS directory, the value of this field shall be copied from the E/A bit in the flag
in the programme general information described in IEC 62328-2.
62328-3 IEC:2005(E) – 15 –
7.2.2.5.3 VNOK (bit5-3) [uimsbf]
The VNOK bits represents the number of valid keyword fields followed in this field.
7.2.2.5.4 VNOG (bit2-1) [uimsbf]
The VNOG bits represents the number of valid genre fields followed in this field.
7.2.2.5.5 VS (bit0) [bslbf]
If the VS bit is set to 1b, the following series name field, episode number field, last episode
number field and series ID shall be valid. If the VS bit is 0b, those fields may be invalid.
7.2.2.6 User ID type
This field describes the type of user ID field. The interpretation of the user ID type is
described in Table 9.
Table 9 – User ID type Interpretation
PI_ TYPE Interpretation
0x0 Shall mean that the user ID field is invalid
0x1-0xBF Reserved
0xC0-0xFE Shall mean that the user ID Type is vender-specific type
0xFF Reserved
7.2.2.7 Network ID
The Network ID may be stored. If the programme identification type of broadcasting TV
programme information is 0x01 or 0x80, which means ISDB specific type or D-VHS specific
type, the value of this field shall be copied from the transport stream ID field in TYPE1
broadcasting TV programme information.
7.2.2.8 Service ID
The service ID may be stored. If the programme identification type of broadcasting TV
programme information is 0x01 or 0x80, which means ISDB specific type or D-VHS specific
type, the value of this field shall be copied from the service ID field in TYPE1 broadcasting TV
programme information.
7.2.2.9 Start time
The programme start time may be stored. If the programme identification type of broadcasting
TV programme information is 0x01 or 0x80, which means ISDB specific type or D-VHS
specific type, the value of this field shall be converted from the value of the event start time
field in the TYPE 1 broadcasting TV programme information.
NOTE The timestamp format of this field is different from that of the broadcasting TV programme information. The
conversion of the timestamp is needed.
7.2.2.10 Title
The title of the programme may be stored. If the programme identification type of
broadcasting TV programme information is 0x01 or 0x80, which means ISDB specific type or
D-VHS specific type, the value of this field may be copied from the event_name_char field in
the short_event_descriptor in broadcasting TV programme information.
– 16 – 62328-3 IEC:2005(E)
7.2.2.11 Series_name
If the VS bit of the flag field is 1b, the series name of the programme shall be stored.
Otherwise, this field shall be ignored. If the programme identification type of broadcasting TV
programme information is 0x01 or 0x80, which means ISDB specific type or D-VHS specific
type, the value of this field may be copied from series_name_char field in series_descriptor in
the broadcasting TV programme information.
7.2.2.12 Episode_number
If the VS bit of the flag field is 1b, the episode number of the programme shall be stored.
Otherwise, this field shall be ignored. If the VS bit is 1b and the value of this field is 0x0000,
this means that the episode number is undefined. If the programme identification type of the
broadcasting TV programme information is 0x01 or 0x80, which means ISDB specific type or
D-VHS specific type, the value of this field may be copied from the episode_number field in
the series_descriptor in the broadcasting TV programme information.
7.2.2.13 Last_episode_number
If the VS bit of the flag field is 1b, the last episode number of the programme shall be stored.
Otherwise, this field shall be ignored. If the VS bit is 1b and the value of this field is 0x0000,
this means that the last episode number is undefined. If the programme identification type of
the broadcasting TV programme information is 0x01 or 0x80, which means ISDB specific type
or D-VHS specific type, the value of this field may be copied from the last_episode_number
field in the series_descriptor in the broadcasting TV programme information.
7.2.2.14 Genre (1)
If the VNOG in the flag field is greater than, or equal to, one, the genre of the programme
shall be stored in this field. Otherwise, this field shall be ignored. If the programme
identification type of broadcasting TV programme information is 0x01, which means ISDB
specific type, the most significant 4 bits correspond to the content_nibble_level_1 field in the
content_descriptor and the least significant 4 bits correspond to the content_nibble_level_2
field in the content_descriptor. The value of this field may be copied from the
content_nibble_level_1 and content_nibble_level_2 field in the content_descriptor in the
broadcasting TV programme information.
7.2.2.15 Genre (2)
If the VNOG in the flag field is greater than, or equal to, two, the genre of the programme
shall be stored in this field. Otherwise, this field shall be ignored. If the programme
identification type of broadcasting TV programme information is 0x01, which means ISDB
specific type, the most significant 4 bits correspond to the content_nibble_level_1 field in the
content_descriptor and the least significant 4 bits correspond to the content_nibble_level_2
field in the content_descriptor. The value of this field may be copied from the
content_nibble_level_1 and content_nibble_level_2 field in the content_descriptor in the
broadcasting TV programme information.
7.2.2.16 Genre (3)
If the VNOG in the flag field is equal to three, the genre of the programme shall be stored in
this field. Otherwise, this field shall be ignored. The most significant 4 bits correspond to the
content_nibble_level_1 field in the content_descriptor and the least significant 4 bits
correspond to the content_nibble_level_2 field in the content_descriptor. If the programme
identification type of broadcasting TV programme information is 0x01, which means ISDB
specific type, the value of this field may be copied from the content_nibble_level_1 and
content_nibble_level_2 field in the content_descriptor in the broadcasting TV programme
information.
62328-3 IEC:2005(E) – 17 –
7.2.2.17 Reserved
This field shall be reserved for future standardization and all bytes shall be set to 0x00.
7.2.2.18 Keyword (1)
If the VNOC in the flag field is greater than, or equal to, one, a keyword shall be stored in this
field. Otherwise, this field shall be ignored. If the programme identification type of
broadcasting TV programme information is 0x01, which means ISDB specific type, the value
of this field may be extracted from the text_char field in the extended_event_descriptor in the
broadcasting TV programme information.
7.2.2.19 Keyword (2)
If the VNOC in the flag field is greater than, or equal to, two, a keyword shall be stored in this
field. Otherwise, this field shall be ignored. If the programme identification type of
broadcasting TV programme information is 0x01, which means ISDB specific type, the value
of this field may be extracted from the text_char field in the extended_event_descriptor in the
broadcasting TV programme information.
7.2.2.20 Keyword (3)
If the VNOC in the flag field is greater than, or equal to, three, a keyword shall be stored in
this field. Otherwise, this field shall be ignored. If the programme identification type of
broadcasting TV programme information is 0x01, which means ISDB specific type, the value
of this field may be extracted from the text_char field in the extended_event_descriptor in the
broadcasting TV programme information.
7.2.2.21 Keyword (4)
If the VNOC in the flag field is greater than, or equal to, four, a keyword shall be stored in this
field. Otherwise, this field shall be ignored. If the programme identification type of the
broadcasting TV programme information is 0x01, which means ISDB specific type, the value
of this field may be extracted from the text_char field in the extended_event_descriptor in the
broadcasting TV programme information.
7.2.2.22 Keyword (5)
If the VNOC in the flag field is grater than, or equal to, five, a keyword shall be stored in this
field. Otherwise, this field shall be ignored. If the programme identification type of the
broadcasting TV programme information is 0x01, which means ISDB specific type, the value
of this field may be extracted from the text_char field in the extended_event_descriptor in the
broadcasting TV programme information.
7.2.2.23 User ID
If the value of the user ID type field is not 0x00, the user ID of the user by which the
programme is recorded shall be stored. The value 0xFFFF means the user is undefined.
7.3 Program information in PROGxxxx.PIF file
Information that is related to a TV programme and is often referred by users is stored in
programme information. Programme information consists of four kinds of information shown
Figure 1.
– 18 – 62328-3 IEC:2005(E)
Program general information
Broadcasting TV programme
Programme information
information
Recording information
Component information
IEC 1142/05
Figure 1 – Structure of programme information
7.3.1 Programme general information in programme information
The structure of programme general information is described in Table 10.
Table 10 – Structure of programme general information
RBP Length
Field name Contents
in bytes
0 4 Programme information length uimsbf
4 1 Programme identification type uimsbf
5 1 Recorded stream type uimsbf
6 1 Service type uimsbf
7 1 Flag FLPGI
8 136 Stream recorded location Dstring[128]
144 4 Broadcasting TV programme information start address uimsbf
148 4 Recording information start address uimsbf
152 4 Component information start address uimsbf
7.3.1.1 Programme identification type (PI_TYPE)
This field describes the type of programme. The programme identification type defines the
type of recorded AV stream and is described in Table 11.
Table 11 – Programme identification type interpretation
PI_ TYPE Interpretation
0x0 Shall mean that the following PI_TYPE specific field has no meaning
0x1 Shall mean that the PI_TYPE is the ISDB specific type for Japanese digital TV
0x2-0x7F Reserved
0x80 Shall mean that the PI_TYPE is the D-VHS specific type for analogue TV
0x81-0xBF Reserved
0xC0-0xFE Shall mean that the PI_TYPE is vendor-specific type
0xFF Reserved
If the PI_TYPE is 0x1, the format of the recorded AV stream complies with the partial TS
format for Japanese digital TV. The abstract of the format is described in Clause B.1. If the
PI_TYPE is 0x80, the format of the recorded AV stream complies with the partial TS format
defined in the D-VHS MPEG transport stream specification and the D-VHS MPEG transport
stream service information specification.
62328-3 IEC:2005(E) – 19 –
7.3.1.2 Service type
This field describes the service type of the broadcasting TV programme. The value of this
field may be copied from the service_type field of the corresponding broadcaster in the
service_list_descriptor. If the PI_TYPE is 0x80, the value of this field shall be 0x00.
Table 12 – Service type interpretation
Service type Interpretation
0x00 Shall mean that the service type has no meaning
0x01 Shall mean that the service type is the digital TV service
0x02 Shall mean that the service type is the digital audio service
0x03 – 0xBF Reserved
0xC0 Shall mean that the service type is the data service
0xC1-0xFF Reserved
7.3.2 Broadcasting TV programme information (BTVPI)
The structure of BTVPI is described in Table 13.
Table 13 – Structure of broadcasting TV programme information
RBP Length
Field name Contents
in bytes
0 1 BTVPI TYPE uimsbf
1 3 Length of broadcasting TV programme
uimsbf
information
4 BTVPI TYPE specific field uimsbf
7.3.2.1 BTVPI TYPE
This field represents the type of the BTVPI TYPE, the interpretation of which is described in
Table 14.
Table 14 – BTVPI TYPE interpretation
BTVPI
Interpretation
TYPE
0x0 Shall mean that the following BTVPI TYPE specific field has no
meaning
0x1 Shall mean that the broadcasting TV programme information is of
TYPE 1
0x2-0xFF Reserved
7.3.2.2 TYPE 1 broadcasting TV programme information
TYPE 1 broadcasting TV programme information is described in Table 15. If the value of the
PI_TYPE field in the programme general information is equal to 0x01, which means ISDB
specific type, or 0x80, which means D-VHS specific type, the TYPE 1 broadcasting TV
programme information shall be used.
– 20 – 62328-3 IEC:2005(E)
Table 15 – Structure of TYPE1 broadcasting TV programme information
RBP Length
Field name Contents
in bytes
0 1 BTVPI TYPE uimsbf
1 3 Length of broadcasting TV
uimsbf
programme information
4 2 Original network ID uimsbf
6 2 Transport stream ID uimsbf
8 2 Service ID uimsbf
10 2 Event ID uimsbf
12 5 Event start time bslbf
17 3 Duration uimsbf
20 N Descriptors descriptors
7.3.2.2.1 BTVPI TYPE
BTVPI TYPE shall be 1.
7.3.2.2.2 Length of broadcasting TV programme information
This field describes the length of the broadcasting TV programme information in bytes.
7.3.2.2.3 Original network ID
In the case of the ISDB specific type (PI_TYPE = 0x1), if the E/A bit of the flag field in
programme general information is 1b, which means the unit of the programme is based on
one event, this field describes the value of the original_network_id of the programme. If the
E/A bit of the flag field in the programme general information is 0b, the value of this field may
be 0xFFFF, which means this field is undefined. The value of this field may be copied from
the original_network_id field in NIT.
In the case of D-VHS specific type (PI_TYPE = 0x80), the value of this field shall be 0xFFFF.
7.3.2.2.4
...




Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...