1. Concluding OFDMA M-BA transmission
July, 2016
Concluding OFDMA M-BA transmission
Date:
Authors:
Name
Affiliation
Address
Phone
Zhou Lan
Broadcom
Matthew Fischer
Sriram Venkateswaran
Ron Porat
Leo Montreuil
Andrew Blanksby
Vinko Erceg
Zhou Lan, Broadcom et al

2. 2111 NE 25th Ave, Hillsboro OR 97124, USA
July, 2016
Authors (continued)
Robert Stacey
Intel
2111 NE 25th Ave, Hillsboro OR 97124, USA     
Shahrnaz Azizi
Po-Kai Huang
Qinghua Li
Xiaogang Chen
Chitto Ghosh
Laurent Cariou
Yaron Alpert
Assaf Gurevitz
Ilan Sutskover
Zhou Lan, Broadcom et al .

3. Authors (continued) July, 2016 Hongyuan Zhang Marvell
Name
Affiliation
Address
Phone
Hongyuan Zhang
Marvell
5488 Marvell Lane, Santa Clara, CA, 95054
Yakun Sun
Lei Wang
Liwen Chu
Jinjing Jiang
Yan Zhang
Rui Cao
Sudhir Srinivasa
Bo Yu
Saga Tamhane
Mao Yu
Xiayu Zheng
Christian Berger
Niranjan Grandhe
Hui-Ling Lou
Zhou Lan, Broadcom et al

4. Authors (continued) July, 2016 Alice Chen Albert Van Zelst
Name
Affiliation
Address
Phone
Alice Chen
Qualcomm
5775 Morehouse Dr. San Diego, CA, USA
Albert Van Zelst
Straatweg 66-S Breukelen, 3621 BR Netherlands
Alfred Asterjadhi
Arjun Bharadwaj
Bin Tian
Carlos Aldana
1700 Technology Drive San Jose, CA 95110, USA
George Cherian
Gwendolyn Barriac
Hemanth Sampath
Lin Yang
Menzo Wentink
Naveen Kakani
2100 Lakeside Boulevard Suite 475, Richardson TX 75082, USA
Raja Banerjea
1060 Rincon Circle San Jose CA 95131, USA
Richard Van Nee
Zhou Lan, Broadcom et al

5. Authors (continued) July, 2016 Rolf De Vegt Sameer Vermani Qualcomm
Name
Affiliation
Address
Phone
Rolf De Vegt
Qualcomm
1700 Technology Drive San Jose, CA 95110, USA
Sameer Vermani
5775 Morehouse Dr. San Diego, CA, USA
Simone Merlin
Tao Tian
Tevfik Yucek  
VK Jones
Youhan Kim
Zhou Lan, Broadcom et al

6. Authors (continued) July, 2016 James Yee Mediatek
Name
Affiliation
Address
Phone
James Yee
Mediatek
No. 1 Dusing 1st Road, Hsinchu, Taiwan  
Alan Jauh
Chingwa Hu
Frank Hsu
Thomas Pare
USA
2860 Junction Ave, San Jose, CA 95134, USA
ChaoChun Wang
James Wang
Jianhan Liu
Tianyu Wu
Russell Huang
Joonsuk Kim
Apple
Aon Mujtaba  
Guoqing Li
Eric Wong
Chris Hartman
Zhou Lan, Broadcom et al .

7. Authors (continued) July, 2016 Peter Loc Jun Luo Yi Luo Yingpei Lin
Name
Affiliation
Address
Phone
Peter Loc
Huawei
Jun Luo
5B-N8, No.2222 Xinjinqiao Road, Pudong, Shanghai
Yi Luo
F1-17, Huawei Base, Bantian, Shenzhen
Yingpei Lin
Jiyong Pang
Zhigang Rong
10180 Telesis Court, Suite 365, San Diego, CA  NA
Rob Sun
303 Terry Fox, Suite 400 Kanata, Ottawa, Canada
David X. Yang
Yunsong Yang
Junghoon Suh
Jiayin Zhang
Edward Au
Teyan Chen
Yunbo Li
Zhou Lan, Broadcom et al

8. Authors (continued) July, 2016 Jinmin Kim LG Electronics
Name
Affiliation
Address
Phone
Jinmin Kim
LG Electronics
19, Yangjae-daero 11gil, Seocho-gu, Seoul , Korea
Kiseon Ryu
Jinyoung Chun
Jinsoo Choi
Jeongki Kim
Dongguk Lim
Suhwook Kim
Eunsung Park
JayH Park
HanGyu Cho
Thomas Derham
Orange
Bo Sun
ZTE
#9 Wuxingduan, Xifeng Rd., Xi'an, China
Kaiying Lv
Yonggang Fang
Ke Yao
Weimin Xing
Brian Hart
Cisco Systems
170 W Tasman Dr, San Jose, CA 95134
Pooya Monajemi
Zhou Lan, Broadcom et al

9. Authors (continued) July, 2016 Fei Tong Samsung Hyunjeong Kang
Name
Affiliation
Address
Phone
Fei Tong
Samsung
Innovation Park, Cambridge CB4 0DS (U.K.)
Hyunjeong Kang
Maetan 3-dong; Yongtong-Gu Suwon; South Korea
Kaushik Josiam
1301, E. Lookout Dr, Richardson TX 75070
(972)
Mark Rison
Rakesh Taori
(972)
Sanghyun Chang
Yasushi Takatori
NTT
1-1 Hikari-no-oka, Yokosuka, Kanagawa Japan  
Yasuhiko Inoue  
Shoko Shinohara
Yusuke Asai  
Koichi Ishihara  
Junichi Iwatani  
Akira Yamada
NTT DOCOMO
3-6, Hikarinooka, Yokosuka-shi, Kanagawa, , Japan
 3759
Zhou Lan, Broadcom et al

10. Authors (continued) July, 2016 Zhou Lan, Broadcom et al Name
Affiliation
Address
Phone
Masahito Mori
Sony Corp.
Yusuke Tanaka
Yuichi Morioka
Kazuyuki Sakoda
William Carney
Minho Cheong
Newracom, Inc.
9008 Research Dr, Irvine, CA 92618
Reza Hedayat
Young Hoon Kwon
Yongho Seok
Daewon Lee
Yujin Noh
Sigurd Schelstraete
Quantenna
3450 W. Warren Ave, Fremont, CA 94538
Huizhao Wang
Zhou Lan, Broadcom et al

11. Abstract
TGax Draft specification supports OFDMA transmission of Multi-STA BA for UL MU acknowledgement
In this contribution we discuss Multi-STA BA related PHY frame format, allowed RUs and usages cases
We propose some rules to limit the usage case of OFDMA transmission of Multi-STA BA to simplify implementation
Zhou Lan, Broadcom et al

12. PHY frame format
M-BA should be PHY agnostic, it shall be allowed in any of the following PHY frame format
NON-HT Duplicate PPDU
HT PPDU
VHT PPDU
HE SU PPDU
HE MU PPDU
HE Trigger Based PPDU
Zhou Lan, Broadcom et al

13. M-BA on 106 tone RU for (STA 1, 2, 3, 4)
Allowed RUs
Question: Do we want to allow M-BA on 26/52RU?
OFDMA M-BA should be PHY agnostic
M-BA can be transmitted in 26RU for single user (unicast RU) or multiple users (Broadcast RU)
Allowing M-BA on smaller size RU helps to release more RU for data and Trigger Frame
No technical reason observed to disallow M-BA on 26 and 52 RUs
Trigger
Frame
UL MU frame (STA8)
UL MU frame (STA7)
UL MU frame (STA6)
UL MU frame (STA5)
UL MU frame (STA4)
UL MU frame (STA3)
UL MU frame (STA2)
UL MU frame (STA1)
M-BA on 106 tone RU for (STA 1, 2, 3, 4)
HE-SIG B
OFDMA PPDU of M-BA
BA for STA 5 on 26 RU
UL MU PPDU
Trigger frame
20MHz/
242 tones
BA for STA 6 on 26 RU
BA for STA 7 on 26 RU
Trigger frame on 26 RU
BA for STA 8 on 26 RU
Zhou Lan, Broadcom et al

14. A bit more thinking on the allowed RU
PHY motion passed regarding legacy preamble of Trigger Based HE MU PPDU
UL pre-HE-STF preamble is sent only on the 20MHz-CH(s) where the HE modulated fields are located. The UL pre-HE-STF preamble includes legacy preamble, RL-SIG and HE-SIG-A and HE modulated fields refer to HE-STF, HE-LTF and data fields. [PHY Motion 154, March 2016, see 16/395]
We should not allow M-BA transmission to be shifted to other 20MHz channel where its associated data PPDU is not transmitted, otherwise the M-BA transmission will not be protected from hidden node that is supposed to be muted by the preamble of the preceding UL PPDU
However we should allow M-BA transmission on broader bandwidth that includes the RU of the preceding UL PPDU
E.g when the preceding Trigger Based PPDU is on 20 MHz, then the M-BA should be allowed on the 40MHz channel that includes this 20MHz
M-BA on broader bandwidth is partially protected by the legacy preamble of the preceding UL PPDU
Low MCS and interleaving can improve the error performance when there is interference from the unprotected 20MHz
M-BA for STAs 1, 2, 4, 5 in RU 1 with MCS 5
20MHz TF
M-BA for STAs 3, 6 in RU 2 with MCS 0
20MHz AP
HE TB PPDUs
STAs 1, 2, 3
20MHz
HE TB PPDUs
STAs 4, 5, 6
20MHz
Zhou Lan, Broadcom et al

15. OFDMA M-BA usage case
Q: Do we really want to have multiple M-BA in one DL HE MU PPDU?
The whole point of OFDMA M-BA compared with OFDMA BA is to avoid PADDING
So….
Zhou Lan, Broadcom et al

16. OFDMA M-BA usage case (Cont.)
If we want to do this…(Users with similar MCS)
Then why not do this?
Trigger
Frame
UL MU frame (STA8)
UL MU frame (STA7)
UL MU frame (STA6)
UL MU frame (STA5)
UL MU frame (STA4)
UL MU frame (STA3)
UL MU frame (STA2)
UL MU frame (STA1)
M-BA 1 for (STA 1, 2, 3, 4)
HE-SIG B
OFDMA PPDU of M-BA
M-BA 2 for (STA 5, 6, 7, 8)
UL MU PPDU
Trigger frame
20MHz/
242 tones
Trigger
Frame
UL MU frame (STA8)
UL MU frame (STA7)
UL MU frame (STA6)
UL MU frame (STA5)
UL MU frame (STA4)
UL MU frame (STA3)
UL MU frame (STA2)
UL MU frame (STA1)
M-BA 1 for (STA 1, 2, 3, 4,5,6,7,8)
HE-SIG B
SU PPDU of M-BA
UL MU PPDU
Trigger frame
20MHz/
242 tones
Zhou Lan, Broadcom et al

17. OFDMA M-BA usage case (Cont.)
If we want to support users with totally different MCSs, then why not just use OFDMA BA like this
Trigger
Frame
UL MU frame (STA8)
UL MU frame (STA7)
UL MU frame (STA6)
UL MU frame (STA5)
UL MU frame (STA4)
UL MU frame (STA3)
UL MU frame (STA2)
UL MU frame (STA1)
HE-SIG B
OFDMA PPDU of M-BA
BA for STA 5 on 26 RU
UL MU PPDU
Trigger frame
20MHz/
242 tones
BA for STA 6 on 26 RU
BA for STA 7 on 26 RU
BA for STA 8 on 26 RU
BA for STA 1 on 26 RU
BA for STA 2 on 26 RU
BA for STA 3 on 26 RU
BA for STA 4 on 26 RU
Zhou Lan, Broadcom et al

18. OFDMA M-BA usage case (Cont.)
If we have most users with similar MCS and only several bad guys, we can do this
Trigger
Frame
UL MU frame (STA8)
UL MU frame (STA7)
UL MU frame (STA6)
UL MU frame (STA5)
UL MU frame (STA4)
UL MU frame (STA3)
UL MU frame (STA2)
UL MU frame (STA1)
M-BA on 106 tone RU for (STA 1, 2, 3, 4)
HE-SIG B
OFDMA PPDU of M-BA
BA for STA 5 on 26 RU
UL MU PPDU
Trigger frame
20MHz/
242 tones
BA for STA 6 on 26 RU
BA for STA 7 on 26 RU
Trigger frame on 26 RU
BA for STA 8 on 26 RU
Zhou Lan, Broadcom et al

19. Proposed change to the current Draft
limiting the number of M-BA in DL HE MU PPDU doesn’t seem a big loss of flexibility
There shall be no more than one M-BA that is addressed to multiple recipients carried in a broadcast RU of the DL MU PPDU.
A HE AP should only transmit group addressed M-BA in the DL MU PPDU to HE non AP STA n on the (broadcast RU) RU (26/52/106/242/484/996) that includes the RU used for receiving the immediate preceding HE Trigger Based PPDU from STA n.
Zhou Lan, Broadcom et al

20. Straw poll Do you support to
Direct TGax Editor to add the following paragraph after the first paragraph of section
 A HE AP should only transmit group addressed M-BA in the DL MU PPDU to HE non AP STA n on the (broadcast RU) RU (26/52/106/242/484/996) that includes the RU used for receiving the immediate preceding HE Trigger Based PPDU from STA n. There shall be no more than one M-BA that is addressed to multiple recipients carried in a broadcast RU of the DL MU PPDU.
Yes No
Abstain
Zhou Lan, Broadcom et al