HbbTV 2.0.5 makes DRM a baseline, not a bonus
The HbbTV Association published HbbTV core specification version 2.0.5, updating hybrid broadcast-broadband interactive TV requirements. The release formally integrates DRM into the core spec—requiring support for at least one listed system (Microsoft PlayReady or Google Widevine)—and adds/clarifies capabilities including optional AV1 and VVC codec support, formal WebAssembly support, and enhanced DVB-I integration and security measures. The association also plans an RfP to extend its Conformance Test Suite for HbbTV 2.0.5.
Key Takeaways
- DRM is now explicitly integrated into HbbTV core: devices must support PlayReady or Widevine.
- Optional support is defined for next-gen codecs AV1 and VVC, clarifying expectations without forcing adoption.
- WebAssembly is formally added, enabling more advanced in-app workloads (e.g., auxiliary video processing like sign-language streams).
- DVB-I integration is refined to better support service-list apps, including consent/terms flows for aggregators and platforms.
- HbbTV plans an RfP to extend its Conformance Test Suite for 2.0.5—critical for interoperability and vendor readiness.
Why It Matters
This is HbbTV’s “premium content” moment: by turning DRM from de facto support into a core requirement, the spec reduces ambiguity for studios, broadcasters, and platform operators trying to ship protected experiences at scale. The mandate (PlayReady or Widevine) also nudges the ecosystem toward fewer, testable permutations—especially important as hybrid TV blends broadcast reach with app-like monetization. Add WebAssembly plus cleaner DVB-I guidance and you get a clearer path to richer CTV apps, safer data flows, and more standardized distribution. Expect conformance testing to become the real gatekeeper.
Read full article at tvtechnology.com
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