Prior Art and Standards LandscapeLink to the section Prior Art and Standards Landscape
On this page
Status: Research scan, 2026-10-14. Items marked ⚠ were not verified against the primary document during this scan and must be confirmed in the formal review (see "Formal review plan").
1. PurposeLink to the section 1. Purpose
Before UNIVIP can credibly claim a gap, the project must show that it understands what exists, where each existing standard stops, and how UNIVIP reuses rather than duplicates it. This document is the starting inventory.
2. InventoryLink to the section 2. Inventory
2.1 ONVIFLink to the section 2.1 ONVIF
| Item | Relevance |
|---|---|
| Profile S | Basic video streaming, PTZ, audio, multicasting, relay outputs. The historical baseline every VMS supports. UNIVIP Profile S borrows the name deliberately so that "Profile S" means "the mandatory streaming baseline" in both worlds. |
| Profile T | Advanced video streaming (H.264/H.265), imaging settings, motion alarm and tampering events, metadata streaming, bidirectional audio. |
| Profile M | Metadata and events for analytics applications. ONVIF states Profile M can apply to a video-based drone and that clients include VMS software. Defines analytics metadata (objects, geolocation attributes) and event handling. Does not define vehicle state or navigation. |
| Profile V (release candidate) | Device-initiated secure uplink to cloud VMS, WebRTC video, event communication with MQTT in the event model. Architecturally closest to what a drone needs because it abandons the camera-on-LAN assumption. |
| PTZ Service | Continuous, relative and absolute move with configurable spaces. UNIVIP maps camera.gimbal.* onto PTZ semantics so a UNIVIP gateway can expose a gimbal to a PTZ-only VMS. |
| Uplink / WebRTC specifications | Mechanism for device-initiated connections; used as the reference design for UNIVIP's outbound session channel. |
| Profile policy v3.2 ⚠ | Describes how new profiles are proposed and approved. Required reading for Route B. |
Gap: no drone vehicle state, no aircraft commands, no control-lease model, no altitude-reference discipline, no frame-synchronized flight telemetry.
2.2 MAVLink (Dronecode Foundation)Link to the section 2.2 MAVLink (Dronecode Foundation)
| Item | Relevance |
|---|---|
Common message set (GLOBAL_POSITION_INT, ATTITUDE, SYS_STATUS, BATTERY_STATUS, GPS_RAW_INT, HEARTBEAT, EXTENDED_SYS_STATE) |
Direct source for UNIVIP telemetry fields; UNIVIP's gateway mapping table cites them. |
Camera protocol (CAMERA_INFORMATION, VIDEO_STREAM_INFORMATION, zoom/focus commands) |
Source for payload capability discovery. MAVLink's own documentation acknowledges limits around frame-synchronized video metadata. |
Gimbal protocol v2 (GIMBAL_MANAGER_*, GIMBAL_DEVICE_*) |
Defines gimbal control authority and attitude reporting; informs UNIVIP's gimbal frame conventions. |
Mission protocol, MAV_CMD_NAV_*, MAV_CMD_DO_SET_MODE, MAV_CMD_NAV_RETURN_TO_LAUNCH |
Source for vehicle.* command mapping. |
| MAVLink 2 signing | Message authentication; not a substitute for TLS-level transport security in UNIVIP. |
Gap: MAVLink is a vehicle protocol, not an enterprise integration protocol. It has no notion of a VMS, no HTTP/REST or WebRTC surface, no multi-tenant identity, no capability negotiation in the ONVIF sense, and in practice is not exposed by consumer or enterprise drones from the largest manufacturers.
2.3 MISB / STANAG 4609 motion imageryLink to the section 2.3 MISB / STANAG 4609 motion imagery
| Item | Relevance |
|---|---|
| MISB ST 0601 (UAS Datalink Local Set) | KLV-encoded platform position, attitude, sensor orientation, field of view, frame center and corner coordinates, multiplexed with video in MPEG-2 TS. Exactly the "synchronized metadata" UNIVIP needs for recordings. UNIVIP's in-band metadata option is ST 0601; UNIVIP defines a mapping between its JSON telemetry and ST 0601 tags rather than a new encoding. |
| MISB ST 0603 / ST 0604 ⚠ | Time stamping and time transfer for motion imagery. Reference for UNIVIP's clock requirements. |
| MISB ST 0903 | VMTI (video moving target indicator) metadata. Reference for the analytics-object part of the geospatial extension. |
| STANAG 4609 | NATO adoption of the MISB stack. |
Gap: military-oriented, no discovery or capability negotiation, no interactive control plane, no modern web transports, limited VMS adoption outside defense.
2.4 NATO STANAG 4586Link to the section 2.4 NATO STANAG 4586
Defines UAV Control System interoperability with Levels of Interoperability (LOI 1: indirect receipt of payload data; LOI 2: direct receipt of payload data; LOI 3: control and monitoring of the payload; LOI 4: control and monitoring of the UAV, less launch and recovery; LOI 5: full control including launch and recovery). UNIVIP's Profile S/C/N ladder is intentionally analogous to LOI 2/3/4.
Gap: heavyweight, defense procurement oriented, not a plug-and-play commercial profile.
2.5 SAPIENT / BSI Flex 335Link to the section 2.5 SAPIENT / BSI Flex 335
UK-originated interface for autonomous sensors, effectors and fusion nodes: registration, status, detection reports, tasking. Relevant to how UNIVIP devices register and report detections to a higher-level system, and a candidate interoperability target for the geospatial extension.
Gap: not video-centric, no VMS media model.
2.6 Vendor APIsLink to the section 2.6 Vendor APIs
| Vendor | What it shows |
|---|---|
| DJI Cloud API (dock, DRC) | MQTT-based telemetry and control, live streaming, payload control, flight tasks. Proves the architecture; locked to DJI. Primary gateway target. |
| Skydio Cloud APIs | RTSP video, live telemetry, external integration. Second gateway target. |
| Autel, Parrot, Teledyne FLIR, others ⚠ | To be inventoried. |
| Drone-in-a-box operators and C2 platforms (DroneSense, DroneDeploy, FlytBase, Auterion, UgCS, etc.) ⚠ | Several already integrate with VMS products through bespoke connectors. These companies are both potential adopters and potential competitors to a standard; their integration shapes should be studied as implementation experience. |
2.7 Adjacent standards worth monitoringLink to the section 2.7 Adjacent standards worth monitoring
| Item | Why |
|---|---|
| ASTM F3411 (Remote ID) | Broadcast identity and position of UAS; UNIVIP identity SHOULD be able to carry the Remote ID serial/session ID so a VMS can correlate UNIVIP devices with Remote ID observations. |
| ASTM F3548 (UTM/USS interoperability) | Airspace authorization; out of UNIVIP scope but Profile N implementations will need to respect it. |
| OGC SensorThings API, OGC Moving Features | Geospatial observation models; possible future alignment for the geospatial extension. |
| OpenC2 | Command-and-control language for cyber defense; a reference for command/response design patterns. |
| EU U-space (Regulation 2021/664), FAA Part 107/108 ⚠ | Regulatory constraints on remote operation that Profile N documentation must acknowledge. |
3. Gap analysisLink to the section 3. Gap analysis
| Capability a VMS needs | ONVIF | MAVLink | MISB 0601 | STANAG 4586 | Vendor APIs | UNIVIP |
|---|---|---|---|---|---|---|
| Discovery and capability negotiation | ✅ | partial | ❌ | partial | per vendor | ✅ |
| Live video to a VMS | ✅ | stream URI only | ✅ (TS) | ✅ | ✅ | ✅ |
| Device-initiated cloud uplink | Profile V | ❌ | ❌ | ❌ | ✅ | ✅ |
| Position/attitude telemetry | geolocation metadata only | ✅ | ✅ | ✅ | ✅ | ✅ |
| Frame-synchronized telemetry in recordings | ❌ | ❌ | ✅ | ✅ | partial | ✅ (via 0601 + out-of-band) |
| Health, battery, link events | partial | ✅ | ❌ | ✅ | ✅ | ✅ |
| Gimbal/camera control | PTZ/imaging | ✅ | ❌ | ✅ | ✅ | ✅ |
| Vehicle control | ❌ | ✅ | ❌ | ✅ | ✅ | optional (Profile N) |
| Separate camera vs vehicle authorization | n/a | partial | n/a | LOI levels | per vendor | ✅ |
| Vendor-neutral conformance program | ✅ | ❌ | partial | NATO | ❌ | planned |
| Commercial VMS adoption | ✅ | ❌ | low | ❌ | bespoke | target |
4. Reuse policyLink to the section 4. Reuse policy
UNIVIP reuses rather than reinvents:
- ONVIF: profile concept, event topic structure, PTZ semantics, Profile V uplink pattern, WebRTC video.
- MAVLink: telemetry field semantics, command vocabulary, gimbal frame conventions.
- MISB ST 0601: in-band metadata encoding and tag semantics for recordings.
- STANAG 4586: the level-of-interoperability ladder as the model for profiles.
- IETF/W3C: TLS 1.3, OAuth 2.0 / JWT, mTLS, WebRTC, WebSocket, RFC 3339 time, GeoJSON.
- OASIS: MQTT 5.
UNIVIP defines only: the unified JSON data model, the capability document, the REST/WebSocket session interface, the control-lease and safety model, the event catalog, the geospatial extension, the mappings, and the conformance rules.
5. Formal review planLink to the section 5. Formal review plan
Before any public first-of-its-kind claim:
- Obtain and read the current ONVIF Profile M, Profile V, Uplink and WebRTC specifications, and the profile policy. Confirm the Profile V status and event model details.
- Obtain MISB ST 0601 (current edition), ST 0603, ST 0604 and ST 0903. Build the tag-level mapping in
spec/09-media.mdfrom the primary text. - Review STANAG 4586 Edition 4 (or current) LOI definitions.
- Review BSI Flex 335 current version.
- Inventory at least five additional drone vendor APIs and at least five drone C2 / drone-in-a-box platforms with existing VMS connectors.
- Commission a professional trademark search for "UNIVIP" and "Universal Vehicle Interoperability Protocol" in the relevant classes and jurisdictions.
- Commission a patent landscape search covering drone-to-VMS integration, synchronized telemetry recording and remote drone tasking from security software.
6. References (starting set)Link to the section 6. References (starting set)
- ONVIF Profile M: https://www.onvif.org/profiles/profile-m/
- ONVIF Profile V: https://www.onvif.org/profiles/profile-v/ and FAQ https://www.onvif.org/profiles/profile-v/faq/
- ONVIF membership levels: https://www.onvif.org/join-us/membership-levels/
- ONVIF profile policy v3.2: https://www.onvif.org/wp-content/uploads/2023/07/onvif-profile-policy-v3-2.pdf
- MAVLink camera protocol: https://mavlink.io/en/services/camera.html
- MAVLink gimbal protocol v2: https://mavlink.io/en/services/gimbal_v2.html
- STANAG 4586 overview (US Government Publishing Office): https://www.govinfo.gov/content/pkg/GOVPUB-D5_400-PURL-gpo5868/pdf/GOVPUB-D5_400-PURL-gpo5868.pdf
- BSI Flex 335 / SAPIENT: https://www.bsigroup.com/en-US/insights-and-media/insights/brochures/bsi-flex-335-interface-of-the-sapient-sensor-management-specification/
- DJI Cloud API, DRC: https://developer.dji.com/doc/cloud-api-tutorial/en/feature-set/dock-feature-set/drc.html
- Skydio live telemetry: https://apidocs.skydio.com/reference/live-telemetry
- SRT protocol: https://github.com/haivision/srt
- MISB standards registry: https://nsgreg.nga.mil/misb.jsp