TGn Sync MAC Response to Reasons and Cures Relating to Frame Formats

Slides:



Advertisements
Similar presentations
Submission on comments to +HTC frames
Advertisements

Coexistence Motions for LB84 Comment Resolution
LB84 General AdHoc Group Sept. Closing TGn Motions
LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
TGn Sync Atlanta Presentation on Confirmation
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
March 2014 Election Results
Legacy OFDM Transmission on several Antennas
doc.: IEEE /xxxxr0 May 2005 May 2005
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
[ Policies and Procedure Summary]
TGn Sync MAC Response to Reasons and Cures
Motion to accept Draft p 2.0
Protected SSIDs Date: Authors: March 2005 March 2005
3GPP liaison report July 2006
[place presentation subject title text here]
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
Protection Assurance Method
TGn Frame Format Ad Hoc Status and Motions
November Opening Report
TGn Sync Simulation Results – Goodput versus PHY overhead
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
TGv Redline D0.06 Insert and Deletion
Solution for comment 32 Date: Authors: July, 2008
ADS Study Group Mid-week Report
Protection Assurance Method
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
TGn LB84 – Frame Format Ad Hoc Status and Motions
Solution for 40MHz in 2.4 GHz band
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
November Opening Report
TGn LB97 Frame Format Ad Hoc San Francisco, July 2007
Freedom to use 40MHz at 5GHz
TGr Proposed Draft Revision Notice
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
March Opening Report Date: Authors: March 2011
Liaison Report From Date: Authors: Month Year
Beamforming and Link Adaptation Motions
Beam Ad Hoc Agenda Date: Authors: March 2007 March 2007
Draft P802.11s D1.03 WordConversion
Questions to the Contention-based Protocol (CBP) Study Group
Power Saving for DLS July 2006 Date: Authors: Month Year
TGn LB84 – Frame Format Ad Hoc Status and Motions
TGu-changes-from-d0-04-to-d0-05
Transition Nowhere Date: Authors: Sept 2005 Sept 2005
TGu-changes-from-d0-03-to-d0-04
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
Selection Procedure Recommendation
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

TGn Sync MAC Response to Reasons and Cures Relating to Frame Formats doc.: IEEE 802.11-05/0430r0 May 2005 May 2005 TGn Sync MAC Response to Reasons and Cures Relating to Frame Formats Date: 2005-05-16 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>. Sudheer Grandhi, Interdigital Tomoko Adachi, Toshiba Corporation

Authors (continued): May 2005 doc.: IEEE 802.11-05/0430r0 May 2005 Sudheer Grandhi, Interdigital Tomoko Adachi, Toshiba Corporation

doc.: IEEE 802.11-05/0430r0 May 2005 May 2005 Comment #7, 76.1 Remove the IAC/RAC frame types. Not worth adding these given the questionable value of the mechanisms they support. The Initiator/Responder Aggregate Control and MRAD mechanisms represent a significant increase in frame types and implementation complexity for marginal benefit. Sudheer Grandhi, Interdigital Tomoko Adachi, Toshiba Corporation

doc.: IEEE 802.11-05/0430r0 May 2005 May 2005 Response #7, 76.1 IAC/RAC frames result in an epoch-making proposal which extends the capability of control frames to manage multi-function without wasting new subtypes. Sudheer Grandhi, Interdigital Tomoko Adachi, Toshiba Corporation

doc.: IEEE 802.11-05/0430r0 May 2005 May 2005 Comments # 20.2, 32, 33, 35, 45.1, 46 IAC, RAC, MRAD, ICB, and DCB frame formats need to be removed. Associated functionality with new frame formats needs to be removed. 802.11e frame formats shall be used in preference to new frame formats. The MAC design is too complicated with too many new frame formats to fix beam forming hidden-node problem. Sudheer Grandhi, Interdigital Tomoko Adachi, Toshiba Corporation

doc.: IEEE 802.11-05/0430r0 May 2005 May 2005 Response #20.2, 32, 33, 45.1,46 We have re-used 802.11e frame formats - as in our use of QoS Data, BA and BAR formats defined in 802.11e. We only add a small change in the 802.11e frame format to offer substantial improvement. IAC/RAC frame formats enable functions such as reverse direction flow, closed-loop link adaptation and pairwise-spoofing, giving significant performance improvement. ICB/DCB frames provide an efficient network management when legacy and 20 MHz HT devices coexist with 40 MHz HT devices. We have replaced the MRAD with a more effective mechanism - the MRA multi-poll. This has permitted some simplification of IAC/RAC. Further simplification is possible. Sudheer Grandhi, Interdigital Tomoko Adachi, Toshiba Corporation

doc.: IEEE 802.11-05/0430r0 May 2005 May 2005 Comment #69 IAC, RAC, MRAD, ICB, and DCB frame formats need to be removed. Associated functionality claimed related to power saving, which is critical to handsets should be backed up with results and should be realized with minimal changes. Sudheer Grandhi, Interdigital Tomoko Adachi, Toshiba Corporation

Response #69 The MMP frame format enables power saving. doc.: IEEE 802.11-05/0430r0 May 2005 May 2005 Response #69 The MMP frame format enables power saving. STAs not addressed in the MMP may conserve power during the remainder of the MRA. MMP is optional. STA can save power whether it supports MMP or not. Also please see response to #20. Sudheer Grandhi, Interdigital Tomoko Adachi, Toshiba Corporation

doc.: IEEE 802.11-05/0430r0 May 2005 May 2005 Comment #73 The MAC has (too) many frame formats (benefit? "enough" benefit? more consideration is due 802.11e) Sudheer Grandhi, Interdigital Tomoko Adachi, Toshiba Corporation

doc.: IEEE 802.11-05/0430r0 May 2005 May 2005 Response #73 Each frame format is introduced to support a new feature for achieving higher throughput efficiency in a specific context. Existing 802.11e frame formats (e.g. QoS Data, BA, BAR) have been re-used where appropriate. Sudheer Grandhi, Interdigital Tomoko Adachi, Toshiba Corporation

doc.: IEEE 802.11-05/0430r0 May 2005 May 2005 Comment #80 New frames, such as IAC/RAC, MRAD, ICB and DCB need to be removed. Sudheer Grandhi, Interdigital Tomoko Adachi, Toshiba Corporation

Response #80 Please see response to #20. doc.: IEEE 802.11-05/0430r0 May 2005 May 2005 Response #80 Please see response to #20. We introduce a few mechanisms and frame formats after careful consideration. However, we are still considering further simplification pending simulation results Sudheer Grandhi, Interdigital Tomoko Adachi, Toshiba Corporation

doc.: IEEE 802.11-05/0430r0 May 2005 May 2005 Comment #90 The contention-based access scheme is becoming too complicated and requires too much changes to 802.11e (we should use solutions that complement 802.11e instead of trying to modify it):- IAC, RAC control frames should be removed Sudheer Grandhi, Interdigital Tomoko Adachi, Toshiba Corporation

doc.: IEEE 802.11-05/0430r0 May 2005 May 2005 Response #90 In fact, the contention-based access scheme is not being modified. TGn Sync only modifies the definition of TXOP by permitting receivers to respond to the initiator during the period specified by the initiator. Reverse Direction addressed elsewhere. Sudheer Grandhi, Interdigital Tomoko Adachi, Toshiba Corporation