HbbTV makes DRM mandatory: hybrid TV goes premium-ready
The HbbTV Association has published HbbTV Core Specification version 2.0.5, formally adding DRM support to the standard for the first time and requiring devices to support at least one approved DRM system (Microsoft PlayReady or Google Widevine). The update also adds specification-level support for WebAssembly, clarifies and enhances DVB-I integration, and defines optional support for next-generation codecs AV1 and VVC, alongside additional security and interoperability changes.
Key Takeaways
- HbbTV 2.0.5 formally adds DRM at the specification level for the first time
- Device compliance now requires at least one DRM: PlayReady or Widevine
- WebAssembly is now specified, enabling more advanced app and auxiliary video use cases (e.g., sign-language streams)
- DVB-I integration is clarified, including app linkage to service lists for consent/terms workflows
- AV1 and VVC are defined as optional codec support; conformance testing updates are forthcoming
Why It Matters
This is HbbTV’s “grown-up” moment: once DRM is standardized, premium rights can move from bespoke integrations to repeatable deployments across connected TV footprints. For broadcasters, operators, and FAST/AVOD aggregators, that reduces friction in hybrid broadcast-broadband rollouts—and shifts the competitive baseline toward secure, app-like experiences on TV. Requiring PlayReady or Widevine also hardens the ecosystem around two DRM poles, simplifying content licensing discussions while narrowing optionality for device makers. Add WebAssembly and cleaner DVB-I mechanics, and HbbTV is positioning hybrid TV as a viable platform layer, not just a catch-up UI.
Read full article at broadbandtvnews.com
Get this in your inbox → Subscribe
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source