Hi Bo,
Please help to add the following SPs to the queue:
SP1
- Do you agree to add the following text to TGbp SFD?
-
IEEE 802.11bp allows AMP Service Period parameters to be carried in a broadcast AMP frame (name TBD).
-
Note: The presence of the AMP Service Period parameters is configurable.
[Reference: 11-25/0039r0, 11-25/0285r1, 11-25/0787r0, 11-25/1244r0, 11-25/1560r0]
SP2
- Do you agree to add the following text to TGbp SFD?
-
The AMP Service Period parameters to be carried in a broadcast AMP frame include SP ID, SP Start Time, SP Interval, and SP Minimum Wake Duration. The SP ID serves to uniquely identify the AMP Service Period. The SP
Interval is the time interval between two subsequent service periods with the same SP ID.
[Reference: 11-25/0039r0, 11-25/0285r1, 11-25/0787r0, 11-25/1244r0, 11-25/1560r0]
SP3
- Do you agree to add the following text to TGbp SFD?
-
The timing granularity of the AMP AP’s partial timestamp carried in a broadcast AMP frame is 64us.
[Reference: 11-25/0285r1, 11-25/0787r0, 11-25/1247r0, 11-25/1560r0, 11-25/1561r0]
SP4
- Do you agree to add the following text to TGbp SFD?
-
The length of the AMP AP’s partial timestamp carried in a broadcast AMP frame is 24 bits.
[Reference: 11-25/0285r1, 11-25/0787r0, 11-25/1247r0, 11-25/1560r0, 11-25/1561r0]
SP5
- Do you agree to add the following text to TGbp SFD?
-
IEEE 802.11bp defines the AMP TSF field to carry the AMP AP’s partial timestamp TSF [6:29] in a broadcast AMP frame.
[Reference: 11-25/0285r1, 11-25/0787r0, 11-25/1247r0, 11-25/1560r0, 11-25/1561r0]
SP6
- Do you agree to add the following text to TGbp SFD?
-
The short timestamp when present in the AMP trigger frame carries the AMP TSF field, TSF [6:29] of the AMP AP’s partial TSF.
-
Other lengths of short timestamp configured to be present in the AMP trigger for some modes of operation is TBD.
[Reference: 11-25/0285r1, 11-25/0787r0, 11-25/1247r0, 11-25/1560r0, 11-25/1561r0]
SP7
- Do you agree to add the following text to TGbp SFD?
-
IEEE 802.11bp defines AWUR frame as one type of AMP frame with the Frame Body including WUR Frame (excluding FCS).
-
Note: AWUR means Ambient Wake-up Radio.
[Reference: 11-25/1246r0, 11-25/1547r0]
Kind Regards
Ian
Dear Bo,
Please help to add the below SPs to the queue:
PDT:
SP: Do you agree to incorporate 11-25\1344r4 (pdt-components-of-architecture) into 802.11bp D0.1?
SP1: Do you agree to add to amend FM-9 in the11bp SFD as:
q
An AMP AP transmits an AMP Trigger frame indicating a time-slot based random access session for non-AP AMP STAs. The frame may carry following parameters:
§
Session ID: Identifies the random access session
§
ACW: Indicates the upper limit of the random access contention window
o
ACWmin: Indicates the minimum value of the upper limit of the random access contention window
o
ACWmax: Indicates the maximum value of the upper limit of the random access contention window
§
Encoding of parameters is TBD.
§
Other parameters are TBD.
[Reference: 25/1246r0, 25/1242r0]
SP2: Do you agree to add to amend MM-27 in the11bp SFD as:
-
Upon receiving an AMP Trigger frame indicating a time-slot based random access session, a non-AP AMP STA performs the following actions:
§
If it is a new random access session, the non-AP AMP STA initializes ACW and randomly chooses an ABO Counter (ABOC) in the range [0, ACW]. Else, if
it a known random access session and the non-AP AMP STA’s previous transmission in the session was unsuccessful, the non-AP AMP STA updates the ACW to (2*ACW+1) and randomly chooses an ABOC in the range [0, ACW].
§
If the ABOC is less than the number of slots (N) allocated by the AMP Trigger frame, the non-AP AMP STA transmits an uplink AMP PPDU carrying the uplink
response in one of the slots allocated by the AMP Trigger frame. Else, ABO Counter is decremented by N.
[Reference: 25/1246r0, 25/1242r0]
AMP Frame Format
SP3: Do you agree to add to the 11bp SFD:
-
The Type field is the first 4 bits of the Frame Control field of AMP frames and differentiates between:
1) AMP WUR frames: AMP frames for communication with AMP Enabled non-AP STAs
§
The frame format of AMP WUR frames inherit from WUR frames defined by IEEE 802.11ba.
2) Non-backscatter AMP frames: AMP frames for communication with Active Tx non-AP AMP STAs
3) Backscatter AMP frames: AMP frames for communication with backscatter non-AP AMP STAs
[Reference: 25/1547r0, 25/1102r1, 25/0817r0, 25/0818r0]
SP4: Do you agree to add to the 11bp SFD:
-
The size of the ID field(s) in AMP frames for communication with Active Tx non-AP AMP STAs and Backscatter non-AP AMP STAs is 16 bits.
[Reference: 25/1547r0, 25/1102r1, 25/0817r0, 25/0818r0]
SP5: Do you agree to add to the 11bp SFD:
-
The size of the Type Dependent Control field, if present in the MAC Header field of AMP frames for communication with Active Tx non-AP AMP STAs and Backscatter non-AP AMP STAs is 8 bits.
[Reference: 25/1547r0, 25/1102r1, 25/0817r0, 25/0818r0]
SP6: Do you agree to add to the 11bp SFD:
-
The length of the Frame Body field, if present in AMP frames for communication with Active Tx non-AP AMP STAs and Backscatter non-AP AMP STAs, is indicated in octets by a Length field in the MAC Header
§
The size of the Length field is TBD bits.
[Reference: 25/1547r0, 25/1102r1, 25/0817r0, 25/0818r0]
SP7: Do you agree to add to the 11bp SFD:
-
A second ID field may be present to indicate Transmitter ID in AMP frames for communication with Active Tx non-AP AMP STAs.
[Reference: 25/1547r0, 25/1102r1, 25/0817r0, 25/0818r0]
SP8: Do you agree to add to the 11bp SFD:
-
A Protected field is present in the Frame Control field of AMP frames for communication with Active Tx non-AP AMP STAs to indicate whether the AMP frame is protected by a security algorithm.
§
If the AMP frame is protected, a Protection Control field is carried in the Frame Body of the AMP frame. The size of the Protection Control field is TBD bits.
§
The security algorithm is TBD.
[Reference: 25/1547r0, 25/1102r1, 25/0817r0, 25/0818r0]
SP9: Do you agree to add to the 11bp SFD:
-
11bp defines one type of AMP frames for communication with Backscatter non-AP AMP STAs to carry a UHF command.
§
The UHF command, excluding CRC if any, is carried in the Frame Body field of the AMP Frame.
§
NOTE – The UHF commands are defined by the EPC® Radio-Frequency Identity Generation-2 Ver-2 UHF RFID Standard.
[Reference: 25/1547r0, 25/1102r1, 25/0817r0, 25/0818r0]
Best Regards,
Rojan Chitrakar
From: You-Wei Chen <ywchen77115@xxxxxxxxx>
Sent: Thursday, September 18, 2025 5:44 AM
To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBP] 回复: [STDS-802-11-TGBP] SP text for tomorrow
Dear Bo,
Please add the following SPs to the queue. Many thanks
Do you agree to incorporate the proposed text changes in 11-25/1439r2 to the latest TGbp draft (TGbp D0.1)
•Do you agree to update the following text in the SFD:
–An DL AMP PPDU in 2.4 GHz is identified in its U-SIG with the following setting:
•PHY version value set to 0
•One or multiple Validate bit subfields sets to 0 or subfield(s) set to a validate state.
•PPDU Type And Compression Mode value sets to 3.
Best Regards,
You-Wei Chen
Hi Alice,
Can you also add our contributions in the below as supporting doc? Thanks.
11-25/1262r1, 11-25/0790r0
Br,
Yinan
Please add the following SP to tomorrow SP list, ideally be run after Amichai's 2 SPs and before Shengquan's 2 SPs:
-
Do you agree to add the following to the 11bp SFD:
-
In the data field of AMP UL active transmission in 2.4 GHz,
-
250kbps data rate only uses 1us chip duration and rate 1/2 binary convolution code (BCC)
-
1Mbps data rate only uses 0.25us chip duration and the same rate 1/2 BCC
-
4Mbps doesn’t use BCC
-
Supporting doc: 11-25/1215r1, 11-25/1552r0
Hi Bo,
Please add the following two SPs to tomorrow SP list:
SP#1:
•
Do you agree to add the following to 802.11bp SFD?
–
The Uplink Sync Field Transmission from a non-Backscatter STA for all data rates shall have a length 48
[Reference Contribution Doc# 11-25/1552r0]
SP#2:
•
Do you agree to add the followings to 802.11bp SFD?
o
Length-48 sync sequence for UL non-backscatter transmission is constructed by repeating length-24 base sequence twice, i.e. S48 = [S24 S24]
o
The length-24 base sequence is given as below:
S24=[1, 1, 1, 1, 1, 0, 1, 0, 0, 1, 1, 0, 0, 1, 1, 0, 0, 0, 0, 1, 0, 1, 0, 0]
[Reference Contribution Doc# 11-25/1552r0]
Thanks,
Shengquan
|
|
External email : Please do not click links or open attachments until you have verified the sender or the content.
|
Hello Bo,
I have 2 SPs to run for this week meeting. If possible to run early slot on Thursday will be good.
SP1:
Do you agree to add into section 4.4.3 of the SFD the following text:
“11bp defines mandatory forward
error correcting code (FEC) of coding rate ½ for the data portion of UL active transmission in 2.4
GHz at rates of 0.25,1Mbps and non-coded mode at rate of 4Mbps”
[Reference contributions: 11-25/1002r1]
Y:
N:
A:
SP2:
Do you agree to add into section 4.4.3 of the SFD the following text:
“11bp defines forward error correcting
code (FEC) for the data portion of UL active transmission in 2.4 GHz based on the code as defined in 17.3.5.6 in 80211-2020”
[Reference contributions: 11-25/1002r1]
Y:
N:
A:
Thank you!
Best Regards
Amichai
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
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
