Dear Bo,
Kindly help to update the below two SPs in SFD MAC SP Set #33:
SP6: Do you agree to add the following to the 11bp SFD:
- An AMP Energizer that supports PASN may request an AMP AP
that supports PASN to setup of WPT/Excitation transmission without associating with the AMP AP.
- If the AMP AP accepts the request, the AMP AP shall assign an unassociated STA ID (USID) to the AMP Energizer.
- Note – Prior to the WPT setup, the AMP Energizer and the AMP AP shall establish PTKSA using PASN as described in 12.13.3 (Key establishment with PASN authentication)
[Reference: 26/0960]
SP7: Do you agree to add the following to the 11bp SFD:
- AMP AP may advertise (in Beacon, Probe Response, Association Response frames etc.) the types of AMP Energizers (WPT or Excitation) it supports.
In addition, an AMP AP that supports PASN may also advertise if unassociated AMP Energizers are supported.
[Reference: 26/0960]
And please help to add the below new SPs in the queue, SP1 is PHY, rest all are mac.
SP1: Do you agree to add the following to the 11bp SFD:
- The AMP DL Type1 PPDU may contain a Padding field after the AMP Data field.
- Note – The Padding field carries the padding defined in FM-36.

Ref:
- FM-36: 11bp defines padding in the DL AMP PPDU that carries the AMP frame that solicits the immediate response for the active Tx AMP non-AP STA.
- Note: actual padding mechanism (expected to be MAC), indications of the presence and the duration of the padding, and field containing the padding are TBD.
[Reference: 26/1297r0]
SP2: Do you agree to add the following text into the 11bp SFD?
- If an AMP frame carries a Frame Body Length field to indicate the length of the Frame Body field carried by the frame, the frame shall carry an error detection code (e.g., a checksum) computed over the Frame
Body Length field.
- Note – The error detection code and its position is TBD.
[Reference: 26/1297r0]
SP3: Do you agree to add the following to the 11bp SFD:
- AMP AP shall use EDCA for AMP monostatic backscatter communication in AMP S1G channels.
- The expectation is that the applicable baseline EDCA mechanisms is reused where applicable.
[Reference: 26/0963, 26/1405r0]
SP4: Do you agree to add the following to the 11bp SFD:
- A S1G mono-static backscatter AMP AP may transmit an AMP TX Announcement frame at the start of its TXOP to announce the TXOP duration.
- Another S1G mono-static backscatter AMP AP that receive the AMP TX Announcement frame shall use the duration information in the frame to set its NAV timer.
- The S1G mono-static backscatter AMP AP may transmit an AMP TX Announcement frame with Transmission Duration set to zero to reset the NAV set by an earlier AMP TX Announcement frame.
[Reference: 26/0963, 26/1405r0]
SP5: Do you agree to amend MM-46 as:
MM-46:
- During a multi-slot uplink access TXOP for Active Tx non-AP AMP STAs, the AMP AP shall transmit a DL AMP PPDU carrying an AMP
Ack frame to indicate the start of the second or subsequent time-slot.
- A non AP AMP STA eligible to transmit in a time slot other than the first slot, transmits its UL AMP PPDU at the end of the applicable IFS from the end of the DL AMP PPDU.
Note – the content of the AMP frame is TBD.- All the AMP Ack frame(s) within the TXOP are transmitted at the same data rate as the DL AMP frame that solicits the uplink access.
[Reference: 26/1424r0]
SP6: Do you agree to amend FM-42 as:
FM-42:
- The AMP DL Ack frame that indicates the start of the time-slot shall include the
transmitter identifier AMP AP’s primary 20 MHz channel.
[Reference: 26/1424r0]
SP7: Do you agree to add the following to the 11bp SFD:
- The Partial STA ID in the AMP-SIG of the AMP DL PPDU carrying an AMP Ack frame used to indicate the start of an uplink slot shall be set as 0 (broadcast).
[Reference: 26/1424r0]
Regards,
Rojan
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