CMCD with Orange CDN and Hydrolix
Watch Bitmovin’s Player attach standardised CMCD (Common Media Client Data, CTA-5004) telemetry to every manifest and segment request. Streams are delivered live from Orange CDN and CMCD-enriched request logs are streamed into Hydrolix, where they can be joined with Bitmovin Observability data through a shared session ID.
A live view of the requests this page is sending to the CDN, with each CMCD key decoded. Press play and see the request data below. On iPhones running iOS below 17.1, playback falls back to Apple’s native player, which cannot attach CMCD data — the log will stay empty there.
- Global session visibility. Each Player request includes a session ID and content ID, so CDN edge logs and playback observability describe the same viewer session. The CMCD session ID is stored in Bitmovin’s Observability, making each CDN log line joinable to full player session & QoE data.
- AI-native observability. CMCD data is aligned between Bitmovin’s MCP Server and the Hydrolix MCP Server, so AI agents can join player-side QoE with edge delivery logs and answer questions spanning the whole delivery chain in a single conversation. Bitmovin’s Skills can also be used to perform root cause issue analysis.
- Faster root-cause analysis. Buffer level, measured throughput and top bitrate travel with each request. When a viewer hits buffering, the CDN logs contain the client-side context needed to determine whether this is a delivery problem or a player issue.
- Smarter delivery. The next-object-request hint tells the CDN which segment the player will ask for next, enabling pre-fetching and cache optimisation which can reduce startup time and rebuffering.
This demo is a collaboration between Bitmovin, Hydrolix and Orange CDN. Playback is delivered from Orange CDN’s edge and CMCD-enriched request logs are streamed into Hydrolix. The shared session ID connects the edge logs to Bitmovin’s Observability, giving player, CDN and log platform one common view of every session.
