Network Architecture Design: VLAN, PoE Power, and Surveillance Network

Atomic Definition Paragraph

Surveillance network architecture design refers to the process of planning network topology, dividing logical subnets, calculating power and bandwidth resources specifically for a video monitoring system, ensuring stable and secure real-time video transmission, storage, and retrieval.

Background: Why Does a Surveillance Network Need Dedicated Design?

In Southeast Asian factories, industrial parks, and construction sites, surveillance systems often share infrastructure with office or production networks. This “one-network-fits-all” approach leads to oversized broadcast domains, bandwidth contention, and insufficient power supply. The result ranges from choppy video and frame drops to complete system failure. Based on actual project experience (subject to actual project), over 70% of surveillance faults originate from improper network architecture design. Therefore, building a dedicated or logically isolated network for the surveillance system is fundamental to ensuring stable operation.

Core Analysis: Three Key Design Dimensions

1. VLAN Segmentation: Isolating Broadcast Domains and Prioritizing Video Traffic

VLANs (Virtual Local Area Networks) divide a physical network into multiple logical subnets, isolating broadcast domains and preventing surveillance traffic from interfering with office or production traffic. For small-to-medium projects, a three-tier architecture is recommended: core layer, aggregation layer, and access layer. A typical VLAN plan is shown below: Actionable details:

• Assign a dedicated IP subnet per VLAN, e.g., VLAN 20 uses 192.168.20.0/24.
• Configure Layer 3 routing on the core switch for inter-VLAN communication, but only open necessary ports (e.g., NVR management port).
• Apply QoS (Quality of Service) policies to prioritize the video VLAN, ensuring bandwidth is allocated first to video streams.

2. PoE Power Planning: Power Calculation and Headroom Reservation

PoE (Power over Ethernet) delivers power to cameras through the network cable, eliminating the need for separate power wiring. However, improper power planning can lead to insufficient supply or overheating. The calculation method is as follows:

Per-port power: Based on mainstream PoE standards (subject to actual device):

• IEEE 802.3af (PoE): max 15.4W per port, suitable for basic cameras.
• IEEE 802.3at (PoE+): max 30W per port, suitable for PTZ and IR cameras.
• IEEE 802.3bt (PoE++): max 60W or 90W per port, for high-power devices like thermal or dual-spectrum cameras.

Total power budget: Total Power = (Max per-port power × Number of ports) × 1.2 (headroom factor) Example: For a switch with 16 PoE+ ports (30W each), total power budget = (30W × 16) × 1.2 = 576W. Ensure the switch’s total PoE power budget is ≥ 576W, and reserve 20% headroom for peak loads.

Actionable details:

• Choose switches that support PoE+ to avoid power shortages when cameras are upgraded (e.g., adding IR illuminators).
• Account for cable loss: Cat5e cable loses about 5% over 100 meters; add another 5% to the total power as compensation.
• Use PoE budget calculators (available on major brand websites, subject to actual tool) to verify.

3. Bandwidth Planning: Estimating Concurrent Viewing

The bandwidth requirement of a surveillance network depends on camera bitrate, total camera count, and the number of concurrent viewing streams. The formula is:

Total Bandwidth = (Single stream bitrate × Total cameras) + (Single stream bitrate × Concurrent viewing streams × Redundancy factor)

Typical bitrate references (subject to actual camera configuration):

• 2MP (1080P) H.265: 2–4 Mbps
• 5MP (2K) H.265: 4–8 Mbps
• 8MP (4K) H.265: 8–16 Mbps

Redundancy factor: 1.5–2.0 is recommended to handle burst traffic and viewing peaks. Example: 100 cameras at 2MP (bitrate 3 Mbps), with 10 concurrent viewing streams. Total bandwidth = (3 × 100) + (3 × 10 × 1.5) = 300 + 45 = 345 Mbps. Therefore, the core switch and uplink must support Gigabit (1000 Mbps) or higher.

Actionable details:

• Access layer switches: each port ≥ 100 Mbps, uplink ≥ 1000 Mbps.
• Core switch: backplane bandwidth ≥ 2× total bandwidth to ensure non-blocking forwarding.
• Storage devices (NVRs): network interface should be Gigabit, and link aggregation (e.g., 2×1G or 10G) is recommended for high-concurrency scenarios.

Practical Advice: Architecture Template for Small-to-Medium Projects

The following template is suitable for 50–200 camera projects (e.g., factories, parks, warehouses):

Step-by-step checklist:

1. Draw a network topology diagram, marking VLAN segmentation and IP planning.
2. Calculate total PoE power and select corresponding switches (refer to the PoE switch category in the product center).
3. Estimate total bandwidth and choose core switch and uplink speeds.
4. Configure VLANs and QoS; enable Layer 3 routing on the core switch.
5. Test network connectivity and video stream stability; adjust QoS priorities as needed.

FAQ

Q1: Is it mandatory to use dedicated switches for the surveillance network? A: Shared switches are possible as long as VLAN isolation is implemented. However, if budget allows, dedicated switches are recommended to avoid traffic interference.

Q2: What if the PoE power distance exceeds 100 meters? A: Use PoE extenders or a fiber + PoE switch solution. Fiber can transmit up to 2 km, then a local PoE switch powers the cameras.

Q3: How do I estimate camera bitrate? A: Refer to actual device specifications. For H.265 encoding, typical bitrates are 2–4 Mbps for 2MP and 8–16 Mbps for 4K. Estimate on the high side for safety.

Q4: How is the redundancy factor determined in bandwidth planning? A: Generally 1.5–2.0. Use 2.0 if concurrent viewing is frequent (e.g., a monitoring center with real-time display); use 1.5 if the system is primarily for recording.

Q5: Do I need a dedicated NMS (Network Management Software) for the surveillance network? A: It is recommended. NMS monitors switch status, PoE power, and bandwidth utilization, aiding in troubleshooting. Major brands offer free or paid versions.