| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi, Giovanni,
Thank you for sharing your nice work.
For doc 25/0599, Section 37.8.1.1, page 22 states：
[CID1788]The MAPC framework includes a set of schemes (Co-BF, Co-SR, Co-TDMA, and Co-RTWT) and procedures in which UHR APs operating their BSSs on the same primary 20 MHz channel coordinate to improve one or more among interference level, medium utilization efficiency, communication reliability, and latency.
I completely agree that these schemes require APs to work on the same P20 as a necessary condition. However, there lacks evidence of how to achieve such a condition. It is highly likely that two APs configure different P20 when they perform channel selection separately. According to baseline (pls check REVme Section [Channel selection procedures], APs each choose the least occupied channel as P20 in order not to overlap.
For consistency, I would suggest including a procedure or some description to accommodate the above issue introduced by the baseline rule. Thanks for your consideration
Best regards,
Yuxin
TCL Industries
Hi Giovanni,
Thanks for preparing and sharing the PDTs. Sorry for taking a while.
I attach the document including my comments for your consideration and action.
Best regards,
Gaius
Panasonic
From: Giovanni Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, 9 April 2025 5:35 am
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] MAC PDTs (2 PDTs): MAPC Signaling and Protocol Aspects, Co-RTWT Signaling and Protocol Aspects
[MAC PDT: MAPC Signaling and Protocol Aspects]
[MAC PDT: Co-RTWT Signaling and Protocol Aspects]
Dear MAPC and Co-RTWT TTT members,
I prepared two PDTs on:
- MAPC Signaling and Protocol Aspects (r1)
- Co-RTWT Signaling and Protocol Aspects (r1)
The first PDT sets the stage for the second by defining elements, frames, and protocols (discovery and negotiations).
The second PDT uses the first as a baseline and further details aspects for Co-RTWT.
The PDTs incorporates the latest passing motions on the topic as well as addressing several CIDs, as reported in the Abstract.
The goal is to collect a first round of comments on these PDTs before presentation of the documents (@Alfred Asterjadhi, would target presentation as early as next week), and refine as needed after the presentation to finalize the documents.
If you have volunteered for the MAPC or the Co-RTWT TTT, please check whether your name/affiliation/contact is correctly included in the PDT.
If your name is spelled incorrectly, or is missing an affiliation, or has an incorrect affiliation, or if your name is missing entirely, or if you are in the list and do not wish to be included in the author list, then please send an individual email to:
Feel free to send any comments on the existing PDTs (i.e. the draft text, not the author list) in 25/0599r1 and/or 25/600r1 as a response to this email, so that all TTT members may see your comment and so that we can discuss the comment and then debate any changes to the document. This will be the general process going forward for text that is included in the document. To identify whether your email is for either or both of the PDTs, please add either or both tags at the beginning of the email, as shown in this email.
Thank you in advance,
Giovanni Chisci (QC)
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