Hi, Alfred. Can you please add the following SP to the agenda? SP: Do you agree to add the following text to the TGbn SFD? - If an initial control frame includes an intermediate FCS for UHR STA(s) that precedes padding and the FCS field, the intermediate FCS has the size of 32 bits.
Supporting list: [24/1129] Best Regards SunHee Baek From: Sindhu Verma <000011381223f2e2-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, September 11, 2024 4:16 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Updated TGbn Agenda for Sept F2F and Action Items Hi Alfred, Can you please add the following SPs to the agenda? NPCA: (Reference:11-24/1093) SP1: Do you agree to define a mode of operation in NPCA where the NPCA non-AP does not use untriggered UL transmissions on the NPCA primary channel - This mode can be enabled/disabled by the AP
- Whether the mode is for all associated non-APs or per non-AP is TBD
- TBD whether MU EDCA parameters mechanism is used for this or not
SP2: Do you agree with the following: - An NPCA STA shall initiate frame exchange on the NPCA Primary channel with an NPCA Initial Control Frame in the non-HT PPDU or non-HT duplicate PPDU format using a rate of 6 Mb/s, 12 Mb/s, or 24 Mb/s
- Details on NPCA ICF are TBD
In-device-coexistence: (Reference: 11-24/1559) SP1: Do you agree with the following: - Unavailability Target Start Time is indicated using 9 bits with a granularity of 64us
- Unavailability Duration is indicated using 9 bits with a granularity of 64us
SP2: Do you support that - The AP maintains up to one unavailability report per STA
- And the most recent unavailability report (received in a control frame) is the valid one
Regards, Sindhu Hi Alfred, Can you please add the following straw polls to the list? - Do you support that an UHR STA that uses the power save mode to transition from lower capability (LC) mode to higher capability (HC) mode, advertises the amount of padding it needs in a received initial control frame?
- Padding values range between 0 and 256 us with a TBD resolution
- Do you support that if a UHR STA (UHR non-AP STA or UHR Mobile AP) operates with the power save mode where the STA transitions from a lower capability mode to a higher capability mode upon reception of an initial control frame (that we call here DPS), then its associated peer STA, that supports transmitting intermediate FCS, shall include an intermediate FCS, if needed by the STA, in the initial control frame that it transmits to the STA.
– Mandatory/optional support for transmitting intermediate FCS is TBD Regards, Sherief Hi Alfred, Can you please add the following straw polls to the list? SP1: Do you support defining the following fields for unavailability indication in M-STA BA frames: - an Unavailability Target Start Time field defined as the TSF time at which the STA becomes unavailable (duration and resolution TBD, expectation is to use a portion of the TSF)
- an Unavailability Duration field defined as the time during which the STA is unavailable (field may be not present or set to an unknown value)
Supporting list: [11-24/543, 11-24/857, 11-24/1226, 11-24/1247] SP2: Do you support to define a special Feedback Per AID TID Info field (name TBD) that carries control feedback in the M-BA frame? - The control feedback (i.e. unavailability indication) is carried instead of the BlockAck Bitmap in that Feedback Per AID TID Info field
- The Ack Type subfield of the Per AID TID Info field is set to 0 and the TID subfield of the Per AID TID Info field is set to a reserved value
- The AID11 subfield of this Per AID TID Info field is set to a reserved TBD value if the control feedback is addressed to all STAs or to the AID11 that identifies the intended recipient STA
- The Starting Sequence Number field of this Per AID TID Info field is reserved
Supporting list: [11-24/543, 11-24/857, 11-24/1226, 11-24/1247] SP3: Do you support that all the fields (These are the fields currently used for TB PPDU generation) of the Common Info field after the UL BW field are reserved in a BSRP Trigger frame that solicits a non-HT (Dup) PPDU except: - for the field that indicates the responding PPDU format
- for the Special User Info Field Flag subfield
These new reserved fields can be used for UHR purposes Supporting list: [11-24/1247, 11-24/1558, 11-24/1562] Regards, Sherief WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hello all, Revised version of the July F2F agenda is uploaded. This revision contains the queue contents until this Saturday evening (PT). Please let me know if i missed anything, such as missing distribution, wrong classification, etc (note that the queue for SPs is partially populated and is work in progress). It also contains a distribution of presentations over the multiple sessions we have scheduled for next week. As we prepare for next week F2F, please take notice/act on the following: 1) Check that the presentations are properly classified and that they are uploaded to the server as soon as possible and no later than 24 hours prior to the scheduled meeting. Presentations that are not uploaded in time will be removed from the list. 2) Some topics have a lot of contributions and from the title of these contributions they seem to discuss similar concepts. If your contribution falls in this category then please check with the other members if there is room for early convergence so that we can optimize the agenda time. 3) As usual, there are 45 mins slots of SP time for MAC and Joint. Plan is to use these slots for running SPs on previously presented contributions and foment convergence so that we can make progress. The reflector is a great tool to seek early feedback from members. Looking forward to seeing/talking to all of you next week and safe travels. PS: Next revision of the agenda will be posted after the usual Sunday 5:00pm (Hawaii time) deadline for submissions requests, and will include any feedback/requests received prior to said deadline. -- IEEE802.11 TGbe/TGbn Chair, Qualcomm Technologies Inc. Office #: +1 858 658 5302
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1 |