Estimate the traffic throughput required for a private 5G deployment during its busiest operating interval. Combine concurrent devices with average per-device demand, then apply separate allowances for network overhead and capacity headroom. The result helps industrial, campus, or warehouse planners compare application demand with radio-sector and backhaul capacity without presenting Mbps as if it were licensed spectrum bandwidth in MHz.
The main result is the traffic throughput to provision in the modeled direction. It separates payload demand from the explicit allowances so the design assumption is auditable.
This output is Mbps of traffic capacity, not MHz of licensed spectrum. Radio bandwidth depends on spectral efficiency, MIMO, duplexing, scheduler behavior, and signal quality.
400 concurrent users at 2.5 Mbps create 1000 Mbps of payload demand. Adding 15% overhead gives 1150 Mbps; adding 30% headroom produces 1495 Mbps.
No. The result is required traffic throughput in Mbps. Converting it to MHz requires an expected spectral efficiency and deployment-specific radio assumptions.
Overhead accounts for non-payload traffic, while headroom reserves capacity for bursts, growth, and imperfect traffic estimates.
Use a defensible busy-hour average for capacity planning. Model exceptional high-rate workloads separately rather than applying peak rate to everyone.
It represents whichever traffic direction the per-user input describes. Calculate uplink and downlink separately when their demand or available capacity differs.
It provides a traffic target, but the final backhaul design should also account for redundancy, service classes, aggregation, and upstream bottlenecks.
| Variable | Meaning | Unit |
|---|---|---|
| Concurrent users | Endpoints actively transferring at once | count |
| Per-user demand | Average busy-hour payload rate | Mbps |
| Overhead | Control and non-payload traffic allowance | % |
| Headroom | Reserve for bursts and uncertainty | % |