Addressing Hidden Node Protection in Coordinated AP Transmissions
Explore the challenges of hidden nodes in multi-AP environments, such as coordinated AP transmissions. The document proposes solutions using MU-RTS/CTS to mitigate hidden node problems. Options for centralized and distributed approaches are discussed to enhance protection mechanisms within BSS. Join the conversation on whether the increased hidden node issue should be tackled by TGbe.
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
May 2020 doc.: IEEE 802.11-20/0933r0 Hidden Node Protection in Coordinated AP Transmissions Date: 2020-06-22 Authors: Name Charlie Pettersson Affiliations Address Phone email dennis.sundman@ericsson.com Dennis Sundman Ericsson Miguel Lopez Submission Slide 1 Dennis Sundman, Ericsson
May 2020 doc.: IEEE 802.11-20/0933r0 Abstract 802.11be shall define coordinated AP transmission mechanism, see section 9.4 in the SFD [1]. As coordinated AP transmission effectively increases the operational spatial domain, the likelihood of hidden nodes increases. The increased hidden node problem emphasizes the need to adapt the TXOP protection mechanisms. This was discussed in [2]. This contribution focuses on the use of MU-RTS/CTS to protect against hidden nodes. Submission Slide 2 Dennis Sundman, Ericsson
May 2020 doc.: IEEE 802.11-20/0933r0 Hidden Node Problem in Multi-AP An example of the problem: AP1 is Sharing AP AP 2 is Shared AP AP3 is an independent BSS STA1 will not be protected without sending a CTS STA2 and AP3 are hidden to AP2 and AP1 AP1 AP3 STA1 AP2 STA2 Submission Slide 3 Dennis Sundman, Ericsson
May 2020 doc.: IEEE 802.11-20/0933r0 Option 1: Centralized The sharing AP is in control of the MU-RTS/CTS procedure Example: Change the MU-RTS such that the sharing AP can request CTS transmissions from STAs in neighboring BSSs Pros: Requires no extra overhead Cons: Does not provide as much coverage as the MU-RTS/CTS in each single BSS Requires some global information (e.g. Global ID information) Submission Slide 4 Dennis Sundman, Ericsson
May 2020 doc.: IEEE 802.11-20/0933r0 Option 2: Distributed Each AP performs local MU-RTS/CTS frame exchanges within their BSS Example: The sharing AP sends a trigger to the shared APs scheduling the local MU-RTS/CTS Pros: Provides similar protection as single cell MU-RTS/CTS No changes needed to the MU-RTS/CTS frames Can be multiplexed with the AP coordination setup frames Cons: Requires some extra overhead compared centralized solution Submission Slide 5 Dennis Sundman, Ericsson
May 2020 doc.: IEEE 802.11-20/0933r0 Straw Poll 1 Do you believe the increased hidden node problem in multi-AP environments (e.g. coordinated AP transmission) should be addressed by TGbe? Yes/No/Abstain: Submission Slide 6 Dennis Sundman, Ericsson
May 2020 doc.: IEEE 802.11-20/0933r0 Straw Poll 2 Do you prefer a centralized solution as in option 1 or a distributed as in option 2 to address the problem in SP 1? (The exact nature of the solution is TBD) Option 1/Option 2/Abstain: Submission Slide 7 Dennis Sundman, Ericsson
May 2020 doc.: IEEE 802.11-20/0933r0 References [1] https://mentor.ieee.org/802.11/dcn/19/11-19-1262-09-00be-specification- framework-for-tgbe.docx [2] https://mentor.ieee.org/802.11/dcn/20/11-20-0643-00-00be-mu-rts-in-multi- ap-operation.pptx Submission Slide 8 Dennis Sundman, Ericsson
