FIG Type 0 - mattpascoe135/dab GitHub Wiki

#Type 0 The FIG type 0 is used to signal the current and future multiplex configuration, a multiplex re-configuration, time and date and other basic Service Information. The structure of the FIG type 0 data field is shown in figure 4.

Type 0

##Header Structure ###Current/Next (C/N) This 1-bit flag shall indicate one of two situations, as follows:

a). the type 0 field applies to the current or the next version of the multiplex configuration, as follows:

0: current configuration;

1: next configuration.

The C/N flag applies to situation (a) for the Extensions associated with multiplex configuration features: these are Extensions 1 to 4, 8 and 14 (see also clause 6 in etsi).
b). the type 0 field carries information for a database. The database may be large and require more than one FIG to transport. The C/N flag indicates the Service Information Version (SIV). Certain Extensions divide the database into smaller portions each addressed by use of a database key. When the database is defined, the C/N flag is used to indicate the first FIG carrying data for the database or subsequent FIGs. Any change to the contents of the database is signalled by sending a Change Event Indication (CEI) which is a FIG with certain parameters set to particular values.

When the database is being defined, the C/N flag is used as follows:

0: start of database

1: continuation of database.

When a change to the database needs to be signalled, using the CEI, the C/N flag is used as follows:

0: change event

1: reserved for future use.

The C/N flag applies to situation (b) for Extensions 6, 9, 11, 18, 21, 22, 24, 25, and 27 (see clauses 8.1.15, 8.1.3.2, 8.1.16.1, 8.1.6.1, 8.1.8, 8.1.9, 8.1.10.2, 8.1.10.5.1 and 8.1.11.2.1, respectively). The database key and CEI are defined individually for each Extension.

For those Extensions which do not use this flag, the bit b7 shall be reserved for future use of the type 0 field. This Reserved for future use (Rfu) bit shall be set to "0" for the currently specified extension field and type 0 field.

###Other Ensemble (OE) This 1-bit flag shall indicate whether the information is related to this or another ensemble, as follows:

0: this ensemble

1: other ensemble (or FM or AM or DRM service).

The OE flag is used to indicate "other ensembles" for Extensions 6, 13, 16, 17, 21, and 24 (see clauses 8.1.15, 8.1.20, 8.1.4, 8.1.5.1, 8.1.8 and 8.1.10.2, respectively). For Extensions 16 and 17 it may also indicate FM, AM or DRM services (see clauses 8.1.11.3, 8.1.11.4, 8.1.19.2 and 8.1.19.3). For Extension 21 the OE flag may also indicate FM and AM services (see clauses 8.1.11.1, 8.1.8 and 8.1.19.1).

For those Extensions which do not use this flag, the bit b6 shall be reserved for future use of the type 0 field. This Rfu bit shall be set to "0" for the currently specified Extension field and type 0 field.

###P/D This 1-bit flag shall indicate whether the Service Identifiers (SIds) are in the 16-bit or 32-bit format, as follows:

0: 16-bit SId, used for programme services

1: 32-bit SId, used for data services.

The P/D flag is used for Extensions 2, 6, 8, 9, 13 and 24 (see clauses 6.3.1, 8.1.15, 6.3.6, 8.1.3.2, 8.1.20 and 8.1.10.2, respectively). When the P/D flag is not used, the Service Identifier (SId) takes the 16-bit format.

For those Extensions which do not use this flag, the bit b5 shall be reserved for future use of the type 0 field. This Rfu bit shall be set to "0" for the currently specified extension field and type 0 field.

NOTE: 16-bit and 32-bit Service Identifiers may not be mixed in the same type 0 field.

###Extension This 5-bit field, expressed as an unsigned binary number, identifies one of 32 interpretations of the FIG type 0 field (see clauses 6.2, 6.3, 6.4 and 8.1). Those extensions, which are not defined, are reserved for future use.

##Field Structure ###Extension 0 ext. 0