Hi Bo,
We have total 7 SPs requests. SP1-5 are earlier SPs raised in May meeting. I also have another 2 new SPs for this meeting.
SP6：
Do you agree to add the following text to 11bp SFD?
802.11bp specifies, for a short timestamp, coarse timing granularity larger than 1µs.
The detailed timing granularity are TBD.
[Reference contributions: 11-25/1251r0, 11-25/0814r0, 11-25/0342r0,
11-24/1774r0]
SP7:
Do you agree to add the following text to 11bp SFD?
802.11bp supports that acknowledge information for two or more AMP non-AP STAs is carried in one AMP frame.
[Reference contributions: 11-25/0859r0]
Best Regards,
Chuanfeng
发件人:
Rojan Chitrakar <00002005fb56ded7-dmarc-request@xxxxxxxxxxxxxxxxx>
发送时间:
2025年7月30日
20:49
收件人:
STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx
主题:
Re: [STDS-802-11-TGBP] TGbp meeting agenda for Jul 802 plenary session uploaded
Hi Bo,
Aside from the earlier 11 SP requests, please also add the following 8 SPs related to AMP Frame format (25/1102r1) and 1 SP related to AMP Acknowledgments (25/1242r0). So total 20 SP
requests from myself.
AMP Frame format:
SP1: Do you agree to add to 11bp SFD:
-
802.11bp defines AMP frames for backscatter communication that may have a different frame format than the AMP frames for
non-backscatter communication.
[Reference: 25/1102r1, 25/0817r0, 25/0818r0]
SP2: Do you agree to add to 11bp SFD:
-
MAC Header of an AMP frame carries the following fields:
Frame Control
Always present
ID
The number of the ID fields and whether they are always present is TBD.
Length
Only present if the Frame Body field is present in the AMP frame.
[Reference: 25/1102r1, 25/0817r0, 25/0818r0]
SP3: Do you agree to add to 11bp SFD:
-
Frame Control of an AMP frame carries the following fields:
-
Frame Type (4 bits)
-
ID Present (1 bit)
-
Length Present (1 bit)
-
Other fields are TBD
[Reference: 25/1102r1, 25/0817r0, 25/0818r0]
SP4: Do you agree to add to 11bp SFD:
-
The ID field in the MAC Header of an AMP frame is 16 bits (2 Octets).
[Reference: 25/1102r1, 25/0817r0, 25/0818r0]
SP5: Do you agree to add to 11bp SFD:
-
The Length field in the MAC Header of an AMP frame is 8 bits (1 Octet).
[Reference: 25/1102r1, 25/0817r0, 25/0818r0]
SP6:
Do you agree to add to 11bp SFD:
-
If the AMP frame is protected, the FCS field of the AMP frame carries a 16-bits MIC.
[Reference: 25/1102r1, 25/0817r0, 25/0818r0]
SP7: Do you agree to add to 11bp SFD:
-
802.11bp defines an AMP Response frame to carry uplink response from non-AP AMP STAs and carries one or more of the following:
-
Response Type
-
Uplink Response
[Reference: 25/1102r1, 25/0817r0, 25/0818r0]
SP8: Do you agree to add to the 11bp SFD:
-
11bp defines an AMP UHF frame type to carry UHF command.
The UHF command is carried in the Payload field
[Reference: 25/1102r1, 25/0817r0, 25/0818r0]
AMP Acknowledgments:
SP1: Do you agree to add to the 11bp SFD:
-
In the AMP Trigger frame, the AMP AP indicates the type of acknowledgment that it intends to use in the slots allocated for uplink access.
[Reference: 25/1242r0]
Best Regards,
Rojan Chitrakar
Hi Bo,
I presented the related contributions this morning. Please add the following SPs to the agenda:
AMP Channel Access:
SP1: you agree to add to the 11bp SFD:
-
An AMP AP transmits an AMP Trigger frame indicating a time-slot based random access session for non-AP AMP STAs. The frame carries:
Session ID: Identifies the random access session
Response Type: Type of the solicited uplink response
ACW: Indicates the upper limits of the random access contention window
The frame may also carry a Number of Slots indicating the number of slots immediately after the AMP Trigger frame that are allocated for uplink transmissions
Other parameters are TBD.
Note (not part of SP): The AMP Trigger frame is referred to as AMP Poll frame in 25/1240r0.
[Reference: 25/1240r0, 25/0817r0, 25/0818r0]
SP2: you agree to add to the 11bp SFD:
-
Upon receiving the 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 session, the non-AP AMP STA initializes ACW and randomly chooses an ABO Counter in the range [0, ACW]. Else, if it a known session and the non-AP AMP STA’s previous transmission was unsuccessful,
the non-AP AMP STA updates the ACW to (2*ACW+1) and randomly chooses an ABO Counter in the range [0, ACW].
If the ABO Counter 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 requested response in one of the slot allocated by
the AMP Trigger frame. Else, ABO Counter is decremented by N.
[Reference: 25/1240r0, 25/0817r0, 25/0818r0]
SP3: you agree to add to the 11bp SFD:
-
An AMP AP may transmit an AMP Trigger frame to continue a time-slot based random access session within a TXOP. The frame carries:
Session ID: Identifies the random access session
Other parameters are TBD.
Note (not part of SP): The AMP Trigger frame is referred to as AMP Re-Poll frame in 25/1240r0.
[Reference: 25/1240r0, 25/0817r0, 25/0818r0]
SP4: you agree to add to the 11bp SFD:
-
Upon receiving the AMP Trigger frame that continues a time-slot based random access session with a known session ID, a non-AP AMP STA performs the following actions: :
If the non-AP AMP STA has not yet transmitted its uplink response, and the ABO Counter is equal to 0, the non-AP AMP STA transmits an uplink AMP PPDU carrying the requested response; else the ABO Counter
is decremented by 1.
[Reference: 25/1240r0, 25/0817r0, 25/0818r0]
SP5: you agree to add to the 11bp SFD:
-
An AMP AP transmits an AMP Trigger frame indicating a time-slot based scheduled access for non-AP AMP STAs. The frame carries:
Response Type: Type of the solicited uplink response
The frame may also carry:
Number of Slots (N) indicating the number of slots immediately after the AMP Trigger frame that are allocated for uplink transmissions, and,
IDs of two or more non-AP AMP STAs that are scheduled for uplink transmission.
Other parameters are TBD.
Note (not part of SP): The AMP Trigger frame is referred to as AMP Request frame in 25/1240r0.
[Reference: 25/1240r0, 25/0817r0, 25/0818r0]
SP6: you agree to add to the 11bp SFD:
-
Upon receiving the AMP Trigger frame indicating a time-slot based scheduled access for non-AP AMP STAs, a non-AP AMP STA performs the following actions:
If the AMP Trigger frame carries the ID of the non-AP AMP STA, the non-AP AMP STA transmits an uplink AMP PPDU carrying the requested response.
[Reference: 25/1240r0, 25/0817r0
MAC Aspects of Backscatter non-AP STAs:
SP1: you agree to add to the 11bp SFD:
-
A Backscatter non-AP AMP STA uses Electronic Product Code (EPC) as its unique global identifier.
NOTE – EPC is defined by the EPC Tag Data Standard (TDS)
Length of the EPC is TBD
[Reference: 25/1239r0, 25/0818r0]
SP2: Do you agree to add to the 11bp SFD:
-
Backscatter non-AP AMP STAs support the tag memory defined by the UHF RFID Standard.
-
EPC memory (StoredCRC, StoredPC and EPC) is mandatory
-
Reserved, TID and USER memory are optional
-
NOTE – UHF RFID Standard refers to the EPC® Radio-Frequency Identity Generation-2 Version 2 UHF RFID Standard.
[Reference: 25/1239r0, 25/0818r0]
SP3: Do you agree to add to the 11bp SFD:
-
11bp shall support the following UHF commands for backscatter communication:
-
Select, Read, Write, Authenticate
-
Other UHF commands supported by 11bp is TBD
-
NOTE – The UHF commands are defined by the EPC® Radio-Frequency Identity Generation-2 Version 2 UHF RFID Standard.
[Reference: 25/1239r0, 25/0818r0]
SP4: Do you agree to add to the 11bp SFD:
-
Backscatter non-AP AMP STAs support the following flags defined by the UHF RFID Standard.
-
Inventoried flags for S0, S1, S2, S3 sessions
-
Selected flag (SL)
[Reference: 25/1239r0, 25/0818r0]
SP5: Do you agree to add to the 11bp SFD:
-
Backscatter non-AP AMP STAs support the tag states (as defined by the UHF RFID Standard) that correspond to the supported UHF commands.
[Reference: 25/1239r0, 25/0818r0]
Best Regards,
Rojan Chitrakar
Hi Bo,
For tomorrow (Jul 30th
) AM1, I request to replace 25/819 with 25/1239, since 1239 is already well discussed in the past, as well as offline. I will do my best to complete in 10 Mins.
11-25/0819, amp-security-follow-up, Rojan Chitrakar (Huawei)
11-25/1239,
MAC Aspects of Backscatter non-AP AMP STAs, Rojan Chitrakar (Huawei)
I also request to swap the sequence for 1242 and 1240, i.e., present 1242 before 1240:
11-25/1242, AMP Acknowledgments, Rojan Chitrakar (Huawei)
11-25/1240, AMP Channel Access, Rojan Chitrakar (Huawei)
Best Regards,
Rojan Chitrakar
From:
sun.bo1@xxxxxxxxxxxxxxxx <sun.bo1@xxxxxxxxxxxxxxxx>
Sent: Sunday, July 27, 2025 10:43 PM
To: STDS-802-11-TGBP@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBP] TGbp meeting agenda for Jul 802 plenary session uploaded
To proceed the submissions as many as possible during the Jul plenary session, one more TGbp meeting slot is added to Tue PM2.
An updated meeting agenda is uploaded, including incorporated changes requested by members.
https://mentor.ieee.org/802.11/dcn/25/11-25-0990-01-00bp-tg-bp-meeting-agenda-for-jul-plenary-2025.pptx
Bo
Original
Subject: [STDS-802-11-TGBP] TGbp meeting agenda for Jul 802 plenary session uploaded
Thanks to those who have announced submissions in the TGbp reflector. The submission requests have been incorporated into the
TGbp meeting agenda and uploaded to the mentor server.
https://mentor.ieee.org/802.11/dcn/25/11-25-0990-00-00bp-tg-bp-meeting-agenda-for-jul-plenary-2025.pptx
There're around 50 submissions received which is much more than we have seen in past meetings. According to our history progress,
not all submissions will be presented during Jul plenary session. Some of them will be deferred to following TCs if the authors agree. All received submissions are classified into several topic groups. Topics of more submissions have higher pirority to present.
More meeting slots are arragned for PHY topics.
If your submisisons are in the agenda, please
upload your submissions at least 24 hours before you presenting them to the group. And if your submissions are
NOT in the submission list, or you have special request for your submisisons (time, order, topic group), let me know it.
Looking forward to seeing you in Madrid!
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