1. Proposed TGac Draft Amendment
Month Year
doc.: IEEE yy/xxxxr0
Proposed TGac Draft Amendment
Date:
Authors:
Name
Affiliation
Address
Phone
Chin-Hung (Jackson) Chen
Atheros
Industrial East Road, IX, Hsinchu Science Park, Hsinchu 308, Taiwan
Qifan Chen
690 Bibo Road, Shanghai, P.R.China
James Cho
1700 Technology Drive, San Jose, CA 95110
Youhan Kim
William McFarland
Kai Shi
Chi-Lin Su
Ning Zhang
Joshua (Shiwei) Zhao
Vinko Erceg
Broadcom
16340 West Bernardo Dr. San Diego, CA 92127
Mathew Fischer
190 Mathilda Place, Sunnyvale, CA 94086

2. 190 Mathilda Place, Sunnyvale, CA 94086 +1 408-922-8814
Peiman Amini
Broadcom
190 Mathilda Place, Sunnyvale, CA 94086
Joonsuk Kim
Ron Porat
16340 West Bernardo Dr. San Diego, CA 92127
Jun Zheng
Brian Hart
Cisco Systems
170 W Tasman Dr, San Jose, CA, 95134, USA
Reza Hedayat
2250 E. Pres. Bush Highway, Richardson, TX, , USA
Minho Cheong
ETRI
161 Gajeong-dong, Yuseong-gu, Daejeon, Korea
Jaewoo Park
Jae Seung Lee
Jong-Ee Oh
Jeeyon Choi
Yun Joo Kim
Sok-kyu Lee
Il-Gu Lee
Robert Stacey
Intel
2111 NE 25th Ave, Hillsboro OR, 97124, USA
Eldad Perahia
Michelle Gong
Santa Clara, CA, USA
Adrian Stephens
Minyoung Park
Daewon Lee
LG Electronics
LG R&D Complex 533, Hogye-1dong, Dongan-Gu, Anyang-Shi, Kyungki-Do, , Korea
Yongho Seok
Byeongwoo Kang
Dong Wook Roh
10225 Willow Creek Rd, San Diego, CA USA

3. 5488 Marvell Lane, Santa Clara CA, 95054 1-408-222-1837
Hongyuan Zhang
Marvell
5488 Marvell Lane, Santa Clara CA, 95054
Yong Liu
Raja Banerjea
Sudhir Srinivasa
Harish Ramamurthy
Hyukjoon Kwon
Yihong Qi
Rohit Nabar
Vish Ponnampalam
Mediatek
2860 Junction Ave, San Jose, CA 95134, USA
ChaoChun Wang
James Wang
Jianhan Liu
Huanchun Ye
VK Jones
Qualcomm
3165 Kifer Road, Santa Clara, CA 95051
Richard Van Nee
Straatweg 66-S, Breukelen, The Netherlands
Allert Van Zelst
Menzo Wentink
Geert Awater
Hemanth Sampath
5665 Morehouse Dr., San Diego, CA 92121
Sameer Vermani
Simone Merlin
Santosh Abraham
Lin Yang
Hossein Taghavi

4. 9120 Irvine Center Dr., Ste. 200, Irvine, CA 92618
Sean Coffey
Realtek
9120 Irvine Center Dr., Ste. 200, Irvine, CA 92618
Der-Zheng Liu
No. 2, Innovation Rd. II, Hsinchu Science Park, Hsinchu 300, Taiwan
Youngsoo Kim
Samsung Electronics
Mt Nongseo-Ri, Giheung-Eup, Yongin-Si, Gyeonggi-Do, Korea
Uikun Kwon
Patil Sandhya
Chunhui (Allan) Zhu
75 W. Plumeria Dr., San Jose, CA 95131
Osama Aboul-Magd
75 W. Plumeria Dr., San Jose, CA 95134
Liwen Chu
ST-Ericsson
2525 Augustine Drive, Santa Clara CA 95054
George Vlantis
Bo Sun
ZTE Corporation
ZTE Building, #10 South Tangyan Rd., Xi'an, China
Kaiying Lv

5. Overview We propose draft text for the TGac amendment
Captures, in detail, all features listed in the TGac Specification Framework
Large number of contributors (see Author’s list)
Extensive review by same list
This presentation
Outlines the parts of the spec that have been amended
Maps Spec Framework features to draft text
Easier to follow than a walk through the draft text itself

6. Major Clauses Modified
Based on REVmb 4.01
prior to section renumbering
3 Definitions
7 Frame Formats
9 MAC sublayer functional description
10 Layer Management
11 MLME
12 PHY service specification
17 OFDM PHY
22 VHT PHY  new clause for VHT PHY
Annex I
Annex J

7. 7 Frame formats New control frames Management frames A-MPDU
Added NDPA and Sounding Poll (section and of Spec Framework)
Management frames
New management IEs
VHT Capabilities element (section 6.2 of Spec Framework)
VHT Operation element (section 6.2 of Spec Framework)
VHT BSS Load element (section of Spec framework)
New action frames (VHT category added)
VHT Compressed Beamforming frame (section of Spec Framework)
Group ID management frame
Notify Operating Mode frame (section of Spec Framework)
A-MPDU
Extended length field to 14 bits
Addition of EOF bit
(from section of Spec Framework)

8. 7 Frame formats VHT Capabilities element VHT Operation element
VHT BSS always includes the HT Capabilities element
Therefore, VHT Capabilities element only includes
Capabilities not present in HT Capabilities element or
Capabilities directly applicable to VHT PPDU
VHT Operation element
VHT BSS always has HT Operation element
Therefore, VHT Operation element only includes
Channel width
Center frequency for 2 segments (to support non-contiguous)
Primary channel is specified in HT Operation element

9. 7 Frame formats VHT Compressed Beamforming frame
From section of Spec Framework (and based on Compressed Beamforming frame (11n))
Contains the following fields:
VHT MIMO Control field
Based on 11n MIMO Control field
VHT Compressed Beamforming Report field
Based on 11n Compressed Beamforming Report field
MU Exclusive Beamforming Report field
New field for MU-MIMO (and only included with MU sounding)
Additional per tone SNR information

10. 9 MAC sublayer functional description
RTS/CTS in wider channels
(section 6.9 of Spec Framework)
9.2 DCF
9.6 Multirate support
These sections are updated to describe
BW signaling using RTS/CTS frames in non-HT duplicate format
Rules for CTS response based on received RTS and secondary channel CCA
Rules for Data transmission based on receive CTS

11. 9 MAC sublayer functional description
9.7d A-MPDU operation
9.7d.5 Transport of A-MPDU by the PHY data service
Updated to require A-MPDU in VHT format frame
9.7d.6 A-MPDU padding for VHT format PPDU
New section describing A-MPDU padding of VHT PPDUs
9.7d.7 Transport of VHT single MPDUs
From section 6.5 of Spec Framework
Rules for transporting a single MPDU in a VHT frame
9.7d.8 Partial AID in VHT PPDUs
From section 6.6 of Spec framework
Rules for setting Partial AID field in VHT PPDUs

12. 9 MAC sublayer functional description
TXOP Sharing
(From section 6.4 of Spec Framework)
3 Definitions
Definitions for Primary AC, etc. (from Spec Framework)
9.9 HCF
EDCA TXOPs
a Sharing an EDCA TXOP  new section
Multiple frame transmission in an EDCA TXOP
Updated to describe TXOP sharing concept

13. 9 MAC sublayer functional description
Backoff procedure
(From section 5.2 of Spec Framework)
EDCA backoff procedure
Updated to describe backoff operation with MU-MIMO frames

14. 9 MAC sublayer functional description
Sounding protocol
(From section 6.7 of Spec Framework)
9.21 Null data packet (NDP) sounding
VHT sounding protocol  new section
Sounding and feedback protocol rules

15. 10 Layer Management 10.4.7 PLME-TXTIME.confirm
The MAC needs to know how much padding is to add to the A-MPDU
MAC sends PLME-TXTIME.request to PHY with LENGTH of useful data, MCS, etc. for each user
PHY returns PLME-TXTIME.comfirm primitive with
TXTIME (original purpose)
PSDU_LENGTH[]
Number of octets in PSDU including padding
Returned as an array since it is per user
Keeps the formula for determining number of octets in PSDU in one place in the spec
TXTIME and PSDU_LENGTH calculation
PHY section where TXTIME and PSDU_LENGTH calculation is described

16. 11 MLME DL MU-MIMO Power Save (from section 6.1.1 of Spec Framework)
11.2 Power management
Power management in infrastructure network
a Power management during MU-MIMO transmissions
b VHT STA power management modes
New sections to describe power save during MU TXOPs

17. 11 MLME Rules for AID assignment (from section 6.6 of Spec Framework)
11.20 VHT BSS operation
AID assignment by VHT AP
Rules to prevent AID assignment that results in two STAs having the same Partial AID

18. 11 MLME 11.20 VHT BSS operation 11.20.3 Basic VHT BSS functionality
Rules for transmitting PPDU of various BW:
All transmission must include primary channel
All transmission must use valid 20/40/80/160/80+80 MHz channel
STA CCA sensing in VHT BSS
(from section 5 of Spec Framework)
To transmit 40 MHz PPDU, secondary channel must be idle PIFS before transmission
To transmit 80 MHz PPDU, secondary channel and secondary 40 MHz channel must be idle PIFS before transmission
To transmit 160/80+80 MHz PPDU, secondary 20 MHz channel, secondary 40 MHz channel, secondary 80 MHz channel must be idle PIFS for transmission

19. 12 PHY service specification
PHY-CCA.indication
Extending primitive to 80 MHz, 160 MHz and MHz channels

20. 17 OFDM PHY BW signaling use scrambler init in SERVICE field
(from section 3a in Spec Framework)
TXVECTOR parameters
RXVECTOR parameters
Etc.
Parameters are added for INDICATED_DYN_BANDWIDTH, INDICATED_CH_BANDWIDTH
PLCP DATA scrambler and descrambler
Details on generating scrambler init field to signal
Dynamic/Static
BW indication

21. 22 VHT PHY Clause 22 maps directly from section 3 of Spec Framework
22.1 Introduction
Overview with mandatory and optional feature list
Bandwidth modes:
20 MHz, 40 MHz, 80 MHz – mandatory
160 MHz (i.e. contiguous 160 MHz) -- optional
80+80 MHz (i.e. non-contiguous 160 MHz) -- optional
MCS
0-7 – same as n, support mandatory
8 and 9 – 256-QAM ¾, 256-QAM 5/6 – optional
Single, unified frame format for both SU and MU

22. 22 VHT PHY 22.2 VHT PHY service interface
VHT PHY includes HT PHY and OFDM PHY
FORMAT parameter
Non-HT (i.e. OFDM PHY), HT_MF, HT_GF and VHT
CH_BANDWIDTH parameter
HT_CBW20, HT_CBW40, HT_CBW80, HT_CBW160, HT_CBW80+80
NON_HT_CBW20, NON_HT_CBW40, NON_HT_CBW80, NON_HT_CBW160, NON_HT_CBW80+80
(HT/NON_HT reference in CBW is redundant since captured in FORMAT, we did not change this, but expect to in future revisions)

23. 22 VHT PHY 22.2 VHT PHY service interface (continued) MU parameters
GROUP_ID (value to place in Group ID field)
NUM_USERS
Array of parameters with NUM_USERS entries
USER_INDEX (integer 0-3, user position in Nsts array)
MCS
NUM_STS
LENGTH (value in VHT-SIG-B)
PSDU_LENGTH (actual PSDU length)
SU parameters
Same as per user list above, but with NUM_USERS set to 1
PARTIAL_AID

24. 22 VHT PHY 22.3 VHT PLCP sublayer 22.3.2 VHT PPDU format
Spec Framework Figure 3 converted to text plus diagram
Transmitter block diagram
Functional blocks for creating various parts of PPDU
Overview of the PPDU encoding process
Modulation and coding scheme
References to section 22.6 (tables detailing rate-dependent parameters)
Timing-related parameters
List of timing and other frequently used parameters
Mathematical description of signals
Mathematical description of the transmitted signal
Transmission of PPDU with less than BSS bandwidth
Adjustments to center frequency to derive narrow bandwidth signals

25. 22 VHT PHY 22.3 VHT PLCP sublayer (continued) 22.3.9 VHT preamble
Descriptions (incl mathematical) for various portions of preamble
In addition, the following is notable:
L-SIG
Value in LENGTH field determined by packet duration
VHT-SIG-A
Detailed description of fields derived from Specification Framework
Describes rotation on second symbol as in Specification Framework
VHT-SIG-B
How value in Length field is derived from LENGTH parameter in TXVECTOR
Fixed bit pattern in VHT-SIG-B for NDP in various bandwidths
Details on repetition of bits for various bandwidths (from Spec Framework)

26. 22 VHT PHY 22.3 VHT PLCP sublayer (continued) 22.3.11 Data field
SERVICE field
Including CRC for VHT-SIG-B
Details on CRC used (same CRC-8 used elsewhere)
Scrambler
Reference to scrambler in Clause 17 (OFDM PHY)
Coding
BCC and LDPC
Encoding process for MU packets
BCC Interleaver
Constellation mapping
Reference to Clause 17 except for 256-QAM
256-QAM mapping defined
LDPC tone mapping

27. 22 VHT PHY 22.3 VHT PLCP sublayer (continued)
Non-HT duplicate transmission
Support for ‘quadruplicate’, ‘octuplicate’ non-HT transmissions (section 5 of Spec Framework)
Beamforming and MU-MIMO
Details on V matrix feedback based beamforming and MU-MIMO
VHT preamble format for sounding PPDUs
Sounding PPDU format (VHT PPDU without Data field)
Channel numbering and channelization
Channels fully defined using {BW, CenterFreq, Primary20MHzChan)
PMD transmit specification
Transmit spectral mask
From section of Spec Framework
Spectral flatness
From section of Spec Framework

28. 22 VHT PHY 22.3 VHT PLCP sublayer (continued)
PMD receiver specification
CCA sensitivity
From section 3.5 of Spec Framework
Carry over 11n sensitivity requirements, extended to 80 and 160 MHz
Mostly TBD for secondary channel sensitivity
PLCP transmit procedure
Follows 11n
PLCP receive procedure
Defer using L-SIG if error in VHT-SIG

29. 22 VHT PHY 22.4 VHT PLME 22.4.3 TXTIME and PSDU_LENGTH calculation
Primitive by which MAC determines how much padding to add
MAC passes down amount of useful data for each user
PHY determines Nsym based on coding, etc.
PHY determines PSDU_LENGTH (total number of octets MAC needs to supply) for each user

30. Annexes I and J Annex I Annex J United States Europe Japan Global
Table I-2 updated for 80 MHz and 160 MHz behavior
Annex J
Operating classes table updated for
United States
Europe
Japan
Global
Following section 3.1 of Spec Framework

31. Summary We propose draft text for the TGac amendment
Includes sections for all features in the Specification Framework
Not complete – there are still TBDs in many sections
Reflecting TBDs in Spec Framework

32. References [1] 09/0992 TGac Specification Framework
Month Year
doc.: IEEE yy/xxxxr0
References
[1] 09/0992 TGac Specification Framework
[2] 09/ ac Proposed Selection Procedure
[3] 10/1361 Proposed TGac Draft Amendment