Re: [STDS-802-11-TGBN] your contribution 24/656

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

Hi Binita, Abhi,

Thanks for the clarification.

The problem is the ML reconfigucation request/response frame shall be SMD-ME level in SMD, not AP MLD level, that's, ML reconfiguration request/response frame will be exchanged between the SMD-ME and non-AP MLD, do you agree with that? If so, how the target AP MLD insert the assigned AID into the ML reconfiguration response frame?

Thanks

Best Regards

Jay Yang (杨志杰)

Original

From: BinitaGupta <bingupta.ieee@xxxxxxxxx>

To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>;

Date: 2025年03月25日 12:34

Subject: Re: [STDS-802-11-TGBN] your contribution 24/656

Thank you Jay for starting this thread on AID assignment during seamless roaming, and thanks Abhi for your response.

Jay,

My response is similar to Abhi's and this is what I explained in my answer during the TGbn MAC call. The AID assigned to a non-AP MLD is specific to an AP MLD. So, the non-AP MLD will have separate AIDs assigned for AP MLD1 and for AP MLD2. So, AID assignment is per AP MLD specific and not LINK specific.

In your example, the non-AP MLD will have AID=100 for AP MLD1 and AID=200 for AP MLD2. The non-AP MLD will look for respective AIDs in frames from AP MLD1 and AP MLD2, so in the DL frames from AP MLD1 it is looking for AID/STA_ID=100, and in DL frames from AP MLD2 it is looking for AID/STA_ID=200.

Thanks,

Binita

On Mon, Mar 24, 2025 at 8:15 PM Abhishek Patil <0000297b717f2a04-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:

Hi Jay,

Thank you for initiating this email thread.

A non-AP MLD will have a mapping of an assigned AID w.r.t to an AP MLD. Therefore, the ambiguity that you are referring to will not occur.

In your example, when non-AP MLD prepares AP MLD 2 and receives AID=200, it will have an internal mapping of:
AID=100 w.r.t AP MLD 1 [and AP MLD 1’s affiliated APs]
AID=200 w.r.t AP MLD 2 [and AP MLD 2’s affiliated APs]

Therefore, during the transitory phase if the non-AP MLD were to receive a DL MU PPDU from affiliated AP of AP MLD 1, it will look for STA_ID=100. Similarly, it will look for AID/STA_ID=200 for TF or DL MU from AP affiliated with AP MLD 2.

Regards,
Abhi

From: Jay Yang <yang.zhijie@xxxxxxxxxx>
Sent: Monday, March 24, 2025 6:31 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] your contribution 24/656

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

A lot of members show the interested in the AID assignment during the roaming procedure, let me initialize this mail thread.
Take the following figure as the example, non-AP MLD set up two links with the current AP MLD before roaming phase, and the current AP MLD assigns AID=100 to the non-AP MLD ,

During the roaming preparation/excuration phase, the Target AP MLD assigns a new AID(like AID=200) via the ML reconfiguration response frame you proposed.
The question is such new AID only applied on Link ID=1 but not Link ID=0 on non-AP MLD side, because link ID=0 is still used to received the DL traffic from the current AP MLD .
Once the AID on two links is updated to AID=200, the MU DL case (and TB UL case) don't work on the current AP MLD , as the current AP MLD has no ideas on the new AIDs unless we define some synchronize between the two AP MLDs .
That's why I said the AID assignment must be LINK level at this moment, that's, there is no AID update on the link associated with the current AP MLD.

Thanks

Best Regards

Jay Yang (杨志杰)

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