From 1G to 5G: How Connectivity Shapes Urban Development

Cities have always grown where connections are strongest—ports, roads, rail hubs. Today, the most powerful connection is digital. From 1G’s simple voice calls to 5G’s ultra-fast, low-latency networks, connectivity is now a core utility that quietly runs traffic lights, dispatches ambulances, balances electric grids, monitors air quality, and powers small businesses. This guide explains how that evolution happened, what it means for planners, developers, and public leaders, and exactly how to turn connectivity into better housing, safer streets, greener utilities, and a more inclusive urban economy.

Key takeaways

• Connectivity is now urban infrastructure. Treat mobile and fiber networks like water, power, and roads—with master planning, service-level targets, and budgeted upkeep.
• 5G is different by design. It brings high throughput, low latency, and massive device density, enabling real-time city operations and new business models.
• Start with the stack. Fiber backhaul, power, spectrum, edge compute, and open data are prerequisites; plan them together.
• Pilot, measure, scale. Run small deployments, track outcomes with clear KPIs, then expand across districts.
• Mind privacy and resilience. Data governance, security-by-design, and multi-path redundancy protect residents and keep essential services running.
• Inclusive access is essential. Public Wi-Fi, affordable devices, and digital skills programs ensure benefits reach every neighborhood.

The Long Arc of Connectivity: From 1G to 5G

What it is and why it matters

• 1G launched the mobile era with analog voice.
• 2G digitized networks, enabling basic messaging and better spectral efficiency.
• 3G introduced mobile data for the masses.
• 4G made the smartphone economy possible with all-IP broadband.
• 5G adds ultra-low latency, high reliability, and the capacity to connect vast numbers of sensors and machines—crucial for city operations.

For urban development, this evolution shifts connectivity from “nice-to-have” to a backbone for real-time mobility, public safety, utilities, and civic engagement.

Requirements and prerequisites

• Reliable fiber backhaul to cell sites and public facilities.
• Access to low-, mid-, and high-band spectrum to balance coverage and capacity.
• Modern core networks and, ideally, standalone 5G to enable features like network slicing.
• Adequate power and site access (easements on rooftops, street furniture).
• Policy alignment across planning, transportation, utilities, public safety, and IT.

Step-by-step: Building literacy across city hall

1. Run a half-day “G evolution” workshop for agency heads to align on capabilities and limits.
2. Map current assets: fiber routes, conduits, dark fiber, towers, poles, rooftops, ducts.
3. Create a shared glossary (latency, backhaul, slicing, spectrum bands) for cross-department collaboration.
4. Set baseline metrics: current mobile coverage, average speeds, public Wi-Fi uptime, device counts on city networks.
5. Publish a one-page policy brief on how 5G supports the city’s mobility, climate, and economic goals.

Beginner modifications and progressions

• Start small: focus on a single corridor (downtown or an industrial zone).
• Progress: extend to a multi-district deployment with standard designs for poles, power, and fiber.
• Advanced: enable network slicing for specific city services (e.g., an EMS slice with priority QoS).

Recommended metrics

• Median download/upload speeds and 95th percentile latency on key corridors.
• Coverage by spectrum band (low/mid/high) across neighborhoods.
• Sensor uptime and data freshness for critical systems (traffic, air quality).
• Service restoration time after network incidents.

Safety, caveats, common mistakes

• Mistake: assuming consumer 5G equals mission-critical reliability. City services may need redundant links (fiber + cellular).
• Caveat: peak rates are lab targets; design for typical, observed performance.
• Safety: ensure secure mounting, grounding, and clearances for radios on street furniture; follow local standards.

Mini-plan

• Step 1: Commission a citywide asset and coverage map.
• Step 2: Select one “innovation zone” to pilot multi-band 5G with fiber upgrades.
• Step 3: Publish KPIs and a 90-day learning report to guide scaling.

The Urban Connectivity Stack (and How to Get It Right)

What it is and core benefits

Think of a city’s digital nervous system as a stack:

1. Passive infrastructure: ducts, poles, rooftops, street furniture, and power.
2. Backhaul and fronthaul: fiber that ties everything together.
3. Radio access network (RAN): macro sites for broad coverage, small cells for dense areas.
4. Spectrum strategy: low-band for reach, mid-band for balanced capacity, high-band (mmWave) for hotspots.
5. Core network and edge compute: where traffic is routed, secured, and processed—ideally with local edge nodes for real-time needs.
6. Devices and sensors: from traffic cameras to environmental monitors and handhelds for field crews.
7. Platforms: data integration, security, observability, and APIs.
8. Governance: contracts, privacy policies, and performance oversight.

Requirements and prerequisites

• Citywide GIS with layers for ducts, poles, fiber strands, buildings, and rights-of-way.
• Standard pole designs and template agreements for attachments.
• Make-ready processes coordinated across utilities and transport agencies.
• Open data and API policies balancing transparency with privacy.

Step-by-step implementation

1. Create a single asset registry with authoritative layers (ducts, poles, fiber, streetlights).
2. Standardize smart pole specs (height, load, power, cabinet volume, cooling, and aesthetics).
3. Adopt “dig once” ordinances—every road project includes conduit and pull boxes.
4. Negotiate master license agreements (MLAs) with operators for predictable, rapid small-cell permitting.
5. Stand up a neutral host pilot in a busy district to reduce clutter and share infrastructure.
6. Deploy an edge node in a municipal data center or colocation facility to host latency-sensitive apps.
7. Integrate security from day one: zero trust, device identity, encrypted data in motion and at rest, and SIEM/SOAR monitoring.

Beginner modifications and progressions

• Beginner: upgrade a subset of streetlights to smart poles with power, fiber, and modular mounts.
• Next: deploy a neutral host system that multiple mobile operators can use.
• Advanced: implement 5G standalone features and edge apps for transit priority and public safety.

Recommended metrics

• Permit cycle time for small cells and fiber works.
• Percentage of road projects including new conduit (“dig once” adherence).
• Edge workload latency (p95) and packet loss.
• Co-location rate: average number of radios per pole.

Safety and pitfalls

• Pitfall: ignoring thermal and power budgets in small-cell cabinets.
• Safety: avoid visual clutter by using integrated designs; ensure pedestrian clearances and ADA compliance.

Mini-plan

• Step 1: Approve a standard smart pole and cabinet spec.
• Step 2: Convert 50 lights in a downtown grid to the standard within 120 days.
• Step 3: Open an RFP for neutral host partners using the new design.

Connected Mobility: Signals, Streets, and the Last Meter

What it is and core benefits

Connected mobility uses cellular links and edge compute to coordinate traffic lights, prioritize buses and emergency vehicles, manage curb space, guide parking, and support micromobility. The goal is safer streets, faster trips, and lower emissions.

Requirements and prerequisites

• Signal controllers capable of network connectivity and remote configuration.
• Backhaul from signals to traffic management centers; redundant links (fiber plus cellular).
• Roadside units (RSUs) for V2X pilots where relevant.
• Data feeds integrated with a real-time platform (traffic, weather, incidents).

Step-by-step implementation

1. Audit signal infrastructure: age, firmware, cabinet power, communications.
2. Connect top 50 intersections via fiber or microwave with 5G backup.
3. Deploy transit signal priority on two bus corridors using cloud-hosted logic and 5G for command messages.
4. Launch a curb management pilot on one commercial street—digital permits, cameras/sensors, and enforcement alerts.
5. Add micromobility hubs with shared docks and geofenced slow zones enforced by networked beacons.

Beginner modifications and progressions

• Starter: simple emergency vehicle pre-emption at 10 intersections.
• Next: adaptive signal control in a district.
• Advanced: V2X day-one applications (hazard warnings, speed harmonization) using network slicing for prioritized messages.

Recommended frequency/duration/metrics

• Monthly safety review: severe crashes, near misses, and response times.
• Weekly transit metrics: on-time performance on pilot corridors.
• Daily intersection KPIs: average delay, throughput, pedestrian wait times.

Safety, caveats, and common mistakes

• Mistake: not coordinating with emergency services on pre-emption logic.
• Caveat: camera analytics can introduce bias; test and validate in diverse conditions.
• Safety: protect roadside equipment from vehicle strikes and tampering.

Mini-plan

• Step 1: Enable bus priority on a 5 km corridor.
• Step 2: Add emergency pre-emption at six critical intersections.
• Step 3: Publish a 60-day evaluation, then extend to the next corridor.

Utilities and Environment: Smarter Energy, Water, and Air

What it is and core benefits

Urban utilities rely on pervasive, low-power connectivity to read meters, detect leaks, control distributed energy resources, and monitor air and noise pollution. 5G’s capacity and density enable high-resolution, real-time operations that cut losses and improve reliability.

Requirements and prerequisites

• Device strategy: mix of cellular IoT (including reduced-capability 5G devices), LoRa/mesh where appropriate, and wired sensors for critical nodes.
• Integration with SCADA and modern data platforms.
• Power and enclosures designed for weather and tamper resistance.

Step-by-step implementation

1. Segment use cases: metering, leak detection, transformer monitoring, air quality.
2. Select the right connectivity per use case: battery-friendly options for meters; higher-bandwidth links for cameras and grid telemetry.
3. Pilot in one pressure zone or feeder with 200–500 devices.
4. Integrate with outage management and maintenance ticketing.
5. Automate alerts to field crews with mobile apps on a prioritized network slice.

Beginner modifications and progressions

• Beginner: deploy smart water meters on a single district.
• Next: add leak detection acoustics and correlate with pressure data.
• Advanced: manage distributed solar and EV chargers with real-time load balancing at the edge.

Recommended metrics

• Non-revenue water reduction; average leak detection time.
• Outage minutes per customer; mean time to repair.
• Air-quality sensor uptime and data latency.

Safety and pitfalls

• Pitfall: mixing unmanaged consumer IoT on utility networks. Use device identity, mutual authentication, and segmentation.
• Safety: follow electrical codes for transformer cabinet sensors; verify RF exposure compliance for rooftop gear.

Mini-plan

• Step 1: Install 1,000 smart water meters and 100 leak sensors in a priority zone.
• Step 2: Connect sensors to a secure, segmented network and integrate alerts with field operations.
• Step 3: Report quarterly savings and reinvest in expansion.

Public Safety and Resilience: Prioritizing What Matters

What it is and core benefits

First responders benefit from prioritized broadband, real-time video, and push-to-talk over cellular. With 5G, agencies can dedicate slices for emergencies, support drones for situational awareness, and maintain service during disasters with satellite backup.

Requirements and prerequisites

• Hardened sites with backup power, and mobile cells for surge coverage.
• Priority and pre-emption capabilities for public safety traffic.
• Integration with CAD systems and encryption policies.

Step-by-step implementation

1. Adopt a priority service for police, fire, and EMS devices.
2. Equip incident command vehicles with 5G routers and satellite fallback.
3. Deploy drone-as-first-responder pilots with secure video backhaul.
4. Run quarterly exercises that cut fiber links and simulate spectrum congestion.
5. Record after-action insights and adjust policies and network configurations.

Beginner modifications and progressions

• Starter: priority SIMs for 100 responders; test in a stadium event.
• Next: add network slicing for major incidents.
• Advanced: integrate edge analytics for automated detection of crowding, smoke, or floods.

Recommended metrics

• Dispatch connect success rate and video start time during incidents.
• Redundancy test pass rate in quarterly drills.
• Coverage heatmaps over patrol routes.

Safety and pitfalls

• Pitfall: unsecured contractor devices on public-safety slices.
• Safety: continuous credential rotation; enforce endpoint protection on all field devices.

Mini-plan

• Step 1: Issue priority SIMs to 100 responders and test at two large events.
• Step 2: Add a portable cell-on-wheels for disaster exercises.
• Step 3: Publish incident network KPIs to command staff monthly.

Private 5G for City Assets: Campuses, Ports, Airports, and Industrial Parks

What it is and core benefits

Private cellular gives a city or operator tight control over coverage, performance, and security within a defined campus—perfect for ports, airports, logistics centers, and large public venues. It reduces interference, enables deterministic performance, and supports automation.

Requirements and prerequisites

• Dedicated or shared spectrum, depending on the jurisdiction.
• Indoor and outdoor RAN tailored to the site.
• Local edge compute for real-time control.
• Device certification and SIM/eSIM lifecycle management.

Step-by-step implementation

1. Select one campus with clear ROI (e.g., reducing turnaround time in a port terminal).
2. Perform a radio survey and design indoor/outdoor coverage.
3. Deploy a small private core and integrate with local applications (AGVs, cranes, cameras).
4. Onboard devices with strong identity and role-based access.
5. Measure business KPIs (e.g., container moves per hour, dwell time).

Beginner modifications and progressions

• Beginner: cover one warehouse or terminal yard.
• Next: expand to adjacent yards and link to city fiber.
• Advanced: interwork with public networks and enable network slicing for roaming city workers.

Recommended metrics

• Uptime and latency within the campus, p95 and p99.
• Device onboarding time; policy compliance rates.
• Operational KPIs: throughput, cycle time, error rates.

Safety and pitfalls

• Pitfall: insufficient RF planning leading to dead zones inside steel structures.
• Safety: coordinate RF exposure, grounding, and lightning protection.

Mini-plan

• Step 1: Conduct a four-week design sprint for one building.
• Step 2: Install indoor radios and a micro-edge node; onboard 200 devices.
• Step 3: Evaluate against two operational KPIs and plan phase 2.

Spectrum and Policy: Making the Airwaves Work for Your City

What it is and core benefits

Spectrum strategy blends low-band (broad coverage), mid-band (capacity/coverage balance), and high-band/mmWave (extreme capacity in hotspots). Policy choices—permitting, fees, right-of-way access—can accelerate or delay deployments by years.

Requirements and prerequisites

• Coordination between planning, public works, and transportation.
• Standard fees and timelines in line with national rules.
• Transparent inventory of attachable assets and available conduits.

Step-by-step implementation

1. Publish a small cell ordinance: timelines, fees, aesthetic standards, and design templates.
2. Offer an asset catalog (poles, rooftops, ducts) with a self-service workflow.
3. Establish a “dig once” rule for every road opening and utility trench.
4. Plan for mmWave zones in stadiums, transit hubs, and dense commercial districts.
5. Run quarterly industry roundtables with operators and neutral hosts.

Beginner modifications and progressions

• Beginner: align fees and timelines to national guidelines.
• Next: pilot a city-run neutral host on one street.
• Advanced: enable shared spectrum or localized licenses for private 5G in industrial zones, as regulation allows.

Recommended metrics

• Average permit time; percentage approved on first pass.
• Assets leased and co-location rate per pole.
• Deployment pace: sites/month per district.

Safety and pitfalls

• Pitfall: unpredictable fees and subjective aesthetics causing disputes.
• Safety: publish clear standards, offer pre-approved designs, and enforce objectively.

Mini-plan

• Step 1: Update ordinances to include standardized designs and fees.
• Step 2: Launch an online asset marketplace with GIS integration.
• Step 3: Track and publish permit KPIs quarterly.

Data Governance and Security: Trust by Design

What it is and core benefits

Connectivity generates sensitive data—locations, video, utility usage. Sustainable urban development requires privacy-by-design, zero-trust networks, and clear accountability for data use.

Requirements and prerequisites

• Data inventory across agencies and vendors.
• Privacy impact assessments for new projects.
• Security architecture: device identity, segmentation, encryption, and monitoring.

Step-by-step implementation

1. Publish a city data charter: what you collect, why, who can access it, how long you keep it.
2. Adopt zero-trust controls: authenticate every device and connection.
3. Implement observability: logs, metrics, traces in a unified platform.
4. Run third-party audits before scaling pilots citywide.
5. Create a resident portal to view and manage consent where applicable.

Beginner modifications and progressions

• Beginner: start with a single data domain (traffic video).
• Next: extend the charter to utilities and public Wi-Fi.
• Advanced: consent and data minimization baked into APIs and procurement.

Recommended metrics

• Mean time to detect/respond to incidents.
• Audit pass rate for projects.
• Data minimization score (fields collected vs. required).

Safety and pitfalls

• Pitfall: feature creep—collecting more than needed.
• Safety: default to minimal viable data; purge schedules enforced via automation.

Mini-plan

• Step 1: Approve a city data charter with public consultation.
• Step 2: Enforce device identity and encrypted transport citywide.
• Step 3: Publish quarterly privacy and security metrics.

Financing and Procurement: Getting Deals, Not Just Gear

What it is and core benefits

Connectivity projects can be financed through public-private partnerships, availability payments, leasing, or shared-revenue arrangements (e.g., for neutral host poles or advertising kiosks). Smart contracts align risk and performance.

Requirements and prerequisites

• Outcome-based RFPs with measurable KPIs.
• Lifecycle costing that includes operations, not just capex.
• Legal templates for site access and revenue sharing.

Step-by-step implementation

1. Define outcomes (e.g., 95% median speed of X on key corridors, 99.95% uptime for public Wi-Fi).
2. Issue an RFI to test market appetite and delivery models.
3. Run a competitive procurement with staged milestones.
4. Tie payments to performance: speed, latency, uptime, and customer satisfaction.
5. Create a “connectivity reserve” in the budget for refresh and maintenance.

Beginner modifications and progressions

• Beginner: one corridor neutral host pilot with shared revenue.
• Next: citywide small cell access framework with standardized fees.
• Advanced: outcome-based contracts across mobility, safety, and utilities.

Recommended metrics

• Cost per covered block; cost per Mbps delivered.
• Uptime compliance rates and SLA credits applied.
• Resident satisfaction scores for public Wi-Fi and digital services.

Safety and pitfalls

• Pitfall: vendor lock-in via proprietary platforms.
• Safety: insist on open APIs, data portability, and exit clauses.

Mini-plan

• Step 1: Publish a model RFP with outcomes and sample SLAs.
• Step 2: Pilot a revenue-sharing neutral host in downtown.
• Step 3: Evaluate costs and scale with multi-year contracts.

Quick-Start Checklist

• Citywide map of ducts, poles, rooftops, fiber, and power access.
• Standard smart pole and cabinet designs approved.
• Small cell ordinance with clear timelines, fees, and aesthetics.
• One “innovation zone” chosen with fiber upgrades and multi-band 5G.
• Edge node location selected and ready.
• Priority connectivity for first responders in place.
• Data charter approved; zero-trust controls piloted.
• Baseline KPIs defined and public dashboard planned.
• Procurement pack ready: outcomes, SLAs, templates.

Troubleshooting and Common Pitfalls

Problem: Permitting bottlenecks and unpredictable timelines.
Fix: Pre-approved designs, firm SLA timelines, online submissions, one-stop shop across agencies.

Problem: Visual clutter from multiple pole types and cabinets.
Fix: Neutral host poles with co-location; integrated designs; aesthetic guidelines.

Problem: Coverage gaps in older neighborhoods.
Fix: Use low-band spectrum for broad reach; add small cells where demand grows; include affordability and device programs.

Problem: Unreliable performance during events.
Fix: mmWave hotspots, temporary cells, and dedicated slices for event operations.

Problem: Data silos and duplicated sensors.
Fix: Central data platform with device registry; shared procurement and API standards.

Problem: Security incidents via unmanaged IoT.
Fix: Device identity/eSIM, network segmentation, certificate rotation, continuous monitoring.

Problem: Budget overruns.
Fix: Lifecycle costing, outcome-based payments, phased rollouts tied to KPIs.

How to Measure Progress and Results

Network KPIs

• Median and p95 download/upload speeds on key corridors.
• Latency to local edge; packet loss rates.
• Coverage by band and co-location rates.

City Service KPIs

• Transit on-time performance, average dwell, and signal priority effectiveness.
• Crash rates and emergency response time.
• Non-revenue water, outage minutes per customer, and leak detection time.
• Public Wi-Fi usage, session length, and satisfaction.

Equity and Inclusion KPIs

• Adoption of affordable plans/devices by neighborhood.
• Public Wi-Fi coverage in community anchors (libraries, parks).
• Digital skills program completion and job placement.

Governance KPIs

• Permit SLA compliance, appeals, and processing time.
• Security incident mean time to detect/respond.
• Open data freshness and API uptime.

A Simple 4-Week Starter Plan

Week 1: Discovery and alignment

• Conduct a cross-agency workshop to define goals for mobility, safety, utilities, and inclusion.
• Approve KPIs and select one innovation zone.
• Launch the asset inventory: ducts, poles, fiber, rooftops, cabinets, and power.

Week 2: Design and policy

• Finalize standard smart pole designs; publish aesthetic guidelines and small cell timelines/fees.
• Draft the data charter and zero-trust baseline.
• Confirm edge node location and power requirements.

Week 3: Procurement and partners

• Issue a market RFI for neutral host/small cell deployment and edge services.
• Invite operators and integrators to a site walk in the innovation zone.
• Prepare model SLAs tied to the KPIs.

Week 4: Pilot kickoff

• Approve permits for 25–50 smart poles in the zone; schedule fiber upgrades.
• Configure public safety priority service and test.
• Publish a project dashboard and community update; announce the 90-day pilot window.

Frequently Asked Questions

1) What’s the practical difference between low-, mid-, and high-band 5G for a city?
Low-band covers large areas and penetrates buildings but delivers modest speeds. Mid-band balances speed and reach, ideal for most urban streets. High-band (mmWave) brings extreme capacity in dense hotspots like stations and stadiums but needs many small cells.

2) Do we really need fiber if we’re investing in 5G?
Yes. Fiber is the backbone that connects radios to the core and edge; without it, you’ll bottleneck performance and reliability. Plan fiber with every road project.

3) How does 5G help buses and emergency vehicles?
It supports reliable, low-latency messaging so signals can grant bus priority or emergency pre-emption, improving travel times and safety.

4) Are there privacy risks with connected cameras and sensors?
There can be. Use privacy impact assessments, minimize data collection, encrypt, limit access, and publish a data charter. Build public trust through transparency and oversight.

5) Can small cities afford this?
Yes, by focusing on corridors and campuses first, using neutral hosts, shared revenue models, and outcome-based contracts. Start with pilots tied to clear KPIs.

6) What’s “network slicing,” and does a city need it now?
It’s a way to create virtual networks with different performance guarantees on the same physical infrastructure. Cities don’t need it for every project, but it’s valuable for priority services like public safety or traffic control.

7) Should we deploy mmWave citywide?
No. Use it surgically where crowds or data demands are highest—stadiums, transit hubs, dense commercial streets—while relying on mid/low bands elsewhere.

8) How do we avoid vendor lock-in?
Specify open standards and APIs, require data portability, and include exit clauses. Favor modular designs and neutral host models.

9) What skills do city staff need?
GIS and asset management, fiber and radio basics, data governance, cybersecurity, and contract management. Upskill through short courses and vendor-agnostic training.

10) What about legacy 2G/3G equipment?
Plan for sunsets and migrations. Inventory devices, budget replacements, and schedule upgrades in phases to avoid service gaps.

11) How fast can we see results?
Pilots on a single corridor or campus can show measurable improvements in 90 days—faster bus runs, fewer outages, better Wi-Fi satisfaction—if you set clear KPIs and publish them.

12) How do we bring communities on board?
Hold open houses, share coverage and aesthetic designs, co-design uses (e.g., safety lighting or public Wi-Fi), and publish privacy rules. Community trust accelerates deployments.

Conclusion

Connectivity has moved from convenience to cornerstone. From 1G’s first mobile calls to 5G’s real-time city operations, networks now shape how people move, work, and live together. Cities that plan the connectivity stack, pilot with purpose, measure relentlessly, and protect privacy will build safer streets, greener utilities, stronger small businesses, and more inclusive opportunities.

Call to action: Choose one corridor, one campus, or one neighborhood—and start building your city’s next connection today.

References

• Minimum technical performance requirements for IMT-2020 (Report M.2410), International Telecommunication Union, 2017. https://www.itu.int/dms_pub/itu-r/opb/rep/R-REP-M.2410-2017-PDF-E.pdf
• IMT-2020 FAQ (International Mobile Telecommunications), International Telecommunication Union, 2024. https://www.itu.int/en/itu-r/documents/itu-r-faq-imt.pdf
• IMT-2020 Requirements Overview, International Telecommunication Union, 2018. https://www.itu.int/en/ITU-R/study-groups/rsg5/rwp5d/imt-2020/Documents/S01-1_Requirements%20for%20IMT-2020_Rev.pdf
• 5G System Overview, 3GPP, August 8, 2022. https://www.3gpp.org/technologies/5g-system-overview
• 5G Network Slice Management, 3GPP, July 10, 2023. https://www.3gpp.org/technologies/slice-management
• America’s 5G Future, Federal Communications Commission, n.d. https://www.fcc.gov/5G
• 5G Spectrum Guide, GSMA, n.d. https://www.gsma.com/connectivity-for-good/spectrum/5g-spectrum-guide-2/
• 5G mmWave: Unlocking the Full Potential of 5G, GSMA, August 9, 2023. https://www.gsma.com/get-involved/gsma-foundry/5g-mmwave-unlocking-the-full-potential-of-5g/
• Spectrum Awards and mmWave Update, Ofcom, updated June 20, 2025. https://www.ofcom.org.uk/spectrum/spectrum-awards
• Award of the 700 MHz and 3.6–3.8 GHz Spectrum Bands, Ofcom, last updated November 8, 2024. https://www.ofcom.org.uk/spectrum/spectrum-awards/award-700mhz-3.6-3.8ghz-spectrum
• Explore the Ericsson Mobility Report: June 2025, Ericsson, June 2025. https://www.ericsson.com/en/reports-and-papers/mobility-report/reports/june-2025
• Mobile Subscriptions Outlook, Ericsson, n.d. https://www.ericsson.com/en/reports-and-papers/mobility-report/dataforecasts/mobile-subscriptions-outlook
• World Urbanization Prospects: 2018 Revision (Highlights), United Nations, 2018. https://population.un.org/wup/assets/WUP2018-Highlights.pdf
• World Urbanization Prospects: 2018 Revision (Report), United Nations, 2018. https://population.un.org/wup/assets/WUP2018-Report.pdf
• Urban Development Overview, World Bank, n.d. https://www.worldbank.org/en/topic/urbandevelopment/overview
• Urban Population (% of total), World Bank Data, n.d. https://data.worldbank.org/indicator/SP.URB.TOTL.IN.ZS
• Urbanization (topic page), Our World in Data, 2024. https://ourworldindata.org/urbanization
• The WIRED Guide to 5G, WIRED, December 31, 2022. https://www.wired.com/story/wired-guide-5g
• Timeline from 1G to 5G: A Brief History on Cell Phones, CENGN, September 21, 2020. https://www.cengn.ca/information-centre/innovation/timeline-from-1g-to-5g-a-brief-history-on-cell-phones/
• 5G Standalone (5G SA): Experience 5G Without Limits, Ericsson, n.d. https://www.ericsson.com/en/5g/5g-sa