Canopy DFS Deployment Guide - Final

Technical Brief
Canopy® Dynamic Frequency

Selection Deployment Guide
Version: 1.0
Issued: February 2008

Notices
The vendor data in this Technical Brief derive from public documents available from the
Internet. Motorola provides this vendor data for Canopy users’ information only and does
not provide any recommendations.
Please refer to the Canopy System User Guide for:
◦ Personal safety guidelines in Preventing Overexposure to RF Energy

◦ Important regulatory and legal notices

Trademarks, Product Names, and Service Names
MOTOROLA, the stylized M Logo and all other trademarks indicated as such herein are
trademarks of Motorola, Inc.® Reg. U.S. Pat & Tm. Office. Canopy and Duo are
trademarks of Motorola, Inc. All other product or service names are the property of their
respective owners.
© 2008 Motorola, Inc. All rights reserved.
www.motorola.com/canopy
Table of Contents
List of Figures .................................................................................................................................. 4
Canopy – Overview of Dynamic Frequency Selection Deployment Guide ..................................... 5
1.0 Abstract...................................................................................................................................... 5
2.0 Definition of Dynamic Frequency Selection............................................................................... 5
2.1 Relationship to Transmission Power Control......................................................................... 6
2.2 Motorola’s Recommended Best Practices............................................................................. 6
2.3 Likely Sources of DFS-type Signals ...................................................................................... 9
2.4 Using Canopy for Site Planning to avoid DFS Events ......................................................... 12
3.0 Canopy’s Implementation of DFS............................................................................................ 15
3.1 Canopy Release 8.2 FCC DFS Operation........................................................................... 16
3.1.1 Canopy FSK 5.4 GHz Band 20 MHz Channel Plan.......................................................... 17
3.1.2 Canopy 5.4 GHz Band OFDM 10 MHz Channel Plan ...................................................... 19
3.2 Canopy Release 8.2 EU/UK Operation ............................................................................... 20
3.3 Summary of DFS Recovery Times ...................................................................................... 21
3.4”False Positive” Mitigation..................................................................................................... 22
3.4 Prizm EMS Management of DFS......................................................................................... 23
4.0 Summary ................................................................................................................................. 24
Appendix A Additional DFS Details .............................................................................................. 25
A.1 Selected DFS Terminology.................................................................................................. 25
A.2 Outline of Conforming DFS Operation ................................................................................ 26
A.3 DFS Timer Values stipulated by the FCC ........................................................................... 27
A.4 Radar Waveform Profiles Detected..................................................................................... 27
A.5 Detailed DFS Requirements – FCC and ETSI .................................................................... 29
Appendix B DFS Regulatory Domain by Country.......................................................................... 31
Appendix C References................................................................................................................. 32
Appendix D 5.2 GHz Band 20 MHz Channel Plan ........................................................................ 33
Appendix E List of USA TDWR Sites ............................................................................................ 34
Technical Brief: Canopy DFS Deployment Guide Page 3

List of Figures
Figure 1 Schedule Whitening on Canopy Configuration Radio tab. 8
Figure 2 A sample map of TDWR airport sites circa 2001. 10
Figure 3 Locations of Canadian C-band weather radar. 12
Figure 4 Example 5.4 GHz Spectrum Analyzer Result 14
Figure 5 Screen capture of DFS Regional Settings menu. 15
Figure 6 20 MHz channel plan potential given 25 MHz centers. 17
Figure 7 A suggested Channel Plan for 5.4 GHz FSK Canopy. 18
Figure 8 DFS channel plan for Canada and Australia. 18
Figure 9 Canopy 5.4 GHz OFDM 4-sector recommended channel centers. 19
Figure 10 OFDM 10 MHz Channel Plan avoiding 5600-5650 MHz. 20
Figure 11 ABCD channel plan for 5.4 OFDM; avoids weather notch. 20
Figure 12 Screen capture of DFS-related Prizm Alerts. 23
Figure 13 Summary of FCC DFS requirements. 29
Figure 14 List of USA TDWR Sites Error! Bookmark not defined.

Canopy – Overview of Dynamic Frequency
Selection Deployment Guide
1.0 Abstract
This Technical Brief describes a new Canopy feature called Dynamic Frequency
Selection (DFS). This feature is mandated by the Federal Communications Commission
(FCC) in the United States to reduce potential interference to certain military and
meteorological radars by 5.2 GHz and 5.4 GHz Unlicensed National Information
Infrastructure (U-NII) radio equipment. This DFS is similar to, but not identical to, other
national DFS requirements, for example the European Union’s (EU) requirements (ETSI
1.3.1). Canada has adopted the FCC’s definition of DFS as specified by Industry Canada
RSS-210, as has Australia.
In particular, Motorola 5.2 GHz and 5.4 GHz Canopy, a Broadband Wireless Access
(BWA) technology intended for the fixed and nomadic (“portable”) market, are impacted
by all of these DFS requirements. Fortunately the 5.4 GHz band is very large, namely
255 MHz, wider than 5.2 and 5.7 GHz bands together. The ability to move to alternate
channels within the 5.4 GHz band helps greatly to mitigate DFS issues that may occur.
In addition, nations outside of North America have DFS requirements in the 5.7 GHz
band. Canopy BWA products intended for those nations are DFS capable.
This document is intended to inform and provide guidance to Canopy equipment

operators of the basics of Canopy DFS operation and its likely impact on BWA services in
the 5.4 GHz band. Emphasis is placed upon the FCC DFS applicable to the USA and
Canada although implications for other regions are also discussed.
The DFS rules of the FCC and of the EU are not identical, but are close and are intended
to meet the same purpose, namely to avoid interference with certain radar signals.
However, in general only those radars profiled (pulse repetition rate and pulse width) with
a received signal strength above -62 dBm are a concern.
Note that this Deployment Guide concerns the general topics of 5.4 GHz deployment and
DFS and is not intended to be a User Guide supplement; please consult the Canopy
System User Guide for explicit information on how to configure Canopy DFS.
2.0 Definition of Dynamic Frequency Selection

DFS regulation falls into two camps: those that are “FCC oriented” and those that are
“ETSI oriented”. Appendix B lists the countries in these two groups.
The FCC U-NII band devices are unlicensed intentional radiators that operate in the
frequency bands 5.15-5.35 GHz and 5.47-5.825 GHz. Specifically, the new FCC rules
require that U-NII devices operating in the 5.25-5.35 GHz and 5.47-5.725 GHz bands
employ DFS.
Note that 5.15-5.25 GHz and 5.725-5.825 GHz are not subject to DFS in the USA and
Canada.
Specifically the FCC issued “orders” for DFS by revising Part 2 and Part 15 of its
regulatory code. Since the initial issuance the rules for DFS have been changed slightly
and clarified. Consequently we reference this document:

Revision of Parts 2 and 15 of the Commission’s Rules to Permit
Unlicensed National Information Infrastructure (U-NII) devices in the 5 GHz
band, ET Docket No. 03-122 MEMORANDUM OPINION AND ORDER,
adopted June 29, 2006 and released June 30, 2006; FCC-06-96A.
The relevant Canadian DFS requirement is stated in document RSS-210 Issue 7, June
2007.
DFS is a feature that monitors the spectrum and selects for operation a frequency
channel that is not already in use. Prior to the start of any transmission, a U-NII device
equipped with DFS capability must continually monitor the radio environment for
presence of radar signals. If the U-NII device determines that a radar is present it must
either select another channel or enter a “lockout mode” if alternate channels are not
available; at that time the device then enters a one minute “listen mode”.
In addition, DFS deployment must provide, on aggregate, a Uniform Spreading of the

Operating Channels across the entire band. This is defined as the spreading of U-NII
device Operating Channels over the 5.25-5.35 GHz and/or 5.47-5.725 GHz bands to
avoid dense clusters of devices operating on the same Channel.
For equipment operating in the 5.25-5.35 GHz band, the FCC requires all manufactures
who apply for equipment certification of U-NII devices filed on or after July 20, 2006 to
comply with the U-NII rules for DFS. Operators using equipment operating in the 5.25-
5,35 GHz band must comply with the DFS requirements for that equipment imported or
marketed on or after July 20, 2007.
All U-NII equipment operating in the 5.47-5.725 GHz band must comply with the FCC
regulations for DFS.
In general only those radars profiled by the FCC (pulse repetition rate and pulse width)
with a received signal strength above -62 dBm are a concern.
The FCC DFS rules are applicable only to the Canopy Access Point (AP) and Backhaul
Master (BHM) whereas other nations require direct involvement of the Canopy SM and
BHS devices. In effect, the FCC DFS rules are somewhat simpler to implement.
2.1 Relationship to Transmission Power Control

Transmission Power Control (TPC) is also mandated by the same FCC Order requiring
DFS. These are distinct technologies with distinct rules and serve distinct purposes.
TPC applies only to U-NII devices having an EIRP exceeding 500 mW (27 dBm) and is
intended maintain the EIRP even when a higher gain antenna is configured.
It is useful to know that Motorola Canopy products are also TPC compliant; they have the
capability of reducing Tx power by manual configuration.
Additional technical details of DFS are provided in Appendix A.
2.2 Motorola’s Recommended Best Practices

In subsequent sections this document describes guidelines and configurations in detail
that minimize DFS issues. For quick reference, Motorola’s “best practice”
recommendations and deployment considerations are listed here:

1. Test the spectrum in your operating area for existing use prior to deployment; this
doesn’t necessarily require a separate spectrum analyzer. A Canopy AP in its
Spectrum Analyzer mode is usually sufficient for this purpose. The safest option
is to deploy an AP and monitor traps with Prizm or other SNMP-based tools.
2. Remember that in the “FCC states” only the AP and BHM devices are active in
DFS detection whereas the “ETSI states” additionally require DFS detection for
the SM and BHS. This may influence your deployment plan.
3. Run the tests in several directions and in as many channel centers as possible;
each test period should last several days. Note “problem sectors” and “problem
channel centers” over a week’s time.
4. Devise a channel plan along the lines described in Section 3.
5. Weather radar that is DFS sensitive is confined to a narrow band of spectrum

between 5.6 to 5.65 GHz. It is best to avoid this sub-band unless testing
indicates the lack of DFS events. The remaining 5.4 GHz spectrum is still very
large and offers many alternate channels, namely 5.495-5.575 GHz and 5.675-
5.705 GHz.
6. Alternate channel frequencies should be at least one channel bandwidth from the
primary frequency and from each other, if possible. Remember that there is a
“Uniform Channel Spreading” requirement. This simply means to use channels
throughout the band.
7. Test and note that DFS “hits” can be direction-specific. DFS “hits” can affect one
AP (with the same frequency) without affecting its opposite mate on the cluster.
In this case, you may want to change the frequency of one AP, but not the other.
8. Even after careful site surveying and channel planning, it is possible to encounter
“random” DFS detections. If so, this means that service in the impacted AP
section is down for the required DFS “listen time” and then each SM (in the
sector) must scan and re-register with the AP on the chosen alternate channel.
In total, a particular subscriber may experience a service outage longer than the
one minute listen time. Experience suggests about 1.5 minutes; this depends
upon the number of SMs in the impacted sector.
Choosing alternate channels at least one channel bandwidth distance from your
primary channel increases your chances to resume transmission more quickly.
9. In those countries (“ETSI states”) requiring that the SM/BHS also actively listen
for DFS detection prior to operation, the service downtime will be 2 minutes at
minimum, with 3 minutes likely in SM-dense sectors.
10. For any FSK Canopy units, enable “schedule whitening”* to avoid self-
interference and reduce the possibility of “false positive” DFS detections.
Schedule whitening is not applicable to Canopy’s OFDM products.
11. In general site Canopy base stations away from the Terminal Doppler Weather
Radar (TDWR) sites hosted by major U.S. airports. Being located below the
horizon (10 or 20 miles from the radar site) is usually sufficient. As a rule, the
TDWR sites are located within 10 miles of the host airport. (See the list of U.S.
airports hosting TDWR sites in the Appendix.)

12. If deploying near a military base, a spectrum analysis is warranted; do not
assume the 5.4 GHz band is not usable in these areas. This will vary by military
base.
13. Many Canopy customers state that in their experience the 5.4 GHz band is
relatively quiet and “clean” compared to the 5.7 GHz band, and that they plan
further 5.4 GHz band deployments.
14. Consider using unique color codes to maintain the original AP to SM relationship
should a DFS channel change occur if that is important in your network.
15. Always update Canopy software to the latest version as it is further optimized for
DFS and additional fixes and features.
16. If experiencing DFS events try downtilting or re-orienting the AP to avoid the
radar’s beam..
*“Schedule Whitening” is a transmission technique that changes the energy pattern of

Canopy equipment so as to avoid peaks that could be interpreted as radar and trigger
DFS. Whitening is not part of the DFS specification, but rather is a technology used by
Canopy to reduce or eliminate false positives from self interference, and is recommended
for all sectors, especially those in frequency bands running DFS in your country or region.
Whitening is enabled on the Configuration → Radio page of a regular Canopy AP or

BHM, using the parameter “Schedule Whitening”. See Figure 1.
Figure 1. Schedule Whitening on Canopy Configuration Radio tab

Important: once Whitening is enabled on an AP or BHM, SMs or BHSs must be running
at least Release 8.2 to register to that AP or BHM. SMs or BHSs running previous
releases will not register to an AP or BHM that has Whitening enabled.
2.3 Likely Sources of DFS-type Signals

DFS is explicitly meant for the protection of “C band” 1 radar profiles (see Appendix A).
The FCC profiles do not indicate the type of radar equipment that produces such signals.
They could be government (national weather or military) or private (weather).
A significant number of radar devices in the C-band do not fall within the FCC’s radar
profile. Therefore, they should not trigger a DFS event. For example, the FAA’s air traffic
control radar operates in a different band and does not fit within the FCC’s profile and
should not trigger a DFS event.
In the USA, the national government operates about 510 radar sites for weather and air
traffic control (excludes military) which can be categorized into seven types: ASR-9, ASR-
11, ARSR-1/2, ARSR-3, ARSR-4, NEXRAD, and TDWR. Of these seven types only the
FAA’s Terminal Doppler Weather Radar (TDWR) is in the C-band, with about 45 sites
deployed near the largest airports (representing 1.5% of all US airports)..
The Federal Aviation Administration (FAA) indicates that all TDWR use is in the 5.6-5.65
GHz range. The FAA site referenced in the Appendix indicates that no other FAA
aviation frequencies impact Canopy’s unlicensed bands. All the remaining government
radars (excludes military) operate in the S-band and so do not produce DFS events.
However, privately owned weather radars (e.g. television stations), do exist in the US
using the C-band. It is difficult to identify these sites or specifically characterize their
radar signal. From all indications, these also primarily operate in the 5.6-5.65 GHz “sub-
band” as this band appears to be particularly suited for weather detection.
Weather radar like TDWR has a very narrow “pencil” beam, typically less that 1° in both
horizontal and vertical. It typically rotates in about 5 to 10 seconds and “paints” a vertical
helix pattern, covering the desired “volume” over several minutes. Consequently, given
the earth’s curvature, it is likely that TDWR is not a 5.4 GHz band issue when the Canopy
equipment is at least 20 miles from the TDWR site (which is typically ~ 10 miles from the
airport such that the site is outside of the airport’s “ground clutter”).
Table 1 shows the technical properties of TDWR.
1
Recall that the electromagnetic spectrum is divided into letter-coded bands, with the C-band being 4 cm to 8
cm wavelength (approximately 3.9 to 6.2 GHz). Source: http://www.jneuhaus.com/fccindex/letter.html).

Table 1 Technical Properties of TDWR.
Figure 2 A sample map of TDWR airport sites circa 2001
Figure 2 shows a map of TDWR sites (circa 2001) and a picture of a TDWR tower
complex. A list of 44 US host airports is included in the Appendix E. Note that this list
could change over time should TDWR grow in popularity.
All government and private weather radar operation is licensed by the FCC.
Example vendors of C-band weather radars are PulseSystems (www.pulsesystems.com),

Enterprise Electronics Corp (www.eecradar.com), and Radtec Engineering Inc
(www.radar-sales.com). The maximum pulse transmit power of these can be as high as
1MW but are typically about half that.
Military Radar
The US military also operates a number of C-band radars which could trigger a DFS
event. Most of these military sites are fixed but some mobile units do exist including
airborne radar. This radar is not used frequently and may be used on occasion for military
base training.

This will vary by region. A thorough spectrum analysis is the best method to detect this
radar in your service area.
Some military radar is of the “frequency hopping” type, in which the radar’s operating
frequency is changed frequently and in a random pattern. Note that this means the BWA
operator can’t necessarily avoid such a DFS event merely by channel frequency planning
if they are operating a DFS-enabled unit within ~ 20 miles of the radar’s site.
Maritime Radar
Although common operating procedures suggest that vessels turn off their radar when in
port, this is not done consistently – by both military and commercial vessels.
Radar equipment may be used while in port for routine maintenance, servicing or repair
work or to stabilize the unit before leaving port. Such vessels may trigger a DFS event
while in port or within ~ 20 miles of the DFS-enabled devices.
It is common practice for short stay vessels to put radars onto “standby” while in port. No
radar emissions occur while on “standby.”
Most radar is configured for a particular frequency within the radar’s band, and with a
particular pulse width and particular pulse repetition rate. These settings can be re-
configured by the operator as needed but it is not known whether this is a real concern.
International Weather Radar
Outside of the US the radar situation is much the same. A big difference is that certain
countries, such as Canada, Australia, and the European Union countries, have deployed
C-band based weather radar nationally. All indications suggest that the 5.60 to 5.65 GHz
sub-band is also commonly used internationally for weather detection. However, other
frequencies might also be licensed for this use.
For example, Canada and Australia employ C-band weather radar and so choose to
prohibit the private use of the 5.60-5.65 GHz sub-band. Consequently BWA vendor
equipment must “notch out” this particular 50 MHz sub-band from any commercial use.
Canopy products automatically account for this when an operator chooses a Regional
Setting.
Figure 3 shows the locations of these Canadian weather radar sites; note that range of
these extend into USA territory where use of 5.60-5.65 GHz is not prohibited explicitly
(but may trigger the FCC’s DFS rules). Canopy operators located sufficiently close to
USA’s national borders must comply with any Canadian regulation regarding DFS and
channel notching.
A more complete description of the Canadian weather radar network can be found at
http://en.wikipedia.org/wiki/Canadian_weather_radar_network.

Figure 3 Locations of Canadian C-band weather radar
Several technologies are not a DFS issue. For example, police traffic radar uses
frequencies well above Canopy’s unlicensed bands. Microwave ovens operate in the
unlicensed 2.4 GHz band.
Motorola strongly recommends adequate spectrum analysis and channel planning prior
to deployment to ensure the best operating environment. This is discussed in greater
detail below.
2.4 Using Canopy for Site Planning to avoid DFS Events

Canopy products support a “spectrum analyzer” mode (available today on the FSK
Canopy products and to be available in early 2Q2008 on 5.4 GHz OFDM product). This
spectrum analyzer senses received signal strength and displays these strengths in a bar
graph-type display. The goal of Canopy’s spectrum analyzer is to indicate ordinary radio
interference.
Although the current Canopy spectrum analyzer is not intended to detect the energy in a
very short radar pulse, it may. Both Motorola and customer testing indicate that it, in fact,
does detect much of the radar energy present.
Figure 4 shows a Canopy 5.4 GHz FSK spectrum analyzer screen. Notice that the
spectrum captured ranges from 5.47 to 5.85 GHz meaning both the 5.4 GHz band and
5.7 GHz band. A Canopy 5.4 GHz product is limited to 5.47 to 5.725 GHz (channel
centers from 5.495 to 5.705 GHz).
The spectrum is “captured” by pressing an “enable” button. The current reading is

displayed as a green bar (at 5 MHz intervals over the received spectrum band) with
longer bars indicating higher received power. Repeated pressing of the “enable” button
(or doing a web page refresh) refreshes the display with a new reading. The maximum
received power is retained in the form of a “tick mark” color either yellow or red
(depending on the received power level).
While not explicitly designed to capture radar-type signals the spectrum analyzer seems
to indicate maximum powers.
For example, in Figure 4, the frequencies from 5.605 to 5.625 GHz all show the red ticks
at the extreme right side indicating strong reception. These frequencies are typical of
current C-band weather radar operation. Note these high power ticks are shown even if
the “bar” establishing them is not.
By employing the Canopy spectrum analyzer, an operator may conclude that any
additional 5.4 GHz band Canopy deployment should avoid these two 5.4 GHz sub-bands:

5.44-5.5 GHz and .5605-5.625 GHz. Note this reduces the available 5.4 GHz band by
about 80 MHz, leaving about 175 MHz for new Canopy channel plan usage.
Recall that even this limitation leaves still much more available bandwidth than the entire
5.7 GHz band (125 MHz).
Of course, the safest approach to understand the potential for radar interference in the
5.2 GHz and 5.4 GHz bands is simply to deploy an AP in the intended operating area to
determine whether actual DFS detection is experienced.
To that end, Motorola recommends purchasing a DFS-band Access Point (AP) and
deploying it in the intended site(s), in multiple directions and on multiple channel
frequencies, over a period of time. A period of one week is strongly suggested.
This pre-service AP deployment can log DFS events by direction and channel frequency
and so, after some period of time (e.g. one week) can provide the Canopy operator with a
level of confidence concerning the tested channel frequencies and sites.
Of course even this testing is not definitive as the DFS environment is subject to change
over time, but this pre-service testing is a low cost and effective way to determine the
viability of reliable service in the 5.2 GHz or 5.4 GHz bands.

Figure 4 Example 5.4 GHz Spectrum Analyzer Result

3.0 Canopy’s Implementation of DFS
It is not the purpose of this Deployment Guide to substitute for the latest Canopy System
User Guide or Release Notes. Rather, this guide is intended to explain the technical
aspects of DFS for general Canopy operation and offer guidelines to maximize
performance.
In this section Canopy’s implementation of DFS is described at a high level. This DFS
description is applicable to both “regular” 20 MHz and 25 MHz channel single carrier
(FSK) Canopy and the OFDM-based 10 MHz channel 5.4 GHz Canopy. The only DFS
distinction between the two Canopy product lines is the narrower channel of the OFDM-
based Canopy which makes channel planning more flexible.
Canopy’s SM-Lite currently supports both the FCC and ETSI DFS rules. The operator
needs to choose the proper region code to enable the proper DFS functionality.
Currently Canopy’s DFS operation is dependent upon geographic region as national DFS
rules require. In Canopy Release 8.2 AP the region is configured in Configuration →
General → Regional Setting webpage as shown in Figure 5; dropdown menu options are:
Other, United States, Canada, Europe, Brazil, Australia, Russia, and None. Selecting the
factory default None results in a message “please select a valid region code.” An
administrator is required by local law to select the correct Regional Setting.
Figure 5 Screen capture of DFS Regional Settings menu.
This Regional Setting configuration will also automatically block channels as required by
that region or nation as discussed earlier (e.g. 5.6-5.65 GHz channel frequencies in
Canada and Australia).

Note each Canopy AP in a cluster is an independent DFS-capable entity and so each
must be individually configured for DFS. There is no communication between or among
Canopy APs concerning DFS.
In general a Canopy device has the ability to “listen” for the specific radar signal profile,
and, if detected, change transmission to an alternate channel as regulation requires. The
Canopy operator must pro-actively select these alternate channels.
Consequently, it is strongly recommended that the Canopy operator have a “DFS

channel plan” (discussed below). 2
3.1 Canopy Release 8.2 FCC DFS Operation

A Canopy DFS-configured AP working channel is always in one of four states. The
particular state is shown on the unit’s Home → General page as “DFS”. The states
possible are:
• “Idle” (if not registered to any other Canopy unit),

• “Checking Channel Availability Remaining Time n seconds” (listening for
radar upon reboot for the required 60 seconds),
• “Normal Transmit” (channel is being used and listening for currently undetected
radar),
• “Radar Detected Stop Transmitting for n minutes” (if an alternate channel is
not configured the unit will wait the required 30 minutes). Note: this state may be
avoided through pro-active per-service channel planning and spectrum analysis.
In FCC situations, if radar is detected and the AP’s or BHM’s primary channel frequency
is “shut down”; the set of sector SMs no longer “hear” the AP’s beacon signal so they
cease regular operation and enter a “pre-registered scan mode”. Naturally the customers
will not have service at this instant. However the SMs will soon “hear” the new beacon
signal on some alternate channel frequency (as configured on the AP by the network
operator) and so re-register automatically and so restore customer service. Note the
sector downtime is just over one minute in this case.
Consequently it is important that each SM in any particular AP sector be configured to

scan at least the three stipulated channel frequencies (primary and two alternatives). Of
course if the SMs were configured to scan all the channel frequencies (the default) that
would likely reduce re-registration time and potential interruptions to broadband service.
2
We confine discussion to the point-to-multipoint (PTMP) base station, but the same DFS rules apply to
Canopy BH10/BH20 operation (in the 5.2 and 5.4 GHz bands). Note, however, that the Canopy BHM must be
configured using the same menus associated with an AP.

3.1.1 Canopy FSK 5.4 GHz Band 20 MHz Channel Plan
To optimize network performance, the Canopy operator must have a “5.4GHz DFS
channel plan” in effect. Being 255MHz wide there is room for nine 20 MHz non-
overlapping channels on 25MHz centers (as recommended for “2x” operation)..
Note: Eleven non-overlapping channels are available on 20 MHz centers for standard
“1X” Canopy operation.
The Canopy recommended nine channel center frequencies are shown in Figure 6. The
colored channels impinge on the 5600-5650 MHz “weather radar” notch.
Figure 6 20 MHz channel plan potential given 25 MHz centers
A channel plan may include all of these channels or a subset if DFS testing indicates
certain channel centers should be avoided due to radar interference.
In general all channel center frequencies infringing between 5.600 GHz and 5.650 GHz
cannot be deployed in Canada and Australia. Thus only six channel centers are
recommended in Canada and Australia: 5495, 5520, 5545, 5570, 5670, and 5695 MHz.
A six-sector Canopy 5.4 GHz base station is normally configured for a 3x2 channel reuse
plan (ABCABC) using three stipulated primary channels; and leaving the other six non-
overlapping channels for DFS alternatives.
A sample Canopy 5.4GHz ABCABC channel plan is show in Figure 7 As stated above all
the nine non-overlapping 20 MHz channels on 25 MHz channel centers are used in this
plan.
In the DFS channel plan illustrated, each of the six base station APs has two DFS
alternatives, and each alternatives are distinct for each of the three primary channel
frequencies. In this case, multiple AP’s could detect a radar signal and continue
operation in an alternate channel ensuring more continuous operation.
This channel plan means that when the primary channel detects radar, it shuts down the
current frequency and enters a one-minute “listen” on the first alternate “DFS1.” By
placing this alternate as “distant” as possible from the now silenced channel frequency, it
is less likely to detect radar on the alternate channel. Consequently the customers being
served in this sector are “down” for only about one minute before the alternate frequency
is up. Note: the sector SMs are default configured to “scan” all the 5.4 GHz channel
frequencies, and so will re-register quickly to the new DFS1 alternate channel frequency.

Figure 7 A suggested Channel Plan for 5.4 GHz FSK Canopy
Note also that the channel center frequency separation remains at 25 MHz in the DFS1
and DFS2 columns in Figure 7. Thus “co-channel” interference is even less likely than
among the primary channels. In Canopy FSK devices a “schedule whitening”
configuration mitigates this interference (discussed in the Best Practices section).
Note that the configuration of these alternate channel frequencies must be done
independently for each AP/BHM. Consequently great care must be taken when
configuring all the AP’s of a 5.4 GHz base station cluster.
These DFS alternative channel stipulations are configured on the AP/BHM’s

Configuration → Radio → Radio Configuration as “Alternate Frequency Carrier 1” and
“Alternate Frequency Carrier 2”. Of course the primary channel frequency is also
stipulated as “Radio Frequency Carrier”.
Each of these alternates has a dropdown menu of all possible 5.4GHz channel center
frequencies. After selecting the primary channel frequency center, the two alternate
frequencies can be configured.
Many other channel plan schemes can be devised for example to account for “weather
notching” when 5600-5650 MHz must be avoided. Figure 8 illustrates a “one alternate
DFS channel” plan suitable for Canada and Australia (or elsewhere by choice). Note the
second alternate DFS is left “not applicable.”
Figure 8 DFS channel plan for Canada and Australia

3.1.2 Canopy 5.4 GHz Band OFDM 10 MHz Channel Plan
Channel planning for 5.4 GHz band Canopy OFDM deployment is even more flexible as
the OFDM radio employs a 10 MHz channel bandwidth. Testing and experience has
shown that 10 MHz channel center separation avoids co-channel interference, even
when in the “3x” (64 QAM modulation) mode. This is possible as the outer subcarriers
are “nulls” (not used). Note that Canopy 5.4 GHz OFDM has 90° sectors (so four per
base station).
Consequently Motorola recommends the 5.4 GHz band channel centers shown in Figure
9 for OFDM deployment:
Figure 9 Canopy 5.4 GHz OFDM 4-sector recommended channel centers
Canopy allows selecting channel centers at 5 MHz intervals; however, Motorola

recommends a 5 MHz “guard” at the lower band extreme to avoid licensed spectrum.
Consequently the recommended channel centers are offset by 5 MHz, and on 10 MHz
centers, so providing a total of 24 non-overlapping channel centers shown in Figure 9.
Note the extreme high end of the 5.4 GHz band abuts the unlicensed “5.7” GHz band so
no explicit guard is needed.
Motorola suggests that Canopy OFDM operators do the same pre-deployment DFS radar
detection as described above. After testing is completed for all four sectors, an OFDM
channel plan can be produced for a 2x2 channel reuse as shown in Figure 10.

Figure 10 OFDM 10 MHz Channel Plan avoiding 5600-5650 MHz
Each channel is offset 60 MHz to avoid any co-channel interference. Note also this
particular OFDM 10 MHz channel plan avoids the weather radar notch so is applicable
worldwide.
In general, with a 2x2 channel reuse plan and 10 MHz channel width on 10 MHz channel
centers, the 5.4 GHz band (of 255 MHz width) has great flexibility. The particular channel
plan illustrated in Figure 10 is but one of many that could have been devised.
Figure 11 ABCD channel plan for 5.4 OFDM; avoids weather notch
Alternately a Canopy operator may opt for an ABCD channel plan; this avoids having any
potential “back to back” self-interference issues. Figure 11 shows such a channel plan.
Note how the channel centers are spaced such that, even if a DFS event forces channel
switching, the adjacent sectors are sufficiently far apart.
A good practice is to select channel center frequencies that are spread over the complete
band thereby satisfying the FCC need for “uniform channel spreading.”
3.2 Canopy Release 8.2 EU/UK Operation

Since Release 8.1 software Canopy has supported the ETSI EN 301 893 V1.2.3, the
EU’s harmonized radio standard for unlicensed devices operating in the 5150 – 5350
MHz and 5470 – 5725 MHz frequency bands. Additionally the UK Interface Requirement
IR2007 requires DFS in the 5.7 GHz band as well; this too has been supported since
Release 8.1.

EU-bound Canopy units will be enforcing the latest ETSI 1.3.1 DFS specification as
required after March 2009. Consequently this DFS is applicable to Canopy 5.4GHz and
5.7GHz bands. DFS applies to AP/SM and to BHM/BHS.
All of these standards are automatically configured for Canopy products by choosing the
correct Regional Setting.
This section emphasizes the differences in Canopy DFS operation in the EU/UK and
operation in the US.
Primarily this difference consists of the Canopy SM and BHS playing an active – rather
than passive – role in DFS operation.
Additionally a primary and two alternate channel frequencies must be configured, again
as per the Canopy FCC DFS configuration.
EU/UK SM DFS Operation
The EU/UK SM is different in that, like the AP, the SM actively “listens” for a radar signal.
Note the ramification is that an AP sector could be operating on a particular channel
frequency (because its particular AP does not detect radar from its location) but one or
more of its sector SMs does detect radar on that same channel frequency.
In the EU/UK the SM scans through its configured list of scan frequencies; these SM
frequencies should correspond to those configured DFS channel frequencies configured
into its AP.
However, prior to “listening” for an AP’s beacon, the SM must enter a one-minute “listen”
mode to determine if a radar signal is present on that particular channel. If radar is not
detected after one minute the SM attempts to register (by transmitting).
If, instead, radar is detected then that particular channel must enter a 30-minute “lock
out” period. At that point the SM can immediately switch to another one of its scanned
frequency set, and listen one minute there. If radar is not detected then the SM will listen
for an AP beacon and, if found, register and enter a normal operational state with the AP
and SM now operating on the same alternate channel.
If radar is detected on its alternate channel, then the SM “locks out” this channel and
proceeds to scan again into its pre-selected frequency list.
Caveat: It is important to note that in the rather unlikely event that the SM (or BHS)
experiences a DFS event and the AP (or BHM) does not, the SM (or BHS) will have
switched to an alternate channel and the AP (or BHM) would still be operating on its
original primary channel. If that happens, the SM (or BHS) would not be able to register
to its AP (or BHM). In this case, the particular SM would have to wait to complete its 30-
minute lock-out time and then re-register to the AP’s primary channel (assuming that this
channel was radar-free). Important: Given that the AP (or BHM) and associated SM’s (or
BHS) are most commonly located within 2 miles of each other, it is somewhat unlikely
that this scenario would occur.*
3.3 Summary of DFS Recovery Times
In “FCC nations” the DFS detection and recovery times are as follows:
• 1.5 minutes for SM to resume after its AP has a DFS detection

• 1.5 minutes for BH link to resume after its BHM has a DFS detection
This time interval is due to the mandatory 1 minute “listening” time (on the DFS alternate
channel frequency) followed by the approximate scanning and re-registration time of the
impacted SMs and BHS.
In “ETSI nations” DFS detection and re-registration has an additional complication,

namely that the Canopy SM or BHS cannot initiate a channel move. This was by design
since it is one SM of many in its AP sector (this is mimicked by the BHS relative to its
BHM) and so it must attempt to re-register on the AP’s (or BHM’s) channel frequency.
Note if an ETSI AP or BHM detects a DFS event, it must listen for 1 minute before
moving channels and must additionally have the SM or BHS listen for 1 independent
minute.
These are likely recovery times for 5.4 GHz Canopy equipment in ETSI DFS regions:
• 2.5 minutes for the SM to resume after its AP has a DFS detection
• 3.5 minutes for the BH link to resume after the BHM has a DFS detection
(requires two channel availability checks)
*Recovery times for ETSI regions are as follows should an SM or BHS experience a DFS
event and the AP or BHM does not as described at the end of Section 3.2:
• 31.5 minutes for the SM to resume after SM DFS detection
• 32.5 minutes for the BH link to resume after the BHS has a DFS detection
Again, this is a somewhat unlikely scenario but is possible.
3.4”False Positive” Mitigation
Canopy’s DFS detection is in effect a “sampling” mechanism and as such has an innate
“failure” probability. As an operator, you would like to avoid any “false positive”
detections in order to maximize system performance.
Schedule whitening (discussed earlier) can help to avoid self-interference and “false
positive” triggers caused by other Canopy equipment.
Motorola has also attempted to “design out” error possibilities and so reduce “false
positives” to close to “zero” and continues to reduce this risk overtime through software
upgrades. Therefore, operators are strongly encouraged to upgrade to the latest version
of software available. Motorola advises Canopy operators that it is impossible to
eliminate “false positive” detections altogether and that all BWA equipment vendors are
subject to this caveat.

3.4 Prizm EMS Management of DFS
Prizm 3.1 supports Release 8.2 features such as DFS. In this section an example of
Prizm’s ability to inform a Canopy operator of DFS detection events is illustrated. Details
are fully described in the Prizm Users Guide.
The Canopy devices Management Information Bases (MIBs) now include the additional
DFS-related information. This allows the Prizm-based management of DFS remotely via
Simple Network Management Protocol (SNMP).
In particular Canopy and Prizm have four DFS-related MIB entries, namely:
• dfsStatus
• dfsStatusAlt1
• dfsStatusAlt2
• dsfStatusPrimary.
Two “traps” are defined, namely:
• whispRadarDetected
• whispRadarEnd
In particular the use of Prizm (using SNMP) allows the operator to be alerted to DFS
events. This allows the operator to see a complete DFS log for all Canopy equipment
triggering DFS events so avoids the need to “visit” every Canopy device individually via
its web GUI interface. Prizm displays a complete log of all past DFS events, including the
shift to alternative channel frequencies, each completely time and date stamped.
Figure 12 Screen capture of DFS-related Prizm Alerts
Figure 12 shows a screenshot of a Prizm sequence of DFS Alerts. Note the date and
time stamp and the channel frequencies (in MHz). Also note that the most current Alert is

at the top; for example the second line from the top shows a “Radar Detected” SNMP
trap at 1:32 (a “warning” happening on the 5625 MHz channel) followed by a “Radar
Ended Back to Normal Transmit” SNMP trap (the top entry also at 1:32) “info” message
indicating the switch to channel center 5630 MHz. This confirms that the channel has
moved successfully. This “all DFS” Alerts is due to searching all Alerts for the word
“Radar” as shown at the bottom of Figure 12.
Importantly SNMP traps are said to be asynchronous, that is they are unilaterally sent
from the Canopy device to the Prizm server (without a Prizm server initiated “poll” of the
devices). Therefore, the operator can receive an e-mail alert that a DFS event has
occurred in “real time”.
4.0 Summary
With proper channel planning, site surveys and configuration, DFS events should be rare
to non-existent.
Based on Motorola’s experience and that of its customers, we can offer the “best
practices and considerations” outlined in Section 2.2.
The impact of DFS can be minimized by a “pre-deployment” check of the 5.4 GHz bands
by purchasing one FSK-based SM and utilizing its spectrum analyzer capability.
Additionally, purchasing an appropriate Canopy AP and probing for DFS events (as per
Section 2.4) can further help you determine the likelihood of a successful Canopy
deployment in the 5.4 GHz band.
The Motorola Canopy product line is compliant with all known DFS regulatory
requirements in all applicable nations. Canopy’s Prizm EMS supports configuring
Canopy devices remotely via SNMP for proper DFS operation and event management.
From a regulatory standpoint, DFS rules in the unlicensed spectrum are an operational
fact. Fortunately the 5.4 GHz band is wider than the 5.2 GHz and 5.7 GHz bands
combined which offers operators many options when navigating DFS compliance. This
provides unlicensed BWA operators the business opportunity to profit as never before in
newly available, uncongested spectrum.

Appendix A Additional DFS Details
A.1 Selected DFS Terminology
The FCC adopts special terms in specifying DFS. Here we introduce a subset of these
terms which will be employed in this Technical Brief.
Master Device: A U-NII device operating in Master Mode.
Master Mode: Operating mode in which the U-NII device has the capability to transmit
without receiving an external control signal and can perform Network Initiation.
Client Device: A U-NII device operating in Client Mode.
Client Mode: Operating mode in which the transmissions of the U-NII device are under
control of the Master Device. A U-NII device operating in Client Mode is not able to
initiate a network.
Channel Availability Check: A DFS function that monitors a Channel to

determine if a Radar Waveform above the DFS Detection Threshold is present.
Channel Availability Check Time: The period of time during which a Channel
Availability Check is performed.
Channel Move Time: The time to cease all transmissions on the current Channel
upon detection of a Radar Waveform above the DFS Detection Threshold.
In-Service Monitoring: A DFS function that monitors the Operating Channel for
the presence of a Radar Waveform above the DFS Detection Threshold.
DFS Detection Threshold: The required detection level defined by a received

signal strength (RSS) that is greater than a specified threshold, within the U-NII
Detection Bandwidth.
Network Initiation: The process by which the Master Device sends control
signals to Client Device(s) that allow them to begin transmissions.
Non-Occupancy Period: The time during which a Channel will not be utilized
after a Radar Waveform is detected on that Channel.
Operating Channel: Once a U-NII device starts to operate on an Available

Channel then that Channel becomes the Operating Channel.
Radar Waveform: A Burst or series of Bursts designed to simulate a radar

signal.
U-NII Detection Bandwidth: The contiguous frequency spectrum over which a U-

NII device detects a Radar Waveform above the DFS Detection Threshold.
Uniform Channel Spreading: The spreading of U-NII device Operating Channels

over the 5250-5350 MHz and/or 5470-5725 MHz bands to avoid dense clusters
of devices operating on the same Channel.
Applicable Canopy APs, SMs, BHMs, and BHSs are, in operation, both a Master Station
and a Slave Station by the definitions above.

A.2 Outline of Conforming DFS Operation
The referenced FCC MEMORANDUM OPINION AND ORDER succinctly outlines DFS
operation for a Master Station (AP is USA/Canada but both AP and SM in EU and other
regions) as follows:
a) The Master Device will use DFS in order to detect Radar Waveforms with
received signal strength above the DFS Detection Threshold in the 5250 - 5350
MHz and 5470 - 5725 MHz bands. DFS is not required in the 5150 − 5250 MHz
or 5725 − 5825 MHz bands.
b) Before initiating a network on a Channel, the Master Device will perform a

Channel Availability Check for a specified time duration (Channel Availability
Check Time) to ensure that there is no radar system operating on the Channel,
using DFS described under subsection a) above.
c) The Master Device initiates a U-NII network by transmitting control signals that
will enable other U-NII devices to Associate with the Master Device.
d) During normal operation, the Master Device will monitor the Channel (In-
Service Monitoring) to ensure that there is no radar system operating on the
Channel, using DFS described under a).
e) If the Master Device has detected a Radar Waveform during In-Service

Monitoring as described under d), the Operating Channel of the U-NII network is
no longer an Available Channel. The Master Device will instruct all associated
Client Device(s) to stop transmitting on this Channel within the Channel Move
Time. The transmissions during the Channel Move Time will be limited to the
Channel Closing Transmission Time.
f) Once the Master Device has detected a Radar Waveform it will not utilize the
Channel for the duration of the Non-Occupancy Period.
g) If the Master Device delegates the In-Service Monitoring to a Client Device,

then the combination will be tested to the requirements described under d)
through f) above.
For a Client Station (SM in USA/Canada) the mandated operation is as follows:
a) A Client Device will not transmit before having received appropriate control
signals from a Master Device.
b) A Client Device will stop all its transmissions whenever instructed by a Master
Device to which it is associated and will meet the Channel Move Time and
Channel Closing Transmission Time requirements. The Client Device will not
resume any transmissions until it has again received control signals from a
Master Device.
c) If a Client Device is performing In-Service Monitoring and detects a Radar

Waveform above the DFS Detection Threshold, it will inform the Master Device.
This is equivalent to the Master Device detecting the Radar Waveform and d)
through f) of the section above for master devices apply. Note: a Canopy SM
does not perform In-Service Monitoring.
d) Irrespective of Client Device or Master Device detection the Channel Move

Time and Channel Closing Transmission Time requirements remain the same.

A.3 DFS Timer Values stipulated by the FCC
Table 2 DFS Mandated Timer Values
Parameter Value
Non-occupancy period Minimum 30 minutes
Channel Availability 60 seconds
Check Time
Channel Move Time 10 seconds
See Note 1.
Channel Closing 200 milliseconds + an aggregate of 60 milliseconds
Transmission Time over remaining 10 second period.
See Notes 1 and 2.
U-NII Detection Minimum 80% of the U-NII 99% transmission power
Bandwidth bandwidth. See Note 3.
Note 1: The instant that the Channel Move Time and the Channel Closing
Transmission Time begins is as follows:
• For the Short Pulse Radar Test Signals this instant is the end of the Burst.
• For the Frequency Hopping radar Test Signal, this instant is the end of
the last radar Burst generated.
• For the Long Pulse Radar Test Signal this instant is the end of the 12
second period defining the Radar Waveform.
Note 2: The Channel Closing Transmission Time is comprised of 200

milliseconds starting at the beginning of the Channel Move Time plus any
additional intermittent control signals required to facilitate a Channel move (an
aggregate of 60 milliseconds) during the remainder of the 10 second period. The
aggregate duration of control signals will not count quiet periods in between
transmissions.
Note 3: During the U-NII Detection Bandwidth detection test, radar type 1 is used
and for each frequency step the minimum percentage of detection is 90 percent.
Measurements are performed with no data traffic.
A.4 Radar Waveform Profiles Detected

In is not necessary to describe in detail the radar waveforms that must be detected, nor
the details of the testing rules. However a succinct stipulation is provided in this
subsection.
The FCC requires DFS detection for four types of Short Pulse radar waveforms (types 1-
4), one type of Long Pulse radar waveform (type 5), and one type of Frequency Hopping
radar waveform (type 6). These are numbered respectively in Table 3 below.
Testing requires the Pulse Widths be stepped randomly in 1µs intervals, along with other
stipulations not necessary to this overview.
We remind the reader that any detection scheme is subject to two kinds of errors:
1. False positive: Detecting a signal when that signal is not present.
2. False negative: Not detecting a signal when that signal is present.

Of course an implementation goal is to reduce both error occurrences to zero probability
but this is not possible.
Note in the first case the device’s radar interference “falsely” continues when it should be
terminated. In the second case the device’s operation is “falsely” terminated when no
radar interference is occurring.
The FCC’s and EU’s rules concerning these error occurrences are met by Canopy.
Table 3 Radar Types and Characteristics.
Radar Type Pulse Pulse

Widths (µs) Repetition
Interval (µs)
1 1 1428
2 1-5 150-230
3 6-10 200-500
4 11-20 200-500
5 50-100 1000-2000
6 1 333
Note that this description of the FCC DFS rules only stipulate that a device detects the
prescribed radar signals and what must then be accomplished. The FCC does not
specify how or even what a vendor should do in order to implement the requirement.
Consequently Canopy’s current DFS deployment may not be identical to other vendors.
In addition Motorola may subsequently change its DFS deployment as experience
dictates.
A connectorized 5.4 and 5.7-GHz module provides an Antenna Gain parameter. When
you indicate the gain of your antenna in this field, the DFS algorithm (where applicable,
as in the UK) calculates the appropriate sensitivity to radar signals, and this reduces the
occurrence of false positives (wherever the antenna gain is less than the maximum).

A.5 Detailed DFS Requirements – FCC and ETSI
Figure 13 Summary of FCC DFS requirements
Figure 13 provides a summary of the FCC DFS requirements. In the FCC context a
“master” is a Canopy Access Point (AP) and Backhaul Master (BHM), and a “slave” is a
Canopy Subscriber Module (SM) and Backhaul Slave (BHS).
In the European Union (EU) the European Technical Standards Institute (ETSI) standard
EN 301 893 V1.2.3, the EU’s harmonized radio standard for unlicensed devices operating
in the 5150 – 5350 MHz and 5470 – 5725 MHz frequency bands, was the first standard to
require DFS. Canopy will support the newer ETSI 1.3.1 DFS specification as required
after March 2009.

Figure 14 Summary of ETSI DFS requirements
Figure 14 shows a summary of the ETSI DFS requirements. Again the “master” is a
Canopy AP (and BHM) and a “slave” is a Canopy SM (and BHS). This is Table 5 in the
ETSI EN 301893 document stipulating DFS. In the ETSI context a Canopy SM is a
“slave with radar detection” by necessity and design.
Additionally the UK Interface Requirement IR2007 requires DFS in the 5.7 GHz band as
well. Norway requires 5.7 GHz band DFS as defined by Annex 1 of ITU-R
Recommendation M.1652 / EN 301 893. Brazil requires 5.4 GHz band DFS. Other
relevant documents are issued by: WRC-03, ITU-R Recommendation M.1652, National
Telecommunications and Information Administration (NTIA).

Appendix B DFS Regulatory Domain by Country
DFS regulation is stipulated by the USA’s Federal Communications Commission (FCC)
or the European Technical Standards Committee (ETSI).
For purposes of DFS countries divide into two groups:
“ETSI states”: Armenia, Austria, Azerbaijan, Belgium, Belize, Bolivia, Brazil, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Georgia, Germany,
Hungary, Iceland, Ireland, Italy, Liechtenstein, Lithuania, Luxembourg, Monaco,
Netherlands, New Zealand, Norway, Poland, Portugal, Slovak Republic, Slovenia, South
Africa, Spain, Sweden, Switzerland, Trinidad & Tobago, Tunisia, Turkey, United
Kingdom, and Venezuela.
“FCC states”: Australia, Canada, Columbia, Dominican Republic, Guatemala, Hong

Kong, Macau, Mexico, Panama, Philippines, Puerto Rico, United States, and Uzbekistan.
This listing is not guaranteed to be correct and is subject to unilateral national change.

Appendix C References
http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-06-96A1.pdf (FCC “rule and order”)
http://www.i4shop.net/cz/iobchod/Img/5GHz/en-301893v010203p.pdf (ETSI “rule and

order)
http://en.wikipedia.org/wiki/Weather_radar (overview: use of weather radar)
http://www.ieee802.org/18/Meeting_documents/2007_Nov/WFA-DFS-
Best%20Practices.pdf (weather radar background)
http://www.thomasregister.com/olc/53732509/rs04.htm (lists C-band radars)
http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/techops/spec
_management/engineering_office/rfb.cfm (lists all spectrum used in FAA-based aviation)

Appendix D 5.2 GHz Band 20 MHz Channel Plan
The 5.2GHz UNII-Lower frequency band is only 100MHz wide, sufficient for three non-
overlapping 20MHz channels as normally used by Single Carrier (SC) Canopy (a.k.a.
“FSK Canopy”). To implement a six-sector Canopy 5.2GHz base station deployment
using a 3x2 channel reuse plan (ABCABC; see Figure 15), the deployment would
exercise the “30 minute” shutdown rule when a DFS event occurs as there are no
alternate unused channels available. The Canopy User Guide recommends 5.2 GHz
channel centers 5275 MHz, 5300 MHz, and 5325 MHz respectively; note these channel
centers have a 25 MHz separation.
Alternatively, the 5.2 GHz Canopy six-sector base station may employ a 2x2 channel
plan (ABABAB) and specify each sector switch to the alternative channel frequency C
upon radar signal detection. Motorola testing suggests that this 2x2 channel plan does
work satisfactorily.
Note that if an adjacent A and B sectors both detect a DFS event then they both switch to
the same DFS alternate; this is unworkable. However, if such a channel plan is not
deployed a DFS detection means a 30 minute sector shutdown.
Figure 15 A suggested 5.2 GHz DFS channel plan

Appendix E List of USA TDWR Sites
Source: TDWR_SPG_ICD_v43.pdf

-
Motorola, Inc. www.motorola.com

The information presented herein is to the best of our knowledge true and accurate. No warranty or guarantee expressed or implied is made
regarding the capacity, performance or suitability of any product. MOTOROLA and the Stylized M Logo are registered in the U.S. Patent and
Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2008

Canopy DFS Deployment Guide - Final

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Canopy DFS Deployment Guide - Final

Uploaded by

Copyright:

Available Formats

Technical Brief

Canopy® Dynamic Frequency

Issued: February 2008

Please refer to the Canopy System User Guide for:

◦ Personal safety guidelines in Preventing Overexposure to RF Energy

© 2008 Motorola, Inc. All rights reserved.

List of Figures .................................................................................................................................. 4

Canopy – Overview of Dynamic Frequency Selection Deployment Guide ..................................... 5

2.0 Definition of Dynamic Frequency Selection............................................................................... 5

2.1 Relationship to Transmission Power Control......................................................................... 6

2.2 Motorola’s Recommended Best Practices............................................................................. 6

2.3 Likely Sources of DFS-type Signals ...................................................................................... 9

3.0 Canopy’s Implementation of DFS............................................................................................ 15

3.1 Canopy Release 8.2 FCC DFS Operation........................................................................... 16

3.1.1 Canopy FSK 5.4 GHz Band 20 MHz Channel Plan.......................................................... 17

3.2 Canopy Release 8.2 EU/UK Operation ............................................................................... 20

3.3 Summary of DFS Recovery Times ...................................................................................... 21

3.4”False Positive” Mitigation..................................................................................................... 22

3.4 Prizm EMS Management of DFS......................................................................................... 23

4.0 Summary ................................................................................................................................. 24

Appendix A Additional DFS Details .............................................................................................. 25

A.1 Selected DFS Terminology.................................................................................................. 25

A.2 Outline of Conforming DFS Operation ................................................................................ 26

A.3 DFS Timer Values stipulated by the FCC ........................................................................... 27

A.4 Radar Waveform Profiles Detected..................................................................................... 27

A.5 Detailed DFS Requirements – FCC and ETSI .................................................................... 29

Appendix B DFS Regulatory Domain by Country.......................................................................... 31

Appendix D 5.2 GHz Band 20 MHz Channel Plan ........................................................................ 33

Appendix E List of USA TDWR Sites ............................................................................................ 34

Technical Brief: Canopy DFS Deployment Guide Page 3

Figure 2 A sample map of TDWR airport sites circa 2001. 10

Figure 3 Locations of Canadian C-band weather radar. 12

Figure 4 Example 5.4 GHz Spectrum Analyzer Result 14

Figure 5 Screen capture of DFS Regional Settings menu. 15

Figure 6 20 MHz channel plan potential given 25 MHz centers. 17

Figure 7 A suggested Channel Plan for 5.4 GHz FSK Canopy. 18

Figure 8 DFS channel plan for Canada and Australia. 18

Figure 9 Canopy 5.4 GHz OFDM 4-sector recommended channel centers. 19

Figure 10 OFDM 10 MHz Channel Plan avoiding 5600-5650 MHz. 20

Figure 12 Screen capture of DFS-related Prizm Alerts. 23

Figure 13 Summary of FCC DFS requirements. 29

Figure 14 List of USA TDWR Sites Error! Bookmark not defined.

Technical Brief: Canopy DFS Deployment Guide Page 4

This document is intended to inform and provide guidance to Canopy equipment

2.0 Definition of Dynamic Frequency Selection

Technical Brief: Canopy DFS Deployment Guide Page 5

In addition, DFS deployment must provide, on aggregate, a Uniform Spreading of the

2.1 Relationship to Transmission Power Control

Additional technical details of DFS are provided in Appendix A.

2.2 Motorola’s Recommended Best Practices

Technical Brief: Canopy DFS Deployment Guide Page 6

4. Devise a channel plan along the lines described in Section 3.

5. Weather radar that is DFS sensitive is confined to a narrow band of spectrum

Technical Brief: Canopy DFS Deployment Guide Page 7

*“Schedule Whitening” is a transmission technique that changes the energy pattern of

Whitening is enabled on the Configuration → Radio page of a regular Canopy AP or

Figure 1. Schedule Whitening on Canopy Configuration Radio tab

Technical Brief: Canopy DFS Deployment Guide Page 8

2.3 Likely Sources of DFS-type Signals

Table 1 shows the technical properties of TDWR.

Technical Brief: Canopy DFS Deployment Guide Page 9

Figure 2 A sample map of TDWR airport sites circa 2001

Example vendors of C-band weather radars are PulseSystems (www.pulsesystems.com),