Integrate a VMSLink to the section Integrate a VMS
On this page
A UNIVIP Client hosts the endpoint that Devices connect to. It receives capabilities, telemetry and events, negotiates media, and maps supported controls to its own operator permissions. A VMS needs this integration to work with UNIVIP Devices.
Start with the viewerLink to the section Start with the viewer
Run the simulator and web viewer to see the reference Client behavior. The viewer uses the .NET Client SDK and provides a concrete example of video, a map, telemetry, events and optional control.
Host a Device session endpointLink to the section Host a Device session endpoint
The .NET SDK exposes AddUnivipClient and MapUnivipSession for ASP.NET Core. Configure a stable ClientId, authenticate connecting Devices and restrict each credential to its permitted Device identities. The configured Client identity must match the identity the Device expects.
The SDK quick start contains the setup code. Part 05 defines the handshake, ordering, keepalive and session proxy; Part 13 defines security requirements.
Build the operator view from capabilitiesLink to the section Build the operator view from capabilities
Read advertised profiles, streams and command capabilities before enabling UI controls. Display position with its vertical reference, distinguish stale or offline state, and preserve active versus cleared event conditions.
The SDK's Device directory holds the latest state and exposes updates. Its REST client can use a Device listener or the session proxy. See Capabilities, Telemetry and Events.
Negotiate and record mediaLink to the section Negotiate and record media
The VMS supplies its WebRTC stack. Use the advertised stream and the SDK's signaling helpers to exchange offers, answers and candidates. The session channel carries signaling; video uses the media plane.
Preserve the relationship between video and telemetry in live display and recording. Media and synchronized metadata defines the timing and recording requirements, and the recording test describes the reference replay evidence.
Keep camera and vehicle authority separateLink to the section Keep camera and vehicle authority separate
Map CameraControl and VehicleControl to distinct VMS permissions. LeaseHandle renews a lease and releases it on disposal; CommandHandle follows status to an outcome. The Client must show lease state and expiry and must never present ACCEPTED as completion.
Follow Profiles, Camera control and Vehicle control. Review the internal WebRTC security report and roadmap for the reference implementation's remaining gates.