1. <January 2002>
doc.: IEEE <02/139r0>
12/8/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. Comment Regarding Training over Beam Forming CTA
<January 2002>
doc.: IEEE c
12/8/2018
Comment Regarding Training over Beam Forming CTA
Comment #
Subclause
Comment
Proposed Change
122 13
There should be a distinction between a DEV beamforming capability and what degree of beamforming it wants to do before communicationg with another DEV. For example DEV1 might want to perfrom a level 1 only beamforming with DEV2 before communication although DEV1 is capable of 2 levels. Or DEV1 might be omni capable and does not want to do any beamforming. after 1st level
When DEV1 requests a CTA from the PN to perform beamforming with DEV2 it should tell the PNC the number of levels it wants to perform during this CTA.
Setting the Beam Tracking field before starting to send the training sequence , is only defined in (p 173 l 19), and is not mentioned at all for beam training.
The commenter is suggesting to define a procedure for negotiating training format w/ PNC.
It is best to define a single procedure for tracking and training .
Sending preamble without phy and mac header is unique to the beam training CTA!!
Qualcomm
Chuck Brabenac, Intel Labs

3. Comment Regarding SAS Training
<January 2002>
doc.: IEEE c
12/8/2018
Comment Regarding SAS Training
Comment #
Subclause
Comment
Proposed Change 74
13.5
in SAS there is no need for feedback for training, but such procedure is not defined
define procedure for SAS training w/o feedback , where each DEV trains its peers by sending repetitions of training sequence in each direction.
Setting the Beam Tracking field before starting to send the training sequence , is only defined in (p 173 l 19), and is not mentioned at all for beam training.
It is best to define a single procedure for tracking and training .
Comment about unique procedure for SAS training is redrawn.
Qualcomm
Chuck Brabenac, Intel Labs

4. Is there really a need for beam forming CTA?
<January 2002>
doc.: IEEE c
12/8/2018
Is there really a need for beam forming CTA?
Probably not since the optional beam forming can used for both training and tracking
Beam forming can be initiated in a regular CTA or CAP, at any time
Clarify beam training rules in 13.1:
If the DEV (say DEV-1) requires to perform beamforming with the other DEV (say DEV-2), DEV-1 shall transmit a empty command frame before transmitting training sequences
DEV-1 shall set the Beam Tracking field in PHY header of the command frame to ‘1’
DEV-1 trains DEV-2 using the on-demand beamforming protocol (using level 1 or 2 levels)
Cancel beam forming stream value from and
Add clarification to 13.1
Qualcomm
Chuck Brabenac, Intel Labs

5. Empty Command Frame Format
<January 2002>
doc.: IEEE c
12/8/2018
Empty Command Frame Format
Stream index is set to CTA isochronous streams value (no need for beam forming stream)
Qualcomm
Chuck Brabenac, Intel Labs

6. Empty CMS Phy Header Format
<January 2002>
doc.: IEEE c
12/8/2018
Empty CMS Phy Header Format
For an empty CMS frame all field of the Phy header are fixed, except for beam tracking, which shall be set to ‘1’ if training sequences for beam tracking are present following the current frame, it shall be set to zero otherwise.
The Frame Length field shall be an unsigned integer that indicates the number of octets in the MAC frame body, excluding the FCS and shall be set to zero for empty CMS frame.
The Aggregation bit shall be set to zero.
The UEP bit shall be set to zero.
The MCS field shall be set to 0b00000.
The Preamble Type field shall be set to 0b00.
The Low Latency mode bit shall be set to zero.
The Pilot Word Length field shall be set to zero.
The PCES field shall be set to zero.
Qualcomm
Chuck Brabenac, Intel Labs

7. HSI / SC Directional transmission w/ training
<January 2002>
doc.: IEEE c
12/8/2018
HSI / SC Directional transmission w/ training
*Assume MIFS between training sequence
*Assume MIFS between Announce command in different
directions during the AAS DEV2 to DEV1 feedback
Qualcomm
Chuck Brabenac, Intel Labs

8. Directional transmission w/o training
<January 2002>
doc.: IEEE c
12/8/2018
Directional transmission w/o training
Assuming that the best transmit pattern is known as a result of the beamforming, DEV (say DEV-1) shall use the best transmit pattern (sector or beam) toward the other DEV (say DEV-2)
Qualcomm
Chuck Brabenac, Intel Labs

9. BACKUP <January 2002> doc.: IEEE 802. 15-08-0183-00-003c
12/8/2018
BACKUP
Qualcomm
Chuck Brabenac, Intel Labs

10. 12/8/2018
Summary of the Q-Omni Association, Capability Exchange and Training Procedure
Procedure
Section 1
Beacon is composed from Q-omni beacon section (I(1,t) packets), PNC Q-omni tracking section (I(1,t) QTs), Sector training section (J(1,t) STs). The QT sequence shall be identical to the CMS preamble. 2
Device associate w/ PNC
13.5 3
DEV capability IE is included in association repeated beacon announcements (mMinBeaconInfoRepeat =4 consecutive times) 
8.6.4 4
All other DEVs that are members of the piconet receiving the beacon containing the DEV Association IE may use the DEV Association IE to update their internal list of associated DEVs in the piconet p 5
Channel time allocation is handled by exchanging command frames between originating DEV and PNC
8.5.1 6
In the case where the DEV is requesting
an allocation for beam forming, the stream index shall be set to beam forming stream value / 7
DEV train each other in allocated Beam Forming CTA
13.1 8
A new Channel time allocation is handled by exchanging command frames between originating DEV and PNC for data transfer
Slide 10
Qualcomm

11. 12/8/2018
Summary of the Q-Omni Association, Capability Exchange and Improved Training Procedure
Procedure
Section 1
Beacon is composed from Q-omni beacon section (I(1,t) packets), PNC Q-omni tracking section (I(1,t) QTs), Sector training section (J(1,t) STs). The QT sequence shall be identical to the CMS preamble. 2
Device associate w/ PNC
13.5 3
DEV capability IE is included in association repeated beacon announcements (mMinBeaconInfoRepeat =4 consecutive times) 
8.6.4 4
All other DEVs that are members of the piconet receiving the beacon containing the DEV Association IE may use the DEV Association IE to update their internal list of associated DEVs in the piconet p 5
Channel time allocation is handled by exchanging command frames between originating DEV and PNC
8.5.1 6
DEV optionally train each other in allocated CTA before sending directional data frame in any supported MCS
13.1
Slide 11
Qualcomm