Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Ming, Thanks for your valuable comment. Now I see what you mean. Strictly speaking, you are right that in your example even if an AID of 2 or 3 is assigned to a non-AP MLD that has a multi-link setup on link1 and link2 only it can avoid duplicated indication. However, there are several things we need to consider. First, during the discussion of multi-link setup and reconfiguration we haven’t made a decision that a non-AP MLD may add another link without having reassociation and/or multi-link resetup. Therefore, it is safe to operate at this stage
that the AP MLD avoid allocating AIDs considering all links instead of current links that the non-AP MLD is associated with. This is the similar concept in baseline spec. that AID of “maximum possible number of BSSIDs” are not assigned to a STA rather than
just AID of “current number of BSSIDs” are not assigned. Second, in terms of AP MLD operation, a common MLD level operation will be implemented on all of affiliated APs while separate AP level operation will be implemented on each AP. Therefore, for an MLD level operation such as AID allocation,
instead of considering each different combination of links it is better and easy to have a common MLD level allocation. Considering these factors, we believe that having a MLD level unified rule of AID allocation is the simpler and the cleaner solution, and considering different non-AP MLD’s different association combinations would be an over-optimization
that increases the complexity without having meaningful gain. Thanks, Young Hoon From: Ganming (Ming) <ming.gan@xxxxxxxxxx> Hello Younghoon As I said in the call, the AID assignment for non-AP MLD does not need to consider the links with which it is not associated. Taking the following figure for example, if a non-AP MLD does multi-link
set up with AP 1a and AP 2b. In this case, the AID assigned to this non-AP MLD could conflict with the AID of a non-transmitted BSSID in link 3. That is to say, the AID 2 and AID 3 could also be assigned to this non AP MLD in this example. What do you think
about it? Best wishes, Ming Gan 发件人: Young Hoon Kwon [mailto:younghoon.kwon@xxxxxxx]
Hi Alfred, As my presentation on 20/0770r1 was the last topic of the last call and due to the limited time, I couldn’t run my SP. Can you add this SP on the agenda? Thanks, Young Hoon From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Caution: EXT Email
Hello all, I uploaded an updated version of the agendas, which contains the agenda for the next conference calls, scheduled on Monday, July 13 (MAC and PHY), 19:00-21:00 ET. The agendas can be found here: The dial in details can be found in the IEEE 802.11 calendar in their respective entries. The calendar can be access from this webpage PS 1: Guidelines for scheduled PHY conf calls:
·
Every time the agenda is sent the TG chair will ask if there are any submissions requests to be added to the PHY submissions queue. Requests can be regarding new submissions or regarding submissions with deferred SPs.
·
Requests may explicitly indicate if the requestor prefers to discuss his/her submission at a particular PHY conf call. If there is no such explicit indication then the submission will be added by default to the PHY submissions
queue and will be scheduled for presentation in a subsequent PHY conference call during which there are at least 3 submissions available for discussion.
·
A scheduled PHY conference call will be cancelled if the planned PHY agenda for that particular conference call does not have queued at least 3 presentations or at least one presentation with an explicit request. The cancellation
notice in this case will be sent at least 24 hours in advance. PS 2: Please send requests for any deferred SPs that need to be added to the agendas at least 24 hours prior to the start
of the conference call (same applies to submissions present in the agenda and that contains a SP). Deadline for uploading the initial version of a submission present in the agenda is 7 days prior to that conference call. Please let me know if you have any questions and/or suggestions.
Best Regards, Alfred -- Alfred Asterjadhi, PhD IEEE802.11 TGbe Chair, Qualcomm Technologies Inc. Cell #: +1 858 263 9445 Office #: +1 858 658 5302 To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 |