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

Re: [STDS-802-11-TGBN] CoBF SPs Request

Hi Alfred,

 

Could you please also queue the following CBF SPs in 11-25-413r0 (maybe better to run them before the third SP from Sherief below):

 

SP#1

Do you agree:

    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 signaling and derivation of these timeout periods to the STA are TBD.
    • 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 ?

 

 

SP#2

 

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 ?

 

 

Regards,

Dibakar

 

 

From: Sherief Helwa <00002dded7ae4daf-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Monday, March 10, 2025 6:16 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] CoBF SPs Request

 

Hi Alfred,

 

Would you please add the following CoBF SPs to the MAC queue?

 

  • Do you agree to use the following CoBF transmission sequence to support STAs requiring ICF/ICR before data frame exchanges?
    • The frame sequence consists of:
      • A CoBF Invite/CoBF Response frame exchange between the sharing and shared APs.
      • Follows ICF/ICR frame exchanges between the APs and their associated STAs happening sequentially across the two APs; sharing AP then shared AP.
        • The presence of the ICF/ICR frame exchange from each AP is conditional on the CoBF PPDU being addressed to one or more STAs.
        • The presence of the ICF/ICR frame exchange from each AP is indicated in the CoBF Invite/Response frames.
        • ICF1-ICR1 are exchanged between the sharing AP and its STAs
        • ICF2-ICR2 are exchanged between the shared AP and its STAs
      • Finally, a CoBF Trigger/Sync frame preceding the data PPDUs sent by the two APs simultaneously.
      • Frame sequence for Ack information polling is TBD.
      • Whether the CoBF-invite and ICF1 can be merged and/or CoBF-response and ICF2 can be merged is TBD.

 

 

 

  • Do you agree to use the following sequence for acknowledgement information polling from STAs scheduled in a CoBF transmission sequence
    • MU-BAR/BA frame exchanges are used by each AP separately, i.e., sequentially.

NOTE1: The first MU-BAR frame (transmitted by the sharing AP) can be embedded in the preceding DL PPDU as in baseline.

NOTE2: The frame sequence for eliciting simultaneous ACKs from clients of both sharing and shared APs if agreed in PHY is TBD.

 

 

 

 

  • Do you agree that:
    • 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.

 

 

 

  • 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.

 

 

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

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