Estimate the total user population a 5G small cell can support from its measured or engineered aggregate throughput. The calculation first applies a network-efficiency allowance, then finds simultaneous active-user capacity and adjusts it for busy-hour concurrency. It is a practical traffic-planning check for comparing radio-sector and backhaul limits without confusing registered devices with users transferring data at the same moment.
The main result is the estimated total user population supportable under the chosen concurrency assumption. The active-user figure is the harder instantaneous capacity constraint.
Capacity is shared and traffic is bursty. Coverage quality, channel width, interference, backhaul, scheduler behavior, and client capabilities can lower real throughput.
With 1200 Mbps available, 75% efficiency, 8 Mbps per active user, and 25% concurrency, usable throughput is 900 Mbps. That supports 112 simultaneous users and an estimated 448 total users.
No. It estimates supported users from expected simultaneous demand. Idle associated devices consume little payload capacity but still add protocol overhead.
Real networks lose usable throughput to contention, scheduling, retransmissions, control traffic, and changing radio conditions.
Use a measured busy-hour average or a workload-based estimate. Video, cloud desktops, and large transfers need more throughput than messaging or telemetry.
It is the share of the total user population expected to be actively transferring data during the same busy interval.
No. It is an early planning estimate. Validate the design with coverage modeling, spectrum conditions, device mix, and busy-hour measurements.
| Variable | Meaning | Unit |
|---|---|---|
| Available throughput | Aggregate service capacity before efficiency | Mbps |
| Per-user demand | Average traffic for one active user | Mbps |
| Concurrency | Users active during the same busy interval | % |
| Efficiency | Share converted to usable payload throughput | % |