Adaptive Frequency Hopping

May 2001
doc.: IEEE 802.15-01/252r0
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: Adaptive Frequency Hopping, a Non-collaborative Coexistence Mechanism Date Submitted: 16th, May, 2001 Source: Bandspeed Inc, Integrated Programmable Communications, Inc., TI Dallas, TI - Israel Address: E-Mail: {h.gan, b.treister} @bandspeed.com.au, {kc,hkchen} @inprocomm.com, {orene, batra} @ti.com Re: Submission of a no-collaborative coexistence mechanism Abstract: [The documentation presents a non-collaborative coexistence mechanism - Adaptive Frequency Hopping. Purpose: [This is a submission to IEEE 802.15.2 of a Recommended Practice for a Non-collaborative Coexistence Mechanism. Notice: This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.
Submission Slide 1 Bandspeed, IPC, TI Dallas, TI Israel
May 2001
doc.: IEEE 802.15-01/252r0
Adaptive Frequency Hopping A Non-collaborative Coexistence Mechanism

Bandspeed IPC TI (Dallas) TI (Israel) (Bijan Treister, Hong Bing Gan et. al) (K.C Chen, H. K. Chen et. al) (Anuj Batra et. al) (Oren Eliezer et. al)
Submission
Slide 2
Bandspeed, IPC, TI Dallas, TI Israel
May 2001
doc.: IEEE 802.15-01/252r0
Structure of AFH (1)

RF input signal
Frequency synthesizer
Partition mapping Original hopping sequence generator
partition sequence
Hop clock
Submission
Slide 3
May 2001
doc.: IEEE 802.15-01/252r0
Structure of AFH (2)

Partitioning channels into good/bad channels
Possibly unused channels
Mode H:
Partition sequence are designed to support traffic
Mode L:
when the number of good channels are more than the required/desired number Using good channels only
Submission
Slide 4
May 2001
doc.: IEEE 802.15-01/252r0
Components of the AFH Mechanism

1. Device Identification and Operation mode 2. Channel Classification 3. Exchange of Channel Information 4. Initiate/Terminate AFH
5. Mechanisms of AFH
Submission
Slide 5
May 2001
doc.: IEEE 802.15-01/252r0
LMP Exchange verifying:
1. Device Identification and Operation mode (1)
Support of AFH and required mode of op. Command includes Nmin (minimum number of channels that must be used) Master
LMP_Support_AFH_Mode( ) LMP_not_accepted LMP_accepted
Slave
Submission
Slide 6
May 2001
doc.: IEEE 802.15-01/252r0
1. Device Identification and Operation mode (2)

These information is exchanged when a new slave
has joined the piconet. AFH mode
LMP_not_accepted means that slave does not use

adaptive frequency hopping mechanism Low power devices may only support a simplified replacement of bad channels LMP_accepted means that slave accepts using adaptive frequency hopping mechanism
Submission
Slide 7
May 2001
doc.: IEEE 802.15-01/252r0
2. Channel Classification (1)

Classification of the channels:
Good or Bad Possible extension in doc. 802.15-01/246r1 CRC, HEC, FEC RSSI
Packet Loss Ratio (PLR) vs. Channel If PLR is above threshold, declare a bad channel Slaves classifications data Transmission sensing Other techniques
Methods of classification include:
May 2001
doc.: IEEE 802.15-01/252r0
2. Channel Classification (2)

Increased speed of classification
Some links require that classification step is fast; Classification of N MHz wide channels;
A guilt by association method;

Larger bandwidth interferers detected faster;
NB: An SCO link may require that the classification is done quickly to avoid prolonged degradation of quality;
Option: continue classifying channels during AFH

May 2001
doc.: IEEE 802.15-01/252r0
3. Exchange of Channel Information

Master makes final decision on channel classification.
Good/Bad/Unused or Good/Bad (to be determined)
Master to Slave message

Good/Bad/Unused or Good/Bad (to be determined)
Slave to Master message [optional] Good/Bad indication only
Submission
Slide 10
May 2001
doc.: IEEE 802.15-01/252r0
4. Initiate /Terminate AFH (1)

Master
LMP_Adaptive_Hopping_Request ( ) LMP_Accepted
Slaves may or may not accept adaptive hopping
Slaves Slaves
LMP_Not_Accepted
LMP_Regular_Hopping LMP_Accepted
optional Re-classification of channels

May 2001
doc.: IEEE 802.15-01/252r0
4. Initiate /Terminate AFH (2)

LMP request to initiate:
Should carry extra parameters of the partition sequence in Mode H. The slave uses the new sequence after the success of this command The master knows which sequence to use for every slave. LMP request to terminate
AFH will also be terminated after loss of synchronization.

May 2001
doc.: IEEE 802.15-01/252r0
5. Mechanism of AFH
Mode H: Baseline Document: 802.15-01/246r1 Channels are classified into 2 groups: (dynamic classification)
Good channels (size = NG) Bad channels (size = NB = 79NG)
Define Nmin to be the minimum number of channels that a Bluetooth device must hop over. Depending on the relationship between Nmin, NG, and NB, only a portion of the previously defined groups need to be used:
Nmin NG: only use good channels in the HS (replace bad channels ~ Mode L) Nmin > NG: must use some or all of the bad, depends on Nmin
If Nmin < 79, need to only use only a portion of bad channels (NminNG) If Nmin = 79, must use all of the bad channels
When bad channels are used, grouping/pairing must be used. When bad channels are not used, grouping/paring does not need to be used, only replacement of bad channels.
May 2001
doc.: IEEE 802.15-01/252r0
Mode H: Partitions
In Mode H, use two partitions: Partition 1 is composed of the good channels (length = NG). Partition 2 is composed of the bad channels (length = NB). Let Nmin = min. frequencies defined by FCC and min. needed for frequency diversity. Nmin NG + NB 79 Note that it possible some of the channels are unused, i.e., there are not in either partition.
Submission
Slide 14
May 2001
doc.: IEEE 802.15-01/252r0
Mode H: Partition Sequence for ACL Link

Consider the following hopping sequence with fixed block lengths:
Good Channels
RG slots
Bad Channels
RB slots
Good Channels
RG slots
Bad Channels
RB slots
For an ACL link, the sequence is completely described by parameters RG and RB.
The equations for selecting RG and RB are give in next 2 slides. For this link, the partition sequence is binary (either 1 or 2). This sequence and the necessary parameters are then sent to each slave within the piconet.
Slide 15 Bandspeed, IPC, TI Dallas, TI Israel
Submission
May 2001
doc.: IEEE 802.15-01/252r0
Mode H: Pseudo-random mapping

Selected channel number of original hopping sequence (0~78)
Mod Nj Mapping table of this partition
Nj shifter signal Size of partition Good Current partition = j (from partition sequence) Bad
Channel Mapping:
Channel in the original hopping sequence

Good Good\Unused Bad \Unused Bad
Desired partition specified by the partition sequence

Good Bad Good Bad
action
Keep the same Mapping Mapping Keep the same Bandspeed, IPC, TI Dallas, TI Israel
Submission
Slide 16
May 2001
doc.: IEEE 802.15-01/252r0
Mode H: Enhanced SHA for SCO Links

Fundamental:
Two layer structure to modify hopping sequence. Pseudo-random mapping device. The idea of allocating good channels in the good partitions for the SCO link remains the same.
Features:
The partitioning is dynamic, as was done for the ACL link. An algorithm to generate the new partition sequence.
Advantages
Takes full advantage of the possibility that good channels may reside in the bad partition. Most effective for narrowband interference sources and possibly narrowband 802.11b signals. A unification for SCO and ACL (01/246r1)
May 2001
doc.: IEEE 802.15-01/252r0
Mode H: Partition Sequence Example

The resulting partition sequence:
Fame 0
s(l ) 1
Frame 1 2 2 1 2
Frame 2 2 1 2
Frame 3 1 1 2
Frame 4
s(l ) 2
Frame 5 2 2 1 2
Frame 6 1 1 2
Frame 7 2 1 2
Frame 8
s(l ) 2
Frame 9 2 1 1 2
Frame 10 2 1 2
These good MAUs are for a HV3 link
1 0
1 1
1 2
1 3
1 4
1 5
1 6
1 7
1 8
1 9
2 0
2 1
2 2
2 3
2 4
2 5
2 6
2 7
2 8
2 9
3 0
3 1
3 2
These good MAUs can be used for ACL link Submission Slide 18 Bandspeed, IPC, TI Dallas, TI Israel
May 2001
doc.: IEEE 802.15-01/252r0
Mapping of Mode L
When the channel is good and Nmin NG do not re-map the channel: When the channel is bad in the HS and a good channel is needed:
good channel
BluetoothS election Kernel
Quality?
bad channel Mod NG CLK_N
0 1 2 . . . 54 55 56
good channel bank

(channels 0 - 56 are good)
Submission
Slide 19
May 2001
doc.: IEEE 802.15-01/252r0
Example mapping of Mode L

Regular Bluetooth hopping sequence 20 60 53 62 55 66 6 64 8 68 57 70 59 74 10 72 12 76 23 60 53 62 55 66 24 64 25 68 57 70 59 74 26 72 27 76
Example of proposed 802.15.1 AFH sequence
Regular Bluetooth hopping sequence used when master addresses normal Bluetooth devices.
AFH used when master addresses proposed 802.15.1 Mode L devices.
May 2001
doc.: IEEE 802.15-01/252r0
Conclusion
Merges ideas of proposals:
An integrated AFH to handle different scenarios.

Easy to implement as a module. Voice without loss even under 802.11b interference backward compatible to legacy devices
Under current high power FCC regulations (Mode H)

01/246R1 as the baseline
Under current low power FCC constraints (Mode L)

00/367R1 as the baseline
Allows for FCC changes in the future as parameter changes in this mechanism.
May 2001
doc.: IEEE 802.15-01/252r0
Reference documents:
00367r1P802-15_TG2-Adaptive-Frequency-Hopping.ppt 01057r1P802-15_TG2-Selective-Hopping-for-Hit-Avoidance.ppt 01169r0P802-15_TG2-Adaptive-Hopping-for-FHSS-Systems.ppt 01082r1P802-15_TG2-Intelligent-Frequency-Hopping.ppt 01246r1P802-15_TG2-Merged IPC and TI Adaptive Frequency Hopping Proposal.ppt
Submission
Slide 22
May 2001
doc.: IEEE 802.15-01/252r0
Summary of the Coexistence Mechanism
Submission
Slide 23
May 2001
doc.: IEEE 802.15-01/252r0
1. Collaborative or Non-collaborative
Non-collaborative
2. Improved WLAN and WPAN performance

Significant performance improvement for both WLAN and WPAN
3. Impact on Standard
No changes or extensions to IEEE 802.11 standard. Few extensions to IEEE 802.15.1 Specifications to implement the mechanism
4. Regulatory Impact
Legal for all classes and scalable depending on regulatory rulings
5. Complexity
Low complexity
May 2001
doc.: IEEE 802.15-01/252r0
6. Interoperability with systems that do not include the coexistence mechanism

Fully interoperable, broadcast packets supported to some degree
7. Impact on interface to Higher layers

No impact on 802.11 interface to higher layers No impact on Bluetooth interface to higher layers.
8. Applicability to Class of Operation

Supports all the Bluetooth profiles
9. Voice and Data support in Bluetooth Supports both ACL (data) and SCO (voice) packets. 10. Impact on Power Management No impact, beneficial to power management

Adaptive Frequency Hopping

Uploaded by

Copyright:

Available Formats

Adaptive Frequency Hopping

Uploaded by

Document Information

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

Adaptive Frequency Hopping

Uploaded by

Copyright:

Available Formats

May 2001

doc.: IEEE 802.15-01/252r0

doc.: IEEE 802.15-01/252r0