Concepts and profilesLink to the section Concepts and profiles
On this page
These terms describe the roles and information used by the v0.2 working draft. Start with the introductory guide or follow the worked example to see them together.
Device and ClientLink to the section Device and Client
A UNIVIP Device is software that exposes a vehicle's capabilities through UNIVIP. It can run in vehicle or dock firmware, a controller app, or a gateway. One gateway can represent several vehicles, each with its own device identity.
A UNIVIP Client receives that information. It can be a compatible VMS, command platform or recorder. An existing VMS needs UNIVIP support or an integration built against the protocol.
Video, telemetry and eventsLink to the section Video, telemetry and events
| Information | Example | Operator use |
|---|---|---|
| Video | A camera stream over WebRTC | See the scene |
| Telemetry | Position, heading, battery, link quality | Understand where the vehicle is and its current condition |
| Event | Low battery becomes active or clears | Notice a change that needs attention |
Video and telemetry have a defined time relationship. A Client can display or replay the position associated with a video frame. See media timing for the exact requirements.
Profiles S, C and NLink to the section Profiles S, C and N
S is the foundation: surveillance and streaming. C adds camera and payload control. N adds authorized vehicle tasking. C and N independently require S; N does not require C.
The profile diagram and feature matrix show what is mandatory and optional. A profile name describes a set of requirements; it does not certify any particular implementation.
Capabilities and control leasesLink to the section Capabilities and control leases
A capability document lists what this particular device supports. The Client reads it before choosing streams or showing controls. A command's presence in the specification does not mean that every device supports it.
A control lease is a time-limited grant of authority to a Client for a particular scope. Camera and vehicle leases are separate. Vehicle commands require a valid vehicle lease, and the Device still enforces operator authority, limits and controller safety.
Command statusLink to the section Command status
ACCEPTED means the Device will attempt a command. The later status messages establish the outcome: completion, failure, cancellation or supersession. See the command lifecycle.