Re: [STDS-802-11-TGBF] 答复: [STDS-802-11-TGBF] Collecting comments on 22/

Thread Links	Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

Hi,

Regarding grouping multiple session IDs, I think we should follow the same approach for both sensing setup and termination. If we allow negotiating multiple sessions with one setup request/response frame we can do that for termination as well.

Regards,

Dibakar

From: Ali Raissinia <alirezar@xxxxxxxxxxxxxxxx>
Sent: Friday, April 15, 2022 9:56 AM
To: STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBF] 答复: [STDS-802-11-TGBF] Collecting comments on 22/0626r1: Updates on measurement setup termination frame

Hi Pei,

Sorry for my comment during the meeting as I heard that you were talking about the use of MAC addresses which took me to the path of frame being sent with broadcast address requesting termination of setup IDs to many devices!! Now that I understand the intention is to accommodate TB and NTB termination in the same frame between pair of devices, we could add a control byte (which could also contain bits indicating “terminate-all MS” and possibly ‘terminate session’) where it can also include TB/NTB setup field present bits. I guess TB/NTB is analogous to your Tx/Rx indicator (depending on whether it is from AP or non-AP initiator).

Regards,

Ali

From: 周培(Pei Zhou) <00001462c7c6c67a-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Friday, April 15, 2022 1:34 AM
To: STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBF] 答复: [STDS-802-11-TGBF] 答复: [STDS-802-11-TGBF] Collecting comments on 22/0626r1: Updates on measurement setup termination frame

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Hi Xiandong,

Please see my comments inline.

Best regards,

Pei

发件人: 董贤东 <dongxiandong@xxxxxxxxxx>
发送时间: 2022年4月15日 15:53
收件人: 周培(Pei Zhou) <zhoupei1@xxxxxxxx>; STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
主题: 答复: [STDS-802-11-TGBF] 答复: [STDS-802-11-TGBF] Collecting comments on 22/0626r1: Updates on measurement setup termination frame

Hi Pei,

Thanks for your clarification, please see my comments inline.

Best Regards

Xiandong

发件人: 周培(Pei Zhou) <00001462c7c6c67a-dmarc-request@xxxxxxxxxxxxxxxxx>
发送时间: 2022年4月15日 15:23
收件人: STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
主题: [STDS-802-11-TGBF] 答复: [STDS-802-11-TGBF] 答复: [STDS-802-11-TGBF] Collecting comments on 22/0626r1: Updates on measurement setup termination frame

Hi Xiandong,

According draft 0.01 (refer to Clause 11.21.18.1 Overview, especially Figure 11-41—Example of a WLAN sensing procedure), AP can initiate TB measurement setup (this setup will keep active before termination), then STA can also initiate non-TB measurement setup before the TB measurement setup is terminated.

That is to say, both TB and non-TB cases are active at the same time period.

【dxd】: this means that the both cases occur in time order, not simultaneously , note that we have defined delayed report and immediate report in the D0.01, and if the delayed report is used for the TB case, I think that it is better to send two separate frames for TB and non-TB case, since the inactivity time for the non-TB case is expired, meanwhile the delayed report is not received/transmitted for TB case.

[Pei]: Please look at the figure below, if we assume Measurement Setup ID = 1 corresponding to TB case, Measurement Setup ID = 2 corresponding to non-TB case, then TB and non-TB can occur in the same time period in disordered. There is no limitation that which case is performed before and then followed by another.

In terms of the delayed report, if there is delayed report after the termination frame, we can just discard it. Because if a station decides to send a termination frame, it usually means the measurement results are enough. By the way, this is not a new issue caused by our contribution. It always exists as a corner case.

Since one termination frame can finish two kinds of termination (for TB and non-TB), why we still use a higher overhead solution: send two separate termination frames?

Hope my explanations can address your concerns.

Therefore, AP or non-AP STA can initiate measurement setup termination for TB case and/or non-TB case.

Best regards,

Pei

发件人: 董贤东 <dongxiandong@xxxxxxxxxx>
发送时间: 2022年4月15日 15:03
收件人: 周培(Pei Zhou) <zhoupei1@xxxxxxxx>; STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
主题: 答复: [STDS-802-11-TGBF] 答复: [STDS-802-11-TGBF] Collecting comments on 22/0626r1: Updates on measurement setup termination frame

Hi Pei,

I don’t understand what does the sentence “Since both TB and non-TB cases may overlapping in time” mean, it means the both cases could be occurred simultaneously for the same initiator and responder?

Best regards

Xiandong

发件人: 周培(Pei Zhou) <00001462c7c6c67a-dmarc-request@xxxxxxxxxxxxxxxxx>
发送时间: 2022年4月15日 14:20
收件人: STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
主题: [STDS-802-11-TGBF] 答复: [STDS-802-11-TGBF] Collecting comments on 22/0626r1: Updates on measurement setup termination frame

Hi Solomon,

Thanks for your clarifications and comments.

Yes, the case is that the same non-AP STA participates in both TB and non-TB sensing with the same AP.

I think your idea is to use two termination frames, one to terminate some measurement setups in TB case and the other to terminate some measurement setups in non-TB case.

Since both TB and non-TB cases may overlapping in time, why we just use one termination frame to terminate measurement setups in both TB and non-TB cases?

Best regards,

Pei

发件人: Solomon Trainin <strainin@xxxxxxxxxxxxxxxx>
发送时间: 2022年4月15日 13:21
收件人: 周培(Pei Zhou) <zhoupei1@xxxxxxxx>; STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
主题: RE: [STDS-802-11-TGBF] Collecting comments on 22/0626r1: Updates on measurement setup termination frame

Hi Pei,

The presentation introduces overlapping of the MS IDs based on the assumption that both the AP and non-AP allocate the MS ID value. The assumption is wrong for TB sensing. It may be relevant when observing both TB and non-TB sensing. So, the case is that the same non-AP STA participates in both TB and non-TB sensing with the same AP. So, one solution can be to indicate in the termination frame what it is TB or non-TB and not to mixt the TB and non-TB in the same termination frame. No need for any TX/RX fields.

Best regards,

Solomon Trainin

+972547885738

From: 周培(Pei Zhou) <00001462c7c6c67a-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Friday, April 15, 2022 7:33 AM
To: STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBF] Collecting comments on 22/0626r1: Updates on measurement setup termination frame

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Hi all,

I presented this contribution today. Let me explain a little bit:

1. Both AP and STA can maintain multiple measurement setups. It is not efficient if we limit one termination frame from only terminating one measurement setup (ID).

2. When we terminate multiple measurement setups by one termination frame, we need to indicate who set the measurement setup ID(s).

3. The method of indicating who set the measurement setup ID(s) is that we use two list (Tx List and Rx List), the “Tx” and “Rx” is the “Transmitter” and ”Receiver” of the termination frame.

4. Why we don’t use “Initiator List” and “Responder List”? Because both AP and non-AP STA can act as Initiator. “Initiator List” and “Responder List” maybe misleading to the receiver of the termination frame.

I hope my explanations can address some of your concerns. Your comments and suggestions are welcome.

Best regards,

Pei Zhou

OPPO

本电子邮件及其附件含有OPPO公司的保密信息，仅限于邮件指明的收件人使用（包含个人及群组）。禁止任何人在未经授权的情况下以任何形式使用。如果您错收了本邮件，请立即以电子邮件通知发件人并删除本邮件及其附件。

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 receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

To unsubscribe from the STDS-802-11-TGBF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1