Slide 1

1. Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution to comment #] Date Submitted: [May-10-2009] Source: [Vered Bar] Company: [Qualcomm] Address: [QUALCOMM, Incorporated, 5775 Morehouse Drive, San Diego, CA 92121] Voice: [], FAX: [], E-Mail:[vbar@qualcomm.com] Re: [] Abstract: [Comment resolutions.] Purpose: [To be considered in IEEE 802.15.3c standard] 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. Qualcomm Slide 1

2. 802.15.3b Association Flow Qualcomm

3. DEV finds best PNC TX direction from quasi-omni-beacon • DEV sends Association Req CMD frames in one of Association S-CAP in one of its TX omni-direction • Each association Req is sent with IACK mode. • Association Req includes best quasi-omni PNC TX toward the DEV using “response TX sector “ IE • PNC response with IACK to first Association Req it detects in association S-CAP in DEV response TX sector • If the DEV does not receive IACK, it will try to re-send Association Req CMD frames in another TX omni-direction • DEV applies the same backoff window per sweep before each association Req in association S-CAP or we make Association S-CAP slotted aloha with slot size of Req+2 default SIFS +IACK • After DME provided Association Response information, PNC should allocate CTA for DEV to complete association • PNC send association Response using response TX sector • Association Response includes PNC best RX quasi-omni-direction (response TX sector IE) • DEV sends second Association Req CMD frame only in one Association S-CAP • PNC can now allocate CTA for beam training and for data transmission 802.15.3c Association Procedure Qualcomm Slide 3

4. 802.15.3c Association Flow Qualcomm

5. DEV trying to access the medium in CAP, shallalways do so by sending long preamble followed by 8 bit Duration field, send in base rate protected with hamming 12`8 • DEV is allowed to send data frame in any MCS supported by the CAP Phy mode, using best direction over Regular CAP. Regular CAP Access Rules It is best to use CMS/HSI MCS0/ AV LRP Preamble for Regular CAP transmission Qualcomm

6. The start of a valid CMS/HSI MCS0/ AV LRP preamble sequence at a receive level equal to or greater than the minimum sensitivity for the CMS shall indicate medium busy with a probability of > 90% within 9 s. The receiver CCA function shall in all circumstances report medium busy with any signal 20 dB above the minimum sensitivity for the CMS/HSI MCS0/ AV LRP . If a DEV ( say DEV-1) wishing to initiate transfer detects a CMS/HSI MCS0/ AV LRP preamble during it’s listen-before-talk (backoff interframe space) period it refrains from transmitting and suspends it’s backoff counter according to the backoff algorithm. This device may also remain in receive mode, to obtain duration information and go to sleep mode for the duration of the frame (+ACK) transmission, to save power consumption. 802.15.3c CCA Qualcomm