Communication method and device

Abstract

The invention provides a communication method and device, which are used for improving the roaming performance of non-access point multi-link equipment. In the method, a non-AP MLD receives a basic service set transfer management BTM request sent by a current AP MLD. The BTM request can comprise function indication information of the candidate AP MLD, and the function indication information is used for representing whether the candidate AP MLD supports tentative association operation or not. The non-AP MLD can initiate a tentative association operation for the candidate AP MLD according to the function indication information of the candidate AP MLD. The present application is applied to a wireless local area network system that supports an IEEE 802.11 be next generation WiFi protocol, such as Wi-Fi 8, UHR, 11bn, or Wi-Fi AI, or millimeter wave (mmWave), or ultra wide band (UWB), or sensing.

Description

Technical Field

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

[0002] 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).

[0003] In the process of switching the AP MLD associated with the non-AP MLD from the current AP MLD to the target AP MLD, that is, in the non-APMLD roaming process, the non-AP MLD and the target AP MLD need to negotiate the key and transmission capability parameters, and establish the block ack (BA) session and other association operations. How to reduce the delay caused by the execution of the association operation while reducing the impact on the data transmission of the non-AP MLD is a problem that needs to be solved in the next generation of wireless fidelity (WiFi) roaming. Summary of the invention

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

[0005] In a first aspect, a communication method is provided, which is 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 receives a basic service set transfer management BTM request sent by the current AP MLD. The BTM request may include functional indication information of a candidate AP MLD, wherein the candidate AP MLD may be a neighbor AP MLD of the current AP MLD. The functional indication information is used to characterize 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 functional indication information of the candidate AP MLD.

[0006] In the above communication method, the non-AP MLD can 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 can initiate a tentative association operation for the candidate AP MLD according to the function indication information of the candidate AP MLD carried in the BTM request. Before switching the associated APMLD, the non-AP MLD negotiates with the candidate AP MLD in advance on the key, capability parameters, operation parameters, and establishes BA session and other association operations. When the roaming condition is triggered, the non-AP MLD can quickly switch the distributed system DS data path to the AP MLD that has established the tentative association operation and perform data transmission, thereby reducing the delay caused by performing the association operation and realizing rapid switching of the AP MLD.

[0007] Among them, the candidate AP MLD is the neighbor AP MLD of the current AP MLD, that is, the function indication information of the neighbor AP MLD of the current AP MLD is carried in the BTM request sent by the current AP MLD to the non-AP MLD. During the process of data transmission with the current APMLD, the non-AP MLD can receive the BTM request sent by the current AP MLD, and then determine whether the neighbor AP MLD of the current AP MLD supports the tentative association operation. The non-AP MLD does not need to switch channels to listen to the beacon frames sent by the neighbor APMLD to determine whether the neighbor AP MLD supports the tentative association operation, and it will not affect the normal data transmission between the non-AP MLD and the current AP MLD, which can improve the roaming performance of the non-AP MLD.

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

[0009] In an optional implementation, the function indication information may include 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, wherein the first type of tentative association operation refers to performing a tentative association operation through 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 through the air interface for the candidate AP MLD.

[0010] In the above implementation, the first function indicator bit is used to indicate whether the corresponding candidate AP MLD supports the tentative association operation through the air interface. The non-AP MLD can determine whether each candidate AP MLD supports the tentative association operation through the air interface according to the first function indicator bit corresponding to each candidate AP MLD. This helps the non-AP MLD to select a suitable AP MLD from the candidate AP MLDs that support the tentative association operation through the air interface to perform the tentative association operation in advance, so as to reduce the delay caused by performing the association operation when switching the AP MLD.

[0011] In another optional implementation, the function indication information may include 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, wherein the second type of tentative association operation refers to performing a tentative association operation through 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 through the DS.

[0012] In the above implementation, the second function indicator bit indicates whether the corresponding candidate AP MLD supports the tentative association operation through DS, and the non-AP MLD can determine whether each candidate AP MLD supports the tentative association operation through DS according to the second function indicator bit corresponding to each candidate AP MLD, which helps the non-AP MLD to select a suitable AP MLD from the candidate AP MLDs that support the tentative association operation through DS to perform the tentative association operation in advance, so as to reduce the delay caused by performing the association operation when switching the AP MLD. At the same time, the non-AP MLD performs the tentative association operation with the candidate AP MLD through DS. During the process of performing the tentative association operation, the information exchanged between the non-AP MLD and the candidate AP MLD can be forwarded through the current AP MLD, and the non-AP MLD does not need to switch the channel to communicate with the candidate AP MLD directly through the air interface. Therefore, the process of the non-AP MLD performing the tentative association operation with the candidate AP MLD through DS will not affect the normal data transmission between the non-AP MLD and the current AP MLD.

[0013] 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 for the candidate AP MLD, a tentative association operation is performed 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 for the candidate AP MLD, a tentative association operation is preferentially performed through the DS. The process of the non-AP MLD performing a tentative association operation with the candidate AP MLD through the DS will not affect the normal data transmission between the non-AP MLD and the current AP MLD.

[0014] 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 the tentative association operation, and the second indication information may be used to indicate the type of the tentative association operation supported by the candidate AP MLD. The type of the tentative association operation may be the first type or the second type described above. The non-AP MLD may select a suitable AP MLD from the candidate AP MLDs to perform the tentative association operation in advance according to the type of the tentative association operation corresponding to each candidate AP MLD.

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

[0016] 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. 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 for the candidate AP MLD according to 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.

[0017] In the above implementation, the BTM request includes request mode indication information, and the request mode indication information can be used to indicate to the non-AP MLD whether to perform a tentative association operation or a BSS transfer operation next, so that the current AP MLD can send a BTM request to the non-AP MLD, and notify the non-AP MLD in advance through the BTM request to perform a tentative association operation with the recommended candidate AP MLD. When the roaming condition is triggered, the BTM request is sent to the non-AP MLD again to instruct the non-AP MLD to perform a BSS transfer operation to switch the AP MLD. By notifying the non-AP MLD in advance through the BTM request to perform a tentative association operation with the recommended candidate AP MLD, it is possible to avoid the situation in which, in a fast-moving scenario, the non-AP MLD has not completed the tentative association operation and the data transmission with the current AP MLD is interrupted due to poor link quality.

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

[0019] In a second aspect, a communication method is provided, which is 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 receives a basic service set transfer management BTM request sent by the current AP MLD. The BTM request may 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. 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 the candidate AP MLD.

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

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

[0022] In a third aspect, a communication method is provided, which is 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 sends 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; and the current AP MLD receives a BTM response sent by the non-AP MLD.

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

[0024] In an optional implementation manner, the function indication information may include 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.

[0025] In an optional implementation, the function indication information may include 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.

[0026] 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 the 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 the tentative association operation may be the first type or the second type described above.

[0027] In an optional implementation manner, 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.

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

[0029] In a fourth aspect, a communication method is provided, which is 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 sends 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 current AP MLD receives a BTM response sent by the non-AP MLD.

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

[0031] In a fifth aspect, a communication device is provided, which can be applied to a non-AP MLD, where the non-AP MLD is connected to a current AP MLD. The communication device may include:

[0032] The request receiving module is used to receive the basic service set transfer management BTM request sent by the current AP MLD; the BTM request includes the function indication information of the candidate AP MLD; the candidate AP MLD is the neighbor AP MLD of the current AP MLD; the function indication information is used to indicate whether the candidate AP MLD supports the tentative association operation;

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

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

[0035] In an optional implementation, the function indication information may include 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, wherein the first type of tentative association operation refers to a tentative association operation performed over an air interface.

[0036] In an optional implementation manner, 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 through an air interface.

[0037] In an optional implementation, the function indication information may include 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, wherein the second type of tentative association operation refers to a tentative association operation performed through a distributed system DS.

[0038] In an optional implementation manner, 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.

[0039] In an optional implementation, the function indication information may include the above-mentioned first function indication bit and second function indication bit; the association operation module can be specifically used 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, then a tentative association operation is performed on the candidate AP MLD through the air interface.

[0040] 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 the 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 the tentative association operation may be the first type or the second type described above.

[0041] 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. The association operation module may be specifically used to: if the request mode indication information instructs the non-AP MLD to perform a tentative association operation, then initiate a tentative association operation for the candidate AP MLD according to the function indication information of the candidate AP MLD.

[0042] 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 indicates that the non-AP MLD performs a basic service set BSS transfer operation, and connect to the network through the target AP MLD after the BSS transfer.

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

[0044] In a sixth aspect, a communication device is provided, which can be applied to a non-AP MLD, where the non-AP MLD is connected to a current AP MLD. The communication device may include:

[0045] A request receiving module is used 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;

[0046] The association operation module is used 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 neighboring APMLD of the current AP MLD.

[0047] 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 indicates that the non-AP MLD performs a basic service set BSS transfer operation, and connect to the network through the target AP MLD after the BSS transfer.

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

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

[0050] The request sending module is used to send a basic service set transfer management BTM request to the non-AP MLD; the BTM request includes the function indication information of the candidate AP MLD; the candidate AP MLD is the neighbor AP MLD of the current AP MLD; the function indication information is used to indicate whether the candidate AP MLD supports the tentative association operation;

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

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

[0053] In an optional implementation manner, the function indication information may include 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.

[0054] In an optional implementation, the function indication information may include 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.

[0055] 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 the 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 the tentative association operation may be the first type or the second type described above.

[0056] In an optional implementation manner, 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.

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

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

[0059] A request sending module is 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;

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

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

[0062] In a ninth aspect, a communication device is provided, the communication device being a non-AP MLD, the non-AP MLD being connected to a current AP MLD. The communication device comprises a memory and a processor, the memory storing a computer program; the processor being configured to execute the computer program stored in the memory to implement any of the methods described in the first or second aspect above.

[0063] In a tenth aspect, a communication device is provided, which is a current access point multi-link device AP MLD of a non-access point multi-link device non-AP MLD. The communication device includes 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 any method recorded in the third aspect or the fourth aspect.

[0064] 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 execute any of the methods described in the first or second aspect, and the AP MLD can be used to execute any of the methods described in the third or fourth aspect.

[0065] 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 aspect or the second aspect.

[0066] In a thirteenth 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 third aspect or the fourth aspect.

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

[0068] In a fifteenth aspect, a computer program product is provided, comprising computer executable instructions, wherein the computer executable instructions are used to enable a computer to execute any one of the methods provided in the third aspect or the fourth aspect.

[0069] 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

[0070] Figure 1 A schematic diagram of a communication system provided in an embodiment of the present application;

[0071] Figure 2 A schematic diagram of the structure of a non-AP MLD and an AP MLD provided in an embodiment of the present application;

[0072] Figure 3 A schematic diagram of an application scenario provided in an embodiment of the present application;

[0073] Figure 4 A schematic diagram of an interaction process between a non-AP MLD and a current AP MLD provided in an embodiment of the present application;

[0074] Figure 5 A schematic diagram of a frame structure of a BTM request provided in an embodiment of the present application;

[0075] Figure 6 A schematic diagram of the field structure of a BSS termination duration sub-element in a BTM request provided in an embodiment of the present application;

[0076] Figure 7 A schematic diagram of the field structure of a neighbor report element in a BTM request provided in an embodiment of the present application;

[0077] Figure 8 A schematic diagram of an interaction process between a non-AP MLD, a current AP MLD, and a target AP MLD provided in an embodiment of the present application;

[0078] Fig. 9 A schematic diagram of the frame structure of a BTM inquiry frame provided in an embodiment of the present application;

[0079] Fig.10 A schematic diagram of the frame structure of a BTM response frame provided in an embodiment of the present application;

[0080] Fig.11 A schematic diagram of the frame structure of an FT action frame provided in an embodiment of the present application;

[0081] Fig.12 A schematic diagram of another interaction process between a non-AP MLD, a current AP MLD, and a target AP MLD provided in an embodiment of the present application;

[0082] Fig.13 A schematic diagram of another interaction process between a non-AP MLD and a current AP MLD provided in an embodiment of the present application;

[0083] Fig.14 A schematic diagram of a frame structure of another BTM request provided in an embodiment of the present application;

[0084] Fig.15 A structural block diagram of a communication device provided in an embodiment of the present application;

[0085] Fig.16 A structural block diagram of another communication device provided in an embodiment of the present application;

[0086] Fig.17 A schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0088] Before introducing the specific solutions provided by the embodiments of the present application, some 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.

[0089] (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 do not support simultaneous transmit and receive (non-STR).

[0090] (2) Distributed system (DS): It is used to interconnect multiple basic service sets (BSSs) and integrate local area networks (LANs) to build an extended service set (ESS); that is, DS can build an ESS that includes multiple interconnected BSSs, or it can be described as: DS includes multiple interconnected BSSs. BSS is the basic component of 802.11 local area networks. For example, DS can include multiple access point (AP) MLDs, and each AP MLD or each AP in the AP MLD corresponds to a BSS.

[0091] Unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned 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 the multiple objects.

[0092] 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 used in a communication device, and 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 sensing wireless local area network protocol. Although the embodiments of the present application are mainly described by taking the network deploying IEEE 802.11 as an example, it is easy for those skilled in the art to understand that the various aspects involved in the embodiments of the present application can be extended to other networks adopting various standards or protocols, for example, Bluetooth (BLUETOOTH), high-performance wireless local area network (local area network, LAN) (high-performance radio LAN, HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard, mainly used in Europe) and wide area network (wide area network, WAN), WLAN, personal area network (personal area network, PAN) or other networks known now or developed later. The technical solutions of the embodiments of the present application can be applied to various cellular communication systems, for example, the fifth generation (5th generation, 5G) system, new radio (new radio, NR), the future sixth generation (6th generation, 6G) system, etc.

[0093] The communication method provided in the embodiment 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, and 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, and can also be 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.

[0094] For example, in Figure 1 In the communication system shown, non-AP MLD300 can communicate with AP MLD100 and AP MLD200. Non-AP MLD300 can be understood as a device with wireless transceiver function. For example, 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 device. In specific applications, non-AP MLD can be a cellular phone, a mobile phone, a tablet computer, a wearable device, a smart point of sale (POS) machine, a customer-premises equipment (CPE), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a terminal device in industrial control, a terminal device in self driving, a terminal device in remote medical, a terminal device in smart grid, a terminal device in smart city, a terminal in smart home, etc.

[0095] The non-AP MLD may include multiple links, each of which corresponds to a different STA function body. The multiple STA functions usually work on different frequency bands or channels. Each STA function body can be understood as a radio frequency module in the non-AP MLD. Figure 1 In the example, non-AP MLD 300 includes two STA functional bodies, namely STA1 and STA2. Both STA1 and STA2 can operate in the 2.4G frequency band and the 5G frequency band. At a certain moment, STA1 and STA2 can operate in different frequency bands. In other embodiments, the number of STA functional bodies included in the non-AP MLD may be more than two.

[0096] AP MLD100 and AP MLD200 can be understood as devices such as wireless hubs or routers for providing wireless network access services, and can be used as access points for non-AP MLDs to access wired Ethernet backbones.

[0097] Similar to non-AP MLD, AP MLD can include multiple links, which correspond to different AP functional bodies. Multiple AP functional bodies usually work on different frequency bands or channels. Each AP functional body can be understood as a RF transceiver module in AP MLD. Figure 1 In the example, AP MLD100 and AP MLD200 respectively include two AP functional bodies, namely AP1 and AP2. AP1 and AP2 operate in different frequency bands, AP1 operates in the 2.4 GHz frequency band, and AP2 operates in the 5 GHz frequency band. In some embodiments, AP MLD100 and AP MLD200, or AP1 and AP2 in AP MLD100, and AP1 and AP2 in AP MLD200 may belong to the same DS.

[0098] In one possible implementation, Figure 1 The communication system shown may also include other non-AP MLD and / or AP MLD devices, or other devices, and this application does not limit this.

[0099] In some embodiments, Figure 2 As shown, the AP MLD or non-AP MLD may include a physical layer (PHY) (such as Figure 2 The physical layer can be used to process physical layer signals, and the MAC layer can be used to process MAC layer signals. Further, in the MAC layer, it can also be divided into an upper-MAC (UMAC) layer (such as Figure 2 The high MAC shown in FIG. 1 and multiple low-MAC (LMAC) layers (such as Figure 2 As shown in Figure 2, low MAC1 and low MAC2). Figure 2As shown, the multiple AP functions included in the AP MLD are independent of each other in the low MAC layer and PHY, and share the high MAC layer. The multiple STA functions included in the non-AP MLD are independent of each other in the low MAC layer and PHY, and share the high MAC layer. The high MAC layer is connected to multiple low MAC layers respectively, that is, the high MAC layer is shared by multiple links. Each link has its own MAC address in the LMAC layer of the MLD, and the MAC address corresponding to each link can be called a link address (linkaddress). In addition, each MLD also has a MAC address in the UMAC layer of the MLD, and the MAC address corresponding to the MLD can be called an MLD MAC address (MLD address).

[0100] Exemplarily, the high MAC layer mainly completes the allocation of sequence number (SN) and packet number (PN) of MAC service data unit (MSDU) and encryption and decryption operations. The low MAC layer mainly completes the assembly of MAC protocol data unit (MPDU) of each link, channel access, packet sending and reception confirmation operations.

[0101] exist Figure 2 In the AP MLD, the PHY1 layer, the low MAC1 layer and the high MAC layer can be regarded as AP1, and the PHY2 layer, the low MAC2 layer and the high MAC layer can be regarded as AP2. That is, it can be understood that the AP MLD may include multiple AP functional bodies, and the multiple AP functional bodies are independent of each other in the low MAC layer and the PHY layer, and share the high MAC layer. Similarly, in the non-AP MLD, the high MAC layer is also shared by multiple links. The PHY1 layer, the low MAC1 layer and the high MAC layer are regarded as STA1, and the PHY2 layer, the low MAC2 layer and the high MAC layer are regarded as STA2. That is, it can be understood that the non-AP MLD may include multiple STA functional bodies, and the multiple STA functional bodies are independent of each other in the low MAC layer and the PHY layer, and share the high MAC layer. PHY1 of AP1 in the AP MLD and PHY1 of STA1 in the non-AP MLD work on the same channel, and AP1 in the AP MLD and STA1 in the non-AP MLD can be connected through Figure 2 The link 1 shown realizes communication; PHY2 of AP2 in the APMLD and PHY2 of STA2 in the non-AP MLD work on another same channel, and AP2 in the AP MLD and STA2 in the non-AP MLD can realize communication through link 2.

[0102] During the communication process, non-AP MLD can connect to the network through its associated AP MLD. Due to factors such as the movement of non-AP MLD, the AP MLD associated with non-AP MLD may be switched. For example, due to the movement of non-AP MLD, it moves from the coverage of AP MLD1 to the coverage of AP MLD2. At this time, it may be necessary to switch the AP MLD associated with non-AP MLD. This switching process can also be called roaming.

[0103] For example, Figure 3 The figure shows a possible process in which the AP MLD associated with the non-AP MLD switches from AP MLD1 to AP MLD2. Figure 3 As shown in the figure, before switching or roaming, non-AP MLD is associated with AP MLD1, and AP MLD1 is called the current AP MLD. For example, STA1 of non-AP MLD works in the 2.4 frequency band and establishes a link with AP1 of AP MLD1. STA2 of non-AP MLD works in the 5G frequency band and establishes a link with AP2 of AP MLD1.

[0104] Due to factors such as movement, the non-AP MLD moves out of the coverage area of ​​the current AP MLD, namely AP MLD1, and enters the coverage area of ​​APMLD2. For example, Figure 3 As shown in the figure, during the handover or roaming process, non-AP MLD and AP MLD2 are tentatively associated, and a link is established and negotiated with AP MLD2 in advance. Among them, STA1 of non-AP MLD establishes a link with AP1 in AP MLD2, and STA2 of non-AP MLD establishes a link with AP2 in AP MLD2.

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

[0106] In actual communication scenarios, AP MLD1 and AP MLD2 may belong to the same DS, that is, as the non-APMLD moves, the AP MLD associated with the non-AP MLD may switch from the current AP MLD to another adjacent AP MLD in the same DS. Since each AP MLD or each AP in the AP MLD corresponds to a BSS, the above switching process can also be understood as the process of switching the non-AP MLD from the current BSS to another adjacent BSS in the same ESS, which can be called BSS transfer or BSS switching.

[0107] When the non-AP MLD switches from the currently associated AP MLD to the target AP MLD, the non-AP MLD and the target AP MLD need to negotiate the key and transmission capability parameters, and establish a BA session and other association operations. These association operations will increase the delay of the switching process.

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

[0109] [Example 1]

[0110] 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, and the BTM request includes functional indication information of the candidate AP MLD, wherein the candidate AP MLD is a neighbor AP MLD of the current AP MLD, and the functional indication information is used to characterize 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 may 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-APMLD can initiate a tentative association operation for the candidate AP MLD according to the function indication information of the candidate AP MLD carried in the BTM request. Before switching the associated AP MLD, the non-APMLD negotiates the key, capability parameters, operation parameters, and establishes BA session and other association operations 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 that has established the tentative association operation, thereby reducing the delay caused by executing the association operation, realizing fast switching of the BSS, and reducing the data transmission interruption time.

[0111] Figure 4 A flowchart of interaction between a non-AP MLD and a current AP MLD during a process of performing a tentative association operation is shown.

[0112] like Figure 4 As shown, the process may include the following steps:

[0113] S401, the current AP MLD sends a BTM request to the non-AP MLD.

[0114] 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 current AP MLD can send a BTM request to the non-AP MLD, recommending the non-AP MLD to switch to the neighboring AP MLD. The BTM request may include the function indication information of the candidate AP MLD. The candidate AP MLD is the neighbor AP MLD of the current AP MLD. The function indication information is used to characterize whether the candidate AP MLD supports the tentative association operation. The current AP MLD can determine whether each neighbor AP MLD of the current AP MLD supports the tentative association operation through a notification message broadcast in the DS, or by asking the neighbor AP MLD, or by using the information collected by the non-AP MLD through channel scanning. Exemplarily, the BTM request may include function indication information corresponding to one or more candidate AP MLDs.

[0115] In some embodiments, the function indication information may include a first function indication bit for characterizing 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 (over-the-air), which may also be referred to as an Over-the-air tentative association operation. Over-the-air tentative association operation means that a non-AP MLD may perform a tentative association with a candidate AP MLD directly over the air interface. During the tentative association process, the non-AP MLD may establish a data transmission link with the candidate AP MLD. The two parties can also negotiate their transmission capability parameters (for example, the transmission bandwidth and maximum number of streams between the two parties), their key information (such as PTK, group temporal key (GTK), integrity group temporal key (IGTK) and beacon integrity group temporal key (BIGTK), etc.), and their resource allocation information (for example, BA sessions, restricted target wakeup time (r-TWT), etc.).

[0116] Exemplarily, the first function indicator bit may occupy 1 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.

[0117] In some other embodiments, the function indication information may include a second function indication bit for characterizing whether the corresponding 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 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 characterize whether the Over-the-DS tentative association operation can be performed with the candidate AP MLD through the current AP MLD. Exemplarily, if the current AP MLD does not support Over-the-DS tentative association operation, then the second function indication bits of all candidate AP MLDs included in the BTM request indicate that the corresponding candidate AP MLD does not support Over-the-DS tentative association operation.

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

[0119] Exemplarily, the second function indicator bit may occupy 1 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 the Over-the-DS tentative association operation, or the Over-the-DS tentative association operation 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 the Over-the-DS tentative association operation, or the Over-the-DS tentative association operation can be performed with the candidate AP MLD through the current AP MLD.

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

[0121] In some other embodiments, the function indication information may include the above-mentioned first function indication bit and the second function indication bit. Exemplarily, 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 Over-the-air tentative association operation, but does not support Over-the-DS tentative association operation or cannot perform Over-the-DS tentative association operation with the candidate AP MLD through the current AP MLD, and 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 Over-the-air tentative association operation, also supports Over-the-DS tentative association operation or can perform 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 means that the corresponding candidate AP MLD does not support the Over-the-air tentative association operation, indicating that the corresponding candidate AP MLD does not support the tentative association operation. Then, 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 will not support the Over-the-DS tentative association operation.

[0122] 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 occupy 1 bit respectively 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, then 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 2 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.

[0123] In some other embodiments, the second indication information may also be embodied as the first function indicator bit and the second function indicator bit mentioned above, that is, the function indication information may include the first indication information and the first function indicator bit and the second function indicator bit. The first indication information and the first function indicator bit and the second function indicator bit may occupy 1 bit respectively in the BTM request. 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", 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 the Over-the-air tentative association operation but does not support the Over-the-DS tentative association operation. 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 the Over-the-air tentative association operation and also supports the Over-the-DS tentative association operation. If the value of the first indication information is "0", it indicates that the corresponding candidate AP MLD does not support the tentative association operation, then the values ​​of the first function indicator bit and the second function indicator bit are both "0".

[0124] The following describes the frame format of the BTM request sent by the current AP MLD to the non-AP MLD. The BTM request may also be called a BTM request frame or a BTM request frame message.

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

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

[0127] Dialogue token field: can be used to identify the correspondence between a request frame and a response frame. A pair of request frames and response frames carry the same dialogue token value.

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

[0129] In the request mode field, the Preferred candidate list include field can be used to indicate whether to carry the preferred candidate list. 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 APMLD 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 by the entire ESS.

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

[0131] Validity time field: can be used to indicate the number of beacon periods during which the BSS transfer candidate list is valid.

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

[0133] The BSS transfer candidate list field may carry one or more neighbor report elements, each of which carries information about a candidate AP MLD, which is a neighbor AP MLD of the current AP MLD. The candidate AP MLD may be an AP MLD recommended by the current AP MLD, and the non-AP MLD may 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 may include information about one or more candidate AP MLDs, and the information about each candidate AP MLD includes function indication information for the candidate AP MLD, which is used to characterize whether the candidate AP MLD supports a tentative association operation.

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

[0135] Among them, the BSSID field can be used to indicate the BSSID of the corresponding candidate AP MLD (neighbor AP MLD). The BSSID information field can be used to indicate the relevant information of the corresponding BSSID. The Operating class field and the Channel number field can be used to indicate the channel to which the BSSID belongs. The PHY Type field can be used to indicate the physical layer type of the candidate AP MLD. The Optional subelenments field can include a basic multi-link subelement field.

[0136] In an optional implementation, Figure 7 As shown, 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.4GHz / 5GHz AP and member of extended service set with 2.4 / 5GHz co-located AP, On-channel tunneling (OCT) supported with reporting AP, co-located with 6GHz AP, and reserved fields.

[0137] In an embodiment of the present application, the BTM request includes functional indication information of one or more candidate AP MLDs, and the functional indication information of each candidate AP MLD can be carried in a 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 above-mentioned 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 Figure 7 In some other embodiments, the MLD capabilities and operations subfield may be set in the basic multi-link subelement field. The functional indication information of a candidate AP MLD may 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.

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

[0139] Exemplarily, 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 an over-the-air tentative association operation and 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 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 an over-the-air tentative association operation and 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 If the MLD supports the over-the-air tentative association operation but does not support the over-the-DS tentative association operation, or the over-the-DS tentative association operation cannot be performed with the candidate AP MLD through the current AP MLD, the non-AP MLD may perform the over-the-air tentative association operation on the candidate AP MLD; if the function indication information indicates that the candidate AP MLD does not support the tentative association operation, the non-AP MLD does not perform the tentative association operation on the candidate AP MLD.

[0140] In some embodiments, when the BTM request may include function indication information of multiple candidate AP MLDs, if there are at least two candidate AP MLDs supporting over-the-air tentative association operations among the multiple candidate AP MLDs, the non-AP MLD may select at least one candidate AP MLD from the at least two candidate AP MLDs supporting over-the-DS tentative association operations, and perform the over-the-air tentative association operation for the selected candidate AP MLD; if there are at least two candidate AP MLDs supporting over-the-DS tentative association operations among the multiple candidate AP MLDs, the non-AP MLD may select at least one candidate AP MLD from the at least two candidate AP MLDs supporting over-the-DS tentative association operations, and perform the over-the-DS tentative association operation for the selected candidate AP MLD.

[0141] 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 over-the-DS tentative association operations, while other part of the candidate AP MLDs support over-the-air tentative association operations or do not support tentative association operations, the non-AP MLD may preferentially select at least one candidate AP MLD from the candidate AP MLDs that support over-the-DS tentative association operations, and perform the over-the-DS tentative association operation on the selected candidate AP MLD; if some of the multiple candidate AP MLDs support over-the-air tentative association operations, while other part of the candidate AP MLDs do not support tentative association operations, the non-AP MLD may preferentially select at least one candidate AP MLD from the candidate AP MLDs that support over-the-air tentative association operations, and perform the over-the-air tentative association operation on the selected candidate AP MLD.

[0142] 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, and 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 may initiate a tentative association operation for the candidate AP MLD according to the function indication information of the candidate AP MLD carried in the BTM request, and negotiate the key, capability parameters, operation parameters, and establish BA session and other association operations with the candidate AP MLD in advance before switching the associated AP MLD. When the roaming condition is triggered, the non-AP MLD can quickly transmit data with the AP MLD that has established the tentative association operation, thereby reducing the delay caused by performing the association operation and realizing the fast switching of the BSS.

[0143] In some designs, before switching the associated AP MLD, the non-AP MLD needs to select a STA from STA1 or STA2 when transmitting data with the current AP MLD, and switch the STA to the channel where a subordinate AP of the target AP MLD is located, so as to listen to the beacon frame sent by the target AP MLD, and determine whether the target AP MLD supports the tentative association operation according to the indication information contained in the beacon frame. This process will affect the normal data transmission between the non-AP MLD and the current APMLD. For enhanced multi-link single radio (EMLSR) non-AP MLD, EMLSR non-AP MLD means that it can monitor multiple links at the same time. When receiving the initial control frame sent by the APMLD, it can switch the radio modules of other links in the EMLSR link set to the corresponding link that receives the initial control frame to increase the number of transceiver streams. However, at any time, the EMLSR non-AP MLD can only select one link for data transmission and reception. Compared with the multi-radio non-AP MLD, the EMLSR non-AP MLD has only one fully functional STA and can only send and receive data on one link. Therefore, when the EMLSR non-AP MLD switches channels to listen to the beacon frame sent by the target AP MLD, the data transmission between the EMLSR non-AP MLD and the current AP MLD will be interrupted.

[0144] In an 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 APMLD. During the data transmission process with the current AP MLD, the non-AP MLD can receive the BTM request sent by the current AP MLD, and determine whether the candidate APMLD supports the over-the-air tentative association operation and the Over-the-DS tentative association operation according to the function indication information of the candidate AP MLD carried in the BTM request. The non-AP MLD does not need to switch channels to listen to the beacon frame sent by the neighbor AP MLD of the current AP MLD to determine whether the corresponding neighbor AP MLD supports the tentative association operation. Therefore, in the present application, before and after the non-AP MLD receives the BTM request, the normal data transmission between the non-AP MLD and the current AP MLD will not be affected, especially for the EMLSR non-AP MLD, the data transmission between the EMLSR non-AP MLD and the current AP MLD can be avoided from being interrupted, the roaming performance of the non-APMLD can be improved, and the data transmission performance of the network can be improved.

[0145] 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 FIG. 1 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 may be any one of the candidate AP MLDs. Figure 8 As shown, the process may include the following steps:

[0146] S801, the non-AP MLD sends a BTM query frame to the current AP MLD.

[0147] 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 may send a BTM query frame to the current AP MLD.

[0148] For example, the frame format of the BTM inquiry frame is as follows: Fig. 9 As shown, some or all of the following fields may be included: category, radio network management operation, session token, BSS transition query reason, and BSS transition candidate list.

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

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

[0151] Table 1

[0152] Value of the BSS transfer inquiry reason field describe 0 not specified 1 Too high packet loss rate or poor link quality 2 Latency is too high … …

[0153] As shown in Table 1, if the value of the BSS Transfer Query Reason field in the BTM Query frame is 1, it indicates that the reason why the non-APMLD sends the BTM Query frame is that there is a high packet loss rate or poor link quality. If the value of the BSS Transfer Query Reason field in the BTM Query frame is 2, it indicates that the delay of receiving or sending data is too high.

[0154] 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 may carry information about neighboring AP MLDs of the current AP MLD monitored by the non-AP MLD.

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

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

[0157] 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 can be referred to Figure 5 As shown, no further description is given here.

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

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

[0160] The BTM response frame may also be referred to as a BTM response. For example, the frame format of the BTM response frame is as follows: Fig.10As shown, some or all of the following fields may be included: category, radio network management operation, session token, BTM status code (statuscode), BSS termination delay (BSS termination delay), target BSSID (target BSSID) and BSS transfer candidate list.

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

[0162] Dialogue token field: can be used to identify the correspondence between a request frame and a response frame. A pair of request frames and response frames carry the same dialogue token value.

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

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

[0165] Table 2

[0166]

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

[0168] When the value of the BTM status code is 0, the BTM response frame may include a target BSSID field, wherein 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.

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

[0170] exist Figure 8In the illustrated embodiment, 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 the over-the-DS tentative association operation. For example, in an optional embodiment, the BTM request frame includes function indication information of multiple candidate AP MLDs, and there are at least two candidate AP MLDs that support the over-the-DS tentative association operation among the multiple candidate AP MLDs. Then, the non-AP MLD can select any one of the at least two candidate AP MLDs that support the over-the-DS tentative association operation as the target AP MLD. The candidate AP MLD that supports the over-the-DS tentative association operation refers to a candidate AP MLD that can perform an Over-the-DS tentative association operation 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.

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

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

[0173] For example, the non-AP may send a fast BSS transition (FT) probe request to the current AP MLD. The FT probe request may be used to request the establishment of a data transmission link between the non-AP MLD and the target AP MLD. After the current AP MLD receives the FT probe request, it may transparently transmit the FT probe request to the target AP MLD through the DS. The target AP MLD may establish a data transmission link between the target AP MLD and the non-AP MLD based on the FT 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 FT probe response to the current AP MLD through the transparent transmission of the DS. The current AP MLD sends the FT probe response to the non-AP MLD.

[0174] Next, the non-AP MLD can send an FT request to the current AP MLD, and the current AP MLD transparently transmits the FT request to the target AP MLD through the DS. The FT request can be used to request the communication parameters of the target AP MLD. The target AP MLD sends an FT response to the current AP MLD through the DS, and 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.

[0175] 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 through the DS. The FT reassociation request can be used to negotiate the link operation 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 through the DS. The current AP MLD sends an FT reassociation response to the non-AP MLD, and the FT reassociation response includes the link operation parameters between the non-AP MLD and the target AP MLD.

[0176] 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. Fig.11 As shown, the frame structure of the FT action frame may include some or all of the following fields: category, FT action, MAC address of non-AP MLD, MAC address of target AP MLD, and frame body.

[0177] 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, and different FT action frames may have different values ​​set in the FT action field. For example, as shown in Table 3:

[0178] Table 3

[0179]

[0180] From Table 3, we can see that when Fig.11 When the FT action frame is used as an FT reassociation request, the value of the FT action field is set to 7. For the FT query request, FT query response, FT request and FT response mentioned above, the Fig.11 The format of the FT action frame in is the same as that in Table 3, except that the FT action field value 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. The address may be the high MAC layer address of the non-AP MLD, or the low MAC layer address, etc. The MAC address field of the target AP MLD includes the MAC layer address of the target AP MLD, which may be the high MAC layer address of the target AP MLD, or the low MAC layer address, etc.

[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 present application does not limit this.

[0183] Through the above steps, the non-AP MLD completes the tentative association operation with the target AP MLD, that is, the non-AP MLD has established an association with the target AP MLD. The non-AP MLD and the target AP MLD establish an association in advance through the tentative association operation. When the BSS switching (or roaming) condition is triggered, the non-AP MLD activates the association with the target AP MLD and can directly transmit data, thereby reducing the delay caused by the association operation between the non-AP MLD and the target AP MLD during the BSS switching process, and realizing the fast switching of the BSS.

[0184] exist Figure 8 In the illustrated embodiment, 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 the process of data transmission with the current AP MLD, the non-AP MLD can receive the BTM request sent by the current AP MLD. The non-AP MLD determines the target AP MLD that supports the over-the-DS tentative association operation according to the function indication information of the candidate AP MLD carried in the BTM request, and performs a trial association operation between the current AP MLD and the target AP MLD. This process does not require the non-AP MLD's affiliated STA to switch channels, which can ensure that the data transmission between the non-AP MLD and the current AP MLD is not interrupted, that is, it will not affect the normal data transmission between the non-AP MLD and the current AP MLD, which is beneficial to improving the data transmission performance of the network.

[0185] Fig.12 FIG. 2 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 may be any one of the candidate AP MLDs. Fig.12 As shown, 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 can be as follows Fig. 9 As shown, no further description is given here.

[0188] 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 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 can refer to Figure 5 As shown, no further description is given here.

[0191] The non-AP MLD receives the BTM request frame sent by the current AP MLD and 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 can be as follows Fig.10 As shown, no further description is given here.

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

[0195] exist Fig.12 In the illustrated embodiment, 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 the over-the-air tentative association operation. For example, in an optional embodiment, the BTM request frame includes function indication information of multiple candidate AP MLDs, and there are at least two candidate AP MLDs that support the over-the-air tentative association operation among the multiple candidate AP MLDs, then the non-AP MLD can select any one of the at least two candidate AP MLDs that support the over-the-air tentative association operation as the target AP MLD. The non-AP MLD can perform the 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] Exemplarily, the non-AP MLD may send a probe request to the target AP MLD, and the probe request may be used to request the 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, which can be used to request the communication parameters of the target AP MLD. 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 may send a reassociation request to the target AP MLD, and the reassociation request may be used to negotiate the link operation parameters between the non-AP MLD and the target AP MLD. The target AP MLD sends a reassociation response to the non-AP MLD, and the reassociation response includes the link operation 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, that is, the non-AP MLD has established an association with the target AP MLD. The non-AP MLD and the target AP MLD establish an association in advance through the tentative association operation. When the BSS switching (or roaming) condition is triggered, the non-AP MLD activates the association with the target AP MLD and can directly transmit data, thereby reducing the delay caused by the association operation between the non-AP MLD and the target AP MLD during the BSS switching process, and realizing the fast switching of the BSS.

[0201] exist Fig.12In the illustrated embodiment, 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 the process of data transmission with the current AP MLD, the non-AP MLD can receive the BTM request sent by the current AP MLD. The non-AP MLD can determine the target AP MLD that supports the over-the-air tentative association operation according to the function indication information of the candidate AP MLD carried in the BTM request, which helps the non-AP MLD select a suitable neighbor AP MLD from the candidate AP MLD for BSS transfer.

[0202] [Example 2]

[0203] Considering that it takes a certain amount of time for non-AP MLD to perform a tentative association operation, if the non-AP MLD is notified to perform a tentative association operation with the recommended candidate AP MLD only when the link quality between the non-AP MLD and the current AP MLD is already very poor, in a fast-moving scenario, the non-AP MLD may not complete the tentative association operation before the data transmission with the current AP MLD is interrupted due to the poor link quality. Therefore, the current AP MLD can notify the non-AP MLD in advance to perform a tentative association operation with the recommended candidate AP MLD. That is, the current AP MLD can send a BTM request to the non-AP MLD in advance, and notify the non-AP MLD in advance through the BTM request to perform a tentative association operation with the recommended candidate AP MLD. In some designs, after receiving the BTM request sent by the current AP MLD, the non-AP MLD usually performs a BSS transfer. 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, and the request mode indication information is used to indicate to the non-AP MLD whether to perform a tentative association operation or a BSS transfer operation next.

[0204] Fig.13 FIG. 1 shows a flow chart of interaction between a non-AP MLD and a current AP MLD during a tentative association operation. Fig.13 As shown, the process may include the following steps:

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

[0206] 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 current AP MLD can send a BTM request to the non-AP MLD, recommending that the non-AP MLD switch to the neighboring AP MLD. The BTM request may include request mode indication information. The request mode indication information may 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 may be carried in the request mode field of the BTM request. Fig.14 As shown, the frame format of the BTM request frame may include some or all of the following fields: category, wireless 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 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 referred to as a tentative association request. The request mode indication information may occupy 1 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 asking the Non-AP MLD to perform a BSS transfer immediately; 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 to perform a tentative association operation or a BSS transfer operation can be distinguished by setting an existing field in the BTM request. Exemplarily, the request mode indication information can be carried by the disassociation imminent in the request mode field. When the value of disassociation imminent is "0", it indicates that the BTM request is to notify the non-AP MLD to perform a tentative association operation instead of letting the Non-AP MLD perform a BSS transfer immediately; when the value of disassociation imminent is "1", it indicates that the BTM request is to notify 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. Figure 8 or Fig.12 As shown, no further description is given here.

[0213] The non-AP MLD may initiate a tentative association operation for the candidate AP MLD according to the information of the candidate AP MLD carried in the BSS transfer candidate list. Exemplarily, the non-AP MLD may select a target AP MLD that supports the tentative association operation from the candidate AP MLD 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 on the target AP MLD. The operation process may refer to Figure 8 In some other embodiments, the non-AP MLD may perform an over-the-air tentative association operation on the target AP MLD. The operation process may refer to Fig.12 shown.

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

[0216] When it is determined that the BSS transfer condition is met, the current AP MLD can send a second BTM request to the non-AP MLD. The frame format of the second BTM request can also be Fig.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 value of the request mode indication information in the second BTM request is "0", which is used to instruct 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 may activate the association with the target AP MLD and trigger the link switching, switching the transmission link of the non-AP MLD from the current AP MLD to the target AP MLD. Exemplarily, the non-AP MLD sends a DS STA and AP mapping request frame (DS-STA-NOTIFY.request) to the target AP MLD, and the STA and AP mapping request frame may be used to request the target AP MLD to perform data path switching. The target AP MLD sends a context transfer request to the current AP MLD. After receiving the context transfer request, the current AP MLD may choose to deliver the complete MSDU in the receiving buffer to the DS in sequence. After the delivery is completed, the current AP MLD sends a context transfer response (context transferresponse) to the target AP MLD. Alternatively, after receiving the context transfer request, the current AP MLD immediately stops delivering the MSDU to the DS, and then the current AP MLD sends a context transfer response to the target AP MLD. The context transfer response includes the context information of the non-AP MLD, such as block confirmation protocol related information. At the same time, the data in the receiving buffer is transferred to the target AP MLD. The non-APMLD disconnects the data transmission with the current AP MLD and transmits data with the target AP MLD. The current AP MLD deletes the context information of the non-APMLD. After the data path is switched, the non-AP MLD and the target AP MLD can transmit data. The non-AP MLD can use the key negotiated with the target AP MLD when performing the tentative association operation to encrypt and decrypt the transmitted data.

[0220] In the above embodiment, the BTM request includes request mode indication information, which can be used to indicate to the non-AP MLD whether to perform a tentative association operation or a BSS transfer operation next. Thus, the current AP MLD can send a BTM request to the non-AP MLD in advance, and notify the non-AP MLD in advance through the BTM request to perform a tentative association operation with the recommended candidate APMLD, thereby avoiding the situation in which the non-AP MLD has not completed the tentative association operation and the data transmission with the current AP MLD is interrupted due to poor link quality in a fast moving scenario.

[0221] The above-mentioned Embodiment 1 and Embodiment 2 may be implemented separately or cross-implemented. For example, in Embodiment 2, the first BTM request may also include the function indication information of the candidate AP MLD recommended by the current AP MLD, which is used to characterize whether the corresponding candidate AP MLD supports the tentative association operation. 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 may perform a tentative association operation on the candidate AP MLD according to the function indication information of the candidate AP MLD carried in the first BTM request.

[0222] Based on the same design concept as the above method embodiment, the present application embodiment also provides a communication device. The communication device can be applied to non-AP MLD, for example, Figure 1 The communication device can be used to implement the functions of the above method embodiment, so the beneficial effects of the above method embodiment can be achieved. Fig.15 As shown, the 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 can be used to receive a basic service set transfer management BTM request sent by the current AP MLD; the BTM request includes the function indication information of the candidate AP MLD; the candidate AP MLD is the 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. The association operation module 1502 can be used to initiate a tentative association operation for the candidate AP MLD according to the function indication information of the candidate AP MLD.

[0224] In some other embodiments, the request receiving module 1501 may be used 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; wherein 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 indicates that the non-AP MLD performs 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 associated operation module 1502 can be used to execute any step in the communication method. The steps that the request receiving module 1501 and the associated operation module 1502 are responsible for implementing can be specified as needed, and the request receiving module 1501 and the associated operation module 1502 respectively implement different steps in the communication method to realize all functions of the communication device.

[0228] Each functional module in the embodiment of the present application can be integrated into one processor, or each module can exist physically separately, or two or more modules can be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional units.

[0229] Based on the same design concept as the above method embodiment, the present application embodiment also provides a communication device. The communication device can be applied to AP MLD, for example, Figure 1 In the AP MLD100 or AP MLD200 shown, the AP MLD is the current AP MLD of the non-AP MLD. The communication device can be used to implement the functions of the above method embodiment, so the beneficial effects of the above method embodiment can be achieved. Fig.16 As shown, the 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 can be used to send a basic service set transfer management BTM request to the non-AP MLD; the BTM request includes the function indication information of the candidate AP MLD; the candidate AP MLD is the neighbor AP MLD of the current AP MLD; the function indication information is used to indicate whether the candidate AP MLD supports the tentative association operation. The response receiving module 1602 can be used to receive the 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-APMLD 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, and the request sending module 1601 and the response receiving module 1602 respectively implement different steps in the communication method to realize all functions of the communication device.

[0233] Each functional module in the embodiment of the present application can be integrated into one processor, or each module can exist physically separately, or two or more modules can be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional units.

[0234] Based on the same technical concept as the above method embodiment, a communication device is also provided in the embodiment of the present application. The communication device can be Figure 1 The non-AP MLD or AP MLD shown in . The communication device can be used to implement the functions of the above method embodiment, so the beneficial effects of the above method embodiment can be achieved.

[0235] In some embodiments, the structure of the communication device 1700 can be as follows: Fig.17 As shown, it includes 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 through 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] The memory 1702 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, at least one application program, etc.; the data storage area may be used to store user data, etc. In addition, the memory 1702 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0238] The processor 1701 in the communication device 1700 is used to run the computer instructions or programs stored in the memory 1702 to perform the functions of any of the above method embodiments. Exemplarily, if the communication device 1700 is a non-AP MLD, the processor 1701 can be used to perform the following steps: receiving a BTM request sent by the current AP MLD, and initiating a tentative association operation for the candidate AP MLD according to the function indication information of the candidate AP MLD carried in the BTM request; or, the processor 1701 can be used to perform the following steps: receiving 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 performs a tentative association operation, initiating a tentative association operation for the candidate AP MLD; wherein the candidate AP MLD is a neighbor AP MLD of the current AP MLD.

[0239] If the communication device 1700 is an AP MLD, the processor 1701 can be used to perform the following steps: send a BTM request to a non-AP MLD, and receive a BTM response sent by 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 characterize whether the candidate AP MLD supports a tentative association operation; or, the processor 1701 can be used to perform the following steps: send a BTM request to a non-AP MLD, and receive a BTM response sent by 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.

[0240] In some embodiments, the processor 1701 may include one or more processing units, and different processing units may be independent devices or integrated into one or more processors. The processor 1701 may also include a controller, which may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[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 some other embodiments, if the communication device 1700 is a non-AP MLD, the communication device may also use Figure 1 or Figure 2 If the communication device 1700 is an AP MLD, the communication device can also use Figure 1 or Figure 2 The structure of the AP MLD shown is not repeated here.

[0243] It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the network device. In other embodiments of the present application, the chip may include more or fewer components than shown in the figure, or combine certain components, or split 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 also provides a communication system. The communication system can be Figure 1 The communication system shown in , 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 sent by the non-AP MLD. The BTM request includes the function indication information of the candidate AP MLD; the candidate AP MLD is the neighbor AP MLD of the current APMLD; the function indication information is used to characterize whether the candidate AP MLD supports a tentative association operation; or, the following steps can be performed: send a BTM request to a non-AP MLD, and receive a BTM response sent by the non-AP MLD. The BTM request includes the 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.

[0246] Each non-AP MLD may perform the following steps: receiving a BTM request sent by the current AP MLD, and initiating a tentative association operation for the candidate AP MLD according to the function indication information of the candidate AP MLD carried in the BTM request; or, the following steps may be performed: receiving 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 performs a tentative association operation, initiating 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, which includes computer executable instructions. In one embodiment, the computer executable instructions are used to enable a computer to execute the functions of the above method embodiment.

[0248] The computer executable instructions may be stored in a computer readable storage medium. The present application also provides a computer readable storage medium, wherein the computer readable storage medium stores the executable instructions. In one embodiment, the computer executable instructions are used to enable a computer to execute the functions in 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 may be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium. For example, the computer program or instructions may be transferred from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means. The computer readable storage medium may 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 may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disc (DVD); it may also be a semiconductor medium, such as a solid state drive.

[0251] In each embodiment 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 of their variations are intended to cover non-exclusive inclusions, for example, including a series of steps or units. Methods, systems, products or devices are 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 in conjunction with specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, the present specification and the accompanying drawings are merely exemplary illustrations of the schemes defined by the appended claims, and are deemed to have covered any and all modifications, variations, combinations or equivalents within the scope of the present application.

[0253] Obviously, those skilled in the art can 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 also 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-APMLD 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