FIG Type 1 - mattpascoe135/dab GitHub Wiki
#Type 1 The FIG type 1 is used to signal labels for display. The structure of the FIG type 1 data field is shown in figure 5.
The following definitions apply:
###Charset: this 4-bit field shall identify a character set to qualify the character information contained in the FIG type 1 field. The interpretation of this field shall be as defined in TS 101 756 [16], table 1.
###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 services).`
The OE flag is used to indicate "other ensembles" for Extensions 0, 1, 4 and 5 (see clauses 8.1.13 and 8.1.14). For Extension 1 it may also indicate an FM or an AM service (see clause 8.1.14.1).
For those extensions which do not use this flag, the bit b3 shall be reserved for future use. The Rfu bit is set to "0" for the currently specified extension field and FIG type 1 field.
###Extension: this 3-bit field, expressed as an unsigned binary number, shall identify one of 8 interpretations of the FIG type 1 field (see clause 8.1). Those extensions, which are not defined, are reserved for future use.
###Identifier field: this field is defined individually for each extension of the FIG type 1 field (see clause 8.1).
###Character field: this 16-byte field shall define the label. It shall be coded as a string of up to 16 characters, which are chosen from the character set signalled by the Charset field in the first byte of the FIG type 1 data field. The characters are coded from byte 15 to byte 0. The first character starts at byte 15.
###Character flag field: this 16-bit flag field shall indicate which of the characters of the character field are to be displayed in an abbreviated form of the label, as follows:
`b_i : (i = 0, ... ,15)'
`0: not to be displayed in abbreviated label`
`1: to be displayed in abbreviated label.`
`NOTE: Not more than 8 of the b_i may be set to "1".`
If the character field contains less than 16 characters, the unused bits in the character flag field (having no corresponding character) shall be set to zero.
#Extension Numbers ##Extension 0 - Ensemble label The ensemble label feature is used to identify the ensemble in a textual format. The feature is encoded in Extension 0 of the FIG type 1 (FIG 1/0) and FIG type 2 (FIG 2/0). Figure 60 shows the structure of the Identifier field for the ensemble label which is part of the Type 1 field (see also figure 5) or part of the Type 2 field (see also figure 6). The OE flag see clause 5.2.2.2) shall be set to "0" for the current ensemble and to "1" for other ensembles.
###Ensemble Identifier (EId): this 16-bit field shall identify the ensemble. The coding details are given in clause 6.4.
##Extension 1 - Programme service label The Programme service label feature is encoded in Extension 1 of the FIG type 1 (FIG 1/1) and FIG type 2 (FIG 2/1). Figure 61 shows the structure of the Identifier field for the service label which is part of the Type 1 field (see also figure 5) or part of the Type 2 field (see also figure 6). The OE flag (see clause 5.2.2.2) shall be set to "0" for the services carried in the current ensemble and set to "1" for services carried in other ensembles.
###Service Identifier (SId): this 16-bit field shall identify the service (see clause 6.3.1).
##Extension 3 The region label feature is encoded in extension 3 of FIG type 1 (FIG 1/3) and FIG type 2 (FIG 2/3). Figure 67 shows the structure of the Identifier field for the region label which is part of the Type 1 field (see also figure 5) or part of the Type 2 field (see also figure 6).
The following definitions apply:
###Rfa: this 2-bit field shall be reserved for future additions. The bits shall be set to zero until they are defined.
###RegionId Lower part: this 6-bit field shall indicate the lower part of the Region Identifier (see clause 8.1.16.1). The RegionId Upper part is assumed to be "00000".
##Extension 4 - Service component label The Service component label feature is encoded in Extension 4 of FIG type 1 (FIG 1/4) and FIG type 2 (FIG 2/4). Figure 63 shows the structure of the Identifier field for the service component label which is part of the Type 1 field (see also figure 5) or part of the Type 2 field (see also figure 6).
The following definitions apply:
###P/D: this 1-bit flag shall indicate whether the Service Identifier (SId) field is used for Programme services or Data services, as follows:
`0: 16-bit SId, used for Programme services`
`1: 32-bit SId, used for Data services.`
###Rfa: this 3-bit field shall be reserved for future additions. The bits shall be set to zero until they are defined.
###SCIdS (Service Components Identifier within the Service): this 4-bit field shall identify the service component within the service. The combination of the SId and the SCIdS provides a service component identifier which is valid globally.
###Service Identifier (SId): this 16-bit or 32-bit field shall identify the service. The length of the SId shall be signalled by the P/D flag, see clause 5.2.2.1.
##Extension 5 - Data service label The Data service label feature is encoded in Extension 5 of the FIG type 1 (FIG 1/5) and FIG type 2 (FIG 2/5). Figure 62 shows the structure of the Identifier field for the service label which is part of the Type 1 field (see also figure 5) or part of the Type 2 field (see also figure 6). The OE flag (see clause 5.2.2.2) shall be set to "0" for the services carried in the current ensemble and set to "1" for services carried in other ensembles.
###Service Identifier (SId): this 32-bit field shall identify the service (see clause 6.3.1).
##Extension 6 - X-PAD user application label The X-PAD User application label feature is encoded in Extension 6 of FIG type 1 (FIG 1/6) and FIG type 2 (FIG 2/6). Figure 64 shows the structure of the Identifier field for the X-PAD user application label which is part of the Type 1 field (see also figure 5) or part of the Type 2 field (see also figure 6).
The following definitions apply:
###P/D: this 1-bit flag shall indicate whether the Service Identifier (SId) field is used for Programme services or Data services, as follows:
0: 16-bit SId, used for Programme services
1: 32-bit SId, used for Data services.
###Rfa: this 3-bit field shall be reserved for future additions. The bits shall be set to zero until they are defined.
###SCIdS (Service Components Identifier within the Service): this 4-bit field shall identify the service component within the service. The combination of the SId and the SCIdS provides a service component identifier which is valid globally.
###Service Identifier (SId): this 16-bit or 32-bit field shall identify the service. The length of the SId shall be signalled by the P/D flag, see clause 5.2.2.1.
###Rfa: this 2-bit field shall be reserved for future additions. The bits shall be set to zero until they are defined.
###Rfu: this 1-bit field shall be reserved for future use of the associated X-PAD application type. The Rfu bits shall be set to zero for the currently specified definition of this associated field.
###X-PAD Application Type: this 5-bit field shall specify the application type (see clause 7.4.3).