
EHT TF User Info Field Proposal
"This proposal focuses on including a special user info field in EHT TF variants, ensuring unified processing of common information. Details cover the presence and handling of the field in different TF types, with specific guidelines for MU-RTS and RU allocation indication. The goal is to streamline information parsing and maintain consistency across EHT implementations." (295 characters)
Download Presentation

Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
March 2021 doc.: IEEE 802.11-21/0485r3 EHT TF Clarifications Date: 03/17/21 Authors Xiaogang Chen Po-Kai Huang Alexander Danny Cheng Chen Laurent Cariou Email Xiaogang.c.chen@intel.com Submission Slide 1 Xiaogang Chen, etc. Intel
March 2021 doc.: IEEE 802.11-21/0485r3 Background TGbe agreed to define a special user field (with AID = 2007) to carry the extra EHT common info for general TF. This contribution focuses on Presence of the special user info field (AID 2007) in different TF types; MU-RTS RU allocation indication. Submission Slide 2 Xiaogang Chen, etc. Intel
March 2021 doc.: IEEE 802.11-21/0485r3 Presence of the special user info field Proposal: All types of EHT TF shall always include the special user info field (with AID=2007) right after the common field. Guarantee a unified processing on the EHT common information (including the HE common info field and special user info field); Rx only adjusts common info parser based on B55 instead of based on both B55 and TF types. B55 (presence of the special user field) -> Parse EHT common info if B55 = 0; otherwise Parse HE common info. Submission Slide 3 Xiaogang Chen, etc. Intel
March 2021 doc.: IEEE 802.11-21/0485r3 SP1 Do you agree: The special user info field (user info field with AID=2007) shall be present in all the EHT TF variants defined in 11be R1. For the EHT variant of MU-RTS, all the bits in the special user info field are reserved except the BW Extension subfield and AID 12 subfield. Submission Slide 4 Xiaogang Chen, etc. Intel
March 2021 Background of the RU allocation in HE MU-RTS doc.: IEEE 802.11-21/0485r3 RU allocation in HE MU-RTS Indicates on which 20MHz subchannels the CTS will be transmitted; Use the entries (61-68) corresponding to the RU 242/484/996/996*2 in the HE RU allocation table; Only allow CTS transmits on P20/P40/P80/160MHz; No puncturing information included in the RU allocation. Submission Slide 5 Xiaogang Chen, etc. Intel
March 2021 Design goal of the RU allocation in EHT MU-RTS doc.: IEEE 802.11-21/0485r3 Using HE MU-RTS as baseline and extending with EHT features: 320MHz CTS response support; Straight forward. CTS response on non-contiguous 20MHz subchannels; Straight forward. EHT MU-RTS trigger CTS from both HE and EHT STA. Transparent to HE and EHT STA; Fully controlled by AP, no need to standardize. Submission Slide 6 Xiaogang Chen, etc. Intel
March 2021 doc.: IEEE 802.11-21/0485r3 RU allocation in EHT MU-RTS Proposal: RU allocation in EHT MU-RTS reuse the RU allocation defined for general EHT TF; For a non-AP STA, the CTS responses to EHT MU-RTS shall be transmitted on the 20MHz subchannel(s) that are overlapped with the large size RU/MRU indicated by its own RU allocation subfield. Submission Slide 7 Xiaogang Chen, etc. Intel
March 2021 doc.: IEEE 802.11-21/0485r3 SP2 Do you agree that The CTS response to MU-RTS supports all the modes in 11ax and 320MHz non-HT duplicate transmission; The CTS response to MU-RTS supports transmitting on non- contiguous 20MHz subchannels; The CTS response to MU-RTS is transmitted on the 20MHz subchannel(s) that are overlapped with the large size RU indicated by its own RU allocation subfield; The CTS response to MU-RTS shall be transmitted including the primary 20MHz channel. Note: This SP is for R1. Submission Slide 8 Xiaogang Chen, etc. Intel
March 2021 doc.: IEEE 802.11-21/0485r3 Backup Submission Slide 9 Xiaogang Chen, etc. Intel
March 2021 doc.: IEEE 802.11-21/0485r3 Valid Large RU indication in MU-RTS PS160 subfield B0 of RU Allocation subfield PHY RU index B7-B1 Allocation subfield of RU Bandwidth RU size RU index 4 N + RU index RU1 20, 40, 80, 160, or 320 MHz 61 40, 320 MHz 80, 160, or RU2 62 RU3 respectively and RU4, 63, 64 80, 160, or 320 MHz 242 40, 320 MHz 80, 160, or RU1 65 2 N + RU index 484 RU2 66 80, 160, or 320 MHz RU1 N + RU index 67 80, 160, or 320 MHz 996 0-1: 0 Reserved Reserved 160 MHz segment where located 1 RU1 LU160 + RU index 68 RU is 2 996 160, or 320 MHz 0 0 0 1 Reserved 69 1 0 Reserved 4 996 1 1 320 MHz RU1 RU1 Submission Slide 10 Xiaogang Chen, etc. Intel
March 2021 Valid Large MRU indication in MU-RTS doc.: IEEE 802.11-21/0485r3 PS160 subfield B0 of RU Allocation subfield PHY RU index B7-B1 Allocation subfield of RU Bandwidth RU size RU index 4 N + RU index MRU1 to MRU4, respectively 90 93 80, 160, or 320 MHz 484+242 4 LU160 + RU index 0-1: 0 MRU1 to MRU2, respectively 94 95 160, or 320 MHz 996+484 1 MRU3 to MRU4, respectively 160 where RU is located MHz segment 8 LU160 + RU index 0-1: 0 MRU1 to MRU4, respectively 96-99 160, or 320 MHz 996+484+242 1 MRU5 to MRU8, respectively 160 where RU is located MHz segment 0 0 MRU1 to MRU4, respectively RU index 0 1 MRU5 to MRU6, respectively 100-103 320 MHz 2x996+484 1 0 MRU7 to MRU8, respectively 1 1 MRU9 respectively to MRU12, 0 0 MRU1 0 1 MRU2 1 0 MRU3 104 320 MHz 3x996 1 1 MRU4 RU index 0 0 MRU1 to MRU2, respectively 0 1 MRU3 to MRU4, respectively 1 0 MRU5 to MRU6, respectively 105-106 320 MHz 3x996+484 1 1 MRU7 to MRU8, respectively RU index Submission Slide 11 Xiaogang Chen, etc. Intel
March 2021 doc.: IEEE 802.11-21/0485r3 Special user info field B0 B11 B12 B14 B15 B16 B17 B20 B21 B24 B25 B36 B37 B39 U-SIG Disregard And Validate Reserved Trigger Dependent User Info PHY Version ID UL Extension Bandwidth Spatial Reuse 1 Spatial Reuse 2 AID12 Bits: 12 3 2 4 4 12 3 variable Submission Slide 12 Intel