Re: [STDS-802-11-TGBF] 答复: TGbf Teleconference on February 2 (Tuesday),

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

I would like submit a motion request to run the motions corresponding to the four SPs I ran in the contribution 21/0147r2(the SPs text had been modified to the version I ran and uploaded as 21/0147r3).

Could you please add them to the agenda of the next applicable 11bf meeting.

Motion 1

Move to add the following to 11bf SFD:

A sensing initiator might be neither a sensing transmitter nor a sensing receiver.

[RR] A sensing initiator may be a sensing transmitter, a sensing receiver, or neither.

Didn't we agree during the last teleconf that a sensing initiator might

be both a sensing transmitter and a sensing receiver? If so, this

rewording might be misleading. I thought that the point of this motion

was to emphasise the possibility that the initiator might not transmit

or receive any sensing PPDUs, in which case I think Rui's wording is

good. But if it's just to cover all the bases it should be:

A sensing initiator may be a sensing transmitter, a sensing receiver, both or neither.

[Rui] Yes, based on the discussion in last meeting, motion 1 emphasize the possibility that sensing initiator could be neither transmitter nor receiver.

OK, then I think the first Motion 1 wording proposal above,

"A sensing initiator might be neither a sensing transmitter nor a sensing receiver.", is better.

Motion 2

Move to add the following to 11bf SFD:

Results of measurement performed in a sensing session should be obtained by or reported to its initiator.

[RR] Initiators of sensing sessions should be able to obtain the results of the measurements performed during the sensing sessions they initiate.

[Rui] Thanks for your suggestions, and I think your suggestion has the similar meaning with the motion 2 text. But the group already agreed with the text in last meeting and I would like keep them unchanged.

Is this always going to be the case? Are there no situations in which

a device might initiate a sensing session on behalf of some other

device, whereby the other device is the one that needs the measurement

results (and obtains them itself or from a third party)?

[Rui] This motion only describe that sensing initiator should obtain the measurement result and never preventing other stations participate in the sensing session achieving the measurement results.

For the situation you described, a device might initiate a sensing session on behalf of some other stations. Is there any reason that the device who want the measurement result cannot initiate a sensing session by itself ?

If the station A wants the sensing measurement results could communicate with the sensing stations/devices, the station A could act as the sensing initiator directly and initiate the sensing session, which is quite straightforward.

If the station A wants the sensing measurement results could not communicate with the sensing stations/devices directly, it could ask station B acts as the sensing initiator and initiates the sensing session. But under this condition, sensing measurement results will be obtained by or reported to sensing initiator(station B) first and then transmitted to the device who want the results(Station A).

I just don't know whether there might be use cases where the "should"

would not be met. Say maybe I want my phone to tell the devices in

my home to check if there's any intruder, and to notify the police

automatically. In that case my phone is the sensing initiator, the

devices in my home are the sensing responders and also the sensing

transmitters and receivers, and my phone does not receive the sensing

measurements.

I'm not sure of the intent of this motion (especially with the "should"),

but if it's just trying to illustrate typical cases, how about:

Results of measurements performed in a sensing session are usually obtained by or reported to its initiator.

Motion 3

Move to add the following to 11bf SFD:

The 11bf amendment may define more than one type of sensing measurement results.

[RR] This amendment may define more than one type of sensing measurement result. [ed: not sure what a “measurement result” is since measurement itself is a noun. It might be worthwhile to define what a “measurement result” is if that has not already been done. I am guessing it may mean something more than just “the result of making a measurement” and that some processing of “raw measurements” may be taking place. This should be clarified.]

[Rui] Based on the discussion until now, CSI and radar are two methods could be adopted in 11bf. The measurement results from CSI and radar are quite different, so I think that in 11bf there will be types of measurement results. And this motion is just a step to describe that there could(and will) be types of sensing measurement results. The exact types could be further discussed in the group.

Motion 4

Move to add the following to 11bf SFD:

The type of measurement result obtained in a sensing session shall be decided by its initiator.

[RR] The initiator of a sensing session determines the measurements to be made and how they are to be processed.

[Rui] Again, thanks for your suggestions, and I think your suggestion has the similar meaning with the motion 4 text. But the group already agreed with the text in last meeting and let’s keep them unchanged.

Thanks,

Mark

Mark RISON, Standards Architect, WLAN English/Esperanto/Français

Samsung Cambridge Solution Centre Tel: +44 1223 434600

Innovation Park, Cambridge CB4 0DS Fax: +44 1223 434601

ROYAUME UNI WWW: http://www.samsung.com/uk

发件人: Hanxiao (Tony, WT Lab) [mailto:tony.hanxiao@xxxxxxxxxx]
发送时间: 2021年1月27日 17:13
收件人: STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx
主题: [STDS-802-11-TGBF] TGbf Teleconference on February 2 (Tuesday), 9:00 – 11:00am ET

Dear all,

This is a reminder and call for submissions for the upcoming teleconference call on February 2 (Tuesday), 9:00 – 11:00am ET.

Please note:

1. Please send the agenda request at least 24 hours prior to the call, following the format below:

• DCN, Title, Author (affiliation), Time duration

2. ~~I will cancel the call if there is no request received 24 hours prior to a call.~~

3. Please upload your submissions (revision 0) on mentor 24 hours prior to the meeting so that members would have a chance to review those submissions offline. Otherwise,

a. If there is not enough time during the meeting, the presentation will be delayed to the next meeting.

b. If there is enough time during the meeting, the presentation will be moved to the end of the queue and be presented in the end. However, any related SP should be delayed to the next meeting.

4. Please send the motion request around 10+5 days before the meeting, so that the TG chair could send the 10 day advance notice to the 802.11 reflector, after getting the approval from the WG chair.

5. Dial-in information:

Join the Webex meeting here: https://ieeesa.webex.com/ieeesa/j.php?MTID=m25939730baab64d1bf426125039728b3

Meeting number: 179 087 7321

Meeting password: wireless (94735377 from phones and video systems)

Join by phone: Tap to call in from a mobile device (attendees only) +1-408-418-9388 USA Toll
Global call-in numbers

Access code: 179 087 7321

Join from a video system or application Dial 1790877321@xxxxxxxxxxxxxxxx You can also dial 173.243.2.68 and enter your meeting number.

Join using Microsoft Lync or Microsoft Skype for Business Dial 1790877321.ieeesa@xxxxxxxxxxxxxx

Need help? Go to http://help.webex.com

Best Regards : )

Tony Xiao Han

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

Re: [STDS-802-11-TGBF] 答复: TGbf Teleconference on February 2 (Tuesday), 9:00 – 11:00am ET