Hi Dmitry,
I have comments on the second bullet.
- The “up-limit” of DS transmissions is not “ETSI” regulation. It is only a requirement related for the operation of SCS in ETSI BRAN HS.
- How to address “up-limit” requirement from different county/region if it is different from the number in the SP?
Thanks
Yonggang
From: Yue Qi <yue.qi@xxxxxxxx>
Sent: Wednesday, March 12, 2025 2:08 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] P-EDCA SP2
|
|
External email : Please do not click links or open attachments until you have verified the sender or the content.
|
I understand that the last bullet aims to prevent excessive use of P-EDCA, which is a reasonable concern and aligns with the intent of the second bullet. However, I’m wondering if this restriction might unintentionally create an issue in cases where a STA
still has buffered low-latency traffic but reaches the DS transmission limit, especially the TBD number is small.
If that happens, the STA is forced back to regular EDCA and may struggle to access the channel within its delay bound—especially if there are still other STAs contending for P-EDCA access. This concern becomes more significant if the TBD limit is quite small.
If the limit is large enough, the second bullet may already address the issue.
Yue
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
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
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
|