| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
“Sometimes it is not the maximum value of the padding delay since the padding for different feature may starts from
the different location in the Trigger frame. [cm] Would you elaborate more on what is the case in your mind for this? Based on the current draft, the recipient is expected to start switching when the padding starts, no? 发件人: Liwen Chu <liwen.chu@xxxxxxx>
Hi Chaoming, Thanks. Please find my replies below. Best Regards, Liwen From:
罗朝明(Chaoming Luo) <luochaoming@xxxxxxxx>
Hi Liwen, For 1090r0, a max of 256 us with unit of 4 us does not need 8 bits. Or, you may add text saying
“65 to 255 are reserved”. [Liwen]The maximum value of 256us with unit of 4us implies 65 to 255 are reserved. For 1097r0, I’m wondering whether it is possible to solicit a DPS STA switching to HC mode (e.g., 160 MHz)
and switching to the DSO subband (e.g., S160 in 320 MHz) at one shot. In such a case, a max of DPS padding delay and DSO padding delay would be needed. [Liwen] Yes it is possible. The following change in 1097 is the related text
—
The padding shall satisfy the padding requirement of each feature enabled by the UHR STA independently where the padding requirement is
—
the value in the UHR STA’s DPS Padding Delay field for enabled DPS feature,
—
the value in the UHR STA’s DSO Padding Delay field for enabled DSO feature, —
the value in the EMLSR Padding Delay field of the non-MLD with which the UHR STA is affiliated for enabled EMLSR feature. “satisfy the padding requirement of each feature enabled by the UHR STA independently” means the maximum value of DPS padding delay and DSO switch delay in your example. Sometimes
it is not the maximum value of the padding delay since the padding for different feature may starts from the different location in the Trigger frame. That is why the text in 1097 is proposed. BR, Chaoming 发件人: Liwen Chu <liwen.chu@xxxxxxx>
Hi Alfred, Please add the following contribution to the MAC agenda https://mentor.ieee.org/802.11/dcn/25/11-25-1097-00-00bn-cc50-mac-cids-in-clause-37-14.docx Best Regards, Liwen From: Liwen Chu
Hi Alfred, Please add the following contribution to the MAC agenda https://mentor.ieee.org/802.11/dcn/25/11-25-1094-00-00bn-cr-cc50-mac-cids-in-clause-37-13.docx Best Regards, Liwen From: Liwen Chu
Hi Alfred, Please add the following contribution to the MAC agenda https://mentor.ieee.org/802.11/dcn/25/11-25-1090-00-00bn-cr-cc50-mac-cids-in-clause-9-4-1-85.docx I will upload my other contributions by the end of this week. Best Regards, Liwen From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Hello all, I ported the table that Ross prepared to our teleconference agenda and am tracking with requests and progress in the CR stage. POCs, please help populate the missing rows.
Tracking of TBDs in TGbn D0.3.
Regards, AA --
Alfred Asterjadhi, PhD IEEE802.11 TGbe/TGbn Chair, Qualcomm Technologies Inc. Cell #: +1 858 263 9445 Office #: +1 858 658 5302 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 |