| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Duncan, Thanks for your response. Please find my response inline. Regards Guogang Huang 发件人: Duncan Ho <00002b3e54cff3e2-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Guogang, Thanks for your comment. Please see my responses inline below. From: huangguogang <huangguogang1@xxxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Duncan, Thanks for preparing this CR document. One question regarding when to suspend the UL data transmission, I think the following two sentences are conflicted or misaligned with each
other. We should define that the non-AP MLD shall not transmit any Data frames to the current AP MLD upon successful reception of the ST execution response with the Status Code field set to SUCCESS if the SMD Type field in the SMD Capabilities field in
the SMD Information element (see 9.4.2.356 (SMD Information element)) is equal to 0.
[DH] If we follow the above, the UL suspension would be too late. Since the DS mapping may be updated anytime between the ST execution request and ST execution response, if we allow UL to the
current AP MLD this time, any UL packets forwarded to the DS from the current AP MLD will undo the DS mapping update and the DS will point back to the current AP MLD. [HGG]I agree that the UL transmission shall be suspended first. After that, the current AP MLD informs the target AP MLD to update the DS mapping and initiates the
dynamic context transfer. For simplicity, we should define as the above mentioned. I don’t see any issue. (#5017)Upon successful transmission of the ST execution request, the non-AP MLD shall not transmit any Class 3 frames to the current AP MLD if the SMD Type field in
the SMD Capabilities field in the SMD Information element (see 9.4.2.356 (SMD Information element)) is equal to 0. [DH] This condition should be correct, per my explanation above. [HGG]It’s a little over-design. Before receiving ST execution response with SUCCESS,
the non-AP MLD keeps in state 4 with the current AP MLD. Considering this, the non-AP MLD should be allowed to exchange data with the current AP MLD, regardless of the DL data or the UP link. Please update Figure 11-23—Relationship
between state and services between a given pair of nonmesh STAs to accommodate SMD transition.
(#5017)Upon reception of an ST execution response frame with the Status Code field not set to SUCCESS from the target AP MLD, all Class 3 frames shall be allowed between
the current AP MLD and the non-AP MLD. [DH] This is the case when the non-AP MLD receives an ST execution response with some kind of failure (i.e., ST failed), we allow the non-AP MLD to resume UL tx with its current AP MLD. Thanks, Duncan Regards Guogang Huang 发件人: Duncan Ho <00002b3e54cff3e2-dmarc-request@xxxxxxxxxxxxxxxxx>
Dear Seamless Roaming TTT members, I’ve drafted this CR to address the UL data suspension and MLD state change. Could you please review it and let me know if you have any feedback? Hope to see you in Victoria! BR, Duncan 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 |