- •Intellectual Property Rights
- •Foreword
- •Modal verbs terminology
- •Introduction
- •1 Scope
- •2 References
- •2.1 Normative references
- •2.2 Informative references
- •3 Definitions, symbols, abbreviations and conventions
- •3.1 Definitions
- •3.2 Symbols
- •3.3 Abbreviations
- •3.4 Conventions
- •4 General characteristics
- •4.1 System overview
- •4.2 System architecture
- •4.3 Audio source coding
- •4.4 Transmission modes
- •4.4.1 Signal bandwidth related parameters
- •4.4.2 Transmission efficiency related parameters
- •4.4.2.0 General
- •4.4.2.1 Coding rates and constellations
- •4.4.2.2 OFDM parameter set
- •5 Source coding modes
- •5.1 Overview
- •5.1.0 Introduction
- •5.1.2 AAC audio coding
- •5.1.3 MPEG Surround coding
- •5.2 Audio super framing
- •5.3.1.0 Introduction
- •5.3.3.0 Introduction
- •5.3.3.1 Frequency Domain coding (AAC based coding and TCX)
- •5.3.3.2 ACELP
- •5.3.3.4 MPS212 parametric stereo
- •5.3.3.5 MDCT based Complex Prediction
- •5.3.3.6 Forward Aliasing Cancellation
- •5.4 AAC coding
- •5.4.3 Parametric Stereo coding
- •5.4.4 AAC error concealment
- •5.4.4.0 Introduction
- •5.4.4.1 Interpolation of one corrupt frame
- •5.4.4.3 Concealment granularity
- •5.4.4.4 SBR error concealment
- •5.4.4.5 Parametric Stereo concealment
- •6 Multiplex definition
- •6.1 Introduction
- •6.2 Main Service Channel (MSC)
- •6.2.1 Introduction
- •6.2.2 Structure
- •6.2.3 Building the MSC
- •6.2.3.0 Introduction
- •6.2.3.1 Multiplex frames
- •6.2.3.2 Hierarchical frames
- •6.2.4 Reconfiguration
- •6.3 Fast Access Channel (FAC)
- •6.3.1 Introduction
- •6.3.2 Structure
- •6.3.3 Channel parameters
- •6.3.4 Service parameters
- •6.3.6 FAC repetition
- •6.4 Service Description Channel (SDC)
- •6.4.1 Introduction
- •6.4.2 Structure
- •6.4.3 Data entities
- •6.4.3.0 Introduction
- •6.4.3.1 Multiplex description data entity - type 0
- •6.4.3.2 Label data entity - type 1
- •6.4.3.3 Conditional access parameters data entity - type 2
- •6.4.3.4 Alternative frequency signalling: Multiple frequency network information data entity - type 3
- •6.4.3.5 Alternative frequency signalling: Schedule definition data entity - type 4
- •6.4.3.6 Application information data entity - type 5
- •6.4.3.7 Announcement support and switching data entity - type 6
- •6.4.3.8 Alternative frequency signalling: Region definition data entity - type 7
- •6.4.3.9 Time and date information data entity - type 8
- •6.4.3.10 Audio information data entity - type 9
- •6.4.3.11 FAC channel parameters data entity - type 10
- •6.4.3.12 Alternative frequency signalling: Other services data entity - type 11
- •6.4.3.13 Language and country data entity - type 12
- •6.4.3.14 Alternative frequency signalling: detailed region definition data entity - type 13
- •6.4.3.15 Packet stream FEC parameters data entity - type 14
- •6.4.3.16 Extension data entity - type 15
- •6.4.3.16.0 General
- •6.4.3.16.1 Service linking information data entity - type 15, extension 0
- •6.4.3.16.2 Other data entity type 15 extensions
- •6.4.4 Summary of data entity characteristics
- •6.4.5 Changing the content of the SDC
- •6.4.6 Signalling of reconfigurations
- •6.4.6.0 Introduction
- •6.4.6.1 Service reconfigurations
- •6.4.6.2 Channel reconfigurations
- •6.5 Text message application
- •6.6 Packet mode
- •6.6.0 Introduction
- •6.6.1 Packet structure
- •6.6.1.0 Introduction
- •6.6.1.1 Header
- •6.6.1.2 Data field
- •6.6.2 Asynchronous streams
- •6.6.3 Files
- •6.6.4 Choosing the packet length
- •6.6.5 Forward Error Correction (FEC) for packet mode streams
- •6.6.5.0 Introduction
- •6.6.5.1 Encoding of FEC Packets
- •6.6.5.2 Transport of FEC packets
- •6.6.5.3 Receiver considerations
- •7 Channel coding and modulation
- •7.1 Introduction
- •7.2 Transport multiplex adaptation and energy dispersal
- •7.2.1 Transport multiplex adaptation
- •7.2.1.0 General
- •7.2.2 Energy dispersal
- •7.3 Coding
- •7.3.1 Multilevel coding
- •7.3.1.0 Introduction
- •7.3.1.1 Partitioning of bitstream in SM
- •7.3.1.2 Partitioning of bitstream in HMsym
- •7.3.1.3 Partitioning of bitstream in HMmix
- •7.3.2 Component code
- •7.3.3 Bit interleaving
- •7.3.3.0 Introduction
- •7.4 Signal constellations and mapping
- •7.5 Application of coding to the channels
- •7.5.1 Coding the MSC
- •7.5.1.0 Introduction
- •7.5.1.2 HMsym
- •7.5.1.3 HMmix
- •7.5.2 Coding the SDC
- •7.5.3 Coding the FAC
- •7.6 MSC cell interleaving
- •7.7 Mapping of MSC cells on the transmission super frame structure
- •8 Transmission structure
- •8.1 Transmission frame structure and robustness modes
- •8.3 Signal bandwidth related parameters
- •8.3.1 Parameter definition
- •8.3.2 Simulcast transmission
- •8.4 Pilot cells
- •8.4.1 Functions and derivation
- •8.4.2 Frequency references
- •8.4.2.0 Introduction
- •8.4.2.1 Cell positions
- •8.4.2.2 Cell gains and phases
- •8.4.3 Time references
- •8.4.3.0 Introduction
- •8.4.3.1 Cell positions and phases
- •8.4.3.2 Cell gains
- •8.4.4 Gain references
- •8.4.4.0 Introduction
- •8.4.4.1 Cell positions
- •8.4.4.2 Cell gains
- •8.4.4.3 Cell phases
- •8.4.4.3.0 Intorduction
- •8.4.4.3.1 Procedure for calculation of cell phases
- •8.4.4.3.2 Robustness mode A
- •8.4.4.3.3 Robustness mode B
- •8.4.4.3.4 Robustness mode C
- •8.4.4.3.5 Robustness mode D
- •8.4.4.3.6 Robustness mode E
- •8.4.5 AFS references
- •8.4.5.0 Introduction
- •8.4.5.1 Cell positions and phases
- •8.4.5.2 Cell gains
- •8.5 Control cells
- •8.5.1 General
- •8.5.2 FAC cells
- •8.5.2.1 Cell positions
- •8.5.2.2 Cell gains and phases
- •8.5.3 SDC cells
- •8.5.3.1 Cell positions
- •8.5.3.2 Cell gains and phases
- •8.6 Data cells
- •8.6.1 Cell positions
- •8.6.2 Cell gains and phases
- •B.1 Robustness modes A, B, C and D
- •B.2 Robustness mode E
- •F.0 Introduction
- •F.2 Possibilities of the announcement feature
- •F.3 SDC data entities overview for Alternative Frequency and announcement signalling
- •F.4 SDC data entities and setup for alternative frequency signalling
- •F.5 SDC data entities and setup for announcement
- •F.6 Alternative frequency and announcement signalling - coding example
- •G.0 Introduction
- •G.1 Alternative Frequency checking and Switching (AFS)
- •G.2 Station buttons for DRM services
- •G.3 Seamless Alternative Frequency checking and Switching (AFS)
- •G.4 Character sets
- •Annex I: (void)
- •Annex N: (void)
- •R.1 Overview
- •R.2 General network timing considerations
- •R.3 Network synchronization rules
- •R.4 Receiver implementation rules
- •R.5 Definition of broadcast signal time references
- •T.0 Introduction
- •T.1 Domestic services
- •T.2 International services
- •History
74 |
ETSI ES 201 980 V4.1.2 (2017-04) |
packet length: this field, coded as an unsigned integer in the range 1 to 255, indicates the length in bytes of the data field of each packet (the total packet length is three bytes longer as it includes the header and CRC fields).
NOTE: All packets contained in one data stream have the same length (see clause 6.6.4).
6.4.3.16Extension data entity - type 15
6.4.3.16.0General
To permit additional data entities to be defined, data entity type 15 is used. The first four bits of the body of the data entity contain the data entity Extension type field.
6.4.3.16.1Service linking information data entity - type 15, extension 0
Service linking information can be used to link together services carrying exactly the same content (hard link) or carrying related content (soft link). This data entity uses the list mechanism for the version flag.
The information is as follows:
• |
Extension type == 0000 |
4 bits. |
• |
Id (Identifier) list flag |
1 bit. |
• |
LA (Linkage Actuator) |
1 bit. |
• |
S/H (Soft/Hard) |
1 bit. |
• |
ILS indicator |
1 bit. |
• |
LSN (Linkage Set Number) |
12 bits. |
• |
Rfu |
1 bit. |
• |
IdLQ (Identifier List Qualifier) |
2 bits. |
• |
Data flag |
1 bit. |
• |
Number of Ids: |
4 bits. |
• |
n Ids |
n × (16 or 24 or 32) bits. |
The following definitions apply:
Extension type: this 4-bit field shall be set to 0000 to indicate the correct extension for service linking information.
Id (Identifier) list flag: this 1-bit flag shall indicate whether the n Ids, together with the preceding byte, is present or not, as follows:
0:Rfu, IdLQ, Data flag, Number of Ids, and n Ids absent;
1:Rfu, IdLQ, Data flag, Number of Ids, and n Ids present.
LA (Linkage Actuator): this 1-bit flag shall indicate whether the link is active or inactive (potential), as follows:
0:potential future link or de-activated link;
1:active link.
S/H (Soft/Hard): this 1-bit flag shall indicate whether the link is soft or hard, as follows:
0:Soft link (related services);
1:Hard link (services carrying the same content).
ETSI
75 |
ETSI ES 201 980 V4.1.2 (2017-04) |
ILS indicator: this 1-bit flag shall indicate whether the link affects only one country (national) or several countries (international), as follows:
0:national link;
1:international link (or DRM or AMSS).
Linkage sets which include services broadcast using DRM or AMSS shall always be an international link, even if all linked services are intended for national use.
NOTE: It is possible but not recommended to signal linkage sets that do not include DRM services.
LSN (Linkage Set Number): this 12-bit field represents a number which shall be common to all Services linked together as a set. The use of LSN = "0000 0000 0000" is reserved.
For an international link, the LSN shall be structured according to IEC 62106 [13].
Rfu: this 1-bit field shall be reserved for future use of the IdLQ, the Rfa, the Number of Ids and the Id list fields. The Rfu bit shall be set to zero for the currently specified definition of the associated fields.
IdLQ (Identifier List Qualifier): this 2-bit field shall indicate how the identifiers, contained in the Id list, are qualified, as follows:
b6 - b5
0 0 : each Id represents a DAB service (see ETSI EN 300 401 [3]);
01 : each Id represents an RDS service (see IEC 62106 [13]);
10 : not used;
1 1 : each Id represents a DRM or AMSS Service (see ETSI TS 102 386 [14]).
Data flag: this 1-bit field is shall indicate whether each Id corresponds to a DAB data service or not, as follows:
0:each Id does not correspond to a DAB data service;
1:each Id corresponds to a DAB data service.
Number of Ids: this 4-bit field, expressed as an unsigned binary number, shall specify the number of identifiers in the Id list (maximum 15).
n Ids: this field carries n service identifiers (n in the range 1 to 15). The bit length and information for every Id value depends upon the value of the IdLQ, ILS indicator and Data flag fields as follows:
Table 22b
IdLQ field value |
ILS indicator |
Data flag |
Id field contains |
Id field length |
|
00 |
|
1 |
0 |
8-bit ECC + 16 bit DAB SId |
24 bits |
00 |
|
1 |
1 |
32-bit DAB SId |
32 bits |
01 |
|
1 |
0 |
8-bit ECC + 16 bit RDS PI code |
24 bits |
11 |
|
1 |
0 |
24-bit DRM or AMSS Service identifier |
24 bits |
|
|
|
|
|
|
00 |
|
0 |
0 |
16-bit DAB SId |
16 bits |
00 |
|
0 |
1 |
32-bit DAB SId |
32 bits |
01 |
|
0 |
0 |
16-bit RDS PI code |
16 bits |
NOTE: |
The entries with the ILS indicator set to 0 are for providing linkage sets which only include DAB and/or FM- |
||||
|
RDS services. |
|
|
|
|
The operational use of this data entity is identical to that of the DAB FIG 0/6, see ETSI TS 103 176 [15].
6.4.3.16.2Other data entity type 15 extensions
Other data entity type 15 extensions are reserved for future definition.
ETSI
