Connect vehicles to your video management system

Working draft 0.2.0 · Aerial conformance test scope

An open protocol for synchronized video, telemetry and events, with separately authorized camera and vehicle control.

Start with the basicsRead the specification

How it works

A UNIVIP Device runs in vehicle firmware, a controller or a gateway. It sends video, position, health and events to a compatible VMS. Authorized commands return through the same interface.

A vehicle exposes a UNIVIP Device from firmware, a controller or a gateway. Video, telemetry and events flow to a VMS; authorized commands return to the vehicle. Camera and vehicle control have separate permissions.
Conceptual overview of the v0.2 working draft. Aerial conformance tests are defined; other vehicle domains remain reserved. Open full-size illustration.

Choose a starting pointLink to the section Choose a starting point

Choose what an operator can doLink to the section Choose what an operator can do

Profile Provides
S — Surveillance and Streaming Video, synchronized telemetry and events
C — Camera and Payload Control S plus advertised camera and payload controls
N — Navigation and Vehicle Control S plus separately authorized vehicle tasking

C and N independently extend S. Camera control and vehicle control have separate permissions. Compare the requirements.

Project statusLink to the section Project status

UNIVIP is a v0.2 working draft with Python and .NET reference implementations. The draft defines aerial conformance tests; other vehicle domains remain reserved. Reference interoperability reports do not establish certification or readiness for operational use.

Run the simulator · Review the roadmap · Contribute