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

[STDS-802-11-TGBN] Co-TDMA ICR related CR SP 11/25-2367



Dear all,

I plan to run a SP on the Co-TDMA ICR this week (21 CIDs) 11/25-2367r8

For those who could not follow the presentation and discussion during last week’s ad-hoc meeting, I would like to summarize the main points and hope we can run the SP in an efficient way.

The CR document adds two information fields to the Co-TDMA ICR, allowing the Coordinated AP to provide additional information related to the TXOP sharing request in addition to yes/no:

  1. Time Requested
  2. Vendor-specific information in a vendor-defined format

Compared to the previous version, the CR has been significantly simplified and now includes fewer options.

After the presentation, the main discussion points were as follows.

Vendor-specific information in a vendor-defined format

The concern raised was that the Co-TDMA ICR should be kept simple in 802.11bn. Additional fields could be considered later, for example in Wi-Fi 9 or beyond, after Co-TDMA has been tested in the field.

The supporting view was that vendor-specific information would allow vendors to experiment with different feedback options in the ICR and potentially improve the Co-TDMA feature based on practical experience.

Time Requested

The concern raised was that Time Requested may not provide significant benefit, since only a short duration is shared and the information may not be useful in the ICR. It was also noted that TXOP sharing allocation could be based on semi-static information exchanged during Co-TDMA negotiations, without requiring instantaneous information.

The supporting view was that, without Time Requested information, the Coordinating AP may over- or under-allocate time to the Coordinated AP. For example, it may allocate 1 ms when only 0.5 ms is needed while under-allocating another AP that would need 1.5ms, reducing the efficiency of the Co-TDMA procedure. Semi-static information may not be sufficient because variations in MCS, medium access time, and other factors can have a large impact on the instantaneous resource needs.

Best regards,
Klaus






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