Scenario Guide

Project: Product Specification | page_id: 1758

40-Channel 400-Concurrent Streaming Media Server — Scenario Usage Guide

Model: XSWTVS-400M40CH/F| Practical Manual

Scenario 1: Smart Campus / Building Security (Core Scenario)

Applicable

Small and medium-sized campuses, office buildings, factories and other sites with surveillance points within 40 channels that need unified access, storage, forwarding and video wall display.

System Topology

[Camera 1~40] --RTSP/ONVIF--+
                           |

[Network switch] <-------------+--RJ45--> [40-Channel 400-Concurrent Streaming Media Server]
                           |              |

[Management PC] <--LAN----------+         [HDMI/VGA]--> [Surveillance large screen]

[Phone/tablet] <--domain name/DNS---(extranet)----+

Operation Steps

1. Hardware installation
   - Install the device into a 19-inch standard cabinet (1U height)
   - Connect AC 100-240V power
   - Connect network port 1 to the core switch (camera network)
   - Optional: connect network port 2 to an independent management network

2. Camera access
   - Log in to the web management interface (default address on the device label or in the manual)
   - Add camera channels (supports ONVIF auto discovery / manual addition)
   - Configure stream parameters for each channel (main stream / sub stream)
   - After all 40 channels are added, check the online status

3. Storage configuration
   - Set the recording plan as needed (24h continuous / motion detection / scheduled recording)
   - Recommended allocation for 8TB storage space:

   • 40 channels 1080P @ 4Mbps → about 7 days playback period
   • Bitrate and recording policy can be adjusted on demand

4. Decoding to video wall
   - Connect the HDMI output to a large-screen TV / video wall
   - Configure the video wall layout (1/4/9/16 screen split)
   - Select the camera channels to be displayed on the wall
   - Supports simultaneous decoding output of 2 channels of 4K or 16 channels of 1080P

5. Remote access configuration
   - Configure a DNS domain name (supports dynamic domain name resolution)
   - Enable HTTPS secure access
   - Create user accounts and assign permissions
   - Phones/computers can view remotely through the domain name

Precautions

• Dual network ports can achieve network isolation: one connected to the camera intranet, one to the management extranet
• The RS485 interface can be used to connect a PTZ decoder to control speed dome cameras
• It is recommended to check disk space and system logs regularly

Scenario 2: Chain Store Video Aggregation

Applicable

Video from multiple store cameras aggregated to headquarters, where headquarters management, security, operations and other departments view simultaneously.

System Topology

[Store A camera] --Internet (public network)---+
[Store B camera] --Internet (public network)---+                              [HQ management PC]
                                               +--> [Streaming media server] <--LAN--+  [Operations dept PC]
[Store C camera] --Internet (public network)---+                              [Security large screen]

Operation Points

1. Cameras in each store must support public network push or access via VPN/port mapping
2. Manage by group on the server according to store name (e.g. "Central China Region - Store 001~010")
3. Use the 400 concurrency capability to support multiple departments and users viewing different store views simultaneously
4. Set different user permissions:
   - Super administrator: all permissions
   - Regional manager: can only view stores under their jurisdiction
   - Store manager: can only view their own store
5. Keep recordings for more than 30 days for later traceability

Precautions

• Pay attention to bandwidth and security for public network access (HTTPS must be enabled)
• It is recommended to set an independent device group and view template for each store

Scenario 3: Campus / Hospital Security

Applicable

Schools, hospitals and other places with high data privacy requirements, where video data must not leave the intranet.

Operation Points

1. Deploy all devices on the internal private network, not exposed to the public network
2. If mobile access is needed, use VPN or intranet mapping for secure access
3. Key areas on campus:
   - School gate / perimeter wall (face capture linkage)
   - Classroom / corridor (daily surveillance)
   - Canteen / playground (densely populated areas)
   - Server room / finance office (high-security areas)
4. Special requirements in hospital scenarios:
   - Ward areas need privacy protection (some channels can be set to be viewable only by authorized personnel)
   - Pharmacy warehouse / cashier require 24-hour continuous recording
5. The audio input interface can be connected to an emergency alarm button / intercom system

Compliance Reminder

• Video data is stored locally, complying with the requirements of the Data Security Law
• It is recommended to enable the operation audit log to record all viewing activities
• Principle of least privilege for user permissions: only give the necessary people access to the necessary channels

Scenario 4: Fast Deployment for Construction Sites / Temporary Projects

Applicable

Construction sites, exhibitions and events, temporary security projects that need to quickly build a surveillance system.

Fast Deployment Checklist

• [ ] Power on the device (AC 100-220V site power is sufficient)
• [ ] Connect to the site LAN (or use a 4G router directly)
• [ ] Camera PoE power supply + network cable connection
• [ ] Add cameras via the web interface (ONVIF discovery is fastest)
• [ ] Connect a monitor via HDMI to confirm the image
• [ ] Configure a domain name (if remote viewing is required)

Migration After Project Ends

• Recording files can be exported through the USB port
• The whole device can be relocated to the next project site
• Configuration can be backed up and restored, no need to re-add channels one by one

General Operation Quick Reference

First Power-On Initialization Flow

1. Power on → wait about 60 seconds for system startup to complete
2. Access the device IP from a browser on a computer in the same network segment (default on the device label)
3. Log in with the default account (see device label or manual)
4. Change the default password
5. Configure network parameters (IP/subnet mask/gateway/DNS)
6. Add camera channels
7. Configure storage plan and user permissions

Routine Maintenance Checklist

Troubleshooting Quick Reference

Common Commands and Interfaces