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

Re: [STDS-802-11-TGBN]   Initiate the discussion of definitions about coordinating/coordinated AP

Hi Chun Huang, Giovanni,

 

Just to state my preference:

 

I have a slight preference towards option 1 since it seems more intuitive and flexible.
For example, Co-RTWT coordinated AP can still be viewed as a coordinated AP under option 1’s definition but not under Option 2. Also, the definition may become more and more confusing with more schemes added.

Having said that, I think both options could be okay and I’m fine to go with whichever is easiest to move forward with.

 

Thanks for the discussions.

 

Best regards,

Gaius

 

From: Chun Huang <huang.chun2@xxxxxxxxxx>
Sent: Friday, 9 May 2025 11:23 am
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN]   Initiate the discussion of definitions about coordinating/coordinated AP

 

Hi Giovanni, 

 

Thank you for your email and your feedback.

I appreciate your support for Option 2.  We will remove the definitions related to MAPC requesting AP and MAPC responding AP as your suggestion, since they are already covered in  25/0599.



Best regards,

Chun Huang

Original

Date:  2025年05月07日 04:23  

Subject: Re: [STDS-802-11-TGBN]   Initiate the discussion of definitions about coordinating/coordinated AP  

Hi Chun,

 

Thanks for your email and your work on this.

 

I prefer Option 2. There is no harm in updating those definitions if there is need to do so (e.g., a new MAPC scheme is introduced).

 

I also wish to highlight that more feature-specific definitions are used in 25/0600

Coordinated restricted target wake time (Co-RTWT) requesting access point (AP): [Co-RTWT requesting AP] An AP that requests [CID742]other AP(s) to protect one or more of its R-TWT schedules.

Coordinated restricted target wake time (Co-RTWT) coordinated access point (AP): [Co-RTWT coordinated AP] An AP that extends protection for the R-TWT schedule(s) for which protection is requested  by a Co-RTWT requesting AP.

 

Could you also please remove or update the following definitions to match 25/0599? There is currently no use of those definitions in the subclause of MAPC Discovery, so we can keep the definition tailored  for MAPC negotiations, as per the use in the PDT.

Multi-AP coordination (MAPC) requesting AP: [MAPC requesting AP] An AP that initiates a MAPC negotiation with a MAPC responding AP for  one or more MAPC schemes.

Multi-AP coordination (MAPC) responding AP: [MAPC responding AP] An AP that responds to a MAPC requesting AP.

 

Best,

Giovanni

 

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

Hi all, 


Could we further discuss the relevant changes to the definitions about coordinating /coordinated AP? Two options are currently under consideration.

  • option 1: General-purpose (forward-compatible)
    • coordinating access point (AP): [coordinating AP] An AP that shares one or more of its resources (e.g. TXOP), or otherwise coordinates with coordinated APs within a TXOP it has obtained as part of a multi-AP coordination (MAPC) procedure.
    • coordinated access point (AP): [coordinated AP] An AP that is granted one or more resources (e.g. TXOP), or is otherwise being coordinated by a coordinating AP as part of a multi-AP coordination (MAPC) procedure

 

  • option 2: Precise and scoped for Co-SR, Co-BF, and Co-TDMA
    • coordinated access point (AP): [coordinated AP] An AP with which a coordinating AP shares a portion of its obtained TXOP by allocating time portions to it or permitting concurrent transmissions  as part of a multi-AP coordination (MAPC) procedure.
    • coordinating access point (AP): [coordinating AP] An AP that has obtained a transmission opportunity (TXOP) and intends to share its obtained TXOP with a set of coordinated APs by either allocating  time portions to them or permitting concurrent transmissions as part of a multi-AP coordination (MAPC) procedure.

 

It would be greatly appreciated if you could review and provide your feedback by the end of this week. I will then address and incorporate the received comments, and request a straw poll during the upcoming IEEE  MAC meeting.

 

 

Best Regards, 

Chun Huang

 

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