Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Dibakar, I see your point, and I agree not to limit the mechanism to the cascading. I also clarify that at least in R1, the scheduled station is associated to the AP (even if its peer is potentially outside of the BSS) So I propose to amend my SP text as follow. “Do you support that 11be defines a procedure for an AP to share a part of the obtained TXOP for peer-to-peer (STA-to-STA) frame exchanges by signaling an RU for P2P communication in a trigger frame, the “UL Length”
field specifying the allocated time for the peer to peer communication, and the RU being allocated to a non-AP STA associated to the AP? Note: The trigger frame may be included in a cascading sequence.” Best regards. Stéphane. From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Hi Stephane, Thank you for providing the clarification below on the cascade sequence.
At a high-level, we are supportive of this overall simplified sequence for R1 as it requires minimal change in spec while significantly improving medium efficiency and potentially reducing peak latency. Based on the discussion
below though we suggest revising the SP text to allow both cascade and non-cascade sequence.
Preferably we will like to remove reference to the Cascade sequence altogether since its more of an implementation choice at AP. We can perhaps instead focus on limiting the scope of the triggered P2P in R1 (e.g., limit
only to associated peer STA,…). What do you think ? Regards, Dibakar From: BARON Stephane <Stephane.BARON@xxxxxxxxxxxx>
Hi Ross, Thank you for your question. I think this up to the AP to include the TF triggering with a P2P RU in a cascading sequence or not. So yes, a simplified sequence as you mention is possible. However, I think that including a TF for P2P transmission in a cascading sequence provides additional benefits:
So, to me, the TF triggering a P2P transmission can be in or out of the scope of a cascading sequence, but have more benefits in a cascading sequence. Best regards. Stéphane. From: Yujian (Ross Yu) <ross.yujian@xxxxxxxxxx>
Hi Stephane, Thanks for preparing the contribution. Could you clarify if the whole (not part of) TXOP can be shared to the triggered P2P transmission or not? In other
words, does it have to be combined with MU cascading sequence in slide 4? How about a simple procedure like this? PS: I usually attend PHY calls, so may not have the chance to ask questions after your presentation. That’s why I send the clarification question here
in advance. Thanks. regards 于健
Ross Yu Huawei Technologies 发件人:
BARON Stephane [mailto:Stephane.BARON@xxxxxxxxxxxx]
Hi Alfred, Can you please add the following contribution to the list:
Best regards. Stéphane. From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Hello all, This is a call for submissions for the upcoming teleconference calls meeting. Please let me know if you have any items to be added to the agenda by sending me an e-mail with a request using the format below: - DCN-Presentation Title (Author, Affiliation), Topic Also please ensure that the presentation is uploaded
at least one week prior to the conference call as I will include the links to the presentations in the Submission's list. If the contribution is not uploaded by that time then it may not be included in the list. PS - There is no need to send an additional request for contributions that are already present in the conf call queue as they
will be imported by default to the Back-Logged Submission's List. 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 |