Recap-How to Design High Capacity Wi-Fi Networks

Andrew von Nagy, Wi-Fi Expert and Owner of Revolution Wi-Fi was the guest speaker at our very successful webinar on “Designing High Capacity Wi-Fi Network’s”. The webinar also featured a Demo of iBwave Wi-Fi’s Capacity Planning capabilities by Sr. Manager Technical Product Management Marc-Antoine Lamontagne. During the webinar we received a large number of questions from attendees, some of which Andrew and Marc-Antoine were was able to answer live. However, we did not have time to answer all of them. This week Marc Antoine and Vladan Jevremovic, Research Director, iBwave took some time to address some key questions asked during the webinar. Read on and let’s keep the discussion going.

1- Can you please explain the impact of deploying access points with dual 5GHz radios on the design of high capacity Wi-Fi Networks?

The first advantage of using dual 5GHz radio is to offer twice the capacity from the same access points. Since you have 2 radios running on different channels you end up with air interface available to support more users and higher throughput. This type of architecture is made possible because of the high number of non-overlapping channels available on the 5GHz band. The second advantage is to reduce the cost of the deployment for high-density environment. Since you have 2 radios in the same access point, you end up with more capacity and keep the number of access points to a minimum. You can also save on installation cost by reducing the number of cables to pull in the ceiling in order to connect all the access points. From a Design perspective, having more than one radio in the same AP will augment the number of channels being used in that location and will reduce the channels that you can use for the other APs. This will increase slightly the risk of co-channel interference (CCI) in your design and decrease the capacity available for each AP since they are sharing the same air interface. Therefore, it will be important, as you validate your network, to look at the CCI (number of access points using the same channel with overlapping coverage). This is done in iBwave Wi-Fi using the CCI map. Also, since you are increasing the density of the channel being used, it will increase the zone of transitions between APs. It will be important to look at the location of these zones to make sure they are not located in areas of high usage. This can be done in iBwave Design using the Best Channel output map.

APs with dual (or more) 5GHz radios are not yet supported out of the box with iBwave Wi-Fi. Anyhow, a simple workaround can be used by creating 2 APs with each one using a different channel. We then have a method in iBwave Design to keep the bill of material accurate. We are currently in discussion with some manufacturers to see how we could better model this type of equipment more seamlessly.

2- How 3G & LTE offloading can be implemented using Wi-Fi and how capacity has to be planned accordingly?

HetNet Capacity modeling combining 3G, 4G and Wi-Fi applications is supported with iBwave Design Enterprise. The application allows precise definition of the market share between cellular operators, technology split between 3G and 4G and finally the % of expected traffic between cellular and Wi-Fi. Based on this information, the application automatically allocates the traffic on the right network and calculates the expected load for each one. In iBwave Design, it is also possible to configure LTE services for voice over LTE and voice over Wi-Fi.

When VoLTE is selected, the traffic is automatically assigned to the 3G service for the same operator. If VoWiFi is selected, the traffic is assigned to the Wi-Fi network. This creates a complete HetNet model to validate the overall quality of experience for the users considering the offload to different network technologies. At the end, the application allows you to validate your KPIs of capacity for each network service and the expected throughput available in average for the users.

3- What main inputs are you considering for Capacity Analysis? And how it relates to the Equipment Capacity?

Equipment capacity is the maximum number of radios associated to an AP. This is specified by the manufacturer, and if the maximum number is reached, AP will decline further association requests. The manufacturer specifies this number based on their own hardware limitations. In our capacity algorithm, we calculate “airtime capacity”, as we look into files that need to be transmitted between AP and a radio. This is specified in our “user profile”, where we list applications that are likely to be used, and file size for each application. These files need to be transmitted over a user-defined period of time. The default is one hour, but it can be expressed in multiples of one hour. In our algorithm we calculate the actual air time required to transfer all files specified in a user profile, taking into account maximum throughput that each AP can achieve, which is based on radio conditions in the network (SNR, CCI, etc). We then multiply the required airtime for each user with a total number of users in AP coverage, to get the total air time needed to transmit all files for all users. Once the total required airtime reaches or exceeds the user-specified period of time, then the maximum number of users per AP has been reached, and no more users can be served with that AP. This is what we call “airtime capacity”.

Unity Webinar – Recap on Project Management Best Practices

7 Best Practices

Hi all,

We just had a great series of webinars on a cure for your project management woes. It was fun and educational! (The dream scenario of every teacher and parent.) We covered some points of contention we face in the world of wireless network deployments. Not least of which are the dreaded “4 Pillars of the Project Apocalypse” – Software, Hardware, Regulations, and People!

OK, maybe apocalypse is a little strong, but wireless network deployment projects are really complex. So many interested parties, so many things to consider, so many things to organize and so little time. You need to make the best of what you’ve got. Using Unity, for example, is a great place to start to leverage all the brilliant designs and mobile files you’ve gathered to deliver the finest QoS your customer will be delighted with, of course.

But beyond that, I want to briefly list the 7 best practices we covered:

Store Project Assets Centrally; Make sure they are in a structured format with classifications and a search function, so you can access them later when you want to leverage what you already did. This way you save time, effort and get projects done more quickly. And don’t forget, those project assets are your IP and they also cover your posterior in case you have to prove something to an official. So cherish them dearly.
Build a ‘Diamond’; Make sure the key influencers inside AND outside your organization talk to each other on a regular basis. Sounds simple, but making it happen is hard. It’s worth the effort when questions come up.
Frequent Checkpoints; Have quality checkpoints, but don’t micromanage. Validate the completed work done using objective KPIs before moving on to the next stage of the project. Fewer long-term costs and repairs that way.
Know Your Regulations; Actually, don’t just know what the regs are, have a go-to person who is the point person for all questions. Not several people, just one. And any documents relating to the regulations should be stored in — you guessed it — your central project repository.
Think Bigger Picture; Don’t focus solely on the budget and timeline of the project. Know how strategic a project is to your organization and the importance it has to the execs. Make sure the key stakeholders (see point #2) are informed at all times, and especially execs – they HATE surprises!
Parallel and Sequential Tasks; The short version, parallel tasks are task silos that can go on without any dependence on another task, whereas sequential tasks have dependencies. For those, use a workflow engine. Way easier to manage projects.
Plan for Iterative Loops; Like the sun rises in the east there will be amendments and fixes from the final design to the actual as-built. But you can make this less painful by leveraging that Diamond I mentioned in #2. Also, plan to have your RFE and field techs hang around for a while after the “final” design, if they need to make changes and retest.

Now wasn’t the helpful? I think it was.

In future episodes of the Unity Blog, I’ll explain in greater detail what to keep in mind when you roll out your next project with iBwave tools & solutions. I promise you’ll profit from it – if not financially, then you’ll at least be able to impress your friends at parties with sage project management advice.

Deep Dive Webinar Update: Matching Smart Shoppers with Smart Networks

In our most recent deep dive webinar, we took a detailed look at how we can design optimum networks for shopping mall environments.

Summary:

Contemporary shopping malls offer more than just shopping opportunities. Many include individual restaurants and bars, a food court, movie theater, gym, skating rink, etc. Malls nowadays serve as anchors of social life in suburban areas and visitors consider wireless connectivity to be a critical aspect of their overall shopping mall experience.Given these trends it is essential to have an in-building wireless network that provides superior coverage without compromise.

Click on the links below to download the case study, presentation and webinar recording.

Download the white paper Watch the webinar