| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Ming, Thanks for your explanation. I think it’s too complicated to schedule GA(group addressed) data cross different links for MLD STA on AP side. For GC data transmission, I do agree below solution in Po-Kai’s contribution.
For the latency STA working on non-primary link, I think GA data can be duplicated on that link like today’s solution. No need to force it to primary link.
Besides, I agree the primary link concept, and we can do further talk on it so that group can accept it too. Thanks Best Regards Jay Yang From: Ganming (Ming) <ming.gan@xxxxxxxxxx> Thanks Jay for your comments “Link specific” means each AP in AP MLD sends its own group address BU, does need to copy the traffic of other AP in the same AP MLD, this just follows the existing delivery scheme. An example
for you, for MLD STAs, it could know which AP has group address BU after DTIM beacon based on notification as described in my contribution such that it could receiver it by the corresponding STA. However, for non MLD STAs, it is not necessary to receive the
group addressed Bus of all the AP because it only cares about some certain AP. Regarding primary link, I did straw poll for this, it seems lots of people does not like this. Moreover, it is not possible for all the Non-AP MLD to choose the same primary link. That means
it will duplicate the group addressed Bus of all the Aps in one AP MLD for each link such that it will bloat the group addressed BU transmission time and do harm to legacy STA and single link STA.
Regarding legacy STA, the same logic. We can not force all the legacy STAs to park only on the same link. What do you think about it? Best wishes Ming Gan 发件人: Yang, Zhijie (NSB - CN/Shanghai) [mailto:zhijie.yang@xxxxxxxxxxxxxxx]
Hi Ming, Thanks for your contribution, I have some comment on it. How to understand the SP that “link specific”? Do you have the details solution that how AP schedule the GC BUs and TX to MLD and non-MLD STAs on different links, which not only guarantee MLD STAs to receive the non-duplicated GC BU, but
also guarantee the non-MLD STAs to receive the whole GC BUs? To make it simple and compatible with the legacy STA, I think it’s better to only allow GC BUs transmission on the primary link/configured link for MLD STA. If there is any non-MLD STA belong to the same group connected to MLD AP on other
link, It’s allowed to duplicate the GC BUs on that link, and MLD STA should ignore these GC BU on it’s non-primary link/non configured link.
Thanks Best Regards Jay Yang From: Ganming (Ming) <ming.gan@xxxxxxxxxx>
Hello all, I proposed that Group addressed BU delivery is link specific and leave this transmission schedule to the AP in this contribution. Because of limited time for Q&A, please tell me if you have any
comments. I try to answer concerns for “switch”, I understand receiving group addressed BU has benefit to the non-AP side. Based on the balance between Rights and Obligations, it indeed requires non-AP
to do something, such as switch. Moreover, it is not needed for single radio MLD to receive group addressed BU by switching frequently because it will park on one link for quite long time. It is not like duplication, it does harm to legacy STA and single
link STA and make every link congested.
Best wishes, Ming Gan 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 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 |