Considerations on Trigger Frame for Random Access Procedure

Slides:



Advertisements
Similar presentations
Submission doc.: IEEE /1097r1 September 2015 Narendar Madhavan, ToshibaSlide 1 Reducing Channel Sounding Protocol Overhead for 11ax Date:
Advertisements

Doc.: IEEE /1280r1 November 2015 SubmissionStéphane Baron et. al., Canon Traffic priority for random Multi User Uplink OFDMA Date: Slide.
Doc.: IEEE /1047r0 September 2015 SubmissionStéphane Baron et. al., Canon Random RU selection process upon TF-R reception Date: Slide.
Doc.: IEEE /1052r0 SubmissionSlide 1Young Hoon Kwon, Newracom Bandwidth for UL MU Transmission Date: Authors: September 2015.
Submission doc.: IEEE /0085r1 January 2016 Woojin Ahn, Yonsei Univ.Slide 1 Congestion control for UL MU random access Date: Authors:
Doc.: IEEE /0591r1 May 2016 SubmissionPatrice NEZOU et al., Canon Issues related to OCW management Date: Slide 1 Authors: NameAffiliationAddress .
Multi-STA BA Design Date: Authors: March 2016 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
Signalling Support for Full Bandwidth MU-MIMO Compressed SIG-B Mode
UL OFDMA Random Access Control
Triggering the Broadcast Probe Response
TDMA for Eliminating Hidden Station Effect in Dense Networks
Month Year doc.: IEEE yy/xxxxr0 July 2017
Random Access RU Allocation in the Trigger Frame
Random Access RU Allocation in the Trigger Frame
Considerations for WUR Response
Wi-Fi Time Sensitive Networking
WUR Acknowledgement Indication
Results for Beacon Collisions
Traffic priority for random Multi User Uplink OFDMA
Channel Access Efficiency
Wake Up Frame to Indicate Group Addressed Frames Transmission
Resource Allocation for Unassociated STAs – Follow Up
Issues related to OCW management
11az STA Polling for MU NDP Ranging
UL OFDMA-based Random Access Parameter Set (RAPS) element
Resource Negotiation for Unassociated STAs in MU Operation
Results for Beacon Collisions
Performance evaluation of Real Time Communication over Wi-Fi
Address field in WUR frame
Default UORA Parameters
Random Access RU Allocation in the Trigger Frame
Follow up on Issue related to unused UL OFDMA RUs
11az STA Polling for MU NDP Ranging
Address field in WUR frame
Discussion on CR for CID 5066
Discussion on Group ID Structure
Random Access RU Allocation in the Trigger Frame
Performance evaluation of Real Time Communication over Wi-Fi
WUR MAC and Wakeup Frame
Enabling Frame Body Capture Effect
Channel Access Efficiency
Further Consideration for WUR Acknowledgement Indication
Performance evaluation of Real Time Communication over Wi-Fi
Regarding buffer status of UL-STAs in UL-OFDMA
Considerations for WUR Response
Performance evaluation of Real Time Communications over Wi-Fi
Comment resolution on CID 20175
TDMA for Eliminating Hidden Station Effect in Dense Networks
MU Synchronization Requirements for SFD
Explicit Block Ack Request in DL MU PPDU
Performance evaluation of Real Time Communications over Wi-Fi
Channel Access Efficiency
Random Access UL MU Resource Allocation and Indication
Triggering the Broadcast Probe Response
Reception Status of Frames Transmitted in Random Access RUs
Discussion on Group ID Structure
Congestion control for UL MU random access
WUR MAC and Wakeup Frame
Channel Access for WUR FDMA
Address field in WUR frame
Considerations on Trigger Frame for Random Access Procedure
Address field in WUR frame
Further Consideration for WUR Acknowledgement Indication
Month Year doc.: IEEE /1081r0 May, 2016
Location Measurement Protocol for 11ax
Regarding trigger frame in UL MU
A unified transmission procedure for multi-AP coordination
Presentation transcript:

Considerations on Trigger Frame for Random Access Procedure Month Year Doc Title March 2016 Considerations on Trigger Frame for Random Access Procedure Date: 2016-03-14 Authors: Name Affiliation Address Phone Email Evgeny Khorov IITP RAS khorov@frtk.ru Anton Kiryanov   kiryanov@iitp.ru Sigurd Schelstraete Quantenna sigurd@quantenna.com Huizhao Wang hwang@quantenna.com IITP RAS John Doe, Some Company

March 2016 Background In [1] it was first proposed to define a Trigger frame that allocates resources for random access. In [2] UL OFDMA-based Random Access Procedure was proposed with some analytics. But the existed procedure is not absolutely clear and many issues are open both in the spec framework [3] and in the standard draft [4]. In this presentation, we identify several open issues in UL OFDMA-based Random Access Procedure and try to clarify them. IITP RAS

Random Access Procedure from [3,4] March 2016 Random Access Procedure from [3,4] When a STA has a frame to send, it initializes its OBO (OFDMA Back-off) to a random value in the range 0 to OCW (OFDMA Contention window). A STA decrements its OBO by the number of RUs assigned to AID value TBD in a TF-R unless OBO=0. A STA with OBO decremented to 0 randomly selects any one of the assigned RUs for random access and transmits its frame. OBO for any STA can only be 0 once every TF-R. How a STA shall select the CWO value? IITP RAS

March 2016 OCWmax An HE AP indicates the value of OCWmin for the random access operation. The method of indication of the OCWmin value is TBD. [4] It is naturally that at the very beginning an HE STA selects OCW=OCWmin If the HE AP does not change OCWmin later, the protocol shall allow to resolve collisions, if any. To reduce contention in case of unsuccessful transmission attempt triggered by a Trigger frame for random access, OCW is doubled similar to CW in DCF until it reaches OCWmax. The OCWmax value may be indicated by an HE AP similarly to the OCWmin value. How an HE STA shall modify OCW value in case of collisions? IITP RAS

March 2016 Restarting backoff The method of indication of the OCWmin value is TBD. Anyway, this value can be changed with time, since contention conditions change. Shall an HE STA restart backoff when an HE AP indicates new OCWmin and OCWmax values? If both values are the same as the previous ones, backoff shall not be restarted. If the current OCW is in the range of new OCWmin and OCWmax, backoff shall not be restarted. Otherwise, it shall be restarted. IITP RAS

March 2016 Indication of OCW The method of indication of the OCWmin value is TBD. Since contention conditions change, an HE AP can adaptively advertise OCWmin and OCWmax in Trigger frames for random access and may be in other frames (e.g. beacons). IITP RAS

Straw Poll #1 Do you agree to add the following text in SFD: Month Year Doc Title March 2016 Straw Poll #1 Do you agree to add the following text in SFD: x.y.z. In case of unsuccessful transmission attempt triggered by a Trigger frame for random access, OFDMA Contention Window (OCW) is doubled (similar to CW in DCF) until it reaches OCWmax. Y N A IITP RAS John Doe, Some Company

Straw Poll #2 Do you agree to add the following text in SFD: Month Year Doc Title March 2016 Straw Poll #2 Do you agree to add the following text in SFD: x.y.z. An HE AP indicates the values of OCWmin and OCWmaх for the UL random access operation. The method of indication of the OCWmin and OCWmax values is TBD. Y N A IITP RAS John Doe, Some Company

Straw Poll #3 Do you agree to add the following text in SFD: Month Year Doc Title March 2016 Straw Poll #3 Do you agree to add the following text in SFD: x.y.z. An HE AP can indicate the values of OCWmin and OCWmaх in a Trigger frame for random access. Y N A IITP RAS John Doe, Some Company

Straw Poll #4 Do you agree to add the following text in SFD: Month Year Doc Title March 2016 Straw Poll #4 Do you agree to add the following text in SFD: x.y.z. When an HE AP changes contention window parameters (OCWmin and OCWmax) for the UL random access operation, an HE STA shall restart the OFDMA Back-off unless: contention window parameters are the same as the previous ones; the current OCW is in the range of new OCWmin and OCWmax. Y N A IITP RAS John Doe, Some Company

March 2016 References [1] IEEE 802.11-15/0604r1 “Random Access with Trigger Frames using OFDMA” [2] IEEE 802.11-15/1105r0 “UL OFDMA-based Random Access Procedure” [3] IEEE 802.11-15/132r15 “Specification Framework for TGax” [4] IEEE 802.11-16/0024r1 “Proposed TGax draft specification” IITP RAS