MOQ Video Streaming for Robots, Drones, and Embedded Devices: Powering the Next Generation of Connected Machines

Skip to content

MOQ Beta<br>Now Open For Enterprises

Learn More

explore

Resources

Resources

more

More

legal

Legal

support

Support

Industries

Solutions

Government & Surveillance

Live Events

Broadcast

Gaming

Sports

Truetime Solutions&trade;

Truetime Solutions&trade;

Meetings<br>Host real-time meetings, collaborate live, and broadcast anywhere.

Products

Licensed

Open source

Comparisons

Demo

Resources

Resources

Support

Technology

Protocols

Codecs

Partners

Partners

Cloud & CDN

Hardware

Software

Resellers & Integrators

Red5 Pro

Red5 Cloud

Red5 Pro

Red5 Cloud

Table of Contents

When people think about MOQ ( Media over QUIC), they usually picture live sports, entertainment, or interactive broadcasts. Those are important markets, but some of the protocol’s most interesting opportunities may come from robots, drones, and other embedded devices.

A drone inspecting power lines, a robot entering a burning building, an underwater vehicle examining offshore infrastructure, and a remotely operated medical system all depend on timely video. However, the video may need to reach far more than one remote operator. Command centers, subject-matter experts, AI models, recording systems, and other authorized viewers may all need access to the same feed. That combination of real-time performance, one-to-many distribution, and support for multiple types of subscribers is where MOQ could become the missing link.

Why Robots and Drones Need More Than a Point-to-Point Video Link

Remote devices often begin with a simple requirement: send video from a camera to an operator. Real deployments quickly become more complex.

Consider a drone used during a wildfire. The pilot needs a responsive feed to navigate safely. Incident commanders may need the same stream for situational awareness. An AI service may analyze frames for smoke, people, or changing fire boundaries. A remote specialist may join to assess infrastructure damage, while the full stream is recorded for later review.

The same pattern appears in many industries:

Public safety robots can send video to operators, incident commanders, and remote specialists.

Industrial inspection drones can share feeds with engineers, asset owners, and AI defect-detection systems.

Autonomous or remotely operated vehicles can deliver video and sensor data to control centers and fleet-management platforms.

Agricultural drones can stream crop imagery to operators and computer vision systems.

Underwater vehicles can connect offshore crews with experts located anywhere in the world.

Broadcast drones can supply live production feeds while creating recordings for replays and highlights.

In each case, a single device may produce video that needs to be consumed live, processed by machines, recorded, replayed, and distributed to multiple locations. A point-to-point connection alone does not address the entire workflow.

Where Current Streaming Protocols Fit

Robots, drones, cameras, and embedded devices commonly use protocols such as RTSP, SRT, RTMP, or WebRTC. These protocols remain useful, and MOQ should not be presented as an immediate replacement for all of them.

RTSP is widely used by IP cameras and other connected devices, but browsers do not play RTSP streams natively. A platform typically needs to ingest the feed and convert or restream it for browser playback and broader distribution.

SRT is designed to deliver reliable, low-latency video over unpredictable networks. Its configurable latency buffer allows retransmission of lost packets, but every workflow must balance additional recovery time against responsiveness. SRT is especially valuable for contribution links, although scaling a feed to many different consumers generally requires additional streaming infrastructure.

WebRTC provides real-time browser communication and is already proven in interactive applications. However, it also brings connection-establishment components such as ICE, STUN, and TURN. H.264 is supported in WebRTC browsers, contrary to a common misconception, but interoperability can still depend on compatible H.264 profiles, levels, and packetization modes between an embedded encoder and the receiving endpoint. In some workflows, the stream may still need to be repackaged or transcoded.

These technologies solve important parts of the problem. The opportunity for MOQ is to create a more unified path from contribution through distribution, processing, and playback.

Requirement RTSP SRT WebRTC Potential MOQ fit Common on cameras and embedded encodersStrongGrowingVariesEmergingReal-time remote operationLimited without added infrastructureStrong with tuned latencyStrongDesigned for real-time deliveryNative browser pathNoNoYesYes through WebTransport-based implementationsOne-to-many distributionRequires a media serverRequires a media server or distribution layerRequires...