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

Re: [STDS-802-11-TGBP] Agenda update for coming TGbp TC

Can you point out which motion talks about these?

Regards,

Alfred

On Wed, Sep 9, 2026 at 11:37 AM Sam Shi <Sam.Shi@xxxxxxxxxxxxxxxx> wrote:
I concur with Amichai about the following case, which were discussed in the group. For inventory, this can be the case that AP and STAs are never associated. Then the frame body would carry upper layer data to allow the target STAs to respond.

Thanks,
Sam


From: Amichai Sanderovich <00003126a116a6ee-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, September 9, 2026 12:40 AM
To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBP] Agenda update for coming TGbp TC

Hello Alfred,

Just a follow-up on yesterday’s call, which I missed on my first pass on the document.
Our intention in the motion for including the frame body in the trigger frame is only for application data (upper layer use).

Some examples for the usage:
  1. Inventory Example: we would like to inventory only Coco cola and not Pepsa cola or chicken nuggets or barbie dolls. Thus we need application data in the trigger frame that will solicit just these. Otherwise we need to trigger ALL the devices and get overwhelming number of non-needed responses.
  2. Agriculture Example: we would like to water the arid ground and avoid watering where the ground is already humid. This is done by using a device next to each plant and water where it is too dry. Application will want to solicit response only from sensors that sense low humidity. It can be 5 in a field of 2000. We do not want a response from all of them. Just from the sensors that passed a threshold.

Best Regards
Amichai
From: Amichai Sanderovich <00003126a116a6ee-dmarc-request@xxxxxxxxxxxxxxxxx>
Date: Wednesday, 2 September 2026 at 19:57
To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBP] Agenda update for coming TGbp TC

Hello Alfred,

See below my response

Best Regards
Amichai

From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Date: Tuesday, 1 September 2026 at 19:57
To: Amichai Sanderovich <amichai.sanderovich@xxxxxxxxxx>
Cc: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBP] Agenda update for coming TGbp TC

Hi Amichai, 

Thanks for reviewing. Please find some responses/thoughts below [AA]:
Few comments I have:

  1. BSSID is not known to the non-AP STA, so perhaps it can be replaced by AP transmitter ID that can be selected randomly.
  •      [AA] Can you elaborate a little bit more? If the non-AP STA does not know the BSSID (which is at the AP side) then it would also not know any other bit sequence (transmitter ID of AP that can be selected randomly) which is also at AP side. 
[AS] when unassociated, the only identity of TX known at the AMP non-AP STA is the short ID TX address. This is sufficient for communicating required AMP information. For example, the TF consists of an AMP-AP ID, which can then be used for the CRC calculation of the SYNC, the receiver ID of the responses and also the ID used in any further communication (non-associated).
  1. AMP-AP are not necessarily APs. They can be non-AP STA as well. So they won’t have a unique BSSID. 
  • [AA] Similar observation, could you elaborate a little bit more? The way i see it is that the term AMP AP has literally AP in it (so it is an AP). While non-AP STAs have literally non-AP in it (so it is not an AP).
[AS] AMP-AP is more a reader than AP. It is not required to transmit beacons, receive prob requests or even associate any non-AP STAs. Thus it does not have to have a BSSID - not sure whether we need to define such AMP-BSSID at all. AFAIK, standard MAC address of the AMP-AP should be sufficient?
  1. Slot duration: We prefer the slot duration to be signaled in units of bytes and not micro-seconds.
  • [AA] Please provide some technical background on the preference so that i can evaluate. The motion mentioned slot duration and slots in general are in units of time. But open to better alternatives.
[AS] By defining the duration as length instead of time in us - we avoid many complexities like: clock drifts/mismatch issues, definitions brevity (will AP have enough time to send the ACK?, do we need to mandate many behaviors of the AP to make sure both sides use the same calculation, etc.). Also it makes the STA MAC simpler since no devision calculation is needed. This is especially helpful when upper layer length calculations are also needed within SIFS. 

Regards,

Alfred
Regards,

Alfred

On Tue, Sep 1, 2026 at 1:14 AM Amichai Sanderovich <amichai.sanderovich@xxxxxxxxxx> wrote:
Hello Alfred,

Thank you for the PDT.
Few comments I have:

  1. BSSID is not known to the non-AP STA, so perhaps it can be replaced by AP transmitter ID that can be selected randomly.
  2. AMP-AP are not necessarily APs. They can be non-AP STA as well. So they won’t have a unique BSSID. 
  3. Slot duration: We prefer the slot duration to be signaled in units of bytes and not micro-seconds.

Best Regards,

Amichai

From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Date: Tuesday, 1 September 2026 at 3:09
To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBP] Agenda update for coming TGbp TC

Hello Bo, all,

I uploaded the PDT for AMP Ack, AMP Trigger and AMP Wake Up frame. 


Please review and let me know if you have any questions and/or suggestions. 

Regards,

Alfred


On Mon, Aug 31, 2026 at 8:49 AM <sun.bo1@xxxxxxxxxxxxxxxx> wrote:
Hello, all, 

The TGbp TC agenda is updated for the coming TC on Sep 1st. 



Please let me know if your requests have been announced to the reflector while missing in the agenda or the PDT proposal list.

Best Regards,
Bo




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

To unsubscribe from the STDS-802-11-TGBP list, click the following link: https://protect.checkpoint.com/v2/r01/___https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBP&A=1___.YzJ1OndpbGlvdDI6YzpvOjkxMDI0NDM0N2E3NzllM2UxMjYzN2FlODA1YmRlODFkOjc6ZjY3ZjplZDM3ODM4NzIzMDljYjMxNzRmY2QzZDIwMTI1MGI0MTg2ZjEzMWUxMDdlYWZkYTZhMGI3NDdmNThiZTExNjFkOnQ6VDpG

To unsubscribe from the STDS-802-11-TGBP list, click the following link: https://protect.checkpoint.com/v2/r01/___https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBP&A=1___.YzJ1OndpbGlvdDI6YzpvOjE4YzkzNGRjNDhmYzJkNWE5NWZjYzVmNTBlMzUwMzQ5Ojc6MTBhYzplZmUzMDM0MDY1YjJlMjU0OWRhZWU3ZTZhMzQ0MzcxOGY3MzJmYTQ4NzFiZGVlZmUyZmM5ZmM2OTM3NmUzMWZiOnQ6VDpG

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

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

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