- •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
|
72 |
ETSI ES 201 980 V4.1.2 (2017-04) |
160 to 182: |
DAB channels L1 to L23 |
(L-Band, Canadian grid) |
Additional information on Alternative Frequency Signalling is provided in annexes F and G.
6.4.3.13Language and country data entity - type 12
The language and country data entity allows addition language and country information to be signalled. This data entity uses the unique mechanism for the version flag. The information is as follows:
• |
Short Id |
2 bits. |
• |
rfu |
2 bits. |
• |
language code |
24 bits. |
• |
country code |
16 bits. |
The following definitions apply:
Short Id: this field indicates the short Id for the service concerned.
rfu: these 2 bits are reserved for future use of the remainder of the parameter field and shall be set to zero until defined.
Language code: this 24-bit field identifies the language of the target audience of the service according to ISO 639-2 [5] using three lower case characters as specified by ISO/IEC 8859-1 [7]. If the language is not specified, the field shall contain three "-" characters.
Country code: this 16-bit field identifies the country of origin of the service (the site of the studio) according to
ISO 3166 [6] using two lower case characters as specified by ISO/IEC 8859-1 [7]. If the country code is not specified, the field shall contain two "-" characters.
6.4.3.14Alternative frequency signalling: detailed region definition data entity - type 13
This data entity allows the definition of geographic areas for which a set of alternative frequencies is provided. This data entity uses the list mechanism for the version flag.
A region can be specified as a geographical area using longitude/latitude and extent values. A range of areas is defined in terms of multiples of 1/16th × 1/16th degree 'squares'. It therefore gives a resolution per square of (EW × NS)
7 km × 7 km (at equator) or 2 km × 7 km at 70° latitude.
This information is as follows:
• |
Region Id |
4 bits. |
• |
m Squares |
m × 48 bits. |
Where each Square is defined as:
• |
rfu |
1 bit. |
• |
Square Latitude |
12 bits. |
• |
Square Longitude |
13 bits. |
• |
Square Latitude Extent |
11 bits. |
• |
Square Longitude Extent |
11 bits. |
ETSI
73 |
ETSI ES 201 980 V4.1.2 (2017-04) |
The following definitions apply:
Region Id: this field indicates the identifier for this region definition. Up to 15 different geographic regions with an individual Region Id (values 1 to 15) can be defined; the value 0 shall not be used, since it indicates "unspecified geographic area" in data entity type 3 and 11. The Region Id values are commonly used for SDC data entities 7 and 13; area definitions per Region Id can be specified by any combination of SDC entities 7 and 13 (see table 24 for limitations).
m Squares: this field carries m definitions of Squares (m in the range 1 to 16). Each Square is coded as a 48-bit field with the following elements:
rfu: this 1 bit is reserved for future use of the remainder of the SDC entity parameter field and shall be set to zero until defined.
Square Latitude: this field specifies the southerly point of the area in 1/16th degrees, as a 2's complement number between -90 (south pole) and +90 (north pole).
Square Longitude: this field specifies the westerly point of the area in 1/16th degrees, as a 2's complement number between -180 (west) and +179 15/16th (east).
Square Latitude Extent: this field specifies the size of the area to the north, in 1/16th degree steps; the value of Latitude plus the value of Latitude Extent shall be equal or less than 90.
Square Longitude Extent: this field specifies the size of the area to the east, in 1/16th degree steps; the value of Longitude plus the value of Longitude Extent may be equal to or exceed the value +180 (i.e. wrap into the region of negative longitude values).
To check whether a certain longitude value is inside the specified longitude range, the formula specified for SDC data entity type 7 shall be used.
This data entity can be used in combination with data entity type 7 which defines the geographic regions with lower resolution as well as the mandatory formula in pseudo program code for evaluating squares.
Additional information on Alternative Frequency Signalling is provided in annexes F and G.
6.4.3.15Packet stream FEC parameters data entity - type 14
MSC streams carrying data service components in packet mode may have additional error protection added to the packet stream (see clause 6.6.5). The FEC parameters for the packet mode stream are described by this data entity.
This data entity uses the reconfiguration mechanism for the version flag. The general form of the entity is as follows:
• |
Stream Id |
2 bits. |
• |
rfu |
2 bits. |
• |
R |
8 bits. |
• |
C |
8 bits. |
• |
packet length |
8 bits. |
The following definitions apply:
Stream Id: this field indicates the stream Id of the stream which has additional error protection applied.
rfu: these 2 bits are reserved for future use of the whole data entity and shall be set to zero until defined.
R: this field, coded as an unsigned binary integer in the range 1 to 180, indicates the value of the R parameter (see clause 6.6.5.1).
C: this field, coded as an unsigned binary integer in the range 1 to 239, indicates the value of the C parameter (see clause 6.6.5.1).
ETSI