Wireless Camera Bridges: PtP and PtMP Link Design and Installation

Wireless camera bridge design: PtP vs PtMP, airtime sharing, Fresnel calculation, capacity headroom, mounting, encryption and a troubleshooting order with iperf3.
Technical summary
Technology
5 GHz and 60 GHz radio bridges, PtP, PtMP, TDMA, iperf3, ITU-R P.530
Topic
Bringing cameras from points where cable can’t be run
Level
Intermediate
Prerequisites
  • Knowledge of camera bitrate and stream profiles
  • Basic RF concepts (dBm, dBi)
In this article8 sections

A car park pole, a guardhouse in the warehouse yard, a building across the road: when cable can’t be run because of digging permits, cost or time, the way to bring a camera from that point is often a wireless bridge. Camera traffic doesn’t behave like office traffic; it flows continuously, mostly in one direction, and outages are paid back as recording gaps. Below, point-to-point (PtP) and point-to-multipoint (PtMP) bridge design for cameras is explained: capacity headroom, airtime, the effect of latency on live viewing, mounting and troubleshooting order.

When a wireless bridge is the right solution

A wireless bridge doesn’t replace a fiber optic camera backbone; it’s used where fiber isn’t possible or economical. Answer these questions in order to decide:

  1. Is there a clear line of sight (LoS) between the two points, or can it be achieved with mast height? If not, the bridge option is weak.
  2. Does the total traffic of the cameras at the remote point stay comfortably below the bridge’s measured capacity?
  3. Is recording loss acceptable when the link drops, or is edge recording (SD card) or a local recorder needed at the remote point?
  4. Could the line of sight be blocked later by a new building, a growing tree or a stacking area?
  5. Can reliable power and lightning protection be provided at the remote point?

If line of sight is problematic, the distance is short and digging is possible, fiber almost always lasts longer. A bridge installed today can lose out to a poplar tree growing five years later. For fiber design in a camera backbone, see the fiber camera backbone design guide.

PtP and PtMP architectures

PtP is a dedicated link between two fixed points using narrow-beam antennas. All radio capacity is dedicated to a single link; it suits long distances and high capacity. In PtMP, a base station with a wide-angle (sector) antenna at the center serves multiple client radios in the field. Installation is economical, but capacity is shared among all clients.

The decisive concept in PtMP is airtime. The channel can be used by only one transmitter at any moment; capacity is divided by the number of clients, and sharing is done by time, not by bits. A client with a weak signal running at low modulation (MCS) spends much more time sending the same data and eats into others’ capacity too. The weakest link determines the sector’s performance. One bad client is enough.

The standard Wi-Fi access method (CSMA/CA) is prone to the “hidden node” problem in PtMP: distant clients that can’t hear each other transmit at the same time and collide. That’s why most outdoor bridge products use vendor-specific scheduled (TDMA/polling) protocols. One setting of these protocols is particularly important in a camera scenario: traffic flows mainly from clients (cameras) to the center. If the download/upload ratio in the time frame can be adjusted, set it in favor of the remote-to-center direction. Default profiles often favor the download direction with internet access in mind. Camera traffic flows the other way.

Criterion PtP PtMP
Capacity Dedicated to a single link Shared among all clients
Range Long (narrow beam, high gain) Shorter (sector antenna)
Suitable scenario Remote point with many cameras, between buildings Scattered points with few cameras
Risk Alignment sensitivity A weak client slowing down the whole sector

Choosing the frequency band and channel width

The most common band for bridges in corporate camera systems is 5 GHz. 2.4 GHz isn’t suitable for links with many cameras because of heavy use and narrow channel options. The 60 GHz band gives very high capacity over short distances; oxygen absorption and rain attenuation limit range, so it’s usually preferred for links of a few hundred meters. Frequencies, channel widths and transmit power (EIRP) limits in Türkiye are subject to BTK (the Turkish telecom regulator) rules; check the device’s country setting during installation.

Channel width is a balance between capacity and robustness. An 80 MHz channel offers higher peak capacity but also collects noise over a wider band, and finding a clean channel gets harder. In a crowded spectrum, a link running stably at high modulation on 40 MHz usually gives more real throughput than one constantly dropping modulation on 80 MHz. A wide channel isn’t always fast. Choose the channel with a spectrum scan before installation, not by guesswork.

Line of sight and Fresnel zone calculation

A radio link doesn’t need a straight line but an ellipse-shaped zone between the two antennas (the first Fresnel zone). The radius at the midpoint, where the zone is widest, is found with this formula:

r (m) = 8.66 × √(D / f) — D: link distance (km), f: frequency (GHz)

Example calculation: for 1 km at 5.5 GHz, r = 8.66 × √(0.182) ≈ 3.7 m. The common design rule is that at least 60% of this radius stays unobstructed; so at the midpoint there should be no obstruction within about 2.2 m below the line. A link isn’t sound just because the antennas “see” each other. Also factor in trees’ height when in leaf, warehouse stacking height and, over long distances, the earth’s curvature. The theoretical basis is in the ITU-R P.530 recommendation.

The link budget calculates the received signal level from transmit power, antenna gains, free-space loss and cable/connector losses, and compares it with the receiver sensitivity needed for the target modulation. The detailed calculation and fade margin are in the point-to-point bridge between buildings and link budget guide; here we look at capacity headroom specific to cameras.

The speed on a bridge datasheet is the radio PHY rate. Because of protocol overhead, retransmissions and half-duplex operation, real application throughput stays significantly below it. Capacity planning is done from the value measured after installation, not from the datasheet:

  • Add up the main stream peak bitrates and continuously pulled substreams of the cameras at the remote point.
  • If live viewing is pulled directly from the camera, add an extra stream for each viewer.
  • Plan so this total doesn’t exceed half of the throughput measured in bad weather (design headroom; not a standard value).

Example calculation: 6 cameras at the remote point with a 6 Mbit/s peak bitrate, each with a 0.75 Mbit/s substream: 6 × 6.75 = 40.5 Mbit/s. The target is for measured UDP throughput to be at least 81 Mbit/s. To determine per-camera bitrate, use the camera network bandwidth calculation guide.

Latency and jitter disrupt live viewing and PTZ control more than recording. High jitter makes the image stutter in the VMS client; with long latency, the camera responds late to the PTZ joystick and the operator loses the target. In TDMA-based systems, frame duration directly determines latency; if there are PTZ points that need low latency, choose the frame duration accordingly.

Installation, alignment and encryption

Installation checklist:

  • Mast and mounting: With a narrow-beam antenna, small angular deviations caused by wind lead to signal fluctuation. Use a rigid mount instead of a flexible mast or a long arm fixed at a single point.
  • Alignment: First coarse alignment (map bearing and binoculars), then fine horizontal and vertical adjustment at each end in turn with the device’s alignment tool. Target RSSI should be close to the value calculated in the link budget; a value several dB lower is a sign of side-lobe alignment or an obstruction. A link stuck on a side lobe works on day one and drops in the first storm.
  • Camera side: At the remote point, cameras are fed from a PoE switch connected to the bridge radio; plan the bridge radio and cameras in the same PoE budget.
  • Grounding and surges: Mast and device grounding, shielded outdoor cable and surge protectors at both ends. For details, see the lightning and surge protection guide.
  • Security: Link encryption (WPA2/WPA3 or the manufacturer’s AES-based encryption), changing default management passwords, access to the radio management interface only from the management VLAN. Hiding the SSID isn’t protection; the real safeguard is strong encryption and restricted management access. If the bridge works at layer 2, verify that the camera VLAN is carried tagged.

Fixing interference and drop-outs

After installation, measure capacity in both directions. A UDP test with iperf3 reports jitter and packet loss as well as throughput:

# Server on the central side
iperf3 -s
# From a laptop at the remote point: remote → center direction, 60 seconds, 80 Mbit/s
iperf3 -c 10.30.0.10 -u -b 80M -t 60
# Reverse direction (center → remote)
iperf3 -c 10.30.0.10 -u -b 80M -t 60 -R

When a fault comes in, this is the order we follow on site: first look at the timing of the symptom, then the RSSI/SNR history, and the channel last. The table below gives this mapping:

Symptom Likely cause First check
Frame loss at certain times Another transmitter on the same channel Spectrum scan, channel change
Drop-outs in rain Insufficient fade margin, rain attenuation at 60 GHz RSSI log, link budget
Signal fluctuating in the wind Flexible mast, loose mounting Mount rigidity
Seasonal decline A tree entering the Fresnel zone Recheck line of sight
The whole sector slowing down in PtMP A single client with low MCS Per-client MCS and airtime

Bring the bridge radios’ RSSI, SNR and MCS values into the monitoring system via SNMP; the problem becomes visible before camera video is lost. Without historical data, fault diagnosis is guesswork. To plan the survey and installation of wireless camera points together, see the wireless IP cameras and point-to-point bridges service page.

Frequently asked questions

How many cameras can a wireless bridge carry?

There’s no fixed number. The total peak bitrate and continuous substreams of the cameras at the remote point are calculated; the aim is for this total not to exceed half of the real throughput measured in bad weather. The radio rate on the datasheet isn’t used in capacity planning.

Should PtP or PtMP be chosen for a camera bridge?

PtP for a single remote point with many cameras or a link between buildings. PtMP is economical for scattered points with few cameras; however, capacity is time-shared among clients, and a single client with a weak signal can slow down the whole sector.

Why does the Fresnel zone matter?

A radio signal uses an ellipse-shaped zone between the two antennas. If a significant part of this zone is obstructed, the signal weakens even if the straight line of sight is clear. The common design rule is that at least 60% of the first Fresnel zone radius stays unobstructed.

What are common causes of video stuttering on a wireless bridge?

Other transmitters on the same channel, insufficient fade margin, a mount moving in the wind, trees entering the Fresnel zone and, in PtMP, a single client running at low modulation. Continuously monitoring RSSI, SNR and MCS values speeds up diagnosis.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Video Surveillance

IP cameras, recording and central management infrastructure. We plan blind spots, retention periods and the camera network around the risks of each site.

Knowledge Center

Other articles