October, 2001 doc.: IEEE 802.15-01/480r0

Submission

Integrated Programmable Communications, Inc. and Texas Instruments, Inc.Slide 1

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

Submission Title: Request for Clarification of Discrepancies between Doc. 01/435 and TG2-Adopted AFH MechanismDate Submitted: October 15, 2001

Source: (1) YC Maa, HK Chen, and KC Chen (2) Anuj Batra, Kofi Anim-Appiah, and Jin-Meng Ho

Company: (1) Integrated Programmable Communications, Inc. (2) Texas Instruments, Inc.Address: (1)Taiwan Laboratories Address: P.O. Box 24-226, Hsinchu, Taiwan 300

(2) 12500 TI Boulevard, Dallas, TX 75243TEL(1) +886 3 516 5106, FAX: +886 3 516 5108, E-Mail: {ycmaa, hkchen, kc}@inprocomm.com (2) +1 214 480 4220, FAX: 972 761 6966, E-Mail: {batra, kofi, jinmengho}@ti.comRe: []Abstract: This presentation shows the discrepancies of Doc. 01/435 and TG2-Adopted AFH Mechanism, and requests a clarification thereof.

Purpose: Submission for requesting clarification of discrepancies with TG2-Adopted AFH 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.

October, 2001 doc.: IEEE 802.15-01/480r0

Submission

Integrated Programmable Communications, Inc. and Texas Instruments, Inc.Slide 2

Request for Clarification of Discrepancies between Doc. 01/435 and TG2-Adopted AFH

Mechanism

YC Maa, HK Chen, and KC ChenIntegrated Programmable Communications

Anuj Batra, Kofi Anim-Appiah, and Jin-Meng HoTexas Instruments

October, 2001 doc.: IEEE 802.15-01/480r0

Submission

Integrated Programmable Communications, Inc. and Texas Instruments, Inc.Slide 3

Adaptive Frequency Hopping in May01 Meeting

As mentioned in 01/255r0:

B. Treister, H. B. Gan, K. C. Chen, H. K. Chen, A. Batra, O. Eliezer,

Adaptive Frequency Hopping: A Non-Collaborative Coexistence Mechanism, (01/252r0)

It was passed 10/0/1 and adopted as TG2 AFH mechanism

October, 2001 doc.: IEEE 802.15-01/480r0

Submission

Integrated Programmable Communications, Inc. and Texas Instruments, Inc.Slide 4

Adaptive Frequency Hopping in Jul01 Meeting

A merged draft (01/366r1)

B. Treister, K. C. Chen, A. Batra,

Clause 14.3 Adaptive Frequency Hopping was presented to TG2

TG2 recommended a merger of the remapping functions as well as other parts of the mechanism.

October, 2001 doc.: IEEE 802.15-01/480r0

Submission

Integrated Programmable Communications, Inc. and Texas Instruments, Inc.Slide 5

Adaptive Frequency Hopping after Jul01 Meeting

A merger of mode H and mode L (01/382r0) was presented by TI/IPC

Merged AFH Proposal (01/385r0, 01/386r0) was presented by Bandspeed

01/435r0 (ICR), 01/435r2, r3 (Standard and Fit Best ICR) were proposed by Bandspeed

October, 2001 doc.: IEEE 802.15-01/480r0

Submission

Integrated Programmable Communications, Inc. and Texas Instruments, Inc.Slide 6

Need for Clarification of Doc. 01/435

New proposals appear at a late stage of the standard drafting process.

Discrepancies seem to exist as compared to originally TG2-adopted AFH mechanism

Need to clarify these issues and decide if the original standard drafting process should include 01/435 and can go on schedule to finish the draft text, without violating current TG2 resolution

October, 2001 doc.: IEEE 802.15-01/480r0

Submission

Integrated Programmable Communications, Inc. and Texas Instruments, Inc.Slide 7

Doc. 01/435 vs. TG2 AFH (1) Is 01/435 proposal included in mode L of TG2 AFH? Is 01/435 proposal the same as mode H of TG2

AFH? How does 01/435 proposal fit into Structure of TG2

AFH? Does 01/435 proposal have same LMP information

exchange and synchronization mechanism of TG2 AFH?

Is 01/435 proposal easy to implement as a module like TG2 AFH?

Do Standard and Fit Best modes of 01/435 proposal have TG2 AFH’s low complexity feature?

October, 2001 doc.: IEEE 802.15-01/480r0

Submission

Integrated Programmable Communications, Inc. and Texas Instruments, Inc.Slide 8

Doc. 01/435 vs. TG2 AFH (2)

QoS Issue The length of bad window depends on the

underlying hopping sequence. 01/435 proposal can create much longer bad window for ACL or mixed SCO-ACL traffic.

01/435 proposal is unable to predict the position and length of each bad window

With QoS capabilities drastically reduced, can TG2 AFH’s “WLAN/WPAN performance be improved” be still valid?

October, 2001 doc.: IEEE 802.15-01/480r0

Submission

Integrated Programmable Communications, Inc. and Texas Instruments, Inc.Slide 9

Doc. 01/435 vs. TG2 AFH (3)

Synchronization Issue01/435’s GUD counter can change for each hop,

and it is a time-varying and time-critical parameter. GUD needs to be synchronized by some scheme.

In TG2 AFH, LMP message is used for synchronization

01/435’s GUD counter cannot be transmitted through the LMP message since LMP cannot handle time-critical information.

October, 2001 doc.: IEEE 802.15-01/480r0

Submission

Integrated Programmable Communications, Inc. and Texas Instruments, Inc.Slide 10

Doc. 01/435 vs. TG2 AFH (4)

Synchronization Issue (Cont)Without proper GUD synchronization,

01/435 slaves cannot join AFH in the midway of AFH.

An AFH session can last from a few seconds to less than 30 seconds. Not allowing to join AFH in the midway could create bad user experience.

October, 2001 doc.: IEEE 802.15-01/480r0

Submission

Integrated Programmable Communications, Inc. and Texas Instruments, Inc.Slide 11

Conclusions

Proposals in Doc. 01/435r{0,2,3} need clarifying discrepancies with the TG2-adopted AFH mechanism, and 75% WG approval to justify its inclusion in the drafting process.

Otherwise, to avoid lengthy discussion and debate on Doc. 01/435 and to speed up the TG2 standard drafting process, the original track for drafting AFH clause should be restored.

October, 2001 doc.: IEEE 802.15-01/480r0

Submission

Integrated Programmable Communications, Inc. and Texas Instruments, Inc.Slide 12

Reference Documents 01252r0P802-15_Adaptive Frequency Hopping, a Non-collaborative

Coexistence Mechanism 01366r1P802_15_Clause 14.3 Adaptive Frequency Hopping 01382r0P802_15_Proposal for merging mode H and mode L of AFH 01385r0P802_15_Merged AFH Proposal 01386r0P802_15 _Clause 14.3 Adaptive Frequency Hopping 01435r0P802_15_ Adaptive Frequency Hopping - An instant channel

replacement approach 01435r2P802_15_Adaptive Frequency Hopping - An instant channel

replacement approach for both ACL and SCO 01435r3P802_15_Adaptive Frequency Hopping - An Simple Instant

Channel Replacement Approach for both ACL and SCO Links 01442r0P802_15_Comparison of TI-IPC's AFH Mechanism and

Bandspeed's ICR Proposal