Submission /0051r1Jan 2016 Slide 1David Xun Yang et al. (Huawei) Response Given Trigger Frame Type Date: NameAffiliationAddressPhone Ross Jian Yu F1-17, Huawei Base, Bantian, Shenzhen David X. Yang F1-17, Huawei Base, Bantian, Shenzhen Peter Loc Huawei Le Liu F1-17, Huawei Base, Bantian, Shenzhen Jun Luo 5B-N8, No.2222 Xinjinqiao Road, Pudong, Shanghai Yi Luo F1-17, Huawei Base, Bantian, Shenzhen Yingpei Lin 5B-N8, No.2222 Xinjinqiao Road, Pudong, Shanghai Jiyong Pang 5B-N8, No.2222 Xinjinqiao Road, Pudong, Shanghai Zhigang Rong Telesis Court, Suite 365, San Diego, CA NA Rob Sun 303 Terry Fox, Suite 400 Kanata, Ottawa, Canada Yunsong Yang Telesis Court, Suite 365, San Diego, CA NA Junghoon Suh 303 Terry Fox, Suite 400 Kanata, Ottawa, Canada

Submission /0051r1Jan 2016 Slide 2 Authors (continued) NameAffiliationAddressPhone Jiayin Zhang Huawei 5B-N8, No.2222 Xinjinqiao Road, Pudong, Shanghai Edward Au 303 Terry Fox, Suite 400 Kanata, Ottawa, Canada Teyan Chen F1-17, Huawei Base, Bantian, Shenzhen Yunbo Li F1-17, Huawei Base, Bantian, Shenzhen

Submission /0051r1Jan 2016 Slide 3 Authors (continued) NameAffiliationAddressPhone Hongyuan Zhang Marvell 5488 Marvell Lane, Santa Clara, CA, 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

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

Submission /0051r1Jan 2016 Slide 5 Authors (continued) NameAffiliationAddressPhone Rolf De Vegt Qualcomm 1700 Technology Drive San Jose, CA 95110, USA Sameer Vermani 5775 Morehouse Dr. San Diego, CA, USA Simone Merlin 5775 Morehouse Dr. San Diego, CA, USA Tao Tian 5775 Morehouse Dr. San Diego, CA, USA Tevfik Yucek 1700 Technology Drive San Jose, CA 95110, USA VK Jones 1700 Technology Drive San Jose, CA 95110, USA Youhan Kim 1700 Technology Drive San Jose, CA 95110, USA

Submission /0051r1Jan 2016 Slide 6 Authors (continued) Joonsuk Kim Apple Aon Mujtaba Guoqing Li Eric Wong Chris NameAffiliationAddressPhone James Yee Mediatek No. 1 Dusing 1 st Road, Hsinchu, Taiwan Alan Jauh Chingwa Hu m Frank Hsu Thomas Pare Mediatek USA 2860 Junction Ave, San Jose, CA 95134, USA ChaoChun Wang om James Wang Jianhan Liu Tianyu Wu Zhou Lan Russell Huang m

Submission /0051r1Jan 2016 Slide 7 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 NameAffiliation AddressPhone Ron Porat Broadcom Sriram Venkateswaran Matthew Fischer Leo Montreuil Andrew Blanksby Vinko Erceg

Submission /0051r1Jan 2016 Slide 8 Authors (continued) NameAffiliationAddressPhone 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 DerhamOrange 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 Pooya Monajemi

Submission /0051r1Jan 2016 Slide 9 Authors (continued) NameAffiliationAddressPhone 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 (972) Mark Rison Innovation Park, Cambridge CB4 0DS (U.K.) Rakesh Taori 1301, E. Lookout Dr, Richardson TX (972) Sanghyun Chang Maetan 3-dong; Yongtong-Gu Suwon; South Korea Yasushi Takatori NTT 1-1 Hikari-no-oka, Yokosuka, Kanagawa Japan Yasuhiko Inoue Shoko Shinohara Yusuke Asai Koichi Ishihara Junichi Iwatani Akira YamadaNTT DOCOMO 3-6, Hikarinooka, Yokosuka- shi, Kanagawa, , Japan

Submission /0051r1Jan 2016 Slide 10 Authors (continued) NameAffiliationAddressPhone Masahito Mori Sony Corp. Yusuke Yuichi Kazuyuki William

Submission /0051r1Jan 2016 Introduction Trigger type (allowed response type / Trigger frame variant) is in the common info field to indicate the allowed response type of the UL MAC frames In this contribution, we discuss how the STAs respond given the allowed response type Slide 11David Xun Yang et al. (Huawei)

Submission /0051r1Jan 2016 Response Given the Trigger Type When the AP sends a trigger frame variant, e.g., TF for CSI (or BF report poll trigger), here are several options for the response rule –Opt1: The response shall only contain the frame with required type; if there is no frame with the required type, the STA shall transmit QoS Null frame –Opt2: The response shall contain at least frame with required type if the required type is available at the STA side; if there is no frame with the required type, the STA shall transmit QoS Null frame –Opt3: The response shall contain at least the frame with required type if the required type is available at the STA side; if there is no frame with the required type, the STA can transmit other frame(s) without required type restriction (e.g., data frame) Slide 12David Xun Yang et al. (Huawei) QoS Null

Submission /0051r1Jan 2016 Pros. VS. Cons. Opt1: The response shall only contain the frame with required type if the required type is available at the STA side; if there is no frame with the required type, the STA shall transmit QoS Null frame –Pros: easy for implementation and scheduling –Cons: a lot of padding may exist, the efficiency is low Opt2: The response shall contain at least frame with required type if the required type is available at the STA side; if there is no frame with the required type, the STA shall transmit QoS Null frame –Pros: easy for implementation, aggregation of other types of MAC frames (e.g., data frame) will increase the efficiency –Cons: the resource will be wasted if no required response is available Opt3: The response shall contain at least the frame with required type if the required type is available at the STA side; if there is no frame with the required type,, the STA can transmit other frame(s) without required type restriction (e.g., data frame) –Pros: efficiency can be high even no required response is available –Cons: the implementation and state machine are very complicated. Difficult for scheduling. We prefer Opt2, and think Opt3 can be helpful Slide 13David Xun Yang et al. (Huawei)

Submission /0051r1Jan 2016 Reference ax-spec-framework Slide 14David Xun Yang et al. (Huawei)

Submission /0051r1Jan 2016 Straw Poll Do you support to add the following to the SFD: –If the trigger frame requests a specific frame type as response, the response to this trigger frame shall contain at least the frame with the required type if the required type is available at the STA side; if the STA has no frame with the required type, the STA should transmit QoS Null frame to AP. –Y –N –A Slide 15David Xun Yang et al. (Huawei)