Communication method and related device

Abstract

The present application relates to the technical field of wireless communications, and provides a communication method and a related device. The communication method is applied to a first non-AP side and comprises: transmitting a connection establishment request to a first AP, wherein the connection establishment request is used for requesting to establish a TDLS direct link with a second non-AP, a first non-AP is associated with the first AP, and the second non-AP is associated with a second AP; and receiving a connection establishment request response transmitted by the first AP, wherein the connection establishment request response is used for indicating that establishment of the TDLS direct link is accepted.

Description

Communication method and related apparatus TECHNICAL FIELD

[0001] The present application relates to the technical field of wireless communication, and in particular to a communication method and related apparatus. BACKGROUND

[0002] In Institute of Electrical and Electronics Engineers (IEEE) 802.11z, a Tunneled Direct Link Setup (TDLS) mechanism is proposed, i.e. two Stations (STAs) in the same Base Station Subsystem (BSS) can establish a TDLS direct link, and the two STAs can leave the base channel of the current BSS and switch to another channel to communicate. The TDLS connection is a direct link established between two STAs connected to the same access point (AP), so that the two STAs can communicate directly without the need of forwarding through the AP, and the two STA devices can switch to another channel to communicate as needed.

[0003] However, according to the IEEE 802.11 standard protocol, the TDLS direct link established by STA1 and STA2 on the AP can only be valid when both of them are associated with the AP and have established a link. If either one or both of the STAs moves and roams to another AP (e.g. AP2), the TDLS direct link established by STA1 and STA2 on the AP1 needs to be torn down.

[0004] Therefore, after the STA that has established a TDLS-based Peer-to-Peer (P2P) link roams and switches to another AP, how to continue to maintain or quickly recover the TDLS P2P link with the Peer STA to perform TDLS-based P2P communication is a topic worth discussing. SUMMARY

[0005] Embodiments of the present application provide a communication method and related apparatus to ensure and improve the continuity of P2P communication.

[0006] To achieve the above-mentioned purpose, the present application adopts the following technical solutions:

[0007] The first aspect of this application provides a communication method applied to a first non-AP side, comprising: sending a connection establishment request to a first AP, the connection establishment request being used to request the establishment of a TDLS direct link with a second non-AP, wherein the first non-AP is associated with the first AP and the second non-AP is associated with the second AP; and receiving a connection establishment request response sent by the first AP, the connection establishment request response being used to indicate acceptance of the establishment of the TDLS direct link.

[0008] A second aspect of this application provides a communication method applied to a second non-AP side, comprising: receiving a connection establishment request sent by a second AP, the connection establishment request being used to request the establishment of a TDLS direct link with a first non-AP, the second non-AP being associated with the second AP, and the first non-AP being associated with the first AP; and sending a connection establishment request response to the second AP, the connection establishment request response being used to indicate whether to accept the establishment of the TDLS direct link.

[0009] A third aspect of this application provides a communication method applied to a first access point (AP), comprising: receiving a connection establishment request sent by a first non-AP and sending the connection establishment request to a second AP, wherein the connection establishment request is used to request the establishment of a TDLS direct link with the second non-AP, wherein the first non-AP is associated with the first AP and the second non-AP is associated with the second AP; receiving a connection establishment request response sent by the second AP and sending the connection establishment request response to the first non-AP.

[0010] A fourth aspect of this application provides a communication method applied to a second access point (AP), comprising: receiving a connection establishment request sent by a first AP, and sending the connection establishment request to a second non-AP, wherein the connection establishment request is used to request the first non-AP and the second non-AP to establish a TDLS direct link, wherein the first non-AP is associated with the first AP, and the second non-AP is associated with the second AP; receiving a connection establishment request response sent by the second non-AP, and sending the connection establishment request response to the first AP.

[0011] The fifth aspect of this application provides a communication method applied to a first non-AP side, comprising: sending roaming notification information to a second non-AP, the roaming notification information being used to notify the first non-AP to switch from roaming to the second AP, the first non-AP and the second non-AP being associated with the first AP and having established a TDLS direct link; and receiving roaming notification response information sent by the second non-AP.

[0012] The sixth aspect of this application provides a communication method applied to a second non-AP side, comprising: receiving roaming notification information sent by a first non-AP, the roaming notification information being used to notify the first non-AP to switch from roaming to the second AP, the first non-AP and the second non-AP being associated with the first AP MLD and having established a TDLS direct link; and sending roaming notification response information to the first non-AP.

[0013] A seventh aspect of this application provides a communication method applied to an access point (AP), comprising: receiving roaming request information sent by a first non-AP, the roaming request information being used by the first non-AP to request a switch from an associated first AP to a second AP, the roaming request information including peer STA information of the first non-AP and / or first TDLS direct link information established with the peer STA; and performing context transfer based on the roaming request information.

[0014] An eighth aspect of this application also provides a wireless communication device, including: a processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to perform the method as described in any of the preceding embodiments.

[0015] A ninth aspect of this application also provides a computer-readable storage medium, the computer-readable storage medium including instructions that, when executed, cause the method described in any of the preceding claims to be implemented. Attached Figure Description

[0016] Figure 1 shows a possible application scenario provided by this application;

[0017] Figure 2 is a flowchart of a possible communication method provided in an embodiment of this application;

[0018] Figure 2a is a flowchart of a possible communication method provided in an embodiment of this application;

[0019] Figure 3 is a flowchart of another possible communication method provided in an embodiment of this application;

[0020] Figure 3a is a flowchart of a possible communication method provided in an embodiment of this application;

[0021] Figure 4 is a flowchart of another possible communication method provided in an embodiment of this application;

[0022] Figure 4a is a flowchart of a possible communication method provided in an embodiment of this application;

[0023] Figure 5 is a schematic diagram of the storage of a possible wireless communication device provided in an embodiment of this application. Detailed Implementation

[0024] For ease of understanding, the relevant technologies involved in the embodiments of this application will be described below.

[0025] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0026] It should be understood that the term "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship. It should be noted that the naming of the parameters in this document is for ease of description; other names may be used in practice, and this application does not impose any restrictions on their specific use.

[0027] The messages described in this article include frames, instructions, commands, etc., and the names of device or functional entities, process names, frames, fields, etc. are not unique and are only used to assist in the description of functions, methods, behaviors, information, etc.

[0028] Currently, Wi-Fi 8 introduces the concept of a Single Mobility Domain (SMD) when discussing seamless roaming. This allows mobile non-AP multilink devices (MLDs) to roam seamlessly between different AP MLDs under the same SMD. An SMD can also be called a single mobility domain or something else; this application does not limit the specific terminology. An SMD is defined as multiple AP MLDs within the same Extended Service Set (ESS) forming a virtual SMD architecture. Under this SMD architecture, when a non-AP MLD is associated with one of the AP MLDs, seamless roaming between different AP MLDs under that SMD can be achieved. However, current Wi-Fi standards only support establishing TDLS direct links between STAs (or non-AP MLDs) associated with the same AP (MLD), and do not support establishing TDLS direct links between STAs (or non-AP MLDs) associated with different APs (MLDs).

[0029] For better understanding, please refer to Figure 1, which illustrates a possible application scenario in practice. In this figure, both non-AP MLD 1 and non-AP MLD 2 are associated with AP MLD 1 and / or establish multiple links. With the assistance of AP MLD 1, non-AP MLD 1 and non-AP MLD 2 establish a TDLS direct link based on the TDLS mechanism, enabling direct peer-to-peer (P2P) communication between them. In practical applications, non-AP MLD 1 could be a head-mounted virtual reality (VR) / augmented reality (AR) device, and non-AP MLD 2 could be a mobile device such as a smartphone or tablet. Data from the VR / AR device will then interact with the mobile device via the P2P link. However, when either or both of non-AP MLD 1 and non-AP MLD 2 move and need to roam to another AP MLD such as AP MLD_2, according to the existing standard protocol, the TDLS direct link established by non-AP MLD 1 and non-AP MLD 2 on AP MLD 1 is only valid if both are associated with AP MLD 1 and a link has been established. Therefore, when roaming occurs, the TDLS direct link established by non-AP MLD 1 and non-AP MLD 2 on AP MLD 1 needs to be terminated.

[0030] In other words, if a non-AP MLD has established a TDLS direct link and the user switches to another AP MLD (within the same SMD), according to current standards, it is impossible to maintain the original TDLS direct link after roaming. This would cause P2P communication to be interrupted, affecting the P2P communication experience. Therefore, how to enable non-AP MLDs that are connected to different AP MLDs within the same SMD to establish TDLS P2P links for more flexible and efficient P2P communication, supporting a wider range of P2P communication applications and scenarios, is a problem that deserves serious discussion.

[0031] In view of this, embodiments of this application provide a communication method for designing rules and a TDLS direct link establishment mechanism under a new architecture. It should be noted that the technical field applied in this application is wireless communication systems such as Wi-Fi based on IEEE 802.11bn (Wi-Fi 8) and later standards. The target scenario is how a STA that has established a TDLS-based P2P link (referred to as a TDLS P2P link or TDLS direct link) can maintain or quickly restore its TDLS P2P link with peer STAs after roaming to another AP, enabling TDLS-based P2P communication. Core technical directions include the establishment and dismantling of the TDLS P2P link, STA roaming operations, and the combination of both.

[0032] In addition, for the sake of better describing this scheme, for a STA that has established a TDLS P2P Link, the peer device of its P2P communication is referred to as a Peer STA in this application. The aforementioned STA can be referred to as a non-AP STA or a non-AP MLD, and the AP can be referred to as an AP MLD; roaming in this application is also called handover or roaming, that is, a non-AP MLD switching from one AP MLD to another AP MLD to work.

[0033] Please refer to Figure 2 for details. It is a flowchart illustrating a possible communication method provided in an embodiment of this application. This communication method can be applied to SMD architecture or other architectures. This embodiment of the application is described in the context of SMD architecture, and includes the following steps:

[0034] 201. The first non-AP sends a connection establishment request to the first AP;

[0035] To facilitate understanding, the device relationships in the embodiments of this application will first be described. The embodiments of this application can be applied to both multi-link device scenarios and single-link device scenarios. When applied to a single-link device scenario, the first non-AP is associated with the first AP, and the second non-AP is associated with the second AP. Under the SMD_X architecture, the first AP and the second AP can establish a trusted secure channel through a wireless or wired backhaul link, allowing them to exchange non-AP data and security information. When applied to a multi-link device scenario, the first AP is designated as the first AP MLD, and similarly, the first non-AP is designated as the first non-AP MLD, the second AP as the second AP MLD, and vice versa. Under the SMD_X architecture, the first non-AP MLD is associated with the first AP MLD, and the second non-AP MLD is associated with the second AP MLD. When the embodiments of this application are applied to a multi-link device scenario, the establishment of a TDLS direct link between the first affiliated STA in the first non-AP MLD and the second affiliated STA in the second non-AP MLD will be used as an example for explanation.

[0036] Specifically, the first non-AP sends a connection establishment request, also known as a TDLS Setup Request, to the first AP. In a single-link device scenario, this connection establishment request is used to request the establishment of a direct TDLS link with the second non-AP. This connection establishment request carries a first link identifier element, which is used by the first AP to forward the connection establishment request to the second AP. The first link identifier element includes, but is not limited to, any of the following parameter combinations:

[0037] Combination 1: The Media Access Control (MAC) address of the first non-AP, the MAC address of the second non-AP, and the MAC address of the first AP can be exemplarily represented as {LI(first non-AP, second non-AP, first AP)}, that is, the first AP identifies / finds the AP associated with the second non-AP (i.e., the second AP) through its SMD_X and forwards the connection establishment request to the second AP;

[0038] Combination Two: The MAC address of the first non-AP, the MAC address of the second non-AP, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI(the first non-AP, the second non-AP, SMD_X)}, that is, the first non-AP can recognize that the second non-AP is also within the SMD_X. Then, after the first AP receives a connection establishment request, it identifies / finds the AP (i.e., the second AP) associated with the second non-AP through the SMD_X where it is located, and forwards the connection establishment request to the second AP;

[0039] Combination Three: The MAC address of the first non-AP, the MAC address of the second non-AP, the MAC address of the first AP, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI(the first non-AP, the second non-AP, the first AP, SMD_X)}, that is, the first non-AP can recognize that both the first AP and the second non-AP are within the SMD_X. Then, after the first AP receives a connection establishment request, it identifies / finds the AP (i.e., the second AP) associated with the second non-AP through the SMD_X where it is located, and forwards the connection establishment request to the second AP.

[0040] In addition, in a multi-link device scenario, the connection establishment request is used to request the first attached STA in the first non-AP MLD to establish a TDLS direct connection link with the second attached STA in the second non-AP MLD. Among them, the connection establishment request carries a first link identifier element, and the first link identifier element Link identifier element is used for the first attached AP to forward the connection establishment request to the second AP. The first link identifier element includes, but is not limited to, any one of the following parameter combinations:

[0041] Combination One: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MAC address of the first attached AP can be exemplarily represented as {LI(the first non-AP MLD, the second non-AP MLD, the first attached AP)}, that is, the first attached AP identifies / finds the AP MLD (i.e., the second AP MLD) associated / established with the multi-link by the second non-AP MLD through the SMD_X where it is located, and forwards the connection establishment request to the second AP MLD;

[0042] Combination Two: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI(First non-AP MLD, Second non-AP MLD, SMD_X)}. That is, the first non-AP MLD can identify that the second non-AP MLD is also within the SMD_X. Then, after the first affiliated AP receives the connection establishment request, it identifies / finds the AP MLD (i.e., the second AP MLD) associated / established with the multi-link by the SMD_X where it is located, and forwards the connection establishment request to the second AP MLD.

[0043] Combination Three: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, the MAC address of the first affiliated AP, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI(First non-AP MLD, Second non-AP MLD, First affiliated AP, SMD_X)}. That is, the first non-AP MLD can identify that both the first AP MLD and the second non-AP MLD are within the SMD_X. Then, after the first AP MLD receives the connection establishment request, it identifies / finds the AP (i.e., the second AP) associated / established with the multi-link by the SMD_X where it is located, and forwards the connection establishment request to the second AP MLD.

[0044] In addition, the connection establishment request may also carry transceiver information, including but not limited to information such as the Receiver Address (RA), Transmitter Address (TA), and Destination Address (DA). That is, in this step, in the scenario of a single-link device, the TA is the first non-AP, the RA is the first AP, and the DA is the second non-AP; in the scenario of a multi-link device, the TA is the first affiliated STA, the RA is the first affiliated AP, and the DA is the second non-AP MLD.

[0045] It should be noted that in the embodiments of the present application, the connection establishment request can be carried in a Data Frame. That is, the first non-AP (MLD) sends the connection establishment request to the first AP (MLD) through the data frame. Optionally, the connection establishment request can also be carried in other information, such as a Control Frame, etc. The present application does not make specific limitations in this regard.

[0046] 202. The first AP sends a connection establishment request to the second AP;

[0047] After the first AP receives the connection establishment request sent by the first non-AP, it learns from the DA in the connection establishment request that the first non-AP requests to establish a TDLS direct link with the second non-AP. Therefore, it can forward the content, that is, the connection establishment request, to the second AP associated with the second non-AP through the link between the first AP and the second AP, and / or the backhaul link; correspondingly, in a multi-link device scenario, if the first attached AP learns that the first attached STA requests to establish a TDLS direct link with the second non-AP MLD, it can forward the connection establishment request to the second AP MLD associated with the second non-AP MLD through the link between the first AP MLD and the second AP MLD, and / or the backhaul link.

[0048] It should be noted that in this step, the frame carrying the connection establishment request can be a Data frame, a management frame, a control frame, etc., and the specific application does not make a limitation.

[0049] In addition, the connection establishment request in this step also carries a third link identification element. In a single-link device scenario, the third link identification element is used for the second AP to forward the connection establishment request to the second non-AP, and the third link identification element includes but is not limited to any one of the following parameter combinations:

[0050] Combination 1: The MAC address of the first non-AP, the MAC address of the second non-AP, and the MAC address of the second AP, which can be exemplarily represented as {LI(the first non-AP, the second non-AP, the second AP)}. That is, when the second AP sends the connection establishment request to the second non-AP again, the second non-AP believes that it establishes a TDLS direct link with the first non-AP through the second AP, and by default, the second AP belongs to SMD_X;

[0051] Combination 2: The MAC address of the first non-AP, the MAC address of the second non-AP, and the MLD MAC address of SMD_X, which can be exemplarily represented as {LI(the first non-AP, the second non-AP, SMD_X)}. That is, when the second AP sends the connection establishment request to the second non-AP again, the second non-AP believes that it establishes a TDLS direct link with the first non-AP through SMD_X;

[0052] Combination Three: The MAC address of the first non-AP, the MAC address of the second non-AP, the MAC address of the second AP, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI(First non-AP, Second non-AP, Second AP, SMD_X)}. That is, when the second AP sends a connection establishment request to the second non-AP, the second non-AP considers that a TDLS direct link is established with the first non-AP through the second AP under SMA_X.

[0053] In a multi-link device scenario, the third link identification element is used for the second attached AP to forward the connection establishment request to the second non-AP MLD. The third link identification element includes, but is not limited to, any one of the following parameter combinations:

[0054] Combination One: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MAC address of the second attached AP can be exemplarily represented as {LI(First non-AP MLD, Second non-AP MLD, Second attached AP)}. That is, when the second AP MLD sends a connection establishment request to the second non-AP MLD, the second non-AP MLD considers that a TDLS direct link is established with the first non-AP MLD through the second attached AP, and it is default that the second attached AP belongs to SMD_X;

[0055] Combination Two: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI(First non-AP MLD, Second non-AP MLD, SMD_X)}. That is, when the second AP MLD sends a connection establishment request to the second non-AP MLD, the second non-AP considers that a TDLS direct link is established with the first non-AP MLD through SMD_X;

[0056] Combination three: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, the MAC address of the second attached AP, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI (the first non-AP MLD, the second non-AP MLD, the second attached AP, SMD_X)}. That is, when the second AP MLD sends a connection establishment request to the second non-AP MLD, the second non-AP MLD believes that it establishes a TDLS direct link with the first non-AP through the second attached AP under SMA_X.

[0057] In addition, the connection establishment request in this step may also carry transceiver information, including but not limited to information such as RA, TA, and DA. That is, in this step, in the scenario of a single-link device, TA is the first AP, RA is the second AP, and DA is the second non-AP; in the scenario of a multi-link device, TA is the first attached AP, RA is the second attached AP, and DA is the second non-AP MLD.

[0058] 203. The second AP sends a connection establishment request to the second non-AP;

[0059] After receiving the connection establishment request sent by the first AP, the second AP forwards the connection establishment request to the second non-AP through the DA in the connection establishment request; correspondingly, in the scenario of a multi-link device, the second attached AP forwards the connection establishment request to the second attached STA affiliated with the second non-AP MLD.

[0060] It should be noted that in this step, the frame carrying the connection establishment request can be a Data frame, a management frame, a control frame, etc., and the specific application does not make a limitation.

[0061] In addition, the connection establishment request in this step also carries a fifth link identification element. In the scenario of a single-link device, the fifth link identification element is used for the second non-AP to send a connection establishment request response to the first non-AP. The fifth link identification element includes but not limited to any one of the following parameter combinations:

[0062] Combination one: The MAC address of the first non-AP, the MAC address of the second non-AP, and the MAC address of the second AP can be exemplarily represented as {LI (the first non-AP, the second non-AP, the second AP)}. In this case, the second non-AP believes that it establishes a TDLS direct link with the first non-AP through the second AP, and by default, the second AP belongs to SMD_X;

[0063] Combination Two: The MAC address of the first non-AP, the MAC address of the second non-AP, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI (first non-AP, second non-AP, SMD_X)}. In this case, the second non-AP considers that it establishes a TDLS direct link with the first non-AP through the SMD_X;

[0064] Combination Three: The MAC address of the first non-AP, the MAC address of the second non-AP, the MAC address of the second AP, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI (first non-AP, second non-AP, second AP, SMD_X)}. In this case, the second non-AP considers that it establishes a TDLS direct link with the first non-AP through the second AP under the SMD_X.

[0065] Correspondingly, in a multi-link device scenario, the fifth link identification element is used for the second affiliated STA to send a connection establishment request response to the first non-AP STA. The fifth link identification element includes, but is not limited to, any one of the following parameter combinations:

[0066] Combination One: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MAC address of the second affiliated AP can be exemplarily represented as {LI (first non-AP MLD, second non-AP MLD, second affiliated AP)}. In this case, the second non-AP considers that it establishes a TDLS direct link with the first non-AP MLD through the second affiliated AP, and it is default that the second affiliated AP belongs to the SMD_X;

[0067] Combination Two: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI (first non-AP MLD, second non-AP MLD, SMD_X)}. In this case, the second non-AP MLD considers that it establishes a TDLS direct link with the first non-AP MLD through the SMD_X;

[0068] Combination Three: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, the MAC address of the second attached AP, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI(First non-AP MLD, Second non-AP MLD, Second attached AP, SMD_X)}. In this case, the second non-AP MLD believes that a TDLS direct link is established with the first non-AP MLD through the second attached AP under the SMD_X.

[0069] In addition, the connection establishment request in this step may also carry transceiver information, including but not limited to information such as RA, TA, and source address (SA). That is, in this step, in the scenario of a single-link device, TA is the second AP, RA is the second non-AP, and SA is the first non-AP; in the scenario of a multi-link device, TA is the second attached AP, RA is the second attached AP, and SA is the first non-AP MLD.

[0070] 204. The second non-AP sends a connection establishment request response to the second AP;

[0071] After receiving the connection establishment request, the second non-AP processes the connection establishment request and sends a connection establishment request response, or TDLS Setup Response, to the associated second AP. This connection establishment request response is used to indicate whether to accept the request to establish a TDLS direct link with the first non-AP under the SMD X.

[0072] It should be noted that in this step, the frame carrying the connection establishment request can be a Data frame or other frames, etc., and the specific application does not make a limitation.

[0073] In addition, the connection establishment request in this step also carries a sixth link identification element. In the single-link device scenario, the sixth link identification element is used for the second AP to send a connection establishment request response to the first AP. The sixth link identification element includes any one of the following parameter combinations:

[0074] Combination 1: The MAC address of the first non-AP, the MAC address of the second non-AP, and the MAC address of the second AP can be exemplarily represented as {LI (the first non-AP, the second non-AP, the second AP)}. In this case, the second AP identifies / finds the AP (i.e., the first AP) associated with the first non-AP through the SMD_X where it is located, and forwards the Data frame containing the TDLS Setup Response to the first AP;

[0075] Combination 2: The MAC address of the first non-AP, the MAC address of the second non-AP, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI (the first non-AP, the second non-AP, SMD_X)}. The second non-AP can identify that the first non-AP is also within the SMD_X. Then, after the second AP receives the TDLS Setup Response, it identifies / finds the AP (i.e., the first AP) associated with the first non-AP through the SMD_X where it is located, and forwards the TDLS Setup Response to the first AP;

[0076] Combination 3: The MAC address of the first non-AP, the MAC address of the second non-AP, the MAC address of the second AP, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI (the first non-AP, the second non-AP, the second AP, SMD_X)}. In this case, the second non-AP can identify that both the second AP and the first AP are within the SMD_X. Then, after the second AP receives the TDLS Setup Response, it identifies / finds the first AP associated with the first non-AP through the SMD_X where it is located, and forwards the TDLS Setup Response to the first AP.

[0077] Correspondingly, in a multi-link device scenario, the sixth link identification element is used for the second attached AP to send a connection establishment request response to the first attached AP. The sixth link identification element includes, but is not limited to, any one of the following parameter combinations:

[0078] Combination 1: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MAC address of the second attached AP can be exemplarily represented as {LI(First non-AP, Second non-AP, Second attached AP)}. In this case, the second attached AP identifies / finds the AP MLD (i.e., the first AP MLD) associated / established with the multi-link by the first non-AP MLD through the SMD_X where it is located, and forwards the Data frame containing the TDLS Setup Response to the first AP MLD;

[0079] Combination 2: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI(First non-AP MLD, Second non-AP MLD, SMD_X)}. The second non-AP MLD can identify that the first non-AP MLD is also within the SMD_X. Then, after the second attached AP receives the TDLS Setup Response, it identifies / finds the AP MLD (i.e., the first AP MLD) associated / established with the multi-link by the first non-AP through the SMD_X where it is located, and forwards the TDLS Setup Response to the first AP MLD;

[0080] Combination 3: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, the MAC address of the second attached AP, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI(First non-AP MLD, Second non-AP MLD, Second attached AP, SMD_X)}. In this case, the second non-AP MLD can identify that both the second attached AP (attached to the second AP MLD) and the first AP MLD are within the SMD_X. Then, after the second attached AP receives the TDLS Setup Response, it identifies / finds the first AP MLD associated with the first non-AP MLD through the SMD_X where it is located, and forwards the TDLS Setup Response to the first AP MLD.

[0081] In addition, the connection establishment request response in this step may also carry transceiver information, including but not limited to information such as RA, TA, and DA. That is, in this step, in the scenario of a single-link device, TA is the second non-AP, RA is the second AP, and DA is the first non-AP; in the scenario of a multi-link device, TA is the second attached STA, RA is the second attached AP, and DA is the first non-AP MLD.

[0082] 205. The second AP sends a connection establishment request response to the first AP;

[0083] After receiving the connection establishment request response sent by the second non-AP, the second AP learns whether the second non-AP accepts to establish a TDLS direct link with the first non-AP through the DA in the connection establishment request response. Therefore, the second AP forwards the content, that is, the connection establishment request response, to the first AP associated with the first non-AP through the link between the first AP and the second AP, and / or the backhaul link; correspondingly, in the scenario of a multi-link device, the second attached AP learns whether the second attached STA accepts to establish a TDLS direct link with the first non-AP MLD, and therefore forwards the connection establishment request to the first AP MLD associated with the first non-AP MLD through the link between the first AP MLD and the second AP MLD, and / or the backhaul link.

[0084] It should be noted that in this step, the frame carrying the connection establishment request response can be a Data frame, a management frame, a control frame, etc., and the specific application does not make a limitation.

[0085] In addition, the connection establishment request in this step also carries a fourth link identification element. In the scenario of a single-link device, the fourth link identification element is used for the first AP to forward the connection establishment request to the first non-AP. The fourth link identification element includes but is not limited to any one of the following parameter combinations:

[0086] Combination 1: The MAC address of the first non-AP, the MAC address of the second non-AP, and the MAC address of the first AP, which can be exemplarily represented as {LI (first non-AP, second non-AP, first AP)}. In this case, when the first AP sends the TDLS Setup Response to the first non-AP, the first non-AP considers that a TDLS direct link is established with the second non-AP through the first AP. And it is default that the first AP belongs to SMD_X;

[0087] Combination Two: The MAC address of the first non-AP, the MAC address of the second non-AP, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI(First non-AP, Second non-AP, SMD_X)}. In this case, when the first AP sends the TDLS Setup Response to the first non-AP, the first non-AP considers that a TDLS direct link is established with the second non-AP through the SMD_X;

[0088] Combination Three: The MAC address of the first non-AP, the MAC address of the second non-AP, the MAC address of the first AP, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI(First non-AP, Second non-AP, First AP, SMD_X)}. In this case, when the first AP sends the TDLS Setup Response to the first non-AP, the first non-AP considers that a TDLS direct link is established with the first non-AP through the first AP under the SMD_X.

[0089] In a multi-link device scenario, the fourth link identification element is used for the first attached AP to forward the connection establishment request response to the first non-AP MLD. The fourth link identification element includes, but is not limited to, any one of the following parameter combinations:

[0090] Combination One: The MAC address of the first non-AP MLD, the MAC address of the second non-AP MLD, and the MAC address of the first attached AP can be exemplarily represented as {LI(First non-AP MLD, Second non-AP MLD, First attached AP)}. In this case, when the first attached AP sends the TDLS Setup Response to the first non-AP MLD, the first non-AP MLD considers that a TDLS direct link is established with the second non-AP MLD through the first attached AP. And by default, the first attached AP belongs to the SMD_X.;

[0091] Combination Two: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI(First non-AP MLD, Second non-AP MLD, SMD_X)}. In this case, when the first affiliated AP sends the TDLS Setup Response to the first non-AP MLD, the first non-AP MLD believes that a TDLS direct link is established with the second non-AP MLD through the SMD_X;

[0092] Combination Three: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, the MAC address of the first affiliated AP, and the MLD MAC address of the SMD_X can be exemplarily represented as {LI(First non-AP, Second non-AP, First affiliated AP, SMD_X)}. In this case, when the first affiliated AP sends the TDLS Setup Response to the first non-AP MLD, the first non-AP MLD believes that a TDLS direct link is established with the first non-AP MLD through the first affiliated AP under the SMD_X.

[0093] In addition, the connection establishment request response in this step may also carry transceiver information, including but not limited to information such as RA, TA, and DA. That is, in this step, in the scenario of a single-link device, TA is the second AP, RA is the first AP, and DA is the first non-AP; in the scenario of a multi-link device, TA is the second affiliated AP, RA is the first affiliated AP, and DA is the first non-AP MLD.

[0094] 206. The first AP sends a connection establishment request response to the first non-AP;

[0095] The first AP sends the TDLS Setup Response signaling forwarded by the second AP to the first non-AP, or in the multi-link device scenario, the first affiliated AP sends the TDLS Setup Response signaling forwarded by the second affiliated AP to the first affiliated STA.

[0096] In the embodiments of the present application, the connection establishment request response can be carried in a data frame Data Frame, that is, the first AP (MLD) sends the connection establishment request response to the first non-AP (MLD) through the data frame. Optionally, the connection establishment request can also be carried in other information, such as a control frame Control Frame or a management frame, etc. The present application does not make specific limitations.

[0097] In addition, the connection establishment request response in this step also carries a second link identification element. In a single-link device scenario, the second link identification element is used for the first non-AP to establish a TDLS Direct Link with the second non-AP. The second link identification element includes, but is not limited to, any one of the following parameter combinations:

[0098] Combination 1: The MAC address of the first non-AP, the MAC address of the second non-AP, and the MAC address of the first AP, which can be exemplarily represented as {LI(first non-AP, second non-AP, first AP)}. In this case, the first non-AP believes that it establishes a TDLS direct link with the second non-AP through the first AP. And by default, the first AP belongs to SMD_X;

[0099] Combination 2: The MAC address of the first non-AP, the MAC address of the second non-AP, and the MLD MAC address of SMD_X, which can be exemplarily represented as {LI(first non-AP, second non-AP, SMD_X)}. In this case, the first non-AP believes that it establishes a TDLS direct link with the second non-AP through SMD_X;

[0100] Combination 3: The MAC address of the first non-AP, the MAC address of the second non-AP, the MAC address of the first AP, and the MLD MAC address of SMD_X, which can be exemplarily represented as {LI(first non-AP, second non-AP, first AP, SMD_X)}. In this case, the first non-AP believes that it establishes a TDLS direct link with the second non-AP through the first AP under SMD_X.

[0101] Correspondingly, in a multi-link device scenario, the second link identification element is used for the first non-AP MLD to establish a TDLS Direct Link with the second non-AP MLD. The second link identification element includes, but is not limited to, any one of the following parameter combinations:

[0102] Combination 1: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MAC address of the first attached AP can be exemplarily represented as {LI (the first non-AP MLD, the second non-AP MLD, the first attached AP)}. In this case, the first non-AP MLD believes that it establishes a TDLS direct link with the second non-AP MLD through the first attached AP. And by default, the first attached AP belongs to SMD_X;

[0103] Combination 2: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MLD MAC address of SMD_X can be exemplarily represented as {LI (the first non-AP MLD, the second non-AP MLD, SMD_X)}. In this case, the first non-AP MLD believes that it establishes a TDLS direct link with the second non-AP MLD through SMD_X;

[0104] Combination 3: The MAC address of the first non-AP, the MAC address of the second non-AP, the MAC address of the first attached AP, and the MLD MAC address of SMD_X can be exemplarily represented as {LI (the first non-AP, the second non-AP, the first attached AP, SMD_X)}. In this case, the first non-AP believes that it establishes a TDLS direct link with the second non-AP through the first AP under SMD_X.

[0105] In addition, the connection establishment request response may also carry transceiver information, including but not limited to information such as RA, TA, and SA. That is, in this step, in the scenario of a single-link device, TA is the first AP, RA is the first non-AP, and SA is the second non-AP; in the scenario of a multi-link device, TA is the first attached AP, RA is the first attached STA, and SA is the second non-AP MLD.

[0106] It should be noted that when the connection establishment request response is used to indicate that the second non-AP accepts the request to establish a TDLS direct link, a TDLS direct link is successfully established between the first non-AP and the second non-AP, or in the scenario of a multi-link device, a TDLS direct link is successfully established between the first attached STA and the second attached STA, and P2P communication can be carried out; otherwise, the TDLS direct link is not established and P2P communication cannot be carried out.

[0107] 207. The first non-AP sends a first data frame to the second non-AP;

[0108] When a TDLS direct connection link is successfully established between the first non-AP and the second non-AP, the two can perform P2P communication, including the interaction of data frames. For example, the first non-AP sends a first data frame to the second non-AP, and the second non-AP then sends a first data response frame to the first non-AP; or, the first non-AP sends a first data frame to the second non-AP; or, the second non-AP sends a second data frame to the first non-AP; or, the second non-AP sends a second data frame to the first non-AP, and the first non-AP then sends a second data response frame to the second non-AP, etc. In the embodiments of the present application, taking the first non-AP sending a first data frame to the second non-AP and the second non-AP making a response as an example for illustration, other situations are similar, and the present application will not elaborate further.

[0109] Specifically, both the first data frame and the first data response frame carry corresponding address indication information. In a multi-link device scenario, the corresponding address indication information includes at least one of the following parameters: the recipient address, the sender address, the BSSID of the BSS where the first non-AP MLD and the second non-AP MLD are located, and a combination of the BSSID and a specific ID. Among them, the BSSID includes at least one of the following addresses: the MAC address of the first affiliated AP, the MAC address of the second affiliated AP, the MLD MAC address of the SMD, and / or a custom address, and the custom address includes a new address formed by combining some address bits of the MAC address of the first affiliated AP, the MAC address of the second affiliated AP, and / or the MLD MAC address of the SMD. It should be noted that when the BSSID includes a custom address, the custom address is indicated in the connection establishment request and / or the connection establishment request response.

[0110] For ease of understanding, in the first data frame, the address indication information may include the following two sets of parameters:

[0111] 1) The receiver address, the sender address, and the BSSID. The receiver address RA is the MLD MAC address of the second non-AP MLD, the sender address TA is the MLD MAC address of the first non-AP MLD. The BSSID can be set to the MAC address of the affiliated AP of the first AP MLD (for example, the first affiliated AP in the example), or the MAC address of the affiliated AP of the second AP MLD (for example, the second affiliated AP in the example), or the MLD MAC address and / or the custom address of SMD_X. Which address to be specifically set is determined by the indication in the TDLS Setup Request and the TDLS Setup Response, that is, it should be consistent with the indication in the TDLS Setup Request and / or the TDLS Setup Response. In the embodiments of this application, the custom address can also be a new address formed by a combination of some address bits of the MAC address of the first affiliated AP and / or the MAC address of the second affiliated AP and / or the MLD MAC address of SMD_X. It should be noted that this new address should have been indicated in the TDLS Setup Request and the TDLS Setup Response;

[0112] 2) The receiver address, the sender address, and the combination of the BSSID and the specific ID. The receiver address RA is the MLD MAC address of the second non-AP MLD, the sender address TA is the MLD MAC address of the first non-AP MLD. The settings of the combination of the BSSID and the specific ID are as follows:

[0113] The BSSID is set to the BSSID of the BSS where the second non-AP MLD is located, that is, the MAC address of the affiliated AP of the second AP MLD (for example, the second affiliated AP); the specific ID is set to the BSSID of the BSS where the first non-AP MLD is located, that is, the MAC address of the affiliated AP of the first AP MLD (for example, the first affiliated AP in the example);

[0114] a) The BSSID is set to the BSSID of the BSS where the first non-AP MLD is located, that is, the MAC address of the affiliated AP of the first AP MLD (for example, the first affiliated AP in the example); the specific ID is set to the BSSID of the BSS where the second non-AP MLD is located, that is, the MAC address of the affiliated AP of the second AP MLD (for example, the second affiliated AP in the example);

[0115] b) The BSSID is set to the BSSID of the BSS where the second non-AP MLD is located, that is, the MAC address of the affiliated AP of the second AP MLD (for example, the second affiliated AP in the example); the specific ID is set to the MLD MAC address of SMD_X;

[0116] c) The BSSID is set to the BSSID of the BSS where the first non-AP MLD is located, that is, the MAC address of the affiliated AP of the first AP MLD (for example, the first affiliated AP in the example); the specific ID is set to the MLD MAC address of SMD_X;

[0117] d) The BSSID is set to the MLD MAC address of SMD_X; the specific ID is set to the BSSID of the BSS where the second non-AP MLD is located, that is, the MAC address of the affiliated AP of the second AP MLD (for example, the second affiliated AP in the example);

[0118] e) The BSSID is set to the MLD MAC address of SMD_X; A4 is set to the BSSID of the BSS where the first non-AP MLD is located, that is, the MAC address of the affiliated AP of the first AP MLD (for example, the first affiliated AP in the example);

[0119] f) Or other combinations that include the MAC address of the first affiliated AP, the MAC address of the second affiliated AP, and the MLD MAC address of SMD_X. Specifically, this application does not make a limitation.

[0120] In the single-link device scenario, the address indication information carried in the first data frame is similar to that in the multi-link device scenario, and this application will not elaborate further.

[0121] 208. The second non-AP sends a first data response frame to the first non-AP.

[0122] Similar to the above first data frame, in the multi-link device scenario, the address indication information carried in the first data response frame may include the following two sets of parameters:

[0123] 1) The receiver address, the sender address, and the BSSID, where the receiver address RA is the MLD MAC address of the first non-AP MLD, the sender address TA is the MLD MAC address of the second non-AP MLD, and the BSSID can be set to the MAC address of the affiliated AP of MLD_A (e.g., AP 1 in the example), or the MAC address of the affiliated AP of MLD_B (e.g., AP 3 in the example), or the MLD MAC address and / or custom address of SMD_X. Which address is specifically set is determined by the indication in the TDLS Setup Request and TDLS Setup Response, that is, it should be consistent with the indication in the TDLS Setup Request and / or TDLS Setup Response. In the embodiments of this application, the custom address can also be a new address formed by a combination of some address bits of the MAC address of the first affiliated AP and / or the MAC address of the second affiliated AP and / or the MLD MAC address of SMD_X. It should be noted that this new address should have been indicated in the TDLS Setup Request and TDLS Setup Response;

[0124] 3) The receiver address, the sender address, and the combination of the BSSID and a specific ID, where the receiver address RA is the MLD MAC address of the first non-AP MLD, the sender address TA is the MLD MAC address of the second non-AP MLD. In addition, the setting of the combination of the BSSID and the specific ID is similar to the setting of the combination of the BSSID and the specific ID mentioned in step 207, and will not be elaborated here specifically. It should be noted that the setting of the combination of the BSSID and the specific ID in step 207 should be consistent with the setting of the combination of the BSSID and the specific ID in step 208.

[0125] Similarly, in the single-link device scenario, the address indication information carried in the first data response frame is similar to that in the multi-link device scenario, and will not be elaborated in this application specifically.

[0126] In summary, this embodiment of the application redesigns the rules and mechanisms for establishing TDLS direct links within the SMD framework, enabling the establishment of TDLS direct links between non-AP MLDs located within the same SMD but associated with different AP MLDs, thus achieving broader and more flexible P2P transmission. Furthermore, it offers the additional technical benefit that when a non-AP MLD with an established TDLS direct link roams within the SMD and switches to another AP MLD, the established TDLS direct link remains unaffected; it does not require dismantling and rebuilding, ensuring the continuity of P2P communication.

[0127] To facilitate a more detailed understanding of the embodiments shown in Figure 2, please refer to Figure 2a, which is a flowchart of another communication method provided by an embodiment of this application. The figure provides a detailed example of the establishment of the TDLS direct link and the interaction process between devices in a cross-AP MLD scenario. Specifically, it includes: MLD_S can correspond to the first non-AP MLD in Figure 2, STA1 and STA2 are both affiliated STAs of MLD_S; MLD_A can correspond to the first AP MLD in Figure 2, AP1 and AP2 are both affiliated APs of MLD_A, where MLD_S is a non-AP MLD associated with MLD_A; MLD_R can correspond to the second non-AP MLD in Figure 2, STA3 and STA4 are both affiliated STAs of MLD_R; MLD_B can correspond to the second AP MLD in Figure 2, AP3 and AP4 are both affiliated APs of MLD_B, where MLD_R is a non-AP associated with MLD_B. MLD; additionally, MLD_A and MLD_B belong to the same SMD (labeled SMD_X) (this condition is not a mandatory prerequisite), meaning that they can establish a trusted secure channel through a wireless or wired backhaul link, and can exchange non-AP MLD data and security information. Figure 2a illustrates the establishment of a TDLS direct link between affiliated STA 1 of MLD_S and affiliated STA 3 of MLD_R as an example. Other examples are similar and will not be elaborated upon in this application. The systematic (signaling) flow shown in Figure 2a includes the following parts:

[0128] Part 1: Forwarding of TDLS Setup Requests.

[0129] Step 1: The affiliated STA 1 of MLD_S sends a data frame to the affiliated AP 1 of MLD_A, containing a TDLS Setup Request signaling request to establish a TDLS direct link under SMD X with MLD_R (via the affiliated AP 1 of MLD_A). The TDLS Setup Request signaling carries the following parameters: {A1(RA) = AP1, A2(TA) = STA1, A3(DA) = MLD_R} and a link identifier element {LI(MLD_S, MLD_R, AP1, SMD_X)}. Here, A1(RA) represents Address 1 (Receiver Address). For example, A1(RA) = AP 1 means that Address 1 (Receiver Address) is set to the MAC address of AP 1 (affiliated with MLD_A). Similarly, A2(TA) represents Address 2 (Transmitter Address). For example, A2(TA) = STA 1 means that Address 2 (Sender Address) is set to the MAC address of AP 1 (affiliated with MLD_S). The MAC address of 1; A3(DA) represents Address 3 (Destination Address). For example, A3(DA) = MLD_R means that Address 3 (Destination Address) is set as the MLD MAC address of MLD_R; The Link identifier element is set to {LI(MLD_S, MLD_R, AP1, SMD_X)}, which means that MLD_S can recognize that AP 1 (attached to MLD_A) and MLD_R are both in SMD_X. Then, after AP 1 receives a Data frame containing a TDLS Setup Request, it identifies / finds the AP MLD (i.e., MLD_B) associated with / establishes a multi-link with MLD_R through the SMD_X where it is located, and forwards the Data frame containing the TDLS Setup Request to MLD_B;

[0130] Step 2: The associated AP 1 of MLD_A transfers the context (i.e., the TDLS Setup Request signaling) to the associated AP MLD (i.e., MLD_B) of MLD_R via a Data frame. In the example in the diagram, the receiver is the associated AP 3 of MLD_B. The forwarded TDLS Setup Request signaling carries the following parameters: {A1(RA) = AP3, A2(TA) = AP1, A3(DA) = MLD_R} and {LI(MLD_S, MLD_R, AP3 or MLD_B, SMD_X)}. This Link identifier element indicates that when MLD_B sends the Data frame containing the TDLS Setup Request to MLD_R, MLD_R considers that a TDLS direct link is established between MLD_S and AP 3 under SMD_X.

[0131] Step 3: MLD_B (affiliated AP 3) sends the TDLS Setup Request signaling transferred by MLD_A's affiliated AP 1 to MLD_R via a data frame. In the example diagram, the receiver is MLD_R's affiliated STA 3. In this step, the TDLS Setup Request signaling carries the following parameters: {A1(RA) = STA3, A2(TA) = AP3, A3(SA) = MLD_S} and {LI(MLD_S, MLD_R, AP3, SMD_X)}. Here, A3(SA) represents Address 3 (Source Address). For example, A3(SA) = MLD_S means that Address 3 (Source Address) is set to the MLD MAC address of MLD_S. Additionally, the Link identifier element in this step indicates that MLD_R believes a TDLS direct link is established with MLD_S through AP 3 under SMD_X.

[0132] Part 2: Forwarding of TDLS Setup Response.

[0133] Step 4: MLD_R processes the request to establish a TDLS direct link with MLD_S (e.g., via the attached STA 3) and sends a Data frame to the attached AP 3 of its associated MLD_B, containing a TDLS Setup Response signal (whether to accept the request to establish a TDLS direct link with MLD_S under SMD_X). This TDLS Setup Response signal carries the following parameters: {A1(RA) = AP3, A2(TA) = STA3, A3(DA) = MLD_S} and {LI(MLD_S, MLD_R, AP3, SMD_X)}. The Link identifier element in this step indicates that MLD_R can recognize that both AP 3 (attached to MLD_B) and MLD_S are within SMD_X. After receiving the Data frame containing the TDLS Setup Response, AP 3 identifies / finds the AP MLD (i.e., MLD_A) associated with / establishing a multi-link with MLD_S through its SMD_X, and sends the Data frame containing the TDLS Setup Response to the AP MLD_S. The frame is forwarded to MLD_A.

[0134] Step 5: The associated AP 3 of MLD_B transfers the context (i.e., TDLS Setup Response signaling) to the associated AP MLD (i.e., MLD_A) of MLD_S via a Data frame, for example, the receiver is the associated AP 1 of MLD_A; the TDLS Setup Response signaling in this step carries the following parameters {A1(RA) = AP1, A2(TA) = AP3, A3(DA) = MLD_S} and {LI(MLD_S, MLD_R, AP1 or MLD_B, SMD_X)}. The Link identifier element in this step indicates that when MLD_A sends the Data frame containing the TDLS Setup Response to MLD_S, MLD_S considers that a TDLS direct link is established between AP 1 under SMD_X and MLD_R.

[0135] Step 6: MLD_A (affiliated AP 1) sends the TDLS Setup Response signaling transferred by MLD_B's affiliated AP 3 to MLD_S via a data frame, for example, the receiver is MLD_S's affiliated STA 1. The TDLS Setup Response signaling in this step carries the following parameters: {A1(RA) = STA1, A2(TA) = AP1, A3(SA) = MLD_R} and {LI(MLD_S, MLD_R, AP1 or MLD_B, SMD_X)}. The Link identifier element in this step indicates that MLD_S believes a TDLS direct link is established between MLD_S and MLD_R via AP 1 under SMD_X. It should be noted that if the TDLS Setup Response signaling indicates acceptance and establishment of a TDLS direct link, a successful TDLS direct link is established between MLD_S (affiliated STA 1) and MLD_R (affiliated STA 3), allowing P2P communication; otherwise, no TDLS direct link is established, and P2P communication is not possible.

[0136] Part 3: P2P communication based on TDLS direct link.

[0137] Step 7: MLD_R (affiliated STA 3) sends a (P2P) data frame to MLD_S (affiliated STA 1), indicating the (MLD) MAC addresses of AP 1 and / or AP 3 and / or SMD_X. The data frame carries the following parameters: {A1(RA) = MLD_S, A2(TA) = MLD_R, A3(BSSID) = (AP1, AP3, SMD_X)}, where A3(BSSID) is the BSSID of the BSS where MLD_S and MLD_R are located. In this step, it is set to a combination of the MAC address of AP1, the MAC address of AP3, and the MLD MAC address of SMD_X.

[0138] Step 8: MLD_S (affiliated STA 1) sends a (P2P) data frame to MLD_R (affiliated STA 3), indicating the (MLD) MAC address of AP 1 and / or AP 3 and / or SMD_X. The data frame carries the following parameters: {A1(RA) = MLD_R, A2(TA) = MLD_S, A3(BSSID) = (AP1, AP3, SMD_X)}, where A3(BSSID) is the BSSID of the BSS where MLD_S and MLD_R are located. The BSSID set in step 8 is the same as the BSSID set in step 7.

[0139] In addition to redesigning the rules and mechanisms for establishing TDLS direct links, this application also notes that during the roaming process from a non-AP MLD to a Serving AP MLD, only the establishment / disconnection of links between the non-AP MLD and both the Serving AP MLD and the Target AP MLD is emphasized, without addressing how the non-AP MLD's TDLS direct link should be established / updated. However, through a series of analyses, it can be seen that in roaming scenarios, the non-AP MLD needs to disconnect all established TDLS direct links and then re-establish a new TDLS direct link with the non-AP MLD associated with the Target AP MLD on the Target AP MLD. Furthermore, if a peer non-AP MLD that has established a TDLS direct link on the Serving AP MLD does not roam to the Target AP MLD, then that non-AP MLD cannot restore its TDLS direct link with the original peer non-AP MLD, resulting in the inability to use the TDLS P2P link for P2P communication. This results in a poor user experience for scenarios where non-AP MLD 1 is a head-mounted VR / AR device and non-AP MLD 2 is a mobile device such as a mobile phone / tablet that establishes P2P communication.

[0140] Therefore, it is essential to design and establish a new technical solution for the rapid recovery / establishment of P2P link in a non-AP MLD based on TDLS P2P link after roaming and switching AP MLD, thereby improving the user experience of P2P communication on mobile devices. In view of this, this application also provides several communication methods for 1) rapid recovery of P2P link or 2) re-establishment of P2P link after roaming. Please refer to Figures 3 and 4 for details, which will describe the two schemes separately.

[0141] Please refer to Figure 3, which is a flowchart of a possible communication method provided in an embodiment of this application, including the following steps:

[0142] 301. The first non-AP sends a roaming notification message to the second non-AP;

[0143] Similar to the embodiment described in Figure 2, this embodiment can also be applied to multi-link device scenarios and single-link device scenarios. When applied to a single-link device scenario, both the first non-AP and the second non-AP are associated with the first AP. The first non-AP roams from the first AP to the second AP, that is, the first AP and the second AP are the Serving AP and the Target AP, respectively, and they can belong to the same SMD (labeled as SMD X) or other architectures. There is a wireless backhaul link or a wired backhaul link between the first AP and the second AP, which can exchange non-AP data and security information. When applied to a multi-link scenario, the first AP is used as the first AP MLD. Similarly, the first non-AP is the first non-AP MLD, the second AP is the second AP MLD, and the second non-AP is the second non-AP MLD. In the SMD_X architecture, both the first and second non-AP MLDs are associated with the first AP MLD.

[0144] For ease of description, this embodiment will use a multi-link scenario as an example, and a single-link scenario can also be understood as a single-link part of a multi-link scenario. Initially, the first non-AP MLD and the second non-AP MLD are associated with the first AP and establish a TDLS direct link. For example, before initiating roaming, the first affiliated STA in the first non-AP MLD sends a roaming notification message, or Roaming Notification frame, to the second affiliated STA in the second non-AP MLD to notify that the first non-AP MLD is about to roam and switch to the second AP MLD. Optionally, the roaming notification message also requests the second non-AP MLD to send context information related to the TDLS direct link, i.e., requests the peer STA to return the TDLS context related to roaming, so that the first non-AP MLD initiating roaming can update the TDLS direct link established with the second non-AP MLD after associating with and establishing a multi-link with the second AP MLD, maintaining the smooth / valid TDLS direct link. Therefore, in this embodiment, the roaming notification message includes, but is not limited to, at least one of the following:

[0145] 1. The MLD MAC address of the Target AP MLD (i.e., the second AP MLD) to which the first non-AP MLD will roam;

[0146] 2. The MAC address / BSSID of the auxiliary AP (e.g., the second auxiliary AP) of the Target AP MLD (i.e., the second AP MLD) to which the first non-AP MLD will roam and establish a link;

[0147] 3. Request the second non-AP MLD to provide feedback on relevant service information on the TDLS direct link, such as the uplink and downlink packet numbers (PN), sequence numbers (SN), and block acknowledgment (BA) agreement information of the (data) frame transmission on the TDLS direct link;

[0148] 4. Request the second non-AP MLD to provide relevant security information on the TDLS direct link in order to negotiate and ensure the security of P2P communication between the second non-AP MLD and the first non-AP MLD. For example, request to obtain at least one or more of the following security information: Dialog token that was used in the MIC calculation for TPK handshake message 3, Transaction Sequence number, FTE, with the MIC field of the FTE set to 0, etc.

[0149] Optionally, in this embodiment, in addition to sending roaming notification information to the second non-AP, the first non-AP may also send context request information to the second non-AP to request the second non-AP MLD to send context information related to the TDLS direct link. That is, the context request information can be included in the roaming notification information or sent separately to the second non-AP MLD; this embodiment does not limit the specifics.

[0150] 302. The second non-AP sends a roaming notification response to the first non-AP;

[0151] After receiving the roaming notification information sent by the first non-AP MLD based on the TDLS direct link, the second non-AP MLD replies with a roaming notification response, or Roaming Context frame, indicating whether it accepts maintaining the previously established TDLS direct link after the first non-AP MLD roams to the second non-AP MLD. When the roaming notification information is also used by the peer STA to return roaming-related TDLS context, the roaming notification response also carries the roaming-related TDLS context. This roaming notification response includes, but is not limited to, at least one of the following:

[0152] 1. Whether to agree to maintain the accessibility / validity of its TDLS direct link after the first non-AP MLD roaming, for example, indicated by 1 bit, setting it to 0 means disagreeing to maintain the accessibility / validity of its TDLS direct link after the first non-AP MLD roaming; setting it to 1 means agreeing to maintain the accessibility / validity of its TDLS direct link after the first non-AP MLD roaming; other methods can also be used, which are not limited here;

[0153] 2. Service information related to the TDLS direct link requested by the first non-AP MLD, such as uplink and downlink PN, SN, BA agreement and other information of (data) frame transmission on the TDLS direct link;

[0154] 3. Security information related to the TDLS direct link requested by the first non-AP MLD, such as the following response: Dialog token that was used in the MIC calculation for TPK handshake message 3, Transaction Sequence number, FTE, with the MIC field of the FTE set to 0.

[0155] Optionally, in this embodiment, the roaming-related TDLS context sent by the second non-AP to the first non-AP can be carried in the roaming notification response information, or in other information, or sent as a separate message to the first non-AP. This application does not limit the specifics.

[0156] 303. The first non-AP sends a roaming request message to the second AP MLD;

[0157] The first non-AP MLD sends a roaming request frame to the second AP MLD, requesting a roaming switch to the second AP MLD. Optionally, the roaming request frame may also carry the peer STA of the first non-AP MLD and / or the first TDLS direct link information.

[0158] It should be noted that the first TDLS direct link information can be carried in the roaming request information, or it can be carried in other information or sent as a separate information to the second AP MLD. This application does not limit the specifics.

[0159] Optionally, the first non-AP MLD can also send roaming request information to the first AP MLD, which will then forward it.

[0160] 304. The first AP and the second AP perform a context transfer;

[0161] The first AP MLD and the second AP MLD perform context transfer, wherein the context transfer includes, but is not limited to, the following: transferring the context of the TDLS direct link, transferring the context of the first non-AP, and the context of the Peer STA of the first non-AP MLD, that is, the first AP MLD and the second AP MLD transfer the context of the first non-AP MLD and the Peer STA and / or the second TDLS direct link information of MLD_R.

[0162] 305. The second AP sends a roaming response message to the first non-AP;

[0163] The second auxiliary AP of the second AP MLD sends a roaming response frame to the first auxiliary STA of the first non-AP MLD to indicate whether roaming was successful. Optionally, the roaming response frame may also indicate whether the TDLS direct link was successfully updated and carry information about the third TDLS direct link.

[0164] The TDLS information signaling during the first non-AP MLD roaming may specifically include the first TDLS direct link information contained in the Roaming Request frame, the second TDLS direct link information for context transfer interaction between the first AP MLD and the second AP MLD, and the third TDLS direct link information contained in the Roaming Response frame. Furthermore, the first, second, and third TDLS direct link information may be the same or different; this application does not impose any specific limitations on this.

[0165] It should be noted that the aforementioned first TDLS direct link information, second TDLS direct link information, and third TDLS direct link information may include, but are not limited to, at least one of the following: security information related to the TDLS direct link, address indication information, and session information related to the TDLS direct link.

[0166] 306. The first non-AP sends the first data frame to the second non-AP;

[0167] 307. The second non-AP sends a first data response frame to the first non-AP.

[0168] After the TDLS direct link is successfully updated, the first non-AP MLD and the second non-AP MLD perform P2P communication based on the updated TDLS direct link, for example, transmitting data frames. Steps 306-307 in this embodiment are similar to steps 207-208 in the embodiment shown in Figure 2, and will not be described in detail here.

[0169] Similarly, for a more detailed understanding of the embodiments shown in Figure 3, please refer to Figure 3a, which is a flowchart of another communication method provided by the embodiments of this application. The figure provides a detailed example of the TDLS direct link maintenance and update process and the interaction process between devices in the scenario of non-AP roaming to a new AP MLD. Specifically, MLD_S can correspond to the first non-AP MLD in Figure 3, and STA1 and STA2 are both affiliated STAs of MLD_S. MLD_A can correspond to the first AP MLD in Figure 3, and AP1 and AP2 are both affiliated APs of MLD_A. MLD_R can correspond to the second non-AP MLD in Figure 3, and STA3 and STA4 are both affiliated STAs of MLD_R. MLD_B can correspond to the second AP MLD in Figure 3, and AP3 and AP4 are both affiliated APs of MLD_B. MLD_R and MLD_S are both non-AP MLDs associated with MLD_B. Furthermore, MLD_A and MLD_B belong to the same SMD (labeled SMD_X) (this condition is not mandatory), meaning they can establish a trusted secure channel via a wireless or wired backhaul link, allowing them to exchange non-AP MLD data and security information. Figure 3a illustrates this using the example of MLD_R roaming to MLD_B, where MLD_A is the Serving AP MLD and MLD_B is the Target AP MLD. The systemic (signaling) flow shown in Figure 3a is as follows:

[0170] Before roaming, MLD_S and MLD_R are associated with MLD_A and a TDLS direct link is established, enabling the mutual transmission of data frames. The process of MLD_R roaming to MLD_B includes the following stages:

[0171] Phase 1: During Roaming.

[0172] Step 1: Before initiating roaming, MLD_R's (associated STA 3) sends a Roaming Notification frame to MLD_S's (associated STA 1) via the TDLS direct link, notifying MLD_S that a roaming is about to occur and the switch will be to MLD_B. Additionally, the Roaming Notification frame can also be used to request MLD_S to send the context related to its TDLS direct link;

[0173] Step 2: MLD_S's (associated STA 1) responds with a Roaming Context frame to MLD_R's (associated STA 3), indicating whether it accepts MLD_R to maintain the previously established TDLS direct link after roaming and switching to MLD_B; If maintaining the TDLS direct link, the Roaming Context frame also additionally carries the context related to the TDLS direct link;

[0174] Step 3: MLD_R sends a Roaming Request frame to MLD_B (or MLD_A), requesting to roam and switch to MLD_B; The Roaming Request frame incidentally carries the Peer STA of MLD_R and / or TDLS direct link information 1, i.e., TDLS Info.1;

[0175] Step 4: MLD_A and MLD_B transfer the context of MLD_R, as well as the Peer STA of MLD_R and / or TDLSInfo.2;

[0176] ] Step 5: MLD_B's (associated roaming AP 3) responds with a Roaming Response frame (which may carry TDLSInfo.2) to MLD_R's (associated STA 3), indicating whether the roaming is successful and whether the TDLS direct link is successfully updated; It should be noted that TDLS Info.1, TDLS Info.2, and TDLS Info.3 contain information related to the security of the TDLS direct link, and / or, address indication information, and / or, information related to the TDLS direct link session, etc.;

[0177] Phase II: P2P communication based on the updated TDLS direct link.

[0178] Step 6: If the TDLS direct link update is successful, MLD_R (affiliated STA 3) sends a (P2P) data frame to MLD_S (affiliated STA 1) through the updated TDLS direct link, indicating the MAC addresses of AP 3 and / or AP 4. The data frame sent carries the following parameters: {A1(RA) = MLD_S, A2(TA) = MLD_R, A3(BSSID) = (AP1 or AP3 or SMD_X)}. In this step, BSSID is set to the MAC address of AP1, the MAC address of AP3, or the MLD MAC address of SMD_X.

[0179] Step 7: If the TDLS direct link update is successful, MLD_S (affiliated STA 1) sends a (P2P) data frame to MLD_R (affiliated STA 3) through the updated TDLS direct link. The (MLD) MAC addresses of AP 1 and / or AP 3 and / or SMD_X need to be indicated. The data frame carries the following parameters: {A1(RA) = MLD_R, A2(TA) = MLD_S, A3(BSSID) = (AP1 or AP3 or SMD_X)}. Note that the BSSID set in Step 7 is the same as the BSSID set in Step 6.

[0180] In summary, the embodiments shown in Figures 3 and 3a propose a process and signaling design for maintaining and updating the original TDLS direct link with the peer STA after the first non-AP MLD roams to the target AP MLD. This application also proposes a process and signaling design for rebuilding the P2P link after roaming. Please refer to Figure 4, which is a flowchart of another possible communication method, including the following steps:

[0181] 401. The first non-AP sends a roaming notification to the second non-AP;

[0182] Similarly, this embodiment can also be applied to multi-link device scenarios and single-link device scenarios. When applied to a single-link device scenario, both the first non-AP and the second non-AP are associated with the first AP. The first non-AP roams from the first AP to the second AP, that is, the first AP and the second AP are the Serving AP and the Target AP, respectively, and they can belong to the same SMD (labeled as SMD X) or other architectures. There is a wireless backhaul link or a wired backhaul link between the first AP and the second AP, which can exchange non-AP data and security information. When applied to a multi-link scenario, the first AP is used as the first AP MLD. Similarly, the first non-AP is the first non-AP MLD, the second AP is the second AP MLD, and the second non-AP is the second non-AP MLD. In the SMD_X architecture, both the first non-AP MLD and the second non-AP MLD are associated with the first AP MLD.

[0183] For ease of description, this embodiment will use a multi-link scenario as an example, and a single-link scenario can also be understood as a single-link part of a multi-link scenario. Initially, the first non-AP MLD and the second non-AP MLD are associated with the first AP and establish a TDLS direct link. For example, before initiating roaming, the first affiliated STA in the first non-AP MLD sends a roaming notification message, or Roaming Notification frame, to the second affiliated STA in the second non-AP MLD through the established TDLS direct link. This notifies the first non-AP MLD that it is about to roam and switch to the second AP MLD, and invites the peer STA to switch to the same Target AP MLD. If the second non-AP MLD accepts the switch to the same AP MLD (e.g., the second AP MLD), the roaming notification message also indicates the recommended time for the second non-AP MLD to initiate the roaming switch, such as t1. Therefore, in addition to requesting whether the second non-AP MLD is willing to roam together, the roaming notification message also includes at least one or more of the following information:

[0184] 1. The MLD MAC address of the Target AP MLD (i.e., the second AP MLD) to which the first non-AP MLD will roam;

[0185] 2. The MAC address / BSSID of the auxiliary AP (e.g., the second auxiliary AP) of the Target AP MLD (i.e., the second AP MLD) to which the first non-AP MLD will roam and establish a link;

[0186] 3. It is recommended that the receiver of this frame (i.e., the first non-AP MLD) start roaming at time t1. It should be noted that time t1 can be set to the time required for the first non-AP MLD to complete roaming to the second AP MLD. In this way, if the second non-AP MLD requests roaming from the second AP MLD at time t1, a conflict can be avoided.

[0187] Optionally, in this embodiment, the first non-AP MLD may also send roaming invitation information to the second non-AP MLD to invite the second non-AP MLD to switch to the same Target AP MLD. This roaming invitation information may also include a recommended time for the second non-AP MLD to initiate a roaming switch. Therefore, this roaming invitation information can be carried in roaming notification information, in other information, or sent as a separate message; this application does not impose any specific limitations.

[0188] 402. The second non-AP sends a roaming notification response to the first non-AP;

[0189] The second non-AP MLD replies to the first non-AP MLD via a TDLS direct link with a roaming notification response message, also known as a Roaming Consideration frame. Besides indicating whether to accept roaming along with the first non-AP MLD to the target AP MLD indicated in the Roaming Notification frame (e.g., the second AP MLD), it also contains at least one or more of the following information:

[0190] 1. The MAC address / BSSID of the auxiliary AP (e.g., the second auxiliary AP) of the Target AP MLD (i.e., the second AP MLD) to which the second non-AP MLD will roam and establish a link;

[0191] 2. The time t2 for the second non-AP MLD to start roaming after updating / confirming (can be equal to t1 or not). It should be noted that the first non-AP MLD should complete roaming to the second AP MLD before time t2 to avoid conflicts with the roaming operation of the second non-AP MLD.

[0192] 3. The estimated completion time t3 for the second non-AP MLD is when the roaming process begins at time t2, switching to the second AP MLD together with the first non-AP MLD; this roaming process should be completed before time t3.

[0193] 4. The second non-AP MLD estimates the roaming duration t3-t2.

[0194] 403. First non-AP roams to second AP;

[0195] The first non-AP MLD roams to the second AP MLD and establishes a multi-link connection with the second AP MLD. The roaming process can adopt the existing roaming procedure, which will not be elaborated in this application.

[0196] 404, Second non-AP roams to second AP;

[0197] The second non-AP MLD accepts the invitation from the first non-AP MLD and also roams to the second AP MLD, establishing a multi-link connection with the second AP MLD.

[0198] It should be noted that in this embodiment, step 403 can be executed first, followed by step 404; or step 404 can be executed first, followed by step 403; or they can be executed simultaneously. That is, the timing of steps 403 and 404 is not limited in this application.

[0199] 405. The first non-AP and the second non-AP establish a new TDLS direct link through the second AP;

[0200] At time t3, the first non-AP MLD (or the second non-AP MLD) will request to establish a new TDLS direct link with the second non-AP MLD (or the first non-AP MLD) through the second AP MLD (its affiliated AP). For example, the first non-AP MLD sends a TDLS connection establishment request to the second non-AP MLD, and the second non-AP MLD sends a TDLS connection establishment request response to the first non-AP MLD to indicate acceptance of the connection establishment request, thus establishing a new TDLS direct link. The specific TDLS direct link establishment process can adopt existing standard specifications, which will not be elaborated in this application.

[0201] 406. The first non-AP sends the first data frame to the second non-AP;

[0202] 407. The second non-AP sends the first data response frame to the first non-AP.

[0203] After the first non-AP MLD and the second non-AP MLD establish a new TDLS direct link, P2P communication, such as data frame transmission, is performed based on this new TDLS direct link. Steps 406-407 in this embodiment are similar to steps 207-208 in the embodiment shown in Figure 2, and will not be described in detail here.

[0204] Similarly, for a more detailed understanding of the embodiment shown in Figure 4, please refer to Figure 4a, which is a flowchart of another communication method provided by the embodiment of this application. The figure provides a detailed example of the process of rebuilding the TDLS direct link and the interaction process between devices in the scenario of non-AP roaming to a new AP MLD. Specifically, MLD_S can correspond to the first non-AP MLD in Figure 4, and STA1 and STA2 are both affiliated STAs of MLD_S. MLD_A can correspond to the first AP MLD in Figure 4, and AP1 and AP2 are both affiliated APs of MLD_A. MLD_R can correspond to the second non-AP MLD in Figure 4, and STA3 and STA4 are both affiliated STAs of MLD_R. MLD_B can correspond to the second AP MLD in Figure 4, and AP3 and AP4 are both affiliated APs of MLD_B. MLD_R and MLD_S are both non-AP MLDs associated with MLD_B. Furthermore, MLD_A and MLD_B belong to the same SMD (labeled SMD_X) (this condition is not mandatory), meaning they can establish a trusted secure channel via a wireless or wired backhaul link, allowing them to exchange non-AP MLD data and security information. Figure 4a illustrates this using the example of MLD_R roaming to MLD_B, where MLD_A is the Serving AP MLD and MLD_B is the Target AP MLD. The systemic (signaling) flow shown in Figure 4a is as follows:

[0205] Before roaming, MLD_S and MLD_R are associated with MLD_A and a TDLS direct link is established, enabling the mutual transmission of date frames. When MLD_R is about to roam to MLD_B, the following stages are involved:

[0206] Phase 1: MLD_R requests MLD_S to roam together.

[0207] Before initiating roaming, MLD_R (affiliated STA 3) sends a Roaming Notification frame to MLD_S (affiliated STA 1) via TDLS direct link to notify MLD_S that it is about to roam and switch to MLD_B. In addition, the Roaming Notification frame is also used to invite MLD_S to roam and switch to MLD_B together, and / or to indicate the recommended time for MLD_S to initiate roaming and switching (e.g., t1).

[0208] MLD_S (affiliated STA 1) responds to the Roaming Consideration frame to MLD_R (affiliated STA 3), indicating whether to accept the roaming handover with MLD_R to MLD_B; if accepted, the Roaming Consideration frame may also carry the confirmed start time of the roaming handover (e.g., t2), and / or, the duration (e.g., t3-t2), and / or, the estimated end time (e.g., t3);

[0209] Phase 2: MLD_R and MLD_S perform roaming respectively.

[0210] Step a: MLD_R performs the existing roaming steps and establishes a multi-link with MLD_B;

[0211] Step b: MLD_S (e.g., at time t3) executes the existing roaming steps and establishes a multi-link with MLD_B; it should be noted that this patent does not limit the execution order of Step a and Step b, they can be performed simultaneously, or Step b can be executed first and then Step a.

[0212] Phase 3: MLD_S and MLD_R perform TDLS setup via MLD_B.

[0213] After time t3, MLD_S and MLD_R establish a new TDLS direct link through MLD_B via TDLS setup. This includes STA1 sending a TDLS Setup Request to AP1 to request the establishment of a new TDLS direct link with STA3, and STA3 responding by sending a TDLS Setup Response to AP1; or STA3 sending a TDLS Setup Request to AP1 to request the establishment of a new TDLS direct link with STA1, and STA1 responding by sending a TDLS Setup Response to AP1.

[0214] Phase 4: After roaming is completed, MLD_S and MLD_R continue P2P communication.

[0215] MLD_R (affiliated STA 3) sends a (P2P) data frame to MLD_S (affiliated STA 1), indicating the MAC address of AP 3 or AP 4. The data frame carries the following parameters: {A1(RA) = MLD_S, A2(TA) = MLD_R, A3(BSSID) = (AP1 or AP3)}, which are set to the MAC address of AP1 and the MAC address of AP3 in this step.

[0216] MLD_S (affiliated STA 1) sends a (P2P) data frame to MLD_R (affiliated STA 3), indicating the MAC address of AP 3 or AP 4. This data frame carries the following parameters: {A1(RA) = MLD_R, A2(TA) = MLD_S, A3(BSSID) = (AP1 or AP3)}. The BSSID set in both steps should be consistent.

[0217] The embodiments shown in Figures 3, 3a, 4, and 4a demonstrate that by performing context transfer or merging the TDLS direct link under the AP MLD architecture conforming to the 802.11 baseline and 802.11be standards into the roaming process, the non-AP MLD that has established the TDLS direct link can quickly restore the TDLS direct link when roaming to other AP MLDs. This minimizes the impact of roaming handover on the TDLS direct link, achieves TDLS direct link recovery without interruption or with minimal interruption time, and improves the continuity of P2P communication.

[0218] The above figures illustrate in detail the communication method provided in the embodiments of this application. Please refer to Figure 5, which is a storage diagram of a wireless communication device in an embodiment of this application. The wireless communication device includes a processor and a memory. The memory stores computer programs, and the processor calls and runs the computer programs stored in the memory to execute the methods provided by any embodiment of the channel determination method or channel switching method of this application, as well as any non-conflicting combination thereof. The storage medium 20 of the wireless communication device in this embodiment stores instruction / program data 21. When the instruction / program data 21 is executed, it implements the methods provided by any embodiment of the communication method of this application, as well as any non-conflicting combination thereof. The instruction / program data 21 can be formed into a program file and stored in the storage medium 20 in the form of a software product, so that a computer device (which may be a personal computer, server, or network device, etc.) or processor executes all or part of the steps of the methods in various embodiments of this application. The aforementioned storage medium 20 includes various media capable of storing program code, such as a USB flash drive, mobile hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, or terminal devices such as computers, servers, mobile phones, and tablets.

[0219] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0220] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0221] The above are merely embodiments of this application and do not limit the scope of this patent application. Any equivalent structural or procedural changes made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of this application.

[0222] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0223] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0224] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0225] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0226] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0227] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0228] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0229] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0230] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0231] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0232] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method applied to the non-access point (non-AP) side, characterized in that, include: A connection establishment request is sent to the first AP, the connection establishment request being used to request the establishment of a TDLS direct link with the second non-AP, wherein the first non-AP is associated with the first AP, and the second non-AP is associated with the second AP; The system receives a connection establishment request response sent by the first AP, which indicates acceptance of establishing the TDLS direct link.

2. The method according to claim 1, characterized in that, The connection establishment request carries the destination address DA, which is the Media Access Control (MAC) address of the second non-AP.

3. The method according to claim 2, characterized in that, The first AP and the second AP are in the same mobile domain SMD.

4. The method according to any one of claims 1 to 3, characterized in that, When the method is applied to a multi-link scenario, the first AP is the first AP multi-link device MLD, the first non-AP is the first non-AP MLD, the second AP is the second AP MLD, and the second non-AP is the second non-AP MLD.

5. The method according to claim 4, characterized in that, The connection establishment request carries a first link identifier element, which is used by the first auxiliary AP in the first AP MLD to forward the connection establishment request to the second AP MLD.

6. The method according to claim 5, characterized in that, The first link identifier element includes, but is not limited to, any of the following parameter combinations: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MAC address of the first auxiliary AP; or, The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MLD MAC address of the SMD; or, The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, the MAC address of the first auxiliary AP, and the MLD MAC address of the SMD.

7. The method according to any one of claims 4 to 6, characterized in that, The connection establishment request response carries a second link identifier element, which is used by the second auxiliary AP in the second AP MLD to forward the connection establishment request response to the first AP MLD.

8. The method according to claim 7, characterized in that, The second link identifier element includes, but is not limited to, any of the following parameter combinations: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MAC address of the second AP; or, The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MLD MAC address of the SMD; or, The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, the MAC address of the second auxiliary AP, and the MLD MAC address of the SMD.

9. The method according to any one of claims 4 to 8, characterized in that, After receiving the connection establishment request response sent by the first AP, the method further includes: Receive the first data frame sent by the second non-AP MLD; or, Send a second data frame to the second non-AP MLD; Both the first data frame and the second data frame carry corresponding address indication information.

10. The method according to claim 9, characterized in that, The method further includes: Send a first data response frame to the second non-AP MLD; or, Receive the second data response frame sent by the second non-AP MLD. Both the first data response frame and the second data response frame carry corresponding address indication information.

11. The method according to claim 9 or 10, characterized in that, The address indication information corresponding to the first data frame and the second data frame includes, but is not limited to, at least one of the following parameters: receiver address, sender address, BSSID of the basic service unit (BSS) where the first non-AP MLD and the second non-AP MLD are located, and a combination of the BSSID and a specific ID.

12. The method according to claim 11, characterized in that, The BSSID includes, but is not limited to, at least one of the following addresses: the Media Access Control (MAC) address of the first affiliated AP, the MAC address of the second affiliated AP, the MLD (MLD) MAC address of the SMD, and / or a custom address.

13. The method according to claim 12, characterized in that, When the BSSID includes the custom address, the custom address is included in the connection establishment request and / or the connection establishment request response.

14. The method according to claim 13, characterized in that, The custom address includes a new address formed by combining a portion of the address bits from the MAC address of the first auxiliary AP, the MAC address of the second auxiliary AP, and / or the MLD MAC address of the SMD.

15. The method according to any one of claims 11 to 14, characterized in that, The combination of BSSID and specific ID includes, but is not limited to, any of the following combinations: The BSSID is the MAC address of the second auxiliary AP, and the specific ID is the MAC address of the first auxiliary AP; or, The BSSID is the MAC address of the first auxiliary AP, and the specific ID is the MAC address of the second auxiliary AP; or, The BSSID is the MAC address of the second auxiliary AP, and the specific ID is the MLD MAC address of the SMD; or, The BSSID is the MAC address of the first affiliated AP, and the specific ID is the MLD MAC address of the SMD; or, The BSSID is the MLD MAC address of the SMD, and the specific ID is the MAC address of the second auxiliary AP; or, The BSSID is the MLD MAC address of the SMD, and the Specific ID is the MAC address of the first auxiliary AP.

16. The method according to any one of claims 11 to 15, characterized in that, In the address indication information corresponding to the first data frame, the receiver address is the MLD MAC address of the first non-AP MLD, and the sender address is the MLD MAC address of the second non-AP MLD; or, In the address indication information corresponding to the second data frame, the receiver address is the MLD MAC address of the second non-AP MLD, and the sender address is the MLD MAC address of the first non-AP MLD.

17. A communication method applied to a second non-AP side, characterized in that, include: The system receives a connection establishment request from a second AP, which requests the establishment of a TDLS direct link with a first non-AP. The second non-AP is associated with the second AP, and the first non-AP is associated with the first AP. Send a connection establishment request response to the second AP, the connection establishment request response being used to indicate whether to accept the establishment of the TDLS direct link.

18. The method according to claim 17, characterized in that, The connection establishment request carries the source address SA, which is the MAC address of the first non-AP.

19. The method according to claim 17 or 18, characterized in that, The connection establishment request response carries a DA, which is the MAC address of the first non-AP.

20. The method according to claim 19, characterized in that, The first AP and the second AP are in the same mobile domain SMD.

21. The method according to any one of claims 17 to 20, characterized in that, When the method is applied to a multi-link scenario, the first AP is the first AP MLD, the first non-AP is the first non-AP MLD, the second AP is the second AP MLD, and the second non-AP is the second non-AP MLD.

22. The method according to claim 21, characterized in that, The connection establishment request carries a fifth link request identifier element, which is used by the second non-AP MLD to send the connection request response to the first non-AP MLD.

23. The method according to claim 22, characterized in that, The fifth link identifier element includes, but is not limited to, any of the following parameter combinations: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MAC address of the second auxiliary AP; or, The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MLD MAC address of the SMD; or, The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, the MAC address of the second auxiliary AP, and the MLD MAC address of the SMD.

24. The method according to any one of claims 21 to 23, characterized in that, The connection establishment request response carries a sixth link identifier element, which is used by the second auxiliary AP in the second AP MLD to forward the connection establishment request response to the first AP MLD.

25. The method according to claim 24, characterized in that, The sixth link identifier element includes, but is not limited to, any of the following parameter combinations: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MAC address of the second auxiliary AP; or, The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MLD MAC address of the SMD; or, The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, the MAC address of the second auxiliary AP, and the MLD MAC address of the SMD.

26. The method according to any one of claims 21 to 25, characterized in that, After sending a connection establishment request response to the second AP, the method further includes: Receive the first data frame sent by the first non-AP MLD; or, Send a second data frame to the first non-AP MLD; Both the first data frame and the second data frame carry corresponding address indication information.

27. The method according to claim 26, characterized in that, The method further includes: Send a first data response frame to the second non-AP MLD; or, Receive the second data response frame sent by the second non-AP MLD. Both the first data response frame and the second data response frame carry corresponding address indication information.

28. A communication method applied to a first AP side, characterized in that, include: The system receives a connection establishment request from a first non-AP and sends the connection establishment request to a second AP. The connection establishment request is used to request the establishment of a TDLS direct link with the second non-AP. The first non-AP is associated with the first AP, and the second non-AP is associated with the second AP. Receive the connection establishment request response sent by the second AP, and send the connection establishment request response to the first non-AP.

29. The method according to claim 28, characterized in that, The connection establishment request carries a first DA, which is the MAC address of the second non-AP.

30. The method according to claim 28 or 29, characterized in that, The connection establishment response carries a second DA, which is the MAC address of the first non-AP.

31. The method according to claim 30, characterized in that, The first AP and the second AP are in SMD.

32. The method according to any one of claims 28 to 31, characterized in that, When the method is applied to a multi-link scenario, the first AP is the first AP multi-link device MLD, the first non-AP is the first non-AP MLD, the second AP is the second AP MLD, and the second non-AP is the second non-AP MLD.

33. The method according to claim 32, characterized in that, The connection establishment request sent to the second AP MLD carries a third link identification element, which is used by the second AP MLD to forward the connection establishment request to the second non-AP MLD.

34. The method according to claim 33, characterized in that, The third link identifier element includes, but is not limited to, any of the following parameter combinations: The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MAC address of the second auxiliary AP; or, The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MLD MAC address of the SMD; or, The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, the MAC address of the second auxiliary AP, and the MLD MAC address of the SMD.

35. The method according to any one of claims 32 to 34, characterized in that, The received connection establishment request response sent by the second AP carries fourth link identification information, which is used to forward the connection establishment request response to the first non-AP MLD.

36. The method according to claim 35, characterized in that, The fourth link identification element includes, but is not limited to, any of the following parameter combinations: The MAC address of the first non-AP MLD, the MAC address of the second non-AP MLD, and the MAC address of the first auxiliary AP; or, The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, and the MLD MAC address of the SMD; or, The MLD MAC address of the first non-AP MLD, the MLD MAC address of the second non-AP MLD, the MAC address of the first auxiliary AP, and the MLD MAC address of the SMD.

37. A communication method applied to a second AP side, characterized in that, include: The system receives a connection establishment request from a first AP and sends the connection establishment request to a second non-AP. The connection establishment request is used to request the first non-AP and the second non-AP to establish a TDLS direct link, wherein the first non-AP is associated with the first AP and the second non-AP is associated with the second AP. Receive the connection establishment request response sent by the second non-AP, and send the connection establishment request response to the first AP.

38. The method according to claim 37, characterized in that, The connection establishment request carries a first DA, which is the MAC address of the second non-AP.

39. The method according to claim 37 or 38, characterized in that, The connection establishment response carries a second DA, which is the MAC address of the first non-AP.

40. The method according to claim 38 or 39, characterized in that, The first AP and the second AP are in SMD.

41. The method according to any one of claims 38 to 40, characterized in that, When the method is applied to a multi-link scenario, the first AP is the first AP multi-link device MLD, the first non-AP is the first non-AP MLD, the second AP is the second AP MLD, and the second non-AP is the second non-AP MLD.

42. A communication method applied to a first non-AP side, characterized in that, include: A roaming notification message is sent to the second non-AP. The roaming notification message is used to notify the first non-AP to switch from roaming to the second AP. Both the first non-AP and the second non-AP are associated with the first AP and have established a TDLS direct link. Receive roaming notification response information sent by the second non-AP.

43. The method according to claim 42, characterized in that, The communication method is applied in a multi-link scenario, where the first AP is the first AP MLD, the first non-AP is the first non-AP MLD, the second AP is the second AP MLD, and the second non-AP is the second non-AP MLD.

44. The method according to claim 42 or 43, characterized in that, The roaming notification response information is used to indicate whether to maintain the TDLS direct link.

45. The method according to claim 44, characterized in that, The roaming notification information is also used to request the second non-AP to send context information related to the TDLS direct link.

46. ​​The method according to claim 45, characterized in that, When the roaming notification response information is used to indicate that the TDLS direct link should be maintained, the roaming notification response information also carries context information related to the TDLS direct link.

47. The method according to claim 44, characterized in that, The method further includes: Send a context request message to the second non-AP to request the second non-AP to send context information related to the TDLS direct link; When the roaming notification response information is used to indicate maintaining the TDLS direct link, the context information sent by the second non-AP is received.

48. The method according to claim 44, characterized in that, The roaming notification information includes, but is not limited to, at least one of the following parameters: the MLD MAC address of the second AP, the MAC address or BSSID of the second auxiliary AP of the second AP MLD, service request information, and / or security request information. The service request information is used to request feedback on service-related information of the TDLS direct link, and the security request information is used to request feedback on security-related information of the TDLS direct link.

49. The method according to claim 48, characterized in that, The roaming notification response information includes, but is not limited to, at least one of the following parameters: link maintenance indication, service-related information of the TDLS direct link, and security-related information of the TDLS direct link.

50. The method according to any one of claims 42-49, characterized in that, The method further includes: Send a roaming request message to the first AP or the second AP, the roaming request message being used to request a switch to the second AP; Receive roaming response information sent by the second AP, the roaming response information being used to indicate whether roaming was successful.

51. The method according to claim 50, characterized in that, The roaming request information also includes the peer STA information of the first non-AP and / or the first TDLS direct link information.

52. The method according to claim 51, characterized in that, The roaming response information is also used to indicate whether the TDLS direct link has been successfully transferred, and the roaming response information also includes second TDLS direct link information.

53. The method according to any one of claims 50 to 52, characterized in that, The method further includes: Send the peer STA information of the first non-AP and / or the first TDLS direct link information to the first AP or the second AP; The system receives a transfer success indication message sent by the second AP, which also includes second TDLS direct link information.

54. The method according to any one of claims 51 to 53, characterized in that, The first TDLS direct link information or the second TDLS direct link information includes, but is not limited to, at least one of the following: security information of the TDLS direct link, and / or, address indication information, and / or, session information of the TDLS direct link.

55. The method according to claim 54, characterized in that, The first TDLS direct link information is the same as the second TDLS direct link information, or the first TDLS direct link information is different from the second TDLS direct link information.

56. The method according to any one of claims 50 to 55, characterized in that, After the TDLS direct link is successfully transferred, the method further includes: Based on the TDLS direct link, a first data frame is sent to the second non-AP, or a second data frame is received from the second non-AP.

57. The method according to claim 56, characterized in that, The first data frame or the second data frame carries corresponding address indication information.

58. The method according to claim 42 or 43, characterized in that, The roaming notification information is also used to instruct the second non-AP to roam and switch to the second AP, and / or to instruct the time when the roaming switch is initiated.

59. The method according to claim 58, characterized in that, When applied to a multi-link scenario, the roaming notification information includes, but is not limited to, at least one of the following: the MLD MAC address of the second AP MLD, the MAC address or BSSID of the affiliated AP of the second AP MLD, and the time indicating when the second non-AP MLD should perform a roaming handover; or, When applied to a single-link scenario, the roaming notification information includes, but is not limited to, at least one of the following: the MAC address or BSSID of the second AP, and the time indicating when the second non-AP should perform a roaming switch.

60. The method according to claim 58 or 59, characterized in that, The method further includes: Send a roaming invitation message to the second non-AP, the roaming invitation message being used to instruct the second non-AP to roam and / or to instruct the time for initiating the roaming handover.

61. The method according to any one of claims 58 to 60, characterized in that, The roaming response information also includes, but is not limited to, at least one of the following: the negotiated start time of the roaming handover, the duration of the roaming handover, and / or the estimated end time of the roaming handover.

62. The method according to any one of claims 58 to 60, characterized in that, The method further includes: Receive roaming invitation response information sent by the second non-AP, wherein the roaming invitation response information includes, but is not limited to, at least one of the following: the negotiated start time for initiating roaming handover, the duration of roaming handover, and / or the estimated end time of roaming handover.

63. The method according to claim 61 or 62, characterized in that, The method further includes: After the estimated end time of the roaming handover is reached, a new TDLS direct link is established with the second non-AP via the second AP.

64. The method according to claim 63, characterized in that, The method further includes: Based on the new TDLS direct link, a third data frame is sent to the second non-AP, or a fourth data frame is received from the second non-AP.

65. A communication method applied to a second non-AP side, characterized in that, include: The system receives roaming notification information from a first non-AP, which is used to notify the first non-AP to switch from roaming to the second AP. Both the first non-AP and the second non-AP are associated with the first AP MLD and have established a TDLS direct link. Send a roaming notification response message to the first non-AP.

66. The method according to claim 65, characterized in that, The communication method is applied in a multi-link scenario, where the first AP is the first AP MLD, the first non-AP is the first non-AP MLD, the second AP is the second AP MLD, and the second non-AP is the second non-AP MLD.

67. The method according to claim 65 or 66, characterized in that, The roaming notification response information is used to indicate whether to maintain the TDLS direct link.

68. The method according to claim 67, characterized in that, When the roaming notification information is also used to request the second non-AP to send context information related to the TDLS direct link, the roaming notification response information also carries the context information related to the TDLS direct link.

69. The method according to claim 67, characterized in that, The method further includes: Receive context request information sent by the first non-AP, used to request the sending of context information related to the TDLS direct link; The context information is sent to the first non-AP.

70. The method according to any one of claims 65 to 69, characterized in that, After the TDLS direct link is successfully transferred, the method further includes: Based on the TDLS direct link, a first data frame is sent to the first non-AP, or a second data frame is received from the first non-AP.

71. The method according to claim 65 or 66, characterized in that, The roaming notification response information is also used to respond to whether to accept roaming and switch to the second AP.

72. The method according to claim 71, characterized in that, When the second non-AP accepts the handover to the second AP, the roaming notification response information also includes the start time of initiating the roaming handover and / or the duration.

73. The method according to claim 72, characterized in that, The method further includes: Based on the start time of the roaming handover, the roaming is switched to the second AP.

74. The method according to claim 73, characterized in that, After the roaming is switched to the second AP, the method further includes: Based on the second AP, a new TDLS direct link is established with the first non-AP.

75. A communication method applied to the AP side, characterized in that, include: The system receives roaming request information sent by the first non-AP. The roaming request information is used by the first non-AP to request a switch from the associated first AP to the second AP. The roaming request information includes the peer STA information of the first non-AP and / or the first TDLS direct link information established with the peer STA. Context transfer is performed based on the roaming request information.

76. The method according to claim 75, characterized in that, The communication method is applied in a multi-link scenario, where the first AP is the first AP MLD, the first non-AP is the first non-AP MLD, the second AP is the second AP MLD, and the second non-AP is the second non-AP MLD.

77. The method according to claim 75 or 76, characterized in that, The context transfer includes, but is not limited to, the following: transferring the context of the TDLS direct link, and / or transferring the context of the first non-AP.

78. The method according to claim 75 or 76, characterized in that, The method further includes: Send roaming response information to the first non-AP, the roaming response information being used to indicate whether roaming was successful.

79. The method according to claim 78, characterized in that, The roaming response information also includes information about the second TDLS direct link.

80. The method according to claim 79, characterized in that, The second TDLS direct link information is the same as the first TDLS direct link information, or the second TDLS direct link information is different from the first TDLS direct link information.

81. A wireless communication device, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to invoke and run the computer program stored in the memory to perform the method as described in any one of claims 1 to 80.

82. A readable storage medium, characterized in that, The computer-readable storage medium includes instructions that, when executed, cause the method according to any one of claims 1 to 80 to be implemented.

Images