| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
| --- This message came from the IEEE 802.11 Working Group Reflector ---
Hi all, I have presented 11-23/46r2 “Multi-AP Coordination for Low Latency Traffic Delivery: Usage Scenarios and potential features”
in the UHR SG meeting this Thursday. And this is to initiate a further discussion on the contribution.
Below are the responses to some of the questions that were raised in the meeting or offline discussion until now. If you have further comments on
the contribution please send the mail to me. Any comments and suggestions are welcome. Thanks. 1) Rubayet: my comment was that your presentation seems to be doing R-TWT MAP coordination specifically to help one particular client. [LM] The contribution just gives an example of a STA requesting for
R-TWT setup with multi-AP coordination, another STA can also follow the same procedure. And in comparison with R-TWT setup in one BSS, more factors needs to be considered
for R-TWT setup with multi-AP coordination, such as the channel condition for the STA, the interfering STAs, and the requirements for the low latency traffic to be delivery,
the STAs to be restricted for transmission etc. If more STAs request for R-TWT setup with multi-AP coordination, the coordination needs to consider more factors related
with the STAs. How to response to R-TWT setup request needs the negotiation among multiple APs. 2) Dmitry: what you propose is very close to already defined/existing C-SR or combination of TDMA + C-SR. The TDMA part is TWT SP in your contribution.
So, this mode is not a new one, it already exists today and the group has been discussing it since the beginning of .11be. The only new part is a need to coordinate/align rTWT SPs, which os definitely needed, and i think, as Laurent mentioned, it is better
to discuss coordination of rTWTs between AP along with other contributions on that topic. [LM] I think that the key point of multiple-ap coordination for low latency delivery is to coordinate/align rTWT SPs, the TDMA + C-SR can be one of
methods helpful to coordinate rTWT SPs, such as which STAs are suitable to be member STAs, which STAs need to be restricted for transmission during SPs. I would like to discuss the coordination of rTWTs among APs with the members on this topic. 3) Jinyoung: I wonder Type 2 is suitable for Low latency traffic. Even if Type 2 can be supported by some conditions e.g. option 1a, Type 2 coordination
needs more preparing procedure before data transmission than Type 1. For example, collecting exact RU info for C-OFDMA or exchanging data among APs for JTX, etc. [LM] I agree with your opinion. Type 1 may be suitable for most scenarios, and Type 2 is used only in some special scenarios under strict requirements
with more procedure needed. [Brian]In slide 4, you write “Option 1: AP1 and AP2 communicate with each other by co-channel signaling with better KPIs … Option 2b: APs can share
the information by backhaul with limited KPIs” To my mind there also is a “combined” option – i.e., APs can communicate via both wired backhaul and wirelessly, and can take advantage of the strengths of each mode of communications. [LM] I agree with your opinion. The combined option needs to be considered. Best regards, Liuming Lu 发件人: laurent cariou <00001be540c02bbe-dmarc-request@xxxxxxxxxxxxxxxxx>
--- This message came from the IEEE 802.11 Working Group Reflector ---
Hi, This is a call for presentation for the 802.11 UHR SG F2F for March. Please let me know if you want to be in the agenda before Saturday March 11th EoD. Plan for March F2F meeting: The main objective is to converge and agree on the PAR and CSD documents for UHR at the end of the week, so strong priority will be put into the discussion on these
documents. As part of this, we will have a poll to evaluate if there is sufficient support to include mmWave in the scope of UHR PAR, and adjust the PAR document accordingly. Thanks, Laurent To unsubscribe from the STDS-802-11 list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11&A=1
OPPO
本电子邮件及其附件含有OPPO公司的保密信息，仅限于邮件指明的收件人（包含个人及群组）使用。禁止任何人在未经授权的情况下以任何形式使用。如果您错收了本邮件，切勿传播、分发、复制、印刷或使用本邮件之任何部分或其所载之任何内容，并请立即以电子邮件通知发件人并删除本邮件及其附件。 网络通讯固有缺陷可能导致邮件被截留、修改、丢失、破坏或包含计算机病毒等不安全情况，OPPO对此类错误或遗漏而引致之任何损失概不承担责任并保留与本邮件相关之一切权利。 除非明确说明，本邮件及其附件无意作为在任何国家或地区之要约、招揽或承诺，亦无意作为任何交易或合同之正式确认。 发件人、其所属机构或所属机构之关联机构或任何上述机构之股东、董事、高级管理人员、员工或其他任何人（以下称“发件人”或“OPPO”）不因本邮件之误送而放弃其所享之任何权利，亦不对因故意或过失使用该等信息而引发或可能引发的损失承担任何责任。 文化差异披露：因全球文化差异影响，单纯以YES\OK或其他简单词汇的回复并不构成发件人对任何交易或合同之正式确认或接受，请与发件人再次确认以获得明确书面意见。发件人不对任何受文化差异影响而导致故意或错误使用该等信息所造成的任何直接或间接损害承担责任。 This e-mail and its attachments contain confidential information from OPPO, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you are not the intended recipient, please do not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. Electronic communications may contain computer viruses or other defects inherently, may not be accurately and/or timely transmitted to other systems, or may be intercepted, modified ,delayed, deleted or interfered. OPPO shall not be liable for any damages that arise or may arise from such matter and reserves all rights in connection with the email. Unless expressly stated, this e-mail and its attachments are provided without any warranty, acceptance or promise of any kind in any country or region, nor constitute a formal confirmation or acceptance of any transaction or contract. The sender, together with its affiliates or any shareholder, director, officer, employee or any other person of any such institution (hereinafter referred to as "sender" or "OPPO") does not waive any rights and shall not be liable for any damages that arise or may arise from the intentional or negligent use of such information. Cultural Differences Disclosure: Due to global cultural differences, any reply with only YES\OK or other simple words does not constitute any confirmation or acceptance of any transaction or contract, please confirm with the sender again to ensure clear opinion in written form. The sender shall not be responsible for any direct or indirect damages resulting from the intentional or misuse of such information. To unsubscribe from the STDS-802-11 list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11&A=1 |