011: MPEG Surround with 7.1 output channels.

100:reserved.

101:reserved.

110:reserved.

111:other mode (the mode can be derived from the MPEG Surround data stream).

Receivers with a different number of output channels than the number of target channels indicated by the MPEG Surround mode shall render the multichannel audio signal according to the available number of output channels (possibly at a reduced quality compared to the case where the number of target channels matches the number of output channels).

The number of output channels provided by MPEG Surround is intended as an information for the listener only. The MPEG Surround decoder shall use this information only to determine whether MPEG Surround is used. If MPEG Surround is used (MPEG Surround mode ≠ 000), the MPEG Surround decoder shall exclusively rely on the information contained within the SpatialSpecificConfig(). A decoder that does not support MPEG Surround shall ignore this parameter and only decode the mono or stereo core audio.

codec specific config: this field depends upon the value of the audio coding field as follows:

audio coding field = 00 (AAC), 01 (reserved), or 10 (reserved):

•the field is not present (n = 0). audio coding field = 11 (xHE-AAC):

•xHE-AAC Static Config, as returned by the xHE-AAC encoder upon initialization (n ≥ 0); see clause 5.3.2. The xHE-AAC Static Config bit-field shall be aligned to full bytes by setting the remaining bits of the last byte to 0.

NOTE: A typical value of n for mono and stereo configurations without MPEG Surround is in the range 1 to 7 bytes; the inclusion of MPEG Surround adds up to 17 additional bytes.

rfa: these fields are reserved for future additions and shall be set to zero until defined.

6.4.3.11FAC channel parameters data entity - type 10

This data entity permits the next configuration FAC channel parameters to be specified in advance for service following across reconfigurations. This data entity uses the reconfiguration mechanism for the version flag. The fields are as follows:

•Base/Enhancement flag 1 bit.

ETSI

The following definitions apply:

Base/Enhancement flag: the definition is given in clause 6.3.3.

Robustness mode: this 2-bit field indicates the robustness mode of the new configuration as follows:

RM flag = 0:

00: A.

01: B.

10:C.

11:D. RM flag = 1:

00:E.

01:reserved.

10:reserved.

11:reserved.

RM flag: the definition is given in clause 6.3.3.

Spectrum occupancy: the definition is given in clause 6.3.3.

Interleaver depth flag: the definition is given in clause 6.3.3.

MSC mode: the definition is given in clause 6.3.3.

SDC mode: the definition is given in clause 6.3.3.

Number of services: the definition is given in clause 6.3.3.

rfa: these 4 bits are reserved for future additions and shall be set to zero until defined.

rfu: this 1 bit is reserved for future use of the whole parameter field and shall be set to zero until defined.

If the DRM transmission is being discontinued at the reconfiguration, then this data entity shall be sent with the length field of the header set to 0, and the first four bits of the body field set to 0.

6.4.3.12Alternative frequency signalling: Other services data entity - type 11

For every service of the tuned DRM multiplex alternative sources can be signalled. These alternative sources can be DRM services (using different DRM Service identifiers) or services on other broadcast systems like AM, FM, FM-RDS or DAB. For every service of the tuned DRM multiplex, this type of data entity lists the corresponding Service identifier within a DRM multiplex or another broadcast system, optionally along with the list of alternative frequencies. It uses the list mechanism for the version flag. At least one other Service identifier or one frequency shall be provided in this data entity.

NOTE 1: The list of alternative DRM frequencies for the entire DRM multiplex or some of its services (i.e. using the same Service identifiers) can be derived from "Alternative frequency signalling: Multiple frequency network information data entity - type 3".

NOTE 2: For dynamic service linking and delinking of audio services, "Service linking information data entity - type 15, extension 0" can be used.

The alternative frequencies may be scheduled to certain times and/or restricted to certain geographic areas.

The information is as follows:

ETSI

The following definitions apply:

Short Id/Announcement Id flag: this flag specifies the content of the Short Id/Announcement Id field as follows:

0:Short Id.

1:Announcement Id.

Short Id/Announcement Id field: the content of this field depends upon the value of the Short Id/Announcement Id flag as follows:

Short Id/Announcement Id flag = 0:

Short Id/Announcement Id flag = 1:

Short Id: this field carries the Short Id of the service in the tuned DRM multiplex to which the alternative frequencies apply.

Announcement Id: this field carries the Announcement Id (value 0 to 3). The information for which services in the tuned DRM multiplex announcements are signalled (and which type of announcements) is described by one or more "Announcement support and switching data entity - type 6" (with the "Same Multiplex/Other Service flag" bit set to 1, indicating that the announcement is provided by another service outside the tuned DRM multiplex).

Region/Schedule flag: this field indicates whether the list of frequencies is restricted by region and/or schedule or not as follows:

0:no restriction.

1:region and/or schedule applies to this list of frequencies.

Same Service flag: this flag indicates whether the specified other service should be considered the "same service" (e.g. carrying the identical audio programme) or an "alternative service" (e.g. a different audio programme either from the same broadcaster offering a similar programme or from another broadcaster - see clauses F.6 and G.1):

0:alternate service.

1:same service.

NOTE: When indicating services from another broadcaster; the Short Id field may be set to an arbitrary value. It is recommended that where there are fewer than four services in the multiplex, an unused Short Id should be used.

rfa: these 2 bits are reserved for future additions and shall be set to zero until defined.

ETSI

System Id: this field indicates which broadcast system the Other Service Id and frequency information applies to as follows:

00000: DRM service

Other Service Id: 24 bits (DRM Service identifier).

00001: AM service with AMSS

Other Service Id: 24 bits (AMSS service identifier).

00010: AM service

Other Service Id: not present (AM service identifier not specified).

00011: FM-RDS service (Europe and North America grid) Other Service Id: 24 bits (ECC+PI code).

00100: FM-RDS service (Europe and North America grid) Other Service Id: 16 bits (PI code only).

00101: FM service (Europe and North America grid)

Other Service Id: not present (PI code not specified).

00110: FM-RDS service (Asia grid)

Other Service Id: 24 bits (ECC+PI code).

00111: FM-RDS service (Asia grid)

Other Service Id: 16 bits (PI code only).

01000: FM service (Asia grid)

Other Service Id: not present (PI code not specified).

01001: DAB service

Other Service Id: 24 bits (ECC + audio service identifier).

01010: DAB service

Other Service Id: 16 bits (audio service identifier only).

01011: DAB service

Other Service Id: 32 bits (data service identifier).

all other values: reserved for future definition.

Region/Schedule field: this 8 bit field is only present if the Region/Schedule flag is set to 1. The information is as follows:

•Schedule Id4 bits.

Region Id: this field indicates whether the region is unspecified (value 0) or whether the alternative frequencies are valid just in certain geographic areas, in which case it carries the Region Id (value 1 to 15). The region may be described by one or multiple "Alternative frequency signalling: Region definition data entity - type 7" and/or "Alternative frequency signalling: Region definition data entity - type 13" with this Region Id.

Schedule Id: this field indicates whether the schedule is unspecified (value 0) or whether the alternative frequencies are valid just at certain times, in which case it carries the Schedule Id (value 1 to 15). The schedule is described by one or multiple "Alternative frequency signalling: Schedule definition data entity - type 4" with this Schedule Id.

Other Service Id: this field carries the other service identifier used on the n frequencies. If an extended country code (ECC) is present, it shall precede the service identifier/PI code. The presence and bit length of this field depends upon the type of broadcast system for which the alternative frequencies are specified (see value of the System Id field for details).

ETSI

n frequencies: this field carries n alternative frequency values (n in the range 0 to 16). The bit length and information for every frequency value depends upon the value of the System Id field as follows:

Table 22a

DRM frequency:

each 16 bit field contains the following information:

multiplier: this 1-bit field shall indicate the frequency multiplier as follows:

0:1 (the frequencies field can indicate from 0 to 32 767 kHz in 1 kHz steps; indicated transmission has robustness mode A, B, C or D).

1:10 (the frequencies field can indicate from 0 to 327 670 kHz in 10 kHz steps; indicated transmission has robustness mode E).

frequency value: this 15 bit field is coded as an unsigned integer and gives the frequency in multiples of 1 or 10 kHz, depending on the value of the multiplier field.

AM frequency:

each 16 bit field contains the following information:

rfu: this 1 bit is reserved for future use of the frequency value field and shall be set to zero until defined. frequency value: this 15 bit field is coded as an unsigned integer and gives the frequency in kHz.

FM1 (87,5 MHz to 107,9 MHz) frequency:

FM2 (76,0 MHz to 90,0 MHz) frequency:

ETSI