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

[STDS-802-11-TGBF] 答复: [STDS-802-11-TGBF] 答复: Discusssion for the Sensing Trigger frame

Hi Dongguk,

 

Thanks for your reply.

I’m fine with the two resolutions now.

 

Best regards,

Mengshi Hu

 

发件人: Dongguk Lim <dongguk.lim@xxxxxxx>
发送时间: 2022年9月7日 11:08
收件人: humengshi <humengshi@xxxxxxxxxx>; STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
抄送: hg.cho@xxxxxxx
主题: RE: [STDS-802-11-TGBF] 答复: Discusssion for the Sensing Trigger frame

 

 

Hi Mengshi,

 

Thanks for your comments.

 

I added my responses inline below.

Please find it and let me know if you have comment for that.

 

Best regards,

Dongguk.

 

From: humengshi [mailto:0000179fd8c5ace5-dmarc-request@xxxxxxxxxxxxxxxxx]
Sent: Tuesday, September 6, 2022 12:12 PM
To: STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBF] 答复: Discusssion for the Sensing Trigger frame

 

Hi Dongguk,

 

Thanks for the sharing.

I have the following suggestions:

1.     Regarding the following table, Poll, Sounding, Report are called different Sensing Trigger frame variant. However, in the text of the CR document, they are called Poll sub-variant, Sounding sub-variant, and Report sub-variant of the Sensing Trigger frame. This is confusing to me because of the consistency.

Sensing Trigger Subtype field value

Sensing Trigger frame variant

0

Poll

1

Sounding

2

Report

3-15

Reserved

 

[Dongguk Lim] Since I referred to the 11az draft when I wrote the initial draft, I followed the styles described in 11az for the name of each sensing trigger frame. for the use of unified terminology in the 11bf spec, I can change the name commented on you as below.

Poll sub-variant, Sounding sub-variant, and Report sub-variant are replaced with Sensing Poll Trigger frame, Sensing Sounding Trigger frame, and Sensing Report frame.

What do you think about making this change?

2.     I know maybe you don’t want to touch the Frame A and Frame C in the Topic Threshold in this CR document (See the figure below).

However, since the above two frames are highly related to the variant designs. Could you add some descriptions saying that it’s TBD whether the Sensing Trigger A and C in 11.21.18.6.5 Threshold-based reporting phase are different subvariants of the Sensing Report Trigger frame, or whether the Sensing Trigger A is another new variant of the Sensing Trigger frame? Otherwise, the variant design seems to be a little bit confusing, because actually Sensing Trigger A and B are two different types and now the design doesn’t consider these two types. Thanks.

[Dongguk Lim] Yes, This document does not include the types of trigger frames related to Threshold based reporting phase because this document is only focusing the three types of sensing trigger frames.

As you know, I will plan to prepare the CR document related to Threshold based reporting phase to resolve the CIDs for frames A and C to discuss it after finishing the three types of sensing Trigger frames.

I think that we need to discuss how to define the trigger frame which is used to solicit the CSI variation information from the STAs. and after making a decision to how define those trigger frames, we can apply it to the 11bf spec by suggesting the modification of the current text or table.

  

Best regards,

Mengshi Hu

 

 

 

 

Dear All,

 

I hope you had a nice holiday.

 

I knew that some members would like to discuss this topic by scheduling additional meetings. However, since we have scheduled many CCs for the discussion of other topics this week, it is hard to schedule another CC for this discussion for the sensing Trigger frame. in addition, the 802.11 Interim sessions are scheduled for next week. 

Thus, first of all, I would like to discuss the sensing Trigger topic by using the email discussion to gather opinions for other members.

I revised the CR document for the sensing Trigger frame based on the Comments received during the last CC.

For the indication of this modification, I add the memo in the attached document and add also some discussion points using the memo.

Attached, Please take look at it. I look forward to the good comments from you.

 

Best regards,

Dongguk.

 

 

 

________________________________________________________________________________________

Dongguk Lim

Chief Technology Officer IoT Connectivity Standard Task/Professional

LG Electronics Inc

19, Yangjae-daero 11-gil, Seocho-gu, Seoul, Korea

M.82-10-8996-4690  E.dongguk.lim@xxxxxxx

___________________________________________________________________

 

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