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

[STDS-802-11-TGBP] 回复: [EXT] [STDS-802-11-TGBP] SFD SP request



Hi Bo,

 

Could you please add the following SFD SP to the queue?

 

Do you agree to add the following to the 11bp SFD?

l  IEEE 802.11bp supports the center frequency of the UL signal from an active non-AP AMP STA located in the center of a 20 MHz channel for all data rates.

l  IEEE 802.11bp may additionally support the center frequency of the UL signal from an active non-AP AMP STA not located in the center of a 20 MHz channel for 250kbps and 1Mbps.

Ø  When the UL signal is not located in the center of the 20 MHz channel, it is located in either -5 MHz or +5 MHz relative to the center frequency of the 20 MHz channel.

[Reference: 11-26/0610r0, 11-26/0609r0, 11-26/0102r0]

 

Thanks.

Br,

Yinan

 

发件人: Rojan Chitrakar <00002005fb56ded7-dmarc-request@xxxxxxxxxxxxxxxxx>
发送时间: 2026312 14:32
收件人: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGBP] [EXT] [STDS-802-11-TGBP] SFD SP request

 

Hi Bo,

 

Please add the following to the SFD SP queue:

 

SP1: Do you agree to add the following to the 11bp SFD:

  • Upon receiving an AMP Trigger frame that indicates time‑slot‑based random access and includes ACW and the number of slots N, a non‑AP AMP STA performs the following:
    • Randomly select an ABOC in the range [0, X].
    • If the selected ABOC is less than N, randomly select one of the N time slots and transmit an uplink AMP PPDU in the selected slot.
    • Otherwise, the STA does not transmit in response to the Trigger frame, in which case the next transmission attempt will be considered an initial transmission attempt.
    • For an initial transmission attempt by the STA, X = ACW. If the initial transmission fails, the next transmission attempt is considered a retransmission attempt.
    • For a retransmission attempt by the STA, X = 2*ACW, except when the non‑AP AMP STA does not retain the status of previous transmission attempts across TXOPs (e.g., STAs without persistent memory, monostatic backscatter non‑AP AMP STAs), in which case X = ACW.

 [Reference: 25/2035r0, 25/1246r0, 25/1240r0, 25/1242r0, 26/0121r0, 26/0592r0]

 

SP2: Do you agree to add the following to the11bp SFD:

  • For bi-static backscatter communication, the AMP frame that solicits uplink response shall indicate the direction of the frequency shifting (higher or lower, relative to the excitation signal) to be used by a non-AP AMP STA to transmit the uplink AMP response.

[Reference: 26/0124r0]

SP3: Do you agree to amend motion MM-7 in the 11bp SFD as:

MM-7:

  • An 802.11bp client may uses the receive time of the end of the last symbol of the DL AMP PPDU carrying the AMP Trigger frame, which solicits UL AMP PPDUs from the client, to determine the timing for transmitting UL AMP PPDUs in the same TXOP
  • The definition of receive time is TBD.

[Reference: 26/593r1]

SP4: Do you agree to add the following to the 11bp SFD:

  • During a multi-slot uplink access TXOP for Active Tx non-AP AMP STAs, the AMP AP may transmit an AMP Ack frame to indicate the start of the second or subsequent time-slots.

[Reference: 26/593r1]

SP5: Do you agree to add the following to the 11bp SFD:

  • During a multi-slot uplink access TXOP for Active Tx non-AP AMP STAs, a non-AP AMP STA eligible to transmit in a time-slot transmits its UL AMP PPDU within the applicable IFS from the end of the DL AMP PPDU carrying an AMP Ack frame.
  • [Reference: 26/593r1]

 

From: Hui Luo <Hui.Luo@xxxxxxxxxxxx>
Sent: Thursday, March 12, 2026 5:55 AM
To:
STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBP] [EXT] [STDS-802-11-TGBP] SFD SP request

 

Hi Bo,

 

Please add the following SFD SP (reference 11-26/0598) in your list (replacing SFD SPs reference 11-26/0118)

 

11-26/0598 SP1

 

Do you agree to add the following text in the TGbp SFD --- 802.11bp shall specify the following secure AMP communication method, in which

 

  • A non-AP AMP STA has a high-entropy PSK and may have a high-entropy PMKv1 stored in persistent memory. An AMP AP (denoted as AP1) has a parameter Modifier1 and a PMK1, with PMK1 = hash(Modifier1, PMKv1) if the non-AP AMP STA has the PMKv1 or PMK1 = hash(Modifier1, PSK) otherwise, where PMKv1 or PSK is unknown to AP1.
  • AP1 sends an ANonce and the Modifier1 in a downlink AMP frame to the non-AP AMP STA.
  • Upon receiving the downlink AMP frame, the non-AP AMP STA generates an SNonce, computes PMK1 = hash(Modifier1, PMKv1) if it has the PMKv1 stored in its persistent memory or PMK1 = hash(Modifier1, PSK) otherwise, derives a PTK using the PMK1, the ANonce, the SNonce, an Authenticator Address (AA), and a Supplicant Address (SA), generates a MIC using a KCK derived from the PTK, and sends back the SNonce and the MIC in an uplink AMP frame to AP1.
    • If the uplink AMP frame is carrying any UL data, the data payload portion of the uplink AMP frame may be protected using the TK derived from the PTK.
  • AP1 computes a PTK using the PMK1, the ANonce, the SNonce, the AA, and the SA, and verifies the MIC using the KCK derived from the PTK. If the MIC is invalid, AP1 aborts.
    • If the uplink AMP frame contains protected data, the AMP AP processes the UL data using the TK derived from the PTK. If there are any subsequent AMP frames to be exchanged, the AMP frames may be protected using the TK derived from the PTK.

 

Note: this does not apply to mono-static backscatter non-AP STAs

Reference: 11-26/0598, 11-26/0118, 11-26/1437

 

Thanks,

 

Hui

 


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