Tutorials · AI

How to Plan the Network for AI Cameras and Video Analytics

AI video means more streams, higher resolutions and analytics servers pulling video from many cameras. Size bandwidth, PoE and storage before you install.

Intermediate12 min6 steps

Before you start

  • Camera list with resolution, codec and frame rate
  • Where analytics runs: camera, NVR or edge server

Step by step

  1. Count every stream

    Each camera may send a main stream to the NVR and a second stream to an analytics server or viewing client. Add them all.

  2. Estimate bandwidth

    Use the bitrate per stream (for example 4–8 Mbit/s for 4K H.265 at 15 fps) × streams × cameras, plus 30% headroom. Keep access ports at 1G and uplinks at 10G where many cameras meet.

  3. Check the PoE budget

    AI cameras with IR, heaters or PTZ draw more power. Use the maximum figure from the datasheet, and PoE+ or PoE++ ports where needed.

  4. Place the analytics

    Analytics on the camera sends only events. Analytics on an edge server (for example a NavEdge in the comms room) pulls full streams over the LAN: keep it on the camera VLAN or route between VLANs at line rate on a Layer 3 switch.

  5. Size storage

    Use your bitrate and retention days to size NVR disks; event-only recording for low-priority cameras cuts storage sharply.

  6. Segment and protect

    Keep cameras, NVRs and analytics servers on their own VLAN, with no direct Internet access.

Pro tips

  • Multicast can reduce load when many clients view the same camera; plan IGMP snooping on the switches.
  • Monitor uplink utilisation after go-live; analytics loads grow as features are added.