
Enhancing TDLS Direct Link in Roaming Scenarios
Explore considerations for TDLS direct link establishment and maintenance during roaming scenarios, proposing updates to address QoS/QoE issues in P2P communication. Follow the example of seamless roaming with non-AP MLDs and learn about the challenges and solutions for TDLS direct link in IEEE 802.11 networks.
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
April 2025 doc.: IEEE 802.11-25/0664r0 Considerations on TDLS Direct Link in Roaming Date: April 15, 2025 Authors: Name Affiliations Address Phone Email Pei Zhou Building G1, TCL International-E City, Shenzhen, Guangdong, China. zhoupei36@gmail.com TCL Xuwen Zhao Submission Slide 1 Pei Zhou, TCL
April 2025 doc.: IEEE 802.11-25/0664r0 Recap of TDLS Direct Link in REVme [1] 11.20 Tunneled direct link setup states the following: To set up and maintain a TDLS direct link, both TDLS peer STAs shall be associated with the same infrastructure BSS. 11.20.5 TDLS direct link teardown states the following: A TDLS Teardown frame with Reason Code LEAVING_NETWORK_DEAUTH shall be transmitted to all TDLS peer STAs (via the AP or via the direct path) prior to reassociation with a different AP, deauthentication, disassociation, or association. After receiving a Deauthentication frame or a Disassociation frame from the AP, a Deauthentication frame with Reason Code LEAVING_NETWORK_DEAUTH shall be transmitted via the direct path to all TDLS peer STAs that are in the awake state, if management frame protection has not been negotiated on the TDLS direct link. Submission Slide 2 Pei Zhou, TCL
April 2025 doc.: IEEE 802.11-25/0664r0 Recap of TDLS Direct Link in EHT [2] Figure AH-42 (Transmission of TDLS Setup Request frame from one non-AP MLD to another) and Figure AH-43 (Transmission of TDLS Setup Response frame from one non-AP MLD to another) illustrate the case where a single link TDLS direct link is set up between two non-AP MLDs that have performed ML setup with the same AP MLD. Submission Slide 3 Pei Zhou, TCL
April 2025 doc.: IEEE 802.11-25/0664r0 Motivation In baseline, TDLS direct link is established between two non-AP MLDs via the same AP MLD. In UHR, we are considering the handover/mobility of non-AP MLDs and defining seamless roaming procedure [3]. According to baseline TDLS procedure, if a non-AP MLD has established TDLS direct link with its peer non-AP MLDs via Current AP MLD roams to Target AP MLD, its TDLS direct link needs to be torn down. This will cause bad P2P communication QoS/QoE (especially, XR-like use cases), since TDLS direct link services are not continued while non-AP MLD performing seamless roaming. Therefore, this proposal provides some updates to the existing TDLS procedure to solve the issues above. Submission Slide 4 Pei Zhou, TCL
April 2025 doc.: IEEE 802.11-25/0664r0 Example of TDLS in Roaming Initially, non-AP MLD 1 and non-AP MLD 2 performed ML setup with the same AP MLD (i.e., AP MLD 1). Then, non-AP MLD 1 and non-AP MLD 2 performed TDLS direct link setup via AP MLD 1. AP MLD 1 AP MLD 2 Issue: When non-AP MLD 1 roams to AP MLD 2, its established TDLS direct link shall be torn down (according to baseline). Therefore, there will be no TDLS direct link between non-AP MLD 1 and non-AP MLD 2. Only when non-AP MLD 2 roaming to AP MLD 2 as well, then a new TDLS direct link can be set up again with non-AP MLD 1 via AP MLD 2. But, this will cause relatively long TDLS P2P communication delay Roaming TDLS Direct Link Non-AP MLD 1 Non-AP MLD 2 Submission Slide 5 Pei Zhou, TCL
April 2025 doc.: IEEE 802.11-25/0664r0 Proposals: TDLS Procedure Update In UHR, SMD concept has already motioned (e.g., Motion #279) for seamless roaming [3]: 11bn defines a Seamless Mobility Domain (SMD, exact name TBD) that covers multiple AP MLDs, where a non- AP MLD can use the UHR seamless roaming procedure to roam between the AP MLDs of the SMD A logical SMD Management Entity (SMD-ME, exact name TBD) provides association, IEEE 802.1X Authenticator (except for the management of 802.1X control ports which is TBD) and RSNA Key management for non-AP MLDs across all AP MLDs of the SMD. A non-AP MLD transitions between AP MLDs within the SMD while maintaining its association and security association with the SMD-ME. We may consider updates to the TDLS procedure for UHR in the following two aspects: Proposal 1: TDLS rules update To set up and maintain a TDLS direct link, both TDLS peer non-AP MLDs shall be associated with the AP MLDs within the same SMD. It means that, if a non-AP MLD s and its peer s AP MLDs are with the same SMD, their TDLS direct link can be maintained while roaming within the SMD. Proposal 2: TDLS direct link setup signaling update (see next slide) Submission Slide 6 Pei Zhou, TCL
April 2025 doc.: IEEE 802.11-25/0664r0 TDLS Setup Signaling Update MLD_S has performed ML setup with MLD_A; MLD_R has performed ML setup with MLD_B. Step 2: Step 1: Step 3: Add SMD_X identifier into TDLS Setup Request and Response signaling; Context Transfer can be reused to transfer TDLS related information; In TDLS Data frames transmission phase, A3 needs to be updated as well (e.g., add SMD_X identifier). Submission Slide 7 Pei Zhou, TCL
April 2025 doc.: IEEE 802.11-25/0664r0 Summary TDLS direct link will be torn down if one of the TDLS peer roams to another AP MLD To provide continuous TDLS P2P communication experience, TDLS procedure may be updated/enhanced according to SMD for UHR TDLS rules update TDLS direct link setup signaling update Open discussions and next steps Detailed signaling update and format design to the whole TDLS procedure TDLS direct link security procedure update Submission Slide 8 Pei Zhou, TCL
April 2025 doc.: IEEE 802.11-25/0664r0 Straw Poll Do you agree to add the following text to the TGbn SFD: TDLS procedure shall be updated to support TDLS direct link setup between non-AP MLDs that have set up links with different AP MLDs within the same SMD. Detailed TDLS procedure updates are TBD. Y/N/A Submission Slide 9 Pei Zhou, TCL
April 2025 doc.: IEEE 802.11-25/0664r0 References [1] Draft P802.11REVme_D7.0 [2] Draft P802.11be_D7.0 [3] 11-24-0209-11-00bn-specification-framework-for-tgbn Submission Slide 10 Pei Zhou, TCL