Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[STDS-802-11-TGBE] Follow-up the comments for the CR to #10474, #10888, #10889 in 11-22/1452r2



Hi all,

 

Thanks for the questions and comments raised for the CRs to #10474, #10888, #10889 in 11-22/1452r2 during the 802.11be MAC ad hoc meeting.

 

I would like to follow up to the comments: 

1.      Why it needs to update EPCS EDCA parameters?

a)      After the EPCS service is enabled in the BSS and/or neighbour BSS, the non-EPCS devices would get lower priority which ends up that most traffic in BSS or OBSS would come from EPCS devices (not from non-EPCS devices).

b)     If many EPCS devices require higher priority access, it could create the access congestion caused by EPCS devices (not from non-EPCS devices).

c)      The current 802.11be D2.0 does not allow the EPCS AP MLD to transmit the updated EPCS EDCA parameters carried in EPCS Priority Access Request message in the enabled state (refer to 35.17.2.2.3 Procedures at the originating AP MLD). Therefore, there is no other way to resolve the EPCS devices’ access congestion issue except for tearing-down the EPCS service.

 

2.      Why it needs to update EPCS EDCA parameters via broadcast frames?

a)      Using broadcast frame to update legacy EDCA parameters has already been supported in 802.11 spec.

b)     When the access congestion is caused by EPCS devices, the EPCS AP MLD would not be able to know which EPCS devices are contending to the media and causing the access congestion, and send the unicast an EPCS Priority Access Request frame to those EPCS devices

c)      Using the unicast EPCS Priority Access Request frame to handle the access congestion is not efficient. It can take a long time to update EPCS EDCA parameters of all associated EPCS devices in the EPCS network. 

 

3.      Reliability concern for broadcast EPCS Priority Access Request message

a)      Broadcast message is already used in 802.11, like Beacon frame, Probe Request/Response frame. Current 802.11 supports to carry EDCA parameters in the Beacon frame. Therefore, it should not be a concern of reliability for carrying the EPCS EDCA parameters in the broadcast EPCS Priority Access Request frames in the EPCS service provider managed Wi-Fi networks.

b)     In addition, depending on the EPCS AP MLD’s configuration, the EPCS AP MLD can schedule multiple broadcast frames of EPCS Priority Access Request with the updated EPCS EDCA parameters to improve the delivery success ratio.

Hope those could address the concerns to the CRs.  If there is any comment or suggestion, please let me know.

 

Best Regards

 

Yonggang

 


To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1