1. IEEE 802.11n Consensus Proposal
Month Year
doc.: IEEE yy/xxxxr0
January 2005
IEEE n Consensus Proposal
Date:
Authors:
Notice: This document has been prepared to assist IEEE 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
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < 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 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 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
TGn Concensus Group
John Doe, Some Company

2. Month Year
doc.: IEEE yy/xxxxr0
January 2005
Abstract
Proposal to gain consensus on how to proceed in TGn. TGn should develop a 2 step process to align the standards process with what will happen in the market.
Proposal to form an 11n sub-committee to recommend how to merge key differences
TGn Concensus Group
John Doe, Some Company

3. Need for Focus and TTM Industry needs Standards based products – NOW
January 2005
Need for Focus and TTM
Industry needs Standards based products – NOW
Many companies will soon have open loop MIMO SDM designs ready for deployment
Align the standards process with what IS happening in the market
TGn needs to have a 2 step process to first develop the mandatory features of the standard and then optional features, for example:
Industry wants both Open AND Closed loop systems
But in a natural progression for the market
Open loop is a subset of Closed loop operation
Bi-directional data flow (nice to have for internet phones)
Interoperability will take a substantial amount of time
TGn Concensus Group

4. TGn Consensus PHY and MAC
January 2005
TGn Consensus PHY and MAC
Propose that 11n form a sub-committee to determine the best way to merge key technical differences
Promotes broader input and debate
Identifies support for individual technical items
Possible Process
Scheduled debate for individual items
Many, many straw polls
TGn Concensus Group

5. TGn Consensus PHY Proposal Examples
January 2005
TGn Consensus PHY Proposal Examples
20MHz vs 40 MHz issue
Wwise, Qualcomm, Mitmot – 40MHz optional
TGnSync – 40MHz mandatory
Compromise: 40MHz mandatory at 5GHz,
20MHz only at 2.4GHz
Code Rate: 5/6 and 7/8 Mandatory
GI: No half rate
Sub-Carriers: XX1 data and X1 20MHz, data MHz
1 - Give to Sub-committee to recommend
TGn Concensus Group

6. TGn Consensus PHY Proposal Examples
January 2005
TGn Consensus PHY Proposal Examples
Preambles:
Full & seamless interoperability with 11g
IS full & seamless interoperability with 11a Required?? Can we have just Greenfield + Protection Mechanisms1
Advanced coding scheme
TGnSync and WWiSE harmonized LDPC scheme
Duplicate 40MHz for 6Mbps/BPSK low rate transmission
Employ this scheme for high-quality low transmission
1 - Give to Sub-committee to recommend
TGn Concensus Group

7. TGn Consensus MAC Proposal Examples
January 2005
TGn Consensus MAC Proposal Examples
Aggregation:
WWiSE – MSDU aggregation +PPDU aggregation. Different transmit power levels can be applied to different receivers within a PPDU aggregation frame. No MAC effort is required to recover MSDU aggregation because the biggest length of PSDU is 8K bytes.
TGnSync – MPDU aggregation. Some receivers’ power can be saved if none of these receivers’ addresses is inside MRAD MPDU within an aggregation frame. Some MAC efforts are required to increase robustness of aggregation frame because the biggest length of PSDU is 256K bytes. Sophisticated mechanism is applied for bi-direction aggregation.
Compromise: Employ both
TGn Concensus Group