| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Bo, Based on further offline feedback, I have revised SPs1 to 7 as below; please help to update. Sorry for the late notice. SP1: Do you agree to add to the 11bp SFD:
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: Do you agree to add to the 11bp SFD:
[Reference: 25/1240r0, 25/0817r0, 25/0818r0] SP3: Do you agree to add to the 11bp SFD:
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] SP4: Do you agree to add to the 11bp SFD:
[Reference: 25/1240r0, 25/0817r0, 25/0818r0] SP5: Do you agree to add to 11bp SFD:
[Reference: 25/1102r1, 25/0817r0, 25/0818r0] SP6: Do you agree to add to 11bp SFD:
[Reference: 25/1102r1, 25/0817r0, 25/0818r0] SP7: Do you agree to add to 11bp SFD:
[Reference: 25/1102r1, 25/0817r0, 25/0818r0] Best Regards, Rojan Chitrakar From: Rojan Chitrakar <00002005fb56ded7-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Bo, Based on feedback received so far, I have updated/consolidated the 12 SPs I plan the run this time as below. Please note that the first four channel access SPs are based on the deferred SPs from the May F2F.
AMP Channel Access:
SP1: Do you agree to add to the 11bp SFD:
§
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: Do you agree to add to the 11bp SFD:
§
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: Do you agree to add to the 11bp SFD:
§
Response Type: Type of the solicited uplink response
§
The frame may also carry:
o
Number of Slots (N) indicating the number of slots immediately after the AMP Trigger frame that are allocated for uplink transmissions, and,
o
IDs of one 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] SP4: Do you agree to add to the 11bp SFD:
§
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, 25/0818r0] AMP Frame Formats:
SP5: Do you agree to add to 11bp SFD:
[Reference: 25/1102r1, 25/0817r0, 25/0818r0] SP6: Do you agree to add to 11bp SFD:
[Reference: 25/1102r1, 25/0817r0, 25/0818r0] SP7: Do you agree to add to 11bp SFD:
[Reference: 25/1102r1, 25/0817r0, 25/0818r0] SP8: Do you agree to add to the 11bp SFD:
§
The UHF command is carried in the Frame Body field [Reference: 25/1102r1, 25/0817r0, 25/0818r0] Backscatter non-AP STAs:
SP9: Do you agree to add to the 11bp SFD:
§
EPC memory comprises the StoredCRC, StoredPC and EPC
§
Length of the EPC is TBD
§
NOTE – EPC, StoredCRC & StoredPC are defined by the UHF RFID Standard which refers to the EPC® Radio-Frequency Identity Generation-2 Version 2 UHF RFID Standard.
[Reference: 25/1239r0, 25/0818r0] SP10: Do you agree to add to the 11bp SFD:
[Reference: 25/1239r0, 25/0818r0] SP11: Do you agree to add to the 11bp SFD:
[Reference: 25/1239r0, 25/0818r0] AMP Acknowledgments:
SP12: Do you agree to add to the 11bp SFD:
[Reference: 25/1242r0] Best Regards, Rojan Chitrakar From: Rojan Chitrakar <00002005fb56ded7-dmarc-request@xxxxxxxxxxxxxxxxx>
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:
[Reference: 25/1102r1, 25/0817r0, 25/0818r0] SP2: Do you agree to add to 11bp SFD:
§
Frame Control
o
Always present
§
ID
o
The number of the ID fields and whether they are always present is TBD.
§
Length
o
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:
[Reference: 25/1102r1, 25/0817r0, 25/0818r0] SP4: Do you agree to add to 11bp SFD:
[Reference: 25/1102r1, 25/0817r0, 25/0818r0] SP5: Do you agree to add to 11bp SFD:
[Reference: 25/1102r1, 25/0817r0, 25/0818r0] SP6: Do you agree to add to 11bp SFD:
[Reference: 25/1102r1, 25/0817r0, 25/0818r0] SP7: Do you agree to add to 11bp SFD:
[Reference: 25/1102r1, 25/0817r0, 25/0818r0] SP8: Do you agree to add to the 11bp SFD:
§
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:
[Reference: 25/1242r0] Best Regards, Rojan Chitrakar From: Rojan Chitrakar <00002005fb56ded7-dmarc-request@xxxxxxxxxxxxxxxxx>
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:
§
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:
§
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:
§
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:
§
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:
§
Response Type: Type of the solicited uplink response
§
The frame may also carry:
o
Number of Slots (N) indicating the number of slots immediately after the AMP Trigger frame that are allocated for uplink transmissions, and,
o
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:
§
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:
§
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:
[Reference: 25/1239r0, 25/0818r0] SP3: Do you agree to add to the 11bp SFD:
[Reference: 25/1239r0, 25/0818r0] SP4: Do you agree to add to the 11bp SFD:
[Reference: 25/1239r0, 25/0818r0] SP5: Do you agree to add to the 11bp SFD:
[Reference: 25/1239r0, 25/0818r0] Best Regards, Rojan Chitrakar From: Rojan Chitrakar <00002005fb56ded7-dmarc-request@xxxxxxxxxxxxxxxxx>
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/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>
Hello, all, 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. Best Regards, Bo
Original From: 孙波 Date: 2025年07月26日
05:21 Subject: [STDS-802-11-TGBP] TGbp meeting agenda for Jul 802 plenary session uploaded Hello, all, 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. 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! Best Regards, Bo 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 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 |