Thanks Gaurang for the draft, discussions and for incorporating some of my offline comments. I still have few more comments (some of which we discussed about before but I want
to include here for others’ consideration as well):
·
Minor grammatical correction: “An AP affiliated with the AP MLD should end frame exchanges initiated with a STA affiliated with the non-AP MLD in one of the EMLSR links
at least an EMLSR transition delay, indicated in the EMLSR Transition Delay subfield,
before another AP …”
·
Your text seems to have rules on termination of frame exchanges by AP but not on the start of a frame exchange. Why not also have additional text of the form: “An AP affiliated with an AP MLD shall not initiate a frame exchange
with an STA of a non-AP MLD in one of the EMLSR links if:
o
Either the frame exchange duration is expected to overlap with group-addressed frame transmissions on another EMLSR enabled link or the frame exchange duration is separated from group-addressed frame transmission on another
EMLSR enabled link by less than an EMLSR transition delay
o
and
the STA affiliated with the non-AP MLD in the other EMLSR link is expected to receive those group addressed frames”.
I remember you had some text for start time before. Any reason it was removed?
- According to your current text, a frame exchange between an AP and a nonAP EMLSR STA will not be feasible if it overlaps
with a TBTT on any of the other EMLSR enabled links of the nonAP MLD. Considering a 100ms beacon rate and 3 EMLSR links, this can be very inefficient since many potential TXOPs can be lost, as illustrated in red in the figure below. In particular, a nonAP
MLD may decode just one beacon every listen interval (shown in green in the Figure) so preventing TXOP overlap with all TBTTs on all links can be an overkill. Some better mechanism may be required to improve channel access opportunities of EMLSR, especially
considering a nonAP MLD doesn’t decode all beacons. One possible option can be that an EMLSR nonAP MLD elects a primary link to receive group-addressed frames on. There needs to be defined
a mechanism for the EMLSR client to inform the AP about the same and correspondingly the AP operation would be to avoid TXOP overlap with only group addressed frames on this primary link. I bring this up because this is inherently tied to the resolution of
this comment CC6946.
Regards,
Vishnu
From: Gaurang Naik <gnaik@xxxxxxxxxxxxxxxx>
Sent: Monday, January 10, 2022 3:07 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBE] 答复: [STDS-802-11-TGBE] TGbe Teleconferences [01/05/2022, and 01/06/2022]: Agendas Posted
Hi Alfred,
Could you please queue document
1706r1
to the MAC queue?
All,
Kindly let me know if you have any feedback.
Thanks,
Gaurang
From: huangguogang <000017b1384624cd-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Sunday, January 9, 2022 11:13 PM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] 答复: [STDS-802-11-TGBE] TGbe Teleconferences [01/05/2022, and 01/06/2022]: Agendas Posted
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Hi Alfred,
Please add the following contribution to the MAC queue:
11-22-0041-00-00be-Some-issues-on-SCS-operation.pptx
Regards,
Guogang Huang
发件人:
Alfred Asterjadhi [mailto:asterjadhi@xxxxxxxxx]
发送时间: 2022年1月5日 5:36
收件人: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
主题: [STDS-802-11-TGBE] TGbe Teleconferences [01/05/2022, and 01/06/2022]: Agendas Posted
Hello all,
First of all I would like to wish everybody a Happy New Year!
I uploaded an updated version of the agendas, which contains the agenda for the next conference calls,
scheduled on Wednesday January 05 (JOINT), 10:00-12:00 ET and Thursday January 06 (MAC),
10:00-12:00 ET.
The agendas can be found here:
https://mentor.ieee.org/802.11/dcn/21/11-21-1775-18-00be-nov-jan-tgbe-teleconference-agenda.docx
Note for CR documents: Please update the baseline to TGbe D1.31
for the CR documents.
DIAL IN DETAILS FOR WEDNESDAY:
Join the JOINT meeting here: https://ieeesa.webex.com/ieeesa/j.php?MTID=m47e46089d108a8ef448b7a3a11976593
Meeting number: 233 886 75218 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=mff9e3bd94518bedcc608845d389fdd3e
Meeting number: 234 227 52561 Meeting password: wireless (94735377 from phones and video systems)
Let me know if you have any questions and/or suggestions.
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
