| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Wook Bong, I think for R1 a simplified signaling is sufficient since the goal is for the AP to find a better channel to switch to. A detailed, more granular signaling may be left for R2.
Regards, Dibakar From: Wook Bong Lee <wookbong.lee@xxxxxxxxxxx> Hi Dibakar and all, I just noticed that the 11-21/222r11 contains “Frequency Separation for STR” subfield. I think this should be discussed in PHY or Joint as it is related to PHY design. In my opinion, just relying on frequency separation will result in non-optimal STR channel selection. In order to make STR happen, there are a certain level of Tx-Rx isolation is required. One of method to make this isolation is filter-bank based design. In this design, whether a device can be STR or not is depending on which subbands will be paired not based on the distance between two link’s frequency. In this case, depending on the channel selection, the frequency separation value required is different. For example, if one device can operate STR using lower 5GHz band and lower 6GHz band. The gap between two channels are different for different channel within the (sub)band. If the frequency separation for STR is static value from non-AP STA, then what the non-AP STA can report is worst case value which means the reported gap will be much larger than most of case which results in
non-optimal operation. Can you please consider this? Best regards, Wook Bong Lee From: Payam Torab [mailto:torab@xxxxxxxx]
Hi Dibakar, how do we reconcile the “Frequency Separation for STR” field and this paragraph, An MLD shall set to 0 every bit in the NSTR Indication Bitmap subfield that corresponds to a link pair where one of the STAs in the link pair operates in the 2.4 GHz band and the other STA operates in the 5 GHz
or 6 GHz band. (seems like the paragraph is putting a max on the “Frequency Separation for STR” field; and if true, why not just specify that). Also it seems there was no merge between -r10 and -r11 (or some changes missing). Thanks. From:
Das, Dibakar <dibakar.das@xxxxxxxxx> Hi Payam, all, I just uploaded r11. Key difference with the previous versions is the insertion of a field that signals the minimum frequency separation required for a non-AP STA to operate in an STR link pair. Regards, Dibakar From: Payam Torab <torab@xxxxxxxx>
Thanks Dibakar, fine with including MLD Capabilities Present. Nits: missing spaces after both math signs in each instances of “(where
0 ≤i <15)” (personally prefer to drop the word “where” too). Do you plan to upload a clean version? From:
Das, Dibakar <dibakar.das@xxxxxxxxx> Hi Payam, I incorporated some of your changes. Please see the attached revision.
On the inclusion of the MLD Capabilities Present bits, you are right in that this text is now out of scope for this document since we moved the bitmap signaling entirely to per-STA Profile. However, the problem now is that we do need to
have this text in the spec somehow. Otherwise the text related to the NSTR Capability signaling that Yunbo has already motioned in would be incomplete. Since the alternative is to create yet another PDT in the interest of time, I would prefer to keep this
text as it is even though its not aesthetically correct. Regards, Dibakar From: Payam Torab <torab@xxxxxxxx>
Hi Dibakar, some comments, cleanup on 11-21/0222r10 attached. One general comment is with the per-STA profile encoding, text related to MLD capability seems to be out of scope of this document. Regards, From:
Das, Dibakar <dibakar.das@xxxxxxxxx> Hi Alfred, Can you please add the following submissions to the queue for PDTs:
11-221-r0-PDT-MAC-MLO-NSTR-blindness-TBD 11-222-r0-PDT-MAC-Common Info-ML
element ? Regards, Dibakar From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Hello all, I uploaded an updated version of the agendas, which contains the agenda for the next conference calls, scheduled on Wednesday, February 03 (JOINT), 10:00-12:00
ET and Monday, February 04 (MAC/PHY), 10:00-12:00 ET. The agendas can be found here: DIAL IN DETAILS FOR WEDNESDAY: Join the JOINT meeting here: https://ieeesa.webex.com/ieeesa/j.php?MTID=m938efd59d1679c848a5d00938211c10c Meeting number: 179 164 5256 Meeting password: wireless (94735377 from phones and video systems) DIAL IN DETAILS FOR THURSDAY: Join the MAC meeting here:
https://ieeesa.webex.com/ieeesa/j.php?MTID=m7bedf9dab22edc153d81df908244c782
Meeting number: 179 921 0663 Meeting password: wireless (94735377 from phones and video systems) Join the PHY meeting here:
https://ieeesa.webex.com/ieeesa/j.php?MTID=mac3ed043b2d78dee8d6e4189877807ee Meeting number: 179 655 7388 Meeting password: wireless (94735377 from phones and video systems) Please let me know if you have any questions and/or clarifications. Best Regards, Alfred -- Alfred Asterjadhi, PhD IEEE802.11 TGbe Chair, Qualcomm Technologies Inc. Cell #: +1 858 263 9445 Office #: +1 858 658 5302 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 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 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 |