Hi Thomas,
Thanks for your comments.
Please see my response inline as follows.
Best regards,
Liuming Lu
发件人: Thomas Derham <00000ad2eabc2931-dmarc-request@xxxxxxxxxxxxxxxxx>
发送时间: 2022年11月23日
6:44
收件人: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGBE] Discussion on 11-22/1036r3 (LB266 CR on Latency sensitive traffic differentiation)
Thanks for this discussion. My 2c:
·
An AP might use various strategies for achieving the KPIs of low-latency flows, including internal queue management, specific scheduling policies, specific triggering policies, possibly use of (r)TWT and others.
I don’t think there is any one mechanism that is the “right” choice - it would depend on AP and STA capability support, characteristics of all in-BSS flows, characteristics of OBSS transmissions/contention, and various other considerations
[V] I agree that the KPIs of
latency depends on several factors, such as what you have mentioned. But AP can estimate the KPIs from its perspective based on the major factors and information it can gain, and how to estimate the KPIs is an implementation issue.
·
I think it is hard for an AP to determine a-priori the specific KPIs it could achieve for a yet-unknown flow. Even if it is assumed the current traffic characteristics remain as-is in the future (as is also
assumed for the baseline ESP elements), the KPIs achievable for a hypothetical newly created flow are likely to be dependent on the TID/UP/AC that flow uses, the traffic volume of that flow etc, at least some of which are a-priori unknown.
[LLM] AP can estimate the CURRENT
achievable KPIs (latency, MSDU Delivery Ratio, etc) under the optimal conditions based on current network environment and BSS load and LL traffic currently delivered etc., which is independent on a specific flow, and can updates the KPIs according to the changes.
The estimated KPIs as a reference information are provided to non-AP STAs which will consider whether to or how to use the KPIs. For a specific flow the non-AP STAs can choose to issue the SCS request to AP, which can further determine based on the qos requirements
of the flow.
Existing RSSI/SNR measurements and load (BSS Load / ESP) advertisements should be enough for the STA to make a reasonable BSS / MLD AP selection decision. The
network is probably in a better position to determine if there is another BSS / MLD AP that might provide better KPIs for a given flow, and if so initiate suitable steering and/or link reconfiguration mechanisms.
[LLM] The BSS load doesn’t differentiate
the LL traffic and non-LL traffic, and cannot reflect a KPI for latency. For the same RSSI/BSS load in 2.4G/5G/6G band the achievable latency may be significantly different. So I think that existing RSSI/SNR measurement and BSS Load advertisements are not
enough for the STA/non-AP MLD to make a reasonable AP/Link selection decisions when starting to initiate a LL traffic delivery. The KPIs for latency can provide the BSS with a more complete picture.
Hi Liuming,
Thanks for your presentation and for initiating the discussion about this topic.
If I understand well, the KPIs are computed based on the network load, the rTWT parameters and the low-latency
traffics parameters known by the AP. This is an interesting concept. Nevertheless, it seems that the computed KPI allows to define the average flows that can be supported by a BSS, not dedicated for low latency flows. It is not a way to prioritize the low
latency flows versus the other types of flows.
It is helpful mainly for the STAs to know if its low-latency flows can be transmitted or not within
the BSS. For me, the rTWT mechanism is a way to prioritize the low latency flows.
Regards.
Patrice
Hi all,
I have presented the contribution 11-22/1036r3 in the TGbe MAC Ad-Hoc today:
https://mentor.ieee.org/802.11/dcn/22/11-22-1036-03-00be-lb266-cr-for-35-9-2-1-latency-sensitive-traffic-differentiation.docx
If you have comments and questions on 22/1036r3 please send e-mail to me.
Thanks.
Best Regards,
Liuming Lu
本电子邮件及其附件含有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 cultural differences
between China and foreign countries, 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-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
|