Call Us: 602-426-0542

Chapter 1: ISP’s experience building large Wi-Fi networks

Several people have asked me how to build lower cost municipal Wi-Fi systems that cover anything from a very small area to hundreds of miles. To be honest, we haven’t yet deployed a muni Wi-Fi network that covers hundreds of miles, but in the course of my work as a wireless ISP over the past few years, I have learned many lessons from our small and medium-scale deployments that may be useful to people who are thinking of rolling out large scale muni Wi-fi projects.

 

As a wireless Internet Service Provider (WISP), our smallest system is 15 clients and the largest system is about 270. I have designed and managed systems that handled up to 3000 users per day and supported about 30,000 users per year through pay per use servers. My designs are based on systems installed and deployed over the last several years that typically didn’t follow the standard cookie-cutter models. Since then I have engineered mesh systems for public safety and municipal utilities for video surveillance/analytics over 100 square miles, Major League spring training baseball facilities, traffic systems, airports, city facilities, point-to-multipoint (PTMP) WISP systems, and point-to-point (PTP) links up to 1Gbps. The proposal I set out below for a city-wide system is based on my experience and the lessons I learned with these systems and concepts.

Basics of a municipal Wi-Fi network

A municipal wireless network is basically a bunch of hot spots connected through some type of wired or wireless backhaul system using a cluster of Access Points (APs). The network eventually funnels all traffic back to a central location which may utilize an authentication system to allow various users on the system. It’s pretty simple stuff with the devil in the details. However, the details are the difference between whether this network becomes financially and technically feasible or not. I am not going to cover that in one article. However, I will show how we developed and deployed different techniques over the last few years to create the foundation for a low cost, scalable muni Wi-Fi network.

Before designing a system, determine the following basic issues:

  • Rules for deliverable product;
  • Potential upgrade path for future growth;
  • Calculate costs/income if applicable.

Simplest case: wireless Internet in a building

Let’s take the first case which is the simple idea of providing Internet in a building. I’m going to spend a little time on it because it is a microcosm of a very large system. Consider it a miniature muni Wi-Fi network in terms of number of users and the foundation for one of our industries. It’s also where we came up with the concept of eliminating fiber by using VDSL converters and using WDS for backhaul for AP to AP hopping. Later, we decided that Wireless Distribution System (WDS) was also preferable to mesh for our outdoor designs due to cost issues, the fact that mesh radios typically only connected to the radios before and after them meaning no change in the mesh structure, and that some of the mesh manufacturers weren’t using load balancing to determine mesh paths, only signal level and modulation.

Inside a building or in a heavily populated area, there are two problems: density and connectivity. The inside of a building is basically a controlled environment. Outside in a populated area, you also have interference, but I will deal with that in a later article. I will also introduce a central server managed design based on these same concepts that will also greatly reduce the cost of in-building Wi-Fi systems.

Lessons learned from a hotel Wi-Fi deployment

The first building we did – the Stratosphere Hotel in Las Vegas – was a pay system. Keep in mind that this was before WDS or mesh was used as a standard for deployments. At the time, we realized that we needed at least 50 access points to cover 2500 rooms on 24 floors with the ability to support about 200 users simultaneously. Due to building codes, all Ethernet cables for each radio would have to be in conduit. In addition, the cable runs from each AP would be well over 300 feet. One hallway alone was 270 feet long. Conduit and cabling costs would run several hundred thousand dollars. The only existing asset we had was a few pairs of telephone wires in a vertical riser conduit that we could use. The vertical riser conduit was already full and there was no way additional cable could go in there.

The vertical asset problem was the easiest. We used Ethernet VDSL converters to push bandwidth from the data room several hundred feet away to a single Access Point to every other floor. These units support 10-15Mbps half-duplex for distances up to a mile across a twisted pair of wires with current versions supporting up to 100Mbps. VDSL also eliminated fiber which would have raised the cost significantly because of the fiber switches. That’s more than enough bandwidth for an 802.11b access point. Basically we traded $250,000-$500,000 worth of conduit work and fiber equipment for about $4000 worth of VDSL converters, a VDSL switch, and WDS, which I will discuss later. We eventually did the World Market Center in Las Vegas about a mile away with many of the same ideas.

Now that we had bandwidth on every other floor to one AP, the second problem was that the hallways were sequential, meaning end-to-end. The hotel is in the shape of an S when seen by planes that fly over. That’s when we came up with the idea of using WDS hops from AP to AP while using the same radios in AP mode simultaneously. Since there were 2 radios in each AP, the WDS path went in one radio and out the other, thus minimizing the 1/n problem. There were 5 radios on every other floor. On each radio, we used custom directional antennas to aim down the hallways for greater range and better room penetration. At the time, the Vivato APs were the only units we could find that could support AP and WDS mode on the same radio simultaneously and were reasonably inexpensive at $350 per radio.

Total cost of equipment for the entire installation was less than $40,000 with labor at about $10,000. It cost $3000-$4000 per month for bandwidth and tech support. We generated over a million dollars worth of revenue over the next 4 years from that system. The reason I use this example is because the techniques we learned became the foundation for almost every future system.

There was a book written called “All I really need to know I learned in Kindergarten” written by Robert Fulghum. We found that the Stratosphere was our Kindergarten. The VDSL units we used later saved another client $100,000 in their initial installation. The roaming spammers gave us the opportunity to test various methods of blocking them and handling high volumes of traffic. Hackers scanning through the system forced us to micromanage connectivity and to be proactive instead of reactive. The system was later upgraded to go from 200 simultaneous users to over 1000 over the next few years by simply adding more radios and VDSL entry points.

The main problem with large scale Wi-Fi systems

This is also where we learned the hard lesson as to what we believe caused many of the problems of future industry municipal systems. Our APs were 200mw. Our antennas were directional and approximately 12dBi. Laptops are 30-100mw.

Because we couldn’t get approval to bring in more access points, there were some areas where clients could see the wireless signal, but couldn’t connect. They weren’t happy. Before I get hammered on why we didn’t have closer access points, the first radios that went in were at the end of the halls for coverage and backhaul. We were going to add additional radios later to cover poor signal areas but a change in management at the Stratosphere held up the second phase of the installation. Therefore, we had to live with hitting laptops at distances up to 135 feet through several rooms for quite a while.

Nobody designs a point-to-point (PTP) system with 2 radios of dissimilar power levels, but that is how many municipal Wi-Fi networks are implemented. Outdoor WiFi AP’s are typically 100mw to 1W. The end result is users thinking that if they see bars on their computer, they should be able to connect. This differential causes huge problems for municipal wireless deployments with APs several hundred feet away trying to pick up laptop signals through brick walls, trees, and other obstacles. The solution is to ask users to purchase high-power indoor units (repeaters) to amplify the signal and reduce the differential. However, that dampened enthusiasm and created additional interference issues. Another option would be a truck roll of an outdoor radio installed by a technician but that idea was never adopted by any of the bigger companies.

Adapting this idea to a municipal wireless model means that early 2.4GHz single radio systems should have been designed with the highest gain aesthetically pleasing antenna connected to APs set to about 100mw. That design would have been more productive, lower cost, and would have reduced the number of connection problems for clients. Ideally, the simplest, least expensive, and best AP would be about 20dBm with a 16dBi omni-antenna. This will deliver the longest range and best penetration bi-directionally with low power clients. Keep in mind I’m not addressing radio specifications, density, interference, or any of the higher tech ideas currently being deployed, just a basic single AP setup. Since we are after a cost effective system, that’s where our focus will be.

Muni wireless systems, like any other wireless network are made up of 3 parts:

  • access points;
  • transport;
  • ingress/egress.

I am going to analyze each one of these for the cost/performance benefits of each phase over the next few articles and mix in some of our other installations to demonstrate real-world applications of these components in action. The goal is to show that it is cost-effective for almost every city to have some type of system in place. Not every city needs a muni wireless network that can do everything and with budgets where they are, it may not be realistic. However, defining the needs and expectations rigorously will help the project stay within the financial scope of most cities.

The overwhelming response to Google’s fiber project shows that hundreds of cities are interested in upgrading their infrastructure. Yes, fiber everywhere would be the ultimate option, but as an intermediate and realistic step (and considering Verizon is backing away from FIOS), not only can the muni wireless system I have outlined above fill that need, it can be built starting at about $3000 per square mile. It can also be deployed as a point-to-multipoint system for less than $300 per AP location and $150 per household for more remote areas while integrating with the muni wireless network later. The ultimate design is an integrated muni wireless/PTMP structure.

What’s really funny is that cell phone companies that clearly can’t get enough bandwidth on a tower to support all the new smart phone applications, haven’t jumped on this concept nationwide to offload some of the bandwidth needs. In some cities, the cable companies are already doing that. In others, the cell phone companies are supporting hot-spot integration. They can do 25 square miles with Gigabytes of capacity for less than it costs to put up 1 tower. That’s a discussion for a future article.

 

Last modified on Monday, 14 March 2016 12:07

Leave a comment

Make sure you enter the (*) required information where indicated. HTML code is not allowed.

We are proud to support the efforts of One Laptop Per Child (OLPC)