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

Re: [STDS-802-11-TGBP] Revised SP text, SP Set #24 SP #1

Hi Bo,

Can you help update SP1 of SP set #24 as follows for Wed discussion?

    • An AMP UL frame with UL response and possible application data
  • Note: Whether security is applied to the UL response is TBD.
Thanks,
Sam



From: Sam Shi <Sam.Shi@xxxxxxxxxxxxxxxx>
Sent: Tuesday, May 12, 2026 5:01 PM
To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBP] Revised SP text, SP Set #24 SP #1

Hi all,

There have been some offline discussions on this "one-shot" communication. The idea behind SP #24 is to support "one-shot data" communication such that the 1st frame exchange between an AP and a STA is DL trigger and UL response containing "data". None of the previous SPs explicitly support this very important scenario.

Having said that,

Option 1:
I propose we can capture the SP as follows:
  • 11bp supports data communication between unassociated AMP AP and STAs consisting of the following frame exchange:  
    • An AMP DL frame with UL access information and possible application data
    • An AMP UL frame with UL response and possible application data

Option 2:
If we do not want to use the wording "unassociated", we may do the following
  • 11bp supports data communication between AMP AP and STAs without previous frame exchange(s):  
    • An AMP DL frame with UL access information and possible application data
    • An AMP UL frame with UL response and possible application data

Let me know what you think. This is the "best" wording that Amichai and I can think of right now...

Thanks,
Sam

From: Sam Shi <Sam.Shi@xxxxxxxxxxxxxxxx>
Sent: Tuesday, May 12, 2026 10:58 AM
To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBP] Revised SP text, SP Set #24 SP #1

Hi Rojan,

I see your point...

Yes, ANY frame exchange would be triggered by the AP in AMP.  Having said that,  the behavior of "an AMP AP may initiate a random access uplink procedure without requiring previous frame exchange(s)." is already true...

The real thing I want to capture is "an AMP AP and a STA may support an AMP data frame exchange without previous frame exchange". 

What do you think we explicitly spell out "data frame exchange"? Then it can be separated from other uplink procedures, e.g. capability exchange, bonding, etc.

Thanks,
Sam

From: Rojan Chitrakar <rojan.chitrakar@xxxxxxxxxx>
Sent: Monday, May 11, 2026 6:01 PM
To: Sam Shi <Sam.Shi@xxxxxxxxxxxxxxxx>; STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx>
Cc: Lei Huang <lei.huang1@xxxxxxxxxx>
Subject: RE: [STDS-802-11-TGBP] Revised SP text, SP Set #24 SP #1

Hi Sam,


We already have many motions in the SFD for uplink access, how about simplifying the SP as below by referencing terms we already agreed (i.e., random access)?

 

  • For active Tx and bistatic backscatter non-AP AMP STAs, an AMP AP may initiate a random access uplink procedure without requiring previous frame exchange(s).

 

Btw, what does previous frame exchange(s) mean here? Any frame exchange would be triggered by AMP AP anyway, isn’t it?

 

Best Regards,

Rojan Chitrakar

 

From: Sam Shi <Sam.Shi@xxxxxxxxxxxxxxxx>
Sent: Monday, May 11, 2026 11:28 AM
To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBP] Revised SP text, SP Set #24 SP #1

 

Hi all,

 

Based on the discussion on last cc, I revised the SP texts reflecting:

  • Describe the procedure as a sequential frame exchange, i.e. 1st frame and 2nd frame.
  • The text is also simplified. 

 

 

SP #1: Do you agree to add the following text into the 11bp SFD?

  • For active Tx and bistatic backscatter non-AP AMP STAs, an uplink access procedure triggered by an AMP AP may be initiated without requiring previous frame exchange(s).
        • 1st frame: An AMP DL frame with UL access information.
        • 2nd frame: An AMP UL frame with UL response.
  • Note: Whether security is applied to the UL response is TBD.
  • Note: Content of the UL response is TBD.

 

Please let me know your comments, if any.

 

Thanks,

Sam

 

 

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

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