1. <January 2002>
doc.: IEEE <02/139r0>
12/29/2018
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [Resolution to comment #]
Date Submitted: [May ]
Source: [Vered Bar]
Company: [Qualcomm]
Address: [QUALCOMM, Incorporated, 5775 Morehouse Drive, San Diego, CA 92121]
Voice: [], FAX: [],
Re: []
Abstract: [Comment resolutions.]
Purpose: [To be considered in IEEE c standard]
Notice: This document has been prepared to assist the IEEE P 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 P
Slide 1
Qualcomm
Chuck Brabenac, Intel Labs

2. 802.15.3c Association Procedure
12/29/2018
c Association Procedure
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 DEV best RX quasi-omni-direction IE
PNC response with IACK to first Association Req it detects in S-CAP in DEV best RX quasi-omni-direction
If the DEV does not receive IACK, it will try to re-send Association Req CMD frames in another TX omni-direction
DEV applies backoff after each association Req in association S-CAP
After DME provided Association Response information, PNC includes DEV Association Response Indication in Q-omni beacon and allocate CTA for DEV to complete association with PNC
PNC send association Response in allocated CTA
Association Response includes PNC best RX quasi-omni-direction 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
DEV always sends announce CMD to PNC over one association S-CAP, PNC always allocate CTA to communicate with DEV
Slide 2
Qualcomm

3. 802.15.3b Association Flow <January 2002>
doc.: IEEE c
12/29/2018
b Association Flow
Qualcomm
Chuck Brabenac, Intel Labs

4. 802.15.3c Association Flow <January 2002>
doc.: IEEE c
12/29/2018
c Association Flow
Qualcomm
Chuck Brabenac, Intel Labs

5. Regular CAP Access Rules
<January 2002>
doc.: IEEE c
12/29/2018
Regular CAP Access Rules
DEV trying to access the medium in CAP, shall always 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.
It is best to use CMS/HSI MCS0/ AV LRP Preamble for Regular CAP transmission
Qualcomm
Chuck Brabenac, Intel Labs

6. <January 2002>
doc.: IEEE c
12/29/2018
c CCA
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.
Qualcomm
Chuck Brabenac, Intel Labs