COMMUNICATION METHODS, COMMUNICATION DEVICES, AND COMMUNICATION EQUIPMENT

Abstract

The invention relates to a method, a communication device, and a communication apparatus for improving the roaming efficiency of a non-access point multi-link device. In the method, a non-access point multi-link device (non-AP MLD) receives a Basic Service Set Transition Management (BTM) request sent by an existing access point multi-link device (AP MLD). The Basic Service Set Transition Management (BTM) request may include functional indicator information of the candidate AP MLD, and functional indicator information indicating whether the candidate AP MLD supports test link operation. The non-AP MLD may initiate test link operation with respect to the candidate AP MLD based on the functional indicator information of the candidate AP MLD.The invention applies to a wireless local area network that supports the next-generation wireless internet access protocol (wireless fidelity, Wi-Fi) IEEE 802.11be, such as Wi-Fi 8, UHR, or 11bn, Wi-Fi AI, millimeter wave (mmWave), ultra-wideband (UWB), or sensing.

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on September 25, 2023, with application number 202311252839.X and application name "A Communication Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The embodiments of the present application relate to the field of communication technology, and in particular to a communication method and apparatus. Background Art

[0004] Due to factors such as the movement of a non-access point multi-link device (non-AP MLD), the non-AP MLD needs to switch its associated access point multi-link device (AP MLD).

[0005] During non-AP MLD roaming, when the AP MLD associated with a non-AP MLD switches from the current AP MLD to the target AP MLD, the two parties must negotiate key and transmission capability parameters and establish a block acknowledgment (BA) session. Reducing the latency associated with these association operations while minimizing the impact on non-AP MLD data transmission is a challenge facing next-generation wireless fidelity (WiFi) roaming.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide a communication method and apparatus, which can improve the roaming performance of non-AP MLD.

[0008] In a first aspect, a communication method is provided. The method is performed by a non-AP MLD, which is connected to a current access point multi-link device (AP MLD). The non-AP MLD may receive a basic service set transfer management (BTM) request sent by the current AP MLD. The BTM request may include function indication information of a candidate AP MLD, where the candidate AP MLD may be a neighbor AP MLD of the current AP MLD. The function indication information indicates whether the candidate AP MLD supports a tentative association operation. The non-AP MLD may initiate a tentative association operation for the candidate AP MLD based on the function indication information of the candidate AP MLD.

[0009] In the above communication method, the non-AP MLD may receive a BTM request sent by the current AP MLD during data transmission with the current AP MLD. After receiving the BTM request, the non-AP MLD may initiate a tentative association operation with the candidate AP MLD based on the function indication information of the candidate AP MLD carried in the BTM request. Before switching the associated AP MLD, the non-AP MLD may negotiate with the candidate AP MLD in advance on association operations such as keys, capability parameters, and operation parameters, and establish a BA session. When a roaming condition is triggered, the non-AP MLD may quickly switch the distributed system DS data path to the AP MLD with which the tentative association operation has been established and perform data transmission, thereby reducing the delay caused by performing the association operation and achieving rapid switching of the AP MLD.

[0010] The candidate AP MLD is a neighboring AP MLD of the current AP MLD. Specifically, the capability indication of the neighboring AP MLD is carried in the BTM request sent by the current AP MLD to the non-AP MLD. During data transmission with the current AP MLD, the non-AP MLD can receive the BTM request sent by the current AP MLD and determine whether the neighboring AP MLD supports tentative association. This eliminates the need for the non-AP MLD to switch channels to listen to beacon frames sent by the neighboring AP MLD to determine whether the neighboring AP MLD supports tentative association. This also does not affect normal data transmission between the non-AP MLD and the current AP MLD, improving roaming performance for the non-AP MLD.

[0011] In an optional implementation, the function indication information of the candidate AP MLD is carried in the neighbor report element field of the BTM request.

[0012] In an optional implementation, the function indication information may include a first function indication bit, where the first function indication bit is used to indicate whether the candidate AP MLD supports a first type of tentative association operation, where the first type of tentative association operation refers to performing a tentative association operation over an air interface. If the first function indication bit indicates that the corresponding candidate AP MLD supports the first type of tentative association operation, a tentative association operation is performed over the air interface for the candidate AP MLD.

[0013] In the above implementation, the first function indicator bit indicates whether the corresponding candidate AP MLD supports the tentative association operation over the air interface. The non-AP MLD can determine whether each candidate AP MLD supports the tentative association operation over the air interface based on the first function indicator bit corresponding to each candidate AP MLD. This helps the non-AP MLD select an appropriate AP MLD from the candidate AP MLDs that support the tentative association operation over the air interface and perform the tentative association operation in advance, thereby reducing the delay caused by performing the association operation when switching the AP MLD.

[0014] In another optional implementation, the function indication information may include a second function indication bit, where the second function indication bit is used to indicate whether the candidate AP MLD supports a second type of tentative association operation, where the second type of tentative association operation refers to performing a tentative association operation via a distributed system (DS). If the second function indication bit indicates that the corresponding candidate AP MLD supports the second type of tentative association operation, a tentative association operation is performed for the candidate AP MLD via the DS.

[0015] In the above implementation, the second function indicator bit indicates whether the corresponding candidate AP MLD supports tentative association via DS. The non-AP MLD can determine whether each candidate AP MLD supports tentative association via DS based on the second function indicator bit corresponding to each candidate AP MLD. This helps the non-AP MLD select an appropriate AP MLD from among those that support tentative association via DS for preemptive tentative association, thereby reducing the latency associated with performing the association operation during AP MLD switching. Furthermore, during the tentative association process, the non-AP MLD and the candidate AP MLD can forward information exchanged between them via DS via the current AP MLD, eliminating the need for the non-AP MLD to switch channels and communicate directly with the candidate AP MLD over the air interface. Therefore, the tentative association process between the non-AP MLD and the candidate AP MLD via DS does not affect normal data transmission between the non-AP MLD and the current AP MLD.

[0016] In another optional implementation, the function indication information may include the above-mentioned first function indication bit and second function indication bit. If the first function indication bit indicates that the candidate AP MLD supports the first type of tentative association operation, and the second function indication bit indicates that the candidate AP MLD does not support the second type of tentative association operation, then a tentative association operation is performed on the candidate AP MLD through the air interface. If the first function indication bit indicates that the candidate AP MLD supports the first type of tentative association operation, and the second function indication bit indicates that the candidate AP MLD supports the second type of tentative association operation, then a tentative association operation is preferentially performed on the candidate AP MLD through the DS. The process of the non-AP MLD and the candidate AP MLD performing the tentative association operation through the DS will not affect the normal data transmission between the non-AP MLD and the current AP MLD.

[0017] In another optional implementation, the function indication information may include first indication information and second indication information. The first indication information may be used to indicate whether the candidate AP MLD supports a tentative association operation, and the second indication information may be used to indicate the type of tentative association operation supported by the candidate AP MLD. The type of tentative association operation may be the first type or the second type described above. The non-AP MLD may select an appropriate AP MLD from the candidate AP MLDs based on the type of tentative association operation corresponding to each candidate AP MLD and perform a tentative association operation in advance.

[0018] In an optional implementation, the second indication information may be specifically expressed as the first function indication bit and the second function indication bit, that is, the function indication information may include the first indication information, the first function indication bit and the second function indication bit.

[0019] In an optional implementation, the BTM request may also include request mode indication information, which may be used to instruct the non-AP MLD to perform a tentative association operation or a basic service set (BSS) transfer operation. If the request mode indication information instructs the non-AP MLD to perform a tentative association operation, the non-AP MLD may initiate a tentative association operation with the candidate AP MLD based on the function indication information of the candidate AP MLD. If the request mode indication information instructs the non-AP MLD to perform a basic service set (BSS) transfer operation, the non-AP MLD may perform a BSS transfer operation and connect to the network through the target AP MLD after the BSS transfer.

[0020] In the above implementation, the BTM request includes request mode indication information, which can be used to instruct the non-AP MLD whether to perform a tentative association operation or a BSS transfer operation next. This allows the current AP MLD to send a BTM request to the non-AP MLD, notifying the non-AP MLD in advance through the BTM request to perform a tentative association operation with the recommended candidate AP MLD. When roaming conditions are triggered, the current AP MLD then sends a BTM request to the non-AP MLD, instructing the non-AP MLD to perform a BSS transfer operation to switch to the AP MLD. Notifying the non-AP MLD in advance through the BTM request to perform a tentative association operation with the recommended candidate AP MLD can avoid the situation in fast-moving scenarios where the non-AP MLD cannot complete the tentative association operation before data transmission with the current AP MLD is interrupted due to poor link quality.

[0021] In an optional implementation, the request mode indication information may be carried in the request mode field of the BTM request.

[0022] A second aspect provides a communication method performed by a non-AP MLD, which is connected to a current access point multi-link device (AP MLD). The communication method may include: the non-AP MLD receiving a basic service set transfer management (BTM) request sent by the current AP MLD. The BTM request may include request mode indication information, which may be used to instruct the non-AP MLD to perform a tentative association operation or a basic service set (BSS) transfer operation. If the request mode indication information instructs the non-AP MLD to perform a tentative association operation, the non-AP MLD initiates a tentative association operation for a candidate AP MLD.

[0023] In an optional implementation, if the request mode indication information instructs the non-AP MLD to perform a BSS transfer operation, the non-AP MLD performs the BSS transfer operation and connects to the network through the target AP MLD after the BSS transfer.

[0024] In an optional implementation, the request mode indication information may be carried in the request mode field of the BTM request.

[0025] According to a third aspect, a communication method is provided. The method is performed by a current access point multi-link device (AP MLD) that is not an access point multi-link device (non-AP MLD). The communication method may include: the current AP MLD sending a basic service set transfer management (BTM) request to the non-AP MLD; the BTM request includes function indication information of a candidate AP MLD; the candidate AP MLD is a neighbor AP MLD of the current AP MLD; the function indication information indicates whether the candidate AP MLD supports a tentative association operation; and the current AP MLD receiving a BTM response sent by the non-AP MLD.

[0026] In an optional implementation, the function indication information is carried in the neighbor report element field of the BTM request.

[0027] In an optional implementation, the function indication information may include a first function indication bit, which is used to indicate whether the candidate AP MLD supports a first type of tentative association operation; the first type of tentative association operation refers to a tentative association operation performed over an air interface.

[0028] In an optional implementation, the function indication information may include a second function indication bit, which is used to indicate whether the candidate AP MLD supports a second type of tentative association operation; the second type of tentative association operation refers to a tentative association operation performed through a distributed system DS.

[0029] In an optional implementation, the function indication information may include first indication information and second indication information. The first indication information may be used to indicate whether the candidate AP MLD supports a tentative association operation, and the second indication information may be used to indicate the type of tentative association operation supported by the candidate AP MLD. The type of tentative association operation may be the first type or the second type described above.

[0030] In an optional implementation, the BTM request may further include request mode indication information, and the request mode indication information may be used to instruct the non-AP MLD to perform a tentative association operation or a basic service set (BSS) transfer operation.

[0031] In an optional implementation, the request mode indication information may be carried in the request mode field of the BTM request.

[0032] In a fourth aspect, a communication method is provided, performed by a current access point multi-link device (AP MLD) of a non-AP MLD. The communication method may include: the current AP MLD sending a basic service set transfer management (BTM) request to the non-AP MLD; the BTM request including request mode indication information; the request mode indication information being used to instruct the non-AP MLD to perform a tentative association operation or a basic service set (BSS) transfer operation; and the current AP MLD receiving a BTM response sent by the non-AP MLD.

[0033] In an optional implementation, the request mode indication information may be carried in the request mode field of the BTM request.

[0034] In a fifth aspect, a communication device is provided, which can be applied to a non-AP MLD, wherein the non-AP MLD is connected to a current access point multi-link device AP MLD. The communication device may include:

[0035] The request receiving module is configured to receive a basic service set transfer management (BTM) request sent by the current AP MLD. The BTM request includes function indication information of a candidate AP MLD. The candidate AP MLD is a neighboring AP MLD of the current AP MLD. The function indication information indicates whether the candidate AP MLD supports a tentative association operation.

[0036] The association operation module is configured to initiate a tentative association operation for the candidate AP MLD according to the function indication information of the candidate AP MLD.

[0037] In an optional implementation, the function indication information of the candidate AP MLD is carried in the neighbor report element field of the BTM request.

[0038] In an optional implementation, the function indication information may include a first function indication bit, which is used to indicate whether the candidate AP MLD supports a first type of tentative association operation, where the first type of tentative association operation refers to a tentative association operation performed over an air interface.

[0039] In an optional implementation, the association operation module may be specifically configured to: if the first function indicator bit indicates that the corresponding candidate AP MLD supports a first type of tentative association operation, perform a tentative association operation on the candidate AP MLD via an air interface.

[0040] In an optional implementation, the function indication information may include a second function indication bit, which is used to indicate whether the candidate AP MLD supports a second type of tentative association operation, wherein the second type of tentative association operation refers to a tentative association operation performed through a distributed system DS.

[0041] In an optional implementation, the association operation module may be specifically configured to: if the second function indicator bit indicates that the corresponding candidate AP MLD supports the second type of tentative association operation, perform a tentative association operation on the candidate AP MLD through the DS.

[0042] In an optional implementation, the function indication information may include the first function indication bit and the second function indication bit mentioned above; the association operation module may be specifically configured to: if the first function indication bit indicates that the candidate AP MLD supports a first type of tentative association operation, and the second function indication bit indicates that the candidate AP MLD does not support a second type of tentative association operation, perform a tentative association operation on the candidate AP MLD via an air interface.

[0043] In an optional implementation, the function indication information may include first indication information and second indication information. The first indication information may be used to indicate whether the candidate AP MLD supports a tentative association operation, and the second indication information may be used to indicate the type of tentative association operation supported by the candidate AP MLD. The type of tentative association operation may be the first type or the second type described above.

[0044] In an optional implementation, the BTM request may further include request mode indication information, which may be used to instruct the non-AP MLD to perform a tentative association operation or a basic service set (BSS) transfer operation. The association operation module may be specifically configured to initiate a tentative association operation for the candidate AP MLD based on the function indication information of the candidate AP MLD if the request mode indication information instructs the non-AP MLD to perform a tentative association operation.

[0045] In an optional implementation, the communication device may further include a transfer operation module configured to perform a BSS transfer operation when the request mode indication information instructs the non-AP MLD to perform a BSS transfer operation, and connect to the network through the target AP MLD after the BSS transfer.

[0046] In an optional implementation, the request mode indication information may be carried in the request mode field of the BTM request.

[0047] In a sixth aspect, a communication device is provided, which can be applied to a non-AP MLD, wherein the non-AP MLD is connected to a current access point multi-link device AP MLD. The communication device may include:

[0048] A request receiving module is configured to receive a basic service set transfer management (BTM) request sent by the current AP MLD; the BTM request includes request mode indication information; the request mode indication information is used to instruct the non-AP MLD to perform a tentative association operation or a basic service set (BSS) transfer operation;

[0049] The association operation module is configured to initiate a tentative association operation for a candidate AP MLD if the request mode indication information indicates that the non-AP MLD performs a tentative association operation; wherein the candidate AP MLD is a neighbor AP MLD of the current AP MLD.

[0050] In an optional implementation, the communication device may further include a transfer operation module configured to perform a BSS transfer operation when the request mode indication information instructs the non-AP MLD to perform a BSS transfer operation, and connect to the network through the target AP MLD after the BSS transfer.

[0051] In an optional implementation, the request mode indication information may be carried in the request mode field of the BTM request.

[0052] In a seventh aspect, a communication device is provided, which can be applied to a current access point multi-link device AP MLD of a non-access point multi-link device non-AP MLD. The communication device may include:

[0053] A request sending module is configured to send a basic service set transfer management (BTM) request to a non-AP MLD. The BTM request includes function indication information of a candidate AP MLD. The candidate AP MLD is a neighboring AP MLD of the current AP MLD. The function indication information indicates whether the candidate AP MLD supports a tentative association operation.

[0054] The response receiving module is used to receive the BTM response sent by the non-AP MLD.

[0055] In an optional implementation, the function indication information is carried in the neighbor report element field of the BTM request.

[0056] In an optional implementation, the function indication information may include a first function indication bit, which is used to indicate whether the candidate AP MLD supports a first type of tentative association operation; the first type of tentative association operation refers to a tentative association operation performed over an air interface.

[0057] In an optional implementation, the function indication information may include a second function indication bit, which is used to indicate whether the candidate AP MLD supports a second type of tentative association operation; the second type of tentative association operation refers to a tentative association operation performed through a distributed system DS.

[0058] In an optional implementation, the function indication information may include first indication information and second indication information. The first indication information may be used to indicate whether the candidate AP MLD supports a tentative association operation, and the second indication information may be used to indicate the type of tentative association operation supported by the candidate AP MLD. The type of tentative association operation may be the first type or the second type described above.

[0059] In an optional implementation, the BTM request may further include request mode indication information, and the request mode indication information may be used to instruct the non-AP MLD to perform a tentative association operation or a basic service set (BSS) transfer operation.

[0060] In an optional implementation, the request mode indication information may be carried in the request mode field of the BTM request.

[0061] In an eighth aspect, a communication device is provided, which can be applied to a current access point multi-link device AP MLD of a non-access point multi-link device non-AP MLD. The communication device may include:

[0062] A request sending module is configured to send a basic service set transfer management (BTM) request to a non-AP MLD; the BTM request includes request mode indication information; the request mode indication information is used to instruct the non-AP MLD to perform a tentative association operation or a basic service set (BSS) transfer operation;

[0063] The response receiving module is used to receive the BTM response sent by the non-AP MLD.

[0064] In an optional implementation, the request mode indication information may be carried in the request mode field of the BTM request.

[0065] In a ninth aspect, a communications device is provided, wherein the communications device is a non-AP MLD, connected to a current access point multi-link device (AP MLD). The communications device includes a memory and a processor, wherein the memory stores a computer program; the processor is configured to execute the computer program stored in the memory to implement any of the methods described in the first or second aspects.

[0066] In a tenth aspect, a communication device is provided, wherein the communication device is a current access point multi-link device (AP MLD) of a non-AP MLD. The communication device includes a memory and a processor, wherein the memory stores a computer program; the processor is configured to execute the computer program stored in the memory to implement any of the methods described in the third or fourth aspects.

[0067] In an eleventh aspect, a communication system is provided, comprising a non-AP MLD and an AP MLD. The non-AP MLD can be used to perform any of the methods described in the first or second aspects, and the AP MLD can be used to perform any of the methods described in the third or fourth aspects.

[0068] In a twelfth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable a computer to execute any one of the methods provided in the first or second aspect above.

[0069] In a thirteenth aspect, a computer-readable storage medium is provided, in which computer-executable instructions are stored. The computer-executable instructions are used to enable a computer to execute any one of the methods provided in the third or fourth aspect.

[0070] In a fourteenth aspect, a computer program product is provided, comprising computer-executable instructions, which are used to enable a computer to execute any one of the methods provided in the first or second aspect.

[0071] In a fifteenth aspect, a computer program product is provided, comprising computer-executable instructions for enabling a computer to execute any one of the methods provided in the third or fourth aspect.

[0072] The technical effects that can be achieved in any of the second to fifteenth aspects mentioned above can refer to the description of the beneficial effects in the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0073] FIG1 is a schematic diagram of a communication system provided in an embodiment of the present application;

[0074] FIG2 is a schematic diagram of the structures of a non-AP MLD and an AP MLD provided in an embodiment of the present application;

[0075] FIG3 is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0076] FIG4 is a schematic diagram of an interaction process between a non-AP MLD and a current AP MLD according to an embodiment of the present application;

[0077] FIG5 is a schematic diagram of a frame structure of a BTM request provided in an embodiment of the present application;

[0078] FIG6 is a schematic diagram of the field structure of a BSS termination duration sub-element in a BTM request provided by an embodiment of the present application;

[0079] FIG7 is a schematic diagram of the field structure of a neighbor report element in a BTM request provided in an embodiment of the present application;

[0080] FIG8 is a schematic diagram of an interaction process between a non-AP MLD, a current AP MLD, and a target AP MLD according to an embodiment of the present application;

[0081] FIG9 is a schematic diagram of a frame structure of a BTM inquiry frame provided in an embodiment of the present application;

[0082] FIG10 is a schematic diagram of a frame structure of a BTM response frame provided in an embodiment of the present application;

[0083] FIG11 is a schematic diagram of a frame structure of an FT action frame provided in an embodiment of the present application;

[0084] FIG12 is a schematic diagram of an interaction process between another non-AP MLD, the current AP MLD, and the target AP MLD according to an embodiment of the present application;

[0085] FIG13 is a schematic diagram of an interaction process between another non-AP MLD and the current AP MLD according to an embodiment of the present application;

[0086] FIG14 is a schematic diagram of a frame structure of another BTM request provided in an embodiment of the present application;

[0087] FIG15 is a structural block diagram of a communication device provided in an embodiment of the present application;

[0088] FIG16 is a structural block diagram of another communication device provided in an embodiment of the present application;

[0089] FIG17 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0090] In order to make the purpose, technical solutions and advantages of the embodiments of the present application more clear, the embodiments of the present application will be further described in detail with reference to the accompanying drawings. The specific operation methods and functional descriptions in the method embodiments can also be applied to the device embodiments or system embodiments.

[0091] Before introducing the specific solutions provided by the embodiments of the present application, some of the terms in the present application are explained to facilitate understanding by those skilled in the art, and the terms in the present application are not limited.

[0092] (1) Multi-link device (MLD): A device with multi-link aggregation capability can be called an MLD. For example, the device can have multiple RF modules at the same time, each operating on a different frequency band / channel. When the channel spacing between two RF modules in a device is large enough, they can operate independently without interfering with each other. MLD is used in the IEEE802.11WiFi extremely high throughput (EHT) scheme to increase the transmission rate. In some embodiments, if any two links of the MLD support sending on one link while receiving on the other link, the two links are said to support simultaneous transmit and receive (STR) capability; otherwise, the two links are said to not support simultaneous transmit and receive capability, that is, the two links are non-STR.

[0093] (2) Distributed system (DS): A distributed system (DS) interconnects multiple basic service sets (BSSs) and integrates local area networks (LANs) to form an extended service set (ESS). In other words, a DS can construct an ESS that includes multiple interconnected BSSs, or alternatively, a DS includes multiple interconnected BSSs. The BSS is a fundamental component of 802.11 local area networks. For example, a DS can include multiple access point (AP) MLDs, with each AP MLD or each AP in an AP MLD corresponding to a BSS.

[0094] Unless otherwise specified, ordinal numbers such as "first" and "second" in the embodiments of the present application are used to distinguish multiple objects and are not used to limit the order, timing, priority or importance of multiple objects.

[0095] The embodiments of the present application can be applied to wireless local area network (WLAN) systems, and the embodiments of the present application can be applied to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series protocols adopted by WLAN, such as 802.11be, 802.11bf, and future 802.11 protocols. The method provided in the embodiments of the present application can be implemented by a communication device in a wireless communication system or a chip or circuit applied to the communication device. Accordingly, the communication device supports communication using the IEEE 802.11 series protocols. For example, the communication device supports the IEEE 802.11be next-generation WiFi protocol, such as Wi-Fi 8, UHR, 11bn, or Wi-Fi AI, or millimeter wave (mmWave), or ultra-wideband (UWB), or a sensing wireless local area network protocol. Although the embodiments of the present application are mainly described using a network deploying IEEE 802.11 as an example, it will be readily understood by those skilled in the art that the various aspects involved in the embodiments of the present application can be extended to other networks that adopt various standards or protocols, such as Bluetooth, high-performance wireless local area network (LAN) (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard, mainly used in Europe), and wide area network (WAN), WLAN, personal area network (PAN) or other networks now known or developed later. The technical solutions of the embodiments of the present application can be applied to various cellular communication systems, such as the fifth generation (5G) system, new radio (NR), and future sixth generation (6G) systems.

[0096] The communication method provided in the embodiments of the present application can be applied to the following communication system, which may include at least one non-access point device and at least two access point devices. The non-access point device and the access point device can communicate with each other, and the access point device can provide wireless network access services for the non-access point device. Among them, the non-access point device can be called a station (STA) device. In some embodiments, the non-access point device can adopt a multi-link device. When the non-access point device adopts a multi-link device, the non-access point device can be called a non-access point (non-AP) MLD, or also called a STA MLD. Similarly, the access point device can also adopt a multi-link device. When the access point device adopts a multi-link device, the access point device can be called an AP MLD.

[0097] For example, in the communication system shown in FIG1 , non-AP MLD 300 can communicate with AP MLD 100 and AP MLD 200. Non-AP MLD 300 can be understood as a device with wireless transceiver capabilities. For example, a non-AP MLD can be a terminal device, user equipment (UE), access terminal, subscriber unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user equipment. In specific applications, non-AP MLDs can be cellular phones, mobile phones, tablets, wearable devices, smart point-of-sale (POS) machines, customer-premises equipment (CPE), computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, industrial control terminals, self-driving terminals, remote medical terminals, smart grid terminals, smart city terminals, and smart home terminals.

[0098] A non-AP MLD can include multiple links, each corresponding to a different STA function. These STA functions typically operate on different frequency bands or channels. Each STA function can be considered a radio frequency module in the non-AP MLD. In the example of Figure 1, non-AP MLD 300 includes two STA functions, STA1 and STA2. Both STA1 and STA2 can operate in the 2.4 GHz and 5 GHz frequency bands, and at certain times, STA1 and STA2 can operate in different frequency bands. In other embodiments, a non-AP MLD can include more than two STA functions.

[0099] AP MLD100 and AP MLD200 can be understood as devices such as wireless hubs or routers used to provide wireless network access services. They can be used as access points for non-AP MLDs to access the wired Ethernet backbone.

[0100] Similar to non-AP MLDs, AP MLDs can include multiple links, each corresponding to a different AP function. These AP functions typically operate on different frequency bands or channels, and each AP function can be understood as a radio frequency transceiver module within the AP MLD. In the example of Figure 1 , AP MLD100 and AP MLD200 each include two AP functions, AP1 and AP2. AP1 and AP2 operate on different frequency bands: 2.4 GHz and 5 GHz, respectively. In some embodiments, AP MLD100 and AP MLD200, or in other words, AP1 and AP2 in AP MLD100 and AP1 and AP2 in AP MLD200, can belong to the same DS.

[0101] In a possible implementation, the communication system shown in FIG1 may further include other non-AP MLD and / or AP MLD devices, or other devices, and this application does not impose any limitation thereto.

[0102] In some embodiments, as shown in Figure 2, an AP MLD or non-AP MLD may include a physical layer (PHY) (PHY1 and PHY2 shown in Figure 2) and a medium access control (MAC) layer. The physical layer can be used to process physical layer signals, and the MAC layer can be used to process MAC layer signals. Furthermore, the MAC layer can be divided into an upper-MAC (UMAC) layer (UMAC shown in Figure 2) and multiple low-MAC (LMAC) layers (LMAC1 and LMAC2 shown in Figure 2). As shown in Figure 2, the multiple AP functions included in the AP MLD are independent of each other at the low-MAC layer and PHY layer, but share the high-MAC layer. The multiple STA functions included in the non-AP MLD are independent of each other at the low-MAC layer and PHY layer, but share the high-MAC layer. The high-MAC layer is connected to multiple low-MAC layers, meaning that the high-MAC layer is shared by multiple links. Each link has its own MAC address at the LMAC layer of the MLD. The MAC address corresponding to each link can be called a link address. In addition, each MLD also has a MAC address at the UMAC layer of the MLD. The MAC address corresponding to the MLD can be called an MLD MAC address (MLD address).

[0103] For example, the high MAC layer mainly completes operations such as the allocation of sequence numbers (SN) and packet numbers (PN) for MAC service data units (MSDUs), as well as encryption and decryption. The low MAC layer mainly completes operations such as the assembly of MAC protocol data units (MPDUs) for each link, channel access, packet transmission, and packet reception confirmation.

[0104] In Figure 2, the PHY1, lower MAC1, and higher MAC layers in an AP MLD are considered AP1, while the PHY2, lower MAC2, and higher MAC layers are considered AP2. This means that an AP MLD can include multiple AP functionalities, which are independent of each other at the lower MAC and PHY layers but share the higher MAC layer. Similarly, in a non-AP MLD, the higher MAC layer is shared by multiple links. The PHY1, lower MAC1, and higher MAC layers are considered STA1, while the PHY2, lower MAC2, and higher MAC layers are considered STA2. This means that a non-AP MLD can include multiple STA functionalities, which are independent of each other at the lower MAC and PHY layers but share the higher MAC layer. PHY1 of AP1 in the AP MLD and PHY1 of STA1 in the non-AP MLD operate on the same channel. AP1 in the AP MLD and STA1 in the non-AP MLD can communicate through link 1 shown in Figure 2. PHY2 of AP2 in the AP MLD and PHY2 of STA2 in the non-AP MLD operate on another same channel. AP2 in the AP MLD and STA2 in the non-AP MLD can communicate through link 2.

[0105] During communication, a non-AP MLD can connect to the network through its associated AP MLD. However, due to factors such as the movement of the non-AP MLD, the AP MLD associated with the non-AP MLD may switch. For example, if a non-AP MLD moves from the coverage area of ​​AP MLD1 to the coverage area of ​​AP MLD2, the AP MLD associated with the non-AP MLD may need to be switched. This switching process is also called roaming.

[0106] For example, Figure 3 illustrates a possible process in which the AP MLD associated with a non-AP MLD switches from AP MLD1 to AP MLD2. As shown in Figure 3, before handover or roaming, the non-AP MLD is associated with AP MLD1, which is called the current AP MLD. For example, STA1 in the non-AP MLD operates in the 2.4 GHz band and establishes a link with AP1 in AP MLD1. STA2 in the non-AP MLD operates in the 5 GHz band and establishes a link with AP2 in AP MLD1.

[0107] Due to factors such as mobility, a non-AP MLD moves out of the coverage area of ​​its current AP MLD, AP MLD1, and into the coverage area of ​​AP MLD2. For example, as shown in Figure 3, during handover or roaming, the non-AP MLD establishes a tentative association with AP MLD2, having previously established and negotiated a link with AP MLD2. STA1 in the non-AP MLD establishes a link with AP1 in AP MLD2, and STA2 in the non-AP MLD establishes a link with AP2 in AP MLD2.

[0108] As shown in Figure 3, after a certain point in time, the non-AP MLD switches the DS data path to AP MLD2, that is, roams to AP MLD2.

[0109] In actual communication scenarios, AP MLD1 and AP MLD2 can belong to the same DS. That is, as the non-AP MLD moves, the AP MLD associated with it can switch from its current AP MLD to a neighboring AP MLD in the same DS. Because each AP MLD, or each AP in an AP MLD, corresponds to a BSS, the aforementioned handover process can also be understood as the process of switching the non-AP MLD from its current BSS to a neighboring BSS in the same ESS. This can be referred to as BSS transfer or BSS handover.

[0110] When a non-AP MLD switches from its currently associated AP MLD to a target AP MLD, it must negotiate keys and transmission capability parameters with the target AP MLD, and establish a BA session. These operations increase the latency of the handover process.

[0111] The present application provides the following embodiments, which are applied to the above-mentioned AP MLD switching scenario.

[0112] [Example 1]

[0113] In an embodiment of the present application, before switching the associated AP MLD, the non-AP MLD can receive a basic service set transfer management (BSS transition management, BTM) request sent by the current AP MLD. The BTM request includes functional indication information of the candidate AP MLD, wherein the candidate AP MLD is the neighbor AP MLD of the current AP MLD, and the functional indication information is used to indicate whether the candidate AP MLD supports a tentative association operation. The non-AP MLD can initiate a tentative association operation for the candidate AP MLD based on the functional indication information of the candidate AP MLD. In some application scenarios, the tentative association operation can also be referred to as a hot standby operation. In an embodiment of the present application, the non-AP MLD can receive a BTM request sent by the current AP MLD during the process of data transmission with the current AP MLD. Before and after receiving the BTM request, the normal data transmission between the non-AP MLD and the current AP MLD will not be affected, which is beneficial to improving the data transmission performance of the network. After receiving the BTM request, the non-AP MLD can initiate a tentative association operation with the candidate AP MLD based on the function indication information of the candidate AP MLD carried in the BTM request. Before switching the associated AP MLD, the non-AP MLD negotiates the key, capability parameters, operation parameters, and establishes a BA session with the candidate AP MLD in advance. When the roaming condition is triggered, the non-AP MLD can quickly transmit data with the AP MLD with which the tentative association operation has been established, thereby reducing the delay caused by the association operation, achieving rapid BSS switching, and reducing data transmission interruption time.

[0114] FIG4 shows a flow chart of interaction between a non-AP MLD and a current AP MLD during a tentative association operation.

[0115] As shown in Figure 4, the process may include the following steps:

[0116] S401: The current AP MLD sends a BTM request to the non-AP MLD.

[0117] A data transmission link exists between the non-AP MLD and the current AP MLD. If the link quality of the non-AP MLD deteriorates, the current AP MLD can send a BTM request to the non-AP MLD, recommending that the non-AP MLD switch to a neighboring AP MLD. The BTM request can include function indication information for a candidate AP MLD, which is a neighboring AP MLD of the current AP MLD. The function indication information is used to indicate whether the candidate AP MLD supports tentative association operations. The current AP MLD can determine whether each of its neighboring AP MLDs supports tentative association operations through a notification message broadcast in the DS, by querying neighboring AP MLDs, or by using information collected by the non-AP MLD through channel scanning. For example, the BTM request can include function indication information corresponding to one or more candidate AP MLDs.

[0118] In some embodiments, the function indication information may include a first function indication bit used to indicate whether the corresponding candidate AP MLD supports a first type of tentative association operation, wherein the first type of tentative association operation refers to a tentative association operation performed over the air interface (also referred to as an over-the-air tentative association operation). The over-the-air tentative association operation means that a non-AP MLD can perform a tentative association with a candidate AP MLD directly over the air interface. During the tentative association process, the non-AP MLD can establish a data transmission link with the candidate AP MLD. The transmission capability parameters of the two parties can also be negotiated (for example, the transmission bandwidth and maximum number of streams between the two parties), the key information of the two parties (such as PTK, group temporal key (GTK), integrity group temporal key (IGTK) and beacon integrity group temporal key (BIGTK), etc.), and the resource allocation information of the two parties (such as BA session, restricted target wakeup time (r-TWT), etc.).

[0119] For example, the first function indicator bit may occupy one bit in the BTM request. If the value of the first function indicator bit is "0," it may indicate that the corresponding candidate AP MLD does not support the over-the-air tentative association operation. If the value of the first function indicator bit is "1," it may indicate that the corresponding candidate AP MLD supports the over-the-air tentative association operation.

[0120] In some other embodiments, the function indication information may include a second function indication bit used to indicate whether the corresponding candidate AP MLD supports a second type of tentative association operation, where the second type of tentative association operation refers to a tentative association operation performed over DS (over-the-DS), which may also be referred to as an Over-the-DS tentative association operation. Whether the Over-the-DS tentative association operation is supported refers to whether the Over-the-DS tentative association operation can be performed with the candidate AP MLD through the current AP MLD. For example, if a candidate AP MLD supports the Over-the-DS tentative association operation, but the current AP MLD does not support the Over-the-DS tentative association operation, the second function indication bit corresponding to the candidate AP MLD is also set to indicate that the candidate AP MLD does not support the Over-the-DS tentative association operation. Therefore, it can also be said that the second function indication bit is used to indicate whether the Over-the-DS tentative association operation can be performed with the candidate AP MLD through the current AP MLD. For example, if the current AP MLD does not support Over-the-DS tentative association operation, the second function indication bits of all candidate AP MLDs included in the BTM request indicate that the corresponding candidate AP MLDs do not support Over-the-DS tentative association operation.

[0121] Over-the-DS tentative association means that a non-AP MLD can establish a tentative association with a candidate AP MLD through the current AP MLD, establish a data transmission link with the candidate AP MLD, and negotiate transmission capability parameters, key information, and resource allocation information between the non-AP MLD and the candidate AP MLD.

[0122] Illustratively, the second function indicator bit may occupy one bit in the BTM request. If the value of the second function indicator bit is "0," it may indicate that the corresponding candidate AP MLD does not support Over-the-DS tentative association operations, or that Over-the-DS tentative association operations cannot be performed with the candidate AP MLD through the current AP MLD. If the value of the second function indicator bit is "1," it may indicate that the corresponding candidate AP MLD supports Over-the-DS tentative association operations, or that Over-the-DS tentative association operations can be performed with the candidate AP MLD through the current AP MLD.

[0123] In the above embodiment, the function indication information may include the above first function indication bit, or include the above second function indication bit.

[0124] In some other embodiments, the function indication information may include the first function indication bit and the second function indication bit. For example, if the value of the first function indication bit is "1" and the value of the second function indication bit is "0", it may indicate that the corresponding candidate AP MLD supports the over-the-air tentative association operation but does not support the over-the-DS tentative association operation, or cannot perform the over-the-DS tentative association operation with the candidate AP MLD through the current AP MLD. If the value of the first function indication bit is "1" and the value of the second function indication bit is "1", it may indicate that the corresponding candidate AP MLD supports the over-the-air tentative association operation and also supports the over-the-DS tentative association operation, or can perform the over-the-DS tentative association operation with the candidate AP MLD through the current AP MLD. If the value of the first function indicator bit is "0", it indicates that the corresponding candidate AP MLD does not support the over-the-air tentative association operation. In this case, the value of the second function indicator bit is also "0", that is, when a candidate AP MLD does not support the over-the-air tentative association operation, it also does not support the over-the-DS tentative association operation.

[0125] In some other embodiments, the function indication information may include first indication information and second indication information. The first indication information may be used to indicate whether the corresponding candidate AP MLD supports the tentative association operation, and the second indication information may be used to indicate the type of tentative association operation supported by the corresponding candidate AP MLD. In an optional embodiment, the first indication information and the second indication information may each occupy one bit in the BTM request. If the value of the first indication information is "0," it may indicate that the corresponding candidate AP MLD does not support the tentative association operation, and the value of the second indication information is meaningless. If the value of the first indication information is "1," it may indicate that the corresponding candidate AP MLD supports the tentative association operation. If the value of the first indication information is "1" and the value of the second indication information is "0," it may indicate that the corresponding candidate AP MLD supports the over-the-air tentative association operation. If the value of the first indication information is "1" and the value of the second indication information is "1," it may indicate that the corresponding candidate AP MLD supports the over-the-DS tentative association operation. In another optional embodiment, the second indication information may occupy two bits in the BTM request. If the value of the first indication information is "0", it may indicate that the corresponding candidate AP MLD does not support the tentative association operation, and the value of the second indication information may be "00". If the value of the first indication information is "1", it may indicate that the corresponding candidate AP MLD supports the tentative association operation. If the value of the first indication information is "1" and the value of the second indication information is "10", it may indicate that the corresponding candidate AP MLD supports the over-the-air tentative association operation. If the value of the first indication information is "1" and the value of the second indication information is "11", it may indicate that the corresponding candidate AP MLD supports the over-the-DS tentative association operation.

[0126] In other embodiments, the second indication information may also be embodied as the first function indicator bit and the second function indicator bit described above, that is, the function indication information may include the first indication information, the first function indicator bit, and the second function indicator bit. The first indication information, the first function indicator bit, and the second function indicator bit may each occupy one bit in the BTM request. If the value of the first indication information is "1," it may indicate that the corresponding candidate AP MLD supports tentative association operations. If the value of the first indication information is "1," the value of the first function indicator bit is "1," and the value of the second function indicator bit is "0," it may indicate that the corresponding candidate AP MLD supports over-the-air tentative association operations but does not support over-the-DS tentative association operations. If the value of the first indication information is "1," the value of the first function indicator bit is "1," and the value of the second function indicator bit is "1," it may indicate that the corresponding candidate AP MLD supports both over-the-air and over-the-DS tentative association operations. If the value of the first indication information is "0," it indicates that the corresponding candidate AP MLD does not support tentative association operations, and the values ​​of the first function indicator bit and the second function indicator bit are both "0."

[0127] The following describes the BTM request frame format sent by the current AP MLD to the non-AP MLD. A BTM request is also called a BTM request frame or a BTM request frame message.

[0128] Exemplarily, in some embodiments, the frame format of the BTM request frame is shown in Figure 5, and may include some or all of the following fields: category, wireless network management operation (WNM action), dialog token, request mode, disassociation timer, validity interval, BSS termination duration, session information (session info URL), and BSS transfer alternative list.

[0129] Among them, the category field can be used to indicate which category the corresponding frame message belongs to, for example, whether it is an inquiry frame, a request frame, or a response frame.

[0130] Dialog Token field: can be used to identify the correspondence between request frames and response frames. A pair of request frames and response frames carry the same dialog token value.

[0131] Request Mode Field: This field can be used to indicate a specific request mode. The Request Mode field can include the following fields shown in Figure 5: whether to carry a preferred candidate list (preferred candidate list include), bridge (abridge), disassociation imminent (disassociation imminent), whether BSS termination (BSS termination included), extended service set disassociation imminent (ESS disassociation imminent), link removal (Link Removal), and reserved (reserved) fields. The reserved field can occupy 2 bits.

[0132] In the request mode field, the Preferred candidate list include field can be used to indicate whether the preferred candidate list is carried. Abridge field: If the current AP MLD does not recommend or prohibits the non-AP MLD from switching to a BSS that does not appear in the preferred candidate list, the Abridged field is set to 0; if the current AP MLD sets the preference value (perference value) of the BSS that does not appear in the preferred candidate list to 0, the Abridged field is set to 1. Disassociation imminent field: When the Disassociation imminent field is set to 1, it means that the current AP MLD will send a Disassociation frame to associate with the STA of the non-AP MLD; when the Disassociation imminent field is set to 0, it means that the current AP MLD will not send a Disassociation frame to associate with the STA. The BSS termination included field can be used to indicate whether the BSS will be shut down. The ESS disassociation imminent field can be used to indicate whether the STA will be disassociated from the entire ESS.

[0133] Disassociation Timer field: can be used to indicate the time after which the current AP MLD sends a disassociation frame, in units of TBTT.

[0134] Validity Time field: can be used to indicate the number of beacon periods within which the BSS transfer candidate list is valid.

[0135] The BSS termination duration field may carry a BSS termination duration subelement. As shown in Figure 6, the subelement may include a subelement identifier (subelement ID), length, BSS termination timing synchronization function (BSS termination TSF), and duration. The subelement identifier occupies 1 byte (octets) and may be used to indicate the identifier of the corresponding BSS termination duration subelement; the length occupies 1 byte and may be used to indicate the length of the BSS termination duration field; the BSS termination TSF may occupy 8 bytes and may carry the value of the TSF timer to indicate the time when the BSS is terminated; the duration may be used to indicate the duration of the BSS being terminated, in minutes. If the duration field is 0, it indicates that the field is reserved.

[0136] The BSS Transfer Candidate List field can carry one or more Neighbor Report Elements (NREs), each of which carries information about a candidate AP MLD (a neighbor AP MLD of the current AP MLD). A candidate AP MLD can be an AP MLD recommended by the current AP MLD, and the non-AP MLD can select a target AP MLD from at least one of the recommended AP MLDs. It can also be understood that the BSS Transfer Candidate List field can include information about one or more candidate AP MLDs, each of which includes function indication information specific to the candidate AP MLD. The function indication information indicates whether the candidate AP MLD supports tentative association operations.

[0137] In some embodiments, as shown in Figure 7, each neighbor report element may include the following fields: element ID, length, BSS ID (BSSID), BSSID information (info), operating class (operating class), channel number (channel number), physical layer type (PHY type), and optional subelenments.

[0138] The BSSID field may be used to indicate the BSSID of the corresponding candidate AP MLD (neighbor AP MLD). The BSSID Information field may be used to indicate relevant information about the corresponding BSSID. The Operating Class field and the Channel Number field may be used to indicate the channel to which the BSSID belongs. The PHY Type field may be used to indicate the physical layer type of the candidate AP MLD. The Optional Subelenments field may include a Basic Multi-Link Subelement field.

[0139] In an optional implementation, as shown in FIG7 , the BSSID information field may include the following fields: AP reachability, security, key scope, capabilities, mobility domain, high throughput, very high throughput, fine timing measurement (FTM), high efficiency, extended range BSS (ER BSS), co-located AP, unsolicited probe response active, co-located with 2.4 GHz / 5 GHz AP and member of extended service set (member of extended service set with 2.4 / 5 GHz co-located AP), on-channel tunneling (OCT) supported with reporting AP, co-located with 6 GHz AP, and reserved fields.

[0140] In an embodiment of the present application, the BTM request includes functional indication information of one or more candidate AP MLDs. The functional indication information of each candidate AP MLD can be carried in the Neighbor Report Element field corresponding to the candidate AP MLD. That is, the Neighbor Report Element field corresponding to a candidate AP MLD can include the identifier of the candidate AP MLD (the aforementioned element identifier) ​​and the functional indication information of the candidate AP MLD. For example, in some embodiments, the functional indication information of a candidate AP MLD can be carried in a reserved field of the Neighbor Report Element field corresponding to the candidate AP MLD shown in FIG7 . In other embodiments, the MLD capabilities and operations subfield can be set in the basic multi-link subelement field. The functional indication information of a candidate AP MLD can be carried in the MLD capabilities and operations subfield in the basic multi-link subelement field of the Neighbor Report Element field corresponding to the candidate AP MLD.

[0141] S402: The non-AP MLD initiates a tentative association operation with respect to the candidate AP MLD according to the function indication information of the candidate AP MLD carried in the BTM request.

[0142] For example, the BTM request may include function indication information of one or more candidate AP MLDs. For each candidate AP MLD in the BTM request, the non-AP MLD may perform the following operations: obtaining the function indication information of the candidate AP MLD from the BTM request. If the function indication information indicates that the candidate AP MLD supports a first type of tentative association operation, namely, an over-the-air tentative association operation, the non-AP MLD may perform an over-the-air tentative association operation on the candidate AP MLD. If the function indication information indicates that the candidate AP MLD supports a second type of tentative association operation, namely, an over-the-DS tentative association operation, or is capable of performing an over-the-DS tentative association operation with the candidate AP MLD through the current AP MLD, the non-AP MLD may perform an over-the-DS tentative association operation on the candidate AP MLD. If the function indication information indicates that the candidate AP MLD supports both the over-the-air tentative association operation and the over-the-DS tentative association operation, or is capable of performing an over-the-DS tentative association operation with the candidate AP MLD through the current AP MLD, the non-AP MLD may preferentially perform an over-the-DS tentative association operation on the candidate AP MLD. If the function indication information indicates that the candidate AP MLD supports both the over-the-air tentative association operation and the over-the-DS tentative association operation, or is capable of performing an over-the-DS tentative association operation with the candidate AP MLD through the current AP MLD, the non-AP MLD may preferentially perform an over-the-DS tentative association operation on the candidate AP MLD. If MLD supports over-the-air tentative association but does not support over-the-DS tentative association, or if over-the-DS tentative association cannot be performed with the candidate AP MLD through the current AP MLD, the non-AP MLD can perform an over-the-air tentative association for the candidate AP MLD. If the capability indication indicates that the candidate AP MLD does not support tentative association, the non-AP MLD does not perform a tentative association for the candidate AP MLD.

[0143] In some embodiments, when the BTM request may include function indication information of multiple candidate AP MLDs, if at least two of the multiple candidate AP MLDs support the over-the-air tentative association operation, the non-AP MLD may select at least one candidate AP MLD from the at least two candidate AP MLDs that support the over-the-DS tentative association operation, and perform the over-the-air tentative association operation on the selected candidate AP MLD; if at least two of the multiple candidate AP MLDs support the over-the-DS tentative association operation, the non-AP MLD may select at least one candidate AP MLD from the at least two candidate AP MLDs that support the over-the-DS tentative association operation, and perform the over-the-DS tentative association operation on the selected candidate AP MLD.

[0144] In some other embodiments, when the BTM request may include function indication information of multiple candidate AP MLDs, if some of the multiple candidate AP MLDs support the over-the-DS tentative association operation while other candidate AP MLDs support the over-the-air tentative association operation or do not support the tentative association operation, the non-AP MLD may preferentially select at least one candidate AP MLD from the candidate AP MLDs that support the over-the-DS tentative association operation and perform the over-the-DS tentative association operation on the selected candidate AP MLD; if some of the multiple candidate AP MLDs support the over-the-air tentative association operation while other candidate AP MLDs do not support the tentative association operation, the non-AP MLD may preferentially select at least one candidate AP MLD from the candidate AP MLDs that support the over-the-air tentative association operation and perform the over-the-air tentative association operation on the selected candidate AP MLD.

[0145] In the above embodiment, the BTM request sent by the current AP MLD to the non-AP MLD may include the function indication information of the candidate AP MLD. The function indication information is used to indicate whether the candidate AP MLD supports the tentative association operation. After receiving the BTM request, the non-AP MLD can initiate a tentative association operation with the candidate AP MLD based on the function indication information of the candidate AP MLD carried in the BTM request. Before switching to the associated AP MLD, the non-AP MLD negotiates the key, capability parameters, operation parameters, and establishes a BA session with the candidate AP MLD in advance. When the roaming condition is triggered, the non-AP MLD can quickly transmit data with the AP MLD with which the tentative association operation has been established, thereby reducing the delay caused by the association operation and achieving rapid BSS switching.

[0146] In some designs, before switching its associated AP MLD, a non-AP MLD must select a STA from STA1 or STA2 and switch it to the channel of one of the target AP MLD's affiliated APs before transmitting data with the current AP MLD. The STA listens for beacon frames sent by the target AP MLD and determines whether the target AP MLD supports tentative association based on the indication contained in the beacon frames. This process can affect normal data transmission between the non-AP MLD and the current AP MLD. For an enhanced multi-link single radio (EMLSR) non-AP MLD, an EMLSR non-AP MLD can monitor multiple links simultaneously. Upon receiving an initial control frame from an AP MLD, the EMLSR non-AP MLD can switch the radio modules of other links in the EMLSR link set to the link that received the initial control frame, thereby increasing the number of transmit and receive flows. However, at any given time, an EMLSR non-AP MLD can only select one link for data transmission and reception. Unlike a multi-radio non-AP MLD, an EMLSR non-AP MLD has only one fully functional STA and can only transmit and receive data on a single link. Therefore, when an EMLSR non-AP MLD switches channels to listen to beacon frames from a target AP MLD, data transmission between the EMLSR non-AP MLD and the current AP MLD is interrupted.

[0147] In this embodiment of the present application, the BTM request sent by the current AP MLD to the non-AP MLD carries the function indication information of the candidate AP MLD. During data transmission with the current AP MLD, the non-AP MLD can receive the BTM request sent by the current AP MLD and, based on the function indication information of the candidate AP MLD carried in the BTM request, determine whether the candidate AP MLD supports over-the-air tentative association operations and over-the-DS tentative association operations. This eliminates the need for the non-AP MLD to switch channels to listen to beacon frames sent by neighboring AP MLDs of the current AP MLD to determine whether the corresponding neighboring AP MLD supports tentative association operations. Therefore, in this application, normal data transmission between the non-AP MLD and the current AP MLD is not affected before and after the non-AP MLD receives the BTM request. In particular, for an EMLSR non-AP MLD, data transmission interruption between the EMLSR non-AP MLD and the current AP MLD is avoided, improving the roaming performance of the non-AP MLD and facilitating enhanced network data transmission performance.

[0148] In some embodiments, before the current AP MLD sends a BTM request frame to the non-AP MLD, the non-AP MLD may send a BTM query frame to the current AP MLD. Figure 8 shows a flowchart of the interaction between the non-AP MLD, the current AP MLD, and the target AP MLD in a specific embodiment. The target AP MLD can be any of the candidate AP MLDs described above. As shown in Figure 8, this process may include the following steps:

[0149] S801: The non-AP MLD sends a BTM query frame to the current AP MLD.

[0150] There is a data transmission link between the non-AP MLD and the current AP MLD. If the link quality of the non-AP MLD deteriorates, the non-AP MLD can send a BTM query frame to the current AP MLD.

[0151] Exemplarily, the frame format of the BTM inquiry frame is shown in FIG9 , and may include some or all of the following fields: category, radio network management operation, session token, BSS transition query reason, and BSS transition candidate list.

[0152] Among them, the category field can be used to indicate which category the corresponding frame message belongs to, for example, whether it is an inquiry frame or a request frame.

[0153] BSS Transfer Query Reason field: can be used to indicate the reason for sending the BTM Query frame. In one embodiment, the structure of the BSS Transfer Query Reason field can refer to Table 1.

[0154] Table 1

[0155] As shown in Table 1, if the BSS Transfer Query Reason field in the BTM Query frame is set to 1, the non-AP MLD sends the BTM Query frame because of excessive packet loss or poor link quality. If the BSS Transfer Query Reason field in the BTM Query frame is set to 2, it indicates that the delay in receiving or sending data is too high.

[0156] The BSS transfer candidate list is an optional field. If the BTM query frame carries the BSS transfer candidate list, the BSS transfer candidate list can carry information about the neighboring AP MLDs of the current AP MLD detected by the non-AP MLD.

[0157] The current AP MLD receives the BTM query frame sent by the non-AP MLD and can reply to the non-AP MLD with an acknowledgment (ACK) frame for the BTM query frame.

[0158] S802: The current AP MLD sends a BTM request frame to the non-AP MLD.

[0159] After receiving the BTM query frame, the current AP MLD can send a BTM request frame to the non-AP MLD. The BTM request frame can include function indication information corresponding to one or more candidate AP MLDs. The frame format of the BTM request frame is shown in Figure 5 and is not further described here.

[0160] After receiving the BTM request frame sent by the current AP MLD, the non-AP MLD can reply to the non-AP MLD with an ACK frame for the BTM request frame.

[0161] S803: The non-AP MLD sends a BTM response frame to the current AP MLD.

[0162] The BTM response frame may also be referred to as a BTM response. For example, the frame format of the BTM response frame is shown in FIG10 , and may include some or all of the following fields: category, radio network management operation, session token, BTM status code, BSS termination delay, target BSSID, and BSS transfer candidate list.

[0163] Among them, the category field can be used to indicate which category the corresponding frame message belongs to, for example, whether it is an inquiry frame, a request frame, or a response frame.

[0164] Dialog Token field: can be used to identify the correspondence between request frames and response frames. A pair of request frames and response frames carry the same dialog token value.

[0165] The BSS termination delay may be used to indicate the duration of a time period from the current time to the termination of the BSS.

[0166] The BTM status code field may be used to indicate whether the BSS transfer request is accepted. For example, the values ​​of the BTM status code may be as shown in Table 2.

[0167] Table 2

[0168] As shown in Table 2, when the BSS transfer request is accepted by the non-AP MLD, the BTM status code value is 0. When the BSS transfer request is rejected by the non-AP MLD, the different values ​​of the BTM status code can indicate the reason for the rejection.

[0169] When the BTM status code is 0, the BTM response frame may include a target BSSID field, where the target BSSID is the BSSID corresponding to the target AP MLD selected by the non-AP MLD from the candidate AP MLDs carried in the BTM request frame.

[0170] When the current AP MLD receives a BTM response frame sent by a non-AP MLD, it can reply to the non-AP MLD with an ACK frame for the BTM response frame.

[0171] In the embodiment shown in Figure 8, it is assumed that the target AP MLD selected by the non-AP MLD from the candidate AP MLDs is an AP MLD that supports over-the-DS tentative association. For example, in an optional embodiment, the BTM request frame includes function indication information for multiple candidate AP MLDs, and at least two of the multiple candidate AP MLDs support over-the-DS tentative association. The non-AP MLD can select any one of the at least two candidate AP MLDs that support over-the-DS tentative association as the target AP MLD. A candidate AP MLD that supports over-the-DS tentative association means that an over-the-DS tentative association operation can be performed with the candidate AP MLD through the current AP MLD. After determining the target AP MLD, the non-AP MLD can perform an over-the-DS tentative association operation on the target AP MLD.

[0172] S804: The non-AP MLD performs an over-the-DS tentative association operation on the target AP MLD.

[0173] The non-AP MLD can tentatively associate the current AP MLD with the target AP MLD:

[0174] For example, a non-AP can send a fast BSS transition (FT) probe request to the current AP MLD. The FT probe request can be used to request the establishment of a data transmission link between the non-AP MLD and the target AP MLD. After receiving the FT probe request, the current AP MLD can transparently transmit the FT probe request to the target AP MLD via the DS. The target AP MLD can establish a data transmission link between the target AP MLD and the non-AP MLD based on the FT probe request. This data transmission link can be an air interface link between the non-AP MLD and the target AP MLD. The target AP MLD can transparently transmit the DS to the current AP MLD. The current AP MLD sends the FT probe response to the non-AP MLD.

[0175] Next, the non-AP MLD can send an FT request to the current AP MLD. The current AP MLD transparently transmits the FT request to the target AP MLD via the DS. The FT request can be used to request communication parameters from the target AP MLD. The target AP MLD sends an FT response to the current AP MLD via the DS. The current AP MLD sends an FT response to the non-AP MLD. The FT response includes the key information negotiated between the non-AP MLD and the target AP MLD.

[0176] The non-AP MLD can send an FT reassociation request to the current AP MLD. The current AP MLD transparently transmits the FT reassociation request to the target AP MLD via the DS. The FT reassociation request can be used to negotiate link operating parameters between the non-AP MLD and the target AP MLD. The target AP MLD sends an FT reassociation response to the current AP MLD via the DS. The current AP MLD sends an FT reassociation response to the non-AP MLD, which includes the link operating parameters between the non-AP MLD and the target AP MLD.

[0177] In some embodiments, the FT query request, FT query response, FT request, FT response, FT reassociation request, and FT reassociation response involved in step S804 may be referred to as FT action frames. As shown in FIG11 , the frame structure of the FT action frame may include some or all of the following fields: category, FT action, MAC address of the non-AP MLD, MAC address of the target AP MLD, and frame body.

[0178] The category field may be used to indicate the category to which the FT action frame belongs. The FT action field may include a value corresponding to the FT action. Different FT action frames may have different values ​​for the FT action field. For example, as shown in Table 3:

[0179] Table 3

[0180] As can be seen from Table 3, when the FT Action frame in Figure 11 is used as an FT Reassociation Request, the FT Action field is set to 7. The FT Query Request, FT Query Response, FT Request, and FT Response mentioned above all use the FT Action frame format in Figure 11; the difference is that the FT Action field in Table 3 is set to the corresponding value.

[0181] The MAC address field of the non-AP MLD includes the MAC layer address of the non-AP MLD. This address can be the high MAC layer address or the low MAC layer address of the non-AP MLD. The MAC address field of the target AP MLD includes the MAC layer address of the target AP MLD. This address can be the high MAC layer address or the low MAC layer address of the target AP MLD.

[0182] The frame body field may be used to carry the frame body corresponding to the FT action frame. The contents of the frame bodies carried by different FT action frames may be the same or different, and this embodiment of the application does not impose any limitation on this.

[0183] Through the above steps, the non-AP MLD completes the tentative association operation with the target AP MLD, which means that the non-AP MLD and the target AP MLD have established an association. The non-AP MLD and the target AP MLD are pre-established through the tentative association operation. When the BSS handover (or roaming) condition is triggered, the non-AP MLD activates the association with the target AP MLD and can directly transmit data. This reduces the association delay between the non-AP MLD and the target AP MLD during the BSS handover process and achieves a fast BSS handover.

[0184] In the embodiment shown in FIG8 , the BTM request sent by the current AP MLD to the non-AP MLD carries the function indication information of the candidate AP MLD. During data transmission between the non-AP MLD and the current AP MLD, the non-AP MLD receives the BTM request sent by the current AP MLD. Based on the function indication information of the candidate AP MLD carried in the BTM request, the non-AP MLD determines a target AP MLD that supports over-the-DS tentative association. The non-AP MLD then performs a trial association operation with the target AP MLD through the current AP MLD. This process completely eliminates the need for the non-AP MLD's affiliated STAs to switch channels, ensuring uninterrupted data transmission between the non-AP MLD and the current AP MLD. This ensures that normal data transmission between the non-AP MLD and the current AP MLD is not affected, thereby improving network data transmission performance.

[0185] FIG12 shows a flowchart of the interaction between the non-AP MLD, the current AP MLD, and the target AP MLD in another specific embodiment. The target AP MLD can be any of the candidate AP MLDs mentioned above. As shown in FIG12 , the process may include the following steps:

[0186] S1201: The non-AP MLD sends a BTM query frame to the current AP MLD.

[0187] The frame format of the BTM inquiry frame may be as shown in FIG9 , which will not be described in detail here.

[0188] The current AP MLD receives a BTM query frame sent by a non-AP MLD and can reply to the non-AP MLD with an ACK frame for the BTM query frame.

[0189] S1202: The current AP MLD sends a BTM request frame to the non-AP MLD.

[0190] The BTM request frame may include function indication information corresponding to one or more candidate AP MLDs. The frame format of the BTM request frame may be as shown in FIG5 , and will not be described in detail here.

[0191] After receiving the BTM request frame sent by the current AP MLD, the non-AP MLD can reply to the non-AP MLD with an ACK frame for the BTM request frame.

[0192] S1203: The non-AP MLD sends a BTM response frame to the current AP MLD.

[0193] The frame format of the BTM response frame may be as shown in FIG10 , which will not be described in detail here.

[0194] When the current AP MLD receives a BTM response frame sent by a non-AP MLD, it can reply to the non-AP MLD with an ACK frame for the BTM response frame.

[0195] In the embodiment shown in Figure 12, it is assumed that the target AP MLD selected by the non-AP MLD from the candidate AP MLDs is an AP MLD that supports over-the-air tentative association. For example, in an optional embodiment, the BTM request frame includes function indication information for multiple candidate AP MLDs, and at least two of the multiple candidate AP MLDs support over-the-air tentative association. In this case, the non-AP MLD can select any one of the at least two candidate AP MLDs that support over-the-air tentative association as the target AP MLD. The non-AP MLD can then perform an over-the-air tentative association operation on the target AP MLD.

[0196] S1204: The non-AP MLD performs an over-the-air tentative association operation on the target AP MLD.

[0197] For example, the non-AP MLD may send a probe request to the target AP MLD. The probe request may be used to request establishment of a data transmission link between the non-AP MLD and the target AP MLD. The target AP MLD may establish a data transmission link between the target AP MLD and the non-AP MLD based on the probe request. The data transmission link may be an air interface link between the non-AP MLD and the target AP MLD. The target AP MLD may send a probe response to the non-AP MLD.

[0198] Next, the non-AP MLD can send an authentication request to the target AP MLD, requesting the target AP MLD's communication parameters. The target AP MLD sends an authentication response to the non-AP MLD, which includes the key information negotiated between the non-AP MLD and the target AP MLD.

[0199] The non-AP MLD can send a reassociation request to the target AP MLD. The reassociation request is used to negotiate link operating parameters between the non-AP MLD and the target AP MLD. The target AP MLD sends a reassociation response to the non-AP MLD, which includes the link operating parameters between the non-AP MLD and the target AP MLD.

[0200] Through the above steps, the non-AP MLD completes the tentative association operation with the target AP MLD, which means that the non-AP MLD and the target AP MLD have established an association. The non-AP MLD and the target AP MLD are pre-established through the tentative association operation. When the BSS handover (or roaming) condition is triggered, the non-AP MLD activates the association with the target AP MLD and can directly transmit data. This reduces the association delay between the non-AP MLD and the target AP MLD during the BSS handover process and achieves a fast BSS handover.

[0201] In the embodiment shown in FIG12 , the BTM request sent by the current AP MLD to the non-AP MLD carries the function indication information of the candidate AP MLD. During data transmission with the current AP MLD, the non-AP MLD can receive the BTM request sent by the current AP MLD. Based on the function indication information of the candidate AP MLD carried in the BTM request, the non-AP MLD can determine a target AP MLD that supports the over-the-air tentative association operation. This helps the non-AP MLD select a suitable neighbor AP MLD from the candidate AP MLDs for BSS transfer.

[0202] [Example 2]

[0203] Considering that a non-AP MLD requires time to perform a tentative association, if the non-AP MLD is notified to perform a tentative association with the recommended candidate AP MLD only after the link quality between the non-AP MLD and the current AP MLD is already deteriorating, in fast-moving scenarios, data transmission between the non-AP MLD and the current AP MLD may be interrupted due to poor link quality before the non-AP MLD completes the tentative association. Therefore, the current AP MLD can notify the non-AP MLD to perform a tentative association with the recommended candidate AP MLD in advance. In other words, the current AP MLD can send a BTM request to the non-AP MLD in advance, using the BTM request to notify the non-AP MLD to perform a tentative association with the recommended candidate AP MLD. In some designs, the non-AP MLD typically performs a BSS transfer after receiving the BTM request from the current AP MLD. In order to prevent the non-AP MLD from directly performing a BSS transfer each time it receives a BTM request sent by the current AP MLD, an embodiment of the present application carries request mode indication information in the BTM request. The request mode indication information is used to instruct the non-AP MLD whether to perform a tentative association operation or a BSS transfer operation next.

[0204] Figure 13 shows a flowchart of the interaction between the non-AP MLD and the current AP MLD during a tentative association operation. As shown in Figure 13, the process may include the following steps:

[0205] S1301: The current AP MLD sends a first BTM request to the non-AP MLD.

[0206] A data transmission link exists between the non-AP MLD and the current AP MLD. If the link quality of the non-AP MLD deteriorates, the current AP MLD can send a BTM request to the non-AP MLD, recommending that the non-AP MLD switch to a neighboring AP MLD. The BTM request can include request mode indication information. This request mode indication information can be used to instruct the non-AP MLD to perform a tentative association operation or a BSS transfer operation.

[0207] In some embodiments, the request mode indication information can be carried in the request mode field of the BTM request. As shown in Figure 14, the frame format of the BTM request frame can include some or all of the following fields: Category, Radio Network Management Operation, Dialog Token, Request Mode, Disassociation Timer, Validity Time, BSS Termination Duration, Session Information, and BSS Transfer Candidate List. The BSS Transfer Candidate List carries information about the candidate AP MLD.

[0208] In an optional embodiment, the reserved field of the request mode field may carry request mode indication information, which may also be called a tentative association request. The request mode indication information may occupy one bit. When the value of the request mode indication information is "0," it indicates that the BTM request is to notify the non-AP MLD to perform a tentative association operation, rather than requiring the non-AP MLD to immediately perform a BSS transfer. When the value of the request mode indication information is "1," it indicates that the BTM request is to notify the non-AP MLD to perform a BSS transfer operation.

[0209] In another optional embodiment, whether a tentative association operation or a BSS transfer operation is performed can be distinguished by setting an existing field in the BTM request. For example, the request mode indication information can be carried by the disassociation imminent field in the request mode field. When the value of disassociation imminent is "0", it indicates that the BTM request notifies the non-AP MLD to perform a tentative association operation rather than requiring the non-AP MLD to immediately perform a BSS transfer. When the value of disassociation imminent is "1", it indicates that the BTM request notifies the non-AP MLD to perform a BSS transfer operation.

[0210] In this embodiment, the current AP MLD sends a first BTM request to the non-AP MLD. The first BTM request includes request mode indication information. Assume that the value of the request mode indication information is "1", which is used to instruct the non-AP MLD to perform a tentative association operation.

[0211] S1302: The non-AP MLD performs a tentative association operation based on the first BTM request.

[0212] In some embodiments, the non-AP MLD receives the first BTM request sent by the current AP MLD and can send a first BTM response to the current AP MLD. This process can be shown in FIG8 or FIG12 and will not be described in detail here.

[0213] The non-AP MLD may initiate a tentative association operation for the candidate AP MLD based on the candidate AP MLD information carried in the BSS transfer candidate list. For example, the non-AP MLD may select a target AP MLD that supports the tentative association operation from the candidate AP MLDs and perform a tentative association operation on the target AP MLD.

[0214] In some embodiments, the non-AP MLD may perform an over-the-DS tentative association operation with respect to the target AP MLD, and the operation process may be shown in FIG8 . In other embodiments, the non-AP MLD may perform an over-the-air tentative association operation with respect to the target AP MLD, and the operation process may be shown in FIG12 .

[0215] S1303: The current AP MLD sends a second BTM request to the non-AP MLD.

[0216] Upon determining that the BSS transfer conditions are met, the current AP MLD may send a second BTM request to the non-AP MLD. The frame format of the second BTM request may also adopt the format shown in Figure 14. The second BTM request may also include request mode indication information, which may be used to instruct the non-AP MLD to perform a tentative association operation or a BSS transfer operation. Assume that the request mode indication information in the second BTM request is set to "0," which instructs the non-AP MLD to perform a BSS transfer operation.

[0217] S1304: The non-AP MLD performs a BSS transfer operation based on the second BTM request.

[0218] When the non-AP MLD determines the request mode indication information in the second BTM request and instructs the non-AP MLD to perform the BSS transfer operation, the non-AP MLD may perform the BSS transfer operation and connect to the network through the target AP MLD after the BSS transfer.

[0219] In some embodiments, the non-AP MLD can activate its association with the target AP MLD and trigger a link switch, switching the non-AP MLD's transmission link from the current AP MLD to the target AP MLD. For example, the non-AP MLD sends a DS STA-AP mapping request frame (DS-STA-NOTIFY.request) to the target AP MLD. This DS-STA-AP mapping request frame can be used to request the target AP MLD to perform a data path switch. The target AP MLD sends a context transfer request to the current AP MLD. Upon receiving the context transfer request, the current AP MLD can choose to sequentially deliver complete MSDUs in its receive buffer to the DS. After the delivery is complete, the current AP MLD then sends a context transfer response to the target AP MLD. Alternatively, upon receiving the context transfer request, the current AP MLD immediately stops delivering MSDUs to the DS and then sends a context transfer response to the target AP MLD. The context transfer response includes context information of the non-AP MLD, such as information related to the block acknowledgement protocol. Simultaneously, the data in the receive buffer is transferred to the target AP MLD. The non-AP MLD disconnects from the current AP MLD and starts communicating with the target AP MLD. The current AP MLD deletes the non-AP MLD's context information. After the data path switchover, the non-AP MLD and the target AP MLD can resume data transmission. The non-AP MLD encrypts and decrypts the transmitted data using the key negotiated with the target AP MLD during the tentative association operation.

[0220] In the above embodiment, the BTM request includes request mode indication information, which can be used to instruct the non-AP MLD whether to perform a tentative association operation or a BSS transfer operation. This allows the current AP MLD to send a BTM request to the non-AP MLD in advance, notifying the non-AP MLD through the BTM request to perform a tentative association operation with the recommended candidate AP MLD in advance. This avoids the situation in fast-moving scenarios where the non-AP MLD has not yet completed the tentative association operation and data transmission with the current AP MLD is interrupted due to poor link quality.

[0221] The above-mentioned Embodiment 1 and Embodiment 2 can be implemented separately or cross-implemented. For example, in Embodiment 2, the first BTM request can also include functional indication information of the candidate AP MLD recommended by the current AP MLD, which is used to indicate whether the corresponding candidate AP MLD supports a tentative association operation. When the non-AP MLD receives the first BTM request sent by the current AP MLD, if the request mode indication information in the first BTM request indicates that the non-AP MLD performs a tentative association operation, the non-AP MLD can perform a tentative association operation on the candidate AP MLD based on the functional indication information of the candidate AP MLD carried in the first BTM request.

[0222] Based on the same design concept as the aforementioned method embodiment, this embodiment of the present application also provides a communication device. This communication device can be used in a non-AP MLD, such as non-AP MLD 300 shown in Figure 1 . This communication device can be used to implement the functions of the aforementioned method embodiment, thereby achieving the beneficial effects of the aforementioned method embodiment. As shown in Figure 15 , this communication device 1500 may include a request receiving module 1501 and an association operation module 1502.

[0223] In some embodiments, the request receiving module 1501 may be configured to receive a Basic Service Set Transfer Management (BTM) request sent by the current AP MLD. The BTM request includes function indication information of a candidate AP MLD. The candidate AP MLD is a neighboring AP MLD of the current AP MLD. The function indication information indicates whether the candidate AP MLD supports a tentative association operation. The association operation module 1502 may be configured to initiate a tentative association operation for the candidate AP MLD based on the function indication information of the candidate AP MLD.

[0224] In some other embodiments, the request receiving module 1501 may be configured to receive a basic service set transfer management (BTM) request sent by the current AP MLD; the BTM request includes request mode indication information; the request mode indication information is used to instruct the non-AP MLD to perform a tentative association operation or a basic service set (BSS) transfer operation;

[0225] The association operation module 1502 may be configured to initiate a tentative association operation for a candidate AP MLD if the request mode indication information indicates that the non-AP MLD performs a tentative association operation; the candidate AP MLD is a neighbor AP MLD of the current AP MLD.

[0226] In some embodiments, the communication device 1500 may further include a transfer operation module. The transfer operation module may be configured to perform a BSS transfer operation when the request mode indication information instructs the non-AP MLD to perform a BSS transfer operation, and connect to the network through the target AP MLD after the BSS transfer.

[0227] It should be noted that, in other embodiments, the request receiving module 1501 can be used to execute any step in the communication method, and the association operation module 1502 can be used to execute any step in the communication method. The steps that the request receiving module 1501 and the association operation module 1502 are responsible for implementing can be specified as needed. By having the request receiving module 1501 and the association operation module 1502 respectively implement different steps in the communication method, the full functionality of the communication device is achieved.

[0228] The functional modules in the embodiments of the present application may be integrated into a processor, or each module may exist physically separately, or two or more modules may be integrated into a single module. The above-mentioned integrated modules may be implemented in the form of hardware or software functional units.

[0229] Based on the same design concept as the aforementioned method embodiment, this embodiment of the present application also provides a communication device. This communication device can be applied to an AP MLD, such as AP MLD 100 or AP MLD 200 shown in Figure 1 , where the AP MLD is the current AP MLD of a non-AP MLD. This communication device can be used to implement the functions of the aforementioned method embodiment, thereby achieving the beneficial effects of the aforementioned method embodiment. As shown in Figure 16 , this communication device 1600 may include a request sending module 1601 and a response receiving module 1602.

[0230] In some embodiments, the request sending module 1601 may be configured to send a Basic Service Set Transfer Management (BTM) request to a non-AP MLD. The BTM request includes capability information of a candidate AP MLD. The candidate AP MLD is a neighboring AP MLD of the current AP MLD. The capability information indicates whether the candidate AP MLD supports a tentative association operation. The response receiving module 1602 may be configured to receive a BTM response sent by the non-AP MLD.

[0231] In other embodiments, the request sending module 1601 can be used to send a basic service set transfer management BTM request to the non-AP MLD; the BTM request includes request mode indication information; the request mode indication information is used to instruct the non-AP MLD to perform a tentative association operation or a basic service set BSS transfer operation; the response receiving module 1602 can be used to receive a BTM response sent by the non-AP MLD.

[0232] It should be noted that, in other embodiments, the request sending module 1601 can be used to execute any step in the communication method, and the response receiving module 1602 can be used to execute any step in the communication method. The steps that the request sending module 1601 and the response receiving module 1602 are responsible for implementing can be specified as needed. The full functionality of the communication device is achieved by having the request sending module 1601 and the response receiving module 1602 respectively implement different steps in the communication method.

[0233] The functional modules in the embodiments of the present application may be integrated into a processor, or each module may exist physically separately, or two or more modules may be integrated into a single module. The above-mentioned integrated modules may be implemented in the form of hardware or software functional units.

[0234] Based on the same technical concepts as the above-described method embodiments, embodiments of the present application also provide a communications device. This communications device may be the non-AP MLD or AP MLD shown in Figure 1 . This communications device can be used to implement the functions of the above-described method embodiments, thereby achieving the beneficial effects of the above-described method embodiments.

[0235] In some embodiments, the structure of the communication device 1700 can be as shown in Figure 17, including a processor 1701 and a memory 1702 connected to the processor 1701. The processor 1701 and the memory 1702 can be connected to each other via a bus. The processor 1701 can be a general-purpose processor, such as a microprocessor, or other conventional processors. The bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc.

[0236] Among them, the memory 1702 can be used to store software programs and modules, and the processor 1701 executes various functional applications and data processing of the communication device 1700 by running the software programs and modules stored in the memory 1702, such as the communication method provided in the embodiment of the present application.

[0237] Memory 1702 may primarily include a program storage area and a data storage area. The program storage area may store an operating system, at least one application program, and the like; the data storage area may be used to store user data, etc. Furthermore, memory 1702 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state memory device.

[0238] The processor 1701 in the communication device 1700 is configured to execute computer instructions or programs stored in the memory 1702 to perform the functions of any of the above-described method embodiments. For example, if the communication device 1700 is a non-AP MLD, the processor 1701 may be configured to perform the following steps: receive a BTM request sent by the current AP MLD, and initiate a tentative association operation for the candidate AP MLD based on the function indication information of the candidate AP MLD carried in the BTM request. Alternatively, the processor 1701 may be configured to perform the following steps: receive a BTM request sent by the current AP MLD, the BTM request including request mode indication information; if the request mode indication information indicates that the non-AP MLD should perform a tentative association operation, then initiate a tentative association operation for the candidate AP MLD; wherein the candidate AP MLD is a neighboring AP MLD of the current AP MLD.

[0239] If communication device 1700 is an AP MLD, processor 1701 may be configured to perform the following steps: send a BTM request to a non-AP MLD and receive a BTM response from the non-AP MLD. The BTM request includes function indication information of a candidate AP MLD; the candidate AP MLD is a neighbor AP MLD of the current AP MLD; the function indication information indicates whether the candidate AP MLD supports a tentative association operation. Alternatively, processor 1701 may be configured to perform the following steps: send a BTM request to a non-AP MLD and receive a BTM response from the non-AP MLD. The BTM request includes request mode indication information; the request mode indication information instructs the non-AP MLD to perform a tentative association operation or a basic service set (BSS) transfer operation.

[0240] In some embodiments, the processor 1701 may include one or more processing units. Different processing units may be independent devices or integrated into one or more processors. The processor 1701 may also include a controller that can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.

[0241] In one embodiment, the communication device 1700 may further include a communication module, and the communication module is used to communicate with other devices in the network.

[0242] In other embodiments, if the communication device 1700 is a non-AP MLD, the communication device may also adopt the non-AP MLD structure shown in Figure 1 or Figure 2. If the communication device 1700 is an AP MLD, the communication device may also adopt the AP MLD structure shown in Figure 1 or Figure 2. No further details are given here.

[0243] It is understood that the structures illustrated in the embodiments of this application do not constitute specific limitations on network devices. In other embodiments of this application, the chip may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0244] Based on the same technical concept as the above method embodiment, the present application embodiment further provides a communication system. The communication system may be the communication system shown in FIG1 , and the communication system may include at least one non-AP MLD and at least two AP MLDs.

[0245] Each AP MLD can perform the following steps: send a BTM request to a non-AP MLD and receive a BTM response from the non-AP MLD. The BTM request includes function indication information of the candidate AP MLD; the candidate AP MLD is a neighbor AP MLD of the current AP MLD; the function indication information indicates whether the candidate AP MLD supports a tentative association operation. Alternatively, the following steps can be performed: send a BTM request to a non-AP MLD and receive a BTM response from the non-AP MLD. The BTM request includes request mode indication information; the request mode indication information instructs the non-AP MLD to perform a tentative association operation or a basic service set (BSS) transfer operation.

[0246] Each non-AP MLD can perform the following steps: receive a BTM request sent by the current AP MLD, and initiate a tentative association operation for the candidate AP MLD based on the function indication information of the candidate AP MLD carried in the BTM request; or, can perform the following steps: receive a BTM request sent by the current AP MLD; the BTM request includes request mode indication information; if the request mode indication information indicates that the non-AP MLD should perform a tentative association operation, initiate a tentative association operation for the candidate AP MLD; wherein the candidate AP MLD is a neighbor AP MLD of the current AP MLD.

[0247] The present application also provides a computer program product comprising computer-executable instructions. In one embodiment, the computer-executable instructions are used to enable a computer to perform the functions of the above method embodiment.

[0248] Computer-executable instructions can be stored in a computer-readable storage medium. The present application also provides a computer-readable storage medium having executable instructions stored therein. In one embodiment, the computer-executable instructions are used to cause a computer to perform the functions of the above method embodiment.

[0249] The computer-readable storage medium provided in the embodiments of the present application may be a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a mobile hard disk, a CD-ROM, or any other form of computer-readable storage medium known in the art.

[0250] Computer-executable instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium such as a floppy disk, hard disk, or magnetic tape; an optical medium such as a digital video disc (DVD); or a semiconductor medium such as a solid-state drive.

[0251] In the various embodiments of the present application, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, including a series of steps or units. The method, system, product or device is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0252] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations thereof may be made without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are intended to be illustrative only of the solutions defined by the appended claims and are to be construed as covering any and all modifications, variations, combinations or equivalents within the scope of the present application.

[0253] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.

Claims

1. A communication method, characterized in that: Applied to a non-AP MLD, the non-AP MLD is connected to a current AP MLD; the method comprises: receiving a basic service set transfer management BTM request sent by the current AP MLD; the BTM request includes function indication information of a candidate AP MLD; the candidate AP MLD is a neighbor AP MLD of the current AP MLD; the function indication information is used to indicate whether the candidate AP MLD supports a tentative association operation; A tentative association operation is initiated for the candidate AP MLD according to the function indication information of the candidate AP MLD.

2. The method according to claim 1, characterized in that The function indication information is carried in a neighbor report element field of the BTM request.

3. The method according to claim 1 or 2, characterized in that: The function indication information includes a first function indication bit, and the first function indication bit is used to indicate whether the candidate AP MLD supports a first type of tentative association operation; the first type of tentative association operation refers to a tentative association operation performed through an air interface.

4. The method according to claim 3, characterized in that The initiating a tentative association operation for the candidate AP MLD according to the function indication information of the candidate AP MLD includes: If the first function indicator bit indicates that the candidate AP MLD supports a first type of tentative association operation, a tentative association operation is performed on the candidate AP MLD through an air interface.

5. The method according to any one of claims 1 to 4, characterized in that: The function indication information includes a second function indication bit, and the second function indication bit is used to indicate whether the candidate AP MLD supports a second type of tentative association operation; the second type of tentative association operation refers to a tentative association operation performed through a distributed system DS.

6. The method according to claim 5, characterized in that The initiating a tentative association operation for the candidate AP MLD according to the function indication information of the candidate AP MLD includes: If the second function indicator bit indicates that the candidate AP MLD supports a second type of tentative association operation, a tentative association operation is performed on the candidate AP MLD through the DS.

7. The method according to claim 5, characterized in that The initiating a tentative association operation for the candidate AP MLD according to the function indication information of the candidate AP MLD includes: If the first function indicator bit indicates that the candidate AP MLD supports a first type of tentative association operation, and the second function indicator bit indicates that the candidate AP MLD does not support a second type of tentative association operation, a tentative association operation is performed on the candidate AP MLD through an air interface.

8. The method according to any one of claims 1 to 7, characterized in that: The BTM request includes request mode indication information; Initiating a tentative association operation for the candidate AP MLD according to the function indication information of the candidate AP MLD includes: If the request mode indication information indicates that the non-AP MLD performs a tentative association operation, a tentative association operation is initiated for the candidate AP MLD according to the function indication information of the candidate AP MLD.

9. The method according to claim 8, characterized in that The method further comprises: If the request mode indication information instructs the non-AP MLD to perform a basic service set BSS transfer operation, the BSS transfer operation is performed, and the network is connected through the target AP MLD after the BSS transfer.

10. The method according to claim 8 or 9, characterized in that: The request mode indication information is carried in the request mode field of the BTM request.

11. A communication method, characterized in that: Applied to a non-AP MLD, the non-AP MLD is connected to a current AP MLD; the method comprises: receiving a basic service set transfer management BTM request sent by the current AP MLD; the BTM request includes request mode indication information; the request mode indication information is used to instruct the non-AP MLD to perform a tentative association operation or a basic service set BSS transfer operation; If the request mode indication information indicates that the non-AP MLD performs a tentative association operation, a tentative association operation is initiated for a candidate AP MLD; the candidate AP MLD is a neighbor AP MLD of the current AP MLD.

12. The method according to claim 11, characterized in that The method further comprises: If the request mode indication information instructs the non-AP MLD to perform a BSS transfer operation, the BSS transfer operation is performed, and the network is connected through the target AP MLD after the BSS transfer.

13. The method according to claim 11 or 12, characterized in that: The request mode indication information is carried in the request mode field of the BTM request.

14. A communication method, characterized in that: The method is applied to a current access point multi-link device AP MLD of a non-access point multi-link device non-AP MLD, comprising: Sending a basic service set transfer management BTM request to the non-AP MLD; the BTM request includes function indication information of the candidate AP MLD; the candidate AP MLD is a neighbor AP MLD of the current AP MLD; the function indication information is used to indicate whether the candidate AP MLD supports a tentative association operation; A BTM response sent by the non-AP MLD is received.

15. The method according to claim 14, characterized in that The function indication information is carried in a neighbor report element field of the BTM request.

16. The method according to claim 14 or 15, characterized in that The function indication information includes a first function indication bit, and the first function indication bit is used to indicate whether the candidate AP MLD supports a first type of tentative association operation; the first type of tentative association operation refers to a tentative association operation performed through an air interface.

17. The method according to any one of claims 14 to 16, characterized in that: The function indication information includes a second function indication bit, and the second function indication bit is used to indicate whether the candidate AP MLD supports a second type of tentative association operation; the second type of tentative association operation refers to a tentative association operation performed through a distributed system DS.

18. The method according to any one of claims 14 to 17, characterized in that: The BTM request includes request mode indication information; the request mode indication information is used to instruct the non-AP MLD to perform a tentative association operation or a basic service set BSS transfer operation.

19. The method according to claim 18, characterized in that The request mode indication information is carried in the request mode field of the BTM request.

20. A communication method, characterized in that: The method is applied to a current access point multi-link device AP MLD of a non-access point multi-link device non-AP MLD, comprising: Sending a basic service set transfer management BTM request to the non-AP MLD; the BTM request includes request mode indication information; the request mode indication information is used to instruct the non-AP MLD to perform a tentative association operation or a basic service set BSS transfer operation; A BTM response sent by the non-AP MLD is received.

21. The method according to claim 20, characterized in that The request mode indication information is carried in the request mode field of the BTM request.

22. A communication device, characterized in that: Applied to a non-access point multi-link device non-AP MLD, the non-AP MLD is connected to a current access point multi-link device AP MLD; the device includes a module for executing the method as described in any one of claims 1 to 10, or a module for executing the method as described in any one of claims 11 to 13.

23. A communication device, characterized in that: A current access point multi-link device AP MLD applied to a non-access point multi-link device non-AP MLD; the device comprises a module for executing a method as claimed in any one of claims 14 to 19, or a module for executing a method as claimed in any one of claims 20 to 21.

24. A communication device, characterized in that: The communication device is a non-AP MLD, and the non-AP MLD is connected to a current access point multi-link device AP MLD; the communication device comprises: a memory and a processor, and a computer program is stored in the memory; the processor is used to execute the computer program stored in the memory to implement the method as claimed in any one of claims 1 to 10, or to execute the method as claimed in any one of claims 11 to 13.

25. A communication device, characterized in that: The communication device is a current access point multi-link device AP MLD of a non-access point multi-link device non-AP MLD; the communication device comprises: a memory and a processor, a computer program is stored in the memory; the processor is used to execute the computer program stored in the memory to implement the method as described in any one of claims 14 to 19, or to execute the method as described in any one of claims 20 to 21.

26. A communication system, characterized in that: It comprises a non-AP MLD and an AP MLD; the non-AP MLD is used to execute a computer program to implement the method as described in any one of claims 1 to 10, or to execute the method as described in any one of claims 11 to 13; the AP MLD is used to execute a computer program to implement the method as described in any one of claims 14 to 19, or to execute the method as described in any one of claims 20 to 21.

27. A computer-readable storage medium, characterized in that: Computer executable instructions are stored, and the computer executable instructions are used to enable a computer to execute the method according to any one of claims 1 to 13, or the method according to any one of claims 14 to 21.

28. A computer program product, characterized in that The method comprises computer executable instructions, wherein the computer executable instructions are used to enable a computer to execute the method according to any one of claims 1 to 13, or the method according to any one of claims 14 to 21.

Images