Streaming Architecture & Protocol Comparison
RUSEON Core provides a versatile, multi-protocol video delivery engine. By leveraging a zero-copy Ring Buffer, a single incoming camera stream can simultaneously serve ultra-low latency browser viewers, mobile HLS clients, AI inference services, and continuous disk archiving.
Streaming Protocols Comparison
| Protocol | Typical Latency | Transport | Key Use Case | Client Support |
|---|---|---|---|---|
| WebRTC (WHEP) | < 500 ms | UDP (RTP/RTCP/SRTP) | Live operator monitoring, interactive PTZ control | Native Chrome, Safari, Firefox, iOS, Android |
| Low-Latency HLS | 1.5 – 3.0 s | TCP (HTTP/1.1, HTTP/2) | Broadcast multi-viewer web portals, smart TVs | Safari, Video.js, HLS.js, ExoPlayer |
| RTSP Restreaming | < 200 ms | TCP / UDP | Re-broadcasting feeds to external NVRs and AI engines | VLC, FFmpeg, Milestone, Genetec |
| Archive Playback | On-demand seek | HTTP Range / HLS | Timeline review, incident playback, MP4 export | HTML5 <video>, Video.js, native players |
Zero-Transcoding Quality Preservation
Because RUSEON Core never decompresses video into uncompressed raw pixels:
- Zero Generation Loss: Visual fidelity is 100% identical to the camera's native sensor encoding.
- Minimal End-to-End Latency: Packets arriving over RTSP are repackaged into WebRTC RTP packets within microseconds.
- Sub-1% CPU Overhead: Eliminates GPU requirements for live viewing.