Recently in 802.11n Category

Phil's Predictions for the new iPhone

| 1 Comment
WIth Apple's World Wide Developers Conference this week there are many predictions being thrown around. I have no special inside knowledge, but can't resist throwing my guesses into the mix. Yes - Apple will announce a new iPhone at the WWDC this week. It will have improved technical specifications... a camera with better resolution, video capability, 802.11n Wi-Fi, faster processor, bigger memory etc... But the new iPhone won’t be marketed that way... Apple doesn’t allow itself to be put on the “mine is bigger than yours” technology treadmill. The new iPhone will be marketed as something like : “... and now the world’s first video phone in your pocket...” Put the camera on the same side as the main screen, add video capability, add iChat.... We already have Skype for the iPhone. Voila - pocket video phone. The only challenge is the impact on AT&T’s network in the US.... Perhaps it will start out as Wi-Fi only like Skype for the iPhone.... Whatever Apple does, the new iPhone will be sufficiently cool that I will have to get one soon after it comes out. Oh.... one more thing. Steve makes an appearance during the keynote. He may the the “one more thing” of this keynote.

Our testing of WLAN systems at scale dramatically demonstrated the effects of interference on limiting WLAN capacity and performance.   And that opens the question of what other means are available to control WLAN interference and hence increase performance.

We tested enterprise wireless LAN systems based on Cisco infrastructure deployed in two ways:

  • in a conventional microcellular architecture and 
  • deployed using the InnerWireless Horizon Distributed Antenna System (DAS). 

In both cases, the same Cisco access points and wireless LAN controller were used. The main difference is in the physical layer - how the wireless signals are distributed throughout the coverage area.

We discovered that controlling interference through carefully crafting antenna coverage doubled the WLAN capacity using the same APs.

Horizon is a Distributed Antenna System (DAS) that can accommodate a broad range of wireless services operating from 400 MHz to 6 GHz including paging, public safety, 2-way radio, cellular/PCS, WMTS and Wi-Fi.  Horizon implements Wi-Fi, 802.11 a, b, g, or n wireless LANs, as layers of independent wireless service. This layered architecture is known as a layered DAS or L-DAS. The Horizon L-DAS provides pervasive coverage, and layering increases capacity in the same area by using multiple Wi-Fi access points (APs) operating on different channels. 

The layering capability is unique when compared the conventional microcellular architecture for wireless LANs, where a single access point (AP) provides both coverage and capacity in an area. In the L-DAS approach the RF coverage is engineered ahead of time. The access points are located in a wiring closet (or other convenient location with other telecom gear) on each floor and multiple antennas are placed throughout the coverage area such that the wireless signal level for each channel used is spread consistently throughout the entire area.  

In the classic microcellular approach, the access points are placed out in the coverage area and each one has its own antennas. The channel and signal level of each AP are set independently by the Wireless LAN controller and can change dynamically. Usually, the resulting coverage pattern is that adjacent access points operate on different channels. In an L-DAS, all channels are available in all locations. We compared the difference in performance for a system deployed in the conventional manner and a system deployed using InnerWireless Horizon Distributed Antenna System (DAS).

Horizon is made up of multi-coverage diversity antennas that are engineered to provide uniform signal-level RF coverage throughout a facility.  Each coverage area uses a single coax cable with multiple RF radiating elements (antennas) to provide a typical coverage area of 6000 square feet, about three times the size of the coverage area expected from a discrete access point in a microcellular deployment. This coverage area is called a segment. 

An access point is connected to the antenna segment using an access point combiner. Access points for each segment are collocated in a common location (e.g. a telecommunication closet or recessed ceiling cabinet) so that they are secure and easy to maintain. Multiple segments can be combined to provide coverage throughout an entire facility. In this architecture, a single channel of Wi-Fi covers the entire area. If more capacity is needed, more APs can be added to the antenna segment and tuned to a different channel. Each new channel provides an independent layer of wireless LAN service. At any specific location, all channels that are in use are available. 

In the 2.4 GHz band there are 3 unique channels and the DAS distributes signals for each channel throughout the entire coverage area. More channels are available in the 5 GHz band depending on which version of 802.11 is being used. Horizon supports from one to six layers on a single DAS segment for wireless LAN coverage, - three channels of 2.4 GHz and up to three channels in the 5 GHz band.   

A fully loaded L-DAS with three layers operating in the 2.4 GHz band would have three access points per 6000 square foot segment, one for each channel.  A micro cellular deployment supporting the same applications and designed for the same capacity will usually require the same number of APs. 

Our testing configuration used 3 DAS segments with 3APs each for a total of nine APs. The Microcellular 

system we tested used 9 APs to deliver coverage and capacity to the same area. 

Key Findings

  • The L-DAS exhibited lower interference between APs in the same system than the classic microcellular system.   
  • The L-DAS delivered more than double the data capacity of the discrete microcellular system in our tests.   
  • The clients on the L-DAS exhibited more uniform and predictable performance.  
  • The DAS system did not compromise the basic functionality of the Cisco Wireless LAN system. All of the expected features worked well on the DAS system. 
  • Roaming, voice support, QoS mechanisms, 802.11a/b/g and 802.11n with 20 or 40 MHz channels worked on the L-DAS with the same clients and software as the discrete microcellular system. 

The Limits of WLAN Capacity

| 0 Comments | 0 TrackBacks

We had a unique opportunity to test wireless LANs in a vacant, but fully built out office building. Most comparisons of  wireless LAN systems have been done with one access point and 10 to 20 clients in an RF chamber. While that is an  excellent controlled environment for repeatable tests with wireless clients, it doesn't reveal the subtlety of the  complete systems or demonstrate their ability to handle large scale deployments. We wanted to examine the behavior of wireless LAN systems in a more realistic environment - in this case in a 20,000 square foot office space with 10-15 APs and 72 data and 48 voice clients.

We tested wireless LAN systems from the leading enterprise vendors Cisco, Aruba Networks and Meru Networks. All of them are enterprise class wireless LAN systems with integrated security and management tools that are designed to handle very large deployments. All of the systems are 802.11 a/b/g and are Wi-Fi certified. All of them employ a wireless LAN controller that addresses the complexity of managing, securing and deploying these systems. 

There are two different system architectures represented. The Aruba and Cisco systems are examples of the micro- cellular architecture which has been the primary approach for deploying large scale enterprise wireless LANs. The Meru system uses a novel system architecture based on single channel spans and explicit AP coordination on packet transmission.    Aruba and Cisco assert the classic micro-cellular approach to scale - add more APs and decrease the transmission power of all the APs to minimize interference and maximize capacity.   Meru takes a very different approach - remembering that APs interfere at far greater distances than they can communicate and chooses to explicitly control interference.

The complete study examines what happens when we push these systems to their limits. We explore how much data capacity these systems deliver, how many voice calls are possible, and how the systems react with a mix of voice and data. The results are surprising, and illustrate some challenges for the 802.11 MAC protocol and highlight the differences between these two architectural approaches to large wireless LANs. 

The story that emerges from this enterprise wireless LAN scale testing is broader than the difference between products from 802.11 infrastructure vendors. It is really about the 802.11 protocol and how it responds when pushed to the limits in an enterprise environment.    And gives us a preview of what well crafter 802.11n versions of both these type of systems might deliver.

I would like to mention a few key results here.

Co-channel interference is a real factor in enterprise wireless LAN deployments whether they are hand tuned or configured with the vendors' automated RF tools. The interference range of Wi-Fi devices is greater than their useful communication range. There are not enough independent channels in the 2.4 GHz band to allow for deployments with continuous coverage that also have APs on the same channel spaced far enough apart to avoid self interference. This co-channel interference causes packet errors and retransmissions, limiting the overall performance of 802.11 systems under load. 

Cisco and Aruba are classic micro-cellular architecture systems. In a data only test, with 15 APs and 72 wireless clients they delivered less than 50 Mbps of system throughput. However, in a 10 AP configuration, both Cisco and Meru delivered more throughput than with 15 APs. Aruba's throughput increased from 46 Mbps to 64 Mbps - almost 40%. If the APs in the system were perfectly isolated from each other, we would have expected the 15 AP configuration to deliver 50% more throughput than the 10 AP configuration with the constant load in this test. But more APs allow more simultaneous transmissions which caused more interference and lowered performance for these systems. 

The Meru system has a very different architecture and deployment strategy that is designed to deal with these enterprise deployment issues. The recommended Meru deployment starts out with all APs on the same channel. In our test environment, we were able to cover the entire floor with 5 Meru APs operating at high power. On the surface, the Meru approach seems like it would be low capacity since it essentially groups APs together on the same channel and the same collision domain. However this deployment approach allows the Meru WLAN controller to coordinate the airtime access of the APs and (indirectly) wireless clients in the system. To increase capacity in the Meru system, a new set of APs is added in the same area, all tuned to a different channel and still operating at high power. The 15 AP Meru configuration we tested is three independent channel spans with 5 APs each on channels 1, 6 and 11. This approach runs contrary to the micro-cellular deployment exemplified by Cisco and Aruba, which adds more APs at lower power distributed throughout the coverage area in order to increase capacity. 

10 AP Throughput (Mbps)

15 AP Throughput (Mbps)










With 10 APs, the Meru, Aruba and Cisco APs delivered approximately the same aggregate capacity.   With the increase in APs to 15  (and the power and cell transmission frequency adjusted for Cisco and Aruba), the Cisco and Aruba capacities substantially decreased, while the Meru system increased its capacity to deliver twice the system throughput of the micro cellular systems in the 15 AP configuration and almost twice the capacity of the 10 AP configuration. 

This dramatic difference was surprising. Co-channel interference is worse that we expected at this scale, and AP coordination is a significant benefit for enterprise WLAN systems. The micro-cellular systems had a very high link level packet retry rate during the testing. (We saw retry rates greater than 40% during some of the tests.) The Meru system with AP coordination had a much lower retry rate. and the result is better system throughput. 

The micro-cellular systems did not scale well. We thought 15 APs would be reasonable for high capacity testing in our environment, but Cisco and Aruba did not perform well with that many APs in this space. They both delivered higher system throughput (and better voice performance) with 10 APs.   

Clearly, adding more APs did not increase the capacity of the micro- cellular systems and there is a limit to the number of APs (and the system capacity) that can be effectively deployed in these systems. The Meru system delivered better performance than the best micro-cellular system in the 15 AP tests. Coordinating access with neighboring APs is a promising area that should be pursued by 802.11 for both increased performance within the same system and better co-existence with other systems in the unlicensed bands. 

Broadband Stimulus

There is a portion of the American Recovery And Reinvestment Act that will fund programs to accelerate the deployment and use of broadband in the United States. In particular, the NTIA's Broadband Technology Opportunities Program (BTOP) and the Department of Agriculture's Rural Utility Services (RUS) grants and loans will go to fund programs "in unserved, underserved, and rural areas and to strategic institutions that are likely to create jobs or provide significant public benefit". These programs are handing out billions of dollars in the next 18 months and will likely have thousands of applicants for the much needed stimulus money. How will these agencies do it? It is a daunting task and efforts are already underway. The first open public meeting was held earlier this week and two more will be held in the coming weeks. At this point there are more questions than answers. How are these agencies going to work together? Who is eligible to receive a grant? How will the success of the program be measured overall? What does "underserved" mean? For that matter - what does "broadband" mean? In the new era of transparency and accountability, grant applicants will have to explain how they are going to execute their program, deliver the claimed benefits, and measure the results. For the wireless broadband piece, this brings us right back to the basics. What are the technical requirements to support a given application - coverage, throughput, latency and overall system capacity? In order to support multiple different applications, what are the system level requirements? What performance is required to deliver an acceptable user experience? Perhaps it is time to dust off our Novarum lessons from the first round of Municipal Wireless. We can not afford to repeat those mistakes again.
IEEE 802.11n is the new international standard for wireless Local Area Networks, incorporating new smart antenna technologies (MIMO - Multiple In and Multiple Out) permitting a 5x performance and 2x coverage improvement for WLANs. While this new technology is now becoming the de facto standard in consumer and enterprise networks, it has not yet made an appearance in outdoor, metropolitan scale networks derived from WiFi technology. Many of these same MIMO techniques are being incorporated in both WiMax and in LTE for cellular. Sadly neither is being produced in much volume as yet and fixed WiMax networks do not incorporate MIMO technology. There has been much dispute about whether the specifics of 802.11n designed for indoor networks would apply to outdoor networks and bring the economy of scale of 802.11 to outdoor applications. We (Novarum) decided to test the effects of .11n on outdoor performance. We found dramatic improvements in using indoor 802.11n technology outdoors - so much so that 802.11n has become the recommended baseline for new network deployments. First, let’s review the key pieces of technology incorporated in 802.11n and how it might affect outdoor performance.
Maximal Ratio Combining Receiver combines signal from multiple paths to maximize SNR. We can see a 3-4 dB receiver link budget improvement even to legacy clients. Dramatically improved receiver signal strengths and dramatically reduced packet error rates. More reliable use of higher level encoding methods increasing link performance.
Transmit Beam-forming Modulate phase and amplitude from multiple antennas to create phased antenna array pointing increased performance at the destination node. 7-8 dB gain possible with omnidirectional antennas Decreased inteference, increased capacity, decreased deployment cost. Likely directional antenna performance with omnidirectional antennas substantially increasing network performance and decreasing deployment cost.
Spatial Multiplexing Use the redundant paths created by multipath to increase throughput by transmitting data in parallel paths. Probably not compelling outdoors since high SNR needed for parallel data paths. However, increasing reliability by taking advantage of multipath around deep fades.
Channel Bonding 20 and 40 MHz channels in both 2.4 and 5 GHz bands 20 MHz channels legacy compatible while 40 MHz channels double throughput, mostly useable in the 5 GHz band.
Protocol Improvements Packet aggregation Modest overhead reduction and performance improvement for streaming media and bulk transfers
Cost Reduction Indoor WiFi network demand is for low cost, dual band (2.4 and 5 GHz) simultaneous radios at commodity prices The availability of these dual band 3x3 MIMO chipsets drives the cost of multiradio outdoor units down
In the course of Novarum’s Wireless Broadband Review in 2007 and 2008, we examined over 25 deployed WiFi networks (including all major vendors), 46 deployed 3G cellular networks and 4 fixed pre-WiMax networks. In the case of the WiFi networks, we noted the dramatic effects that client selection had on network performance, coverage and ultimately user satisfaction. We both examined 802.11n clients against the installed multivendor base of 802.11g infrastructure and constructed our own testbed from early outdoor 802.11n components to evaluate the effect of 802.11n when deployed in the infrastructure itself. It is important to recognize that in almost all outdoor WiFi networks, the client access uplink is the weakest link in the communication chain. Legacy 802.11b/b clients experience VERY high packet retry rates of between 100 and 1000% and there are often deep multi-path fades of between 10-30 dB within a few tens of feet. The WiFi protocol is VERY good at masking these effects - instead they are most commonly seen indirectly - by lower throughput and higher delay variance. These effects are seen even for deployments of very high access node density of 50 nodes per square mile or more. These deep fades and very high packet retry rates made mobility difficult, dramatically effect throughput, make packet delay variance so high as to make streaming media difficult and materially decrease the overall capacity of these networks. The improvements that 802.11n provides outdoors astonished us - particularly for a technology that has been disparaged as inappropriate for outdoor deployment. Deploying IEEE 802.11n technology has dramatic effects outdoors - both with legacy systems and even more compellingly with green fields deployment. Let’s summarize the facts of what we found in Novarum’s experiments:
  • 100% throughput improvement of 802.11n WiFi clients with legacy 802.11g outdoor infrastructure;
  • 100% throughput improvement of legacy 802.11g WiFi clients with new 802.11n outdoor infrastructure;
  • 200% throughput improvement of 802.11n client with 802.11n outdoor infrastructure;
  • Similar coverage of 802.11n clients and infrastructure in the 5.4 GHz band as for legacy 802.11g clients and infrastructure in the 2.4 GHz band - making the 5.4 GHz band useful for client access;
  • 25% decrease in access latency and a dramatic improvement in latency variance;
  • a low power 802.11n client has the same throughput and coverage as a high power 802.11g with 10x the power and antenna; and
  • coverage to smartphones at low power and with poor antennas dramatically improves.
These results have a dramatic impact on outdoor wireless networks - bringing the benefits of MIMO technology at consumer price-points. We can expect that 802.11n technology will dramatically improve outdoor WiFi networks.
  • 4-800% increase in system capacity and throughput
    • 2-300% improvement in spectral efficiency through increased link budgets, reduced packet errors, increased modulation rates and improved fading performance
    • effective client access to the 200 MHz of the 5.4 GHz band
  • 802.11n clients dramatically improve legacy 802.11g networks and new 802.11n networks dramatically improve legacy 802.11g clients.
  • Streaming media applications will perform as we expect and will be much easier to deploy.
  • Better backbone designs by reducing the interference of the backbone mesh through beam-forming antennas rather than omnidirectional broadcast.
  • Decreased deployment cost due to decreased node cost. Possibly dramatically.
While not optimally designed for outdoors, 802.11n will SUBSTANTIALLY increase the performance and customer satisfaction of outdoor wireless networks. We can expect the first product announcements of outdoor WiFi networks incorporating 802.11n shortly and can expect that all major vendors of outdoor WiFi equipment to be shipping by the end of 2009. Novarum recommends that all new outdoor WiFi networks use 802.11n products in their infrastructure and strongly recommends 802.11n clients wherever possible.

Rural Internetification Project

| 0 Comments | 0 TrackBacks
One of the smaller towns we tested in the NWBR was Rochelle, IL - a farming town of 10,000 people about 75 miles West of Chicago. In this case the ISP providing wireless internet service was the city itself through the Rochelle Municipal Utilities organization - along with power and water. It was an interesting experience going to the small office, right next store to the window where a citizen would pay their electric bill, to shop and sign up for Internet service ... with a variety of recommended CPE devices displayed on the wall. One the key items we argue about in building municipal networks is ownership - who should own and operate the network? And here in Rochelle was a rather good wireless network that was built by the town. And clearly where other options for broadband access offer poor performance or do not exist (The city started by offering dial-up Internet access and the wireless cellular carriers offer spectacularly poor wireless data products - the city’s networks offers roughly 20x the performance of the sadly 2G wireless cellular networks in the town.) This reminded me of the Rural Electrification Project (that had originally sponsored bringing electricity to Rochelle after WWII) - (from Wikipedia): In 1936 the Rural Electrification Act was enacted. Also, the Tennessee Valley Authority is an agency involved in rural electrification. The Rural Electrification Administration (REA), a former agency of the U.S. Department of Agriculture, was charged with administering loan programs for electrification and telephone service in rural areas. The REA was created in 1935 by executive order as an independent federal bureau, authorized by the United States Congress in 1936, and later in 1939, reorganized as a division of the U.S. Dept. of Agriculture. The REA undertook to provide farms with inexpensive electric lighting and power. To implement those goals the administration made long-term, self-liquidating loans to state and local governments, to farmers' cooperatives, and to nonprofit organizations; no loans were made directly to consumers. In 1949 the REA was authorized to make loans for telephone improvements; in 1988, REA was permitted to give interest-free loans for job creation and rural electric systems. By the early 1970s about 98% of all farms in the United States had electric service, a demonstration of REA's success. The administration was abolished in 1994 and its functions assumed by the Rural Utilities Service. The Rural Electrification Administration (REA) was an agency of the United States federal government created on May 11, 1935 through efforts of the administration of President Franklin D. Roosevelt. The REA's task was to promote electrification in rural areas, which in the 1930s rarely were provided with electricity due to the unwillingness of power companies to serve farmsteads. America lagged significantly behind European countries in rural electrification. Private electric utilities argued that the government had no right to compete with or regulate private enterprise, despite many of these utilities having refused to extend their lines to rural areas, claiming lack of profitability. Since private power companies set rural rates four times as high as city rates, this was a self-fulfilling prophecy.[1] Under the REA program there was no direct government competition to private enterprise. Instead, REA made loans available to local electrification cooperatives, which operated lines and distributed electricity. By 1939 the REA served 288,000 households, prompting private business to extend service into the countryside and to lower rates. By the end of the decade, forty percent of rural homes had power, up from around 10% in 1930. From 1949, the REA could also provide assistance to co-operative telephone companies. In ten years, rural electrification increased from 10% of rural homes to 40% by 1940. So why can’t we use this already successful model of the Rural Electrification Project as the basis for government deploying broadband, particularly in less developed areas? While some of the early attempts at municipal wireless were not considered successful (Philadelphia, for example) they had the clear effect of dropping the local cost of wired broadband access. Competition beyond the entrenched monopolies of DSL and cable is a good thing.

Why Network Clients Matter!

| 0 Comments | 0 TrackBacks
It was clear from the beginning of the NWBr that the proper choice of client device makes all the difference in the complete system performance of a municipal wireless network ... and in particular the user experience. Cellular and pre-WiMax (and mobile WiMax when delivered) networks precisely specify the client and test its performance. These clients are much more rigorously controlled and, in general, have much high transmit power and better antennas with less noise than WiFi clients. In the process of the NWBR we have tested many client devices to see the effect of client devices on network performance - testing them in the same networks in the same locations, at the same time ... to more accurately assess the difference. We tested the following clients:
  1. Standard 802.11g laptop client - approximately 30 mW output power
  2. A high power 802.11g laptop client - approximately 200 mW output power
  3. A first generation 2x2 MIMO 802.11n client - approximately 30 mW output power. Current .11n clients should have even better performance.
  4. First generation iPhone smartphone WiFi client.
Let’s first examine the average performance of these clients across all the networks in which they were tested.
Client Delay (msec) Uplink (kbps) Downlink (kbps) Availability
Average Laptop 157 481 1030 64%
Average High Power 113 767 1286 85%
Average .11n 115 845 1712 82%
Average iPhone 422 231 810 45%
The clear performance advantage of the higher power client and for the 802.11n clients leaps out. Both deliver average megabit performance with approximately 85% outdoor availability - availability comparable to both the best of cellular and pre-WiMax with superior performance. The lower performance of both the standard laptop client and the iPhone client is understandable with the low power iPhone still showing a rather amazing 45% availability on average. The difference a good infrastructure network makes is clear when we look at the best performance by each of these clients. Our top three performing networks (Minneapolis, Toronto, and St. Cloud) all deliver outstanding performance but the single best performances were by the laptop, high power AND .11n clients in Minneapolis - delivering multimegabit performances that leave both cellular and pre-WiMax in the dust - while delivering avaiailability uniforming over 80% - including 100% for the high power client. The St. Cloud network delivered the best performance and availability combination for the iPhone client with 75%.
Client Delay (msec) Uplink (kbps) Downlink (kbps) Availability
Best Laptop (Minneapolis) 74 457 3090 80%
Best High Power (Minneapolis) 63 2062 2949 100%
Best .11n (Minneapolis) 77 1939 3237 82%
Best iPhone (St. Cloud) 415 158 831 75%
Some conclusions:
  1. A modern WiFi network designed with appropriate access node density ( greater than 40 nodes/mi^2) can deliver performance and coverage that outperforms cellular and pre-WiMax.
  2. The increasing usage of 802.11n in client devices will only improve the quality of already installed networks ... increasing performance, coverage and user satisfifaction.
  3. All the WiFi network infrastructure we tested was 802.11g compatible, often without diversity antennas for the uplink from clients. As infrastructure vendors move from .11g to MIMO .11n we can only expect these performance gains to increase even more.

Novarum Wireless Broadband Review

| 0 Comments | 0 TrackBacks
We have been curious about how real wireless networks perform - both in the enterprise and in metropolitan areas. We have also been impressed by how few third party measurements at scale have been performaned for both applications of wireless networks. Most of our knowledge about how these networks really deliver service is either based on anecdotal reports or the marketing information from the service providers and equipment vendors. So we decided to test and obtain some real, non-partial information. We went out and tested over 136 wireless networks in 22 North American cities from July 2006 through early 2008. We devised an network independent testing regime that mimics the behaviour that ordinary users of these services would observe - testing packet delay, upload and download throughput (using industry standard tools) and percentage of the claimed service area in which we could actually get service. We tested in the following cities (some twice to reflect major changes in the networks between tests): Anaheim CA (2x), Brookline MA, Chico CA, Cuperino CA, Daytona FL, Eugene OR, Foster City CA, Galt CA, Longmont CO, Madison WI, Minneapolis MN, Mountain View CA (2x), Palo Alto CA, Philadelphia PA (2x), Portland OR (2x), Raleigh NC, Rochelle IL, St. Cloud FL, Santa Clara CA, Sunnyvale CA, Tempe AZ, and Toronto ON (2x). Where we could find them, we tested cellular data networks from ATT (nee’ Cingular), Sprint and Verizon; pre-WiMax networks from ClearWire and WiFi networks from a variety of ISPs. The data clearly shows that all these technologies can deliver similar levels of service when properly built out. Subsequent blogs will address individual lessons learned for each of these network technologies.


| 0 Comments | 0 TrackBacks
This blog is the combined thoughts of Ken Biba and Phil Belanger ... two pioneers of wireless networking and arguably two of the co-inventors of the networking systems we think of as WiFi:
  1. Minimal licensing.
  2. Sharing of scarce radio spectrum.
  3. Robust technologies that survive (and often prosper) in a severe radio environment.
  4. Dirt cheap.
  5. Ubiquitous.
  6. High performance.
Look for us to be posting product critiques, technology thoughts and the results from our ongoing measurements of both enterprise and municipal networks. Over the last 18 months, we have done extensive studies of many of the foundation myths of deploying large scale wireless networks in both large enterprise and metropolitan environments. We will be reporting on those studies here and many of the implications of those studies on future use of unlicensed technology for providing mission critical network services. The Novarum Wireless Broadband Review surveyed and measured over 100 deployed municipal WiFi, cellular and pre-standard WiMax networks and comprises the largest available database of experience about these networks. We will be using this large experience base to inform our comments ... rather than mere opinion. We look forward to your comments.