Document number Author / Prepared

Document name / type

Revision/version

FAQ & Compare requirements DVB-T2 IRDs

Ptu
Document responsible/Approved

Draft V014

Page Date

1 (3) 2012-04-26

Per Tullstedt

FAQ Teracom and Boxer DVB Receiver requirements

FAQ technical IRD requirements 1.
DVB-T2

Q1. Is DVB-T2 required for all IRDs? A1. All new IRDs from 1 January 2013 shall support DVB-T2 (i.e. DVB-T2 is optional but highly recommended for new IRDs that start its selling on the market during 2012). This means that DVB-T1 only IRDs that do not support DVB-T2 and that has passed Teracom and Boxer approval before end 2012 may still be sold with Teracom and Boxer approval during 2013.

2.

DVB-T2

Q2. Is it required to support TFS and 1.7Mhz bandwidth for DVB-T2? A2. No, it is not required for the Teracom/Boxer DVB-T2 IRDs to support TFS nor 1.7 MHz.

3.

CI+

Q3. Is Common Interface Plus extensions (CI+) mandatory for IRDs with Common Interface (CI)? A4. Yes, from 1 January 2012 all new IRDs with CI shall support CI+ extension (i.e. both DVB-T and DVB-T2 IRDs). Q4. HE.AAC/E.AC3/AC3 Multichannel audio decoding down to (2.0) stereo is to any desired format, like AC3 or PCM or is there any preferred factory default mode the IRD shall have? A4. Factory default mode for multichannel audio broadcast after the audio decoding is to down-mix it and output it as stereo PCM on HDMI. IRDs may during viewing let the user change this mode of the output format to e.g. AC3 stereo, AC3 multi or DTS etc as desired or let user change default settings from factory default. (More info see NorDig Unified IRD spec ch 6 requirements and ch 16 factory default).

4.

Multi audio

5.

Audio metadata

Q5. Is there requirements to support and process audio metadata during audio decoding? A5. Yes, for HE-AAC, E-AC3 and AC-3 all IRDs shall support reading and applying any metadata during the audio decoding process, which refers to adjusting loudness control of down-mix and dynamic range. (Audio metadata is not applicable for MPEG1 Layer II audio streams). Observe that not all HE-AAC streams will include audio metadata, in these cases the IRD shall interpret that these audio streams use standard default parameters and loudness.

6.

Teletext subtitling playback for PVRs

Q6. There is a requirement for PVRs to handle good lip sync (relative timing) of the Teletext subtitling during playback also for services which has a Teletext stream without PTS (presentation time stamp). Are there really any such services in the Network? Is it only for services with hard-or-hearing Teletext subtitling? A6. Most of the TV services that have an EBU Teletext in the Swedish DTT network have no PTS in their Teletext stream. Instead IRDs shall use standard decoding buffer model for the Teletext as specified by DVB/ETSI to achieve reasonable good lip sync compared to video and audio. In the network there are both services with normal Teletext subtitling (for translation) and services with HoH Teletext subtitling which has a Teletext stream without PTS and has no DVB Subtitling.

This document is the property of TERACOM AB and may not without our written permission be copied, imparted to a third party or used for any other unauthorized purpose.

Document number Author / Prepared

Document name / type

Revision/version

FAQ & Compare requirements DVB-T2 IRDs

Ptu
Document responsible/Approved

Draft V014

Page Date

2 (3) 2012-04-26

Per Tullstedt

7.

DVB SI HD Simulcast

Q7. There is no mention for the use of HD LCN or HD/SD switching within the SI chapter. Can this be clarified if there is any intention to use these functions? A7. The (DVB-T2) IRD requirements for Teracom/Boxer DTT networks are based on NorDig Unified IRD specification (and not the UK DTG D-book). (The terms HD LCN and HD/SD switching is likely coming from UK-D-book). In NorDig there is no extra descriptor for HD LCN to be used in NIT. Instead NorDig specifies that HDTV services (service type 0x19) shall have priority for a certain LCN compared to a SDTV (service type 0x01, 0x16), see chapter NorDig Unified 12.1.4 and 13.2.1.1. In addition NorDig specifies for HDTV IRDs the capability to (quasi-static) hide the SD version for some HD and SD simulcasting services via the Linkage type 0x82 in SDT (see ch 12.3.4). Dynamic changes in broadcast (like changes of codec MPEG2 SD MPEG4 HD, change of PID values for regional insertion etc), the IRDs shall be able to handle and follow these dynamic changes with some disturbance without user interaction (see 12.1.1 and 6.1.3). Q8. Is the new DVB SI Target Region Descriptor mandatory for T2-IRDs or planned to be used in the DVB-T2 broadcast? A8. No, not at this stage for Swedish DTT network.

8.

DVB SI Target Region Descriptor

9.

Front-End VHF

Q9. Is VHF required and will it really be used in the DVB-T2 broadcast? A9. Yes, VHF band III and UHF band IV-V is required for all IRDs. VHF is used for DVB-T2 (both in the Swedish and Finnish DTT network). Q10. Is DVB new CSA3 required for descrambling? A10. Not at this stage. The CA is still based on the DVB CSA version 2. (The requirement in IRDs for CSA3 has been removed in latest update 27 April 2010. The plan is still to include this in new IRDs from 2012). Q11. OK that all DVB-T and DVB-T2 modes are required for the IRDs, but which mode(s) are actually currently used in the Swedish DTT network? A11. All IRDs shall support all DVB-T/-T2 modes as specified in NorDig Unified. As today the current Swedish DTT network has 3 DVB-T modes (all for UHF band) and 5 DVB-T2 modes (2 for VHF and 3 for UHF band). For more description regarding the used DVB-T/-T2 modes, see below.

10.

CA CSA3

11.

DVB-T/-T2 modes

This document is the property of TERACOM AB and may not without our written permission be copied, imparted to a third party or used for any other unauthorized purpose.

Document number Author / Prepared

Document name / type

Revision/version

FAQ & Compare requirements DVB-T2 IRDs

Ptu
Document responsible/Approved

Draft V014

Page Date

3 (3) 2012-04-26

Per Tullstedt

Planned and used DVB-T/-T2 modes for Swedish DTT network

DVB-T modes, used modes today (some changes my occur in the future)
DVB-T Mode alias DVB-T DVB-T

U11
VHF long UHF UHF IV-V 8 MHz 8K 64-QAM 1/4 3/4 non 22.39 Mux 1-5

U12
normal UHF UHF IV-V 8 MHz 8K 64-QAM 1/8 2/3 non 22.12 Mux 1-5

U13
short UHF UHF IV-V 8 MHz 8K 64-QAM 1/32 2/3 non 24.13 Mux 1-5 Mbps

RF band
Spectrum Bandwidth FFT Modulation Guard Interval Code Rate Hierarchical Bitrate TS Current usage

DVB-T2 modes, as planned today (some changes my occur in the future)

DVB-T2 Mode alias DVB-T2

V21
normal VHF VHF III 7 MHz v1.1.1 64QAM SISO No 32k 19/256 TR-PAPR PP4 2 42 Relative TS HEM* Single 256QAM Yes 64k LDPC 2/3 0 3 No No 30.81 SWE-DTT Mux 7

V22
long VHF VHF III 7 MHz v1.1.1 64QAM SISO No 32k 1/8 TR-PAPR PP2 2 22 Relative TS HEM* Single 256QAM Yes 64k LDPC 3/4 0 3 No No 31.07 SWE-DTT Mux 7

RF band
Spectrum Bandwidth T2 version L1 modulation T2 frame preamble format Extended carrier mode FFT size Guard Interval PAPR reduction Pilot pattern Num T2 frames Lf Timestamp type Payload type PLP mode Single/multiple PLP PLP modulation Rotated constellation FEC type Code Rate Time interleaving type Time interleaving length ISSY Null packet deletion Effective bitrate Current usage

DVB-T2 U21 normal UHF

UHF IV-V 8 MHz v1.1.1 64QAM SISO Yes 32k 19/256 TR-PAPR PP4 2 20 Relative TS HEM* Single 256QAM Yes 64k LDPC 3/5 0 3 No No 31,66 SWE-DTT Mux 7

DVB-T2 U22 normal UHF

UHF IV-V 8 MHz v1.1.1 64QAM SISO Yes 32k 1/16 TR-PAPR PP4 2 62 Relative TS HEM* Single 256QAM Yes 64k LDPC 2/3 0 3 No No 36.55 SWE-DTT Mux 6

DVB-T2 U22b normal UHF

UHF IV-V 8 MHz v1.2.1 64QAM SISO Yes 32k 1/16 TR-PAPR PP4 2 62 Relative TS HEM* Single 256QAM Yes 64k LDPC 2/3 0 3 Yes No 36.55 DNK-DTT Mux 5

DVB-T2 U23 long UHF

UHF IV-V 8 MHz v1.1.1 64QAM SISO Yes 32k 1/8 TR-PAPR PP2 2 22 Relative TS HEM* Single 256QAM Yes 64k LDPC 3/4 0 3 No No 36.61 SWE-DTT Mux 6 Mbps

HEM: High Efficiency Mode, ISSY: Input Stream Synchroniser,

This document is the property of TERACOM AB and may not without our written permission be copied, imparted to a third party or used for any other unauthorized purpose.