f******o
发帖数: 2469 | 1 160mhz的话
802.11ac Channel Planning
March 20, 2013
The forthcoming 802.11ac Gigabit Wi-Fi amendment will bring with it support
for larger channels at 80 MHz and 160 MHz widths. This is one of the primary
drivers behind the increased peak performance and bandwidth of wireless APs
and clients. Therefore, careful consideration of channel widths allowed on
APs and the channel plan for WLAN deployments must be made prior to an
enterprise deployment.
Channel Numbering
First, let's tackle how channels are numbered and referenced in 802.11ac.
The standard method to denote 5 GHz channels has been to always use the 20
MHz center channel frequencies for both 20 MHz and 40 MHz wide channels.
Starting with 802.11n, 40 MHz channels were referenced as the primary 20 MHz
channel plus an extension channel either above or below the primary channel
. An example would be a 40 MHz channel consisting of channel 36 (primary) +
40 (extension above).
802.11ac changes how we reference larger channel widths. Instead of
continuing to reference the 20 MHz extension channel(s), we will now
reference the center channel frequency for the entire 20, 40, 80 or 160 MHz
wide channel.
The valid channel numbers for various channel widths are:
Channel Width Valid Channel Numbers
20 MHz 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116,
120, 124, 128, 132, 136, 140, 144, 149, 153, 161, 165, 169
40 MHz 38, 46, 54, 62, 102, 110, 118, 126, 134, 142, 151, 159
80 MHz 42, 58, 106, 122, 138, 155
160 MHz 50, 114
This results in channel numbers that may look unfamiliar to most WLAN
administrators. Simply remember that channel numbers increment by one for
every 5 MHz increase in frequency. This will probably be easier to reference
through a graphic for most people. In the graphic below, identify the
center of each 80 MHz and 160 MHz channel block, follow it up to the 20 MHz
IEEE channel numbers, then split the difference between the two 20 MHz
channel numbers that it falls between. For example, the 80 MHz channel block
in UNII-1 is centered between channels 40 and 44; splitting the difference
gives us channel 42.
5 GHz Channels, with DFS and TDWR Restrictions
Non-Overlapping Channels
As I previously detailed in my post on the impact of 802.11ac on enterprise
networks, these wide channel widths may not be realistic to use in an
enterprise environment where multiple access points are deployed on non-
overlapping channels and co-channel interference must be minimized. To recap:
80 MHz wide channels allow for five (5) non-overlapping channels in the U.S.
and five (5) in the UK/EU (channels 149 and higher require light licensing
for outdoor use only) when DFS is used, but only two (2) channels in the U.S
. and one (1) in UK/EU without DFS.
160 MHz wide channels allow for one (1) non-overlapping channel in the U.S.
and two (2) in the UK/EU, with DFS being mandatory for their use in all
circumstances.
Note - In the U.S. channels 120-128 are prohibited due to TDWR restrictions,
and in the UK/EU channels in Band C (equivalent to UNII-3) require "light"
licensing an are restricted to outdoor use.
I'm purposely going to skip the 160 MHz wide channels that are possible
using 80+80 MHz discontiguous channels for simplicity at this point.
It's clear that 80 MHz channels will be hard to implement in an enterprise
setting that requires high capacity due to issues with channel re-use and
minimizing co-channel interference. Even when DFS is used, only 4 or 5 non-
overlapping channels will be available. And forget about using 160 MHz
channels in the enterprise... leave those for home use where only one AP
will be deployed (and hopefully you're neighbors don't live too close to
cause interference)!
However, it's not quite as dire a situation as that. There is a saving grace
that will allow enterprises to take advantage of these wider channels on a
"best-effort" basis. Let's step back for a moment - with 802.11n, 40 MHz
channels were an all-or-nothing proposition. The APs channel width was
statically set at 20 or 40 MHz. On the other hand, 802.11ac allows per-
frame channel width and bandwidth signaling. Practically, this means that
WLAN administrators can allow the use of wider channels by APs and clients
when all of the constituent smaller channels are clear. If a portion of the
large channel is busy at the point in time when a frame needs to be
transmitted, for instance a neighboring AP or WLAN is actively using a 20 or
40 MHz portion, then the AP or client can simply back down and use the
primary 20 or 40 MHz portion of the larger channel that is clear. For the
next frame transmission, if the entire 80/160 MHz channel is clear then the
AP or client can ramp back up and use the full channel width.
Critical to this dynamic per-frame channel width procedure is the notion of
the primary and secondary channels. The WLAN administrator must designate
which 20 MHz segment within a 40, 80, or 160 MHz wide channel is the primary
20 MHz channel. This channel forms the core frequency segment that the BSS
(basic service set) or AP radio operates on. Based on the channel blocks
depicted in the table above, the BSS will then automatically designate the
primary 40 MHz and primary 80 MHz channels by extending the primary 20 MHz
channel (moving downward through the table). Only the 40 MHz and 80 MHz
channels pictured in the table are allowed. For example primary 20 MHz
channel 56 can only be expanded into 40 MHz channel 54 (combining channel 56
and 52); combination with channel 60 is not allowed. For easy reference,
just use the channels as depicted :)
802.11ac Primary and Secondary Channels
(Image from 802.11ac: A Survival Guide)
For example, consider a 160 MHz channel in UNII-1 / UNII-2 where the WLAN
admin has selected channel 60 as the primary 20 MHz channel. The primary 40
MHz channel will be 62, and the primary 80 MHz channel will be 58. If any
portion of the secondary 80 MHz channel (ch42) is busy then the frame can
use the primary 80 MHz channel (ch58). If any portion of the secondary 40
MHz channel (ch54) is busy then the frame can use the primary 40 MHz channel
(ch62). And if any portion of the secondary 20 MHz channel (ch64) is busy
then the frame can use the primary 20 MHz channel (ch60). This allows an AP
or client to dynamically fallback to narrower channel widths in the presence
of co-channel interference or noise that only affects a portion of the
larger channel.
This has some interesting implications for channel planning!
Developing a Channel Plan
Since eliminating co-channel interference is one of the main objectives in
designing a WLAN channel plan, you'll want to carefully consider how you
select the operating channel width and primary 20 MHz channels for APs in
order to avoid co-channel interference.
First, determine if DFS channels can be used in your environment based on
proximity to radar systems and client device support. DFS client support
with 802.11a/n has been spotty at best. Hopefully 802.11ac clients will
support DFS channels since 5 GHz support is mandated by the amendment and
the FCC has eased DFS band adoption by clients since they no longer have to
implement radar detection if they passively scan (listen-only) for an AP
before transmitting any frames. In essence, they are relying on the AP to
perform the radar detection and begin operating on a DFS channel if allowed.
But until the time comes when a majority of clients support DFS channels,
administrators must verify what channels the client devices on their network
support so they don't cause coverage holes by having APs operate on
channels that clients can't use.
Second, determine the channel width that you want to attempt to "guarantee"
to client devices, which needs to be free of co-channel interference as much
as possible. This needs to be based on the density of your AP deployment as
well as client device capabilities. Remember - 802.11ac certified clients
must support 80 MHz channel width, while 160 MHz channel width is optional.
The key is to ensure that every AP has fewer neighboring APs within radio
range than non-overlapping channels available.
In high-density areas, this should be 20 MHz (stadiums, large event centers,
urban areas with many neighboring WLANs, etc.).
In normal-density areas, this is likely to be 40 MHz channels (large
building office space).
In low-density areas this could be 80 MHz channels (small buildings, few
neighbors, etc.).
In single-AP areas, this could be 160 MHz channels (such as homes or very
small offices).
Third, make a list of the acceptable primary 20 MHz channels that results in
non-overlapping channels at the "guaranteed" channel width. This will
maximize the likelihood of transmitting at the wider channel width without
causing interference with other APs. For example, if attempting to guarantee
non-overlapping 80 MHz channels, limit the allowed subset of primary 20 MHz
channels to 36, 52, 100, 116, 132, and 149. The specific 20 MHz channels
could be different than I have listed in this example, but the key point is
that only ONE primary 20 MHz channel be allowed within each "guaranteed"
wider channel width.
Finally, channels will be configured by WLAN administrators in two steps:
Select a channel width (20, 40, 80, 160 MHz) for AP or WLAN operation
This should be the "guaranteed" channel width, at minimum. It could be
larger than the "guaranteed" channel width if you want to allow APs and
clients to achieve higher peak performance when the network is fairly idle.
Since this can be done on a per-frame basis and clear-channel assessment is
performed prior to transmission, allowing dynamic use of wider bandwidth
shouldn't result in significantly more collisions. But it will result in
more co-channel interference (sharing of bandwidth) between neighboring APs.
The exact impact of per-frame channel width and co-channel interference in
a multi-AP environment will require more in-depth testing once 802.11ac
equipment is released. I would stick with using the "guaranteed" channel
width until you are able to test in your own environment.
Assign the primary 20 MHz channel to each AP (or allow auto-assignment)
The primary 40 MHz and 80 MHz channels will be determined automatically
based on the primary 20 MHz channel selected. If "Auto" channel planning is
used, which is common in enterprise WLAN equipment, ensure the subset of
primary 20 MHz channels allowed to be assigned to APs is limited to those in
your list.
Final Thoughts
802.11ac offers exciting prospects for "Gigabit" Wi-Fi. However, most of the
benefit of the first wave of products centers around the use of ever-wider
channels. Two barriers to the use of these wider channels exist for
enterprise WLANs:
Limited spectrum, resulting in insufficient channels to facilitate a re-use
plan that effectively allows wider channels without excessive co-channel
interference.
Greater reliance on DFS channels to provide more spectrum and channels,
which many Wi-Fi clients do not support today.
Luckily, the engineers designing 802.11ac learned from 802.11n's
shortcomings and devised a clever method to minimize co-channel interference
through per-frame channel width adaptation and the designation of primary
channels. This presents a fundamental shift in how administrators should
approach WLAN channel planning. Administrators should be careful in
selecting primary 20 MHz channels that result in non-overlapping channels at
the larger channel widths that they wish to use in their environments. Also
, a heavier reliance on DFS channels is required to realize the benefits
that 802.11ac has to offer in an enterprise environment. Enterprises will
need to evaluate what devices are in use on their WLANs to determine if 5
GHz DFS channel use is feasible. This can be especially problematic with
personal devices where the organization has little control over the devices
being used. However, consumer device lifecycles are typically shorter than
enterprise lifecycles, so the adoption of 802.11ac capable client devices
should occur relatively quickly (~2 years).
From an implementation perspective, most enterprises should plan around non-
overlapping 40 MHz channels, or even 20 MHz channels in high-density areas.
If the FCC frees up an additional 195 MHz of shared spectrum in late 2014 or
early 2015 then designing around non-overlapping 80 MHz channels (or
possibly even 160 MHz channels) in the U.S. will become much more practical. |
|
