| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Sanket,
Thanks for quick reponse. Please see my addition question inline.
Best Regards
Taeyoung
-------------------------------------------------------
--------- Original Message ---------
Sender : Sanket Kalamkar <sankal@xxxxxxxxxxxxxxxx>
Date : 2025-07-26 00:15 (GMT+9)
Title : Re: [STDS-802-11-TGBN] (2) [STDS-802-11-TGBN] (2) [STDS-802-11-TGBN] PDT-MAC-CR-Co-TDMA Part 3
Hi Taeyoung,
Thanks for the questions. Please see my responses inline.
Best,
Sanket
From: Taeyoung HA <ty1115.ha@xxxxxxxxxxx>
Sent: Friday, July 25, 2025 1:43 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBN] (2) [STDS-802-11-TGBN] (2) [STDS-802-11-TGBN] PDT-MAC-CR-Co-TDMA Part 3
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Sanket, Thanks for your hard work on PDT. I have some clarification question on Traffic Profile field format. Q1) Could you elaborate the purpose of Allocated TXOP Duration field? Is it for determining the acceptability of Co-TDMA negotiation or determining the duration of TXOP to be shared in Co-TDMA operation? |
[Sanket] When combined with the periodicity of the traffic specified in the Allocation Interval field, the Allocated TXOP Duration field helps the sharing AP make decisions about whom to poll, based on the available resources and the resources requested by APs that have agreements with it.
[Taeyoung] Thanks for the clarification. I agree that this information could assist the sharing AP in making decisions.
However, since the amount of traffic and MCS at the polling phase can vary dynamically, it leads to uncertainties in the TXOP duration required for the shared AP.
Additionally, the sharing AP cannot guarantee Co-TDMA operation during the polling phase with this information.
Therefore, I believe this information could be exchanged during the polling phase. (exchange in the Negotiation phase of MAPC may not be effective.)
Q2) Why multiple Traffic Profile is needed for each AC? |
[Sanket] It is up to the requesting AP to decide how many traffic profiles it wishes to report (limited by the value of Traffic Profile Count field). An AP may have multiple traffic flows with varying periodicities and payloads that may not be adequately represented by a single TXOP duration and periodicity.
[Taeyoung] Thanks for the clarification. Could you explain why the Profile ID subfield is necessary?
Since these Traffic Profile fields are included in the MAPC Scheme Parameter Set, this information is just delivered through the MAPC Negotiation Request/Response.
These details do not need to be explicitly identified because they will be overridden by new MAPC Negotiation Request/Response messages.
(i.e., Partial update or delete of Traffic Profile can not be conducted in the current MAPC Framework)
I think Co-TDMA Coordinating AP just need summarized interval to determine which Co-TDMA coordinated AP can be candidate for polling phase. [Sanket] Could you please elaborate on the design a bit more? [Taeyoung] I can get your point through the above answer. Some traffic may not be represented by a single periodicity. Best Regards, Taeyoung -------------------------------------------------------
--------- Original Message --------- Sender : 源μ 뺤€ <jungjun.kim@xxxxxxxxxxx> Connectivityν쒖€Lab(SR)/μ궪μ꽦μ 꾩 Date : 2025-07-25 17:39 (GMT+9) Title : Re: [STDS-802-11-TGBN] (2) [STDS-802-11-TGBN] PDT-MAC-CR-Co-TDMA Part 3
Hi Sanket, Thank you for preparing the document. I would also like to share a suggestion on the PDT. For Per-AC Traffic Info field, an AC may have different meanings for differenet APs in terms of QoS characteristics or channel access probability. In this context, I think it would be better for a reqeuseting AP to include some more information about ACs. Best Regards Jungjun Kim
--------- Original Message --------- Sender : 援ъ’낇 <jh89.koo@xxxxxxxxxxx> Connectivityν쒖€Lab(SR)/μ궪μ꽦μ 꾩 Date : 2025-07-25 17:21 (GMT+9) Title : Re: [STDS-802-11-TGBN] PDT-MAC-CR-Co-TDMA Part 3
Hi Sanket,
Thanks for working on the Co-TDMA negotiation details. Attached please find my comments and suggestions. Summary of my comments are as follows:
1. We may need to specify the condition to the value of the Rx TXOP Return Support field to 1 in consideration of the Co-TDMA negotiation results (specifically, Rx TXOP Return Support field setting during the Co-TDMA negotiation) with any polled APs in a Co-TDMA ICF.
2. It seems more appropriate if Traffic Control field is included in the MAPC Request Parameter Set field rather than the MAPC Scheme Parameter Set field.
3. It would be much better if we specify reasons to allow multiple Traffic Profiles per AC.
4. Suggest to have βLengthβ field in the Traffic Profile field for future extensibility.
5. Suggest not to prevent using βAlternateβ MAPC Operation Type for future extensibility.
Hi Sanket,
Thanks for your work on Co-TDMA PDT. How about to including βAP TB PPDU Response Supportedβ into the Co-TDMA Info field? This information seems to be only used for Co-TDMA, isnβt it?
Best Regards, GeonHwan Kim LG Electronics
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
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 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
