- •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
78 |
ETSI ES 201 980 V4.1.2 (2017-04) |
When the Time and date data entity or announcement support and switching data entity is included in the SDC, and alternative frequencies are signalled, then a semi-dynamic use of the SDC is recommended. In this case one or more SDC blocks in the cycle defined by the AFS index are signalled to be invalid by use of the FAC Identity field thereby allowing the content of those blocks to be changed continuously, whilst other SDC blocks are always signalled as valid by use of the FAC Identity field thereby allowing the AFS function to be performed. An example of changing the SDC content and of using the semi-dynamic scheme with the AFS index = 1 is given in annex G.
A change of the AFS index is only allowed at reconfiguration.
6.4.6Signalling of reconfigurations
6.4.6.0Introduction
The DRM Multiplex may be reconfigured at transmission super frame boundaries.
Reconfiguration of the DRM multiplex shall be signalled in advance in order to permit receivers to make the best decisions about how to handle the changes. There are two types of reconfiguration: a service reconfiguration, which concerns the reallocation of the data capacity between the services of the MSC, changes in the MSC protection level or changes in the source coding or data applications; and a channel reconfiguration, which concerns changes to the channel parameters or robustness mode.
Both types of reconfiguration are signalled by setting the FAC reconfiguration index to a non-zero value. The index then counts down on each subsequent transmission super frame. The reconfiguration index shall be identical for all transmission frames of a transmission super frame. The final transmission super frame corresponding to the current configuration shall be that in which the reconfiguration index = 1. The new configuration takes effect for the next transmission super frame and in which the reconfiguration index = 0.
All data entity types that use the reconfiguration mechanism for the version flag that are present in the current configuration, and all data entity types that use the reconfiguration mechanism for the version flag that are required in the new configuration, shall be sent during the period when the reconfiguration index is non-zero with the version flag indicating the next configuration. This shall include data entity type 10 that signals the FAC channel parameters for the new configuration.
6.4.6.1Service reconfigurations
A service reconfiguration is one in which the data capacity of the MSC is reallocated between services. This happens when the number of services in the multiplex is changed or the size of data streams is changed. A service reconfiguration shall also be signalled if any of the content of the data entity types using the reconfiguration mechanism of the version flag changes. The reconfiguration shall be signalled as far in advance as possible in order to provide the greatest chance that the receiver gets all the information necessary for the next configuration. Therefore the reconfiguration index shall first take the value 7. In most cases the receiver can follow service reconfigurations without interruption to the audio (see annex Q).
When a new service is introduced, and the overall capacity of the MSC is not changed, then the receiver shall follow the currently selected service through the reconfiguration. To facilitate this, the Service identifier and Short Id of all continuing services shall remain the same. The new service shall use a Short Id that is not used in the current configuration. The one exception to this rule is if there are four services in the current configuration and four services in the new configuration. In this case, if the currently selected service is discontinued, then the receiver follows to the new service with the same Short Id if it is of the same type (e.g. both are audio services).
If the currently selected service is discontinued at the reconfiguration, then the receiver may try to find another source of that service on another frequency and/or system by using the information from data entity types 3 and 11.
ETSI