You've spotted the perfect opportunity. You select 'Place Bet' and….. it’s a goal!
But did your bet go through before the goal was scored, or a split second afterwards?
In live sports betting, precision timing is everything. When money is at stake, knowing exactly when an event happened and when the bet was placed is critical to determining whether the bet should stand.
This is where Media over QUIC (MOQ), an emerging approach to transporting live video, audio and metadata over IP, comes in. Its ultra-low-latency capabilities are attracting attention for applications such as in-play betting, while its publish/subscribe architecture also has significant implications for primary distribution.
In this two-part series, we'll first look at why MOQ matters – from latency and synchronised media and metadata, to its broader implications for primary distribution. In Part 2 (add link), we'll explore the technology behind it: the timelines, timestamps, synchronized playback and delivery records that address the demanding technical requirements of in-play betting.
Looking beyond latency
Much of the conversation around MOQ has focused on its ability to deliver ultra-low latency. And rightly so. As live sports become increasingly interactive and audiences expect ever more immediate experiences, reducing latency is essential.
But speed is only part of the story.
Built on QUIC and WebTransport, MOQ introduces a publish/subscribe architecture that allows video, audio and metadata to move through the same workflow. Unlike traditional HTTP-based streaming technologies, which were never designed for today's interactive experiences, MOQ provides a more flexible way to distribute live media, allowing receivers to subscribe dynamically to the media streams they require.
That opens up opportunities well beyond simply delivering live video faster.
Why metadata matters
In-play betting is one use case where synchronized metadata is critical.
Today, betting platforms typically rely on separate systems that operate independently from the video itself to determine exactly when key events occur. Goals, penalties and red cards are time-stamped separately, often requiring additional infrastructure and manual processes to ensure bets are settled fairly.
MOQ creates the opportunity for that metadata to travel within the same streaming workflow as the live media. Metadata identifying a goal, penalty or red card could be carried alongside the video with an associated timestamp, while the placed bet could also be time-stamped using the same workflow. That shared timing reference could help determine whether a bet was placed before or after a match-changing moment.
The lower the latency, the shorter the window in which legitimate last-second bets may be rejected. But a betting service also needs viewers to remain closely synchronised, so the gap between them can be measured and kept as small as possible.
This is just one example of the opportunities created by transporting synchronized metadata alongside live media, and one of the areas we're helping to explore through our contribution to the IETF MOQ working group.
The potential also extends beyond betting. Keeping media and metadata synchronized throughout distribution could support automated clipping, more personalized viewing experiences and richer interactive services, all while ensuring the right information is associated with the right content.
A broader opportunity
MOQ’s capabilities also have significant implications for primary distribution.
MOQ’s publish/subscribe architecture lets broadcasters publish multiple streams including alternative audio, subtitles, accessibility services, regional variants and metadata, while receivers subscribe only to the streams they require.
This provides a more flexible approach to primary distribution over IP. Rather than creating multiple bespoke outputs for different affiliates or distribution partners, broadcasters can publish a richer set of content while allowing receivers to select only the streams they need.
As distribution becomes increasingly IP-based, this model also provides a practical path for broadcasters to evolve existing workflows over time. Rather than requiring a wholesale replacement of downstream infrastructure, it can co-exist with established MPEG Transport Stream and SDI environments as the industry transitions.
This is an important part of the broader MOQ story: not simply delivering live media with lower latency, but creating a more flexible approach to how media and the metadata associated with it are distributed.
More than a low-latency protocol
Ultra-low latency is one of the key reasons the industry is embracing MOQ, particularly for live sports and emerging interactive applications such as betting.
But focusing only on latency risks overlooking the bigger picture. By transporting synchronized video, audio and metadata together, MOQ enables new ways of distributing live media while providing the foundation for richer services built on synchronized information.
As active members of the IETF MOQ working group and Open MOQ consortium, we’re helping shape how synchronized metadata can be transported alongside live media within the emerging standard. As MOQ evolves, we believe this will support more flexible media distribution over IP while enabling richer, more interactive services.
In Part 2, we'll explore the technology behind MOQ's approach to in-play betting, looking at the technical requirements around latency, synchronised playback, timelines, timestamps and delivery records.
