| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Mengshi, Thank you for sharing the draft of the PDT. Please find my comments in the attached file.
Best regards, Ray From: humengshi <0000179fd8c5ace5-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Rajat, Thanks for your suggestions and comments. Please see my answers below: Comment 1: Typo:
“basd” Answer 1: I’ve changed it. Maybe I’ll use TBD for this frame later according to some suggestions. Comment 2: How is the threshold being set? Answer 2:
The threshold for each responder to be compared with the CSI variation value is determined by the initiator, and is transmitted to each receiver through a
TBD frame. I think this frame could be the NDPA frame or the trigger frame. In this version I use TBD for it. Comment 3: The Threshold-based Subvariant Sensing Trigger frame and how is it different than the existing Trigger frame?
Answer 3: I’ve shown in the Discussion that the Threshold-based Subvariant Sensing Trigger frame is a newly added subvariant frame
(Just want to give a name for it). Since I find that some people have concerns about using a new subvariant frame, I will make it a TBD frame in the updated version. The difference is that a new subvariant frame can have a different User Info, and this Info
can contain the threshold related information such as the threshold value per user. Actually I’m open to the design. If people think a unified trigger is good enough, I’m also fine with it.
Best regards, Mengshi Hu
发件人: Rajat
PUSHKARNA <rajat.pushkarna@xxxxxxxxxxxxxxxx>
Hi Mengshi, Thanks for preparing the PDT. Please find my comments attached herein. Thanks. Best Regards, From: humengshi <0000179fd8c5ace5-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Dongguk, Thanks for your comments. Regarding your first comment, you can see from that figure, for the sensing receiver 2, there is no need to feedback the CSI information. What the receiver 2
feeds back is the CSI variation in the Selection Procedure. In the case of a room without some object motions, there is a high possibility that only the Selection procedure is needed for a receiver. Thus the overhead can be saved in this case. Note that compared
with the CSI information, the CSI variation only consumes several bits, which can be negligible if the CSI information size is large. Regarding the second comment, the reason I choose a new trigger frame subvariant instead of a reporting subvariant is: we need to convey maybe a 4-bit threshold
for each receiver. If this is conveyed in the NDPA, maybe it’s fine to only define a reporting subvariant. However, if the 4-bit threshold information per user is conveyed in the trigger, it’s better to define
a new one and let them be in the Trigger Dependent User Info. In general, I’m open to the design. I can make it TBD this time. Thanks. Best regards, Mengshi Hu
发件人:
stds-802-11-tgbf@xxxxxxxxxxxxxxxxx <stds-802-11-tgbf@xxxxxxxxxxxxxxxxx>
代表 Dongguk Lim Hi Mengshi, Thanks for your drafting the spec text.
I added my comments in the attached. Please see my comments. best regards, Dongguk.
From: HUANG LEI [mailto:000013c45bbec18b-dmarc-request@xxxxxxxxxxxxxxxxx]
Hi Mengshi, Thank you for preparing this draft text. Attached please find my comments. Best regards, Lei From: humengshi <0000179fd8c5ace5-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi all, I’ve written a PDT for the threshold-based sensing procedure, which has been uploaded to the Mentor:
https://mentor.ieee.org/802.11/dcn/22/11-22-0134-00-00bf-pdt-threshold-based-sensing-procedure.docx This PDT reflect the Motions 18 and 33 shown in 11-20/1847r40. Your comments and suggestions are welcome. Mengshi Hu 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
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
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
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
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 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 |
Attachment:
11-22-0134-00-00be-pdt-threshold-based-sensing-procedure(RY).docx
Description: 11-22-0134-00-00be-pdt-threshold-based-sensing-procedure(RY).docx