| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Sindhu，
Editing the subject slightly and adding the TGbn mailing listHi Yuxin,
Thanks for reaching out.
The use case you are describing can have only the following options:
There is a non-AP MLD which has an STR relationship between a link in 5GHz and a link in 6GHz (because that is where DSO can be enabled) . That STR relationship can turn to NSTR when DSO is enabled. However, there can never be a possibility of an NSTR relationship turning to STR. The mechanism you are proposing to define covers possibilities in both directions and hence, not suitable
Even then, the NSTR or STR relationship for a pair of links with a certain bandwidth is supposed to be static across multiple enablements and disablements. Again, the mechanism you are proposing allows for a dynamic change in this relationship every time DSO is enabled or disabled.
[Yuxin] The NSTR or STR relationship depends on the location of the DSO subband, which is negotiated via the OMP procedure. I suppose the NSTR or STR relationship needs to be signaled together with the OMP procedure (my initial proposal in r1). But as you suggested, it should remain the same until the DSO subband is renegotiated. Another option is that the non-AP STA signals its NSTR status by considering the AP's operating bw as its own, which I think may not be very reasonable and is inefficient.
Hence, I request you to reconsider your design and at most propose a static negotiation mechanism which is usable only if the non-AP MLD is already STR between a pair of links. The negotiation of the worst case relationship is also a good alternative as it is not clear if 2 NSTR links with DSO on one or both of them can give gains over 2 STR links without DSO.
[Yuxin] Thanks for this recommendation. In summary, the negotiation of the worst case relationship can be done together with the negotiation of the DSO subband via the OMP procedure, and remain the same until the DSO subband is renegotiated. What do you think?
Regards,
Sindhu
Hi Gaurang, Morteza, Sindhu, and Dibakar,cc Mikaël,This is Yuxin from TCL.Thanks for your comments during yesterday's joint call. Didn't have time to respond then. Let me reply together here for efficient communications before continuing the discussion next Thursday.Correspondingly, a revised revision of CR 25/0793 is attached per your comments and my reply below. Please kindly review it and let me know your further recommendations. Thanks a lot.Q from Gaurang: Why can't the non-AP MLD use the frame that was defined in 11be? Put other way, are there any changes needed to handle this case？[Yuxin] This NSTR update is effective along with the DSO enablement, so it would be more effective to send it as DSO parameters (which is a one-round handshake), compared to sending it using a separate signaling (which requires a two-round handshake)If you prefer a two-round handshake, using the legacy frame, I suppose it also works, but it is less efficient.Please refer to the attached document, which addresses your comments. ThanksQ from Morteza: When enabling DSO, non-AP STA can indicate its NSTR status based on worst case, using the current mechanism[Yuxin] As replied to Gaurang, using the legacy frame also works, but is less efficient, since it requires a two-round handshake: UHR OMP request/response, EHT NSTR status update procedure.Agree with you that the NSTR status can be based on the worst case, and it requires additional capability to determine this worst case result. Therefore, it is necessary to indicate a new capability instead of mandating every DSO non-AP to do this.Please refer to the attached document, which addresses your comments. ThanksHi Sindhu:Please review the revised doc and provide your comments. ThanksQ from Dibakar: STA is NSTR during DSO and STR otherwise？[Yuxin] Indeed, this is the bottleneck case where the AP MLD is unaware of such a status change, does not follow the NSTR transmission limitations during DSO, and transmission may fail or interfere with the other link. The DSO subband is beyond the operating bandwidth of the non-AP STA, so this certainly may happen.Have a good day. Looking forward to hearing from you. :)--Best Regards,Yuxin
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