UnitedRhino 联犀
Book a demoStart now

IoT / Foundation

Look beyond device readings and see the site.

Organize cameras and channels, live preview, recordings, and controls so video can support project workflows.

IoT SIM guide ↗Back to the foundation →

THE CUSTOMER PROBLEM

Start with the connectivity management problem.

When a field device behaves unexpectedly, readings may show the result while video offers a way to observe the site. Camera access, browser playback, and recording storage are separate paths; one playback screenshot does not prove that every capability is enabled.

INSIDE THE FOUNDATION

Access, playback, and recording follow different paths

Video capability overview · No live stream is connected, and no PTZ or recording action is performed.

MECHANISM / REASON / TRADE-OFF

See how the capability works through the interface.

01

Separate device access from browser playback

GB28181, ONVIF, RTSP, and RTMP cover different device access patterns. A media service handles streams, while browsers use configured playback such as WebRTC or HLS.

What this saves customers
Business pages do not need to implement each device registration, directory, and stream protocol.
Choice and trade-off
Network conditions, device support, and media-service settings affect availability. Control features vary by device.
02

Manage devices and channels separately

Cameras and NVRs are managed as devices; channels identify individual video sources. Preview, PTZ, and presets are available only when the device supports them.

What this saves customers
One device can expose multiple channels, and a channel state may differ from the device state.
Choice and trade-off
After discovery or registration, verify each channel, stream, and playback path.
03

Distinguish platform recordings from device recordings

Platform recordings follow configured retention. GB28181 device recordings are searched and played back from the device. Show the source, time range, and available records.

What this saves customers
No platform recording for a time range does not prove that the device has no recording, or the reverse.
Choice and trade-off
Show an empty result when none is returned. Do not invent footage or imply that video access includes AI vision by default.
Historical security-case video previewA public historical security interface; it is not a live camera service.

A CONCRETE EXAMPLE / MECHANISM EXAMPLE

Review a site camera live view and its history

This is an interaction outline. The real screenshots come from an existing security case; the website does not connect to cameras or move a PTZ camera.

  1. Choose a device and channel within the project scope
  2. Check preview status and supported controls
  3. Choose a recording source and time, then review returned footage

READY TO INTEGRATE

Confirm these points before connecting.

IoT SIM guide ↗
  • Confirm device protocols, network paths, and media-service configuration
  • Define channel access and recording-retention requirements
  • Verify playback, controls, and recording retrieval separately

IN PRACTICE

Move from capability checks to delivery.

All cases →

The security case shows a historical interface; it does not represent a live video or recording service.

Verify access, playback, PTZ controls, and recording search separately against the device and deployment.

CONTINUE WITH THE FOUNDATION

Explore more of the same foundation.

Device operations →

Connect device identity, channel topology, status, and maintenance records.

Automation and alerts →

Separate rule triggers, device actions, alert events, and human response.

Configuration and visualization →

Bring device data and field context into business interfaces.

Develop with your own AI tools →

Skills provide methods and templates; CLI acts with the user’s authorization. WorkBuddy and similar tools belong to the customer’s development workflow.

Organizations, apps, and project permissions →

A visible interface does not imply permission to act. Business APIs continue to enforce data scope.

Start by checking one SIM.

Prepare channel credentials, device bindings, and synchronization requirements. Check timestamps and task results, then correlate device logs.

View the device connection path →
Back to the IoT overview →