Oct 9, 2025
Blend propagation models with population density, competitor footprint, travel time, and field constraints to set SLAs you can keep.
Coverage is not service
A polygon on a planning map does not guarantee speed or uptime. Customers judge service, not signal predictions. Optimized service territories start with physics - 3GPP channel models - and end in operations: dispatch windows, depot locations, backhaul, and maintenance routes.
Start with demand: population and where it moves
Model resident and daytime population to understand who needs service and when. In dense cores, small grid cells capture high-contrast demand; in suburbs, commuter flows shift peak load. Ofcom's recent work on presenting coverage with a -95 dBm threshold shows how to tie predictions to user experience (methodology; Mobile Matters 2025).
Map competitors and constraints
Territories should reflect where rivals already deliver and where you can differentiate. Map competitor footprints and known infrastructure. Combine that with fiber/backhaul availability, power, and permitting windows to avoid designs that pass a propagation check but fail in the field.
Calibrate propagation to a service threshold
Pick a field-verifiable KPI (e.g., a reference RSRP/RSRQ or throughput) and set it as your service threshold. Use TR 38.901 models for planning, then validate with drive tests and crowdsourced data. Layer against daytime population density rasters to forecast service coverage. Iterate the map until predictions and measurements converge.
Densify where the model says you are thin
Service gaps are not always fixed by more power - often by more sites. Small-cell playbooks from the Small Cell Forum and 5G Americas outline siting, ML-assisted planning, and cost levers for urban infill.
Mind the rulebook
Permitting and federal shot clocks shape time-to-service. See the FCC's 2018 small cell order and subsequent clarifications such as FCC 20-75. Coordinate legal early to de-risk schedules.
From map to field: an operational playbook
Generate candidate territories by overlaying modeled coverage with drive-time to depots and hubs.
Balance workload with population density and ticket history to set credible SLAs.
Target densification where thresholds are missed; re-simulate and re-check against population and competitors.
Publish a territory ledger: inputs, vintages, parameters, PDFs, and GeoJSON for auditability.
Where to go next
Population Density and 5G Rollout - how density guides spectrum strategy.
