Communication method and device

Abstract

This application provides a communication method and apparatus for improving the roaming performance of a non-access point multilink device. In the method, a non-AP MLD receives a basic service set transition management (BTM) request transmitted by the current AP MLD. The BTM request may include functional instruction information for a candidate AP MLD, which indicates whether the candidate AP MLD supports provisional association operation. Based on the functional instruction information for the candidate AP MLD, the non-AP MLD may initiate provisional association operation with the candidate AP MLD. This application applies to wireless local area network systems that support IEEE 802.11be next-generation Wi-Fi protocols such as Wi-Fi 8, UHR, or 11bn, Wi-Fi AI, millimeter wave (mmWave), ultra-wideband (UWB), or sensing.

Description

TECHNICAL FIELD

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims the priority of Chinese Patent Application No. 202311252839.X entitled "Communication Method and Apparatus" filed with the China National Intellectual Property Administration on September 25, 2023, the entire content of which is incorporated herein by reference.

[0002] TECHNICAL FIELD Embodiments of this application relate to the field of communication technologies, and in particular, to a communication method and apparatus. BACKGROUND ART

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

[0004] In a process in which the AP MLD associated with the non-AP MLD is switched from a current AP MLD to a target AP MLD, that is, in a non-AP MLD roaming process, association operations such as negotiating a key and transmission capability parameter, and establishing a block acknowledgment (BA) session need to be performed between the non-AP MLD and the target AP MLD. How to reduce the delay caused by performing the association operation and reduce the impact on data transmission of the non-AP MLD is a problem that needs to be resolved in next-generation wireless fidelity (Wi-Fi) roaming. SUMMARY OF THE INVENTION MEANS FOR SOLVING THE PROBLEMS

[0005] Embodiments of the present invention provide a communication method and apparatus for improving the roaming performance of a non-AP MLD.

[0006] According to a first embodiment, a communication method is provided. The method is performed by a non-access point multilink device (non-AP MLD), which is connected to a current access point multilink device (AP MLD). The communication method may include the non-AP MLD receiving a basic service set transition management (BTM) request sent by the current AP MLD, the BTM request possibly including functional indication information for a candidate AP MLD, the candidate AP MLD being a neighboring AP MLD of the current AP MLD, the functional indication information indicating whether the candidate AP MLD supports a provisional association operation, and the non-AP MLD initiating a provisional association operation with respect to the candidate AP MLD based on the functional indication information for the candidate AP MLD.

[0007] In the aforementioned communication method, during the process of data transmission with the current AP MLD, the non-AP MLD may receive a BTM request sent by the current AP MLD. After receiving the BTM request, the non-AP MLD may initiate a provisional association operation with the candidate AP MLD based on the functional instruction information of the candidate AP MLD carried in the BTM request. Before switching to the associated AP MLD, the non-AP MLD may perform association operations such as negotiating keys, capability parameters, and operational parameters with the candidate AP MLD, and establishing a BA session. When a roaming condition is triggered, the non-AP MLD can quickly switch the distributed system DS data path to the AP MLD with which it has established a provisional association operation and transmit data. This reduces the delay caused by performing the association operation and implements high-speed AP MLD switching.

[0008] A candidate AP MLD is a neighboring AP MLD of the current AP MLD. In other words, functional instruction information for the neighboring AP MLDs of the current AP MLD is carried in BTM requests sent by the current AP MLD to the non-AP MLD. In the process of data transmission with the current AP MLD, the non-AP MLD may receive the BTM request sent by the current AP MLD and determine whether the neighboring AP MLD of the current AP MLD supports provisional association operation. The non-AP MLD does not need to determine whether the neighboring AP MLD supports provisional association operation by switching channels to listen for beacon frames sent by the neighboring AP MLD, normal data transmission between the non-AP MLD and the current AP MLD is unaffected, thereby improving the roaming performance of the non-AP MLD.

[0009] In an optional selection implementation, the functional instruction information for candidate AP MLDs is carried in the neighbor report element field of the BTM request.

[0010] In an optional implementation, the function instruction information may include a first function instruction bit, which indicates whether the candidate AP MLD supports a first type of quasi-association operation, the first type of quasi-association operation being a quasi-association operation performed through the air interface. If the first function instruction bit indicates that the corresponding candidate AP MLD supports a first type of quasi-association operation, the quasi-association operation is performed to the candidate AP MLD through the air interface.

[0011] In the aforementioned implementation, the first functional instruction bit indicates whether the corresponding candidate AP MLD supports performing a provisional association operation through the air interface, and the non-AP MLD may determine whether each candidate AP MLD supports performing a provisional association operation through the air interface based on the first functional instruction bit corresponding to each candidate AP MLD. This helps the non-AP MLD to select the appropriate AP MLD from the candidate AP MLDs that support performing a provisional association operation through the air interface in order to perform a provisional association operation in advance, thereby reducing the delay caused by performing the association operation during AP MLD switching.

[0012] In other optional implementations, the function instruction information may include a second function instruction bit, which indicates whether the candidate AP MLD supports a second type of quasi-association operation, the second type of quasi-association operation being a quasi-association operation performed through the distributed system DS. If the second function instruction bit indicates that the corresponding candidate AP MLD supports a second type of quasi-association operation, the quasi-association operation is performed on the candidate AP MLD through the DS.

[0013] In the aforementioned implementation, the second function instruction bit indicates whether the corresponding candidate AP MLD supports performing a provisional association operation through the DS, and the non-AP MLD may determine whether each candidate AP MLD supports performing a provisional association operation through the DS based on the second function instruction bit corresponding to each candidate AP MLD. This helps the non-AP MLD to select an appropriate AP MLD from the candidate AP MLDs that support performing a provisional association operation through the DS in order to perform a provisional association operation in advance in order to reduce the delay caused by performing an association operation during AP MLD switching. The non-AP MLD also performs a provisional association operation with the candidate AP MLD through the DS. During the process of performing a provisional association operation, the information exchanged between the non-AP MLD and the candidate AP MLD may be transferred through the current AP MLD, and the non-AP MLD does not need to switch channels to communicate directly with the candidate AP MLD through the air interface. Therefore, the process by which a non-AP MLD performs a provisional association operation with a candidate AP MLD via DS does not affect normal data transmission between the non-AP MLD and the current AP MLD.

[0014] In other optional implementations, the function instruction information may include a first function instruction bit and a second function instruction bit. If the first function instruction bit indicates that the candidate AP MLD supports a first type of quasi-association operation and the second function instruction bit indicates that the candidate AP MLD does not support a second type of quasi-association operation, the quasi-association operation is performed to the candidate AP MLD via the air interface. If the first function instruction bit indicates that the candidate AP MLD supports a first type of quasi-association operation and the second function instruction bit indicates that the candidate AP MLD supports a second type of quasi-association operation, the quasi-association operation is preferentially performed to the candidate AP MLD via the DS. The process by which a non-AP MLD performs a quasi-association operation with a candidate AP MLD via the DS does not affect normal data transmission between the non-AP MLD and the current AP MLD.

[0015] In other optional implementations, the functional instruction information may include first and second instruction information. The first instruction information may indicate whether a candidate AP MLD supports a provisional association operation, and the second instruction information may indicate the type of provisional association operation supported by the candidate AP MLD. The type of provisional association operation may be either the first type or the second type. A non-AP MLD may pre-perform a provisional association operation by selecting an appropriate AP MLD from the candidate AP MLDs based on the type of provisional association operation corresponding to each candidate AP MLD.

[0016] In an optional implementation, the second instruction information may specifically be represented as the first function instruction bit and the second function instruction bit. In other words, the function instruction information may include the first instruction information, the first function instruction bit, and the second function instruction bit.

[0017] In optional implementations, a BTM request may further include request mode instruction information, which may instruct a non-AP MLD to perform a provisional association operation or a basic service set (BSS) transition operation. If the request mode instruction information indicates that the non-AP MLD should perform a provisional association operation, the non-AP MLD may initiate a provisional association operation with the candidate AP MLD based on the candidate AP MLD's functional instruction information. If the request mode instruction information instructs the non-AP MLD to perform a basic service set (BSS) transition operation, the non-AP MLD may perform the BSS transition operation and connect to the network through the target AP MLD after the BSS transition.

[0018] In the aforementioned implementation, the BTM request includes request mode indication information, which may indicate whether the non-AP MLD will subsequently perform a provisional association operation or a BSS transition operation. Therefore, the current AP MLD can send a BTM request to the non-AP MLD to notify it in advance to perform a provisional association operation with the recommended candidate AP MLD by using the BTM request, and when the roaming condition is triggered, it can send a BTM request to the non-AP MLD to instruct it to perform a BSS transition operation for AP MLD switching. The BTM request is used to notify the non-AP MLD in advance to perform a provisional association operation with the recommended candidate AP MLD, thus avoiding cases in high-speed travel scenarios where data transmission with the current AP MLD is interrupted due to poor link quality before the non-AP MLD completes the provisional association operation.

[0019] In optional implementations, request mode indication information can be carried in the request mode field of the BTM request.

[0020] According to a second aspect, a communication method is provided. The method is performed by a non-access point multilink device (non-AP MLD), which is connected to a current access point multilink device (AP MLD). The communication method includes the non-AP MLD receiving a basic service set transition management (BTM) request transmitted by the current AP MLD, the BTM request which may include request mode instruction information, which may instruct the non-AP MLD to perform a provisional association operation or a basic service set transition operation, and if the request mode instruction information instructs the non-AP MLD to perform a provisional association operation, the non-AP MLD initiating a provisional association operation with respect to a candidate AP MLD.

[0021] In an optional implementation, if the request mode instruction information instructs the non-AP MLD to perform a BSS transition operation, the non-AP MLD will perform the BSS transition operation and, after the BSS transition, connect to the network through the target AP MLD.

[0022] In optional implementations, request mode indication information can be carried in the request mode field of the BTM request.

[0023] According to a third aspect, a communication method is provided. The method is performed by the current access point multilink device AP MLD of a non-access point multilink device non-AP MLD. The communication method may include the current AP MLD sending a basic service set transition management BTM request to the non-AP MLD, the BTM request including functional indication information for a candidate AP MLD, the candidate AP MLD being a neighboring AP MLD of the current AP MLD, the functional indication information indicating whether the candidate AP MLD supports provisional association operation, and the current AP MLD receiving the BTM response sent by the non-AP MLD.

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

[0025] In an optional implementation, the capability indication information may include a first capability indication bit, where the first capability indication bit indicates whether a candidate AP MLD supports a first type of provisional association operation, and the first type of provisional association operation is a provisional association operation performed over the air interface.

[0026] In an optional implementation, the capability indication information may include a second capability indication bit, where the second capability indication bit indicates whether the candidate AP MLD supports a second type of provisional association operation, and the second type of provisional association operation is a provisional association operation performed through the distribution system DS.

[0027] In an optional implementation, the capability indication information may include first indication information and second indication information. The first indication information may indicate whether the candidate AP MLD supports a provisional association operation, and the second indication information may indicate the type of provisional association operation supported by the candidate AP MLD. The type of the provisional association operation may be the first type or the second type.

[0028] In an optional implementation, the BTM request may further include request mode indication information, and the request mode indication information may instruct a non-AP MLD to perform a provisional association operation or a basic service set BSS transition operation.

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

[0030] According to a fourth aspect, a communication method is provided. The method is performed by the current access point multilink device AP MLD of a non-access point multilink device non-AP MLD. The communication method may include the current AP MLD sending a basic service set transition management BTM request to the non-AP MLD, the BTM request including request mode instruction information, the request mode instruction information instructing the non-AP MLD to perform a provisional association operation or a basic service set BSS transition operation, and the current AP MLD receiving the BTM response sent by the non-AP MLD.

[0031] In optional implementations, request mode indication information can be carried in the request mode field of the BTM request.

[0032] According to a fifth aspect, a communication device is provided. The device may be used in a non-access point multilink device (non-AP MLD), which is connected to a current access point multilink device (AP MLD). The communication device is A request receiving module configured to receive a basic service set transition management BTM request sent by the current AP MLD, wherein the BTM request includes functional instruction information for a candidate AP MLD, the candidate AP MLD is a neighboring AP MLD of the current AP MLD, and the functional instruction information indicates whether the candidate AP MLD supports provisional association operation. This may include an association operation module configured to initiate a provisional association operation with a candidate AP MLD based on the functional instruction information of the candidate AP MLD.

[0033] In an optional selection implementation, the functional instruction information for candidate AP MLDs is carried in the neighbor report element field of the BTM request.

[0034] In an optional implementation, the function instruction information may include a first function instruction bit, which indicates whether the candidate AP MLD supports a first type of quasi-association operation, the first type of quasi-association operation being a quasi-association operation performed through an air interface.

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

[0036] In an optional implementation, the function instruction information may include a second function instruction bit, which indicates whether the candidate AP MLD supports a second type of quasi-association operation, the second type of quasi-association operation being a quasi-association operation performed through a distributed system DS.

[0037] In an optional implementation, the association operation module may be configured to perform a provisional association operation to a candidate AP MLD via the DS, specifically if the second function instruction bit indicates that the corresponding candidate AP MLD supports a second type of provisional association operation.

[0038] In an optional implementation, the function instruction information may include a first function instruction bit and a second function instruction bit, and the association operation module may be configured to perform a provisional association operation to the candidate AP MLD via the air interface if the first function instruction bit indicates that the candidate AP MLD supports a first type of provisional association operation, and the second function instruction bit indicates that the candidate AP MLD does not support a second type of provisional association operation.

[0039] In an optional implementation, the functional instruction information may include first and second instruction information. The first instruction information may indicate whether the candidate AP MLD supports a provisional association operation, and the second instruction information may indicate the type of provisional association operation supported by the candidate AP MLD. The type of provisional association operation may be the first type or the second type.

[0040] In optional implementations, the BTM request may further include request mode instruction information, which may instruct a non-AP MLD to perform a provisional association operation or a basic service set BSS transition operation. The association operation module may be specifically configured to initiate a provisional association operation for a candidate AP MLD based on the candidate AP MLD's function instruction information if the request mode instruction information indicates that the non-AP MLD should perform a provisional association operation.

[0041] In an optional implementation, the communication device may further include a transition operation module configured to perform a basic service set (BSS) transition operation when the request mode instruction information instructs the non-AP MLD to perform a BSS transition operation, and to connect to the network through the target AP MLD after the BSS transition.

[0042] In optional implementations, request mode indication information can be carried in the request mode field of the BTM request.

[0043] According to the sixth aspect, a communication device is provided. The device may be used in a non-access point multilink device (non-AP MLD), which is connected to the current access point multilink device (AP MLD). The communication device is A request receiving module configured to receive a Basic Service Set Transition Management (BTM) request sent by the current AP MLD, wherein the BTM request includes request mode instruction information, and the request mode instruction information instructs the non-AP MLD to perform a provisional association operation or a Basic Service Set (BSS) transition operation. The association operation module may include an association operation module configured to initiate a provisional association operation with a candidate AP MLD when the request mode instruction information indicates that a non-AP MLD will perform a provisional association operation, wherein the candidate AP MLD is a neighboring AP MLD of the current AP MLD.

[0044] In an optional implementation, the communication device may further include a transition operation module configured to perform a basic service set (BSS) transition operation when the request mode instruction information instructs the non-AP MLD to perform a BSS transition operation, and to connect to the network through the target AP MLD after the BSS transition.

[0045] In optional implementations, request mode indication information can be carried in the request mode field of the BTM request.

[0046] According to the seventh aspect, a communication device is provided. The device may be used in a current access point multilink device (AP MLD) of a non-access point multilink device (non-AP MLD). The communication device is A request sending module configured to send a basic service set transition management BTM request to a non-AP MLD, wherein the BTM request includes functional instruction information for a candidate AP MLD, the candidate AP MLD is a neighboring AP MLD of the current AP MLD, and the functional instruction information indicates whether the candidate AP MLD supports provisional association operation. It may include a response receiving module configured to receive BTM responses sent by a non-AP MLD.

[0047] In optional implementations, function instruction information is carried in the neighbor report element field of the BTM request.

[0048] In an optional implementation, the function instruction information may include a first function instruction bit, which indicates whether the candidate AP MLD supports a first type of quasi-association operation, the first type of quasi-association operation being a quasi-association operation performed through an air interface.

[0049] In an optional implementation, the function instruction information may include a second function instruction bit, which indicates whether the candidate AP MLD supports a second type of quasi-association operation, the second type of quasi-association operation being a quasi-association operation performed through a distributed system DS.

[0050] In an optional implementation, the functional instruction information may include first and second instruction information. The first instruction information may indicate whether the candidate AP MLD supports a provisional association operation, and the second instruction information may indicate the type of provisional association operation supported by the candidate AP MLD. The type of provisional association operation may be the first type or the second type.

[0051] In optional implementations, a BTM request may further include request mode instruction information, which may instruct a non-AP MLD to perform a provisional association operation or a basic service set BSS transition operation.

[0052] In optional implementations, request mode indication information can be carried in the request mode field of the BTM request.

[0053] According to the eighth aspect, a communication device is provided. The device may be used in a current access point multilink device (AP MLD) of a non-access point multilink device (non-AP MLD). The communication device is A request sending module configured to send a Basic Service Set Transition Management (BTM) request to a non-AP MLD, wherein the BTM request includes request mode instruction information, and the request mode instruction information instructs the non-AP MLD to perform a provisional association operation or a Basic Service Set (BSS) transition operation. It may include a response receiving module configured to receive BTM responses sent by a non-AP MLD.

[0054] In optional implementations, request mode indication information can be carried in the request mode field of the BTM request.

[0055] According to the ninth aspect, a communication device is provided. The communication device is a non-access point multilink device (non-AP MLD), which is connected to a current access point multilink device (AP MLD). The communication device includes memory and a processor. The memory stores a computer program. The processor is configured to execute the computer program stored in memory and to perform any method described in the first or second aspect.

[0056] According to the tenth aspect, a communication device is provided. The communication device is an access point multilink device (AP MLD), which is a non-access point multilink device (non-AP MLD). The communication device includes memory and a processor. The memory stores a computer program. The processor is configured to execute the computer program stored in the memory and to perform any method described in the third or fourth aspect.

[0057] According to the eleventh aspect, a communication system is provided that includes a non-access point multilink device (non-AP MLD) and an access point multilink device (AP MLD). The non-AP MLD may be configured to perform any of the methods described in the first or second aspect, and the AP MLD may be configured to perform any of the methods described in the third or fourth aspect.

[0058] According to the twelfth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer-executable instructions, which are used to enable a computer to perform any method provided in the first or second aspect.

[0059] According to the 13th aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer-executable instructions, which are used to enable a computer to perform any method provided in the third or fourth aspect.

[0060] According to the fourteenth aspect, a computer program product is provided which includes computer-executable instructions. The computer-executable instructions are used to enable a computer to perform any of the methods provided in the first or second aspect.

[0061] According to the 15th aspect, a computer program product is provided which includes computer-executable instructions. The computer-executable instructions are used to enable the computer to perform any method provided in the third or fourth aspect.

[0062] For technical effects that can be achieved in any one of the second through fifteenth embodiments, please refer to the description of beneficial effects in the first embodiment. Further details are not described herein. [Brief explanation of the drawing]

[0063] [Figure 1] This figure shows a communication system according to an embodiment of the present invention.

[0064] [Figure 2] This figure shows the structures of non-AP MLD and AP MLD according to the embodiments of the present invention.

[0065] [Figure 3] This is a schematic diagram illustrating an application scenario according to the embodiment of the present invention.

[0066] [Figure 4] This is a schematic flowchart illustrating the interaction between the non-AP MLD according to the embodiment of the present invention and the current AP MLD.

[0067] [Figure 5] This figure shows the frame structure of a BTM request according to an embodiment of the present invention.

[0068] [Figure 6] This is a structural diagram showing the BSS termination duration sub-element field in a BTM request according to an embodiment of the present invention.

[0069] [Figure 7] This is a structural diagram showing the neighbor report element field in a BTM request according to an embodiment of the present invention.

[0070] [Figure 8] This is a schematic flowchart illustrating the interaction between the non-AP MLD, the current AP MLD, and the target AP MLD according to the embodiment of the present invention.

[0071] [Figure 9] This figure shows the frame structure of a BTM query frame according to an embodiment of the present invention.

[0072] [Figure 10] This figure shows the frame structure of the BTM response frame according to the embodiment of the present invention.

[0073] [Figure 11] This figure shows the frame structure of the FT action frame according to an embodiment of the present invention.

[0074] [Figure 12] This is another schematic flowchart illustrating the interaction between the non-AP MLD, the current AP MLD, and the target AP MLD according to the embodiment of the present invention.

[0075] [Figure 13] This is another schematic flowchart illustrating the interaction between a non-AP MLD and a current AP MLD according to an embodiment of the present invention.

[0076] [Figure 14] This figure shows the frame structure of another BTM request according to an embodiment of the present invention.

[0077] [Figure 15] This is a block diagram of the structure of a communication device according to an embodiment of the present invention.

[0078] [Figure 16] This is a block diagram of the structure of another communication device according to an embodiment of the present invention.

[0079] [Figure 17] This is a diagram showing the structure of a communication device according to an embodiment of the present invention. [Modes for carrying out the invention]

[0080] To further clarify the purpose, technical solutions, and advantages of the embodiments of this application, the embodiments are described in more detail below with reference to the accompanying drawings. Specific descriptions of operation, functions, etc., in the method embodiments may also apply to the apparatus or system embodiments.

[0081] Before describing the specific solutions provided in the embodiments of this application, some terms used in this application are explained and described in order to facilitate understanding by those skilled in the art, but are not intended to be limiting.

[0082] (1) Multi-link device (MLD): A device having multi-link aggregation capabilities may be referred to as an MLD. For example, a device may have multiple radio frequency modules operating simultaneously, each operating separately in different frequency bands / channels. When the distance between the channels on which two radio frequency modules operate within a single device is sufficiently large, the two radio frequency modules can operate independently without interfering with each other. In the IEEE 802.11 Wi-Fi extremely high throughput (EHT) scheme, MLDs are used to improve the transmission rate. In some embodiments, if transmission on one link and reception on the other link can occur simultaneously for any two links of an MLD, then the two links are considered to support simultaneous transmit and receive (STR) capability. Otherwise, the two links are considered not to support simultaneous transmit and receive capability. In other words, non-STR transmission and reception occurs on the two links.

[0083] (2) Distributed system (DS): A distributed system is configured to interconnect multiple basic service sets (BSSs) and integrate a local area network (LAN) to build an extended service set (ESS). In other words, a DS can build an ESS, and an ESS contains multiple interconnected BSSs. Alternatively, it can be described as follows: A DS contains multiple interconnected BSSs. A BSS is the basic part of a local area network 802.11. For example, a DS contains multiple access point (AP) MLDs, and each AP MLD or each AP within an AP MLD may correspond to one BSS.

[0084] Unless otherwise specified, in the embodiments of this application, ordinal numbers such as "first" and "second" are used to distinguish between multiple subjects and are not intended to limit the order, chronological order, priority, or importance of the multiple subjects.

[0085] Embodiments of the present invention may be applied to wireless local area network (WLAN) systems, and embodiments of the present invention may be applied to Institute of Electrical and Electronics Engineers (IEEE) 802.11 series protocols such as 802.11 be and 802.11 bf, and future 802.11 protocols used in WLANs. The methods provided in embodiments of the present invention can be implemented by communication devices in wireless communication systems, chips or circuits applied to communication devices, etc. Correspondingly, the communication device supports communication by using IEEE 802.11 series protocols. For example, the communication device supports IEEE 802.11be such as Wi-Fi 8, UHR, and 11bn, next-generation Wi-Fi protocols such as Wi-Fi AI, and wireless local area network protocols such as millimeter wave (mmWave), ultra-wideband (UWB), and sensing. While embodiments of this application are primarily described using networks deployed under IEEE 802.11 as examples, those skilled in the art will readily understand that aspects of embodiments of this application can be extended to other networks using various standards or protocols, such as Bluetooth (BLUETOOTH®), high-performance radio local area networks (LANs) (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard, mainly used in Europe), wide area networks (WANs), WLANs, personal area networks (PANs), or other known or subsequently developed networks. The technical solutions in embodiments of this application can be applied to various cellular communication systems, such as fifth-generation (5G) systems, new radio (NR) systems, and future sixth-generation (6G) systems.

[0086] The communication method provided in the embodiments of the present application may be applied to the following communication system: The communication system may include at least one non-access point device and at least two access point devices. The non-access point device and the access point devices may communicate with each other. The access point devices may provide wireless network access services to the non-access point device. The non-access point device may be referred to as a station (STA) device. In some embodiments, the non-access point device may be a multilink device. When the non-access point device is a multilink device, it may be referred to as a non-access point (non-AP) MLD or an STA MLD. Similarly, the access point device may be a multilink device. When the access point device is a multilink device, it may be referred to as an AP MLD.

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

[0088] A non-AP MLD may include multiple links, each of which may correspond to a different STA function. These multiple STA functions typically operate on different frequency bands or channels, and each STA function can be understood as a radio frequency module in the non-AP MLD. In the example in Figure 1, the non-AP MLD 300 includes two STA functions, designated STA1 and STA2, respectively. Both STA1 and STA2 may operate in the 2.4 GHz and 5 GHz frequency bands. At some point, STA1 and STA2 may operate in different frequency bands. In other embodiments, the number of STA functions included in a non-AP MLD may be greater than two.

[0089] AP MLD 100 and AP MLD 200 may be understood as wireless hubs or router-like devices configured to provide wireless network access services, respectively, and may be used as access points to non-AP MLDs to access a wired Ethernet backbone.

[0090] Similar to non-AP MLDs, AP MLDs can contain multiple links. Each link corresponds to a different AP function. Multiple AP functions typically operate on different frequency bands or channels. Each AP function can be understood as a radio frequency transceiver module within the AP MLD. In the example shown in Figure 1, AP MLD 100 and AP MLD 200 each contain two AP functions, referred to as AP1 and AP2, respectively. AP1 and AP2 operate on 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 MLD 100 and AP MLD 200, or AP1 and AP2 within AP MLD 100 and AP1 and AP2 within AP MLD 200, may belong to the same DS.

[0091] In possible implementations, the communication system shown in Figure 1 may further include other non-AP MLDs and / or other AP MLD-like devices, other devices, etc. This is not limited to the present invention.

[0092] In some embodiments, as shown in Figure 2, an AP MLD or non-AP MLD may include a physical layer (PHY) (PHY1 and PHY2 shown in Figure 2) and a medium access control (MAC) layer. The physical layer may be used to process physical layer signals, and the MAC layer may be used to process MAC layer signals. Furthermore, the MAC layer may be further divided into an upper-MAC (UMAC) layer (upper MAC shown in Figure 2) and multiple lower-MAC (LMAC) layers (lower MAC 1 and lower MAC 2 shown in Figure 2). As shown in Figure 2, multiple AP functions included in an AP MLD are independent of each other in the lower MAC layer and PHY, and share the upper MAC layer. Multiple STA functions included in a non-AP MLD are independent of each other in the lower MAC layer and PHY, and share the upper MAC layer. The upper MAC layer is individually connected to multiple lower MAC layers; that is, the upper 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 may be called the link address. In addition, each MLD also has a MAC address in the UMAC layer of the MLD, and the MAC address corresponding to the MLD may be called the MLD MAC address.

[0093] For example, the upper MAC layer primarily completes operations such as sequence number (SN) assignment, packet number (PN) assignment, and encryption / decryption of MAC service data units (MSDUs). The lower MAC layer primarily completes operations such as assembly of MAC protocol data units (MPDUs) for lower MAC layer links, channel access, and packet transmission and acknowledgment.

[0094] In Figure 2, in the AP MLD, the PHY1 layer, low MAC1 layer, and upper MAC layer may be considered as AP1, and the PHY2 layer, low MAC2 layer, and upper MAC layer may be considered as AP2. In other words, an AP MLD may contain multiple AP functions, and it can be understood that these multiple AP functions are independent of each other in the lower MAC and PHY layers, and share the upper MAC layer. Similarly, in a non-AP MLD, the upper MAC layer is also shared by multiple links, and the PHY1 layer, low MAC1 layer, and upper MAC layer may be considered as STA1, and the PHY2 layer, low MAC2 layer, and upper MAC layer may be considered as STA2. In other words, a non-AP MLD may contain multiple STA functions, and it can be understood that these multiple STA functions are independent of each other in the lower MAC and PHY layers, and share the upper MAC layer. The PHY1 of AP1 in the AP MLD and the PHY1 of STA1 in the non-AP MLD operate on the same channel, and the AP1 in the AP MLD and the STA1 in the non-AP MLD can communicate through Link 1 as shown in Figure 2. The PHY2 of AP2 in the AP MLD and the PHY2 of STA2 in the non-AP MLD operate on other identical channels, and the AP2 in the AP MLD and the STA2 in the non-AP MLD can communicate through Link 2.

[0095] In the communication process, a non-AP MLD may connect to the network through an AP MLD associated with it. Factors such as the movement of a non-AP MLD may cause the associated AP MLD to switch. For example, the movement of a non-AP MLD causes it to move from the coverage of AP MLD1 to the coverage of AP MLD2. In this case, the AP MLD associated with the non-AP MLD may need to switch, and this switching process can be called roaming.

[0096] For example, Figure 3 illustrates a possible process in which an AP MLD associated with a non-AP MLD switches from AP MLD 1 to AP MLD 2. As shown in Figure 3, prior to switching or roaming, the non-AP MLD is associated with AP MLD1, which is referred to as the current AP MLD. For example, STA1 of the non-AP MLD operates in the 2.4 GHz frequency band and establishes a link with AP1 of AP MLD1. STA2 of the non-AP MLD operates in the 5 GHz frequency band and establishes a link with AP2 of AP MLD1.

[0097] Due to factors such as movement, a non-AP MLD leaves the coverage area of ​​the current AP MLD, i.e., AP MLD 1, and enters the coverage area of ​​AP MLD 2. For example, as shown in Figure 3, during a switching or roaming process, a non-AP MLD performs a provisional association with AP MLD2, establishes a link with AP MLD2, and negotiates with AP MLD2 in advance. STA1 of the non-AP MLD establishes a link with AP1 within AP MLD2, and STA2 of the non-AP MLD establishes a link with AP2 within AP MLD2.

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

[0099] In actual communication scenarios, AP MLD1 and AP MLD2 may belong to the same DS. In other words, when a non-AP MLD moves, the AP MLD associated with the non-AP MLD may switch from the current AP MLD to another neighboring AP MLD in the same DS. Since each AP MLD or each AP within an AP MLD corresponds to one BSS, the switching process may also be understood as the process by which a non-AP MLD switches from its current BSS to another neighboring BSS in the same ESS, and may be referred to as a BSS transition or BSS switch.

[0100] The process of switching a non-AP MLD from its currently associated AP MLD to a target AP MLD requires association operations between the non-AP MLD and the target AP MLD, such as negotiating keys and transmit capability parameters, and establishing a BA session. These association operations increase the delay of the switching process.

[0101] This application provides the following embodiments applicable to the aforementioned AP MLD switching scenario. [Embodiment 1]

[0102] In this embodiment of the present application, before switching the associated AP MLD, a non-AP MLD may receive a basic service set transition management (BSS transition management, BTM) request sent by the current AP MLD, where the BTM request includes functional indication information for a candidate AP MLD, the candidate AP MLD being a neighboring AP MLD of the current AP MLD, and the functional indication information indicating whether the candidate AP MLD supports a provisional association operation. Based on the functional indication information for the candidate AP MLD, the non-AP MLD may initiate a provisional association operation for the candidate AP MLD. In some application scenarios, the provisional association operation may also be referred to as a hot backup operation. In this embodiment of the present application, during the process of data transmission with the current AP MLD, the non-AP MLD may receive a BTM request sent by the current AP MLD. Normal data transmission between the non-AP MLD and the current AP MLD is unaffected before and after the BTM request is received. This helps improve the data transmission performance of the network. After receiving a BTM request, a non-AP MLD may initiate a provisional association operation with the candidate AP MLD based on the functional instruction information of the candidate AP MLD carried in the BTM request. This association operation may include negotiating with the candidate AP MLD in advance regarding keys, capability parameters, and operational parameters, as well as establishing a BA session, before switching to the associated AP MLD. When a roaming condition is triggered, the non-AP MLD may rapidly transmit data with the AP MLD with which it has established a provisional association operation, thereby reducing delays caused by the association operation, implementing a fast BSS transition, and reducing data transmission interruption time.

[0103] Figure 4 is a flowchart illustrating the interaction between a non-AP MLD and a current AP MLD in the process of performing a provisional association operation. As shown in Figure 4, this process may include the following steps.

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

[0105] A data transmission link exists between the non-AP MLD and the current AP MLD. If the link quality of the non-AP MLD deteriorates, the current AP MLD may send a BTM request to the non-AP MLD recommending that it switch to a neighboring AP MLD. The BTM request may include functional indication information for a candidate AP MLD, which is a neighboring AP MLD of the current AP MLD, and the functional indication information indicates whether the candidate AP MLD supports provisional association operation. The current AP MLD may determine whether each of its neighboring AP MLDs supports provisional association operation by using notification messages broadcast in the DS, by querying neighboring AP MLDs, or by using information collected by the non-AP MLD through channel scanning. For example, the BTM request may include functional indication information corresponding to one or more candidate AP MLDs.

[0106] In some embodiments, the functional instruction information may include a first functional instruction bit indicating whether the corresponding candidate AP MLD supports a first type of provisional association operation. The first type of provisional association operation is an over-the-air provisional association operation performed over an air interface and may be referred to as an over-the-air provisional association operation. An over-the-air provisional association operation means that a non-AP MLD can directly perform a provisional association with a candidate AP MLD over a radio interface. In the provisional association process, the non-AP MLD can establish a data transmission link with the candidate AP MLD. The transmit capability parameters of the non-AP MLD and candidate AP MLD (e.g., transmit bandwidth and maximum stream amount between the non-AP MLD and candidate AP MLD), key information of the non-AP MLD and candidate AP MLD (e.g., PTK, group temporal key (GTK), integrity group temporal key (IGTK), and beacon integrity group temporal key (BIGTK)), and resource allocation information of the non-AP MLD and candidate AP MLD (e.g., BA sessions and restricted target wakeup time (r-TWT)) may be further negotiated.

[0107] For example, the first function instruction bit may occupy one bit in the BTM request. If the value of the first function instruction bit is "0", this may indicate that the corresponding candidate AP MLD does not support over-the-air quasi-association operation; or if the value of the first function instruction bit is "1", this may indicate that the corresponding candidate AP MLD supports over-the-air quasi-association operation.

[0108] In some other embodiments, the function instruction information may include a second function instruction bit indicating whether the corresponding candidate AP MLD supports a second type of quasi-association operation. The second type of quasi-association operation is an over-the-DS quasi-association operation, which may also be referred to as an over-the-DS quasi-association operation. Whether an over-the-DS quasi-association operation is supported means whether an over-the-DS quasi-association operation can be performed with the candidate AP MLD through the current AP MLD. For example, if the candidate AP MLD supports an over-the-DS quasi-association operation, but the current AP MLD does not, the second function instruction bit corresponding to the candidate AP MLD is set accordingly to indicate that the candidate AP MLD does not support an over-the-DS quasi-association operation. Therefore, in other words, the second function instruction bit indicates whether over-the-DS quasi-association operation can be performed with the candidate AP MLD through the current AP MLD. For example, if the current AP MLD does not support over-the-DS quasi-association operation, the second function instruction bit for all candidate AP MLDs included in the BTM request will indicate that the corresponding candidate AP MLD does not support over-the-DS quasi-association operation.

[0109] The over-the-DS provisional association operation means that a non-AP MLD can complete a provisional association with a candidate AP MLD through the current AP MLD, establish a data transmission link with the candidate AP MLD, and negotiate transmission capability parameters, key information, and resource allocation information of both the non-AP MLD and the candidate AP MLD.

[0110] For example, the second function instruction bit may occupy one bit in the BTM request. If the value of the second function instruction bit is "0", this may indicate that the corresponding candidate AP MLD does not support over-the-DS quasi-association operation, or that over-the-DS quasi-association operation cannot be performed with the candidate AP MLD through the current AP MLD; or if the value of the second function instruction bit is "1", this may indicate that the corresponding candidate AP MLD supports over-the-DS quasi-association operation, or that over-the-DS quasi-association operation can be performed with the candidate AP MLD through the current AP MLD.

[0111] In the embodiments described above, the function instruction information may include a first function instruction bit or a second function instruction bit.

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

[0113] In some other embodiments, the functional instruction information may include first instruction information and second instruction information. The first instruction information may indicate whether the corresponding candidate AP MLD supports a provisional association operation, and the second instruction information may indicate the type of provisional association operation supported by the corresponding candidate AP MLD. In an optional embodiment, the first instruction information and the second instruction information may each occupy one bit in the BTM request. If the value of the first instruction information is "0", this may indicate that the corresponding candidate AP MLD does not support a provisional association operation. In this case, the value of the second instruction information is meaningless. If the value of the first instruction information is "1", this may indicate that the corresponding candidate AP MLD supports a provisional association operation. If the value of the first instruction information is "1" and the value of the second instruction information is "0", this may indicate that the corresponding candidate AP MLD supports over-the-air provisional association operation. If the value of the first instruction information is "1" and the value of the second instruction information is "1", this may indicate that the corresponding candidate AP MLD supports over-the-DS quasi-association operation. In other optional embodiments, the second instruction information may occupy 2 bits in the BTM request. If the value of the first instruction information is "0", this may indicate that the corresponding candidate AP MLD does not support quasi-association operation, and the value of the second instruction information may be "00". If the value of the first instruction information is "1", this may indicate that the corresponding candidate AP MLD supports quasi-association operation. If the value of the first instruction information is "1" and the value of the second instruction information is "10", this may indicate that the corresponding candidate AP MLD supports over-the-air quasi-association operation. If the value of the first instruction information is "1" and the value of the second instruction information is "11", this may indicate that the corresponding candidate AP MLD supports over-the-DS quasi-association operation.

[0114] In some other embodiments, the second instruction information may be represented as a first function instruction bit and a second function instruction bit. In other words, the function instruction information may include the first instruction information, the first function instruction bit, and the second function instruction bit. The first instruction information, the first function instruction bit, and the second function instruction bit may each occupy one bit in the BTM request. If the value of the first instruction information is "1", this may indicate that the corresponding candidate AP MLD supports quasi-association operation. If the value of the first instruction information is "1", the value of the first function instruction bit is "1", and the value of the second function instruction bit is "0", this may indicate that the corresponding candidate AP MLD supports over-the-air quasi-association operation but does not support over-the-DS quasi-association operation. If the value of the first instruction information is "1", the value of the first function instruction bit is "1", and the value of the second function instruction bit is "1", this may indicate that the corresponding candidate AP MLD supports over-the-air quasi-association operation and also supports over-the-DS quasi-association operation. If the value of the first instruction information is "0", this indicates that the corresponding candidate AP MLD does not support quasi-association operation. In this case, the values ​​of both the first and second function instruction bits are "0".

[0115] The following describes the frame format of BTM requests sent by current AP MLDs to non-AP MLDs. BTM requests may also be referred to as BTM request frames or BTM request frame packets.

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

[0117] The category field may indicate the category to which the corresponding frame packet belongs, for example, whether the frame packet is a query frame, request frame, or response frame.

[0118] The dialog token field can identify the correspondence between a request frame and a response frame. Dialog tokens carried within a request frame and response frame pair will have the same value.

[0119] The request mode field may indicate a specific request mode. The request mode field may include the following fields shown in Figure 5: preferred candidate list include field, abridge field, disassociation imminent field, BSS termination included field, ESS disassociation imminent field, Link Removal field, and reserved field. The reserved field may occupy 2 bits.

[0120] In the request mode fields, the preferred candidate list include field may indicate whether a preferred candidate list is carried. Abridge field: The abridge field is set to 0 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 abridge field is set to 1 if the current AP MLD sets the preference value of a BSS that does not appear in the preferred candidate list to 0. Disassociation imminent field: When the Disassociation imminent field is set to 1, this indicates that the current AP MLD will send a Disassociation imminent frame to disassociate the non-AP MLD's STA. When the Disassociation imminent field is set to 0, this indicates that the current AP MLD will not send a Disassociation imminent frame to disassociate the STA. The BSS termination included field may indicate whether the BSS is disabled. The ESS disassociation imminent field may indicate whether the STA is disassociated from the entire ESS.

[0121] The Disassociation Timer field may indicate the time in TBTT (Track Byte Time) since the current AP MLD sent a disassociation frame.

[0122] The Valid Interval field may indicate the amount of beacon duration for which the BSS transition candidate list is valid.

[0123] The BSS termination duration field may carry a BSS termination duration subelement. As shown in Figure 6, a subelement may include a subelement ID field, a length field, a BSS termination timing synchronization function (BSS termination TSF) field, and a duration field. The subelement ID field occupies one octet and may indicate the identifier of the corresponding BSS termination duration subelement. The length field occupies one octet and may indicate the length of the BSS termination duration field. The BSS termination TSF field may occupy eight octets and carries a TSF timer value to indicate the BSS termination time. The duration field may indicate the BSS termination duration in minutes. If the duration field is 0, this indicates that the field is reserved.

[0124] The BSS transition candidate list field may carry one or more neighbor report elements, each neighbor report element carrying information about one candidate AP MLD, the candidate AP MLD being 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 a non-AP MLD may select a target AP MLD from at least one recommended AP MLD. The BSS transition candidate list field may contain information about one or more candidate AP MLDs, and the information about each candidate AP MLD may contain functional indication information for the candidate AP MLD, which may also indicate whether the candidate AP MLD supports provisional association behavior.

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

[0126] The BSSID field may indicate the BSSID of the corresponding candidate AP MLD (neighboring AP MLD). The BSSID information field may indicate related information for the corresponding BSSID. The operating class and channel number fields may indicate the channel to which the BSSID belongs. The PHY type field may indicate the physical layer type of the candidate AP MLD. The Optional subelements field may include a basic multi-link subelement field.

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

[0128] In this embodiment of the present application, a BTM request includes functional information for one or more candidate AP MLDs, and the functional information for each candidate AP MLD may be carried in a neighbor reporting element field corresponding to the candidate AP MLD. In other words, the neighbor reporting element field corresponding to a candidate AP MLD may include the identifier of the candidate AP MLD (the element identifier mentioned above) and the functional information for the candidate AP MLD. For example, in some embodiments, the functional information for a candidate AP MLD may be carried in a reserved field of the neighbor reporting element field corresponding to the candidate AP MLD, as shown in Figure 7. In some other embodiments, an MLD capabilities and operations subfield may be set in a basic multi-link subelement field. The functional information for a candidate AP MLD may be carried in the MLD capabilities and operations subfield within the basic multi-link subelement field of the neighbor reporting element field corresponding to the candidate AP MLD.

[0129] S402: The non-AP MLD initiates a provisional association operation with the candidate AP MLD based on the functional instruction information of the candidate AP MLD carried in the BTM request.

[0130] For example, a BTM request may contain functional instruction information for one or more candidate AP MLDs. For each candidate AP MLD in the BTM request, a non-AP MLD may perform the following actions, namely, retrieving the functional instruction information for the candidate AP MLD from the BTM request. If the functional instruction information indicates that the candidate AP MLD supports a first type of quasi-association operation, i.e., an over-the-air quasi-association operation, the non-AP MLD may perform an over-the-air quasi-association operation with the candidate AP MLD. If the functional instruction information indicates that the candidate AP MLD supports a second type of quasi-association operation, i.e., an over-the-DS quasi-association operation, or that an over-the-DS quasi-association operation with the candidate AP MLD can be performed through the current AP MLD, the non-AP MLD may perform an over-the-DS quasi-association operation with the candidate AP MLD. If the functional information indicates that the candidate AP MLD supports both over-the-air and over-the-DS provisional association operations, or that over-the-DS provisional association operations can be performed with the candidate AP MLD through the current AP MLD, the non-AP MLD may prioritize over-the-DS provisional association operations with respect to the candidate AP MLD. If the functional information indicates that the candidate AP MLD supports over-the-air provisional association operations but not over-the-DS provisional association operations, or that over-the-DS provisional association operations cannot be performed with the candidate AP MLD through the current AP MLD, the non-AP MLD may perform over-the-air provisional association operations with respect to the candidate AP MLD. If the functional information indicates that the candidate AP MLD does not support provisional association operations, the non-AP MLD will not perform provisional association operations with respect to the candidate AP MLD.

[0131] In some embodiments, when a BTM request may include functional instruction information for multiple candidate AP MLDs, if at least two of the multiple candidate AP MLDs support over-the-air quasi-association operations, the non-AP MLD may select at least one candidate AP MLD from the at least two candidate AP MLDs that support over-the-DS quasi-association operations and perform over-the-air quasi-association operations on the selected candidate AP MLD. If at least two of the multiple candidate AP MLDs support over-the-DS quasi-association operations, the non-AP MLD may select at least one candidate AP MLD from the at least two candidate AP MLDs that support over-the-DS quasi-association operations and perform over-the-DS quasi-association operations on the selected candidate AP MLD.

[0132] In some other embodiments, when a BTM request may include functional instruction information for multiple candidate AP MLDs, if some of the candidate AP MLDs support over-the-DS quasi-association operation and some other candidate AP MLDs support over-the-air quasi-association operation or do not support quasi-association operation, the non-AP MLD may preferentially select at least one candidate AP MLD from those that support over-the-DS quasi-association operation and perform over-the-DS quasi-association operation on the selected candidate AP MLD. If some of the candidate AP MLDs support over-the-air quasi-association operation and some other candidate AP MLDs do not support quasi-association operation, the non-AP MLD may preferentially select at least one candidate AP MLD from those that support over-the-air quasi-association operation and perform over-the-air quasi-association operation on the selected candidate AP MLD.

[0133] In the embodiments described above, the BTM request sent by the current AP MLD to the non-AP MLD may include functional instruction information for the candidate AP MLD, which indicates whether the candidate AP MLD supports a provisional association operation. After receiving the BTM request, the non-AP MLD may initiate a provisional association operation with the candidate AP MLD based on the functional instruction information for the candidate AP MLD carried in the BTM request, and perform association operations such as negotiating with the candidate AP MLD in advance regarding keys, capability parameters, and operation parameters, as well as establishing a BA session, before switching the associated AP MLD. When a roaming condition is triggered, the non-AP MLD can rapidly transmit data with the AP MLD with which it has established a provisional association operation, reduce the delay caused by performing the association operation, and implement a fast BSS transition.

[0134] In some designs, when a non-AP MLD transmits data with the current AP MLD before switching to the associated AP MLD, the non-AP MLD must select an STA from STA1 or STA2, switch the STA to the channel where the target AP MLD's secondary AP is located, listen for beacon frames transmitted by the target AP MLD, and determine whether the target AP MLD supports provisional association operation based on the instructional information contained in the beacon frames. This process affects normal data transmission between the non-AP MLD and the current AP MLD. In the case of an enhanced multi-link single radio (EMLSR) non-AP MLD, the EMLSR non-AP MLD can listen on multiple links simultaneously. When an initial control frame transmitted by the AP MLD is received, radio frequency modules on other links in the EMLSR link set may be switched to the corresponding link where the initial control frame was received, increasing the amount of receive and transmit streams. However, at any given time, an EMLSR non-AP MLD can select only one link to receive and transmit data. Compared to a multi-radio non-AP MLD, an EMLSR non-AP MLD has only one fully functional STA and can receive and transmit data on only one link. Therefore, when an EMLSR non-AP MLD switches channels to listen for beacon frames transmitted by a target AP MLD, data transmission between the EMLSR non-AP MLD and the current AP MLD is interrupted.

[0135] In this embodiment of the present application, a BTM request sent by the current AP MLD to a non-AP MLD carries functional instruction information for the candidate AP MLD. In the process of data transmission with the current AP MLD, the non-AP MLD receives the BTM request sent by the current AP MLD and may determine, based on the functional instruction information for the candidate AP MLD carried in the BTM request, whether the candidate AP MLD supports over-the-air quasi-association operation and whether the candidate AP MLD supports over-the-DS quasi-association operation. The non-AP MLD does not need to determine whether the corresponding neighboring AP MLD supports quasi-association operation by switching channels to listen for beacon frames sent by the current AP MLD's neighboring AP MLD. Therefore, in this application, normal data transmission between the non-AP MLD and the current AP MLD is unaffected before and after the non-AP MLD receives the BTM request. In particular, for EMLSR non-AP MLDs, interruptions in data transmission between EMLSR non-AP MLDs and current AP MLDs can be avoided, improving the roaming performance of non-AP MLDs and thus improving the overall network data transmission performance.

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

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

[0138] A data transmission link exists between the non-AP MLD and the current AP MLD. If the link quality of the non-AP MLD deteriorates, the non-AP MLD may send BTM query frames to the current AP MLD.

[0139] For example, the frame format of a BTM query frame is shown in Figure 9 and may include some or all of the following fields: a category field, a wireless network management action field, a dialog token field, a BSS transition query reason field, and a BSS transition candidate list field.

[0140] The category field may indicate the category to which the corresponding frame packet belongs, for example, whether the frame packet is a query frame or a request frame.

[0141] The BSS transition query reason field may indicate the reason for sending the BTM query frame. In one embodiment, see Table 1 for the structure of the BSS transition query reason field. [Table 1]

[0142] As shown in Table 1, a value of 1 in the BSS Transition Query Reason field within a BTM query frame indicates that a non-AP MLD is sending the BTM query frame due to an excessively high packet loss rate or insufficient link quality. A value of 2 in the BSS Transition Query Reason field within a BTM query frame indicates an excessively large delay in receiving or transmitting data.

[0143] The BSS transition candidate list field is an optional field. If the BTM query frame carries the BSS transition candidate list field, it is for the current AP MLD and may carry information about neighboring AP MLDs discovered by non-AP MLDs.

[0144] The current AP MLD can receive BTM query frames sent by non-AP MLDs and respond to the non-AP MLDs with ACK (acknowledgment) frames for the BTM query frames.

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

[0146] After receiving a BTM query frame, the current AP MLD may send a BTM request frame to the non-AP MLD. The BTM request frame may contain functional instruction information corresponding to one or more candidate AP MLDs. See Figure 5 for the frame format of the BTM request frame. Further details are not described herein.

[0147] A non-AP MLD can receive a BTM request frame sent by an AP MLD and respond to the non-AP MLD with an ACK frame for the BTM request frame.

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

[0149] A BTM response frame may also be referred to as a BTM response. For example, the frame format of a BTM response frame is shown in Figure 10 and may include some or all of the following fields: category field, wireless network management action field, dialog token field, BTM status code field, BSS termination delay field, target BSSID field, and BSS transition candidate list field.

[0150] The category field may indicate the category to which the corresponding frame packet belongs, for example, whether the frame packet is a query frame, request frame, or response frame.

[0151] The dialog token field can identify the correspondence between a request frame and a response frame. The dialog token carried in a request frame and a response frame pair will have the same value.

[0152] The BSS end delay may indicate the duration of the time period from the current time to the BSS end time.

[0153] The BTM status code field may indicate whether the BSS transition request is accepted. For example, the values ​​of the BTM status code are as shown in Table 2. [Table 2]

[0154] As shown in Table 2, when a BSS transition request is accepted by a non-AP MLD, the BTM status code value is 0. When a BSS transition request is rejected by a non-AP MLD, the reason for rejection can be identified by using a different BTM status code value.

[0155] If the BTM status code value is 0, the BTM response frame may include a target BSSID field. The target BSSID corresponds to the target AP MLD and is selected by the non-AP MLD from the candidate AP MLDs carried in the BTM request frame.

[0156] Currently, an AP MLD can receive a BTM response frame sent by a non-AP MLD and respond to the non-AP MLD with an ACK frame for the BTM response frame.

[0157] In the embodiment shown in Figure 8, the target AP MLD selected by the non-AP MLD from the candidate AP MLDs is assumed to be an AP MLD that supports over-the-DS quasi-association operations. For example, in the optional embodiment, if the BTM request frame contains functional instruction information for multiple candidate AP MLDs, and at least two of the multiple candidate AP MLDs support over-the-DS quasi-association operations, the non-AP MLD may select one of the at least two candidate AP MLDs that support over-the-DS quasi-association operations as the target AP MLD. A candidate AP MLD that supports over-the-DS quasi-association operations means that over-the-DS quasi-association operations can be performed with the candidate AP MLDs through the current AP MLD. After the target AP MLD is determined, the non-AP MLD may perform over-the-DS quasi-association operations with the target AP MLD.

[0158] S804: The non-AP MLD performs an over-the-DS provisional association operation with the target AP MLD.

[0159] A non-AP MLD can perform a provisional association operation with the target AP MLD through the current AP MLD.

[0160] For example, a non-AP may send a fast BSS transition (FT) probe request to the current AP MLD, and 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 receiving the FT probe request, the current AP MLD may transparently transmit the FT probe request to the target AP MLD via DS. Based on the FT probe request, the target AP MLD may establish a data transmission link between the target AP MLD and the non-AP MLD. The data transmission link may be an air interface link between the non-AP MLD and the target AP MLD. The target AP MLD sends an FT probe response message to the current AP MLD via DS transparent transmission. The current AP MLD sends an FT probe response to the non-AP MLD.

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

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

[0163] In some embodiments, the FT query request, FT query response, FT request, FT response, FT reassociation request, FT reassociation response, etc., in step S804 may be referred to as an FT action frame. As shown in Figure 11, the frame structure of an FT action frame may include some or all of the following fields: a category field, an FT action field, a MAC address field for the non-AP MLD, a MAC address field for the target AP MLD, and a frame body field.

[0164] The category field may indicate the category to which the FT action frame belongs. The FT action field may contain a value corresponding to an FT action, and different values ​​are set for FT action fields corresponding to different FT action frames. See Table 3, for example. [Table 3]

[0165] Table 3 shows that when the FT action frame in Figure 11 is used as an FT reassociation request, the value of the FT action field is set to 7. The format of the FT action frame in Figure 11 can be used for the aforementioned FT query requests, FT query responses, FT requests, and FT responses. The difference is that the FT action field value in Table 3 is set to the corresponding value.

[0166] The MAC address field of a non-AP MLD contains the MAC layer address of the non-AP MLD, and the address may be the upper MAC layer address, lower MAC layer address, etc. of the non-AP MLD. The MAC address field of the target AP MLD contains the MAC layer address of the target AP MLD, and the address may be the upper MAC layer address, lower MAC layer address, etc. of the target AP MLD.

[0167] A frame body field may be used to carry a frame body corresponding to an FT action frame. The contents of frame bodies carried in different FT action frames may be the same or different. This is not limited to the embodiments of the present application.

[0168] By using the steps described above, the non-AP MLD completes a provisional association operation with the target AP MLD, i.e., the non-AP MLD establishes an association with the target AP MLD. The non-AP MLD establishes an association with the target AP MLD in advance through the provisional association operation. When the BSS transition (or roaming) condition is triggered, the non-AP MLD enables its association with the target AP MLD and directly transmits data, thereby reducing the delay caused by the association operation between the non-AP MLD and the target AP MLD in the BSS transition process and enabling a fast BSS transition.

[0169] In the embodiment shown in Figure 8, the BTM request sent by the current AP MLD to the non-AP MLD carries functional instruction information for the candidate AP MLD. In the process of data transmission with the current AP MLD, the non-AP MLD may receive the BTM request sent by the current AP MLD. Based on the functional instruction information for the candidate AP MLD carried in the BTM request, the non-AP MLD determines the target AP MLD that supports over-the-DS quasi-association operation and performs quasi-association operation with the target AP MLD through the current AP MLD. This process does not require channel switching of the non-AP MLD's secondary STA, and as a result, it can be ensured that data transmission between the non-AP MLD and the current AP MLD is not interrupted, i.e., normal data transmission between the non-AP MLD and the current AP MLD is not affected. This helps to improve the data transmission performance of the network.

[0170] Figure 12 is a flowchart showing the interaction between the non-AP MLD, the current AP MLD, and the target AP MLD in another specific embodiment. The target AP MLD can be any AP MLD among the candidate AP MLDs. As shown in Figure 12, the process may include the following steps.

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

[0172] The frame format of a BTM query frame may be as shown in Figure 9. Further details are not described herein.

[0173] Currently, an AP MLD can receive a BTM query frame sent by a non-AP MLD and respond to the non-AP MLD with an ACK frame for the BTM query frame.

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

[0175] The BTM request frame may contain functional instruction information corresponding to one or more candidate AP MLDs. See Figure 5 for the frame format of the BTM request frame. Further details are not described herein.

[0176] A non-AP MLD can now receive a BTM request frame sent by an AP MLD and respond to the non-AP MLD with an ACK frame for the BTM request frame.

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

[0178] The frame format of the BTM response frame may be as shown in Figure 10. Further details are not described herein.

[0179] Currently, an AP MLD can receive a BTM response frame sent by a non-AP MLD and respond to the non-AP MLD with an ACK frame for the BTM response frame.

[0180] In the embodiment shown in Figure 12, the target AP MLD selected by the non-AP MLD from the candidate AP MLDs is assumed to be an AP MLD that supports over-the-air quasi-association operation. For example, in the optional embodiment, if the BTM request frame contains functional instruction information for multiple candidate AP MLDs, and at least two of the multiple candidate AP MLDs support over-the-air quasi-association operation, the non-AP MLD may select one of the at least two candidate AP MLDs that support over-the-air quasi-association operation as the target AP MLD. The non-AP MLD can then perform over-the-air quasi-association operation on the target AP MLD.

[0181] S1204: The non-AP MLD performs an over-the-air provisional association operation with the target AP MLD.

[0182] For example, a non-AP MLD may send a probe request to a target AP MLD, which may be used to request the establishment of a data transmission link between the non-AP MLD and the target AP MLD. Based on the probe request, the target AP MLD may establish a data transmission link between the target AP MLD and the non-AP MLD. 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.

[0183] Next, the non-AP MLD may send an authentication request to the target AP MLD, which may be used to request communication parameters from the target AP MLD. The target AP MLD sends an authentication response to the non-AP MLD, which includes key information negotiated between the non-AP MLD and the target AP MLD.

[0184] A non-AP MLD may send a reassociation request to a target AP MLD, which may be used to negotiate 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, which includes link operation parameters between the non-AP MLD and the target AP MLD.

[0185] By using the steps described above, the non-AP MLD completes a provisional association operation with the target AP MLD, i.e., the non-AP MLD establishes an association with the target AP MLD. The non-AP MLD establishes an association with the target AP MLD in advance through the provisional association operation. When the BSS transition (or roaming) condition is triggered, the non-AP MLD enables its association with the target AP MLD and directly transmits data, thereby reducing the delay caused by the association operation between the non-AP MLD and the target AP MLD in the BSS transition process and enabling a fast BSS transition.

[0186] In the embodiment shown in Figure 12, the BTM request sent by the current AP MLD to the non-AP MLD carries functional instruction information for the candidate AP MLD. In the process of data transmission with the current AP MLD, the non-AP MLD may receive the BTM request sent by the current AP MLD. Based on the functional instruction information for the candidate AP MLD carried in the BTM request, the non-AP MLD may determine the target AP MLD that supports over-the-air provisional association operation. This helps the non-AP MLD select an appropriate neighboring AP MLD from the candidate AP MLDs and perform a BSS transition. [Embodiment 2]

[0187] A non-AP MLD requires time to perform a provisional association operation. Therefore, if a non-AP MLD is notified to perform a provisional association operation with a recommended candidate AP MLD only when the link quality between the non-AP MLD and the current AP MLD is already extremely poor, in a high-speed travel scenario, data transmission with the current AP MLD will be interrupted due to poor link quality before the non-AP MLD completes the provisional association operation. Therefore, the current AP MLD may notify the non-AP MLD in advance to perform a provisional association operation with a recommended candidate AP MLD. Specifically, the current AP MLD may send a BTM request to the non-AP MLD in advance and use the BTM request to notify the non-AP MLD in advance to perform a provisional association operation with a recommended candidate AP MLD. In some designs, after receiving the BTM request sent by the current AP MLD, the non-AP MLD typically performs a BSS transition. To prevent a non-AP MLD from directly performing a BSS transition each time a BTM request sent by the current AP MLD is received, in this embodiment of the present application, the BTM request carries request mode indication information, which indicates whether the non-AP MLD will subsequently perform a provisional association operation or a BSS transition operation.

[0188] Figure 13 is a flowchart illustrating the interaction between a non-AP MLD and a current AP MLD in the process of performing a provisional association operation. As shown in Figure 13, this process may include the following steps.

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

[0190] A data transmission link exists between the non-AP MLD and the current AP MLD. If the link quality of the non-AP MLD deteriorates, the current AP MLD may send a BTM request to the non-AP MLD, recommending that the non-AP MLD switch to an adjacent AP MLD. The BTM request may include request mode indication information. This request mode indication information may indicate that the non-AP MLD will perform a provisional association operation or a BSS transition operation.

[0191] In some embodiments, request mode instruction information may be carried in the request mode field of the BTM request. As shown in Figure 14, the frame format of the BTM request frame may include some or all of the following fields: category field, wireless network management action field, dialog token field, request mode field, disassociation timer field, valid interval field, BSS end duration field, session information field, and BSS transition candidate list field. The BSS transition candidate list carries information about candidate AP MLDs.

[0192] In an optional embodiment, the reserved field of the request mode field may carry request mode instruction information, which may be referred to as a tentative association request. The request mode instruction information may occupy 1 bit. When the value of the request mode instruction information is "0", it indicates that the BTM request notifies the non-AP MLD to perform a tentative association operation instead of allowing the non-AP MLD to immediately perform a BSS transition. When the value of the request mode instruction information is "1", it indicates that the BTM request notifies the non-AP MLD to perform a BSS transition operation.

[0193] In other optional embodiments, the distinction between performing a provisional association action and a BSS transition action can be made by setting an existing field in the BTM request. For example, request mode instruction information may be carried in the disassociation imminent field within the request mode field. If the value of the Disassociation Imminent field is "0", this indicates that the BTM request should inform the non-AP MLD to perform a provisional association action instead of allowing the non-AP MLD to immediately perform a BSS transition. If the value of the Disassociation Imminent field is "1", this indicates that the BTM request should inform the non-AP MLD to perform a BSS transition action.

[0194] In this embodiment, the current AP MLD sends a first BTM request to the non-AP MLD, and the first BTM request includes request mode indication information. Assume that the value of the request mode indication information is "1", indicating that the non-AP MLD will perform a provisional association operation.

[0195] S1302: non-AP MLD performs a provisional association operation based on the first BTM request.

[0196] In some embodiments, a non-AP MLD may receive a first BTM request sent by the current AP MLD and send a first BTM response to the current AP MLD. See Figure 8 or Figure 12 for the process. Further details are again not described herein.

[0197] A non-AP MLD may initiate a provisional association operation with a candidate AP MLD based on information about the candidate AP MLDs carried in the BSS transition candidate list. For example, a non-AP MLD may select a target AP MLD that supports provisional association operation from the candidate AP MLDs and perform a provisional association operation with that target AP MLD.

[0198] In some embodiments, a non-AP MLD may perform an over-the-DS quasi-association operation with respect to the target AP MLD. See Figure 8 for the operation process. In some other embodiments, a non-AP MLD may perform an over-the-air quasi-association operation for respect to the target AP MLD. See Figure 12 for the operation process.

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

[0200] When it is determined that the BSS transition conditions are met, the current AP MLD may send a second BTM request to the non-AP MLD. The frame format of the second BTM request may be the format shown in Figure 14. The second BTM request may also include request mode instruction information, which may instruct the non-AP MLD to perform a provisional association operation or a BSS transition operation. Assume that the value of the request mode instruction information in the second BTM request is "0", indicating that the non-AP MLD should perform a BSS transition operation.

[0201] S1304: non-AP MLD performs a BSS transition operation based on the second BTM request.

[0202] When the request mode instruction information in the second BTM request determines that the non-AP MLD should perform a BSS transition operation, the non-AP MLD may perform the BSS transition operation and, after the BSS transition, connect to the network through the target AP MLD.

[0203] In some embodiments, a non-AP MLD may enable association with a target AP MLD, trigger a link switch, and switch the non-AP MLD's transmit link from the current AP MLD to the target AP MLD. For example, a non-AP MLD may send a DS STA to AP mapping request frame (DS-STA-NOTIFY.request) to the target AP MLD, which may be used to request the target AP MLD to perform a data route switch. 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 sequentially deliver the complete MSDU in its receive buffer to the DS. After delivery is complete, the current AP MLD sends a context transfer response to the target AP MLD. Alternatively, after receiving the context transfer request, the current AP MLD may immediately stop delivering the MSDU to the DS and then send a context transfer response to the target AP MLD. The context transfer response includes context information from the non-AP MLD, such as block acknowledgment protocol-related information. In addition, the data in the receive buffer is transferred to the target AP MLD. The non-AP MLD disconnects data transmission with the current AP MLD and begins data transmission with the target AP MLD. The current AP MLD deletes the context information from the non-AP MLD. After the data path switch, data transmission may occur between the non-AP MLD and the target AP MLD, and the non-AP MLD may encrypt and decrypt the transmitted data by using the key negotiated with the target AP MLD when performing the provisional association operation.

[0204] In the embodiments described above, the BTM request includes request mode instruction information, which may indicate that the non-AP MLD will subsequently perform a provisional association operation or a BSS transition operation. Therefore, the current AP MLD can send a BTM request to the non-AP MLD in advance to notify the non-AP MLD in advance to perform a provisional association operation with the recommended candidate AP MLD by using the BTM request, thereby avoiding the occurrence in high-speed mobile scenarios where data transmission with the current AP MLD is interrupted due to insufficient link quality before the non-AP MLD can complete the provisional association operation.

[0205] Embodiments 1 and 2 may be implemented separately or in a cross-implementation manner. For example, in Embodiment 1, the first BTM request may also include functional indication information for a candidate AP MLD recommended by the current AP MLD to indicate whether the corresponding candidate AP MLD supports a provisional association operation. A 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 provisional association operation, the non-AP MLD may perform a provisional association operation for the candidate AP MLD based on the functional indication information for the candidate AP MLD carried in the first BTM request.

[0206] Based on the same design concept as the embodiments of the method described above, one embodiment of the present application further provides a communication device. The communication device may be used in a non-AP MLD, for example, the non-AP MLD 300 shown in Figure 1. The communication device may be configured to implement the functions of the embodiments of the method described above, and thus can implement the beneficial effects of the embodiments of the method described above. As shown in Figure 15, the communication device 1500 may include a request receiving module 1501 and an association operation module 1502.

[0207] In some embodiments, the request receiving module 1501 may be configured to receive a basic service set transition management BTM request sent by the current AP MLD, the BTM request containing functional instruction information for a candidate AP MLD, the candidate AP MLD being a neighboring AP MLD of the current AP MLD, and the functional instruction information indicating whether the candidate AP MLD supports a provisional association operation. The association operation module 1502 may be configured to initiate a provisional association operation for the candidate AP MLD based on the functional instruction information for the candidate AP MLD.

[0208] In some other embodiments, the request receiving module 1501 may be configured to receive a Basic Service Set Transition Management (BTM) request sent by the current AP MLD, the BTM request including request mode indication information, which indicates that the non-AP MLD is performing a provisional association operation or a Basic Service Set (BSS) transition operation.

[0209] The association operation module 1502 may be configured to initiate a provisional association operation for a candidate AP MLD when the request mode instruction information indicates that a non-AP MLD should perform a provisional association operation, and the candidate AP MLD is a neighboring AP MLD of the current AP MLD.

[0210] In some embodiments, the communication device 1500 may further include a transition operation module. The transition operation module may be configured to perform a BSS transition operation when the request mode instruction information indicates a non-AP MLD to perform a basic service set (BSS) transition operation, and to connect to the network through the target AP MLD after the BSS transition.

[0211] It should be noted that in other embodiments, the request receiving module 1501 may be configured to perform any step in the communication method, and the association operation module 1502 may be configured to perform any step in the communication method. The steps performed by the request receiving module 1501 and the association operation module 1502 may be specified as needed. The request receiving module 1501 and the association operation module 1502 perform different steps in the communication method separately in order to perform all the functions of the communication device.

[0212] In embodiments of the present invention, the functional modules may be integrated into a single processor, or each module may exist physically independently, or two or more modules may be integrated into a single module. The integrated module may be implemented in hardware form or in the form of a software functional unit.

[0213] Based on the same design concept as the embodiments of the method described above, one embodiment of the present application further provides a communication device. The communication device may be used in an AP MLD, for example, AP MLD 100 or AP MLD 200 shown in Figure 1. The AP MLD is a current AP MLD of a non-AP MLD. The communication device may be configured to implement the functions in the embodiments of the method described above, and thus can implement the beneficial effects of the embodiments of the method described above. As shown in Figure 16, the communication device 1600 may include a request transmission module 1601 and a response reception module 1602.

[0214] In some embodiments, the request sending module 1601 may be configured to send a basic service set transition management BTM request to a non-AP MLD, the BTM request including functional indication information for a candidate AP MLD, the candidate AP MLD being a neighboring AP MLD of the current AP MLD, and the functional indication information indicating whether the candidate AP MLD supports provisional association operation. The response receiving module 1602 may be configured to receive the BTM response sent by the non-AP MLD.

[0215] In some other embodiments, the request sending module 1601 may be configured to send a Basic Service Set Transition Management (BTM) request to a non-AP MLD, the BTM request including request mode instruction information, which instructs the non-AP MLD to perform a provisional association operation or a Basic Service Set (BSS) transition operation. The response receiving module 1602 may be configured to receive the BTM response sent by the non-AP MLD.

[0216] It should be noted that in other embodiments, the request transmission module 1601 may be configured to perform any step in the communication method, and the response reception module 1602 may be configured to perform any step in the communication method. The steps performed by the request transmission module 1601 and the response reception module 1602 may be specified as needed, and the request transmission module 1601 and the response reception module 1602 perform different steps in the communication method separately in order to perform all the functions of the communication device.

[0217] In embodiments of the present invention, the functional modules may be integrated into a single processor, or each module may exist physically independently, or two or more modules may be integrated into a single module. The integrated module may be implemented in hardware form or in the form of a software functional unit.

[0218] Based on the same technical concepts as the embodiments of the method described above, one embodiment of the present application further provides a communication device. The communication device may be a non-AP MLD or AP MLD as shown in Figure 1. The communication device may be configured to implement the functions in the embodiments of the method described above, and thus can implement the beneficial effects of the embodiments of the method described above.

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

[0220] Memory 1702 may be configured to store software programs and modules. The processor 1701 executes the software programs and modules stored in memory 1702 to perform various functional applications and data processing of the communication device 1700, such as the communication method provided in the embodiments of the present application.

[0221] Memory 1702 may primarily include a program storage area and a data storage area. The program storage area may store the operating system, application programs for at least one application, etc. The data storage area may be used to store user data, etc. In addition, memory 1702 may include high-speed random-access memory and may further include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

[0222] The processor 1701 within the communication device 1700 is configured to perform the functions of any one of the embodiments of the method described above by executing computer instructions or programs stored in memory 1702. For example, if the communication device 1700 is a non-AP MLD, the processor 1701 may be configured to perform the following steps: receiving a BTM request sent by the current AP MLD, and initiating a provisional association operation with a candidate AP MLD based on the functional instruction information of the candidate AP MLD carried in the BTM request. Alternatively, the processor 1701 may be configured to perform the following steps: receiving a BTM request sent by the current AP MLD, wherein the BTM request includes request mode instruction information, and, if the request mode instruction information indicates that a non-AP MLD performs a provisional association operation, initiating a provisional association operation with a candidate AP MLD, wherein the candidate AP MLD is a neighboring AP MLD of the current AP MLD.

[0223] If the communication device 1700 is an AP MLD, the processor 1701 may be configured to perform the following steps: sending a BTM request to a non-AP MLD and receiving a BTM response sent by the non-AP MLD. The BTM request includes functional information for a candidate AP MLD, where the candidate AP MLD is a neighboring AP MLD of the current AP MLD, and the functional information indicates whether the candidate AP MLD supports a provisional association operation. Alternatively, the processor 1701 may be configured to perform the following steps: sending a BTM request to a non-AP MLD and receiving a BTM response sent by the non-AP MLD. The BTM request includes request mode information, where the request mode information indicates whether the non-AP MLD performs a provisional association operation or a basic service set (BSS) transition operation.

[0224] In some embodiments, the processor 1701 may include one or more processing units, which may be independent devices or integrated into one or more processors. The processor 1701 may further include a controller. The controller may generate operation control signals based on instruction operation codes and time-series signals to complete the control of instruction fetching and instruction execution.

[0225] In one embodiment, the communication device 1700 may further include a communication module for communicating with other devices in the network.

[0226] In some other embodiments, if the communication device 1700 is a non-AP MLD, the communication device may use the non-AP MLD structure shown in Figure 1 or Figure 2. If the communication device 1700 is an AP MLD, the communication device may use the AP MLD structure shown in Figure 1 or Figure 2. Further details are not described herein.

[0227] It can be understood that the structure shown in this embodiment of the Application does not constitute a particular limitation on network devices. In some other embodiments of the Application, the chip may contain more or fewer components than those shown in the figure, or some components may be combined, or some components may be separated, or there may be a different component layout. The components shown in the figure may be implemented by hardware, software, or a combination of software and hardware.

[0228] Based on the same technical concepts as the embodiments of the method described above, one embodiment of the present application further provides a communication system. The communication system may be the communication system shown in Figure 1, and the communication system may include at least one non-AP MLD and at least two AP MLDs.

[0229] Each AP MLD may perform the following steps: sending a BTM request to a non-AP MLD and receiving a BTM response sent by the non-AP MLD. The BTM request includes functional information for a candidate AP MLD, where the candidate AP MLD is a neighboring AP MLD of the current AP MLD, and the functional information indicates whether the candidate AP MLD supports a provisional association operation. Alternatively, the following steps may be performed: sending a BTM request to a non-AP MLD and receiving a BTM response sent by the non-AP MLD. The BTM request includes request mode information, where the request mode information indicates whether the non-AP MLD performs a provisional association operation or a basic service set (BSS) transition operation.

[0230] Each non-AP MLD may perform the following steps: receiving a BTM request sent by the current AP MLD and initiating a provisional association operation with a candidate AP MLD based on the functional instruction information of the candidate AP MLD carried in the BTM request; or, it may perform the following steps: receiving a BTM request sent by the current AP MLD, wherein the BTM request includes request mode instruction information, and, if the request mode instruction information indicates that the non-AP MLD will perform a provisional association operation, initiating a provisional association operation with a candidate AP MLD, wherein the candidate AP MLD is a neighboring AP MLD of the current AP MLD.

[0231] One embodiment of the present application further provides a computer program product, which includes computer-executable instructions. In one embodiment, the computer-executable instructions are used to enable a computer to perform the functions in the embodiments of the method described above.

[0232] Computer-executable instructions can be stored in a computer-readable storage medium. Embodiments of the present application further provide a computer-readable storage medium in which executable instructions are stored. In one embodiment, the computer-executable instructions are used to enable a computer to perform the functions in the embodiments of the method described above.

[0233] The computer-readable storage medium provided in this embodiment of the present application may be random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), registers, hard disk drives, removable hard disks, CD-ROMs, or any other form of computer-readable storage medium known in the art.

[0234] Computer-executable instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, a computer program or instruction may be transmitted by wire or wirelessly from a website, computer, server, or data center to another website, computer, server, or data center. A computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device that integrates one or more available media, such as a server or data center. The available media may be magnetic media, such as floppy disks, hard disks, or magnetic tapes; optical media, such as digital video discs (DVDs); or semiconductor media, such as solid-state drives.

[0235] In the embodiments of this application, unless otherwise specified or unless there is a logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be mutually referenced, and the technical features in different embodiments can be combined according to their internal logical relationships to form new embodiments. Also, “includes,” “has,” and any variations thereof are intended to cover non-exclusive inclusion, for example, a set of steps or units. A method, system, product, or device is not necessarily limited to the explicitly enumerated steps or units and may include other steps or units that are not explicitly enumerated or that are specific to such process, method, product, or device.

[0236] While this application is described with reference to certain features and embodiments thereof, it is evident that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Correspondingly, this specification and the accompanying drawings are merely illustrative descriptions of the solutions defined by the accompanying claims and may be considered any or all of the modifications, variations, combinations, or equivalents that fall within the scope of this application.

[0237] It will be apparent to those skilled in the art that various modifications and variations of the present application can be made without departing from the scope of the present application. In this case, the present application is intended to encompass these modifications and variations of the embodiments of the present application, provided that these modifications and variations fall within the scope of protection defined by the claims of the present application and their equivalent art.

Claims

1. A communication method applicable to a non-access point multilink device (non-AP MLD), wherein the non-AP MLD is connected to a current access point multilink device (AP MLD), and the method is: A step of receiving a basic service set transition management BTM request sent by the current AP MLD, wherein the BTM request includes functional instruction information for a candidate AP MLD, the candidate AP MLD being a neighboring AP MLD of the current AP MLD, and the functional instruction information indicating whether the candidate AP MLD supports provisional association operation. A method comprising the step of initiating a provisional association operation for the candidate AP MLD based on the function instruction information of the candidate AP MLD.

2. The method according to claim 1, wherein the function instruction information is carried in the neighbor report element field of the BTM request.

3. The method according to claim 1 or 2, wherein the function instruction information includes a first function instruction bit, the first function instruction bit indicating whether the candidate AP MLD supports a first type of quasi-association operation, the first type of quasi-association operation being a quasi-association operation performed through an air interface.

4. The step of initiating the provisional association operation for the candidate AP MLD based on the function instruction information of the candidate AP MLD is: The method according to claim 3, wherein if the first function instruction bit indicates that the candidate AP MLD supports the first type of provisional association operation, the method further comprises performing the provisional association operation on the candidate AP MLD through the air interface.

5. The method according to any one of claims 1 to 4, wherein the function instruction information includes a second function instruction bit, the second function instruction bit indicating whether the candidate AP MLD supports a second type of quasi-association operation, the second type of quasi-association operation being a quasi-association operation performed through a distributed system DS.

6. The step of initiating the provisional association operation for the candidate AP MLD based on the function instruction information of the candidate AP MLD is: The method of claim 5, comprising performing the provisional association operation on the candidate AP MLD via the DS if the second function instruction bit indicates that the candidate AP MLD supports the second type of provisional association operation.

7. The step of initiating the provisional association operation for the candidate AP MLD based on the function instruction information of the candidate AP MLD is: The method of claim 5, further comprising the step of performing the provisional association operation on the candidate AP MLD through the air interface if the first function instruction bit indicates that the candidate AP MLD supports the first type of provisional association operation and the second function instruction bit indicates that the candidate AP MLD does not support the second type of provisional association operation.

8. The BTM request includes request mode instruction information, and the step of initiating the provisional association operation for the candidate AP MLD based on the function instruction information of the candidate AP MLD is: If the request mode instruction information indicates that the non-AP MLD will perform a provisional association operation, the provisional association operation is initiated for the candidate AP MLD based on the function instruction information of the candidate AP MLD. The method according to any one of claims 1 to 7.

9. The method according to claim 8, further comprising the step of performing a BSS transition operation if the request mode instruction information indicates that the non-AP MLD performs a basic service set BSS transition operation, and then connecting to the network through the target AP MLD after the BSS transition.

10. The method according to claim 8 or 9, wherein the request mode instruction information is carried in the request mode field of the BTM request.

11. A communication method applicable to a non-access point multilink device (non-AP MLD), wherein the non-AP MLD is connected to a current access point multilink device (AP MLD), and the method is: The steps include receiving a Basic Service Set Transition Management (BTM) request transmitted by the current AP MLD, wherein the BTM request includes request mode instruction information, and the request mode instruction information instructs the non-AP MLD to perform a provisional association operation or a Basic Service Set (BSS) transition operation; A method comprising the step of initiating a provisional association operation with a candidate AP MLD when the request mode instruction information instructs the non-AP MLD to perform the provisional association operation, wherein the candidate AP MLD is a neighboring AP MLD of the current AP MLD.

12. The aforementioned method, If the request mode instruction information instructs the non-AP MLD to perform the BSS transition operation, the further step includes performing the BSS transition operation and connecting to the network through the target AP MLD after the BSS transition. The method according to claim 11.

13. The method according to claim 11 or 12, wherein the request mode instruction information is carried in the request mode field of the BTM request.

14. A communication method applicable to a current access point multilink device (AP MLD) of a non-access point multilink device (non-AP MLD), wherein the method is: A step of sending a basic service set transition management BTM request to the non-AP MLD, wherein the BTM request includes functional instruction information for a candidate AP MLD, the candidate AP MLD being a neighboring AP MLD of the current AP MLD, and the functional instruction information indicating whether the candidate AP MLD supports provisional association operation. A method comprising the step of receiving a BTM response transmitted by the non-AP MLD.

15. The method according to claim 14, wherein the function instruction information is carried in the neighbor reporting element field of the BTM request.

16. The method according to claim 14 or 15, wherein the function instruction information includes a first function instruction bit, the first function instruction bit indicates whether the candidate AP MLD supports a first type of quasi-association operation, and the first type of quasi-association operation is a quasi-association operation performed through an air interface.

17. The method according to any one of claims 14 to 16, wherein the function instruction information includes a second function instruction bit, the second function instruction bit indicating whether the candidate AP MLD supports a second type of quasi-association operation, the second type of quasi-association operation being a quasi-association operation performed through a distributed system DS.

18. The method according to any one of claims 14 to 17, wherein the BTM request includes request mode instruction information, and the request mode instruction information instructs the non-AP MLD to perform a provisional association operation or a basic service set BSS transition operation.

19. The method according to claim 18, wherein the request mode instruction information is carried in the request mode field of the BTM request.

20. A communication method applicable to a current access point multilink device (AP MLD) of a non-access point multilink device (non-AP MLD), The steps include: sending a basic service set transition management (BTM) request to the non-AP MLD, wherein the BTM request includes request mode instruction information, and the request mode instruction information instructs the non-AP MLD to perform a provisional association operation or a basic service set transition operation; A method comprising the step of receiving a BTM response transmitted by the non-AP MLD.

21. The method according to claim 20, wherein the request mode instruction information is carried in the request mode field of the BTM request.

22. A communication device used in a non-access point multilink device (non-AP MLD), wherein the non-AP MLD is connected to a current access point multilink device (AP MLD), and the device includes a module configured to perform the method according to any one of claims 1 to 10, or a module configured to perform the method according to any one of claims 11 to 13.

23. A communication device used in a current access point multilink device (AP MLD) of a non-access point multilink device (non-AP MLD), wherein the device includes a module configured to perform the method described in any one of claims 14 to 19, or a module configured to perform the method described in claim 20 or 21.

24. A communication device, wherein the communication device is a non-access point multilink device (non-AP MLD), the non-AP MLD is connected to a current access point multilink device (AP MLD), and the communication device includes memory and a processor, the memory storing a computer program, and the processor executing the computer program stored in the memory to implement the method of any one of claims 1 to 10 or to perform the method of any one of claims 11 to 13.

25. A communication device, wherein the communication device is a non-access point multilink device (non-AP MLD) or an access point multilink device (AP MLD), and the communication device includes memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program stored in the memory to implement the method of any one of claims 14 to 19 or to perform the method of claim 20 or 21.

26. A communication system comprising a non-access point multilink device (non-AP MLD) and an access point multilink device (AP MLD), wherein the non-AP MLD is configured to execute a computer program and implement the method of any one of claims 1 to 10 or to perform the method of any one of claims 11 to 13, and the AP MLD is configured to execute a computer program and implement the method of any one of claims 14 to 19 or to perform the method of claim 20 or 21.

27. A computer-readable storage medium for storing computer-executable instructions, wherein the computer-executable instructions are used to enable a computer to perform the method according to any one of claims 1 to 13 or any one of claims 14 to 21.

28. A computer program product comprising computer-executable instructions, wherein the computer-executable instructions are used to enable a computer to perform the method according to any one of claims 1 to 13 or any one of claims 14 to 21.

Images