Resource Negotiation for Unassociated STAs in MU Operation

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0880r2 Submission Scheduled Trigger frames July 2015 Slide 1 Date: Authors: A. Asterjadhi, H. Choi, et. al.
Advertisements

Submission doc.: IEEE /1340r2 November 2015 Narendar Madhavan, ToshibaSlide 1 NDP Announcement for HE Sequence Date: Authors:
Submission doc.: IEEE /0353r1 March 2016 Hanseul Hong, Yonsei UniversitySlide 1 MU-RTS/CTS for TWT Protection Date: Authors:
Multi-STA BA Design Date: Authors: March 2016 Month Year
802.11az Negotiation Date: Authors: Jan 2017 Month Year
Location Measurement Protocol for Unassociated STAs
MU BAR Frame Format Date: Authors: November 2015 Month Year
Resource Negotiation for Unassociated STAs in MU Operation
802.11az Negotiation Date: Authors: May 2017 Month Year
Trigger Frame Format for az
Polling for MU Measurements
Ranging ID and its Lifetime Management
Month Year doc.: IEEE yy/xxxxr0 July 2015
Month Year doc.: IEEE yy/xxxxr0 July 2017
WUR MAC issues follow-up
Random Access RU Allocation in the Trigger Frame
Random Access RU Allocation in the Trigger Frame
Considerations for WUR Response
BSS Management through WUR Wakeup Frame
Wakeup Frame Format Date: Authors: Sept 2017 Liwen Chu
Channel Access Efficiency
Wake Up Frame to Indicate Group Addressed Frames Transmission
Further considerations on WUR frame format
Synchronization with Low Power Antenna
Resource Allocation for Unassociated STAs – Follow Up
Amendment text submissions formatting conventions
Considerations on Trigger Frame for Random Access Procedure
Issues related to OCW management
11az NDP Announcement Date: July 2008
Two-sided LMR Feedback between AP and STA
11az STA Polling for MU NDP Ranging
UL OFDMA-based Random Access Parameter Set (RAPS) element
WUR MAC issues follow-up
MU Ranging Sequence Date: Authors: Nov 2017 Month Year
Further considerations on WUR frame format
Month Year doc.: IEEE yy/xxxxr0 July 2015
BSS Color in NDP Ranging
Wakeup Frame Format Date: Authors: Sept 2017 Liwen Chu
Functional requirements for scalability operation
Random Access RU Allocation in the Trigger Frame
An unified az Protocol Date: Authors: Nov 2016
11az STA Polling for MU NDP Ranging
WUR MAC and Wakeup Frame
11az NDP Announcement Date: July 2008
Discussion on CR for CID 5066
Discussion on Group ID Structure
Random Access RU Allocation in the Trigger Frame
WUR MAC and Wakeup Frame
Further considerations on WUR frame format
Channel Access Efficiency
Considerations for WUR Response
Comment resolution on CID 20175
FTM Frame Exchange Authentication
Explicit Block Ack Request in DL MU PPDU
Explanations for CR on NDP feedback report
Channel Access Efficiency
Comment resolution on CID 20175
Wakeup Frame Format Date: Authors: Sept 2017 Liwen Chu
Random Access UL MU Resource Allocation and Indication
Discussion on Group ID Structure
WUR MAC and Wakeup Frame
NDP Bandwidth Selection in Range Measurement
Secure SU and MU Ranging Measurement Procedure
Considerations on Trigger Frame for Random Access Procedure
Location Measurement Protocol for 11ax
BSS Color in NDP Ranging
Functional Requirements for a .11az Scalability Requirements
11az Negotiation Protocol (update)
Data Sharing for Multi-AP Coordination
EHT Power saving considering multi-link
Presentation transcript:

Resource Negotiation for Unassociated STAs in MU Operation Month Year doc.: IEEE 802.11-yy/xxxxr0 March 2017 Resource Negotiation for Unassociated STAs in MU Operation Date: 2017-03-13 Authors: Name Affiliation Address Phone Email Chao-Chn Wang MediaTek Inc Chao-chun.wang@mediatek.com James Yee James.yee@mediatek.com Chao-Chun Wang (MediaTek Inc) John Doe, Some Company

March 2017 Background FTM negotiation protocol in dense environment must be able to adapt to the network loading to improve the efficiency of the protocol. The FTM negotiation phase can be further separated into request and response phase. There are three possible modes of operation The request phase operates in SU mode and the response phase operates in SU Same as REVmc and there is no need to add new protocol in 11 az standard. The request phase operates in SU mode and the response phase operates in MU mode The request phase operates in MU mode and response phase operates in MU mode The request phase operates in MU mode and response phase operates in SU mode The request is very similar to MU Mode request and the response is the same as in SU Response case. The presentation is discussing the pro and con of the second and third methods Chao-Chun Wang (MediaTek Inc)

March 2017 Mode of Operations (SU-MU) An STA sends FTM request in SU mode and receive FTM response (in SU PPDU format) for MU operation What’s AP behavior? (MU – MU) An STA sends FTM request in MU mode and receive FTM response (in SU, MU PPDU format) for MU operation What is AP’s behavior? Should AP includes an IE to announce the FTM MU operation parameters? Parameters are TBD Alternately there might be no IE, instead the details are announced in the Trigger Frame for MU operation Chao-Chun Wang (MediaTek Inc)

March 2017 SU-MU Operations An STA sends FTM request in SU mode and receive FTM response (in SU PPDU format) for MU operation Does FTM Request has a field indicating the preference by the STA as to how it wants to receive FTM Response? The MU response frame (in SU PPDU) has a pre-defined/announced unique AID/multicast address to indicate that it is a FTM response frame An STA is expected to read all fields of the response frame with RA set to a pre-defined/announced multicast Address, The MU response frame (in SU PPDU) carries FTM parameters for every STAs, a FTMid (a.k. pre-AID) is assigned to each unassociated STA. The succeeding measurement operations operate in MU mode Chao-Chun Wang (MediaTek Inc)

March 2017 MU-MU Operations - 1 An STA sends FTM request in MU mode and receive FTM response (in SU, MU PPDU format) for MU operation AP sends trigger frame that indicates availability of random access RUs, each random access RU has a RUid Each STA selects one of the RU to transmit a FTM Request and records the RUid AP responds with a FTM response frame for MU operation (no ACK necessary) STA can determine if its request was sent successfully or not by looking at the MU FTM response frame. MU FTM response frame in SU PPDU – same as the previous page MU FTM response frame in MU PPDU The response frame use the same RU allocation as the request frame The MU response frame (in SU PPDU) carries FTM parameters for every STAs, a FTMid (a.k. pre-AID) is assigned to each unassociated STA. Chao-Chun Wang (MediaTek Inc)

March 2016 MU-MU Operations - 2 An STA sends FTM request in MU mode and receive FTM response (in SU, MU PPDU format) for MU operation AP sends trigger frame that indicates availability of random access RUs, each random access RU has a Ruid, this can be a trigger frame very specific to send FTM Request frames Each STA selects one of the RU to transmit a FTM Request and records the Ruid AP Responds back with a frame Acknowledging (or MBA ACK) the FTM Requests using the pre-defined Multicast Address (included in the Random RU Trigger frame, or pre-defined for the BSS) Acknowledgement can be an SU PPDU (with RA field set to the pre-defined or signaled MAC address in the Trigger Frame used to receive FTM Requests) AP responds with a FTM response frame for MU operation and a Trigger frame is allocated to receive Acknowledgement from STA MU FTM response frame in SU PPDU – same as the previous page MU FTM response frame in MU PPDU - TBD Chao-Chun Wang (MediaTek Inc)

Trade-offs for evaluating various options March 2017 Trade-offs for evaluating various options Power Consumption: The STA that has sent an MU request will be required to process all the Broadcast frames or a limited number of frames SU-MU is an allowed mode -> has power implications MU-MU has power implications Waiting time from transmitting FTM Request to Receiving FTM Response: Revmc has this value at 10msec Revmc has a value defined to allow for STAs to save power APs take time to process FTM Requests and allowing for a large number of requests can increase the waiting time for FTM Response(s) -> tradeoff to be addressed Using frames defined in 11ax or defining new frames to allow for 11az support Chao-Chun Wang (MediaTek Inc.)

Soliciting Unassociated STAs with Short NDP Operations March 2017 Soliciting Unassociated STAs with Short NDP Operations Using short NDP feedback mechanism to find out how many unassociated STAs are interested in doing ranging Each short NDP random access RU is assigned with an RUid. The MU response frame (in SU PPDU) carries FTM parameters for every STAs, a FTMid (a.k. pre-AID) is assigned to each unassociated STA Chao-Chun Wang (MediaTek Inc)

March 2017 Mode of Operations (SU-MU) An STA send FTM request in SU mode and receive FTM response (in SU PPDU format) for MU operation Pro Con (MU – MU) An STA send FTM request in MU mode and receive FTM response (in SU, MU PPDU format) for MU operation - 1 (MU – MU) An STA send FTM request in MU mode and receive FTM response (in SU, MU PPDU format) for MU operation (MU-MU Operation 2) Chao-Chun Wang (MediaTek Inc)

Motion 1 We agree that Pre-AID per STA used for measurement phase will be assigned in the FTM Rsp frame. Y: N: A: Absent: Ganesh Venkatesan (Intel Corporation)

Straw Poll Do you agree to include the (SU-MU) procedure in the SFD An STA send FTM request in SU mode and receive FTM response (in SU PPDU format) for MU operation Do you agree to include the (MU-MU) procedure in the SFD An STA send FTM request in MU mode and receive FTM response (in SU, or the PPDU format supported by 11ax specification) for MU operation – 1 Do you agree to include the (MU-MU) procedure in the SFD (in SU, or the PPDU format supported by 11ax specification) for MU operation – 2 Y: N: A: Absent: Ganesh Venkatesan (Intel Corporation)