Multi-link roaming communication method, multi-link communication method and wireless communication device

Abstract

Provided in the embodiments of the present application are a multi-link roaming communication method, a multi-link communication method, and a wireless communication device. The multi-link roaming communication method is executed by a first station device. The communication method comprises: performing non-simultaneous transmitting and receiving on at least any two of a plurality of links, wherein a first station device, a second station device and a third station device refer to the fact that when the first station device roams, the first station device is configured to be suitable for switching to the second station device or switching from the second station device to the third station device.

Description

Multi-link roaming communication methods, multi-link communication methods and wireless communication devices Technical Field

[0001] This application relates to the field of mobile communication technology, specifically to a multi-link roaming communication method, a multi-link communication method, and a wireless communication device. Background Technology

[0002] In the Institute of Electrical and Electronics Engineers (IEEE) Wireless Fidelity 7 (Wi-Fi 7) standard, communication between an Access Point (AP) Multi-Link Device (MLD) and a Non-AP Multi-Link Device (non-AP MLD) uses multiple links. If the non-AP MLD moves away from the first AP MLD, it needs to disconnect its authentication and association with the first AP MLD and re-authenticate and associate with the second AP MLD. During this process, the non-AP MLD's communication will suffer link interruption, making it impossible to achieve the goal of uninterrupted Wi-Fi 8 roaming.

[0003] Summary of the Invention

[0004] This application provides a multi-link roaming communication method, a multi-link communication method, and a wireless communication device to improve the problems of the prior art and other issues.

[0005] This application provides a multi-link roaming communication method, executed on a first site device. The communication method includes: non-simultaneous transmission and reception on at least two links of the multi-link system. The first site device, the second site device, and the third site device refer to the first site device being configured to switch to the second site device or to be switched from the second site device to the third site device when the first site device is roaming.

[0006] The above technical solutions ensure roaming success rate, reduce roaming latency, and facilitate uninterrupted roaming.

[0007] This application provides a multi-link communication method, executed on a first site device. The communication method includes: non-simultaneous transmission and reception on at least two links of the multi-link system. The first site device receives a frame from the second site device on a channel corresponding to the main link of the second site device. The frame of the second site device carries information of the second site device, including information of the non-main link of the second site device.

[0008] The above technical solutions ensure roaming success rate, reduce roaming latency, and facilitate uninterrupted roaming.

[0009] This application provides a multi-link communication method, executed on a first site device, wherein the communication method includes: non-simultaneous transmission and reception on at least any two links of the multi-link system, wherein the first site device simultaneously receives first data transmitted by a second site device on the first link and second data transmitted by a third site device on the second link, wherein the end time of the first data and the end time of the second data are aligned.

[0010] The above technical solutions ensure roaming success rate, reduce roaming latency, and facilitate uninterrupted roaming.

[0011] This application provides a multi-link roaming communication method, executed on a second site device. The communication method includes: non-simultaneous transmission and reception on at least two links of the multi-link system. The first site device, the second site device, and the third site device refer to the first site device being configured to switch to the second site device or to be switched from the second site device to the third site device when the first site device is roaming.

[0012] The above technical solutions ensure roaming success rate, reduce roaming latency, and facilitate uninterrupted roaming.

[0013] This application provides a multi-link communication method, executed on a second site device. The communication method includes: non-simultaneous transmission and reception on at least two links of the multi-link system. The second site device receives a frame from the third site device on the channel corresponding to the main link of the third site device. The frame of the third site device carries information of the third site device, including information of the non-main link of the third site device.

[0014] The above technical solutions improve the communication performance of multi-link communication.

[0015] This application provides a multi-link communication method, executed on a second site device. The communication method includes: non-simultaneous transmission and reception on at least two links of the multi-link system. The second site device receives a frame from the third site device on a channel corresponding to the backhaul link of the third site device. The frame from the third site device carries information about the third site device, including information about the non-primary link of the third site device.

[0016] The above technical solutions improve the communication performance of multi-link communication.

[0017] This application provides a multi-link roaming communication method, executed on a third site device. The communication method includes: non-simultaneous transmission and reception on at least two links of the multi-link system. The first site device, the second site device, and the third site device refer to the first site device being configured to switch to the second site device or to be switched from the second site device to the third site device when the first site device is roaming.

[0018] The above technical solutions ensure roaming success rate, reduce roaming latency, and facilitate uninterrupted roaming.

[0019] This application provides a multi-link communication method, executed on a third site device. The communication method includes: non-simultaneous transmission and reception on at least two links of the multi-link system. Specifically, a frame of the third site device is transmitted to a first site device on the channel corresponding to the main link of the third site device. The frame of the third site device carries information about the third site device, including information about the non-main link of the third site device.

[0020] The above technical solutions improve the communication performance of multi-link communication.

[0021] This application provides a multi-link communication method executed on a third site device. The communication method includes: non-simultaneous transmission and reception on at least two links of the multi-link system. Specifically, a frame of the third site device is transmitted to a second site device on the channel corresponding to the main link of the third site device. The frame of the third site device carries information about the third site device, including information about the non-main link of the third site device. The third site device is a target site device, and the second site device is the current site device.

[0022] The above technical solutions improve the communication performance of multi-link communication.

[0023] This application provides a multi-link communication method, executed on a third-site device, wherein the communication method includes:

[0024] Non-simultaneous transmission and reception on at least two links of a multi-link system, wherein a frame of the third site device is transmitted to the second site device on the channel corresponding to the backhaul link of the third site device, the frame of the third site device carrying information of the third site device, the information of the third site device including information of the non-primary link of the third site device, wherein the third site device is the target site device, and the second site device is the current site device.

[0025] The above technical solutions improve the communication performance of multi-link communication.

[0026] This application provides a multi-link communication method executed on a first site device. The communication method includes: transmitting information to a second site device via a backhaul link and / or a frame, which is used by the first site device to transmit data; or receiving information to be transmitted by the second site device via the backhaul link and / or the frame. The first site device transmits and receives data on at least two links of the multi-link system at different times.

[0027] The above technical solutions improve the communication performance of multi-link communication.

[0028] This application provides a wireless communication device, including a processor and a memory. The memory stores a computer program, and the processor calls and runs the computer program stored in the memory to execute the relay communication method described above.

[0029] The relay communication device provided in this application includes a processor and a memory. The memory stores a computer program, and the processor calls and runs the computer program stored in the memory to perform the relay communication method described above.

[0030] The first node provided in this application embodiment includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to perform the relay communication method described above.

[0031] The chip provided in this application embodiment is used to implement the above-described relay communication method.

[0032] Specifically, the chip includes a processor for retrieving and running a computer program from memory, causing a device equipped with the chip to perform the aforementioned relay communication method.

[0033] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to execute the above-described relay communication method.

[0034] The computer program product provided in this application includes computer program instructions that cause a computer to execute the above-described relay communication method.

[0035] The computer program provided in this application embodiment, when run on a computer, causes the computer to execute the above-described relay communication method.

[0036] The above technical solutions ensure high roaming success rates, reduce roaming latency, and facilitate uninterrupted roaming. They also improve the communication performance of multi-link systems. Attached Figure Description

[0037] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0038] Figure 1A is a flowchart illustrating the multi-link roaming communication method provided in an embodiment of this application;

[0039] Figure 1B is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0040] Figure 1C is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0041] Figure 1D is a flowchart illustrating the multi-link roaming communication method provided in an embodiment of this application;

[0042] Figure 1E is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0043] Figure 1F is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0044] Figure 1G is a flowchart illustrating the multi-link roaming communication method provided in an embodiment of this application;

[0045] Figure 1H is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0046] Figure 1I is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0047] Figure 1J is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0048] Figure 1K is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0049] Figure 2A is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0050] Figure 2B is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0051] Figure 2C is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0052] Figure 2D is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0053] Figure 3A is a schematic diagram of the time indication element format provided in an embodiment of this application;

[0054] Figure 3B is a schematic diagram of the format of the roaming window indicator element provided in an embodiment of this application;

[0055] Figure 4 is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0056] Figure 5 is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0057] Figure 6 is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0058] Figure 7 is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0059] Figure 8 is a flowchart illustrating the multi-link communication method provided in an embodiment of this application;

[0060] Figure 9 is a schematic structural diagram of a wireless communication device provided in an embodiment of this application;

[0061] Figure 10 is a schematic structural diagram of a chip according to an embodiment of this application;

[0062] Figure 11 is a schematic block diagram of a wireless communication system provided in an embodiment of this application. Detailed Implementation

[0063] 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.

[0064] 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. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0065] For ease of understanding, Table 1 provides the definitions of the main abbreviations used in this application.

[0066] Table 1: Explanation of Abbreviations

[0067] The process of a non-AP MLD switching from the current AP MLD to the target AP MLD, as well as the operations and functions implemented in each step, do not take into account the nonsimultaneous transmit and receive (NSTR) capability limitation of the MLD itself. When non-AP MLD and AP MLD devices have NSTR limitations, the above steps cannot be performed at any time, but the transmit and receive status on other links of the device must be considered to determine when roaming-related operations can be initiated.

[0068] A series of problems caused by the NSTR limitation of Non-AP MLD itself:

[0069] If the non-AP MLD is an NSTR MLD, the following NSTR-related issues need to be considered throughout the roaming process:

[0070] 1) When a Non-AP MLD initiates a roaming request to a target AP MLD on a new link, it needs to consider that the link established between itself and the current AP MLD conforms to the NSTR link pair specification.

[0071] 2) When the target AP MLD responds to the non-AP MLD with a roaming request (and / or link establishment request), it needs to consider that the link already established between the non-AP MLD and the current AP MLD conforms to the NSTR link pair specification.

[0072] 3) When the current AP MLD sends buffered downlink data to the non-AP MLD on a link that has already been established with the non-AP MLD, it needs to consider that the non-AP MLD should conform to the NSTR link pair specification when sending uplink data to the target AP MLD after establishing a new link with the target AP MLD.

[0073] 4) When the current AP MLD sends buffered downlink data to the non-AP MLD on an established link, it needs to consider that after the non-AP MLD establishes a new link with the target AP MLD, the target AP MLD should use the new link to send downlink data to the non-AP MLD in accordance with the NSTR link pair specification.

[0074] A series of problems caused by the NSTR limitation of the target AP MLD:

[0075] If the target AP MLD is an NSTR mobile AP MLD, then the following NSTR-related issues need to be considered throughout the roaming process:

[0076] 1) When a Non-AP MLD initiates a roaming request to a target AP MLD on a new link, it needs to consider the transmit and receive status of other links on the target AP MLD so that the working links on the target AP MLD conform to the NSTR link pair specification.

[0077] 2) When the target AP MLD responds to the non-AP MLD with a roaming request (and / or link establishment request), it needs to consider the transmission and reception status of the link responding to the roaming request and its other links to comply with the NSTR link pair specification.

[0078] 3) After a new link is established between a Non-AP MLD and a target AP MLD, when sending uplink data to the target AP MLD using the new link, the transmit and receive status of other links on the target AP MLD needs to be considered so that the working links on the target AP MLD conform to the NSTR link pair specification.

[0079] 4) After a non-AP MLD establishes a new link with a target AP MLD, when the target AP MLD uses the new link to send downlink data to the non-AP MLD, it is necessary to consider that the current AP MLD sends buffered downlink data to the non-AP MLD on the link already established with the non-AP MLD, in accordance with the NSTR link pair specification.

[0080] During roaming in a non-AP MLD (from initiating a roaming request, to context transfer between the current AP MLD and the target AP MLD, to completing the roaming with a roaming response), the NSTR capabilities of the current AP MLD, non-AP MLD, and target AP MLD need to be comprehensively considered. The transmission and reception of any device on a certain link (e.g., a newly established link) needs to consider its own transmission and reception status on other links when acting as an MLD, and also the transmission and reception status of other (peer) devices on various links when acting as MLDs, to ensure that the current AP MLD, non-AP MLD, and target AP MLD all comply with NSTR specifications. Therefore, execution rules need to be designed for each step of each device's operation (receive or send) (e.g., recommending / indicating when to send and / or receive) to avoid interference from simultaneous transmission and reception on NSTR links.

[0081] The methods designed through some embodiments of this application accurately indicate the receiving and / or transmitting status of the current AP MLD, non-AP MLD, and target AP MLD during roaming. This avoids the problem of frequent roaming failures or excessive time / number of attempts required for successful roaming caused by NSTR devices being unable to receive / transmit on other links when some links are in working state (e.g., receiving / transmitting). To a certain extent, this ensures the roaming success rate, reduces the latency of the roaming process, and is more conducive to achieving the goal of uninterrupted roaming.

[0082] Some embodiments of this application address the NSTR problem at different stages of roaming. Firstly, the first solution requires indication of transmission and / or reception time information on each link in the NSTR link pair. Furthermore, existing technical solutions reveal two roaming mechanisms, both facing limitations imposed by the NSTR capabilities of the transmitting / receiving devices during roaming. Therefore, the processes of the second and third solutions will be described separately.

[0083] Figure 1A is a flowchart illustrating the communication method for multi-link roaming provided in an embodiment of this application. As shown in Figure 1A, the communication method for multi-link roaming is executed on a first site device. The communication method includes at least one of the following operations: Operation 101A: The first site device transmits and receives data non-simultaneously on at least two links of the multi-link system. The first site device, the second site device, and the third site device refer to the first site device being configured to switch to the second site device or to be switched from the second site device to the third site device when the first site device is roaming.

[0084] Through the above technical solution, the first site device can transmit and receive on at least two links of the multi-link system simultaneously, which ensures the roaming success rate, reduces the latency of the roaming process, and is more conducive to achieving uninterrupted roaming.

[0085] The first site device can be a non-access point multilink device (non-AP MLD). The second site device can be the multilink device currently connected to the non-AP MLD, also known as the current site device. The third site device can be the multilink device that the non-AP MLD needs to roam to, also known as the target site device.

[0086] Simultaneous transmission and reception on at least two links in a multi-link system can be used in some embodiments of this application to address the NSTR problem at different stages of roaming. Before transmitting a frame on a link, an NSTR MLD (e.g., AP MLD or non-AP MLD) needs to consider the transmission and reception status of its other links. Through internal NSTR constraints, it can choose an appropriate time to send the frame. The first frame can only be sent to the second site device (e.g., the current AP MLD) on the first link when other links (e.g., the second link) of the first site device (e.g., the non-AP MLD) are not receiving operations.

[0087] In some embodiments of this application, the communication method further includes: when the first station device roams, determining the transmission time on at least one of the multiple links based on its own prediction. In some embodiments of this application, determining the transmission time on at least one of the multiple links based on its own prediction includes: determining the transmit / receive time information of the first station device on each link of the multiple links based on its own prediction on a first link or a second link, wherein the first link and the second link are both any one of the multiple links. In some embodiments of this application, the communication method further includes: based on the transmit / receive time information of the first station device on each link of the multiple links, the transmission time of the first station device on the first link is staggered from the reception time of the first station device on the second link, or the reception time of the first station device on the first link is staggered from the transmission time of the first station device on the second link. In some embodiments of this application, the communication method further includes: when the first station device does not perform a reception operation on one link of the multiple links, the first station device performs a transmission operation on another link of the multiple links. In some embodiments of this application, the communication method further includes: when the second site device or the third site device does not perform a transmission operation on one link of the multi-link, the first site device sends a frame to the second site device or the third site device on the other link of the multi-link.

[0088] In some embodiments of this application, all three devices (e.g., the first site device, the second site device, and the third site device) determine their transmission timing through an estimation method. This staggers the transmission timing and avoids NSTR (Network Strike-Redirect) errors. In some embodiments of this application, the first site device considers its own end: it will only transmit if there is no receiving activity on its other links. The first site device also considers the other end based on its own estimation: it will only transmit if there is no transmission activity on links other than the link receiving the first site device's transmitted frame. In some embodiments of this application, the second site device considers its own end: it will only transmit if there is no receiving activity on its other links. The second site device also considers the other end based on its own estimation: it will only transmit if there is no transmission activity on links other than the link receiving the second site device's transmitted frame. In some embodiments of this application, the third site device considers its own end: it will only transmit if there is no receiving activity on its other links. The third station device will only perform a transmission operation if there is no transmission activity on other links besides the link receiving the transmission frame from the third station device, based on its own estimation.

[0089] In some embodiments of this application, the communication method further includes: confirming the transmission and reception time information of the first station device on each of the multiple links on at least any one of the multiple links. In some embodiments of this application, confirming the transmission and reception time information of the first station device on each of the multiple links on at least any one of the multiple links includes: confirming the transmission and reception time information of the first station device on each of the multiple links on a first link or a second link, wherein the first link and the second link are both any one of the multiple links. In some embodiments of this application, the communication method further includes: based on the transmission and reception time information of the first station device on each of the multiple links, the transmission time of the first station device on the first link is staggered from the reception time of the first station device on the second link, or the reception time of the first station device on the first link is staggered from the transmission time of the first station device on the second link.

[0090] In some embodiments of this application, the three devices (e.g., the first site device, the second site device, and the third site device) all determine their transmission timing using a time indication method. The time indication can be a precise time indication or a time window indication. This staggers the transmission timing and avoids NSTR (Non-Standard Transmission).

[0091] In some embodiments of this application, the first station device considers its own end: the first station device will only perform a transmission operation if there is no receiving activity on other links of the first station device (this is its own decision and does not need to be based on the time indication). The first station device considers the peer end based on the time indication: the first station device will only perform a transmission operation if there is no transmission activity on other links besides the link receiving the transmitted frame from the first station device. In some embodiments of this application, the second station device considers its own end: the second station device will only perform a transmission operation if there is no receiving activity on other links of the second station device (this is its own decision and does not need to be based on the time indication). The second station device considers the peer end based on the time indication: the second station device will only perform a transmission operation if there is no transmission activity on other links besides the link receiving the transmitted frame from the second station device. In some embodiments of this application, the third station device considers its own end: the third station device will only perform a transmission operation if there is no receiving activity on other links of the third station device (this is its own decision and does not need to be based on the time indication). The third station device considers the peer end based on the time indication: the third station device will only perform a transmission operation if there is no transmission activity on other links besides the link receiving the transmitted frame from the third station device.

[0092] In some embodiments of this application, the communication method further includes: determining whether to send a first frame to the second station device on the first link based on the transmit / receive time information of the first station device on each of the multiple links. In some embodiments of this application, the first frame carries the transmit / receive time information of the first station device on each link. In some embodiments of this application, the communication method further includes: when the first station device does not perform a receive operation on the second link, the first station device sends the first frame to the second station device on the first link. In some embodiments of this application, the first station device sends the first frame to the second station device on the first link within a predefined time window.

[0093] In some embodiments of this application, the communication method further includes: when the first station device does not transmit on the second link, the first station device receives a second frame transmitted by the second station device on the first link. In some embodiments of this application, the first station device receives the second frame transmitted by the second station device on the first link within a predefined time window. In some embodiments of this application, the second frame carries transmit / receive time information of the second station device on each link and / or transmit / receive time information of the third station device on each link.

[0094] In some embodiments of this application, the communication method further includes: determining whether to send a third frame to the third station device on the second link based on the transmit / receive time information of the first station device on each link of the multi-link system or based on the first station device's own prediction of the transmit time on at least one link of the multi-link system. In some embodiments of this application, the third frame carries the transmit / receive time information of the first station device on each link. In some embodiments of this application, the communication method further includes: when the first station device does not perform a receive operation on the first link, the first station device sends the third frame to the third station device on the second link. In some embodiments of this application, the first station device sends the third frame to the third station device on the second link within a predefined time window. In some embodiments of this application, the communication method further includes: when the first station device does not perform a transmit operation on the first link, the first station device receives a fourth frame sent by the third station device on the second link. In some embodiments of this application, the first station device receives the fourth frame sent by the third station device on the second link within a predefined time window.

[0095] In some embodiments of this application, the fourth frame carries the transmit / receive time information of the third station device on each link and / or the transmit / receive time information of the second station device on each link. In some embodiments of this application, the communication method further includes: when the first station device does not perform a receive operation on one link of the multi-link system, the first station device performs a transmit operation on another link of the multi-link system. In some embodiments of this application, the communication method further includes: when the second station device or the third station device does not perform a transmit operation on one link of the multi-link system, the first station device transmits a frame to the second station device or the third station device on another link of the multi-link system.

[0096] In some embodiments of this application, the communication method further includes: the first station device receiving a frame from the third station device on a channel corresponding to the main link of the third station device, wherein the frame from the third station device carries information about the third station device, including information about the non-main link of the third station device. In some embodiments of this application, the communication method further includes: simultaneously receiving first data transmitted by the second station device on a first link and second data transmitted by the third station device on a second link, wherein the end time of the first data is aligned with the end time of the second data.

[0097] Figure 1B is a flowchart illustrating a multi-link communication method provided in an embodiment of this application. As shown in Figure 1B, the multi-link communication method is executed on a first site device. The communication method includes at least one of the following operations: Operation 101B: The first site device transmits and receives data non-simultaneously on at least two links of the multi-link system; Operation 102B: The first site device receives a frame from the second site device on the channel corresponding to the main link of the second site device. The frame carries information about the second site device, including information about the non-main links of the second site device. This technical solution improves the communication performance of the multi-link system. The second site device can be a target site device.

[0098] In some embodiments of this application, a first site device (e.g., a Non-AP MLD) receives frames such as beacons and probe responses from the second site device (e.g., the target AP MLD) on the channel corresponding to the main link (i.e., the first link) of the second site device (e.g., the target AP MLD), and learns information about the second site device (e.g., the target AP MLD) (e.g., functional elements, extended functional elements, and multi-link elements), including information from the non-main link.

[0099] Figure 1C is a flowchart illustrating a multi-link communication method provided in an embodiment of this application. As shown in Figure 1C, the multi-link communication method is executed on a first station device, wherein the communication method includes at least one of the following operations: Operation 101C: The first station device transmits and receives data non-simultaneously on at least two links of the multi-link system; Operation 102C: The first station device simultaneously receives first data transmitted by a second station device on the first link and second data transmitted by a third station device on the second link, wherein the end time of the first data and the end time of the second data are aligned. This technical solution improves the communication performance of the multi-link system.

[0100] Figure 1D is a flowchart illustrating the multi-link roaming communication method provided in an embodiment of this application. As shown in Figure 1D, the multi-link roaming communication method is executed on a second site device. The communication method includes at least one of the following operations: Operation 101D: The second site device transmits and receives data non-simultaneously on at least two links of the multi-link system. The first site device, the second site device, and the third site device refer to the first site device being configured to switch to the second site device or to be switched from the second site device to the third site device when the first site device is roaming.

[0101] Through the above technical solution, the second site equipment can transmit and receive on at least two links of the multi-link system simultaneously, which ensures the roaming success rate, reduces the latency of the roaming process, and is more conducive to achieving uninterrupted roaming.

[0102] The first site device can be a non-access point multilink device (non-AP MLD). The second site device can be the multilink device currently connected to the non-AP MLD, also known as the current site device. The third site device can be the multilink device that the non-AP MLD needs to roam to, also known as the target site device.

[0103] In some embodiments of this application, the communication method further includes: when the second station device responds to the roaming of the first station device, determining the transmission time on at least one of the multiple links based on its own prediction. In some embodiments of this application, determining the transmission time on at least one of the multiple links based on its own prediction includes: determining the transmit / receive time information of the second station device on each link of the multiple links based on its own prediction on a first link or a second link, wherein the first link and the second link are both any one of the multiple links. In some embodiments of this application, the communication method further includes: based on the transmit / receive time information of the second station device on each link of the multiple links, the transmission time of the second station device on the first link is staggered from the reception time of the second station device on the second link, or the reception time of the second station device on the first link is staggered from the transmission time of the second station device on the second link. In some embodiments of this application, the communication method further includes: when the second station device does not perform a reception operation on one link of the multiple links, the second station device performs a transmission operation on another link of the multiple links. In some embodiments of this application, the communication method further includes: when the first site device or the third site device does not perform a transmission operation on one link of the multi-link, the second site device sends a frame to the first site device or the third site device on another link of the multi-link.

[0104] In some embodiments of this application, all three devices (e.g., the first site device, the second site device, and the third site device) determine their transmission timing through an estimation method. This staggers the transmission timing and avoids NSTR (Network Strike-Redirect) errors. In some embodiments of this application, the first site device considers its own end: it will only transmit if there is no receiving activity on its other links. The first site device also considers the other end based on its own estimation: it will only transmit if there is no transmission activity on links other than the link receiving the first site device's transmitted frame. In some embodiments of this application, the second site device considers its own end: it will only transmit if there is no receiving activity on its other links. The second site device also considers the other end based on its own estimation: it will only transmit if there is no transmission activity on links other than the link receiving the second site device's transmitted frame. In some embodiments of this application, the third site device considers its own end: it will only transmit if there is no receiving activity on its other links. The third station device will only perform a transmission operation if there is no transmission activity on other links besides the link receiving the transmission frame from the third station device, based on its own estimation.

[0105] In some embodiments of this application, the communication method further includes: confirming the transmission and reception time information of the second station device on each of the multiple links on at least any one of the multiple links. In some embodiments of this application, confirming the transmission and reception time information of the second station device on each of the multiple links on at least any one of the multiple links includes: confirming the transmission and reception time information of the second station device on each of the multiple links on a first link or a second link, wherein the first link and the second link are both any one of the multiple links. In some embodiments of this application, the communication method further includes: based on the transmission and reception time information of the second station device on each of the multiple links, the transmission time of the second station device on the first link is staggered from the reception time of the second station device on the second link, or the reception time of the second station device on the first link is staggered from the transmission time of the second station device on the second link. In some embodiments of this application, the communication method further includes: based on the transmission and reception time information of the second station device on each of the multiple links, confirming whether a first frame sent by the first station device is received on the first link. In some embodiments of this application, the first frame carries the transmission and reception time information of the first station device on each link. In some embodiments of this application, the communication method further includes: when the second station device does not perform a transmission operation on the second link, the second station device receives the first frame transmitted by the first station device on the first link. In some embodiments of this application, the second station device receives the first frame transmitted by the first station device on the first link within a predefined time window. In some embodiments of this application, the communication method further includes: when the second station device does not perform a reception operation on the second link, the second station device transmits a second frame to the first station device on the first link. In some embodiments of this application, the second station device transmits the second frame to the first station device on the first link within a predefined time window. In some embodiments of this application, the second frame carries the transmission and reception time information of the second station device on each link and / or the transmission and reception time information of the third station device on each link.

[0106] In some embodiments of this application, the three devices (e.g., the first site device, the second site device, and the third site device) all determine their transmission timing using a time indication method. The time indication can be a precise time indication or a time window indication. This staggers the transmission timing and avoids NSTR (Non-Standard Transmission).

[0107] In some embodiments of this application, the first station device considers its own end: the first station device will only perform a transmission operation if there is no receiving activity on other links of the first station device (this is its own decision and does not need to be based on the time indication). The first station device considers the peer end based on the time indication: the first station device will only perform a transmission operation if there is no transmission activity on other links besides the link receiving the transmitted frame from the first station device. In some embodiments of this application, the second station device considers its own end: the second station device will only perform a transmission operation if there is no receiving activity on other links of the second station device (this is its own decision and does not need to be based on the time indication). The second station device considers the peer end based on the time indication: the second station device will only perform a transmission operation if there is no transmission activity on other links besides the link receiving the transmitted frame from the second station device. In some embodiments of this application, the third station device considers its own end: the third station device will only perform a transmission operation if there is no receiving activity on other links of the third station device (this is its own decision and does not need to be based on the time indication). The third station device considers the peer end based on the time indication: the third station device will only perform a transmission operation if there is no transmission activity on other links besides the link receiving the transmitted frame from the third station device.

[0108] In some embodiments of this application, the communication method further includes: determining, based on the transmit / receive time information of the second station device on each of the multiple links or based on its own prediction, whether to send a third frame to the third station device on the second link. In some embodiments of this application, the communication method further includes: the third frame carrying the transmit / receive time information of the second station device on each link. In some embodiments of this application, the communication method further includes: when the second station device does not have a receiving operation on the first link, the second station device sends the third frame to the third station device on the second link. In some embodiments of this application, the communication method further includes: the second station device sending the third frame to the third station device on the second link within a predefined time window. In some embodiments of this application, the communication method further includes: when the second station device does not have a transmitting operation on the first link, the second station device receives a fourth frame sent by the third station device on the second link. In some embodiments of this application, the second station device receives the fourth frame sent by the third station device on the second link within a predefined time window.

[0109] In some embodiments of this application, the fourth frame carries the transmission and reception time information of the third station device on each link. In some embodiments of this application, the communication method further includes: when the second station device does not receive on one link of the multi-link system, the second station device performs a transmission operation on another link of the multi-link system. In some embodiments of this application, the communication method further includes: when the first station device or the third station device does not transmit on one link of the multi-link system, the second station device sends a frame to the first station device or the third station device on another link of the multi-link system. In some embodiments of this application, the communication method further includes: the second station device receives a frame from the third station device on the channel corresponding to the main link of the third station device, the frame carrying information about the third station device, including information about the non-main link of the third station device.

[0110] In some embodiments of this application, the communication method further includes: the second station device receiving a frame from the third station device on a channel corresponding to the backhaul link of the third station device, wherein the frame from the third station device carries information about the third station device, including information about the non-main link of the third station device. In some embodiments of this application, the communication method further includes: the second station device sending the information about the third station device to the first station device.

[0111] Figure 1E is a flowchart illustrating a multi-link communication method provided in an embodiment of this application. As shown in Figure 1E, the multi-link communication method is executed on a second station device, wherein the communication method includes at least one of the following operations: Operation 101E: The second station device transmits and receives data non-simultaneously on at least two links of the multi-link system; Operation 102E: The second station device receives a frame from the third station device on the channel corresponding to the main link of the third station device. The frame from the third station device carries information about the third station device, including information about the non-main link of the third station device. The second station device then sends the information of the third station device to the first station device.

[0112] The second site device (e.g., the current AP MLD) receives beacon frames or other information (e.g., functional elements, extended functional elements, and multi-link elements, etc.) from the third site device (e.g., the target AP MLD) on the main link (i.e., the first link), including information from the non-main link, and then sends it to the first site device (e.g., the non-AP MLD) through the interaction of roaming request / response and / or FT request / response (and / or (re)association request / response).

[0113] Figure 1F is a flowchart illustrating a multi-link communication method provided in an embodiment of this application. As shown in Figure 1F, the multi-link communication method is executed on a second station device, wherein the communication method includes at least one of the following operations: Operation 101F: The second station device transmits and receives data non-simultaneously on at least two links of the multi-link system; Operation 102F: The second station device receives a frame from the third station device on the channel corresponding to the backhaul link of the third station device. The frame from the third station device carries information about the third station device, including information about the non-primary link of the third station device. The second station device then sends the information of the third station device to the first station device.

[0114] The second site device (e.g., the current AP MLD) obtains information (e.g., functional elements, extended functional elements, and multi-link elements, etc.) of the third site device (e.g., the target AP MLD) via the backhaul link, including information of the non-primary link, and then sends it to the first site device (e.g., the non-AP MLD) through the interaction of roaming request / response and / or FT request / response (and / or (re)association request / response).

[0115] Figure 1G is a flowchart illustrating the multi-link roaming communication method provided in an embodiment of this application. As shown in Figure 1G, the multi-link roaming communication method is executed on a third site device. The communication method includes at least one of the following operations: Operation 101G: The third site device transmits and receives data non-simultaneously on at least two links of the multi-link system. The first site device, second site device, and third site device refer to the first site device being configured to switch to the second site device or be switched from the second site device to the third site device when the first site device is roaming. The second site device sends information about the third site device to the first site device.

[0116] Through the above technical solution, the third station device can transmit and receive on at least two links of the multi-link system simultaneously, which ensures the roaming success rate, reduces the latency of the roaming process, and is more conducive to achieving uninterrupted roaming.

[0117] The first site device can be a non-access point multilink device (non-AP MLD). The second site device can be the multilink device currently connected to the non-AP MLD, also known as the current site device. The third site device can be the multilink device that the non-AP MLD needs to roam to, also known as the target site device.

[0118] In some embodiments of this application, the communication method further includes: when the third station device responds to the roaming of the first station device, determining the transmission time on at least one link of the multi-link based on its own prediction. In some embodiments of this application, determining the transmission time on at least one link of the multi-link based on its own prediction includes: determining the transmission and reception time information of the third station device on each link of the multi-link based on its own prediction on a first link or a second link, wherein the first link and the second link are both any links in the multi-link. In some embodiments of this application, the communication method further includes: based on the transmission and reception time information of the second station device on each link of the multi-link, the transmission time of the third station device on the first link is staggered from the reception time of the third station device on the second link, or the reception time of the third station device on the first link is staggered from the transmission time of the third station device on the second link. In some embodiments of this application, the communication method further includes: when the third station device does not perform a reception operation on one link of the multi-link, the third station device performs a transmission operation on another link of the multi-link. In some embodiments of this application, the communication method further includes: when the first site device or the second site device does not perform a transmission operation on one link of the multi-link, the third site device sends a frame to the first site device or the second site device on another link of the multi-link.

[0119] In some embodiments of this application, all three devices (e.g., the first site device, the second site device, and the third site device) determine their transmission timing through an estimation method. This staggers the transmission timing and avoids NSTR (Network Strike-Redirect) errors. In some embodiments of this application, the first site device considers its own end: it will only transmit if there is no receiving activity on its other links. The first site device also considers the other end based on its own estimation: it will only transmit if there is no transmission activity on links other than the link receiving the first site device's transmitted frame. In some embodiments of this application, the second site device considers its own end: it will only transmit if there is no receiving activity on its other links. The second site device also considers the other end based on its own estimation: it will only transmit if there is no transmission activity on links other than the link receiving the second site device's transmitted frame. In some embodiments of this application, the third site device considers its own end: it will only transmit if there is no receiving activity on its other links. The third station device will only perform a transmission operation if there is no transmission activity on other links besides the link receiving the transmission frame from the third station device, based on its own estimation.

[0120] In some embodiments of this application, the communication method further includes: confirming the transmission and reception time information of the third station device on each of the multiple links on at least any one of the multiple links. In some embodiments of this application, confirming the transmission and reception time information of the third station device on each of the multiple links on at least any one of the multiple links includes: confirming the transmission and reception time information of the third station device on each of the multiple links on a first link or a second link, wherein the first link and the second link are both any one of the multiple links. In some embodiments of this application, the communication method further includes: based on the transmission and reception time information of the third station device on each of the multiple links, the transmission time of the third station device on the first link is staggered from the reception time of the third station device on the second link, or the reception time of the third station device on the first link is staggered from the transmission time of the third station device on the second link. In some embodiments of this application, the communication method further includes: based on the transmission and reception time information of the third station device on each of the multiple links, confirming whether a first frame sent by the first station device is received on the first link. In some embodiments of this application, the first frame carries the transmission and reception time information of the first site device on each link. In some embodiments of this application, the communication method further includes: when the third site device does not transmit on the second link, the third site device receives the first frame transmitted by the first site device on the first link. In some embodiments of this application, the third site device receives the first frame transmitted by the first site device on the first link within a predefined time window. In some embodiments of this application, the communication method further includes: when the third site device does not receive on the second link, the third site device sends a second frame to the first site device on the first link. In some embodiments of this application, the third site device sends the second frame to the first site device on the first link within a predefined time window. In some embodiments of this application, the second frame carries the transmission and reception time information of the second site device on each link and / or the transmission and reception time information of the third site device on each link.

[0121] In some embodiments of this application, the three devices (e.g., the first site device, the second site device, and the third site device) all determine their transmission timing using a time indication method. The time indication can be a precise time indication or a time window indication. This staggers the transmission timing and avoids NSTR (Non-Standard Transmission).

[0122] In some embodiments of this application, the first station device considers its own end: the first station device will only perform a transmission operation if there is no receiving activity on other links of the first station device (this is its own decision and does not need to be based on the time indication). The first station device considers the peer end based on the time indication: the first station device will only perform a transmission operation if there is no transmission activity on other links besides the link receiving the transmitted frame from the first station device. In some embodiments of this application, the second station device considers its own end: the second station device will only perform a transmission operation if there is no receiving activity on other links of the second station device (this is its own decision and does not need to be based on the time indication). The second station device considers the peer end based on the time indication: the second station device will only perform a transmission operation if there is no transmission activity on other links besides the link receiving the transmitted frame from the second station device. In some embodiments of this application, the third station device considers its own end: the third station device will only perform a transmission operation if there is no receiving activity on other links of the third station device (this is its own decision and does not need to be based on the time indication). The third station device considers the peer end based on the time indication: the third station device will only perform a transmission operation if there is no transmission activity on other links besides the link receiving the transmitted frame from the third station device.

[0123] In some embodiments of this application, the communication method further includes: determining, based on the transmission and reception time information of the third station device on each of the multiple links or the third station device's own prediction, whether to send a third frame to the second station device on the second link. In some embodiments of this application, the communication method further includes: the third frame carrying the transmission and reception time information of the third station device on each link. In some embodiments of this application, the communication method further includes: when the third station device does not have a receiving operation on the first link, the third station device sends the third frame to the second station device on the second link. In some embodiments of this application, the third station device sends the third frame to the second station device on the second link within a predefined time window. In some embodiments of this application, the communication method further includes: when the third station device does not have a transmitting operation on the first link, the third station device receives a fourth frame sent by the second station device on the second link.

[0124] In some embodiments of this application, the third station device receives the fourth frame sent by the second station device on the second link within a predefined time window. In some embodiments of this application, the fourth frame carries the transmission and reception time information of the second station device on each link. In some embodiments of this application, the communication method further includes: when the third station device does not perform a receiving operation on one link of the multi-link system, the third station device performs a transmitting operation on another link of the multi-link system. In some embodiments of this application, the communication method further includes: when the first station device or the second station device does not perform a transmitting operation on one link of the multi-link system, the third station device sends a frame to the first station device or the second station device on another link of the multi-link system.

[0125] In some embodiments of this application, the communication method further includes: sending a frame of the third site device to the first site device on a channel corresponding to the main link of the third site device, wherein the frame of the third site device carries information of the third site device, and the information of the third site device includes information of the non-main link of the third site device. In some embodiments of this application, the communication method further includes: sending a frame of the third site device to the second site device on a channel corresponding to the main link of the third site device, wherein the frame of the third site device carries information of the third site device, and the information of the third site device includes information of the non-main link of the third site device. In some embodiments of this application, the communication method further includes: sending a frame of the third site device to the second site device on a channel corresponding to the backhaul link of the third site device, wherein the frame of the third site device carries information of the third site device, and the information of the third site device includes information of the non-main link of the third site device.

[0126] Figure 1H is a flowchart illustrating a multi-link communication method provided in an embodiment of this application. As shown in Figure 1H, the multi-link communication method is executed on a third station device. The communication method includes at least one of the following operations: Operation 101H: The third station device transmits and receives data non-simultaneously on at least two links of the multi-link system; Operation 102H: The third station device sends a frame to a first station device on the channel corresponding to the main link of the third station device. The frame of the third station device carries information about the third station device, including information about the non-main link of the third station device.

[0127] Figure 1I is a flowchart illustrating a multi-link communication method provided in an embodiment of this application. As shown in Figure 1I, the multi-link communication method is executed on a third site device. The communication method includes at least one of the following operations: Operation 101I: The third site device transmits and receives data non-simultaneously on at least two links of the multi-link system. Operation 102I: The third site device sends a frame to a second site device on the channel corresponding to the main link of the third site device. The frame of the third site device carries information about the third site device, including information about the non-main link of the third site device. The third site device is the target site device, and the second site device is the current site device.

[0128] Figure 1J is a flowchart illustrating a multi-link communication method provided in an embodiment of this application. As shown in Figure 1J, the multi-link communication method is executed on a third site device. The communication method includes at least one of the following operations: Operation 101J: The third site device transmits and receives data non-simultaneously on at least two links of the multi-link system; Operation 102J: The third site device sends a frame to a second site device on the channel corresponding to the backhaul link of the third site device. The frame of the third site device carries information about the third site device, including information about the non-primary link of the third site device. The third site device is the target site device, and the second site device is the current site device.

[0129] Figure 1K is a flowchart illustrating a multi-link communication method provided in an embodiment of this application. As shown in Figure 1K, the multi-link communication method is executed on a first station device, wherein the communication method includes at least one of the following operations: Operation 101K: transmitting information to a second station device via a backhaul link and / or a frame for data transmission by the first station device, or receiving information to be transmitted by the second station device via the backhaul link and / or the frame, wherein the first station device transmits and receives data non-simultaneously on at least two links of the multi-link system. This technical solution improves the communication performance of the multi-link system.

[0130] In some embodiments of this application, the information includes one or more of the following: modulation and coding scheme (MCS), channel bandwidth, resource unit size, and / or number of spatial streams. In some embodiments of this application, the communication method further includes: using the buffer status reports of the first site device and / or the second site device to assist one of the first site device and the second site device in calculating and / or estimating the data transmission time of the other of the first site device and the second site device. In some embodiments of this application, the first site device is a target site device, and the second site device is the current site device, or the first site device is the current site device, and the second site device is the current target site device.

[0131] In some embodiments of this application, the first site device and the second site device (e.g., between the current AP MLD and the target AP MLD) can exchange information about the MCS (Modulation and Coding Scheme) and / or channel bandwidth and / or Resource Unit (RU) size and / or Spatial Stream number used for data transmission via backhaul links or beacon frames (or other frames). This information, combined with the AP MLD's Buffer Status Report (BSR), can assist one AP MLD in calculating / estimating the data transmission time of another AP MLD. Therefore, when performing multi-AP cooperation, the calculated / estimated data transmission time can be used to share transmission resources (e.g., transmission duration, bandwidth used for transmission, etc.) with the other AP MLD.

[0132] The solution will now be described with reference to the accompanying drawings:

[0133] First Solution: NSTR Time Indication and Interaction: The first solution is applicable to all subsequent embodiments.

[0134] Before sending a frame on a link, an NSTR MLD (such as an AP MLD or non-AP MLD) needs to consider the transmission and reception status of its other links. Through internal NSTR constraints, it can choose an appropriate time to send the frame. For example, as shown in Figure 2A, before a non-AP MLD sends the first frame to the current AP MLD on the first link, it can first perform a "time information determination" operation: only when other links of the non-AP MLD (such as the second link) are not receiving data can the first frame be sent to the current AP MLD on the first link. The first frame can also carry the transmission and reception time information of each link of the non-AP MLD (see the second embodiment of this application for specific design). After receiving this transmission and reception time information, the current AP MLD can decide when to send the second frame to the non-AP MLD on the first link based on the transmission and reception information of each link of the non-AP MLD. Because the transmission time of the second frame needs to be staggered from the transmission time of the non-AP MLD on the second link, simultaneous transmission and reception operations on the NSTR link are avoided. The second frame can also carry the transmission and reception time information of each link of the current AP MLD to help the non-AP MLD decide when to initiate frame transmission to the current AP MLD in the future (or next time).

[0135] Similarly, when a non-AP MLD sends a third frame to the target AP MLD on the second link, it can first perform a "time information determination" operation. Only when other links of the non-AP MLD (such as the first link) are not receiving data can the first frame be sent to the current AP MLD on the first link. The third frame can also carry the transmission and reception time information of each link of the non-AP MLD. After receiving this transmission and reception time information, the target AP MLD can decide when to send a fourth frame to the non-AP MLD on the second link based on the transmission and reception information of each link of the non-AP MLD. This is because the transmission time of the fourth frame needs to be staggered from the transmission time of the non-AP MLD on the first link to avoid simultaneous transmission and reception on the NSTR link. The fourth frame can also carry the transmission and reception time information of each link of the target AP MLD to assist the non-AP MLD in deciding when to initiate frame transmission to the target AP MLD in the future (or next time).

[0136] Furthermore, the current AP MLD and the target AP MLD can exchange their respective transmit and receive time information on each link via the backhaul link. For example, the current AP MLD carries the transmit and receive time information of the target AP MLD on each link in the second frame, thereby assisting the non-AP MLD in deciding when to initiate the third frame on the second link.

[0137] It is worth noting that the first, second, third, and fourth frames do not require each frame to carry the aforementioned transmission and reception time information. Alternatively, the aforementioned transmission and reception time information can be carried when a frame (e.g., the third frame) is sent but no corresponding response frame (e.g., the fourth frame, or an acknowledgment frame) is received, and the frame is re-initiated. This helps to better assist in deciding the timing of subsequent frame transmissions, avoids frame transmission failures caused by NSTR interference, and prolongs roaming time.

[0138] The transmit / receive time information on each link comes from the time schedule records of the NSTR MLD device itself for preparing to receive and / or send frames on each link.

[0139] The principle for using the aforementioned transmit / receive time information is that a certain (NSTR) MLD device arranges its own frame interaction time according to the instructions of the transmit / receive time information to avoid simultaneous transmission and reception on the NSTR link for itself and the peer. For example, in Figure 2A, if the non-AP MLD indicates in the third frame that it will transmit on the first link at time t1 to t2, then the target AP MLD should avoid time t1 to t2 when replying to the fourth frame on the second link.

[0140] The specific design of the transmission and reception time information on each link is as described in the second embodiment of this application.

[0141] Second solution: MLO-based roaming: The second solution can be applied to Examples 1-8 and Example 15.

[0142] As shown in Figure 2B, in the initial state, the non-AP MLD establishes a first link with the current AP MLD. When the non-AP MLD needs to switch from the current AP MLD to the target AP MLD due to movement (or other reasons), the main signaling process for roaming through link reconfiguration is as follows:

[0143] Step 1 (corresponding to Example 3): The non-AP MLD (using the first link) initiates a roaming request to the current AP MLD, and can also be used to request information about candidate AP MLDs.

[0144] Step 2 (corresponding to Example 3): The current AP MLD (on the first link) replies with a roaming response, allowing / rejecting roaming requests from non-AP MLDs, and may also carry information about candidate AP MLDs recommended by the current AP MLD.

[0145] Note 1: If the non-AP MLD has already obtained the appropriate target AP MLD information by receiving beacon frames from other surrounding AP MLDs, then steps 1 and 2 can be skipped, and step 3 can be executed directly.

[0146] Note 2: Non-AP MLDs can select a suitable AP MLD as the target AP MLD from the candidate AP MLDs.

[0147] Step 3 (corresponding to Example 4): The non-AP MLD (using its associated STA) initiates a link reconfiguration request to the target AP MLD (via a link reconfiguration request frame or via an FT request frame), requesting the establishment of a new link (e.g., a second link).

[0148] Step 4 (corresponding to Example 6): After receiving the link reconfiguration request from the non-AP MLD, the target AP MLD will request the context of the non-AP MLD from the current AP MLD through the backhaul link to perform context transfer in preparation for roaming.

[0149] Note: Step 4 can also occur before step 3, for example, between step 2 and step 3.

[0150] Step 5 (corresponding to Example 5): The target AP MLD sends a link reconfiguration response to the non-AP MLD on the second link. If the target AP MLD agrees to the non-AP MLD's link reconfiguration request and establishes a new second link, then the establishment of the second link between the non-AP MLD and the target AP MLD is complete.

[0151] Step 6 (corresponding to Example 7): This mainly involves data transmission between the non-AP MLD and the current AP MLD and / or the target AP MLD; specifically, it consists of 3 operations (the operations are not in any particular order, and only some of them may be performed):

[0152] Step 6a: Downlink data buffered by the current AP MLD for the non-AP MLD can continue to be transmitted to the non-AP MLD through the previously established first link.

[0153] Step 6b: The target AP MLD can send new downlink data to the non-AP MLD through the newly established second link.

[0154] Step 6c: The Non-AP MLD can send uplink data to the target AP MLD through the newly established second link.

[0155] Step 7 (corresponding to Example 8): After the Non-AP MLD establishes a new second link with the target AP MLD, the first link with the current AP MLD can be disconnected. Then, the non-AP MLD can send a link reconfiguration request to the current AP MLD on the first link, instructing the first link to be deleted.

[0156] Step 8 (corresponding to Example 8): After receiving the link reconfiguration request sent by the non-AP MLD on the first link, the current AP MLD replies with a link reconfiguration response, confirming that the first link with the non-AP MLD has been disconnected.

[0157] Through the above steps, the non-AP MLD completes the handover / roaming operation from the current AP MLD to the target AP MLD. It is worth noting that Figure 2B is only an example and does not represent the only process for implementing roaming. In actual roaming, the current AP MLD (or the target AP MLD) may also initiate the roaming request. Furthermore, roaming initiated by the non-AP MLD can also involve sending a roaming request to the current AP MLD.

[0158] Third solution: FT-based roaming: The third solution can be applied to Examples 1-2 and 9-15.

[0159] Roaming is performed via enhanced FT as shown in Figure 2C. If the target AP MLD is an NSTR mobile AP MLD, then when a non-AP MLD initiates a reassociation request to the target AP MLD, it must be initiated on the primary link according to the standard. Then, a link is added on the non-primary link through the reassociation request initiated on the primary link. The specific main signaling flow is as follows:

[0160] Step 1 (corresponding to Example 9): The non-AP MLD (using the first link) initiates an FT request to the current AP MLD to request AP MLD switching, and can also be used to request information on candidate AP MLDs; the current AP MLD sends the FT request to the target AP MLD.

[0161] Step 2 (corresponding to Example 9): The target AP MLD responds to the FT request of the non-AP MLD by sending an FT response to the current AP MLD, which may carry information about the target AP MLD; the current AP MLD (on the first link) sends the FT response sent by the target AP MLD to the non-AP MLD, which may carry a roaming request to allow / deny the non-AP MLD, and may also carry information about candidate AP MLDs recommended by the current AP MLD or requested by the non-AP MLD.

[0162] Step 3 (corresponding to Example 10): The non-AP MLD (using its affiliated STA) initiates a reassociation request to the affiliated AP corresponding to the main link of the target AP MLD, requesting to associate with the target AP MLD and establish a new link (e.g., a second link).

[0163] Step 4 (corresponding to Example 12): After receiving the reassociation request from the non-AP MLD, the target AP MLD requests the context of the non-AP MLD from the current AP MLD through the backhaul link to perform context transfer in preparation for roaming.

[0164] Note: The context transfer performed in step 4 can also occur before step 3.

[0165] Step 5 (corresponding to Example 11): The target AP MLD sends a reassociation response to the non-AP MLD on the main link. If the target AP MLD agrees to the non-AP MLD's reassociation request and establishes a new second link, then the second link between the non-AP MLD and the target AP MLD is established.

[0166] Step 6 (corresponding to Example 13): This mainly involves data transmission between the non-AP MLD and the current AP MLD and / or the target AP MLD; specifically, it consists of 3 operations (the operations are not in any particular order, and only some of them may be performed):

[0167] Step 6a: Downlink data buffered by the current AP MLD for the non-AP MLD can continue to be transmitted to the non-AP MLD through the previously established first link.

[0168] Step 6b: The target AP MLD can send new downlink data to the non-AP MLD through the newly established second link.

[0169] Step 6c: The Non-AP MLD can send uplink data to the target AP MLD through the newly established second link.

[0170] Step 7 (corresponding to Example 14): After establishing a new second link between the Non-AP MLD and the target AP MLD, the first link with the current AP MLD can be disconnected. Then, the non-AP MLD can send a disconnect request to the current AP MLD on the first link, indicating that it is disconnected from the current AP MLD and the first link is deleted.

[0171] Step 8 (corresponding to Example 14): After receiving the deassociation request sent by the non-AP MLD on the first link, the current AP MLD replies with a deassociation response, confirms the deassociation, and disconnects the first link with the non-AP MLD.

[0172] Through the above steps, the non-AP MLD completes the handover / roaming operation from the current AP MLD to the target AP MLD. It is worth noting that Figure 2C is only an example and does not represent the only process for implementing roaming.

[0173] The common core inventive point of the second and third solutions is that in each of the above steps, any device (non-AP MLD, current AP MLD, and target AP MLD) must consider its own NSTR capability and the NSTR capability of the peer device when transmitting and receiving on any link, so as to avoid simultaneous transmission and reception on the NSTR link pair.

[0174] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings:

[0175] Example 1: A method for Non-AP MLD to obtain non-master link information of target AP MLD.

[0176] For a non-AP MLD to roam / switch to a target AP MLD, it needs to know the target AP MLD's information in advance (e.g., functional elements, extended functional elements, and multi-link elements; see IEEE 802.11(be) series standards for details). The non-AP MLD determines its suitability as a target AP MLD based on the target AP MLD's information, its own capabilities, and operating parameters. If the target AP MLD is an NSTR mobile AP MLD, with the first link being the primary link and the second link being a non-primary link, then according to MLO rules, beacon and probe response frames cannot be sent on the second link. Therefore, the non-AP MLD cannot obtain the target AP MLD's information through the affiliated AP corresponding to the target AP MLD's second link. There are three solutions, see Figure 2D:

[0177] 1) Solution 1: Non-AP MLD receives beacon and probe response frames from the target AP MLD on the channel corresponding to the main link (i.e., the first link) of the target AP MLD, and learns information about the target AP MLD (such as functional elements, extended functional elements and multi-link elements, including information from non-main links).

[0178] 2) Solution 2: The current AP MLD receives beacon frames sent by the target AP MLD on the main link (i.e., the first link) carrying information about the target AP MLD (such as functional elements, extended functional elements, and multi-link elements, including information from the non-main link), and then sends it to the non-AP MLD through the interaction of roaming request / response and / or FT request / response (and / or (re)association request / response).

[0179] 3) Solution 3: The current AP MLD obtains information about the target AP MLD (such as functional elements, extended functional elements, and multi-link elements) through the backhaul link, including information about the non-primary link, and then sends it to the non-AP MLD through the interaction of roaming request / response and / or FT request / response (and / or (re)association request / response).

[0180] The advantage of this embodiment 1 is that when the target AP MLD is an NSTR mobile AP MLD, the non-AP MLD cannot obtain the capability information of the NSTR mobile AP MLD through its non-primary link, and therefore cannot know whether the target AP MLD is suitable as the destination AP MLD for handover. This embodiment 1 designs a method for the non-AP MLD to obtain the non-primary link information of the target AP MLD in various ways, providing the possibility for the non-AP MLD to roam to the target AP MLD that is an NSTR mobile AP MLD.

[0181] In the independent technical solution of this application, referring to FIG2D, in some embodiments, AP MLDs (e.g., between the current AP MLD and the target AP MLD) can exchange information about the MCS (Modulation and Coding Scheme) and / or channel bandwidth and / or Resource Unit (RU) size and / or Spatial Stream number used for data transmission via backhaul links or beacon frames (or other frames). This information, combined with the AP MLD's Buffer Status Report (BSR), can assist one AP MLD in calculating / estimating the data transmission time of another AP MLD. Therefore, when performing multi-AP cooperation, the calculated / estimated data transmission time can be used to share transmission resources (e.g., transmission duration, bandwidth used for transmission, etc.) with another AP MLD. Example 2: Design of transmit / receive status / time indication.

[0182] During the switchover of a non-AP MLD from the current AP MLD to the target AP MLD, roaming-related transmit / receive behaviors need to take into account the transmit / receive behaviors on the peer's NSTR link pair to avoid NSTR interference. To avoid NSTR, the device's transmit / receive status / time needs to be indicated. Upon receiving this indication, the peer can schedule transmit / receive times based on the indication, thereby avoiding NSTR. This functionality can be achieved in two ways:

[0183] 1) Option 1: Indicate the time of reception and transmission on each link.

[0184] The current AP MLD and the target AP MLD exchange transmit / receive status / time information on each link via the backhaul link. The non-AP MLD can obtain the transmit / receive status / time information on each link of the AP MLD through roaming request / response and / or FT request / response (and / or (re)association request / response) interactions. Specifically, this can be designed as the NSTR link transmit / receive (TX / RX) time indication element shown in Figure 3A, with the format and explanation as follows:

[0185] Number of Link Status: This indicates how many link status information the current NSTR link TX / RX time indicator element carries.

[0186] Status of Link 1 to n: This indicates information on the links 1 to n, including one or more of the following: link ID, main link tag, and transmission time indication.

[0187] Link ID: An identifier used to identify the link corresponding to the state of the m-th link (m is any value from 1 to n).

[0188] Primary Link Marker: Indicates whether the link corresponding to this link ID is a primary link of the current NSTR mobile AP MLD. If it is a primary link, the primary link mark is 1; if it is not a primary link, the primary link mark is 0, and vice versa.

[0189] Note: If the current AP MLD (e.g., the current AP MLD or the target AP MLD) is not an NSTR mobile AP MLD, the main link tag field does not exist.

[0190] Transmission Time Indication (TX Time Indication): Used to indicate the transmission time information on the link corresponding to the current link ID, specifically including one or more of the following information:

[0191] Number of TX: Indicates the timing of frame transmission for the link corresponding to the current link ID.

[0192] TX Start Time (1st to xth transmissions): Indicates the start time of the first to xth transmissions of the link corresponding to the current link ID.

[0193] TX Duration (1 to x): Indicates the duration of the first to xth transmission frames of the link corresponding to the current link ID.

[0194] Note: The start time and duration of the transmission together indicate the time of a transmission action.

[0195] The advantage of option 1 is that the above units can indicate the transmission and reception time on each link of MLD, so the frame interaction during roaming can avoid the NSTR link transmitting and receiving to the corresponding link at the same time.

[0196] 2) Option 2: Indicate the time window during which roaming operations are allowed.

[0197] Specifically, it can be designed as the roaming window indicator element shown in Figure 3B, with the following format and explanation:

[0198] Number of Link Status: Indicates how many links' roaming window information the current roaming window indicator element carries.

[0199] Status of Link 1 to n: This indicates the roaming window information on the links 1 to n, specifically including one or more of the following: Link ID, Main Link Marker, Roaming Window.

[0200] Link ID: An identifier used to mark the link corresponding to the state of the m-th link (m is any value from 1 to n).

[0201] Primary Link Marker: Indicates whether the link corresponding to this link ID is a primary link of the current NSTR mobile AP MLD. If it is a primary link, the primary link mark is 1; if it is not a primary link, the primary link mark is 0, and vice versa.

[0202] Note: If the current AP MLD (e.g., the current AP MLD or the target AP MLD) is not an NSTR mobile AP MLD, the main link tag field does not exist.

[0203] Roaming Window: This indicates the time window information allowed for roaming-related frame interactions on the link corresponding to the current link ID. Specifically, it includes one or more of the following:

[0204] Number of Window: Indicates the number of time windows in which roaming-related frame interactions can occur for the link corresponding to the current link ID.

[0205] Start Time of Window 1 to x: This indicates the start time of the time window during which roaming transmission and reception are allowed for the link corresponding to the current link ID in windows 1 to x.

[0206] Duration of Window 1 to x: This indicates the duration of the time windows during which roaming transmission and reception are allowed on the link corresponding to the current link ID.

[0207] Note: The start time and duration of a window together constitute a time window.

[0208] The advantage of option 2 is that the above unit can indicate the time window for sending and receiving roaming-related frames on each link of the MLD. Then, the frame interaction during roaming can only be carried out within the indicated time window. During this time window, each link can receive roaming-related frames at any time, and other operations unrelated to roaming are suspended, thus avoiding simultaneous sending and receiving of corresponding links by NSTR links.

[0209] Example 3: NSTR design for roaming requests / responses.

[0210] This corresponds to steps 1 and 2 in Figure 2B. Initially, the non-AP MLD establishes a first link with the current AP MLD, enabling data transmission and reception. When the non-AP MLD needs to switch from the current AP MLD to the target AP MLD due to movement (or other reasons), steps 1 and 2 of the roaming process are performed via link reconfiguration as follows:

[0211] Step 1 (corresponding to Example 3): The non-AP MLD (using the first link) initiates a roaming request to the current AP MLD, and can also be used to request information about candidate AP MLDs.

[0212] Step 2 (corresponding to Example 3): The current AP MLD (on the first link) replies with a roaming response, allowing / rejecting the roaming request from the non-AP MLD, and may also carry information about the candidate AP MLDs recommended by the current AP MLD. The non-AP MLD can select a suitable AP MLD as the target AP MLD from the candidate AP MLDs.

[0213] As shown in Figure 4, when a non-AP MLD needs to switch AP MLDs, it sends a roaming request to the current AP MLD on the first link. If the non-AP MLD is an NSTR device, then the constraints / rules for the non-AP MLD initiating the roaming request to the current AP MLD and the current AP MLD replying with a roaming response must satisfy the requirements described in IEEE 802.11be standard 35.3.16.4 NSTR operation. That is, the following conditions must be met:

[0214] 1) Condition 1: A non-AP MLD can only initiate a roaming request on the first link if there is no receiving activity on a link other than the first link (i.e., the second link).

[0215] 2) Condition 2: When the current AP MLD replies to the roaming response on the first link, it must satisfy the condition that the non-AP MLD has no transmitting behavior on the link outside the first link (i.e., the second link).

[0216] The methods / actions to achieve condition 2 are as follows:

[0217] When a non-AP MLD sends a roaming request to the current AP MLD, it may include the transmit / receive status / time indication described in Example 2. Upon receiving the roaming request, the current AP MLD can then ascertain the transmit / receive status / time on each link of the non-AP MLD. Therefore, when responding to a roaming response on the first link, it can choose to wait until the non-AP MLD has no ongoing transmission activity on a link other than the first link (i.e., the second link) before sending the roaming response. The first and second links of the non-AP MLD are an NSTR link pair.

[0218] The benefits of this embodiment 3 are as follows: Through the above behavioral design / restriction, the non-AP MLD is made to comply with the NSTR specification on the NSTR link pair (i.e., the first link and the second link), which avoids invalid conditions for the non-AP MLD and / or the current AP MLD to attempt to initiate roaming, improves the success rate, and also reduces roaming latency to a certain extent.

[0219] Example 4: NSTR design when a non-AP MLD sends a link reconfiguration request.

[0220] Corresponding to step 3 in Figure 2B (corresponding to embodiment 4): The non-AP MLD (using its associated STA) initiates a link reconfiguration request to the target AP MLD (via a link reconfiguration request frame or via an FT request frame) to request the establishment of a new link (e.g., a second link).

[0221] As shown in Figure 5, after the non-AP MLD receives the roaming response from the current AP MLD, if it is allowed to switch to the target AP MLD and establish a new link, then the non-AP MLD can initiate a link reconfiguration request (LRReq) to the target AP MLD.

[0222] Considering that if the non-AP MLD is the MLD of the NSTR, then the time when it sends the link reconfiguration request needs to meet condition 3: the non-AP MLD has no receiving behavior on the link other than the link that initiated the link reconfiguration request (i.e., the second link) (i.e., the first link).

[0223] If the target AP MLD is an NSTR mobile AP MLD, then in addition to condition 3 above, the non-AP MLD must also meet condition 4 when sending the link reconfiguration request: there is no ongoing transmission on the link other than the link where the target AP MLD receives the link reconfiguration request (i.e., the second link) (i.e., the first link).

[0224] The methods / actions to achieve condition 4 are as follows:

[0225] The current AP MLD may obtain the transmit / receive status / time indications of each link of the target AP MLD through methods such as backhaul links or receiving beacon frames from the target AP MLD. Then, after the non-AP MLD sends a roaming request to the current AP MLD, the current AP MLD will reply with a roaming response on the first link. This roaming response can also carry the transmit / receive status / time indications of each link of the target AP MLD. Therefore, the non-AP MLD can use the transmit / receive status / time indications of each link of the target AP MLD to select a link reconfiguration request to be sent only when there is no ongoing transmission activity on a link other than the link where the target AP MLD receives the link reconfiguration request (i.e., the second link).

[0226] Example of step 3: Figure 5 provides a simplified design for conditions 3 and 4 above. When the non-AP MLD successfully receives the roaming response from the current AP MLD on the first link, there is no receiving behavior on the non-AP MLD's first link. However, the target AP MLD is still transmitting on its first link. Considering that the target AP MLD is an NSTR mobile AP MLD, it cannot transmit on the first link and receive on the second link at the same time. Therefore, the non-AP MLD needs to wait for the target AP MLD to finish transmitting on the first link, and then, after a gap (e.g., an interval equal to SIFS, PIFS, etc.), initiate a link reconfiguration request to the target AP MLD's second link.

[0227] The advantages of this embodiment 4 are: through the aforementioned behavioral restrictions, the non-AP MLD is made to conform to the NSTR specification on the NSTR link pair (i.e., the first link and the second link), and the target AP MLD is also made to conform to the NSTR specification on the NSTR link pair (i.e., the first link and the second link). Furthermore, it avoids invalid conditions that would cause the non-AP MLD to attempt to initiate a link reconfiguration request, improving the success rate and reducing roaming latency to some extent.

[0228] Example 5: NSTR design when the target AP MLD responds to the link reconfiguration response.

[0229] Corresponding to step 5 in Figure 2B (corresponding to Example 5): The target AP MLD sends a link reconfiguration response to the non-AP MLD on the second link. If the target AP MLD agrees to the non-AP MLD's link reconfiguration request and establishes a new second link, then the second link between the non-AP MLD and the target AP MLD is established. As shown in Figure 5, after receiving the link reconfiguration request from the non-AP MLD, the target AP MLD needs to reply with a link reconfiguration response (LRResp) to the non-AP MLD. The link reconfiguration response can also carry information that the new link has been established.

[0230] If the target AP MLD is an NSTR mobile AP MLD, then the target AP MLD must meet condition 5 when replying to the link reconfiguration response: there is no receiving activity on the link other than the link that sent the link reconfiguration response (i.e., the second link) (i.e., the first link).

[0231] Considering that if the non-AP MLD is the MLD of the NSTR, then in addition to the above condition 5, the time when the target AP MLD replies to the link reconfiguration response also needs to meet condition 6: the non-AP MLD is not transmitting on the link other than the link receiving the link reconfiguration response (i.e., the second link) (i.e., the first link).

[0232] The methods / actions to achieve condition 6 are as follows:

[0233] When a non-AP MLD sends a link reconfiguration request to a target AP MLD, it may carry the transmit / receive status / time indication described in Example 2. After receiving the link reconfiguration request, the target AP MLD can know the transmit / receive status / time on each link of the non-AP MLD. Therefore, when replying to the link reconfiguration response on the second link, it can choose to send the link reconfiguration response only when the non-AP MLD has no transmitting activity on a link other than the second link (i.e., the first link).

[0234] The benefits of this embodiment 5 are as follows: Through the aforementioned behavioral restrictions, the target AP MLD is made to conform to the NSTR specification on the NSTR link pair (i.e., the first link and the second link), and the non-AP MLD is also made to conform to the NSTR specification on the NSTR link pair (i.e., the first link and the second link). Furthermore, it avoids invalid conditions that would cause the target AP MLD to attempt to respond to link reconfiguration responses, thus improving the success rate and reducing roaming latency to some extent.

[0235] Example 6: NSTR design during context transition.

[0236] This corresponds to step 4 in Figure 2B. Step 4 (corresponding to Example 6): After receiving the link reconfiguration request from the non-AP MLD, the target AP MLD will request the context of the non-AP MLD from the current AP MLD through the backhaul link to perform context transfer in preparation for roaming.

[0237] As shown in Figure 6, after the current AP MLD or the target AP MLD learns of the handover request from the non-AP MLD, it can initiate a context request to the other party. The other party replies with a context response to complete the context transfer. It is worth noting that step 4 can occur at any time before step 6 shown in Figure 2B.

[0238] Based on the different types of backhaul links between AP MLDs (i.e., the current AP MLD and the target AP MLD), as shown in Figure 6, context transfer methods can be divided into two categories:

[0239] Option 1: If there is a dedicated backhaul link between AP MLDs (e.g., a wired link or an out-of-band wireless link dedicated to backhaul and not used as a service non-AP MLD), then context transfer between AP MLDs can be performed at any time without considering the NSTR restrictions of both parties or whether other transmission / reception activities are in progress.

[0240] Option 2: If the backhaul link between AP MLDs uses a conventional in-band wireless link serving non-AP MLDs (e.g., the first link), then the following conditions / restrictions must be met when AP MLDs perform context transfer:

[0241] Condition 7: When the AP MLD initiates a context request on the backhaul link (e.g., the first link), none of its other links (e.g., the second link) are currently receiving data. Note: This condition 7 does not apply if the AP MLD initiating the context request is a device with STR capability.

[0242] Condition 8: And there is no ongoing transmission activity on any link other than the backhaul link of the peer AP MLD. For example, as shown in Figure 6, if the target AP MLD is an NSTR mobile AP MLD, then the current AP MLD needs to wait for the target AP MLD to complete its current transmission activity (i.e., TX time (to other STAs)) on the second link, followed by the duration of the gap (e.g., the gap equal to SIFS, PIFS, etc.), before it can send a context request to the target AP MLD on the first link. Note: If the AP MLD receiving the context request is an STR-capable device, then this condition 8 does not apply.

[0243] The methods / actions to achieve condition 8 are as follows:

[0244] The current AP MLD and the target AP MLD may obtain the transmit / receive status / time indication information (i.e., the information designed in Implementation #2) of each other's links by receiving beacon frames sent by the other party. Then, one AP MLD (e.g., the current AP MLD) can select to send a context request when there is no transmitting activity on other links besides the backhaul link of the other AP MLD, based on the aforementioned transmit / receive status / time indication information of each link of the other party.

[0245] The conditions / restrictions for AP MLD to respond to the context response under option 2 are the same as those for sending the context request described in option 2, and will not be repeated here.

[0246] The benefits of this embodiment 6 are as follows: By restricting the behavior as described above, the target AP MLD is made to conform to the NSTR specification on the NSTR link pair (i.e., the first link and the second link), which avoids invalid conditions for the current AP MLD and / or the target AP MLD to attempt to perform context transfer, improves the success rate, and also reduces roaming latency to some extent.

[0247] Example 7: NSTR Design in the Data Transmission Phase

[0248] This corresponds to steps 6a, 6b, and 6c in Figure 2B. Step 6 (corresponding to Example 7): This mainly involves data transmission between the non-AP MLD and the current AP MLD and / or the target AP MLD; specifically, it consists of 3 operations (the operations are not in any particular order, and only some of them may be performed):

[0249] Step 6a: Downlink data buffered by the current AP MLD for the non-AP MLD can continue to be transmitted to the non-AP MLD through the previously established first link.

[0250] Step 6b: The target AP MLD can send new downlink data to the non-AP MLD through the newly established second link.

[0251] Step 6c: The Non-AP MLD can send uplink data to the target AP MLD through the newly established second link.

[0252] As shown in Figure 7, after establishing a new link (i.e., the second link) between the non-AP MLD and the target AP MLD through the preceding steps, the non-AP MLD can receive data sent by the target AP MLD on the new link (i.e., the second link) (corresponding to step 6b), and the non-AP MLD can also send data to the target AP MLD on the new link (i.e., the second link) (corresponding to step 6c). Before the non-AP MLD disconnects the old link (i.e., link 1) from the current AP MLD, the non-AP MLD can continue to receive data cached by the current AP MLD on the old link (i.e., the first link) (corresponding to step 6a). As mentioned above, this patent does not limit the order in which steps 6a, 6b, and 6c occur, nor does it require all steps 6a, 6b, and 6c to be executed. The specific steps to be executed and their order are product implementation issues and are determined by business requirements.

[0253] 1) For step 6a, if the current AP MLD is a STR MLD, then when it sends the buffered downlink data to the non-AP MLD on the first link, it needs to meet condition 9: the non-AP MLD has no sending behavior on the link outside the first link (i.e., the second link).

[0254] The methods / actions to achieve condition 9 are as follows:

[0255] In step 1 (or other steps) shown in Figure 2B, when a non-AP MLD sends a roaming request to the current AP MLD, it may carry transmit / receive status / time indication information for its various links. Therefore, the current AP MLD can select, based on this information, to send data only when there is no ongoing transmission activity on other links (i.e., the second link) besides the non-AP MLD's first link.

[0256] 2) For step 6b, if the target AP MLD is an NSTR mobile AP MLD, then the timing of the target AP MLD sending downlink data to the non-AP MLD on the second link must satisfy condition 10: there is no receiving activity on the link other than the link through which the target AP MLD sends downlink data (i.e., the second link) (i.e., the first link). Considering that if the non-AP MLD is an NSTR MLD, then in addition to the above condition 10, the timing of the target AP MLD sending downlink data also needs to satisfy condition 11: the non-AP MLD has no sending activity on the link other than the link through which it receives downlink data (i.e., the second link) (i.e., the first link).

[0257] The methods / actions to achieve condition 11 are as follows:

[0258] In step 3 (or other steps) shown in Figure 2B, when the non-AP MLD sends a link reconfiguration request to the target AP MLD, it may carry transmit / receive status / time indication information for each of its own links. Therefore, the target AP MLD can select, based on this information, to send data only when there is no ongoing transmission activity on other links (i.e., the first link) besides the second link where the non-AP MLD receives downlink data.

[0259] For example, in step 6b as shown in Figure 7, when the target AP MLD is preparing to send downlink data to the non-AP MLD on the second link, it cannot send downlink data to the non-AP MLD on the second link because the target AP MLD is receiving frames / data from other non-AP MLDs / STAs on the first link. This is due to the limitation of NSTR capability. The target AP MLD must wait until the receiving behavior on the first link of the target AP MLD is completed, and then wait for the interval gap (e.g., the interval is equal to SIFS, PIFS, etc.) before the target AP MLD can send downlink data to the non-AP MLD on the second link.

[0260] 3) For step 6c, if the non-AP MLD is an NSTR MLD, then the time when it sends uplink data needs to satisfy condition 12: the non-AP MLD has no receiving activity on a link other than the link initiating the uplink data (i.e., the second link) (i.e., the first link). Considering that if the target AP MLD is an NSTR mobile AP MLD, then in addition to the above condition 12, the time when the non-AP MLD sends uplink data to the target AP MLD on the second link also needs to satisfy condition 13: there is no sending activity on a link other than the link where the target AP MLD receives the non-AP MLD's uplink data (i.e., the second link) (i.e., the first link).

[0261] The methods / actions to achieve condition 13 are as follows:

[0262] In step 5 (or other steps) shown in Figure 2B, when the target AP MLD sends a link reconfiguration response to the non-AP MLD, it may carry transmit / receive status / time indication information for each of its own links. Therefore, the non-AP MLD can select, based on this information, to send data only when there is no ongoing transmission activity on other links (i.e., the first link) besides the second link where the target AP MLD receives uplink data.

[0263] For example, in step 6c as shown in Figure 7, when the non-AP MLD is preparing to send uplink data to the target AP MLD on the second link, since the target AP MLD is sending frames / data to other non-AP MLDs / STAs on the first link, the non-AP MLD cannot send uplink data to the target AP MLD on the second link due to the limitation of the target AP MLD's NSTR capability. It needs to wait until the target AP MLD's transmission behavior on the first link is completed, and then wait for a gap duration (e.g., the gap is equal to SIFS, PIFS, etc.) before the non-AP MLD can send uplink data to the target AP MLD on the second link.

[0264] The advantages of this embodiment 7 are as follows: Through the aforementioned behavioral restrictions, the non-AP MLD conforms to the NSTR specification on the NSTR link pair (i.e., the first link and the second link), and the (target) AP MLD also conforms to the NSTR specification on the NSTR link pair (i.e., the first link and the second link). Furthermore, it avoids invalid conditions that would prevent data transmission between the non-AP MLD and the current AP MLD, as well as between the non-AP MLD and the target AP MLD, thus improving the success rate and reducing roaming latency to some extent.

[0265] Example 8: NSTR Design for Disconnecting from the Current AP MLD

[0266] Corresponding to steps 7 and 8 in Figure 2B, step 7 (corresponding to embodiment 8): After establishing a new second link between the Non-AP MLD and the target AP MLD, the first link with the current AP MLD can be disconnected. Then, the non-AP MLD can send a link reconfiguration request to the current AP MLD on the first link, instructing that the first link be deleted. Step 8 (corresponding to embodiment 8): After receiving the link reconfiguration request from the non-AP MLD on the first link, the current AP MLD replies with a link reconfiguration response, confirming the disconnection of the first link with the non-AP MLD.

[0267] The rules for link reconfiguration requests and responses between the Non-AP MLD and the current AP MLD are designed in the same way as in Example 3. For example, the roaming request and roaming response in Figure 2B are replaced with link reconfiguration requests and link reconfiguration responses, respectively. Specific details will not be repeated here.

[0268] The embodiments 1-8 above describe the design of each step in Solution 2: MLO-based roaming. Embodiments 9-15 below will design the steps in Solution 3: FT-based roaming. Since most of the signaling processes in Solution 2 and Solution 3 are identical, the related embodiment designs are also similar and will be briefly described in Embodiments 9-15 below. Embodiments 9-15 below provide detailed designs for the differing steps.

[0269] Example 9: NSTR design for FT request / response.

[0270] This corresponds to steps 1 and 2 in Figure 2B. The rule design for FT requests and FT responses between the Non-AP MLD and the current AP MLD is consistent with that in Example 3, for example, replacing the roaming request and roaming response in Figure 2B with FT requests and FT responses, respectively. Specific details will not be elaborated further.

[0271] The difference between Example 9 and Example 3 is that in Example 9, after the current AP MLD receives an FT request from a non-AP MLD, it needs to send the FT request to the target AP MLD via the backhaul link. Then, the target AP MLD responds with an FT response to the current AP MLD via the backhaul link. The rules for the interaction of FT requests and FT responses between the current AP MLD and the target AP MLD (via the backhaul link) can be referenced from Example 6. For example, the context request and context response in Figure 6 can be replaced with FT requests and FT responses, respectively. Specific details will not be elaborated further.

[0272] The benefits of this embodiment 9 are as follows: Through the above behavioral design / restriction, the non-AP MLD is made to comply with the NSTR specification on the NSTR link pair (i.e., the first link and the second link), which avoids invalid conditions for the non-AP MLD and / or the current AP MLD to attempt to initiate roaming through FT request / response, improves the success rate, and also reduces roaming latency to a certain extent.

[0273] Example 10: NSTR design when a non-AP MLD sends a reassociation request.

[0274] Corresponding to step 3 in Figure 2B: The non-AP MLD (using its associated STA) initiates a link reconfiguration request to the target AP MLD (via a link reconfiguration request frame or via an FT request frame) to request the establishment of a new link (e.g., a second link).

[0275] As shown in Figure 8, the difference between this embodiment 10 and embodiment 4 is that if the target AP MLD is an NSTR mobile AP MLD, then a reassociation request from a non-AP MLD will be received on the main link (i.e., the first link) (correspondingly, the target AP MLD replies with a reassociation response to the non-AP MLD on the main link (i.e., the first link).

[0276] Considering that if the non-AP MLD is an MLD of the NSTR, then the time when it sends the reassociation request needs to meet condition 14: the non-AP MLD has no receiving activity on a link other than the link that initiated the reassociation request (i.e., the first link) (i.e., the second link).

[0277] Since the target AP MLD is an NSTR mobile AP MLD, in addition to the above condition 14, the non-AP MLD must also meet condition 15 when sending the reassociation request: there is no sending activity on the link other than the link where the target AP MLD receives the reassociation request (i.e., the first link) (i.e., the second link).

[0278] The methods / actions to achieve condition 15 are as follows:

[0279] The current AP MLD may obtain the transmit / receive status / time indications of each link of the target AP MLD through methods such as backhaul links, FT interactions, or receiving beacon frames from the target AP MLD. Then, after the non-AP MLD sends an FT request to the current AP MLD, the current AP MLD will reply with an FT response on the first link. This FT response can also carry the transmit / receive status / time indications of each link of the target AP MLD. Therefore, the non-AP MLD can use the transmit / receive status / time indications of each link of the target AP MLD to select a link other than the link where the target AP MLD receives the reassociation request (i.e., the first link) to send a reassociation request when there is no ongoing transmission activity.

[0280] For example, in step 3, the non-AP MLD (using its associated STA) initiates a link reconfiguration request to the target AP MLD (via a link reconfiguration request frame or an FT request frame) to request the establishment of a new link (e.g., a second link).

[0281] Figure 8 provides a simplified design for conditions 14 and 15 above. When the non-AP MLD successfully receives the FT response from the current AP MLD on the first link, there is no receiving activity on the non-AP MLD's first link. However, the target AP MLD is still transmitting on its second link. Considering that the target AP MLD is an NSTR mobile AP MLD, it cannot transmit on the second link while simultaneously receiving on the first link. Therefore, the non-AP MLD needs to wait for the target AP MLD to finish transmitting on the second link, and then, after a gap (e.g., a gap equal to SIFS, PIFS, or other durations), initiate a reassociation request to the target AP MLD's first link.

[0282] The advantages of this embodiment 10 are: through the aforementioned behavioral restrictions, the non-AP MLD is made to conform to the NSTR specification on the NSTR link pair (i.e., the first link and the second link), and the target AP MLD is also made to conform to the NSTR specification on the NSTR link pair (i.e., the first link and the second link). Furthermore, it avoids invalid conditions that would cause the non-AP MLD to attempt to initiate a re-association request, improving the success rate and reducing roaming latency to some extent.

[0283] Example 11: NSTR design when the target AP MLD responds to the reassociation response.

[0284] In step 5 of Figure 2B: The target AP MLD sends a link reconfiguration response to the non-AP MLD on the second link. If the target AP MLD agrees to the non-AP MLD's link reconfiguration request and establishes a new second link, then the establishment of the second link between the non-AP MLD and the target AP MLD is complete.

[0285] As shown in Figure 8, the difference between this embodiment 11 and embodiment 5 is that if the target AP MLD is an NSTR mobile AP MLD, since it receives the reassociation request from the non-AP MLD on the main link (i.e., the first link), the target AP MLD will correspondingly reply with a reassociation response to the non-AP MLD on the main link (i.e., the first link).

[0286] Given that the target AP MLD is an NSTR mobile AP MLD, the moment when the target AP MLD replies with a reassociation response must meet condition 16: there is no receiving activity on the link other than the link where the target AP MLD sent the reassociation response (i.e., the first link) (i.e., the second link).

[0287] If the non-AP MLD is the MLD of the NSTR, then in addition to condition 16 above, the time when the target AP MLD responds to the reassociation response also needs to meet condition 17: the non-AP MLD is not sending any data on a link other than the link that received the reassociation response (i.e., the first link) (i.e., the second link).

[0288] The methods / actions to achieve condition 17 are as follows:

[0289] When a non-AP MLD sends a reassociation request to a target AP MLD, it may carry the transmit / receive status / time indication as described in Example #2. After receiving the reassociation request, the target AP MLD can know the transmit / receive status / time on each link of the non-AP MLD. Therefore, when the target AP MLD replies to the reassociation response, it can choose to send the reassociation response only when there is no transmitting activity on the link other than the first link on which the non-AP MLD received the reassociation response (i.e., the second link).

[0290] The advantages of this embodiment 11 are: through the aforementioned behavioral restrictions, the target AP MLD is made to conform to the NSTR specification on the NSTR link pair (i.e., the first link and the second link), and the non-AP MLD is also made to conform to the NSTR specification on the NSTR link pair (i.e., the first link and the second link). Furthermore, it avoids invalid conditions that would cause the target AP MLD to attempt to respond with a re-association response, thus improving the success rate and reducing roaming latency to some extent.

[0291] Example 12: NSTR design during context transition.

[0292] Corresponding to step 4 in Figure 2B: After receiving the link reconfiguration request from the non-AP MLD, the target AP MLD will request the context of the non-AP MLD from the current AP MLD through the backhaul link to perform context transfer in preparation for roaming.

[0293] The rules for context requests and context responses between the Non-AP MLD and the current AP MLD are designed in the same way as in Example 6, and the specific details will not be repeated here.

[0294] The benefits of this embodiment 12: see the explanation of the benefits of embodiment 6.

[0295] Example 13: NSTR design for the data transmission phase.

[0296] This corresponds to steps 6a, 6b, and 6c in Figure 2B. Step 6a: Downlink data buffered by the current AP MLD for the non-AP MLD can continue to be transmitted to the non-AP MLD via the previously established first link. Step 6b: The target AP MLD can send new downlink data to the non-AP MLD via the newly established second link. Step 6c: The non-AP MLD can send uplink data to the target AP MLD via the newly established second link.

[0297] The rules for uplink and downlink data between the non-AP MLD and the target AP MLD, as well as the downlink data sent by the current AP MLD to the non-AP MLD, are designed in the same way as in Example 7, and the specific details will not be repeated here.

[0298] The benefits of this embodiment 13: see the explanation of the benefits in embodiment 7.

[0299] Example 14: Decouple the NSTR design from the current AP MLD phase.

[0300] Corresponding to steps 7 and 8 in Figure 2B, step 7: After establishing a new second link between the Non-AP MLD and the target AP MLD, the first link with the current AP MLD can be disconnected. The non-AP MLD can then send a link reconfiguration request to the current AP MLD on the first link, instructing that the first link be deleted. Step 8: After receiving the link reconfiguration request from the non-AP MLD on the first link, the current AP MLD replies with a link reconfiguration response, confirming the disconnection of the first link with the non-AP MLD.

[0301] The rules for deassociation requests and responses between Non-AP MLDs and the current AP MLDs are designed in the same way as in Examples 3 and 8. For example, the roaming requests and roaming responses in Figure 4 are replaced with deassociation requests and deassociation responses, respectively. Specific details will not be repeated here.

[0302] Example 15: Physical layer Protocol Data Unit (PPDU) end-time alignment design, applicable to Solution 2 and Solution 3.

[0303] Considering that links are established between the non-AP MLD and both the current AP MLD and the target AP MLD, the non-AP MLD, acting as an NSTR MLD, can simultaneously receive downlink frames (including control frames, management frames, and data frames) sent by the current AP MLD and the target AP MLD on different links, but the following conditions must be met:

[0304] When the current AP MLD and the target AP MLD need to align the end times of simultaneously transmitted PPDUs, the following conditions should be met:

[0305] The current AP MLD and the target AP MLD should ensure that the time difference between the end of the PPDU transmitted simultaneously is less than or equal to 8 microseconds, where the end time of the PPDU is the end time of the last OFDM symbol or the end time of the packet extension (if any), whichever is later.

[0306] The current AP MLD and the target AP MLD should ensure that the end time of one or more PPDUs carrying a request for an immediate response frame is at most 4 microseconds earlier than the end time of any PPDU of a trigger frame containing a subfield of the CS requirement set to 1.

[0307] For example (using a data frame as an example): As shown in Figure 7, if step 6a (i.e., the current AP MLD sends downlink buffered data to the non-AP MLD through the first link) and step 6b (the target AP MLD sends downlink data to the non-AP MLD through the second link) are performed simultaneously, since the non-AP MLD is the MLD of the NSTR, the end times of the PPDUs sent by the current AP MLD and the target AP MLD on the two links (belonging to the NSTR link pair) must be aligned.

[0308] The specific definition of alignment: When the current AP MLD and the target AP MLD need to align the end times of PPDUs transmitted simultaneously, the following conditions should be met:

[0309] The current AP MLD and the target AP MLD should ensure that the time difference between the end of the PPDU transmitted simultaneously is less than or equal to 8 microseconds, where the end time of the PPDU is the end time of the last OFDM symbol or the end time of the packet extension (if any), whichever is later.

[0310] The current AP MLD and the target AP MLD should ensure that the end time of one or more PPDUs carrying a request for an immediate response frame is at most 4 microseconds earlier than the end time of any PPDU of a trigger frame containing a subfield of the CS requirement set to 1.

[0311] The advantage of this embodiment 15 is that the device acting as an NSTR MLD can transmit or receive simultaneously on multiple links, without waiting for reception to complete on one link before receiving on another, or waiting for transmission to complete on one link before transmitting on another. This saves signaling interaction time and reduces roaming latency.

[0312] Figure 9 is a schematic structural diagram of a wireless communication device 500 provided in an embodiment of this application. This wireless communication device can be a relay communication device, an access point (AP), or a standby station (STA). The wireless communication device 500 shown in Figure 9 includes a processor 510, which can call and run computer programs from memory to implement the methods in the embodiments of this application. In some embodiments of this application, the AP includes an AP STA or an AP MLD, and the STA includes an AP STA or a non-AP STA or an AP MLD or a non-AP MLD.

[0313] Optionally, as shown in FIG9, the wireless communication device 500 may further include a memory 520. The processor 510 can retrieve and run computer programs from the memory 520 to implement the methods in the embodiments of this application. The memory 520 may be a separate device independent of the processor 510, or it may be integrated into the processor 510.

[0314] Optionally, as shown in Figure 9, the wireless communication device 500 may further include a transceiver 530. The processor 510 can control the transceiver 530 to communicate with other devices. Specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include an antenna, and the number of antennas may be one or more.

[0315] Optionally, the wireless communication device 500 may specifically be a relay communication device in the embodiments of this application, and the wireless communication device 500 may implement the corresponding processes implemented by the relay communication device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0316] Optionally, the wireless communication device 500 may specifically be a mobile AP in the embodiments of this application, and the wireless communication device 500 may implement the corresponding processes implemented by the AP in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0317] Optionally, the wireless communication device 700 may specifically be a STA in the embodiments of this application, and the wireless communication device 700 may implement the corresponding processes implemented by the STA in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here. In some embodiments of this application, the STA includes an AP STA or a non-AP STA or an AP MLD or a non-AP MLD.

[0318] Figure 10 is a schematic structural diagram of a chip according to an embodiment of this application. The chip 600 shown in Figure 10 includes a processor 610, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0319] Optionally, as shown in FIG10, chip 600 may further include memory 620. Processor 610 can call and run computer programs from memory 620 to implement the methods in the embodiments of this application. Memory 620 may be a separate device independent of processor 610, or it may be integrated into processor 610.

[0320] Optionally, the chip 600 may also include an input interface 630. The processor 610 can control the input interface 630 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0321] Optionally, the chip 600 may also include an output interface 640. The processor 610 can control the output interface 640 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0322] Optionally, the chip can be applied to the relay communication device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the relay communication device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0323] Optionally, the chip can be applied to the AP in the embodiments of this application, and the chip can implement the corresponding processes implemented by the AP in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0324] Optionally, the chip can be applied to the STA in the embodiments of this application, and the chip can implement the corresponding processes implemented by the STA in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0325] Figure 11 is a schematic block diagram of a wireless communication device 700 provided in an embodiment of this application. As shown in Figure 11, the wireless communication device 700 includes an access point (AP) 710, a relay communication device 720, and a relay communication device (STA) 730. The AP 710 can be used to implement the corresponding functions implemented by the AP in the above method; the relay communication device 720 can be used to implement the corresponding functions implemented by the relay communication device in the above method; and the STA 730 can be used to implement the corresponding functions implemented by the STA in the above method. For simplicity, further details are omitted here.

[0326] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by software instructions.

[0327] It is understood that the memory in the embodiments of this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory. Embodiments of this application also provide a computer-readable storage medium for storing a computer program.

[0328] Optionally, the computer-readable storage medium can be applied to the relay communication device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the relay communication device in the various methods of the embodiments of this application. For simplicity, further details are omitted here. Optionally, the computer-readable storage medium can be applied to the AP in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the AP in the various methods of the embodiments of this application. For simplicity, further details are omitted here. Optionally, the computer-readable storage medium can be applied to the STA in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the STA in the various methods of the embodiments of this application. For simplicity, further details are omitted here.

[0329] This application also provides a computer program product, including computer program instructions.

[0330] Optionally, the computer program product can be applied to the relay communication device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the relay communication device in the various methods of the embodiments of this application. For simplicity, further details are omitted here. Optionally, the computer program product can be applied to the AP in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the AP in the various methods of the embodiments of this application. For simplicity, further details are omitted here. Optionally, the computer program product can be applied to the STA in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the STA in the various methods of the embodiments of this application. For simplicity, further details are omitted here.

[0331] This application also provides a computer program.

[0332] Optionally, the computer program can be applied to the relay communication device in the embodiments of this application. When the computer program runs on a computer, it causes the computer to execute the corresponding processes implemented by the relay communication device in the various methods of the embodiments of this application. For simplicity, this will not be described in detail here. Optionally, the computer program can be applied to the AP in the embodiments of this application. When the computer program runs on a computer, it causes the computer to execute the corresponding processes implemented by the AP in the various methods of the embodiments of this application. For simplicity, this will not be described in detail here. Optionally, the computer program can be applied to the STA in the embodiments of this application. When the computer program runs on a computer, it causes the computer to execute the corresponding processes implemented by the STA in the various methods of the embodiments of this application. For simplicity, this will not be described in detail here.

[0333] 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.

[0334] 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 multi-link roaming communication method, executed at a first site device, wherein, The communication method includes: Non-simultaneous transmission and reception on at least two links of a multi-link system, wherein the first site device, the second site device, and the third site device refer to the first site device being configured to switch to the second site device or be switched from the second site device to the third site device when the first site device is roaming.

2. The communication method according to claim 1, wherein, The communication method further includes: When the first site device roams, it determines the transmission time on at least one of the multiple links based on its own predictions.

3. The communication method according to claim 2, wherein, Determining the transmission time on at least one of the multiple links based on its own predictions includes: The first site device determines the transmission and reception time information on each link of the multi-link system based on its own prediction on the first link or the second link, wherein the first link and the second link are either links in the multi-link system.

4. The communication method according to claim 3, wherein, The communication method further includes: Based on the transmission and reception time information of the first site device on each of the multiple links, the transmission time of the first site device on the first link is staggered from the reception time of the first site device on the second link, or the reception time of the first site device on the first link is staggered from the transmission time of the first site device on the second link.

5. The communication method according to claim 2, wherein, The communication method further includes: When the first site device does not receive operations on one link of the multi-link system, the first site device performs a transmission operation on the other link of the multi-link system.

6. The communication method according to claim 2, wherein, The communication method further includes: When the second site device or the third site device does not transmit on one of the links of the multi-link, the first site device transmits a frame to the second site device or the third site device on the other link of the multi-link.

7. The communication method according to claim 1, wherein, The communication method further includes: The first site device confirms the transmit and receive time information on each link of the multi-link system on at least one of the multi-link systems.

8. The communication method according to claim 7, wherein, Confirming the transmit / receive time information of the first site device on each of the multiple links includes: The first site device confirms the transmit and receive time information on each link of the multi-link system on the first link or the second link, wherein the first link and the second link are either links in the multi-link system.

9. The communication method according to claim 8, wherein, The communication method further includes: Based on the transmission and reception time information of the first site device on each of the multiple links, the transmission time of the first site device on the first link is staggered from the reception time of the first site device on the second link, or the reception time of the first site device on the first link is staggered from the transmission time of the first site device on the second link.

10. The communication method according to claim 9, wherein, The communication method further includes: Based on the transmit and receive time information of the first site device on each link of the multi-link system, it is determined whether to send the first frame to the second site device on the first link.

11. The communication method according to claim 10, wherein, The first frame carries the transmission and reception time information of the first site device on each link.

12. The communication method according to claim 10, wherein, The communication method further includes: When the first site device does not receive operations on the second link, the first site device sends the first frame to the second site device on the first link.

13. The communication method according to claim 12, wherein, The first site device sends the first frame to the second site device on the first link within a predefined time window.

14. The communication method according to claim 10, wherein, The communication method further includes: When the first site device does not transmit on the second link, the first site device receives the second frame sent by the second site device on the first link.

15. The communication method according to claim 14, wherein, The first site device receives the second frame sent by the second site device on the first link within a predefined time window.

16. The communication method according to claim 14, wherein, The second frame carries the transmission and reception time information of the second site device on each link and / or the transmission and reception time information of the third site device on each link.

17. The communication method according to claim 1 or 7, wherein, The communication method further includes: Based on the transmit and receive time information of the first site device on each link of the multi-link system, or based on its own prediction, the first site device determines the transmission time on at least one link of the multi-link system, and confirms whether to send a third frame to the third site device on the second link.

18. The communication method according to claim 17, wherein, The third frame carries the transmission and reception time information of the first site device on each link.

19. The communication method according to claim 17, wherein, The communication method further includes: When the first site device does not receive operations on the first link, the first site device sends the third frame to the third site device on the second link.

20. The communication method according to claim 19, wherein, The first site device sends the third frame to the third site device on the second link within a predefined time window.

21. The communication method according to claim 17, wherein, The communication method further includes: When the first site device does not transmit on the first link, the first site device receives the fourth frame sent by the third site device on the second link.

22. The communication method according to claim 21, wherein, The first site device receives the fourth frame sent by the third site device on the second link within a predefined time window.

23. The communication method according to claim 21, wherein, The fourth frame carries the transmission and reception time information of the third site device on each link and / or the transmission and reception time information of the second site device on each link.

24. The communication method according to claim 7, wherein, The communication method further includes: When the first site device does not receive operations on one link of the multi-link system, the first site device performs a transmission operation on the other link of the multi-link system.

25. The communication method according to claim 7, wherein, The communication method further includes: When the second site device or the third site device does not transmit on one of the links of the multi-link, the first site device transmits a frame to the second site device or the third site device on the other link of the multi-link.

26. The communication method according to claim 1, wherein, The communication method further includes: The first site device receives a frame from the third site device on the channel corresponding to the main link of the third site device. The frame from the third site device carries information about the third site device, including information about the non-main link of the third site device.

27. The communication method according to claim 1, wherein, The communication method further includes: Simultaneously, the system receives first data sent by the second site device on the first link and second data sent by the third site device on the second link, wherein the end time of the first data and the end time of the second data are aligned.

28. A multi-link communication method, executed at a first site device, wherein, The communication method includes: Non-simultaneous transmission and reception on at least two links of a multi-link system, wherein the first site device receives a frame from the second site device on the channel corresponding to the primary link of the second site device, the frame of the second site device carrying information of the second site device, including information of the non-primary link of the second site device.

29. The communication method according to claim 28, wherein, The second site device is the target site device.

30. A multi-link communication method, executed at a first site device, wherein, The communication method includes: Non-simultaneous transmission and reception on at least two links of a multi-link system, wherein the first station device simultaneously receives first data transmitted by the second station device on the first link and second data transmitted by the third station device on the second link, wherein the end time of the first data and the end time of the second data are aligned.

31. A multi-link roaming communication method, executed at a second site device, wherein, The communication method includes: Non-simultaneous transmission and reception on at least two links of a multi-link system, wherein the first site device, the second site device, and the third site device refer to the first site device being configured to switch to the second site device or be switched from the second site device to the third site device when the first site device is roaming.

32. The communication method according to claim 31, wherein, The communication method further includes: When the second site device responds to the roaming of the first site device, it determines the transmission time on at least one of the multiple links based on its own predictions.

33. The communication method according to claim 32, wherein, Determining the transmission time on at least one of the multiple links based on its own predictions includes: The second site device determines the transmission and reception time information on each link of the multi-link system based on its own prediction on the first link or the second link, wherein the first link and the second link are either links in the multi-link system.

34. The communication method according to claim 33, wherein, The communication method further includes: Based on the transmission and reception time information of the second station device on each of the multiple links, the transmission time of the second station device on the first link is staggered from the reception time of the second station device on the second link, or the reception time of the second station device on the first link is staggered from the transmission time of the second station device on the second link.

35. The communication method according to claim 32, wherein, The communication method further includes: When the second site device does not receive operations on one link of the multi-link, the second site device performs a transmission operation on the other link of the multi-link.

36. The communication method according to claim 32, wherein, The communication method further includes: When the first site device or the third site device does not transmit on one of the links in the multi-link system, the second site device transmits a frame to the first site device or the third site device on the other link in the multi-link system.

37. The communication method according to claim 31, wherein, The communication method further includes: The second site device confirms the transmit and receive time information of each link in the multi-link system on at least one of the multi-link systems.

38. The communication method according to claim 37, wherein, Confirming the transmit / receive time information of the second site device on each of the multiple links in at least one of the multiple links includes: The second site device confirms the transmit and receive time information on each link of the multi-link system on the first link or the second link, wherein the first link and the second link are either links in the multi-link system.

39. The communication method according to claim 38, wherein, The communication method further includes: Based on the transmission and reception time information of the second station device on each of the multiple links, the transmission time of the second station device on the first link is staggered from the reception time of the second station device on the second link, or the reception time of the second station device on the first link is staggered from the transmission time of the second station device on the second link.

40. The communication method according to claim 39, wherein, The communication method further includes: Based on the transmit and receive time information of the second site device on each link of the multi-link system, it is determined whether the first frame sent by the first site device is received on the first link.

41. The communication method according to claim 40, wherein, The first frame carries the transmission and reception time information of the first site device on each link.

42. The communication method according to claim 41, wherein, The communication method further includes: When the second site device does not transmit on the second link, the second site device receives the first frame transmitted by the first site device on the first link.

43. The communication method according to claim 42, wherein, The second site device receives the first frame sent by the first site device on the first link within a predefined time window.

44. The communication method according to claim 41, wherein, The communication method further includes: When the second site device does not receive operations on the second link, the second site device sends a second frame to the first site device on the first link.

45. The communication method according to claim 44, wherein, The second site device sends the second frame to the first site device on the first link within a predefined time window.

46. ​​The communication method according to claim 44, wherein, The second frame carries the transmission and reception time information of the second site device on each link and / or the transmission and reception time information of the third site device on each link.

47. The communication method according to claim 31 or 44, wherein, The communication method further includes: Based on the transmit and receive time information of the second site device on each link of the multi-link system, or based on its own prediction, the second site device determines the transmission time on at least one link of the multi-link system, and confirms whether to send a third frame to the third site device on the second link.

48. The communication method according to claim 46, wherein, The third frame carries the transmission and reception time information of the second site device on each link.

49. The communication method according to claim 47, wherein, The communication method further includes: When the second site device does not receive operations on the first link, the second site device sends the third frame to the third site device on the second link.

50. The communication method according to claim 49, wherein, The second site device sends the third frame to the third site device on the second link within a predefined time window.

51. The communication method according to claim 47, wherein, The communication method further includes: When the second site device does not transmit on the first link, the second site device receives the fourth frame sent by the third site device on the second link.

52. The communication method according to claim 51, wherein, The second site device receives the fourth frame sent by the third site device on the second link within a predefined time window.

53. The communication method according to claim 51, wherein, The fourth frame carries the transmission and reception time information of the third site device on each link.

54. The communication method according to claim 37, wherein, The communication method further includes: When the second site device does not receive operations on one link of the multi-link, the second site device performs a transmission operation on the other link of the multi-link.

55. The communication method according to claim 37, wherein, The communication method further includes: When the first site device or the third site device does not transmit on one of the links in the multi-link system, the second site device transmits a frame to the first site device or the third site device on the other link in the multi-link system.

56. The communication method according to claim 31, wherein, The communication method further includes: The second site device receives a frame from the third site device on the channel corresponding to the main link of the third site device. The frame from the third site device carries information about the third site device, including information about the non-main link of the third site device.

57. The communication method according to claim 31, wherein, The communication method further includes: The second site device receives a frame from the third site device on the channel corresponding to the backhaul link of the third site device. The frame from the third site device carries information about the third site device, including information about the non-main link of the third site device.

58. The communication method according to claim 56 or 57, wherein, The communication method further includes: The second station device sends the information of the third station device to the first station device.

59. A multi-link communication method, executed at a second site device, wherein, The communication method includes: In a multi-link system, the second site device receives frames from the third site device on the channel corresponding to the main link of the third site device, and the frames of the third site device carry information about the third site device, including information about the non-main link of the third site device.

60. The communication method according to claim 59, wherein, The communication method further includes: The second station device sends the information of the third station device to the first station device.

61. A multi-link communication method, executed at a second site device, wherein, The communication method includes: Non-simultaneous transmission and reception on at least two links of a multi-link system, wherein the second station device receives a frame from the third station device on the channel corresponding to the backhaul link of the third station device, the frame of the third station device carrying information of the third station device, the information of the third station device including information of the non-primary link of the third station device.

62. The communication method according to claim 61, wherein, The communication method further includes: The second station device sends the information of the third station device to the first station device.

63. A multi-link roaming communication method, executed at a third-site device, wherein, The communication method includes: Non-simultaneous transmission and reception on at least two links of a multi-link system, wherein the first site device, the second site device, and the third site device refer to the first site device being configured to switch to the second site device or be switched from the second site device to the third site device when the first site device is roaming.

64. The communication method according to claim 63, wherein, The communication method further includes: When the third site device responds to the roaming of the first site device, it determines the transmission time on at least one of the multiple links based on its own prediction.

65. The communication method according to claim 64, wherein, Determining the transmission time on at least one of the multiple links based on its own predictions includes: The third site device determines the transmission and reception time information on each link of the multi-link system based on its own prediction on the first link or the second link, wherein the first link and the second link are either links in the multi-link system.

66. The communication method according to claim 65, wherein, The communication method further includes: Based on the transmit and receive time information of the second station device on each of the multiple links, the transmit time of the third station device on the first link is staggered from the receive time of the third station device on the second link, or the receive time of the third station device on the first link is staggered from the transmit time of the third station device on the second link. open.

67. The communication method according to claim 64, wherein, The communication method further includes: When the third station device does not receive operations on one link of the multi-link, the third station device performs a transmission operation on the other link of the multi-link.

68. The communication method according to claim 64, wherein, The communication method further includes: When the first site device or the second site device does not transmit on one of the links in the multi-link system, the third site device transmits a frame to the first site device or the second site device on the other link in the multi-link system.

69. The communication method according to claim 63, wherein, The communication method further includes: The third site device confirms the transmit and receive time information of each link in the multi-link system on at least one of the multi-link systems.

70. The communication method according to claim 69, wherein, Confirming the transmit / receive time information of the third site device on each of the multiple links includes: The third station device confirms the transmit and receive time information on each link of the multi-link system on either the first link or the second link, wherein the first link and the second link are either links in the multi-link system.

71. The communication method according to claim 70, wherein, The communication method further includes: Based on the transmission and reception time information of the third station device on each link of the multi-link, the transmission time of the third station device on the first link is staggered from the reception time of the third station device on the second link, or the reception time of the third station device on the first link is staggered from the transmission time of the third station device on the second link.

72. The communication method according to claim 71, wherein, The communication method further includes: Based on the transmission and reception time information of the third site device on each link of the multi-link system, it is determined whether the first frame sent by the first site device is received on the first link.

73. The communication method according to claim 72, wherein, The first frame carries the transmission and reception time information of the first site device on each link.

74. The communication method according to claim 72, wherein, The communication method further includes: When the third station device does not transmit on the second link, the third station device receives the first frame transmitted by the first station device on the first link.

75. The communication method according to claim 74, wherein, The third site device receives the first frame sent by the first site device on the first link within a predefined time window.

76. The communication method according to claim 72, wherein, The communication method further includes: When the third station device does not receive operations on the second link, the third station device sends a second frame to the first station device on the first link.

77. The communication method according to claim 76, wherein, The third site device sends the second frame to the first site device on the first link within a predefined time window.

78. The communication method according to claim 76, wherein, The second frame carries the transmission and reception time information of the second site device on each link and / or the transmission and reception time information of the third site device on each link.

79. The communication method according to claim 63 or 76, wherein, The communication method further includes: Based on the transmission and reception time information of the third station device on each link of the multi-link system, or based on its own prediction, the third station device determines the transmission time on at least one link of the multi-link system, and confirms whether to send a third frame to the second station device on the second link.

80. The communication method according to claim 79, wherein, The third frame carries the transmission and reception time information of the third site device on each link.

81. The communication method according to claim 79, wherein, The communication method further includes: When the third station device does not receive operations on the first link, the third station device sends the third frame to the second station device on the second link.

82. The communication method according to claim 81, wherein, The third station device sends the third frame to the second station device on the second link within a predefined time window.

83. The communication method according to claim 79, wherein, The communication method further includes: When the third station device does not transmit on the first link, the third station device receives the fourth frame sent by the second station device on the second link.

84. The communication method according to claim 83, wherein, The third site device receives the fourth frame sent by the second site device on the second link within a predefined time window.

85. The communication method according to claim 83, wherein, The fourth frame carries the transmission and reception time information of the second site device on each link.

86. The communication method according to claim 69, wherein, The communication method further includes: When the third station device does not receive operations on one link of the multi-link, the third station device performs a transmission operation on the other link of the multi-link.

87. The communication method according to claim 69, wherein, The communication method further includes: When the first site device or the second site device does not transmit on one of the links in the multi-link system, the third site device transmits a frame to the first site device or the second site device on the other link in the multi-link system.

88. The communication method according to claim 63, wherein, The communication method further includes: The third site device sends a frame to the first site device on the channel corresponding to the main link of the third site device. The frame of the third site device carries information about the third site device, including information about the non-main link of the third site device.

89. The communication method according to claim 63, wherein, The communication method further includes: The third site device sends a frame to the second site device on the channel corresponding to the main link of the third site device. The frame of the third site device carries information about the third site device, including information about the non-main link of the third site device.

90. The communication method according to claim 63, wherein, The communication method further includes: The third site device sends a frame to the second site device on the channel corresponding to the backhaul link of the third site device. The frame of the third site device carries information about the third site device, including information about the non-main link of the third site device.

91. A multi-link communication method, executed at a third-site device, wherein, The communication method includes: Non-simultaneous transmission and reception on at least two links of a multi-link system, wherein a frame of the third site device is transmitted to the first site device on the channel corresponding to the main link of the third site device, the frame of the third site device carrying information of the third site device, including information of the non-main link of the third site device.

92. A multi-link communication method, executed at a third-site device, wherein, The communication method includes: Non-simultaneous transmission and reception on at least two links of a multi-link system, wherein a frame of the third site device is transmitted to the second site device on the channel corresponding to the primary link of the third site device, the frame of the third site device carrying information of the third site device, the information of the third site device including information of the non-primary link of the third site device, wherein the third site device is the target site device, and the second site device is the current site device.

93. A multi-link communication method, executed at a third-site device, wherein, The communication method includes: Non-simultaneous transmission and reception on at least two links of a multi-link system, wherein a frame of the third site device is transmitted to the second site device on the channel corresponding to the backhaul link of the third site device, the frame of the third site device carrying information of the third site device, the information of the third site device including information of the non-primary link of the third site device, wherein the third site device is the target site device, and the second site device is the current site device.

94. A multi-link communication method, executed at a first site device, wherein, The communication method includes: The first station device transmits information to the second station device via a backhaul link and / or a frame, or receives information to the second station device via the backhaul link and / or the frame, wherein the first station device transmits and receives data non-simultaneously on at least two links of a multi-link system.

95. The communication method according to claim 94, wherein, The information includes one or more of the following: modulation and coding scheme (MCS), channel bandwidth, resource unit size, and / or number of spatial streams.

96. The communication method according to claim 94, wherein, The communication method further includes: The cache status report of the first site device and / or the second site device is used to assist one of the first site device and the second site device in calculating and / or estimating the data transmission time of the other of the first site device and the second site device.

97. The communication method according to claim 96, wherein, The first site device is the target site device, and the second site device is the current site device, or the first site device is the current site device, and the second site device is the current target site device.

98. 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 97.

Images