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

Re: [STDS-802-11-TGBN] [EXT] [STDS-802-11-TGBN] Motion Request

Happy to Second the first motion.

 

Please add supporting docs 24/1883, 24/1884 to the first motion.

 

Thanks,

Giovanni

 

 

From: Liwen Chu <liwen.chu@xxxxxxx>
Sent: Thursday, March 13, 2025 7:22 AM
To: Giovanni Chisci <gchisci@xxxxxxxxxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: RE: [EXT] [STDS-802-11-TGBN] Motion Request

 

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Hi Alfred,

 

Please add the following  motion requests to MAC motion list.

 

Best Regards,

Liwen

 

Move to add the following text to the TGbn SFD:

  • a serving AP MLD can use the BTM procedure with update(s) (if required) to recommend one or more candidate target AP MLDs within the UHR seamless roaming mobility domain to a non-AP MLD for roaming.
    • Note – An AP can transmit the BTM Request frame unsolicited or as a response to BTM Query from a non-AP MLD.

TBD – detailed information to be carried

Supporting Documents: 24/1889r1

SP result: no objections

 

 

Move to add the following text to the TGbn SFD:

  •                An AP shall not allow the use of NPCA within its BSS if the BSS operating bandwidth is less than or equal to 40 MHz.

Supporting Documents: 24/1891r2

SP result: no objections

 

Move to add the following text to the TGbn SFD:

  •                If a TXOP on the NPCA Primary channel overlaps with the TBTT, the AP shall not transmit the Beacon frame or group addressed frames until it switches back to the BSS Primary channel.
  •                NOTE – The NPCA AP and non-AP STA participating in frame exchanges must not switch back to the BSS Primary channel at the TBTT and can continue operating on NPCA Primary until the OBSS transmission ends on BSS Primary channel. In such cases, the group addressed frame will be buffered and delivered immediately following the next DTIM Beacon, unless explicitly specified otherwise.

Supporting Documents: 24/1891r2

SP result: no objections

 

 

Move to amend Motion #273 as following:

  • TGbn defines or improves an existing mechanism so that a non-AP STA that is a TXOP responder can indicate its buffered low latency LL traffic needs (for traffic from the TxOP TXOP responder to the TxOP TXOP Holder) in a control response frame Multi-STA Block Ack. The TXOP holder should consider the indication in determining subsequent actions. Subsequent actions related to this indication are out of the scope of the standard.
    • Note: whether an AP can Indicate  its low latency needs is TBD
    • The Low Latency Indication is included in the Feedback field of the Feedback Per AID TID Info field (the one that carries control feedback).
    • The Feedback Type field is set to 1
      • Note: Feedback Type field set to 0 is used for DUO feedback
    • TBD bits in the Feedback field is defined to provide the low latency need

Supporting Documents: 24/421r0

SP result: no objections

 

 

 

 

 

 

From: Giovanni Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, March 13, 2025 6:52 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [EXT] [STDS-802-11-TGBN] Motion Request for MAPC and Co-RTWT

 

Caution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, report the message using the 'Report this email' button

 

Dear Alfred,

 

Could you please add the following Motions to the list for TGbn MAC?

 

To all, please let me know if you want to add supporting docs.

 

Best,

Giovanni

 

 

Move to add the following text to the TGbn SFD:

TGbn defines new actions for Public Action frames for MAPC communications such as discovery and negotiations?

  • An action is defined for MAPC Discovery
  • An action is defined for MAPC Negotiation Request
  • An action is defined for MAPC Negotiation Response
  • Others are TBD

Supporting Documents: 24/1220r1, 24/0407r0

SP result: no objections

 

Move to add the following text to the TGbn SFD:

When an AP use Management frames to discover the capabilities and/or parameters of individual M-AP coordination schemes, the AP shall use the defined MAPC Public Action frame with the following setting:

  • The action field is set to MAPC Discovery

Supporting Documents: 24/1220r1

SP result: no objections

 

Move to add the following text to the TGbn SFD:

  • When an AP (AP1) uses an individually addressed Management frame to initiate a negotiation to establish agreements for M-AP coordination schemes (if enabled by another AP (AP2)), the AP (AP1) shall use the defined MAPC Public Action frame with the following setting:
    • The action field is set to MAPC Negotiation Request
  • If new negotiations are disabled by another AP (AP2) the AP (AP1) shall not send a negotiation request the other AP (AP2)
    • TBD details of ‘new negotiations disabled’

Supporting Documents: 24/1220r1, 25/0378r0

SP result: no objections

 

 

Move to add the following text to the TGbn SFD:

When an AP (AP2) receives an individually addressed Management frame that initiates a negotiation to establish agreements for M-AP coordination schemes, the AP (AP2) shall respond by using the defined MAPC Public Action frame with the following setting, if negotiations are enabled:

    • The action field is set to MAPC Negotiation Response

Supporting Documents: 24/1220r1

SP result: no objections

 

Move to add the following text to the TGbn SFD:

A Co-RTWT Requesting AP, shall include one or more Co-RTWT Parameter Set fields corresponding to each requested R-TWT schedule in the TBD individually addressed Management frame used for the request to the Co-RTWT Responding AP. The Co-RTWT Parameter Set field includes the following:

  • Target Wake Time field
  • Broadcast TWT ID field
  • Broadcast TWT Persistence
  • TWT Wake Interval Mantissa
  • TWT Wake Interval Exponent
  • Nominal Minimum TWT Wake Duration
  • TBD other fields

Supporting Documents: 24/1220r1, 23/1887r1, 24/160r1, 24/908r0, 24/0407r0

SP result: 97 Y / 28 N / 66 A

 

 

From: Giovanni Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, March 12, 2025 3:18 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] FW: Request for MAPC and Co-RTWT SPs

 

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Dear Alfred,

 

I would kindly request to amend the agenda for TGbn so that the timestamp for the request of these SPs is honored, since these were requested before several SPs that are currently in agenda.

 

I also provide an updated support list.

 

Thanks,

Giovanni

 

 

SPa1 (MAPC Public action frame actions)

Do you support to define new actions for Public Action frames for MAPC communications such as discovery and negotiations?

  • A new action is defined for MAPC Discovery
  • An action is defined for MAPC Negotiation Request
  • An action is defined for MAPC Negotiation Response
  • Others are TBD

Supporting Documents: 24/1220r1, 24/0407r0

 

SPa2 (M-AP coordination discovery)

Do you support that when an AP use Management frames to discover the capabilities and/or parameters of individual M-AP coordination schemes, the AP shall use the defined MAPC Public Action frame with the following setting:

  • The action field is set to MAPC Discovery

Supporting Documents: 24/1220r1

 

SPa3 (M-AP coordination negotiations - Request)

  • Do you support that, when an AP (AP1) uses an individually addressed Management frame to initiate a negotiation to establish agreements for M-AP coordination schemes (if enabled by another AP (AP2)), the AP (AP1) shall use the defined MAPC Public Action frame with the following setting:
    • The action field is set to MAPC Negotiation Request
  • If new negotiations are disabled by another AP (AP2) the AP (AP1) shall not send a negotiation request the other AP (AP2)
    • TBD details of ‘new negotiations disabled’

Supporting Documents: 24/1220r1, 25/0378r0

 

 

SPa4 (M-AP coordination negotiations - Response)

Do you support that when an AP (AP2) receives an individually addressed Management frame that initiates a negotiation to establish agreements for M-AP coordination schemes, the AP (AP2) shall respond by using the defined MAPC Public Action frame with the following setting, if the negotiation is not disabled:

    • The action field is set to MAPC Negotiation Response

Supporting Documents: 24/1220r1

 

 

SPc1 (Co-RTWT Parameters Set)

A Co-RTWT Requesting AP, shall include one or more Co-RTWT Parameter Set fields corresponding to each requested R-TWT schedule in the TBD individually addressed Management frame used for the request to the Co-RTWT Responding AP. The Co-RTWT Parameter Set field includes the following:

  • Target Wake Time field
  • Broadcast TWT ID field
  • Broadcast TWT Persistence
  • TWT Wake Interval Mantissa
  • TWT Wake Interval Exponent
  • Nominal Minimum TWT Wake Duration
  • TBD other fields

Supporting Documents: 24/1220r1, 23/1887r1, 24/160r1, 24/908r0, 24/0407r0

 

 

From: Giovanni Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, March 11, 2025 8:40 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] Request for MAPC and Co-RTWT SPs

 

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Dear Alfred,

 

Could you please add to the MAC queue the following SPs on MAPC and Co-RTWT? I would like to run them since they have been harmonized with many members.

 

To all, please let me know if you would like to add your contributions to the support list.

 

Thank you in advance,

Giovanni

 

SPa1 (MAPC Public action frame actions)

Do you support to define new actions for Public Action frames for MAPC communications such as discovery and negotiations?

  • A new action is defined for MAPC Discovery
  • An action is defined for MAPC Negotiation Request
  • An action is defined for MAPC Negotiation Response
  • Others are TBD

Supporting Documents: 24/1220r1

 

SPa2 (M-AP coordination discovery)

Do you support that when an AP use Management frames to discover the capabilities and/or parameters of individual M-AP coordination schemes, the AP shall use the defined MAPC Public Action frame with the following setting:

  • The action field is set to MAPC Discovery

Supporting Documents: 24/1220r1

 

SPa3 (M-AP coordination negotiations - Request)

  • Do you support that, when an AP (AP1) uses an individually addressed Management frame to initiate a negotiation to establish agreements for M-AP coordination schemes (if enabled by another AP (AP2)), the AP (AP1) shall use the defined MAPC Public Action frame with the following setting:
    • The action field is set to MAPC Negotiation Request
  • If new negotiations are disabled by another AP (AP2) the AP (AP1) shall not send a negotiation request the other AP (AP2)
    • TBD details of ‘new negotiations disabled’

Supporting Documents: 24/1220r1

 

 

SPa4 (M-AP coordination negotiations - Response)

Do you support that when an AP (AP2) receives an individually addressed Management frame that initiates a negotiation to establish agreements for M-AP coordination schemes, the AP (AP2) shall respond by using the defined MAPC Public Action frame with the following setting, if the negotiation is not disabled:

    • The action field is set to MAPC Negotiation Response

Supporting Documents: 24/1220r1

 

 

SPc1 (Co-RTWT Parameters Set)

A Co-RTWT Requesting AP, shall include one or more Co-RTWT Parameter Set fields corresponding to each requested R-TWT schedule in the TBD individually addressed Management frame used for the request to the Co-RTWT Responding AP. The Co-RTWT Parameter Set field includes the following:

  • Target Wake Time field
  • Broadcast TWT ID field
  • Broadcast TWT Persistence
  • TWT Wake Interval Mantissa
  • TWT Wake Interval Exponent
  • Nominal Minimum TWT Wake Duration
  • TBD other fields

Supporting Documents: 24/1220r1, 23/1887r1

 

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