UI profiles

Base profiles

A HbbTV device will support at least one of the UI-related base profiles defined in the following table.

Base UI Profile Name Default values

OITF_HD_UIPROF <width>1280</width>
<height>720</height>
<colors>high</colors>
<hscroll>false</hscroll>
<vscroll>true</vscroll>
<font type=”sans-serif” defaultsize=”24″>Tiresias</font> with support for the Unicode character range “Generic Application Western European Character set” as defined in Annex C of [TS102809].
<key>VK_BACK</key>
<colorkeys>true</colorkeys>
<navigationkeys>true</navigationkeys>
<numerickeys>true</numerickeys>
<pointer>false</pointer>
<security protocolNames=”tls”>true</security>
<overlay>per-pixel</overlay><!– whereby at least one level of partial transparency between graphics and video must be supported as per the minimum requirements of section [9.1](http://oipf.tv/web-spec/volume5.html#minimum-dae-capabilities) –><overlaylocal>per-pixel</overlaylocal><!– whereby at least one level of partial transparency between graphics and video must be supported as per the minimum requirements of section [9.1](http://oipf.tv/web-spec/volume5.html#minimum-dae-capabilities) –>
<overlaylocaltuner>per-pixel</overlaylocaltuner><!– whereby at least one level of partial transparency between graphics and video must be supported as per the minimum requirements of section [9.1](http://oipf.tv/web-spec/volume5.html#minimum-dae-capabilities) –>
<overlayIPbroadcast>per-pixel</overlayIPbroadcast><!– whereby at least one level of partial transparency between graphics and video must be supported as per the minimum requirements of section [9.1](http://oipf.tv/web-spec/volume5.html#minimum-dae-capabilities) –>
<notificationscripts>false</notificationscripts>
<save-restore>false</save-restore>

OITF_FULL_HD_UIPROF Same as OITF_HD_UIPROF, with the following modifications:
<width>1920</width>
<height>1080</height>

Base UI Profile Name	Default values
`OITF_HD_UIPROF`	`<width>1280</width>` `<height>720</height>` `<colors>high</colors>` `<hscroll>false</hscroll>` `<vscroll>true</vscroll>` `<font type=”sans-serif” defaultsize=”24″>Tiresias</font> with support for the Unicode character range “Generic Application Western European Character set” as defined in Annex C of [TS102809].` `<key>VK_BACK</key>` `<colorkeys>true</colorkeys>` `<navigationkeys>true</navigationkeys>` `<numerickeys>true</numerickeys>` `<pointer>false</pointer>` `<security protocolNames=”tls”>true</security>` <overlay>per-pixel</overlay><!– whereby at least one level of partial transparency between graphics and video must be supported as per the minimum requirements of section [9.1](http://oipf.tv/web-spec/volume5.html#minimum-dae-capabilities) –><overlaylocal>per-pixel</overlaylocal><!– whereby at least one level of partial transparency between graphics and video must be supported as per the minimum requirements of section [9.1](http://oipf.tv/web-spec/volume5.html#minimum-dae-capabilities) –> `<overlaylocaltuner>per-pixel</overlaylocaltuner><!– whereby at least one level of partial transparency between graphics and video must be supported as per the minimum requirements of section [9.1](http://oipf.tv/web-spec/volume5.html#minimum-dae-capabilities) –>` `<overlayIPbroadcast>per-pixel</overlayIPbroadcast><!– whereby at least one level of partial transparency between graphics and video must be supported as per the minimum requirements of section [9.1](http://oipf.tv/web-spec/volume5.html#minimum-dae-capabilities) –>` `<notificationscripts>false</notificationscripts>` `<save-restore>false</save-restore>`
`OITF_FULL_HD_UIPROF`	Same as OITF_HD_UIPROF, with the following modifications: `<width>1920</width>` `<height>1080</height>`

Complementary UI Profile Name Fragments

In order to capture the heterogeneity of the features supported by HbbTV devices, the HbbTV specification also defines a set of complementary UI Profile name fragments, each constituting a particular logical subset of capabilities, for which a HbbTV device can indicate support by appending the UI Profile name fragment to the name of the supported base UI profile as defined above.

The HbbTV device may concatenation the series of UI profile name fragments in any order.

UI Profile Name Fragment	Default values
`+TRICKMODE`	`<key>VK_PLAY</key>` `<key>VK_PAUSE</key> and/or <key>VK_PLAY_PAUSE</key> ()` `<key>VK_STOP</key>` `<key>VK_REWIND</key>` `<key>VK_FAST_FWD</key>` () The +TRICKMODE profile fragment identifier does not distinguish between remote controls having separate “play” and “pause” keys; and remote controls having a single “play/pause” toggle key. For that reason, in general, it is recommended that applications are written to handle both the VK_PLAY/VK_PAUSE key codes and the VK_PLAY_PAUSE key code
`+DL`	Support for file download feature. `<download protocolNames=”http”>true</download>`
`+DVB_C`	`<video_broadcast type=”ID_DVB_C ID_DVB_SI_DIRECT” scaling=”quarterscan”>true</video_broadcast>`
`+DVB_T`	`<video_broadcast type=”ID_DVB_T ID_DVB_SI_DIRECT” scaling=”quarterscan”>true</video_broadcast>`
`+DVB_S`	`<video_broadcast type=”ID_DVB_S ID_DVB_SI_DIRECT” scaling=”quarterscan”>true</video_broadcast>`
`+DVB_C2`	`<video_broadcast type=”ID_DVB_C2 ID_DVB_SI_DIRECT” scaling=”quarterscan”>true</video_broadcast>`
`+DVB_T2`	`<video_broadcast type=”ID_DVB_T2 ID_DVB_SI_DIRECT” scaling=”quarterscan”>true</video_broadcast>`
`+DVB_S2`	`<video_broadcast type=”ID_DVB_S2 ID_DVB_SI_DIRECT” scaling=”quarterscan”>true</video_broadcast>`
“+DVB\_I”
`+META_EIT`	`<clientMetadata type=”eit-pf”>true</clientMetadata>`
`+META_SI`	`<clientMetadata type=”dvb-si”>true</clientMetadata\>`
`+PVR`	Support for PVR feature. `<key>VK_RECORD</key><recording>true</recording>`
`+DRM`	Support for the DRM feature – specifically that the XML capabilities include a <drm> element. `<drm DRMSystemID=”urn:dvb:casystemid:19188″>TS_BBTS TTS_BBTS MP4_PDCF</drm>`
`+POINTER`	`<pointer>true</pointer>`
`+HTML5_MEDIA`	`<html5_media>true</html5_media>`
“+AFS”	Support for the CICAM Auxiliary File System as defined in the DVB Extensions to CI Plus ETSI TS 103 205.

Whenever an HbbTV device supports an extension to the capabilities that can be defined using a combination of a base UI Profiles and a (number of) UI Profile fragment(s), it advertises this extension using the mechanism as defined in the user agent string and through the capabilities object.