110 likes | 199 Views
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]
E N D
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
Comment Regarding Training over Beam Forming CTA • Setting the Beam Tracking field before starting to send the training sequence , is only defined in 13.5.2 (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
Comment Regarding SAS Training • Setting the Beam Tracking field before starting to send the training sequence , is only defined in 13.5.2 (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
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 7.2.5 and 7.6.5.1 • Add clarification to 13.1 Qualcomm
Empty Command Frame Format • Stream index is set to CTA isochronous streams value (no need for beam forming stream) Qualcomm
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. Empty CMS Phy Header Format Qualcomm
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
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
BACKUP Qualcomm
Summary of the Q-Omni Association, Capability Exchange and Training Procedure Qualcomm Slide 10
Summary of the Q-Omni Association, Capability Exchange and Improved Training Procedure Qualcomm Slide 11