Dmitry,
The current text seems to merge two aspects:
- Support for P-EDCA by APs. I don’t feel that has been discussed to the same degree as support by non-AP STAs. What does support by
APs mean? Do they engage in post-defer contention with other APs? With non-AP STAs? Both? Do APs have any additional advantage in post-defer contention?
- Seems clear that AP needs mechanism to control whether or not non-AP STAs in the BSS are allowed to use the feature, so need to include
that requirement, making it conditional on use of P-EDCA by non-AP STAs.
Would help if the SP created clear separation between these issues and clarified what the behavior to the extent possible.
John
From: Akhmetov, Dmitry <Dmitry.Akhmetov@xxxxxxxxx>
Sent: Tuesday, March 11, 2025 11:44 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [EXTERNAL] [STDS-802-11-TGBN] P-EDCA SP2
Greetings everyone,
Today I tried to run SP2 on which touches P-EDCa enablement
SP2: Dmitry Akhmetov, Channel Access: 24/1918r1:
- Do you support that a STA may use HIP EDCA
- If HIP EDCA option is enabled by the AP to which that STA is associated to
- May transmit up to TBD but no more than 50 transmissions of DS and up to 2.5 ms of total transmission time to start HIP EDCA contention over 50ms interval
- Note: ETSI regulation of Short Control Signaling transmission
- Shall not initiate more than TBD number of transmissions of DS to start HIP EDCA consecutively.
- Note: consecutive DS transmission are multiple attempts to perform HIP EDCA contention w/o falling back to regular EDCA operation
Given SP results, it looks like the group would like to have more discussion.
Would you please provide your comments in this email thread so we can progress towards successful resolution.
Thank you
Dmitry
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1