Open telemetry for converged TV
DVB-I is moving from trials towards real deployments. That also raises a basic question: how do broadcasters understand what is actually happening on DVB-I clients across devices and implementations, without building another proprietary telemetry stack?
A standards-based approach
We are working on an approach based on CMCD v2, using client-to-server signalling around media delivery as the basis for DVB-I measurement. CMCD v2 adds richer reporting capabilities, including event-based reporting, while keeping the data model standardized across players and platforms.
CMCD v2 / CTA-5004-B spec: Official CTA WAVE page / Freely available non-binding HTML version
For information useful for DVB-I but not part of the core CMCD specification, we use CMCD custom keys rather than introducing a parallel format. We have also contributed to the SVTA CMCD Custom Keys Repository, providing a shared registry for those keys.
SVTA CMCD Custom Keys Registry: Repository / Current keys
Why this matters for DVB-I
Measurement needs to work across different TV manufacturers and client implementations, scale to large deployments, and ideally build on standards already supported by the streaming ecosystem.
CMCD v2 provides a good foundation for that.
Moving towards deployment
We are now preparing a first pilot with a major public broadcaster in the EU.
See it at IBC
If you are working on DVB-I and want to see what this looks like in practice, we are happy to show the setup and a live demo at IBC, booth 3.B48c.