The proposed agenda is:

Draft NorDig-T minutes of meeting 27th October 2020, Per Tullstedt (per.tullstedt@teracom.se)

DRAFT NorDig/T Minutes of meeting 27th October 2020

Time: NorDig-T CET 10:00 - 12:00 (meeting ended at 12:10)

Location: Webinar

Participants:

Per Tullstedt, Teracom (chair)

Peter Mølsted, (editor)

Johan Lindroos, SVT

Pasi Toiva, Labwise

Chris Buma van Haersma,Philips (first 30min)

Torsten Krokotsch, Panasonic

Nicholas Frame, TP Vision

Guillaume de Keating-Hart, Samsung

Ralf Schaefer, Technicolor/InterDigital

Anirban Majumdar, Dolby

Erik Vold, NRK

Stuart Savage, LGe

Agenda proposal, inputs & minutes from previous NorDig T meeting

· Agenda: OK

· Minutes from prev meeting (29th September 2020): OK

· (Per T by mistake wrote in NorDig T meeting calendar that today’s meeting was Thu 27th Oct, should of course be Tue/Tuesday 27th Oct)

· Inputs and proposal for the agenda:

· RoO, final draft NorDig Rules of Operation_ver_3.1.1._final_draft001.docx + pdf from editor

· Technical report back from NorDig Excom meeting 8 Oct, 3. NorDig T report back from Excom 2020.10.08.pptx

· HbbTV org liaison letter to NorDig T/API group HbbTV-liaisons-00198-000-liaision-to-NorDig-announcing-hbbtv-203-and-errata-5-to-hbbtv-201.pdf

· HbbTV org (from their website) HbbTV-SPEC-00521-004-HbbTV-203-Explained.pdf

· HbbTV Webinar presentation ADB2 from 21st Oct 2020, HbbTV ADB2 Webinar Presentation Oct. 21.pptx

· Outputs DRAFT documents during this meeting (NorDig website/members section/NorDig T):

· (none)

Market information from members and other organizations (DVB etc)

· Sweden, after Swedish major cable operator ComHem analogue TV switch off in their cable network 8th September 2020, quite some reports of viewers having problem with finding services and getting supplementary audio instead of normal audio.

· DVB, investigating/preparing work with new codecs (after HEVC). Now it is good time to give input for commercial requirements/market needs. Ralf S woke the question if NorDig as organisation would be interested to give inputs to this DVB work of new codecs for example as liaison letter or similar. Per T answer that NorDig (Tech group nor Excom) has not discuss this yet, typically would NorDig members give direct input as a DVB member, but not all NorDig members are DVB members (e.g. Teracom no longer DVB member). AP Per T will check with NorDig Excom chair if interest inside NorDig to come with common NorDig input to DVB for this topic.

· HbbTV, has sent a liaison letter to NorDig about new HbbTV 2.0.3, new errata (#2 for v2.0.2) and indications of features inside future coming “v2.0.4”, see liaison letter. There is a presentation at HbbTV website describing v2.0.3 and new errata, see HbbTV-SPEC-00521-004-HbbTV-203-Explained.pdf. Erik V finds for the indication of future items both better co-exist w accessibility support and DVB-I interesting topics/feature for NorDig of the coming “v2.0.4”.

· HbbTV, webinar workshop 21st oct 2020, where our Erik Wold, NRK/NorDig API group chair has among with others made a presentation about Application Discovery over Broadband (ADB) Phase 2, see presentation HbbTV ADB2 Webinar Presentation Oct. 21.pptx. Erik made a summary of this ADB 2 presentation, ADB phase 2 May2020 (in addition to phase 1 fr Sep 2016) solve STB case, stream events and timeline. ADB2 with only audio watermark (no video watermark) should solve most parts with some reduced functionality for stream events and timeline functionality. There are some indication of that the audio watermark tech is reasonable non-audible (should be investigated further).

Report to/back from NorDig Excom (last 8th Oct 2020, next 11th March 2021)

· Per T presented his technical report back from NorDig Excom meeting 8th Oct, see presentation 3. NorDig T report back from Excom 2020.10.08.pptx (observe that this is not the official NorDig Excom minutes of meeting):

· RoO spec, draft010 no comments/disagreement/OK, continue finalise RoO v3.1.1 d010 (correct cross ref, typos, ref) as current proposed content (i.e. do not incl Samsung’s proposed changes for HbbTV). Target to finalise final draft within 3-5weeks. When ready send to Excom (e-mail) for a 2w silent approval, if no (major) comment then OK to publish new version. HbbTV additions for pre-testing, contacts w manufactures etc is pushed for next version.

· RoO - NorDig T task to propose a new draft RoO “v3.1.2” to next Excom meeting in March 2021 (among thing to incl additions HbbTV part at reasonable level and above proposed items).

· IRD spec dHDR - task for NorDig T to continue draft from d008, update and make more clear that dHDR is not required/mandatory, however the dHDR text shall be clear (as d008). (Draft011 not seen clear enough, some Industry/Samsung arguments was discussed).

· AP for NorDig T now to start draft new IRD spec v3.1.2 (w buglist + dHDR + Audio) and a new RoO v3.1.2 (as proposed) for coming Excom March 2021,

· Per T added that even if not explicit mention during NorDig Excom meeting, NorDig has the intension to keep all three spec (IRD + TestPlan + RoO) in line with each other and therefore the plan is also to make a proposal for updated TestPlan v3.1.2 to coming NorDig Excom meeting March 2021.

NorDig T and subgroups, short report status and progress

· Plan is now (directly after RoO v3.1.1 is finalised) start drafting update of NorDig IRD, TestPlan and RoO v3.1.2 to be ready to present to Excom meeting 11th March 2021.

· Main context of updates IRD+TestPlan+RoO to v3.1.2:

· NorDig IRD spec v3.1.2: buglist, audio corrections, dHDR, HbbTV (errata or v2.0.3), ref.list,

· NorDig RoO spec v3.1.2: remaining chapters and work from v3.1.1 (SSU etc), HbbTV and new items in IRD (audio etc), typos etc

· NorDig TestPlan v3.1.2: align with new items in IRD v3.1.2, typos etc

·

API/HbbTV

· No meeting since last NorDig T meeting. Will now plan for a meeting inside NorDig API/HbbTV group (Erik reminder to include Nicholas Frame into mail list).

· AP for NorDig API/HbbTV subgroup since previous was to review if NorDig should update to reference to include this new Errata #1 and if needed propose if grace period is needed/recommended. Now when HbbTV released errata #2 for v2.0.2 and the new v2.0.3 (which incl this errata #2). Since earlier HbbTV v2.0.2 errata #1, OK for TP Vision, Panasonic and LG. Samsung OK if from 2022.

· Grace period for adding/updating NorDig IRD HbbTV requirement either to HbbTV v2.0.3 or keep HbbTV v2.20.2 but add errata #2 (or just errata#1), reasonable grace period to be discussed inside NorDig API/HbbTV group, but TP Vision mention a reasonable grace period could be until 2022. (Per T mention that NorDig often uses 12 month as “standard” grace period from publication of new spec, here other values may of course be used).

· For coming update of NorDig IRD (RoO+TestPlan) specs to v3.1.2, NorDig API/HbbTV group should study and if interest propose text proposal for:

· HbbTV version/errata: v2.0.3, v2.0.2 w errata#2 (or v2.0.2errata#1)

· HbbTV feature ADB: v2 or v1

· (HbbTV feature TA: used for regional/local program insertion case for PSB)

· Samsung/Guillaume regarding grace period for new IRD HbbTV requirements; “the HbbTV test suite for the release considered (either HbbTV or Errata) should be ready in the HbbTV Test suite “xxxx-1” release of that year for the specification to be considered for the next year. (additional remark: otherwise there is a risk that the test suite will not be stable enough potentially causing issues – regardless of whether the changes in the release considered are big or small – Samsung doesn’t consider “it will be ready by that date in x months” as a guarantee that it will ready and stable in time and needs to minimise risks)”.

EPG/Event info exchange format subgroup (Peter M)

· Several meetings last period,

· ”List of EPG metadata in NorDig TVA format ver. 1.1” updated version have been released on NorDig website 26th Oct 2020.

· Workshop 2nd Oct 2020 webinar, successful meeting with presentions from SVT, TDC, DR and NRK. Plan next open workshop in 6 months.

Test subgroup (Pasi Toiva)

· No meeting since last NorDig T meeting, but plan a meeting mid Nov2020 to plan update of TestPlan v3.1.1 to v3.1.2 to Feb/March 2021 (typos, new coming items in IRD spec etc). Pasi will send invitation to whole NorDig T group.

· Pasi T is checking with French FAVN group related to get access to their TTML test stream. If NorDig could get a copy of that. AP for Test group/Pasi.

Audio subgroup (Johan L)

· No new meetings planned yet (all previous listed work/item is done). For coming IRD/RoO/TestPlan v3.1.2 no remaining audio points listed so far.

· During today NorDig T meeting two new items was listed for the Audio group:

· Investigate with NorDig API group using audio watermark for HbbTV ADB what impact it has on audio quality, if it is audible or not.

· NGA/AC4, collect more information about what has been done around Europe/World for NGA/AC4, finding, especially around improved accessibility (e.g. dialogue enhancement).

Accessibility – nothing at this meetingRules of Operation (Peter M)

· Had several meetings since last NorDig T meeting, stable draft sent to Excom in beginning of Oct 2020.

· After Excom decision Peter has now started going through all cross-references etc in draft010 and has sent out new final draft001 19th Oct2020 for all to comment.

· So far only Per T commented with a number of typos and missing cross-ref.

· Guillaume mention that he has observed a number of typos that he will send to Peter

· Please all, help scrutinise final draft001 for typos etc, latest day is this Friday 30th Oct 2020.

· The plan is to send to Excom during next week (w45 y2020) a final draft for their silent approval (two week process). Peter will create one clean copy and one delta copy (markup from prev. published version) of the new RoO v3.1.1.

· After RoO v3.1.1 the group will start working upon v3.1.2 for March 2021 (HbbTV, SSU etc).

Video related (within main NorDig T group)

· dHDR, dynamic metadata HDR, NorDig’s main intension for dHDR: not mandate dHDR, if used then according to DVB, IRD not to be disturbed by formats not supported.

· dHDR drafting, Excom decided to continue drafting from d008, but if needed clarify even more that this dHDR is not mandatory.

· Ralf comment to Samsung proposal (d011) was mainly political and current text in d008 might be clear enough.

· It was decided to have a NorDig Video group meeting 1st Dec 2020 at 15:30-16:30 CET to continue discussing this.

Old AP from March/May 2020 meetings:

· Liaison letter from NorDig to HbbTV about dHDR, during meeting presentation of draft004 (20200228) (and during updated to draft005). Proposal OK but agreed to remove last note about “Several NorDig members are” – OK. Proposal now ready to send to HbbTV.

· AP Per T to send liaison letter to HbbTV (Vincent)

NorDig specifications issues (RoO, IRD, Test Plan, EPG Exchange and others) NorDig Unifies IRD spec

· New NorDig Unified IRD spec planned for Feb/March 2021 (to Excom meeting 11th March) which plan to include:

· dHDR (as not mandatory),

· Audio prio corrections,

· HbbTV updates (v2.0.2errata#2 or v2.0.3) plus

· “Buglist”/Bugzilla, see Annex A below.

NorDig Test Plan

· New NorDig Test Plan planned for Feb/March 2021 (to Excom meeting 11th March) which plan to include:

· debugging

· new items in coming IRD spec v3.1.2 (see above).

NorDig Rules of Operation

· Finalise NorDig RoO v3.1.1 now w44-45, send to Excom w45 2020 for final approval (“silent approval”) and if approved then published new RoO at NorDig website mid/end Nov 2020.

· New NorDig RoO planned for Feb/March 2021 (to Excom meeting 11th March) which plan to include:

· debugging

· chapters not fully updated in v3.1.1 (SSU, new Annex of SI etc)

· HbbTV

· new items in coming IRD spec v3.1.2 (see above).

NorDig EPG/Event exchange file formatNorDig Guidelines for editing and proposal for text updates (nothing at this meeting)NorDig website etc

· AP Peter to check if mail reflector could be arranged.

· NorDig website have added inform visitors about cookies

· NorDig T, RoO, EPG group meeting from 2021will stop using WebEx, will instead use Microsoft Teams.

Dates for next meetings

NorDig T group meeting calendar 2020, no changes to meeting calendar:

· NorDig T, Thu 28th January 2020, webinar, 10:00-12:00 CET

· NorDig T, Tue 25th February 2020, webinar, 10:00-12:00 CET

· Excom 5th March 2020

· NorDig T, Tue 31st March 2020, webinar, 10:00-12:00 CET

· NorDig T, Tue 26th May 2020, webinar, 10:00-12:00 CET,

· NorDig T, Tue 1st Sep 2020, webinar, 10:00-12:00 CET

· NorDig T, Tue 29th Sep 2020, webinar, 10:00-13:00 CET (extend meeting to get time for RoO v3.1 walkthrough, IRD dHDR new input fr Samsung)

· Excom 8th October 2020

· NorDig T, Tuehu 27th October 2020, webinar, 10:00-12:00 CET

· NorDig T, Tue 1st December 2020, webinar, 10:00-12:00 CET.

AP Per T to propose meeting calendar for 2021 before next NorDig T meeting 1st Dec 2020.

FIRST PROPOSAL for NorDig T group meeting calendar 2021, everyone is asked to comment to these proposed dates:

· NorDig T, #1, 12th January 2021, webinar, 10:00-12:00 CET

· NorDig T, #2, 2nd February 2021, webinar, 10:00-12:00 CET

· NorDig T, #3, 2nd March 2021, webinar, 10:00-13:00 CET

· Excom 11th March 2021

· NorDig T, #4, 30th March 2021, webinar, 10:00-12:00 CET

· NorDig T, #5, 25th May 2021, webinar, 10:00-12:00 CET,

· NorDig T, #6, 31st August 2021, webinar, 10:00-12:00 CET

· NorDig T, #7, 28th September 2021, webinar, 10:00-12:00 CET

· Excom 14th October 2021

· NorDig T, #8, 2nd November 2021, webinar, 10:00-12:00 CET

· NorDig T, #9, 7th December 2021, webinar, 10:00-12:00 CET.

Informative: other relevant dates for 2021:

· NorDig Excom, 11th March 2021, 14th October 2021.

· NAB 9-13 Oct 2021(?), IFA 3-7 Sep 2021, IBC 10-13 Sep 2021

AoB

none

Annexes

Annex A – Bugzilla and proposals for future NorDig Unified IRD spec v3.1.1

Chapter

Status

date, description

owner

Old open points from earlier drafting (v2.5 etc, earlier postponed) to be investigated for v3.1.21

Chapter

Status

date, description

owner

?

postponed

2015-02-11 Questions from Test subgroup up to NorDig T: Below some unclarified things in nordig u v2.5.1 we identified during the today’s nordig ver test meeting for discussion within nordig/t.

Question 1: How to specify OTA for ONid which not follow country code like deployed some cable and satellite networks ? ONId may be allocated per operator or broadcasted as 0 or something else. need for more detailed specification?

Answer 1: TBD (Per T, Teracom, investigate)

NorDig T (Per T)

16.2

User preference settings

postponed

2015-02-11 Questions from Test subgroup up to NorDig T: Below some unclarified things in nordig u v2.5.1 we identified during the today’s nordig ver test meeting for discussion within nordig/t.

Question 4: Ch 16.2 User setting country setting states “pre-select” language. what does “pre-select” mean ? does it mean that ird proposes in menu by default majority language of the country ? ”Country setting based on country code [49] for pre-selection of the primary menu, primary audio language, primary subtitle language settings and channel list selection as defined in 12.2.9.3.”

Answer 4: (Per T) Same view, default proposes languages. Wording probably needs to be reformulated (same wording since IRD spec v1.0.3 from 2007). Our understanding this intend to refer to this Country value may typically be used by an IRD to also pre-select audio and subtitling languages and maybe also other country related settings. Example if user set “Sweden” as country menu, the IRD pre-select “Swedish” for audio&subt languages to speed up first-time installation process so most user can just confirm language menus during first time installation (similar as many mobile telephones does).

NorDig T (Per T)

Chapter

Status

date, description

owner

New items for NorDig IRD v3.1.1 2 (or laterwhen updating v3.2)

5 video dHDR

drafting

2019-10-10 NorDig Excom meeting, related to dynamic metadata HDR: add text that where used dHDR signaling shall be as DVB specified and that IRD shall not be disturbed by formats not supported (i.e. not mandate dHDR, just if used then…).

Ralf + Wiebe

Main NorDig T group

7.4 Subtitling TTML

open

2019-10-18 RoO group meeting, typo. TTML only mandatory for HEVC IRDs but missed in text the word “HEVC”:

original text: “The NorDig IRD shall be capable of decoding, as a minimum, the DVB TTML subtitle service that are in conformance with ETSI EN 303 560 [94], and displayed using…”

proposed text: “The NorDig HEVC IRD shall be capable of decoding, as a minimum, the DVB TTML subtitle service that are in conformance with ETSI EN 303 560 [94], and displayed using…”

AND typo also for updated reference and end chapter:

“For IRDs supporting TTML Audio Description subtitles and converting these to text-to-speech (optional), these NorDig HEVC IRDs shall be able to display one subtitle type (e.g. translation subtitle stream) at the same time as rendering text-to-speech subtitles (see DVB TTML specification ETSI EN 3DD DDD ETSI EN 303 560 [94].”

editor

Ref

Open

2020-06-02 NorDig RoO group, update Bluetooth reference.

editor

12.1.1 SI General

Open

2020-08-26 Sony, Kari Eriksson input proposal to clarify how often an IRD has to perform automatic updating in standby/night-time with respect to still be able to follow the more stricter EU power regulation, AP from earlier NorDig T meeting May 2020. Different IRDs uses today typically one of the following alternatives for auto update “in standby”:

· when the user press standby when IRD enters standby (or auto-standby after X hours) OR

· sometimes during standby (“night time”/long standby) OR

· when user press power on and the IRD wakes up from standby

Sony would like to clarify what happens/is required if multiple power cycle per day:

“The NorDig IRD shall at least start updating for any changes in the received “quasi-static” SI data after it returns to active from standby mode at least once per day. (Once per day refers here to daily usage of the IRD and that the IRD is daily put into standby). “Quasi static“ SI-data includes NIT and SDT, i.e. SI that is typically stored in the flash memory for service navigations, such as service name, service_ID, number of services. (The ‘running status’ is not included in the quasi-static SI data. As a guideline for the implementation, this updating may be performed in the background, to shorten the start-up of the basic video and audio).”

Kari

5 video frame rates

open

2020-09-01 during NorDig T meeting (observed by Nicholas F), strange requirements, the two sentences/paragraphs seems to contradict each other, first says shall while second says should. Might needs review or?

“The Video Decoder of the NorDig HEVC IRD shall also be able to receive and decode a half frame rate (50Hz) component of a dual PID 100Hz HFR bitstream, according to ETSI TS 101 154 [26] section 5.14.5 “HEVC HDR HFR UHDTV IRDs and Bitstreams and HEVC HFR UHDTV Bitstreams”, subsection 5.14.5.7 “HEVC encoding structure for HFR Bitstreams using dual PID and temporal scalability”.

Support for frame rates other than 25 Hz, 50 Hz and the reception and decoding of a half frame rate (50Hz) component of a dual PID 100Hz HFR bitstream, is optional in the NorDig HEVC IRD. For HEVC encoded video, only decoding of progressive scan video is mandatory.”

NorDig T

12.1

SI General table 12.3

new

2020-09-10 Per Tullstedt noted missing descriptor in NorDig IRD spec table 12.3 after input from Stephan Schreiner related to NorDig RoO same topic. The message descriptor is missing in table 12.3, but at least included in the SDT chapter.

Proposal is to add Message descriptor in table 12.3, Tag extension value 0x08 and marked for SDT as “Ob Mr (1)”.

editor

6.5.6

Audio NGA prio

agreed

2020-09-29 NorDig Audio group after questions from Industry has (June-Sep) reviewed and proposed corrections and clarification into IRD spec related Audio prio after NGA has been added, proposal was presented and accepted at NorDig T meeting 29th Sep 2020:

6.5.6 Audio Prioritisation inside the NGA Audio PID/stream

This section applies only to the NGA capable NorDig HEVC IRD.

Audio Prioritisation inside the NGA Audio PID/stream can be done based on the Audio Preselection Descriptor or based on the ac4_toc, as specified in ETSI TS 103 190–2 [98] in the elementary stream.

The information from the elementary stream (ac4_toc) shall be used for audio prioritisation inside the NGA audio PID/stream based on the user preference settings (1).

For manual selection, the information from the Audio Preselection Descriptor (APD) shall be used (1).

The NGA audio stream(s) may contain additional or fewer preselections than those listed in the Audio Preselection Descriptor.

If the presentation corresponding to a manually selected preselection from the Audio Preselection Descriptor is not found in the bitstream, then the IRD shall fall back to preference-based presentation selection based on IRD settings and signalling in the elementary stream as specified above.

In case the presentation currently playing does not have corresponding information in the Audio Preselection Descriptor (APD), the information should be extracted from the elementary stream (ac4_toc) or, if that is not feasible, a default called “currently playing” or similar could be displayed.

Similarly, when a presentation present in APD but not present in the elementary stream (ac4_toc) is manually selected by the user, the NorDig HEVC IRD applies preference-based presentation selection based on the elementary stream (ac4_toc), resulting in a selection different to the user’s. This selection should be reflected in the UI by extracting the information from the elementary stream (ac4_toc) or, if that is not feasible, a default called “currently playing” or similar could be displayed. Additionally, when a presentation present in APD but not present in the elementary stream (ac4_toc) is manually selected by the user, the NorDig HEVC IRD may inform the user that the selected audio presentation is not available in the current broadcast. It is expected that quasi-static APD signaling could result in an overrepresentation of presentations in the APD e.g. during advertisement breaks, where during the advert break there could be only one audio track available to all languages.

Language:….

6.11.4 Audio Supplem. (legacy audio)

Agreed

2020-09-29 NorDig Audio group after questions from Industry has (June-Sep) reviewed and proposed corrections and clarification into IRD spec related Audio prio after NGA has been added, proposal was presented and accepted at NorDig T meeting 29th Sep 2020:

6.11.4 Selection of audio streams

The NorDig IRD shall be able to select the correct audio type stream according to user preference settings, see section 6.5.

When the user has selected Normal audio as preferred audio, the NorDig IRD shall by default select the Normal audio stream for services which have several audio streams with different audio type for selected language.

When the user has selected Supplementary Audio as preferred audio, the NorDig IRD shall by default select the supplementary audio stream for services which have several audio streams with different audio type for selected language.

The NorDig IRD with separate user preference settings for Audio Type selection of Audio Description and Spoken Subtitles (see section 16.2.3) shall select the appropriate Supplementary audio stream based on supplementary_audio_descriptor signalling. Furthermore, if the Supplementary Audio is signaled via ISO 639(1) language descriptor but no supplementary_audio_descriptor (i.e. supplementary_audio_descriptor is missing, meaning that the IRD can not distinguish if Supplementary Audio is Audio Description or Spoken Subtitles), the Supplementary Audio shall be selected if any of the user preferences settings Audio Description or Spoken Subtitles are turned on.

Note 1: ISO_639_language_descriptor audio_type 0x03 (visually impaired commentary) is used in combination with one particular language, while Normal Audio is signalled as audio_type 0x00.

Observe that the Supplementary Audio descriptor overrides….

New Annex Audio prio flowchart

Agreed

2020-09-29 NorDig Audio group after questions from Industry has (June-Sep) reviewed and proposed corrections and clarification into IRD spec related Audio prio after NGA has been added, proposal was presented and accepted at NorDig T meeting 29th Sep 2020:

Flowchart describing Audio Prioritisation for NGA capbale NorDig HEVC IRD

1. Introduction

Find below a flowchart that describes the PID selection as detailed in section 6.5.2 Audio Prioritisation for NGA capable NorDig HEVC IRD.

PID Selection for NGA capable NorDig HEVC IRD

·

Status

New

New proposal/input/action listed, but not yet presented inside NorDig T

Waiting

Proposal been presented inside NorDig T, but no decision whether continue with proposal or close it. Work/activity not yet started.

Draft/open

Work in progress. Proposal been presented inside NorDig T. NorDig T has agreed upon continue work and start drafting text proposal (i.e. normally refers to agreed inside NorDig T upon content of the proposal but detailed/final text is still under preparation/drafting).

Agreed/final

Final text proposal is ready and agreed within NorDig T and to be presented up to NorDig Excom for final approval before publication.

(Accepted

Accepted by NorDig Excom)

Info

Informative point

Closed

Proposed point/action closed, no (more) action will be made. No text inserted in any specification/document.

Deleted

NorDig T has agreed upon deleting proposed point/action/comment

Annex B – Bugzilla & proposals f future NorDig Unified Test Plan and Test streams

Chapter

Status

date, description

owner

New items for NorDig Test Plan v3.1.21 (or laterwhen updating v3.2)

Test streams

new

Sep 2019 Sony input related to Test streams:

· NGA/AC-4 test stream that includes multiple (two or more) services, in order to test audio prio etc it is necessary to zap between services.

· DVB TTML (broadcasted TTML), difficult to test/verify this and it would be very good if NorDig could investigate TTML test stream (check w DVB or other body, otherwise if NorDig could establish a stream).

Test streams

new

Sep 2019 Sony reports that this becomes more important the availability of good reference test streams in future when IRD verification goes more into self-testing in some markets.

Annex C – Bugzilla & proposals f future NorDig Rules of Operation (RoO)

Chapter

Status

date, description

owner

New items for NorDig RoO v3.1.1

video

openagreed

2020-02-25 NorDig T meeting, whenever dHDR text is added into NorDig IRD spec, then also add following text in RoO spec at suitable place within video section:

“It is highly recommended that bitstreams that include DMI provide video quality at the level that can be expected from a NorDig HEVC IRD that does not support DMI, and that the DMI enables further enhancement of the video.”

2020-05-25 Ralf S and Wiebe d H updated proposal (input to NorDig T and RoO group):

“Dynamic Mapping Information (DMI) may optionally be included as metadata in SEI messages in HEVC video bitstreams. If included, DMI shall be included in the video stream according to the DVB specifications [include references to TS 101 154 V2.6.1 and EN 300 468 V1.17.1]. IRDs that do not support DMI will decode the video stream, but ignore any DMI metadata. The DVB specification requires that video encoding is done in such a way that the video quality from that bitstream without applying dynamic mapping is at the level that can be expected from a bitstream that does not include DMI messages.”

editor

New items for NorDig RoO v3.1.2

Annex D: NorDig Technical group’s mandates and work item for period 2019-2020 (approved by Excom 9th March 2019)

General: Keep IRD, RoO and Test Plan in line with each other

RoO

· Maintain and update NorDig RoO - focus for 2019 RoO v3.1.x

· (Excom Oct 2018) changing layout to same as IRD spec, focus for RoO on items necessary to avoid misbehavior in IRDs.

Test Plan

· Maintain and update NorDig Test plan to match IRD spec

· Review and where possible combine similar test cases to make it easier and faster to test

· “minimize” redundant test cases if possible without compromising with test quality, to speed up time for verification testing.

· Update and improve test cases

NorDig Unified IRD spec

· Maintain and update NorDig IRD specification

· debugging, references to international standards and specifications are up to date)

· Other items (listed since earlier):

· Review and improve IRD’s auto update for network changes?

· Handle mix of broadcast and OTT in same channel list? (similar to or based upon DVB-I)

Video, audio, subtitling

· Video: maintain NorDig’s subset of HEVC (DVB’s UHD, HDR&WCG, SFR), incl video processing and I/O (HDMI).

· Video: add optional dynamic metadata HDR (if used then according to DVB, IRD not supporting dHDR shall not be disturb by the dynamic metadata HDR).

· Video: Secure good IRD implementation for mixing/blending of SDR content (HbbTV, menus, subtitling) on top of HDR video.

· Audio NGA (Dolby AC-4), monitor DVB and Dolby specifications and recommendations

· Audio: monitor evolution immersive audio and object based audio.

· Audio: if it is possible supports with tests and trials of NGA audio (both basic NGA and more advanced NGA).

· Subtitling: monitor DVB specifications (TXT subt, DVB Subt, TTML).

· HbbTV: Investigate use and mandate of new codes (HEVC and NGA) for (HEVC) HbbTV/Hybrid IRDs.

HbbTV

· NorDig HbbTV test and test cases:

· Maintain NorDig developed test cases. Propose new test cases to be developed if needed.

· NorDig HbbTV IRD requirements:

· Maintain and update HbbTV requirements

· Monitor and report HbbTV spec development and usage.

· Investigate additional HbbTV feature and requirements that are of interest for NorDig members (to be confirmed by –T and Excom before detailed proposal and any incl into IRD spec).

· Investigate DVB-TA watermarking, impact V/A and possibility to use for STB solutions where STB do not support HbbTV (STB bypass)

· HbbTV implementation:

· Monitor and report HbbTV implementation in NorDig networks and other networks,

· Monitor and report implementation status on IRD side

· Monitor and discuss experience and issues/problems with launching HbbTV services

· HbbTV DRM

· Monitor HbbTV DRM

· Review security requirements

Accessibility

· Work with harmonization of broadcast and better describe current broadcast for IRD manufactures

· Subtitling, propose updates and new IRD requirements both for normal and hard-of-hearing subtitling.

· Create document explaining the work of the group, (which ExCom members to pass this to their internal accessibility teams). Gather information from accessibility groups and broadcasters to understand what their pain points are.

· Set up a best practice workshop with broadcasters, manufacturers and distributors

· Investigate the implications for streaming services on accessibility

· HbbTV for Accessibility services – investigate how HbbTV can be used for Accessibility and if needed propose changes to IRD and RoO requirements

· Investigate benefits with NGA for accessibility.

CA and CI

· monitor and report CIplus LLP (CI+ v1.4 and v2.0) and DVB work (CI+ v2.0 etc) within these topics to NorDig Excom and Technical group.

· Review security requirements

EPG/Event exchange file format

· Promote use for NorDig members for example via open workshops to support promoting and implementation of NorDig TVA format.

· Maintain NorDig specification of common EPG/Event exchange file format and Guidelines, to be inline with TA Anytime specs

· Common solution and recommendations about unique program ID’s.

· Translation of genres between Nordic and Irich language and English.

· Transform NorDig TVA XML schemas to JSON and developing guidelines for using TVA with JSON (on request from developers)

Annex B: Input to DVB GBS for DVB SI spec related SI for NGA

From Jonas Rödén (Dolby):

Last week the APD / ISO639 signaling was discussed a little in DVB. In short the DVB group was not clear on why an update was needed. Lets discuss cause of action in today’s NorDig-T meeting.

Find below alternative drafts.

 

Original DVB SI spec text in Annex:

M.2 PSI PMT Signalling

If the audio preselection descriptor is used for one audio programme contained in one or more NGA elementary streams, neither the ISO_639_language_descriptor nor the supplementary_audio_descriptor should be present in the ES_info descriptor loop of any of the NGA streams (main or auxiliary) of an audio programme.

When an audio_preselection_descriptor is present in the ES info loop for an NGA elementary stream in the PMT, receivers shall ignore any supplementary_audio_descriptor or ISO_639_language_descriptor which are present in the same ES info loop.

 

NorDig proposal ALT 2:

M.2 PSI PMT Signalling

For markets where all NGA receivers supports the audio preselection descriptor, when the audio preselection descriptor is used for one audio programme contained in one or more NGA elementary streams, neither the ISO_639_language_descriptor nor the supplementary_audio_descriptor should be present in the ES_info descriptor loop of any of the NGA streams (main or auxiliary) of an audio programme. (This means that audio preselection descriptor in combination with the ISO_639_language_descriptor or the supplementary_audio_descriptor should only be used to be to achieve backward compatibility when part of the NGA receivers do not support the audio preselection descriptor).

When an audio_preselection_descriptor is present in the ES info loop for an NGA elementary stream in the PMT, receivers supporting the audio_preselection_descriptor shall ignore any supplementary_audio_descriptor or ISO_639_language_descriptor which are present in the same ES info loop.

 

New proposal ALT 4:

M.2 PSI PMT Signalling

If the audio preselection descriptor is used for one audio programme contained in one or more NGA elementary streams, neither the ISO_639_language_descriptor nor the supplementary_audio_descriptor should be present in the ES_info descriptor loop of any of the NGA streams (main or auxiliary) of an audio programme.

When an audio_preselection_descriptor is present in the ES info loop for an NGA elementary stream in the PMT, receivers supporting the audio_preselection_descriptor shall ignore any supplementary_audio_descriptor or ISO_639_language_descriptor which are present in the same ES info loop.

Select Lowest NGA PID
with matching Primary language or no language signalized 
(info from APD)Any non-NGA PID
with matching Primary or Secondary language 
(ISO639 / SAD match)?NGA PID selected, go to Preselection Prioritization(Section 6.5.6)Go to Non-NGA PID Selection(Section 6.5.3)No MatchMatch FoundSelect lowest NGA PID (AC-4 Descriptor)No MatchMatch FoundGo to Non-NGA PID Selection(Section 6.5.3)No MatchNGA PID selected, go to Preselection Prioritization(Section 6.5.6)Match Found

Select Lowest NGA PIDwith matching Primary language or no language signalized (info from APD)Any non-NGA PIDwith matching Primary or Secondary language (ISO639 / SAD match)?NGA PID selected, go to Preselection Prioritization(Section 6.5.6)Go to Non-NGA PID Selection(Section 6.5.3)No MatchMatch FoundSelect lowest NGA PID (AC-4 Descriptor)No MatchMatch FoundGo to Non-NGA PID Selection(Section 6.5.3)No MatchNGA PID selected, go to Preselection Prioritization(Section 6.5.6)Match Found