Addition of a test to display the DRM version number that the terminal supports

[HESE-NigelMoore]

On the assumption that this is possible, it would be useful if there was a test that could be run that simply queries the DRM system and determines the version number (the full version number, not just the major version), and displays it on the screen.

[jpiesing]

I also think this would be useful.

[juhajoki]

let's combine all version information including DRM and App to a single screen, #30 is related (closing it now to be combined with this one)

[juhajoki]

Staging instance has DRM capabilities option in Settings. Not perfect, but a start.

[bobcampbell-resillion]

Adding a note to make sure that when this ticket is implemented we don't forget about the need to somewhere display some additional text from #30

Build date and version (Production/Staging YYYY/MM/DD)

Data collection/logging warning: "Anonymous usage information is collected, including number of visitors and amount of total data transferred. Individual addresses or test results are not stored. Please see the readme for more information."

[Murmur]

Check for CBCS capabilities, display in Settings/Show MSEEME capabilities screen. If CBCS tests fail maybe should indicate CBCS may not be supported based on eme query. However devices may still fail on cbcs test even if they advertised a compatibility.
See EME interface Querying encryption scheme through EME interface
https://github.com/WICG/encrypted-media-encryption-scheme/blob/main/explainer.md

• scheme cbcs-1-9 is what we use for cbcs encryption pattern and is preferred “Apple derived” cbcs scheme
Video(NAL units) is 10%=crypt:90%=skip pattern. Audio(non NAL units) is 100%=crypt:0%=skip pattern (whole-block full sample encryption). Both tracks use ConstantIV init vector.

[Murmur]

Modified Settings/Show MSEEME capabilities to check for CBCS-1-9 encryption scheme.

Brief testing indicates Win10/Edge: playready cbcs19=false, widevine cbcs19=true, clearkey cbcs19=true but the browser playbacks playready-cbcs test content anyway. Brief test on one hbbtv device indicates all three playready cbcs19=true, widevine cbcs19=true, clearkey cbcs19=true flags.

https://refapp.hbbtv.org/production/catalogue/
https://refapp.hbbtv.org/staging/catalogue/