Part 02 — TerminologyLink to the section Part 02 — Terminology
Maturity: Draft · Profiles: all
| Term | Definition |
|---|---|
| Vehicle | The uncrewed mobile platform: an aircraft (UAV/RPAS), an underwater vehicle (UUV/ROV/AUV), a surface vessel (USV) or a ground vehicle (UGV). Called "drone" informally. |
| Domain | The medium the vehicle operates in: AIR, UNDERWATER, SURFACE, GROUND, or MULTI for vehicles that cross media. |
| Aircraft | A vehicle in the AIR domain. Used in this specification only where a requirement is aviation-specific. |
| Payload | A camera or other sensor carried by the vehicle, together with its gimbal if any. A vehicle may carry several payloads. |
| Gimbal | The stabilized mount that points a payload independently of the vehicle body. |
| Dock | A fixed or mobile station that houses, charges and may launch and recover a vehicle (including a tether management system or launch-and-recovery system for underwater vehicles). |
| Controller | The hardware or software that the remote pilot uses to operate the vehicle. |
| Operator | The organization or person legally responsible for the operation. The operator holds operator authority: the final say over whether the vehicle moves. |
| Remote pilot (pilot) | The person exercising operator authority in real time, if any. |
| UNIVIP Device (device) | The UNIVIP endpoint that represents one vehicle (and its payloads and dock, if any) to clients. May run natively, on the controller or dock, or in a gateway. |
| Gateway | Software that implements UNIVIP on behalf of one or more vehicles by translating a native protocol or API. |
| UNIVIP Client (client) | A consumer of UNIVIP: a VMS, recorder, command-and-control platform, map application or test tool. |
| Session | A long-lived, authenticated, device-initiated connection between one device and one client over which real-time channels are multiplexed (Part 05). |
| Session channel | The secure WebSocket (or MQTT alternative) connection carrying telemetry, events, WebRTC signaling and command status within a session. |
| UNIVIP endpoint | The client-side HTTPS/WSS service that devices connect to (/univip/v1/session). When it also serves the REST surface for devices that do not host it, it is a client-hosted endpoint and forwards each REST request to the device as a request envelope (session proxy, Part 05 §5.5.1). |
| Verified client identity | The client_id a device associates with a session from its own configuration of the endpoint it connected to, after authenticating that endpoint (Part 05 §5.3.1). |
| Capability document | The JSON document in which a device declares exactly which profiles, features, limits, transports and schema versions it supports (Part 06). |
| Telemetry | Continuous, periodically published state of the vehicle and payloads (Part 07). |
| Event | A discrete notification of a state change or occurrence (Part 08). |
| Command | A request from a client to a device to change state (Parts 10 and 11). |
| Control lease | A time-limited, scoped grant of control authority from the device (on behalf of the operator) to one client (Part 11). |
| Profile | A named, testable set of mandatory features. UNIVIP defines Profiles S, C and N (Part 04). |
| Operation | One deployment from launch (take-off, dive, departure) to recovery (landing, surfacing and recovery, return), identified by session_id. Distinct from the connection "session". Where ambiguity is possible this specification says "operation". |
| Media time | The timeline of a video stream as carried in RTP timestamps or container presentation timestamps, which UNIVIP relates to wall-clock time (Part 09). |
| AGL / MSL / HAE | Above Ground Level / Mean Sea Level / Height Above (WGS84) Ellipsoid. See ADR-0006. |
| Depth | Distance below the water surface, positive downward (depth_m). Seabed clearance is altitude_above_seabed_m. |
| NED | North-East-Down coordinate convention. |
| VMS | Video Management System. |