|Thread Links||Date Links|
|Thread Prev||Thread Next||Thread Index||Date Prev||Date Next||Date Index|
I initiate this thread to discussion 1931r4. I would like to explain the setting of these subfields in the ESS Report element by using two examples.
Since all APs affiliated with the same AP MLD have the same SSID and belong to the same ESS, the existing Planned ESS subfield and Edge Of ESS subfield cannot be used to assist the roaming for the non-AP MLD. Because the Planned ESS subfield shall be always set to 1 for the legacy STA if the AP MLD has more than one affiliated AP.
In the following, I will give two examples to explain the setting of these subfields. In scenario 1, since there is no neighboring AP or AP MLD, the Planned Of ESS For MLDs subfield is set to 0. But for a legacy STA, since it can initiate a BSS transition between AP 1 and AP 2, the Planned Of ESS subfield is set to 1.
Scenario 1: Single AP MLD
In scenario 2, since a non-AP MLD can initiate a BSS transition among AP MLD 1, AP MLD 2 and AP 3, the Planned Of ESS For MLDs subfield is set to 1.
Scenario 2 with non-co-located multiple APs or AP MLDs belonging to the same ESS
When there is at least one affiliated AP that sets the Edge Of ESS subfield to 1, then the Edge of ESS For MLDs shall be set to 1, which can be expressed as the following formula:
The value of Edge Of ESS For MLDs subfield = the value of the Edge Of ESS subfield of affiliated AP 1∨ the value of the Edge Of ESS subfield of affiliated AP 2∨…∨the value of the Edge Of ESS subfield of affiliated AP n
Please reply with your comments.
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