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

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

Hi Jay, Binita, Abhi and all,

 

Thank you for the very good discussions.

Let me jump in to ask the following 2 questions for my clarification.

 

  1. According to Motion 279, an SMD-ME provides association for non-AP MLDs across all AP MLDs of the SMD. Is this the only association for the non-AP MLD during seamless roaming? Or are there any other associations, e.g. the association with the current AP MLD and/or the association with the target AP MLD in addition to the one with the SMD-ME?
  2. In legacy system, an association corresponds to a single respective AID. Are we going to change this principle for seamless roaming?

 

Best regards,

Kyosuke (SHARP CORPORATION)

 

From: Jay Yang <yang.zhijie@xxxxxxxxxx>
Sent: Wednesday, March 26, 2025 5:09 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] your contribution 24/656

 

 

Sorry, there is a typo in my previous mail.

 

 

the MLD level frame construction-->the  SMD level frame construction.

 

 

Thanks

 

Best Regards

 

Jay Yang (杨志杰)

 

 

Original

From: 杨志杰

Date: 2025年03月26日 15:48

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

Hi Abhi , Binita ,

 

In 11be, we define MLD level authentication, association, and AP MLD allocate the AID to the non-AP MLD .

In 11bn, do you agree the authentication, association, EAPOL frame exchange, ML reconfiguration are between non-AP MLD and SMD -ME in SMD ? (If I recalled correctly, we already have a motion to say SMD level association)?

If we follow the logic defined in 11be, there will be some interaction between SMD -ME and its affiliated AP MLD for AID allocation.

On the other hand, all SMD level frame exchange shall be received by  (one link affiliated with) one AP MLD ,  and then be forwarded to the SMD -ME,  it doesn't matter which links/AP MLD receive such SMD level frame. 

@Abhi , I don't propose the single AID pool in SMD -ME, each AP MLD still maintain their own AID pool, but there will be some interaction between SMD -ME and its affiliated AP MLD . Otherwise, how the MLD level frame construction? Who is the authenticator ?

@Binita , I don't talk anything about context transfer and maintain, each AP MLD can maintain their own context for the non-AP MLD , like each AP affiliated with AP MLD  maintain the partial BA scoreboard.

 

Sorry, I have too many question on the SMD -ME framework although we agree the general framework, but we don't have the fully discussion in ARC group. Not sure other members feeling on this.

 

I would like to hear the insight from other ARC expert, Mark, Mike, etc.

 

 

 

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

Date: 2025年03月26日 15:17

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

Hi Jay,

 

I couldn't follow the connection between Link Reconfiguration Request/Response and assignment of AID. The AID is assigned by an AP MLD not by the SMD . We cannot have a common pool of AID values at the SMD level. It will not be scalable .

 

Regards,

Abhi

 

From: Binita Gupta <bingupta.ieee@xxxxxxxxx>
Sent: Tuesday, March 25, 2025 9:08 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [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 Jay,

 

The non-AP MLD is performing roaming to a target AP MLD through the current AP MLD within the same SMD . LInk reconfig Request is received by the current AP MLD . There is over-the-DS exchange between the current AP MLD and target AP MLD for link setup, static and dynamic context transfer etc in a distributed SMD architecture. As part of this exchange, the target AP MLD provides AID that it assigns for the non-AP MLD . 

 

Thanks,

Binita

 

On Tue, Mar 25, 2025 at 7:35 PM Jay Yang <yang.zhijie@xxxxxxxxxx> wrote:

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>

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 MLD 1 and for AP MLD 2. 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 MLD 1 and AID=200 for AP MLD 2. The non-AP MLD will look for respective AIDs in frames from AP MLD 1 and AP MLD 2, so in the DL frames from AP MLD 1 it is looking for AID/STA_ID=100, and in DL frames from AP MLD 2 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

 

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