Traffic priority for random Multi User Uplink OFDMA

Slides:



Advertisements
Similar presentations
Doc.: IEEE /1123r0 Submission September 2010 Zhu/Kim et al 1 Date: Authors: [TXOP Sharing for DL MU-MIMO Support]
Advertisements

Submission doc.: IEEE /1013r0 September 2015 Guido R. Hiertz et al., EricssonSlide ae & ax Date: Authors:
Submission doc.: IEEE /1097r1 September 2015 Narendar Madhavan, ToshibaSlide 1 Reducing Channel Sounding Protocol Overhead for 11ax Date:
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.
Submission doc.: IEEE /0085r1 January 2016 Woojin Ahn, Yonsei Univ.Slide 1 Congestion control for UL MU random access Date: Authors:
Submission doc.: IEEE /1116r1 September 2015 Jinsoo Ahn, Yonsei UniversitySlide 1 Trigger Frame Channel Access Date: Authors:
Submission doc.: IEEE /0662r0 May, 2016 Jing Ma, NICTSlide 1 Further consideration on channel access rule to facilitate MU transmission opportunity.
Doc.: IEEE /0591r1 May 2016 SubmissionPatrice NEZOU et al., Canon Issues related to OCW management Date: Slide 1 Authors: NameAffiliationAddress .
Doc.: IEEE /0048r0 SubmissionSlide 1Young Hoon Kwon, Newracom Protection using MU-RTS/CTS Date: Authors: January 2016.
Doc.: IEEE /0333r0 March 2016 SubmissionStéphane Baron et al., Canon Issue related to unused UL OFDMA RUs Date: Slide 1 Authors: NameAffiliationAddress .
Location Measurement Protocol for Unassociated STAs
UL OFDMA Random Access Control
BSS Load Information Element for 11ax
Compressed Uplink Trigger Frame
QoS Handling of Trigger Frame
Preliminary 11ax PAR Verification
Considerations for WUR Response
Differentiated Initial Link Setup (Follow Up)
WUR Acknowledgement Indication
WUR Acknowledgement Indication
Preliminary 11ax PAR Verification
Issue of Buffer Status reporting
Issue of Buffer Status reporting
Issue of Buffer Status reporting
Channel Access Efficiency
MAC Calibration Results
Speaker:Fu-Yuan Chuang Advisor:Ho-Ting Wu Date:
Considerations on Trigger Frame for Random Access Procedure
Issues related to OCW management
2840 Junction Ave. San Jose, CA 95134
RTS*/CTS* for UL/DL OFDMA Control
Issue of Buffer Status reporting
Issue of Buffer Status reporting
Wake Up Response mode to WUR frame
Preliminary 11ax PAR Verification
Follow up on Issue related to unused UL OFDMA RUs
Discussion on CR for CID 5066
Consideration of EDCA for WUR Signal
Functional Requirements for EHT Specification Framework
WUR Acknowledgement Indication
Channel Access Efficiency
Further Consideration for WUR Acknowledgement Indication
Access distribution in ai
Considerations for WUR Response
Comment resolution on CID 20175
DL MU MIMO Error Handling and Simulation Results
MU Synchronization Requirements for SFD
Channel Access Efficiency
Comment resolution on CID 20175
UL MU Random Access Analysis
2840 Junction Ave. San Jose, CA 95134
Random Access UL MU Resource Allocation and Indication
AP Coordination in EHT Date: Authors: Name Affiliations
Reception Status of Frames Transmitted in Random Access RUs
May 2016 doc.: IEEE /584r1 May 2016 Need of SDU Fragmentation to Reduce Padding Ratio in UL-OFDMA Transmission Date: Authors: Yu Wang.
TD Control field with Response indication in WUR frame
Congestion control for UL MU random access
Differentiated Initial Link Setup (Follow Up)
Consideration of EDCA for WUR Signal
Access distribution in ai
AP Coordination in EHT Date: Authors: Name Affiliations
Functional Requirements for EHT Specification Framework
Considerations on Trigger Frame for Random Access Procedure
Further Consideration for WUR Acknowledgement Indication
Month Year doc.: IEEE /1081r0 May, 2016
BSS Load Information Element for 11ax
Location Measurement Protocol for 11ax
Enabling Uplink Persistent Allocation for EHT
Latency enhancement for EHT
Presentation transcript:

Traffic priority for random Multi User Uplink OFDMA Month Year doc: IEEE 802.11-13/xxxxr0 Traffic priority for random Multi User Uplink OFDMA Date: 2015-11 Authors: Name Affiliation Address Email Stéphane BARON Canon Cesson-Sevigné, France stephane.baron@crf.canon.fr Patrice NEZOU patrice.nezou@crf.canon.fr Romain GUIGNARD romain.guignard@crf.canon.fr Pascal VIGER pascal.viger@crf.canon.fr Yonggang Fang, ZTETX

Abstract 802.11ax SFD specifies OFDMA to be supported. [2] A trigger frame (TF-R) enables random access mechanism for MU UL-OFDMA transmissions: Resource Units (RU) can be randomly accessed by more than one STA [1] The selection method of the Random RU is based on an OFDMA Backoff (called OBO). [3] AP may broadcast a Randomization Parameter in trigger frame to help the STAs in their procedure to randomly access an RU. [4] In this contribution, we propose to introduce traffic priority in the Multi user uplink procedure for any 11ax STA receiving a TF-R frame, based on its EDCA traffic prioritization and the AP Randomization parameter.

Background 1/2 CSMA/CA EDCA / IEEE 802.11e std 802.11 is contention based access technology - CSMA/CA, which is originally designated for single STA to occupy the medium in a fairness way. The random backoff procedure is a fully distributed method and ensures the fairness (allocates the channel to stations with roughly the same probability). EDCA / IEEE 802.11e std Enhanced Distributed Channel Access (EDCA), for differentiated QoS Each Access Category (AC) has its own set of channel access parameters (including backoffs), in order to manage local traffic priorities Priority Access Catagory CWmin CWmax AIFSN lowest Background (AC_BK) aCWmin aCWmax 7 Best Effort (AC_BE) 3 Video (AC_VO) aCWmin/2 2 highest Voice (AC_VI) aCWmin/4 EDCA default parameters

Background 2/2 Terminology (as referred in [3] :15/1105r1) : CWO: Contention Window for UL-OFDMA CWOmin, CWOmax : Min and max values for CWO UL-OFDMA Backoff (OBO) Count : A counter maintained by the STA that determines the random access RU the STA utilizes. RU selection process:

Data selection process for MU UL Principle : OBO runs in parallel of EDCA backoff(s), and manages the medium access onto UL-OFDMA. [3] Data stored in the AC queues can be sent through EDCA CSMA/CA medium access or through the OFDMA MU_UL . OFDMA muxer manages traffic priorities by reusing Access Category priorities to select data to be transmitted. Advantages EDCA still runs in parallel, Reuse of the existing AC queues STA locally ensures its EDCA data priority for both CSMA/CA and MU_UL schemes.

Data selection process for MU UL Random selection Selection using AC priorities CWO=64, 64 RU CWO=64, 64 RU Same efficiency Simulation scenario: Full buffer for the 4 AC queues AC backoffs evolve between 2 consecutive TF-R. Local data priority is respected

Data selection process for MU UL Selection using AC priorities only Simulation scenario: Each STA only send one type of data (full buffer for only one AC queue per STA). CWO=64, 64 RU, no Offset Same efficiency Data priority is respected locally, but not between STAs. Additional mechanism required.

OBO determination Advantages ST#4 EDCA introduced the AIFSN concept to apply the AC priorities among the STAs. Similarly, The OBO computing shall take into account the AC priorities using an AC_Offset value (depending of the Current AC). AC_Offset[] values shall be adapted to the number of RUs. Each STA computes its OBO according the formula : OBO=rand[0,CWO]+AC_Offset[Current AC] AC_Offset[] (TBD). Advantages OBO can be adapted to the data priority ready to be sent at the moment of the TF-R reception.

Data selection process for MU UL With Offset usage Simulation scenario: Each STA only send one type of data (full buffer for only one AC queue per STA). CWO=64, 64 RU, Offset : vo=0,vi=0,be=32,bg=64 Same efficiency Data priority between STAs is OK.

CWO computation 1/2 Advantages : ST#2 AP may broadcast a Randomization Parameter in trigger frame to help the STAs in their procedure to randomly access an RU. [4] CWO computation : CWO=CWOmin x 2CRF A Collision Risk Factor (CRF) is a multiplication factor reflecting the probability of transmission error to be taken into account in the congestion window computation. The CRF can be provided by the AP (optional Randomization Parameter [4]) or computed locally by each STA based on its previous MU UL transmission status. Randomization Parameter received from AP is priority compared to locally computed CRF value. Advantages : 2CRF factor reflects the successive “doubling” of the CWO. Use of AP randomization parameter for CWO computation enhances the RU usage efficiency, since AP has a global view of the MU UL session efficiency. Locally computed CRF allows CWO adaptation when optional Randomization Parameter is not provided by the AP.

CWO computation 1/2 Simulation scenario: Simulation scenario: Each STA only send one type of data (full buffer for only one AC queue per STA). CWO = constant No CWO evolution mechanism Simulation scenario: Each STA only send one type of data (full buffer for only one AC queue per STA). CWO=CWOmin x 2 CRF CWOmin = Number of RU With CWO evolution mechanism

CWO computation 2/2 CWO is in the range [CWOmin, CWOmax]. [3] ST#3 CWO is in the range [CWOmin, CWOmax]. [3] CWOmin = number of random RU. CWOmin shall be adapted according to the number of RU defined by a TF-R. [3] CWOmin shall be determined upon each TF-R reception. CWOmax= fct( AC_Priority_Factor[Current AC] ) CWOmax shall be adapted according to the current highest priority of the data contained in AC queues : Fct() is TBD. AC_Priority_Factor[] (TBD) shall reflects the ratio between AC priorities as defined in EDCA. possible TBD values may follow EDCA ratio : (Vo=7, Vi=15, Be=1023, Bg=1023). Current AC is the AC of the highest priority among active AC queues (AC queues priority determined based on AC backoff values). Advantages CWO can be adapted dynamically if Nb of RUs changes between two successive TF-R. MU_UL medium access scheme follows the AC priority under high collision rate.

CWO computation 2/2 Simulation scenario: Each STA only send one type of data (full buffer for only one AC queue per STA). 8 RU CWO = CWOmin*2 CRF

Data priority handling for Random procedure Principle : Upon TF-R reception If No active OBO STA compute the CWO based on NbRu, Collision Probability, and data priority. Collision Probability received from AP is priority compared to locally computed value. STA computes a new OBO from CWO + an offset based on data AC. STA selects an RU [3]. STA transmits data Select the data with the highest priority Transmit the data on the selected RU. STA updates locally the collision probability: Advantages The proposal is respectful of the data priority defined in EDCA. Use of AP randomization parameter for OBO computation reduces the probability of RU collision. ST#3 ST#2 ST#4 ST#1

Data priority handling : example of application Principle : Upon TF-R reception If No active OBO STA compute the CWO: CWO = CWOmin * 2CRF Collision Risk Factor computed locally (TBD), and/or received from the AP (e.g. Transmission probability control) provided by AP in the trigger frame CWO is in the range [CWOmin, CWOmax] Typically: CWOmin = number of random RUs of TF-R (theoretical optimal value [3]) CWOmax = CWmaxac , wherein ac is the current highest priority AC queue (this limit may evolve if data is stored in another queue with higher/lower priority) STA computes a new OBO from CWO OBO = rand [0 , CWO] + AC_Offset : Offset values based on NbRu and the Current_AC (TBD) (e.g VO=0, VI=0, BE=max(1,NbRU/4), BG=max(2,NbRU/2)) STA selects an RU. STA transmit data Select the data with the highest priority (e.g : data in the AC[] queue having the lowest backoff) Transmit the data on the selected RU. STA update locally the CRF : Upon successful transmission CRF=0. Upon transmission failure : CRF=CRF+1.

Summary In this presentation, we proposed to introduce traffic priority in the Multi user uplink procedure for any 11ax STA receiving a TF-R frame, based on its EDCA traffic prioritization and the AP Randomization parameter : A data selection process for MU UL reusing the AC queues. A CWO computation mechanism, including the CWOmin, and CWOmax initialization based on the AC priorities, and on a Collision Risk Factor (CRF) reflecting the probability of transmission error. An OBO determination mechanism including an AC_Offset value reflecting the data priority ready to be sent at the moment of the TF-R reception.

References [1] IEEE 802.11-15/0875r1 “Random Access with Trigger Frames using OFDMA” [2] IEEE 802.11-15/0132r2 “Specification Framework for Tax” [3] IEEE 802.11-15/1105r0 “UL OFDMA-based Random Access Procedure” [4] IEEE 802.11-15/1137r1 “Triggered OFDMA Random Access Observations”

Straw-poll 1 Do you agree to add to the TG specification framework document? The spec shall define a procedure for the data selection upon random trigger frame reception, respectful of AC priorities: OFDMA MU_UL muxer picks data from AC queues. OFDMA MU_UL muxer follows traffic priorities of Access Categories to select data to be transmitted. Yes: No: Abstain:

Straw-poll 2 Do you agree to add to the TG specification framework document? The spec shall define a Collision Risk Factor (CRF) reflecting the probability of transmission error to be taken into account in the CWO computation according to the formula: CWO = CWOmin x 2CRF The CRF can be provided by the AP (optional Randomization Parameter [4]) or computed locally by each STA based on its previous MU UL transmission status. Randomization Parameter received from AP is priority compared to locally computed CRF value. Yes: No: Abstain:

Straw-poll 3 Do you agree to add to the TG specification framework document? A STA shall compute the CWOmin and CWOmax values upon TF-R reception. The CWOmin value shall be adapted according to the number of RU (NbRu) defined by the received TF-R, and the CWOmax shall be adapted (AC_Priority_Factor[] is TBD) according to the current highest priority (CurrentAC) of the data contained in AC queues. The resulting formulas for the CWOmin and CWOmax shall be: CWOmin=NbRu CWOmax=fct (AC_Priority_Factor[Current AC] ) Yes: No: Abstain:

Straw-poll 4 Do you agree to add to the TG specification framework document? The STA shall compute the OBO from CWO + an offset based on data AC according to the formula : OBO=rand[0,CWO]+AC_Offset[Current_AC](TBD) Yes: No: Abstain:

Backup slides

AC usage % 4RU 8RU 16RU 32RU 4RU 8RU 16RU 32RU Offset : (0,8,32,32), CWOmax : (32,64,128,128) 4RU 8RU 16RU 32RU

Random selection Efficiency Cwo= 64