Proposed Resolution to CID 1420

Slides:



Advertisements
Similar presentations
Coexistence Motions for LB84 Comment Resolution
Advertisements

LB84 General AdHoc Group Sept. Closing TGn Motions
LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
Motions Date: Authors: January 2006
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
March 2014 Election Results
TGp Closing Report Date: Authors: July 2005 Month Year
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
Motion to accept Draft p 2.0
3GPP liaison report July 2006
[place presentation subject title text here]
Motions Date: Authors: January 2006
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
On Coexistence Mechanisms
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
TGn Frame Format Ad Hoc Status and Motions
November Opening Report
On Coexistence Mechanisms
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGu Timeline Date: Authors: January 2005 January 2005
TGv Redline D0.06 Insert and Deletion
ADS Study Group Mid-week Report
Scaling and Quantization for CSI Matrices Feedback
Protection Assurance Method
TGu-changes-from-d0-01-to-d0-02
Number of Encoder as a function of MCS
LB73 Noise and Location Categories
PHY CID 3242 Date: Authors: September 2007 September 2007
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D1.04-D1.0 Insert and Deletion
TGv Redline D0.10 Insert and Deletion
TGn LB84 – Frame Format Ad Hoc Status and Motions
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
TGp Closing Report Date: Authors: March 2007 Month Year
November Opening Report
TGr Proposed Draft Revision Notice
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
Beam & LA January Agenda & Status
Beamforming and Link Adaptation Motions
TGn Proposed Draft Revision Notice
PHY Motions for LB84 Comment Resolution
PHY CID 3242 Date: Authors: September 2007 September 2007
Beam Ad Hoc Agenda Date: Authors: March 2007 March 2007
Draft P802.11s D1.03 WordConversion
January Opening Report
TGn LB84 – Frame Format Ad Hoc Status and Motions
Beam Ad Hoc Agenda Date: Authors: March 2007 March 2007
TGu-changes-from-d0-04-to-d0-05
TGu-changes-from-d0-03-to-d0-04
Proposed Resolution to CID 1420
TGu Timeline Date: Authors: January 2005 January 2005
TGu Motions Date: Authors: May 2006 May 2006
PSMP Adhoc Oct TGn Adhoc
Beamforming and Link Adaptation Motions for LB 84 Comment Resolutions
TGn LB84 – Frame Format Ad Hoc Motions
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGr Proposed Draft Revision Notice
TGp Motions Date: Authors: January 2006 Month Year
May 2012 Opening Report Date: Authors: May 2012
Presentation transcript:

Proposed Resolution to CID 1420 September 2006 doc.: IEEE 802.11-06/1397r0 September 2006 Proposed Resolution to CID 1420 Date: 2006-09-13 Authors: Notice: This document has been prepared to assist IEEE 802.11. 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 grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <stuart.kerry@philips.com> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. John Ketchum, Qualcomm Incorporated John Ketchum, Qualcomm Incorporated

September 2006 doc.: IEEE 802.11-06/1397r0 September 2006 Abstract This document contains proposed changes to the IEEE P802.11n Draft to address the following LB84 comments: 1420, 7652 The changes marked in this document are based on TGn Draft version D1.03. John Ketchum, Qualcomm Incorporated John Ketchum, Qualcomm Incorporated

CID 1420 Comment: Proposed change: September 2006 doc.: IEEE 802.11-06/1397r0 September 2006 CID 1420 Comment: do we need to mention the other possible ways that this feedback is returned? Is the intent here simply to describe the case of "fast" linke adaptation? If so, then the other mechanisms need not be stated, but this sentence should then be qualified with the fact that fast link adaptation is being described (I know that the subclause header sort of says that, but...) Proposed change: start the sentence on line 19 with "For fast link adaptation, this frame may be John Ketchum, Qualcomm Incorporated John Ketchum, Qualcomm Incorporated

CID 7652 Comment: Proposed change: September 2006 doc.: IEEE 802.11-06/1397r0 September 2006 CID 7652 Comment: this subclause reads oddly - it introduces link adpatation which has just been defined in previous sections Proposed change: Replace heading with "Fast link adaptation using CSI feedback" and delete the first two paragraphs. John Ketchum, Qualcomm Incorporated John Ketchum, Qualcomm Incorporated

Text in Question 9.21.4 Fast link adaptation using explicit feedback September 2006 doc.: IEEE 802.11-06/1397r0 September 2006 Text in Question 9.21.4 Fast link adaptation using explicit feedback Two types of explicit feedback support fast link adaptation: MCS feedback and channel state feedback. MCS feedback is carried in an HT Control field in any supported frame type (see 7.1.3.5 (QoS Control field) and 7.1.3.5a (HT Control field)). Channel state feedback is carried in the CSI matrices feedback management action frame defined in 7.4.8.8 (MIMO CSI Matrices). This frame may be embedded in a QoS Null + HTC (MAP=1) frame with its Ack Policy field set to “no ack”, allowing it to be contained along with data or control frames inside an A-MPDU within an HT frame exchange. John Ketchum, Qualcomm Incorporated John Ketchum, Qualcomm Incorporated

Counter Proposal Counter proposal: September 2006 doc.: IEEE 802.11-06/1397r0 September 2006 Counter Proposal Counter proposal: Remove section 9.19.4 (9.21.4 in D1.03). The section mixes up link adaptation and explicit feedback in a confusing manner that adds nothing to the section. These two mechanisms should be addressed separately in the text, as they are already in 9.21.1, 9.21.2, 9.21.3, and 9.22.3 John Ketchum, Qualcomm Incorporated John Ketchum, Qualcomm Incorporated