Update on Intermec Deployment of IEEE 802.11d
CN3 and CN3e 802.11d Reference
Document
September 2008
Page 1 of 8
Update on Intermec Deployment of IEEE 802.11d
Contents:
Section 1: Overview
Section 2: What is 802.11d?
Section 3: Why 802.11d?
Section 4: What does this mean to my customer?
Section 5: Steps for Implementing
Section 6: Additional Resources
Section 7: Competitive Comparisons
Section 1 Overview:
With the release of Microsoft’s Windows Mobile (WM) 6.1 operating system,
Intermec will be introducing 802.11d operation for the CK3 and CN3 Series
handheld computers. This document provides an overview of 802.11d and
explains its implementation for the CN3 and CN3e products.
Use of the 802.11d standard allows for configuration reductions in the
manufacturing of Intermec WLAN enabled products. Now a single 802.11
configuration can now support multiple regulatory domains (Ex: FCC, ETSI,
MKK, RAIIM, etc.).
Proper operation of 802.11d requires the WLAN infrastructure to have at least
one AP visible to clients broadcasting regulatory country information in its
beacon. The broadcasting of country information is possible for most Cisco
based networks, however it is not possible for legacy Intermec based networks.
In such a case, default operation will be assumed and the handheld will transmit
on channels 1-11.
Page 2 of 8
Update on Intermec Deployment of IEEE 802.11d
Section 2: What is 802.11d?
The IEEE 802.11d standard, ratified in 2001, is an amendment to the 802.11
Wireless LAN standard and adds support for multiple regulatory domains by
means of having Country Information Elements contained in beacons and
probes. This information allows an AP to indicate to the client in which regulatory
domain the network is located. The client will then use the information received
from the AP to configure its radio for proper adherence to local spectrum
regulations. This process is commonly referred to as World Mode operation.
How Does it Work?
The following is an overview of the operation details and limitations associated
with this feature:
The initial state begins with the client radio unaware of which domain it is
operating in. The CN3/CN3e radio begins searching for wireless networks by
using a default 802.11d mode where it passively scans channels 1 through 11.
At this point, there is no active RF emission from the client as required by the
standard. The client will remain in the default 802.11d passive scan mode to
scan channels until an AP has been witnessed. If the client sees beacons from
an AP on the channel being passively scanned, the system will then switch to
actively probing for wireless networks (SSID’s) on a particular channel.
When the client receives a country information element from an appropriately
configured 802.11d AP, the client will adopt the advertised regulatory domain
after locating it in the radio driver’s internal list of approved regulatory domains.
Once the country information is received and applied, it can begin to transmit
over the locally approved spectrum or channels. The client will continue to use
the advertised domain configuration until it connects to an AP advertising a
different regulatory domain. If the sends the client Country Information Element
that is not found in it’s approved list, the client will revert to a previously adopted
regulatory domain, or will continue to passively scan. In addition, all Intermec
clients will operate in this default passive scanning mode if they are being
deployed in legacy environments where the AP’s cannot support the 802.11d
functionality. Please note that while operating in this default 11d mode, adhoc
networking is not allowed.
Why Default to Channels 1-11?
For the 2.4 GHz ISM band used in 802.11b/g networking, the available channels
are very close to each other and it is possible for the radio to receive beacons
from the neighboring channels. As the radio cannot accurately discriminate
Page 3 of 8
Update on Intermec Deployment of IEEE 802.11d
channels, it is possible that the radio might incorrectly switch to active probing on
an unintended channel. To prevent potential regulatory violation by actively
probing on an unintended channel, the current Intermec default implementation
limits the passive scanning mode operation to Channels 1 through 11, as these
channels are common for all regulatory domains. This restriction prevents the
clients from operating on Channels 12 through 14, unless specifically
implemented.
Section 3: Why 802.11d?
The implemented 802.11d client functionality allows Intermec to manufacture and
support WLAN deployments with a single configuration. This simplifies our
partner’s and customer’s distribution requirements for global, multi-regulatory
domain deployments.
With the implementation of the 802.11d standards for the CN3 Series, we will be
eliminating separate configuration part numbers for the 802.11 FCC (previously
configuration number ‘84’), 802.11 ETSI (previous configuration number ‘83’) and
802.11 China (previous configuration number ‘8C’) requirements. Any CN3 or
CN3e configurations that previously included the ‘83’, ‘84’ or ‘8C’ part numbers in
positions 7 and 8, will now contain an ‘80’ to indicate the 802.11d support.
Example:
CN3AQC831G2E200 will now be CN3AQC801G2E500.
Please note: This applies only to units supporting Microsoft’s Windows Mobile
6.1 (or above) operating system. In addition, distinctive WWAN configurations
part numbers (ie. G2 or G5) are still required for each region.
Due to country specific labeling requirements for the AsiaPac region, all
distinctive CN3 and CN3e 802.11 configuration part numbers will be maintained
for sales to: Hong Kong, Indonesia, Malaysia, Philippines, Taiwan, Thailand, and
South Korea. As such, implementation of the 802.11d standards, do not apply to
these areas.
Page 4 of 8
Update on Intermec Deployment of IEEE 802.11d
Section 4: What Does This Mean to My Customer?
Intermec customers ordering a mobile handheld product that supports Microsoft’s
Windows Mobile 6.1 (or above) and requires the ability to transmit on channels
12-14 of their WLAN (and is not deploying the units in Hong Kong, Indonesia,
Malaysia, Philippines, Taiwan, Thailand, or South Korea), must enable 802.11d
on their wireless network infrastructure.
Intermec’s Windows Mobile 6.1 (or above) handheld devices are not
preconfigured to support a country’s specific regulatory channel range or
domains (like the current Window Mobile 5 configurations), and therefore no
longer come out of the box knowing which channels to transmit on. This allows
for simplifying our partner’s and customer’s distribution requirements for global,
multi-regulatory domain deployments. No longer do customers have to order a
specific wireless network radio configuration for deployment in different countries.
If your customer has Cisco AP’s deployed after year 2002, adaption of the
802.11 standards is easy, as they should only have to enable World Mode on the
AP’s and choose the country code. Everything else will function the same.
If your customer has Intermec AP’s, or and AP that doesn’t support the 802.11d
standards, and their regulatory domain supports transmitting on channels 12-14.,
they will need to purchase at least one Cisco AP, or an AP capable of supporting
the 802.11d standards and broadcasting the necessary country information
elements.
Section 5: Steps for Implementing
Support of 802.11d functionality within Intermec’s products is to be accomplished
through the use of the IEEE 802.11d standard capable of supporting multiple
regulatory domains, and commonly referenced as world mode regulatory domain.
The following list of questions is provided to assist you in helping your customer
determine whether they can support the 802.11d standards:
Q1. Do you have Intermec or Cisco AP’s?
If Cisco, go to question Q2. If Intermec, see Section 5b.
.
Q2: When did you purchase your Cisco APs?
A2: If purchased after 2002, and supporting firmware v. 12.2(15) or later,
to go Section 5a: “Overview of How to Implement 802.11d within a Cisco
AP Infrastructure.” If purchased prior to 2002, see Section 5b.
Page 5 of 8
Update on Intermec Deployment of IEEE 802.11d
Section 5a: Overview of how to implement 802.11d within a
Cisco AP infrastructure
Cisco AP’s have built-in support for 802.11d under the setting called World
Mode.
To enable 802.11d on a Cisco infrastructure follow the steps outlined below.
Prior to implementing, you will need to know the answers to the following:
Can the firmware be upgraded to version 12.2(15) or later?
Does the network include outdoor and indoor coverage?
1. Web browse into the Cisco AP. Click on Network Interfaces, found on
the left hand side of the page.
2. Next click on the Radio0-802.11G interface.
3. Click on the Settings Tab on the top, near the center.
4. Scroll down until you see a setting called World Mode.
Page 6 of 8
Update on Intermec Deployment of IEEE 802.11d
5. Click on the radial button for Dot11d.
6. Click on the drop down menu and choose the desired country from the
list.
7. When done, scroll down and click Apply. The changes will be
activated and saved.
Section 5b: Overview of How to Implement 802.11d within an
Intermec (or any other non- 802.11d Supported) AP
Infrastructure
For an implementation in an Intermec AP environment or any vendor’s AP that
does not support 802.11d, at least one AP that supports the 802.11d standards
will need to be purchased. The AP will need to be placed in an area where the
handheld will be able to hear it once. The handheld does not need to be in
constant or continuous contact with the one AP in order to function; as once it
obtains the approved country code it maintains it.
Configure the single Cisco AP as outlined in Section 5a; however, you will need
to enable a SSID in order for a Cisco AP to broadcast. It is recommended that
this SSID be different then the SSID of the infrastructure.
What if my customer refuses to deploy 802.11d?
If the customer refuses to deploy 802.11d they run the risk of violating country
domain regulations. Customers choosing not to deploy 802.11d will be restricted
to using the FCC regulatory domain and their devices only work on channels 111.
For those regions whose domains include channels 12-14, lack of 802.11d
support could generation complaints regarding poor roaming or dead spots, as
the handheld will not connect in those areas using channels 12-14.
Page 7 of 8
Update on Intermec Deployment of IEEE 802.11d
Adhoc Operation
Following 802.11d implementation and client receipt of the approved country
information element, adhoc networking is allowed on the channels approved by
the country regulatory domain.
If the CN3 or CN3e is operating in its default passive scanning mode (no 802.11d
implementation), adhoc networking is not allowed.
Section 6: Additional Resources
IEEE standards:http://standards.ieee.org/getieee802/
IEEE 802.11d Standard: http://standards.ieee.org/getieee802/download/802.11d-2001.pdf
Cisco Wireless LAN Compliance:
http://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps5861/product_data_sheet0900aec
d80537b6a_ps4570_Products_Data_Sheet.html
Contact Cisco via: www.cisco.com
Additional 802.11d Q&As available via Knowledge Central:
http://intermec.custhelp.com
Section 7: Competitive Comparisons
A competitive comparison of the MC70 and MC75 indicates that the handhelds
ship with an 802.11d set-up utility, however testing concluded that if the AP is not
properly configured to support 802.11d, the MC7x unit will not associate.
Although use of the 802.11d set-up utility on the handheld is optional, our testing
found that when using the 802.11d utility in the MC7x, the selected country must
match the country code that the AP is broadcasting or it will not associate. If the
end user does not use the 802.11d utility, then it requires choosing “Any Country”
in the AP wireless profile manager.
In summary, use of the MC7x 802.11d set-up utility requires configuration of both
the access point and handheld. Intermec’s implementation of the 802.11d
standards is limited to AP set-up (see Section 5).
Page 8 of 8