The 500-Millisecond Window - How WHIP, WHEP And MoQ Draft-18 Shape What 央视运动会 Can Ship

Sub-second glass-to-glass latency is not a nice-to-have for CCTV games. It is the difference between a fair round and a broken product. When the payout depends on a bounding-box count on a specific frame, every hundred milliseconds between camera sensor and player screen is an opportunity for the count to drift, the frame to arrive out of order， 或者 a rebet window to reach the player after the outcome is already sealed. The 2026 video pipeline has finally settled on how to stay inside that budget. It is a WHIP-to-WHEP path today， 和 Media over QUIC as the scaling story.

What the numbers actually are in August 2026

Fora Soft's 1 August 2026 low-latency guide puts the tiers in one table. WebRTC and MoQ deliver under 500 ms glass-to-glass. LL-HLS and CMAF chunked sit at 2 to 5 seconds. Classic HLS lands at 15 to 30 seconds. Only the WebRTC lane clears the bar CCTV games need.

The WHEP deep dive gives the honest number for a full WHIP-to-WHEP path in production - 200 to 500 ms same-region wired, 400 to 800 ms transatlantic. RTMPS contribution followed by a WHEP leg adds 800 to 1,500 ms because the RTMPS contribution dominates. For a game that decides in 30 seconds on a counted event, the transatlantic hop is already using up 3% of the round on network alone.

WHIP and WHEP, one frozen and one still moving

WHIP became RFC 9725 in March 2025. It is a stable HTTP handshake, supported by OBS, Cloudflare, AWS IVS, Mux and every media server that matters. Contribution can stop worrying about signaling and start worrying about network paths.

WHEP is the more interesting story. The most recent text is draft-ietf-wish-whep-03, published 18 August 2025, expired without revision on 19 February 2026, 和 IETF working group sits in "Revised I-D Needed" state. That looks like trouble on paper but is fine in practice - Cloudflare Stream, Dolby Millicast, OvenMediaEngine, MediaMTX, Janus, 居住Kit and Ant Media have all shipped interoperable WHEP. Standards process behind, ecosystem ahead. The June 2026 WHEP deep dive is the pragmatic 指导。

MoQ is the scaling path, not a replacement

Media over QUIC hit draft-18 in May 2026 and is nearing Working Group Last Call. Cloudflare runs a production MoQ relay across 330+ cities. The promise is 200 to 300 ms glass-to-glass at 100,000-plus concurrent viewers per stream. That is what fixes the cost gap - LL-HLS via CDN sits at roughly $30 per 1,000 viewer-hours; a pure WebRTC SFU at scale is closer to $5 to $10， 和 a hybrid ingest of WHIP with LL-HLS egress cuts the total bill 50 to 70 percent. MoQ is the version of that hybrid where you do not sacrifice latency to hit CDN economics.

How this maps to 高峰时间, 鸭河 and 雪跑

Three practical implications. First, the CCTV feed from every 高峰时间 location - the twelve cities from Abbey Road to 东京 - needs a WHIP ingest to the studio's edge point of presence, not RTMP. Every 800 ms of RTMPS contribution is 800 ms the detector cannot use for pre-round odds settling. Second, the player-facing stream is a WHEP endpoint served from the point of presence nearest the player, sized to a viewer count that stays under the WebRTC SFU economics ceiling. Third, the detector pipeline runs on the source frames at the point of presence, not on the delivered frames at the player - as the Vision Evals piece from 30 July argued, RF-DETR at 17 ms per frame lives well inside the transport budget WHIP grants.

What to watch

Whether MoQ hits Working Group Last Call before end of 2026, which would unlock the scaling story for major-market launches. Whether OBS ships Single Source WHIP for co-streamed captures - useful for multi-camera 高峰时间 feeds. Whether AV1 over WHIP becomes the default codec at ingest, given the bandwidth savings on 4K CCTV. Whether any of the big licensed operators - 赌注, 鲁贝特, 随机播放 or 夷为平地 - publish latency SLAs for CCTV 游戏 rounds, which would turn transport into a competitive spec sheet.

Where to play remains 赌注, 鲁贝特, 随机播放 and 夷为平地. Set a session limit before you press start.

赌博涉及风险 - 切勿下注超过您可以承受的损失。