IEEE 802.11-23/1884r2 Seamless Roaming Solutions
Explore the technical agreements and general directions for seamless roaming in IEEE 802.11-23/1884r2 standard proposals. Discuss mechanisms enabling non-AP MLD roaming, data frame exchanges, and buffer delivery during roaming phases.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
January 2024 doc.: IEEE 802.11-23/1884r2 Seamless Roaming SPs Date: 2023-11 Authors: Name Affiliations Address Phone email Duncan Ho Qualcomm Technologies, Inc. 5665 Morehouse Dr., San Diego CA 92121 (858)845-3214 dho@qti.qualcomm.com George Cherian gcherian@qti.qualcomm.com Alfred Asterjadhi aasterja@qti.qualcomm.com Abhishek Patil appatil@qti.qualcomm.com Gaurang Naik gnaik@qti.qualcomm.com Giovanni Chisci gchisci@qti.qualcomm.com Sherief Helwa shelwa@qti.qualcomm.com Sanket Kalamkar sankal@qti.qualcomm.com Submission Slide 1 Duncan Ho (Qualcomm), et. al.,
January 2024 doc.: IEEE 802.11-23/1884r2 Introduction In this presentation, we present some common directions for 11bn seamless roaming design, which are mentioned in various proposals ([1] [7]) We present a few SPs seeking some technical agreements Submission Slide 2 Duncan Ho (Qualcomm), et. al.,
January 2024 doc.: IEEE 802.11-23/1884r2 General Directions Most proposals are trying to achieve the following: The non-AP MLD should be able to roam from one AP MLD to another non- colocated AP MLD with minimal data interruptions/loss Non-AP MLD remains associated No reauthen, reassoc, and no need to re-establish the BA sessions Allow the non-colocated AP MLDs that belong to the same ESS to be controlled by a higher layer logical entity (e.g., by a single mobility domain AP MLD) Allow some form of context transfer from the serving AP MLD to the target AP MLD Allow the non-AP MLD to retrieve buffered DL data frames from the serving AP MLD However, we should limit concurrent serving by non-colocated APs to only during the roaming phase Submission Slide 3 Duncan Ho, Qualcomm Incorporated
January 2024 doc.: IEEE 802.11-23/1884r2 SP1 Do you support to define a mechanism in 11bn that enables a non-AP MLD to roam from one AP MLD to another AP MLD while the non-AP MLD stays in state 4 during and after roaming? Submission Slide 4 Duncan Ho (Qualcomm), et. al.,
January 2024 doc.: IEEE 802.11-23/1884r2 SP2 Do you agree that in 11bn when a non-AP MLD that is in state 4 and is not in the process of roaming, the non- AP MLD is allowed to exchange class 3 frames only with one AP MLD? Submission Slide 5 Duncan Ho (Qualcomm), et. al.,
January 2024 doc.: IEEE 802.11-23/1884r2 SP3 Do you agree that during roaming, after the DS mapping change from the current AP MLD to the target AP MLD, the current AP MLD will be able to deliver buffered DL data frames to the non-AP MLD for a TBD period of time, during which the non-AP MLD may retrieve the buffered DL data frames. It is assumed that the target AP MLD is able to deliver data frames after the DS mapping change Submission Slide 6 Duncan Ho (Qualcomm), et. al.,
January 2024 doc.: IEEE 802.11-23/1884r2 SP4 Do you support that when a non-AP MLD roams from one AP MLD to another AP MLD, the context related to the non-AP MLD is transferred from one AP MLD to the other AP MLD such that it preserves the data exchange context for the non-AP MLD? Details of the context that can be transferred are TBD How to transfer the context is TBD. For example, the transfer of context can occur over the backhaul Submission Slide 7 Duncan Ho (Qualcomm), et. al.,
January 2024 doc.: IEEE 802.11-23/1884r2 SP5 Do you support the following for roaming: Define a request frame for a non-AP MLD in state 4 to initiate the roaming procedure The roaming procedure involves context transfer between the current AP MLD and the target AP MLD and data path change (DS mapping changed from the current AP MLD to target AP MLD) Define a response frame to the non-AP MLD to indicate the completion of the context transfer so the non-AP MLD may send class 3 frames to the target AP MLD NOTE The details of data path change is TBD Submission Slide 8 Duncan Ho (Qualcomm), et. al.,
January 2024 doc.: IEEE 802.11-23/1884r2 References [1] 11-22-1910-03-0uhr-seamless-roaming-for-uhr (Duncan Ho) [2] 11-23-0231-00-0uhr-thoughts-on-seamless-roaming-under-the- non-collocated-ap-mld-architecture (Guogang Huang) [3] 11-23-0279-00-0uhr-considerations-on-seamless-roaming (Insun Jang) [4] 11-23-0322-00-0uhr-improve-roaming-between-mlds (Po-kai Huang) [5] 11-23-0324-01-0uhr-roaming-requirements (Brian Hart) [6] 11-23-0632-01-0uhr-smooth-roaming-follow-up (Liwen Chu) [7] 11-23-1131-00-0uhr-thoughts-on-seamless-roaming (Ryuichi Hirata) Submission Slide 9 Duncan Ho, Qualcomm Incorporated
