Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[STDS-802-11-TGBN] CoBF Motions Request

Hi Alfred,

 

Can you please add the following passed SPs to the motion list to be run?

 

SP1: If an eMLSR non-AP MLD that receives an ICF addressed to one of its affiliated STAs during CoBF sequences and if the affiliated STA responds with an ICR, then the eMLSR non-AP MLD shall follow the eMLSR procedure defined in 35.3.17, except that the STA shall use an extended time-out period prior to switching back upon inactivity:

  • The duration of the extended time-out period shall be sufficient to cover any inactivity period within the COBF sequence, e.g. (but not limited to), from the end of the ICR to the beginning of the data PPDU, or from the DL PPDU until the beginning of the MU-BAR frame from the shared AP for STAs associated with the shared AP
  • The duration of the extended timeout period is explicitly indicated to the STA in the ICF frame sent by its associated AP.
  • Once the eMLSR STA(s) switch back to listen mode, they start using the default time-out period (aSIFSTime + aSlotTime + aRxPHYStartDelay) in future TXOPs unless otherwise indicated in the ICF.
  • This is applicable to CoBF transmission sequence

Supporting document: [25/412, 25/0879]

Result: No objection.

 

SP2: For DPS non-AP STA(s) scheduled with CoBF in high capability mode, the same switch-back behavior as for eMLSR with extended time-out period is used

  • The RTS frame shall not be used as an ICF for DPS in the CoBF Transmission sequence even when the DPS STA does not have any DPS padding required

NOTE: The RTS frame cannot be modified to include the extended timeout period usage and the extended timeout period duration indications.

Supporting document: [25/412, 25/0879]

Result: No objection.

 

SP3: Do you agree that an AP shall use the BSRP NTB Trigger frame variant for the Sounding Invite frame

  • The Sounding Response frame shall be M-BA
  • TBD whether there’s another frame variant allowed for the Sounding Invite/Response frame

Supporting document: [25/412, 25/0879]

Result: No objection.

 

SP4: Do you agree that an AP shall use the BSRP NTB Trigger frame variant for the CoBF Invite frame

  • The CoBF Response frame shall be M-BA
  • TBD whether there’s another frame variant allowed for the CoBF Invite/Response frame

Supporting document: [25/412, 25/0879]

Result: No objection.

 

SP5: Do you agree that an AP MLD that receives an ICR from a STA affiliated with an EMLSR non-AP MLD during CBF data frame exchange does not attempt to transmit to the eMLSR non-AP MLD on another link during the extended time-out periods, per baseline behavior.

Supporting document: [25/412, 25/0879]

Result: No objection.

 

SP6: Do you support that any CoBF sounding sequence that includes Cross-BSS CSI collection shall be initiated by a two-way handshake between the two APs participating in the sequence

  • The two-way handshake exchange consists of a Sounding Invite frame and a Sounding Response frame.
  • The Sounding Invite/Response frame exchange is used to:
    • Confirm the availability of both APs for CSI collection.
    • TBD for indication whether each AP will include ICF/ICR exchanges with its client or not.
    • Further information to be exchanged is TBD.

Supporting document: [25/412, 25/0879, 25/0492]

Result: No objection.

 

SP7: Do you support that in CBF transmission phase, the Feedback User Info field in the BSRP/MU-RTS Trigger addressed to EMLSR/DPS STA carries the extended timeout period duration?

  • A new feedback type value is defined for CoBF.
  • An “Extended Timeout Duration” field with a TBD length is included in the Feedback user Info field
    • The duration value is reported with granularity of 4 us.
    • A value 0 of the “Extended Timeout Duration” field is an indication to the STA to follow the default eMLSR/DPS switch back behavior, i.e., do not use an extended timeout period.
    • Whether the field indicates maximum value or actual value is TBD.

Supporting document: [25/412, 25/879]

Result: No objection.

 

 

Regards,

Sherief

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