Estimate the busy-hour traffic capacity a 5G small cell must carry from concurrent user count and average per-user demand. Network overhead and operational headroom remain separate, making the result suitable for comparing a traffic forecast with sector capacity or backhaul. The answer is expressed in Mbps of throughput—not radio channel width—because MHz depends on the deployment's spectral efficiency and radio configuration.
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.
180 concurrent users at 5 Mbps create 900 Mbps of payload demand. Adding 12% overhead gives 1008 Mbps; adding 25% headroom produces 1260 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 | % |