Multi-link trial association method and related device

Abstract

The invention relates to the field of wireless communication, in particular to a multilink trial association method and a related device, for example, the multilink trial association method and the related device are applied to a wireless local area network supporting an 802.11 be standard. The method comprises the following steps: a first STA in a Non-AP MLD, the link state between the first STA and a first AP MLD being a disconnected state, generates and sends a multi-link association request frame to a second AP MLD, and the multi-link association request frame is used for requesting the Non-AP MLD and the second AP MLD to perform multi-link tentative association; and under the condition of successful association, the Non-AP MLD sends indication information for triggering the second AP MLD to update the mapping relationship between the station and the access point, so that the interruption time of data transmission in the roaming process can be reduced when the multi-link equipment roams, and the data transmission efficiency is improved. And the data transmission in the roaming process is not interrupted by controlling the opportunity of updating the mapping information of the station and the access point.

Description

[0001] This application is a divisional application. The original application has the application number 202010550151X and the original application date is June 16, 2020. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication technology, and in particular to a multi-link interconnection method and related apparatus. Background Technology

[0003] Wireless local area network (WLAN) roaming or Wi-Fi roaming refers to the process by which a wireless terminal or station (STA) moves from one access point (AP) to another, that is, the wireless terminal or STA moves from one basic service set (BSS) to another BSS. During WLAN or Wi-Fi roaming, the STA can move freely within the Wi-Fi network belonging to the same extended service set (ESS), such as switching from one BSS to another within the same ESS; and by ensuring that the user's identity (Internet Protocol (IP) address) remains unchanged, that is, the IP address obtained by the client at the initial connection to the network does not change throughout the roaming process, thus achieving uninterrupted service (i.e., uninterrupted client service).

[0004] When a STA roams from one AP to another, it first disconnects from the original AP. Until a connection is established with the new AP, no data transmission can occur between the AP and the STA. Therefore, to reduce data transmission interruption time during roaming, i.e., to reduce roaming latency (roaming latency refers to the time from when the STA disconnects from the original AP until it can transmit data with the new AP), this can be achieved through pairwise master key (PMK) caching. See also... Figure 1 , Figure 1 This is a diagram illustrating the use of PMK caching to achieve fast STA roaming. For example... Figure 1 As shown, before roaming, the STA and the original AP ( Figure 1AP1 in the diagram completes the association negotiation between the STA and the original AP through user association, 802.1X authentication, unicast / multicast key negotiation, and encrypted data packet communication. During the unicast / multicast key negotiation between the STA and the original AP, the STA caches the PMK and / or PMK identifier (i.e., PMKID), and the access point controller (AP controller, AC) also caches the PMK and / or PMKID. When the STA roams, the STA sends a message to the new AP (AP1) to complete the association negotiation process. Figure 1 AP2 initiates a reassociation, carrying the PMKID cached by the STA. Upon receiving the PMKID, the new AP sends it to the AC. The AC checks if it has the same PMKID stored locally. If it does, it means the STA has already passed 802.1X authentication and does not need to perform 802.1X authentication again; it can directly derive unicast and multicast keys with the new AP. After the unicast and multicast key negotiation is completed, the STA can use the negotiated key to encrypt data and communicate with the new AP.

[0005] Therefore, the STA fast roaming mechanism using PMK caching reduces roaming latency by caching the PMKID, allowing the STA to skip the cumbersome 802.1X authentication process after switching APs. However, this mechanism only reduces data transmission interruption time during roaming; it does not ensure uninterrupted data transmission. Uninterrupted data transmission means that at least one link is always available for data transmission during the roaming process (or the process of switching from one BSS to another, or from one AP to another).

[0006] Therefore, a key technology of the next-generation Wi-Fi standard IEEE 802.11be (referred to as Wi-Fi 7 by the Wi-Fi Alliance, also known as the Extremely High Throughput (EHT) standard) is multi-link technology. Correspondingly, multi-link technology requires multi-link devices (MLDs) for support. A multi-link device is a device that simultaneously has multiple radio frequency modules, each operating on different frequency bands or channels. Thus, roaming with multi-link devices promises to achieve uninterrupted data transmission. However, how to implement roaming with multi-link devices under IEEE 802.11be, reduce data transmission interruption time during roaming, or ensure uninterrupted data transmission during roaming, remains unresolved. Summary of the Invention

[0007] This application provides a multi-link trial association method and related apparatus, which can reduce the interruption time of data transmission during roaming of multi-link devices under IEEE 802.11be, and can ensure uninterrupted data transmission during roaming by controlling the timing of updating the mapping information between the site and the access point.

[0008] In a first aspect, embodiments of this application provide a multi-link trial association method, applied in a non-access point multi-link device (Non-AP MLD), wherein the Non-AP MLD includes multiple STAs, and the multi-link trial association method includes: one or more first STAs in the Non-AP MLD whose link status with a first AP MLD is disconnected, generating and sending a multi-link association request frame to one or more second AP MLDs, the multi-link association request frame being used to initiate a multi-link trial association between the Non-AP MLD and one or more second AP MLDs; the Non-AP MLD receiving one or more multi-link association response frames returned by one or more second AP MLDs; if the one or more multi-link association response frames indicate that the multi-link trial association is successful, the Non-AP MLD sends indication information to a target AP MLD to trigger the target AP MLD to update the mapping relationship between the site and the access point, the target AP MLD being a second AP MLD determined from one or more second AP MLDs.

[0009] Optionally, the link status between the second STA of the Non-AP MLD and the first AP MLD is in a connected state.

[0010] Optionally, the Non-AP MLD determines the target AP MLD from one or more second AP MLDs by selecting one final target AP MLD from the multiple second AP MLDs based on whether the association between the Non-AP MLD and the multiple second AP MLDs is successful, the capabilities of each second AP MLD, and the link quality between the Non-AP MLD and each second AP MLD.

[0011] This scheme utilizes one or more STAs in a Non-AP MLD whose link status with the first AP MLD is disconnected, to simultaneously initiate multi-link exploratory associations with one or more second AP MLDs. After successful association, an indication message is sent to notify the second AP MLD that the site-to-access point mapping relationship can be updated, so that data packets from the Non-AP MLD can be correctly delivered to the corresponding AP MLD. This reduces the data transmission interruption time during roaming for multi-link devices under IEEE 802.11be, and the timing of updating the site-to-access point mapping information can be controlled to ensure uninterrupted data transmission during roaming.

[0012] In conjunction with the first aspect, in one possible design, before the first STA of the Non-AP MLD sends a multi-link association request frame to the second AP MLD, the method further includes: the Non-AP MLD can send link status indication information to the first AP MLD, the link status indication information being used to indicate that the link status between the first STA of the Non-AP MLD and the first AP MLD is disconnected.

[0013] Optionally, the link status indication information is also used to indicate the reason why the link status between the first STA of the Non-AP MLD and the first AP MLD is disconnected.

[0014] Optionally, the reason why the link status between the first STA and the first AP MLD is disconnected is for exploratory association.

[0015] This solution uses link status indication information to inform the first AP MLD that one or more links have been disconnected due to trial association, thus preventing the first AP MLD from attempting to request the opening of one or more links due to a large amount of data to be transmitted.

[0016] Secondly, embodiments of this application provide a multi-link trial association method applied to a target AP MLD, which includes multiple APs. The multi-link trial association method includes: the target AP MLD receiving a multi-link association request frame from a Non-AP MLD, the multi-link association request frame being used to request the Non-AP MLD to perform a multi-link trial association with the target AP MLD; if the multi-link association response frame returned by the target AP MLD indicates successful association, the target AP MLD receives indication information from the Non-AP MLD, the indication information being used to trigger the target AP MLD to update the mapping relationship between sites and access points; after receiving the indication information, the target AP MLD sends the mapping information between sites and access points, the mapping information being used to indicate that the mapping relationship between sites and access points is updated from the association between the Non-AP MLD and the first AP MLD to the association between the Non-AP MLD and the target AP MLD.

[0017] In conjunction with the second aspect, in one possible design, the mapping information between the site and the access point includes the SAP Media Access Control MAC address of the Non-APMLD service access point and the SAP MAC address of the second AP MLD.

[0018] Thirdly, embodiments of this application provide a communication device, which can be a Non-AP MLD or a chip in a Non-AP MLD, such as a Wi-Fi chip, comprising: The processing unit is used to generate a multi-link association request frame; the transceiver unit is used to send a multi-link association request frame to one or more second AP MLDs, the multi-link association request frame being used to initiate a multi-link exploratory association between a Non-AP MLD and one or more second AP MLDs; the transceiver unit is also used to send an indication message to a target AP MLD when the multi-link exploratory association between the Non-AP MLD and one or more second AP MLDs is successful, to trigger the target AP MLD to update the mapping relationship between the site and the access point, the target AP MLD being a second AP MLD determined from one or more second AP MLDs.

[0019] Optionally, the link between the first STA and the first AP MLD is disconnected, and the link between the second STA (non-AP MLD) and the first AP MLD is connected.

[0020] In conjunction with the third aspect, in one possible design, the aforementioned transceiver unit is further configured to: send link status indication information to the first AP MLD, the link status indication information being used to indicate that the link status between one or more first STAs of the Non-AP MLD and the first AP MLD is disconnected.

[0021] Optionally, the link status indication information is also used to indicate the reason why the link status between the first STA and the first AP MLD is disconnected.

[0022] Optionally, the reason why the link status between the first STA and the first AP MLD is disconnected is for exploratory association.

[0023] Fourthly, embodiments of this application provide another communication device, which can be a target AP MLD or a chip in the target AP MLD, such as a Wi-Fi chip, including: The transceiver unit is configured to receive a multi-link association request frame from a Non-AP MLD, which requests the Non-AP MLD to perform a multi-link exploratory association with a target AP MLD. The transceiver unit is also configured to receive indication information from the Non-AP MLD when the target AP MLD returns a multi-link association response frame indicating successful association. This indication information is used to trigger the target AP MLD to update the site-access point mapping relationship. The processing unit is configured to generate site-access point mapping information. The transceiver unit is also configured to send the site-access point mapping information, which indicates that the site-access point mapping relationship has been updated from the Non-AP MLD associating with the first AP MLD to the Non-AP MLD associating with the target AP MLD.

[0024] In conjunction with the fourth aspect, in one possible design, the site-to-access point mapping information includes the service access point SAP media access control MAC address of the Non-APMLD and the SAP MAC address of the target AP MLD.

[0025] In any of the above implementations, the aforementioned indication information can be carried in the A-control field or in a notification frame, such as the STA-AP Mapping Notify frame.

[0026] In any of the above implementations, the multi-link association request frame may include the link status of the non-transmission link between the Non-AP MLD and the second AP MLD.

[0027] Optionally, the multi-link association request frame may also include a reason code field, which can be used to indicate the reason why the link status between the second STA of the Non-AP MLD and the second AP MLD is disconnected. This reason code field can be set to "Associated with the old AP MLD".

[0028] This solution avoids the second AP MLD from transmitting data to the Non-AP MLD using a disconnected link because the second AP MLD does not know the link status between the Non-AP MLD and the second AP MLD. By carrying the link status of the non-transmission link between the Non-AP MLD and the second AP MLD in the multi-link association request frame, this solution can prevent the second AP MLD from transmitting data to the Non-AP MLD using a disconnected link because it does not know the link status between the Non-AP MLD and the second AP MLD.

[0029] In any of the above implementations, the multi-link association request frame may further include exploratory association indication information to indicate whether the current association operation is a multi-link exploratory association.

[0030] Optionally, the aforementioned multi-link association request frame may also include tentative association lifetime information to indicate the lifecycle of the multi-link tentative association.

[0031] Optionally, the tentative association indication information and the tentative association lifecycle information are carried in the public information field of the multi-link aggregation MLA element.

[0032] This scheme carries tentative association indication information in the multi-link association request frame to distinguish between normal multi-link association and multi-link tentative association; by carrying tentative association lifetime information, when the time without interaction between Non-AP MLD and AP MLD exceeds the lifetime, AP MLD deletes the information previously negotiated with Non-AP MLD, thereby freeing up cache space.

[0033] Fifthly, embodiments of this application provide a communication device, specifically a Non-AP MLD, including a processor and a transceiver. The processor is configured to support the Non-AP MLD in performing the corresponding functions of the method described in the first aspect. The transceiver is used to support communication between the Non-AP MLD and an AP MLD, sending information, frames, data packets, or instructions involved in the above method to the AP MLD. The Non-AP MLD may further include a memory coupled to the processor, which stores necessary program instructions and data of the Non-AP MLD.

[0034] Specifically, the processor is used to generate a multi-link association request frame; the transceiver is used to send a multi-link association request frame to one or more second AP MLDs, the multi-link association request frame being used to initiate a multi-link tentative association between the Non-AP MLD and one or more second AP MLDs; the transceiver is also used to send an indication message to the target AP MLD when the multi-link tentative association between the Non-AP MLD and one or more second AP MLDs is successful, to trigger the target AP MLD to update the mapping relationship between the site and the access point, the target AP MLD being the second AP MLD determined from one or more second AP MLDs.

[0035] Sixthly, embodiments of this application provide a communication device, specifically a target AP MLD, including a processor and a transceiver. The processor is configured to support the target AP MLD in performing the corresponding functions of the method described in the second aspect above. The transceiver is used to support communication between the target AP MLD and a non-AP MLD, sending information, frames, data packets, or instructions involved in the above method to the non-AP MLD. The AP MLD may further include a memory coupled to the processor, which stores necessary program instructions and data of the AP MLD.

[0036] Specifically, the transceiver is used to receive a multi-link association request frame from a Non-AP MLD, which requests the Non-AP MLD to perform a multi-link exploratory association with a target AP MLD; the transceiver is also used to receive indication information from the Non-AP MLD when the multi-link association response frame returned by the target AP MLD indicates successful association, which triggers the target AP MLD to update the mapping relationship between the site and the access point; the processor is used to generate the mapping information between the site and the access point; the transceiver is also used to send the mapping information between the site and the access point, which indicates that the mapping relationship between the site and the access point is updated from the association between the Non-AP MLD and the first AP MLD to the association between the Non-AP MLD and the target AP MLD.

[0037] In a seventh aspect, embodiments of this application provide a wireless communication system, which includes the Non-AP MLD described in the third or fifth aspect above, and the target AP MLD described in the fourth or sixth aspect above.

[0038] Eighthly, embodiments of this application provide a chip or chip system, including an input / output interface and a processing circuit. The processing circuit is used to generate a multi-link association request frame. The input / output interface is used to send the multi-link association request frame to one or more second AP MLDs. The multi-link association request frame is used to initiate a multi-link tentative association between a Non-AP MLD and one or more second AP MLDs. The input / output interface is also used to send indication information to a target AP MLD when the multi-link tentative association between the Non-AP MLD and one or more second AP MLDs is successful. This instruction is used to trigger the target AP MLD to update the mapping relationship between the site and the access point. The target AP MLD is a second AP MLD determined from one or more second AP MLDs.

[0039] In one possible design, the input / output interface is used to receive a multi-link association request frame from a Non-AP MLD, which requests the Non-AP MLD to perform a multi-link exploratory association with a target AP MLD. The input / output interface is also used to receive indication information from the Non-AP MLD when the target AP MLD returns a multi-link association response frame indicating successful association. This indication information triggers the target AP MLD to update the site-to-access point mapping relationship. The processing circuitry is used to generate site-to-access point mapping information. Furthermore, the input / output interface is used to send the site-to-access point mapping information, which indicates that the site-to-access point mapping relationship has been updated from the Non-AP MLD associating with the first AP MLD to the Non-AP MLD associating with the target AP MLD.

[0040] Ninthly, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the multi-link interconnection method described in any of the preceding aspects.

[0041] In a tenth aspect, this application provides a computer program product containing instructions that, when run on a computer, cause the computer to execute the multi-link trial association method described in any of the preceding aspects.

[0042] By implementing the embodiments of this application, multi-link devices under IEEE 802.11be can reduce the interruption time of data transmission during roaming, and the timing of updating the mapping information between the site and the access point can be controlled to ensure that data transmission is not interrupted during roaming. Attached Figure Description

[0043] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below.

[0044] Figure 1 This is a diagram illustrating the use of PMK caching to achieve fast STA roaming; Figure 2 This is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of this application; Figure 3 This is a schematic diagram of the structure of a multi-link device provided in an embodiment of this application; Figure 4 This is a schematic diagram of the connection between an AP multi-link device and a Non-AP multi-link device; Figure 5 This is a schematic flowchart of a multi-link trial association method provided in an embodiment of this application; Figure 6a This is a schematic diagram of the frame structure of a new element provided in an embodiment of this application; Figure 6b This is a schematic diagram of the frame structure of another new element provided in the embodiments of this application; Figure 7a This is a schematic diagram of a frame structure for a neighbor reporting element provided in an embodiment of this application; Figure 7b This is a schematic diagram of a frame structure for a simplified neighbor reporting element provided in an embodiment of this application; Figure 7c This is a schematic diagram of a frame structure for a 12-byte TBTT information length field provided in an embodiment of this application; Figure 8 This is a schematic diagram illustrating the interaction between a Non-AP MLD and an AP MLD for 802.1X authentication and four-way handshake to derive PTK and GTK, as provided in an embodiment of this application. Figure 9a This is a schematic diagram of part or all of the frame structure of the BSS transfer management query frame provided in the embodiments of this application; Figure 9b This is a schematic diagram of part or all of the frame structure of the BSS transfer management request frame provided in the embodiments of this application; Figure 9c This is a schematic diagram of part or all of the frame structure of the BSS transfer management response frame provided in the embodiments of this application; Figure 10 This is a schematic diagram of the Non-AP MLD switching AP MLD during roaming, provided in an embodiment of this application; Figure 11 This is a schematic diagram of the signaling interaction of a Non-AP MLD switching AP MLD during roaming, provided in an embodiment of this application. Figure 12a This is a schematic diagram illustrating the transition relationships between different states and the frame types allowed to be sent in different states, as provided in the embodiments of this application. Figure 12b This is another schematic diagram illustrating the transition relationships between different states and the frame types allowed to be sent in different states, as provided in the embodiments of this application. Figure 13a This is a schematic diagram of the interaction between Non-AP MLD and AP MLD during the initial association process provided in the embodiments of this application; Figure 13b This is another interactive diagram of Non-AP MLD and AP MLD during the initial association process provided in the embodiments of this application; Figure 13c This is another interactive diagram of Non-AP MLD and AP MLD during the initial association process provided in the embodiments of this application; Figure 14 This is a schematic diagram of the optimal association scenario during the Non-AP MLD movement process provided in the embodiments of this application; Figure 15 This is a schematic flowchart of an association method for non-co-located multi-link devices provided in an embodiment of this application; Figure 16 This is a schematic diagram illustrating the interaction between a Non-AP MLD and an AP MLD provided in an embodiment of this application; Figure 17 This is a schematic diagram of the structure of the communication device provided in an embodiment of this application; Figure 18 This is another structural schematic diagram of the communication device provided in the embodiments of this application. Detailed Implementation

[0045] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0046] To better understand the multi-link trial association method provided in the embodiments of this application, the system architecture and / or application scenarios of the multi-link trial association method provided in the embodiments of this application will be described below. It is understood that the scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application and do not constitute a limitation on the technical solutions provided in the embodiments of this application.

[0047] This application provides a multi-link trial association method for use in wireless communication systems. This method reduces data transmission interruption time during roaming for multi-link devices under IEEE 802.11be, and ensures uninterrupted data transmission during roaming by controlling the timing of updating the mapping information between stations and access points. The wireless communication system can be a wireless local area network (WLAN). The multi-link trial association method can be implemented by a communication device within the wireless communication system, or by a chip or processor within that device. This communication device can be a wireless communication device that supports parallel transmission across multiple links; for example, it can be called a multi-link device or a multi-band device. Optionally, based on the number of radio frequencies in the multi-link device, it can be further divided into single-radio multi-link devices and multi-radio multi-link devices.

[0048] A multi-radio multi-link device includes multiple affiliated stations (STAs). These affiliated stations can be access points (APs) or non-access point stations (non-AP STAs). For ease of description, this application refers to multi-link devices whose affiliated stations are APs as multi-link APs, multi-link AP devices, or AP multi-link devices (AP MLDs), and multi-link devices whose affiliated stations are non-AP STAs as multi-link Non-APs, multi-link Non-AP devices, or Non-AP multi-link devices (Non-AP MLDs). For ease of description, "multi-link devices include affiliated stations" is also briefly described in this application embodiment as "multi-link devices include stations."

[0049] The link identifier mentioned below is used to characterize the basic service set established by the AP MLD on a specific channel in a specific frequency band, namely (Operating Class, Channel Number, Basic Service Set Identifier (BSSID)). A Non-AP MLD establishes multiple transmission links by having multiple affiliated STAs simultaneously associate with different APs of the AP MLD through a single association operation. Both the Non-AP MLD and AP MLD can use the link identifier to indicate the corresponding link and the corresponding AP and Non-AP STA at both ends of the link. Therefore, when performing related signaling indications between the Non-AP MLD and AP MLD, only the corresponding link identifier needs to be carried, reducing signaling overhead.

[0050] In one example, when an AP multi-link device establishes a BSS, the management frame it sends, such as a beacon frame, carries elements including multiple link identification information fields. Each link identification information field includes a link identifier, and also one or more of the following: BSS identifier, operation class, and channel number, where the BSS identifier, operation class, and channel number correspond to the link identifier. In another example, during the establishment of a multi-link association, the AP MLD and the Non-AP MLD negotiate multiple link identification information fields. In subsequent communications, the AP MLD or the Non-AP MLD will use the link identifier to identify the sites at both ends of the corresponding link.

[0051] Multi-link devices can achieve wireless communication by following the IEEE 802.11 series of protocols. For example, they can follow a site with extremely high throughput or follow a site based on or compatible with IEEE 802.11be to achieve communication with other devices.

[0052] The multi-link trial association method provided in this application embodiment can be applied to multi-link device roaming scenarios in wireless communication systems, such as when at least one Non-AP multi-link device roams between at least two AP multi-link devices, or when at least one Non-AP multi-link device switches from one BSS to another within the same ESS.

[0053] See Figure 2 , Figure 2 This is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of this application. Figure 2 As shown, the wireless communication system includes: multiple AP multi-link devices (such as...) Figure 2 The system includes AP multi-link devices 100 and 200, and a Non-AP multi-link device 300. The AP multi-link device provides services to the Non-AP multi-link device, which can communicate with the AP multi-link device using multiple links, thereby improving throughput. Figure 2 The number of AP multi-link devices and Non-AP multi-link devices is merely an example.

[0054] For example, multi-link devices (such as...) Figure 2The AP multi-link device (any one of the AP multi-link device 100, AP multi-link device 200, and Non-AP multi-link device 300) is a device with wireless communication capabilities. This device can be a complete unit or a chip or processing system installed within a complete unit. Devices with these chips or processing systems installed can implement the methods and functions of the embodiments of this application under the control of these chips or processing systems. For example, the Non-AP multi-link device in the embodiments of this application has wireless transceiver capabilities, can support the 802.11 series protocols, and can communicate with AP multi-link devices or other Non-AP multi-link devices. For example, a Non-AP multi-link device is any user communication device that allows users to communicate with an AP and thus with a WLAN. For example, a Non-AP multi-link device can be a network-connected user device such as a tablet, desktop, laptop, notebook computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), or mobile phone; or an IoT node in the Internet of Things (IoT); or an in-vehicle communication device in the Internet of Vehicles (IoV); a Non-AP multi-link device can also be the chip and processing system in these terminals. The AP multi-link device in this application embodiment is an apparatus that provides services to a Non-AP multi-link device and can support the 802.11 series of protocols. For example, an AP multi-link device can be a communication server, router, switch, bridge, or other communication entity; or, an AP multi-link device can include various forms of macro base stations, micro base stations, relay stations, etc. Of course, an AP multi-link device can also be the chip and processing system in these various forms of devices, thereby implementing the methods and functions of the embodiments of this application.

[0055] Understandably, multi-link devices can support high-speed, low-latency transmission. With the continuous evolution of wireless LAN application scenarios, multi-link devices can be applied to more scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air quality monitoring nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things (IoT), entertainment terminals (e.g., AR, VR wearable devices), smart devices in smart offices (e.g., printers, projectors, etc.), vehicle-to-everything (V2X) devices, and some infrastructure in daily life scenarios (e.g., vending machines, supermarket self-service navigation kiosks, self-checkout machines, self-ordering machines, etc.). This application does not limit the specific forms of Non-AP multi-link devices and AP multi-link devices; these are merely illustrative examples. The 802.11 protocol can be a protocol that supports or is compatible with 802.11be.

[0056] Optional, see Figure 3 , Figure 3 This is a schematic diagram of a multi-link device provided in an embodiment of this application. The IEEE 802.11 standard focuses on the 802.11 physical layer (PHY) and MAC layer portions of the multi-link device. Figure 3 As shown, multiple STAs in a multi-link device share a single high MAC layer, but the low MAC layer and PHY layer are independent of each other. It is understood that the multiple STAs in a multi-link device can also be independent of each other at both the low MAC and PHY layers, and at the high MAC layer. This application does not limit the internal structure diagram of the multi-link device. Figure 3 This is merely an illustrative example. For instance, either the high MAC layer or the low MAC layer can be implemented by a processor in the chip system of a multi-link device, or they can be implemented by different processing modules in a single chip system.

[0057] In the embodiments of this application, the multi-link device may allow services with the same traffic identifier (TID) to be transmitted simultaneously on different links, or even allow the same data packets to be transmitted on different links; it may also disallow services with the same TID to be transmitted on different links, but allow services with different TIDs to be transmitted on different links.

[0058] Multi-link devices can operate in one or more frequency bands, including sub 1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and high frequency 60 GHz.

[0059] Optional, see Figure 4 , Figure 4 This is a schematic diagram illustrating the connection between an AP multi-link device and a Non-AP multi-link device. For example... Figure 4 As shown, both Non-AP multi-link devices and AP multi-link devices adopt a shared high MAC layer architecture. An AP multi-link device includes two APs, while a Non-AP multi-link device includes two STAs. One AP in an AP multi-link device can establish a link with one STA in a Non-AP multi-link device for communication. For example... Figure 4 In an AP multi-link device, AP1 establishes link 1 with STA1 in a Non-AP multi-link device for communication; Figure 4 In the AP multi-link device, AP2 establishes link 2 with STA2 in the Non-AP multi-link device for communication.

[0060] The above content describes the system architecture and / or application scenarios of the multi-link trial association method provided in the embodiments of this application. The multi-link communication method provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0061] In some feasible implementations, the Non-AP multi-link device mentioned in the embodiments of this application can be... Figure 2 The Non-AP multi-link device 300 in the middle, the first AP multi-link device can be Figure 2 The AP multi-link device 100 in the middle, the second multi-link device can be Figure 2 The AP multi-link device 200 in this application is also referred to as a STA multi-link device. It is understood that the Non-AP multi-link device in this embodiment can also be called a STA multi-link device, and therefore the Non-AP multi-link device and the STA multi-link device can be used interchangeably.

[0062] In some feasible implementations, the multi-link devices in the embodiments of this application all support simultaneous transmit and receive (STR) on multiple links, or the multi-link devices in the embodiments of this application have STR capability. A multi-link device with STR capability means that the channel spacing between any two radio frequency modules in the multi-link device is large enough so that the two radio frequency modules can operate independently without interfering with each other, supporting transmission on one link while normal reception on another link is possible.

[0063] Example 1 This application provides a multi-link trial association method, which utilizes multiple radios / links that can work simultaneously with a Non-AP MLD to perform trial associations with multiple AP MLDs, thereby enabling uninterrupted data transmission or reducing data transmission interruption time when multi-link devices are roaming.

[0064] See Figure 5 , Figure 5 This is a schematic flowchart of a multi-link trial association method provided in an embodiment of this application. Figure 5 As shown, the multi-link trial association method provided in this application includes, but is not limited to, the following steps: S101, when the partial link between the Non-AP MLD and the first AP MLD is in a disconnected state (or disabled), one or more first STAs of the Non-AP MLD send multi-link association request frames to one or more second AP MLDs respectively. These multi-link association request frames are used to request the Non-AP MLD to establish a tentative multi-link association with one or more second AP MLDs. The link between the first STA and the first AP MLD is in a disconnected state (or disabled), while the link between the one or more second STAs of the Non-AP MLD and the first AP MLD is in a connected state (or enabled).

[0065] S102, one or more second AP MLDs return multi-link association response frames to the Non-AP MLD.

[0066] Specifically, when there is only one disabled link between the Non-AP MLD and the first AP MLD (i.e., when there is only one first STA in the Non-AP MLD), the first STA in the Non-AP MLD with the disabled link to the first AP MLD sends a multi-link association request frame to a second AP MLD. When there are multiple disabled links between the Non-AP MLD and the first AP MLD (i.e., when there are multiple first STAs in the Non-AP MLD), any first STA in the Non-AP MLD can send a multi-link association request frame to a second AP MLD. Understandably, when there are multiple first STAs in the Non-AP MLD, these multiple first STAs can send multi-link association request frames to multiple second AP MLDs. Correspondingly, one or more second AP MLDs return a multi-link association response frame to the Non-AP MLD.

[0067] Optionally, the multi-link association request frame may include the status of the non-transmission link between the Non-AP MLD and the second AP MLD, such as disabled or enabled. Optionally, when the status is disabled, the multi-link association request frame may also carry a reason code field to indicate the reason why the link status between the Non-AP MLD and the second AP MLD is disabled. Specifically, if the status of a link between the Non-AP MLD and the second AP MLD is disabled, the reason code field can further indicate that the reason for the disabled status of the link is one of power saving, low received signal strength indication, tentative association, and association with the first AP MLD (i.e., "Associated with old AP MLD"). In this embodiment, the reason code field carried in the multi-link association request frame can be set to "Associated with old AP MLD".

[0068] Optionally, for Non-AP MLD, multiple links can be simultaneously associated with the AP MLD by performing multi-link association operations on a single link. The link that performs the multi-link association request / response frame exchange is called the Transmitted Link, and the other links are called Non-transmitted Links.

[0069] Optionally, if the APs in the second AP MLD can also be turned off, the multilink association response frame can also indicate whether each AP in the second AP MLD is in a disabled or enabled state.

[0070] Optionally, the status of the non-transmission link between the Non-AP MLD and the second AP MLD can also be implicitly indicated through TID-to-link mapping. This TID-to-link mapping can be carried in the multi-link association request / response frame, or a separate TID-to-mapping request can be sent after the multi-link association request / response frame interaction is completed to indicate the status of the non-transmission link between the Non-AP MLD and the second AP MLD.

[0071] Optionally, the multi-link association request frame may carry tentative association indication information, and optionally, it may also carry tentative association lifetime information. The tentative association indication information can be used to indicate whether to perform a tentative association. For example, setting the field carrying the tentative association indication information to 1 indicates that a tentative association is performed; setting the field to 0 indicates that a normal association defined by the existing protocol is performed. It is understood that this application embodiment does not limit the value and meaning of the field carrying the tentative association indication information. The tentative association lifetime information can be used to indicate the lifetime of the tentative association. When the time without interaction between the Non-AP MLD and the AP MLD exceeds this lifetime, the AP MLD deletes the information previously negotiated with the Non-AP MLD. The tentative association indication information and the tentative association lifetime information can be carried in the common information field of the multi-link aggregation (MLA) element in the multi-link association request frame. Optionally, Tentative Association indication information and Tentative Association lifetime information can also be included in a newly defined element. See also Figure 6a , Figure 6a This is a schematic diagram of the frame structure of a new element provided in an embodiment of this application. For example... Figure 6a As shown, the frame structure of this element includes an element identifier, length, control field, and tentative association lifetime. The control field uses 1 bit to indicate whether to perform a tentative association, with the remaining 7 bits reserved.

[0072] Optionally, the multi-link association request frame may carry a tentative association control field and a tentative association lifecycle. The tentative association control field includes three indicator bits: a Non-AP MLD trigger 802.1X authentication indicator bit, a Non-AP MLD trigger four-way handshake indicator bit, and a Non-AP MLD trigger STA-AP mapping notification indicator bit. Specifically, when the Non-AP MLD trigger 802.1X authentication indicator bit is set to 1, it indicates that the Non-AP MLD will actively send a message to trigger the start of the 802.1X authentication process; when the Non-AP MLD trigger four-way handshake indicator bit is set to 1, it indicates that the Non-AP MLD will actively send a message to trigger the start of the four-way handshake process; and when the Non-AP MLD trigger STA-AP mapping notification indicator bit is set to 1, it indicates that the Non-AP MLD will actively send a message to trigger STA-AP mapping notification. It is understood that the values ​​and meanings of the three indicator bits included in the above tentative association control field are not limited. The tentative association lifecycle information can be used to indicate the lifecycle of the tentative association. When there is no interaction between the Non-AP MLD and the AP MLD for more than this lifecycle, the APMLD deletes the information previously negotiated with the Non-AP MLD.

[0073] Optionally, the tentative association control field and the tentative association lifecycle can be carried in a newly defined element. See also Figure 6b , Figure 6b This is a schematic diagram of the frame structure of another new element provided in the embodiments of this application. For example... Figure 6b As shown, the frame structure of this element includes an element identifier, length, tentative association control field, and tentative association lifetime. The tentative association control field includes a 1-bit Non-AP MLD trigger 802.1X authentication indicator, a 1-bit Non-AP MLD trigger four-way handshake indicator, and a 1-bit Non-AP MLD trigger STA-AP mapping notification indicator; the remaining 4 bits are reserved.

[0074] Optionally, the Non-AP MLD can receive probing association capability indication information sent by each AP MLD. This probing association capability indication information can be used to indicate whether the AP MLD supports probing association. This probing association capability indication information can be carried in a Fast BSS Transition element, a Multi-Link Aggregation (MLA) element, or a Mobility Domain element. The Fast BSS Transition element can be carried in a Beacon frame.

[0075] Specifically, a 1-bit can be added to both the neighbor report element and the reduced neighbor report element to indicate whether a neighboring AP or its MLD supports tentative association. The neighbor report element describes a neighboring AP and its BSS information. An AP can indicate relevant information for all its neighbors by carrying multiple neighbor report elements. Specifically, a reserved bit in the BSSIDinformation field of the neighbor report element indicates whether the BSS supports tentative association. Similarly, a reserved bit in the BSS Parameter field of the reduced neighbor report element indicates whether the BSS supports tentative association.

[0076] See Figure 7a , Figure 7a This is a schematic diagram of a frame structure for a neighbor reporting element provided in an embodiment of this application. For example... Figure 7a As shown, the neighbor reporting element includes an element identifier, length, BSS identifier, BSSID information, operation class, channel number, physical layer type, and optional subelements. The BSSID field indicates the BSSID corresponding to the reported neighbor AP; the BSSID information field indicates relevant information about the reported BSSID; the Operating Class and channelNumber fields indicate the channel on which the reported BSSID is located; the PHY Type field indicates the physical layer type of the AP corresponding to the reported BSSID; and the Optional subelements field carries some optional subelements.

[0077] The BSSID information field carries the following specific information: 1. AP Reachability: Indicates whether the AP is reachable. 2. Security: Indicates whether the reporting AP supports the same security configuration as existing connections. 3. Key Scope: Indicates whether the reporting AP and the AP sending the report are the same authenticator. 4. Capabilities: Indicates some optional capability information of the reporting AP. 5. Mobility domain: Indicates whether the reporting AP and the AP sending the report are in the same mobility domain. 6. High Throughput: Indicates that the HT capabilities element of the reporting AP (carrying the optional subelement field) is the same as the HT capabilities element of the AP sending the report. 7. Very High Throughput: Indicates that the VHT capabilities element of the reporting AP is the same as the VHT capabilities element of the AP sending the report. 8. FTM (fine timing measurement): Indicates whether the reporting AP supports fine timing measurement. 9. High Efficiency field: Indicates that the HE capabilities element of the reporting AP is the same as the HE capabilities element of the AP sending the report. 10. ER (Extended range) BSS field: Indicates that the beacon sent by the reporting AP is transmitted using HE ER SU PPDU mode. 11. Collocated AP field: Indicates whether the reporting AP and the AP sending the report are co-located APs. 12. Unsolicited Probe Response Active field: Indicates whether the reporting AP has enabled active probe response. 13. Member of ESS with 2.4 / 5 GHz co-located AP field: Indicates whether the reporting AP is co-located with a 2.4 / 5 GHz AP and is a member of an extended service set. 14. OCT supported with reporting AP field: Indicates whether the reporting AP supports exchanging management frame type MPDUs via OCT (On-channel tunneling) mechanism.15. Co-located with 6 GHz AP field: Indicates whether the reporting AP is co-located with a 6 GHz AP. 16. Reserved field.

[0078] The Capabilities field also includes the following information fields: Spectrum management: indicates whether the reporting AP supports spectrum management functions; QoS (Quality of Service): indicates whether the reporting AP supports QoS mechanisms; APSD (Automatic Power Save Delivery): indicates whether the reporting AP supports automatic power save delivery mechanisms; Radio Measurement: indicates whether the reporting AP supports wireless measurement functions.

[0079] Optionally, the AP MLD can carry a simplified neighbor reporting element in management frames, such as beacon frames, or probe response frames. During scanning, the non-AP MLD receives association frames sent by the AP MLD to obtain information about surrounding neighboring APs, and then selects a suitable AP MLD for association.

[0080] See Figure 7b , Figure 7b This is a schematic diagram of a frame structure for a simplified neighbor reporting element provided in an embodiment of this application. For example... Figure 7b As shown, a simplified neighbor reporting element includes an element identifier, length, and one or more neighbor AP information fields. A neighbor AP information field includes a target beacon transmission time (TBTT) header, operation category, channel number, and a TBTT information set. The TBTT information set includes one or more TBTT information fields.

[0081] The TBTT info field header contains the following information: TBTT info Field Type, which indicates the type of TBTT info and, together with the TBTT info length field, indicates the format of the TBTT info field; Filteredneighbor AP, which indicates whether the SSIDs of all BSSs carried in the Neighbor AP info field match the SSIDs in the Probe Request frame; Reserved field (1 bit); TBTT info count, which indicates the number of TBTT info fields in the TBTT info set; and TBTT info Length, which indicates the length of each TBTT info field.

[0082] The specific information format carried by the different lengths of the TBTT info Length field is shown in Table 1 below.

[0083]

[0084] See Figure 7c , Figure 7c This is a schematic diagram of a frame structure for the 12-byte TBTT information length field provided in an embodiment of this application. For example... Figure 7c As shown, the 12-byte TBTT information length field includes the neighbor AP's TBTT offset, BSS identifier, short service set identifier, and BSS parameters. The Neighbor AP TBTT offset field indicates the offset between the reported BSS and the Beacon transmission time of the BSS that sent the report. The BSSID field indicates the BSS identifier corresponding to the reported BSS. The ShortSSID field indicates the service set identifier to which the BSS belongs. The BSS Parameter field indicates the relevant parameters of the BSS.

[0085] The BSS Parameter field specifically includes the following information: (1) OCT recommended: Indicates that the reporting BSS expects to exchange management type MPDUs with it via the OCT mechanism. (2) Same SSID: Indicates whether the reporting AP and the AP transmitting the report have the same SSID. (3) Multiple BSSID: Indicates whether the reporting AP belongs to a set of multiple BSSIDs. (4) Transmitted BSSID: If the reporting AP belongs to a set of multiple BSSIDs, it further indicates whether the reporting AP is a Transmitted BSSID or a non-transmitted BSSID. (5) Member Of ESS With 2.4 / 5 GHz Co-Located AP: Indicates whether the reporting AP is co-located with a 2.4 / 5 GHz AP (i.e., not a 6 GHz only AP) and is a member of an extended service set. (6) Unsolicited Probe Response Active: Indicates whether the reporting AP has enabled active probe response. (7) Co-located AP: Indicates whether the reporting AP is co-located with the AP transmitting the report. (8) Reserved field.

[0086] S103, Non-AP MLD performs 802.1X authentication and four-way handshake PTK and GTK derivation procedures with one or more second AP MLDs.

[0087] Specifically, after the multi-link association response frame indicates successful association, the Non-AP MLD and AP MLD perform 802.1X authentication to obtain the PMK, and through a four-way handshake, a pairwise transient key (PTK) and a group temporal key (GTK) can be derived. See also Figure 8 , Figure 8 This is a schematic diagram illustrating the interaction between a Non-AP MLD and an AP MLD for 802.1X authentication and a four-way handshake to derive PTK and GTK, as provided in an embodiment of this application. Figure 8As shown, the AP MLD sends an Extended Authentication Protocol (EAP) request / identity verification to the Non-AP MLD; the Non-AP MLD returns an EAP response / identity verification to the AP MLD; the AP MLD sends a RADIUS access request to the authentication server (AS), and so on. After the EAP is successful, a four-way handshake is performed to derive the PTK and GTK. Figure 8 As shown, the four-step handshake process for deriving PTK and GTK includes: Non-AP MLD sending Key Message 1 to AP MLD; AP MLD returning Key Message 2 to Non-AP MLD; Non-AP MLD sending Key Message 3 to AP MLD; and AP MLD returning Key Message 4 to Non-AP MLD. After obtaining PTK and GTK, Non-AP MLD and AP MLD encrypt the data packets using the corresponding keys according to the type of the data packets being sent.

[0088] Understandably, the 802.1X authentication and four-way handshake PTK and GTK derivation process between a Non-AP MLD and multiple Second AP MLDs can be referenced to the process of a single Non-AP MLD performing 802.1X authentication and four-way handshake PTK and GTK derivation with a single AP MLD, and will not be elaborated here. It is also understandable that a Non-AP MLD can simultaneously perform 802.1X authentication and four-way handshake PTK and GTK derivation with multiple Second AP MLDs to improve roaming success rates. This is because a First STA within a Non-AP MLD can perform 802.1X authentication and four-way handshake PTK and GTK derivation with one Second AP MLD, therefore multiple First STAs within a Non-AP MLD can simultaneously perform 802.1X authentication and four-way handshake PTK and GTK derivation with multiple Second AP MLDs.

[0089] S104, Non-AP MLD determines the final target AP MLD from one or more second AP MLDs.

[0090] S105, the Non-AP MLD sends an indication message to the target AP MLD to trigger the target AP MLD to update the mapping relationship between sites and access points in the distribution system (DS).

[0091] Specifically, the aforementioned indication information can be carried in the A-Control field. Optionally, the indication information can also be carried in a newly defined frame. For ease of description, the frame carrying this indication information will be referred to as the STA-APMapping Notify frame below. Understandably, the frame carrying this indication information can also be called the STA-AP Mapping trigger frame, etc. The embodiments of this application do not limit the name of the frame carrying this indication information.

[0092] Optionally, the Non-AP MLD can select a final target AP MLD from among the multiple second AP MLDs based on whether the association between the Non-AP MLD and the multiple second AP MLDs is successful, the capabilities of each second AP MLD, and the link quality between the Non-AP MLD and each second AP MLD. Understandably, in the case of only one second AP MLD, the Non-AP MLD directly sends indication information to that second AP MLD.

[0093] In an optional embodiment, the above steps S101-S103 can be described as follows: The Non-AP MLD uses one or more disabled links to simultaneously perform Multi-link Tentative Association with one or more second AP MLDs to perform various operations / processes, except for triggering the sending of the DS-STA-Notify.request primitive.

[0094] In another alternative embodiment, assuming the Non-AP MLD has three links, the Non-AP MLD can disable the status of two links with the first AP MLD, and then use the corresponding STA to simultaneously perform tentative reassociation with the two adjacent second AP MLDs. The Non-AP MLD determines which second AP MLD to reassociate with based on whether the association is successful, the capabilities of the two adjacent second AP MLDs, and the link quality between the Non-AP MLD and each second AP MLD. The Non-AP MLD can then skip 802.1X authentication and directly perform PTK and / or GTK derivation.

[0095] Optionally, since the Non-AP MLD can skip 802.1X authentication, the Non-AP MLD needs to send a newly defined frame to trigger a four-way handshake to derive PTK and GTK with the new AP MLD.

[0096] Understandably, in practical applications, the multi-link trial association method provided in this application embodiment may have more steps than S101-S104 described above. The following will describe the possible additional steps in the multi-link trial association method provided in this application embodiment.

[0097] In one example, before step S101, step S106 is included: the Non-AP MLD sends link status indication information to the first AP MLD. This link status indication information is used to indicate that the link status between the Non-AP MLD and the first AP MLD is Disabled. The link status indication information may include one or more link identifiers between the Non-AP MLD and the first AP MLD and the status corresponding to each link identifier. Optionally, the link status indication information may also indicate the reason why the status of one or more links between the Non-AP MLD and the first AP MLD is Disabled. It is understood that the reason why the link status between the Non-AP MLD and the first AP MLD is Disabled may include one of power saving, low received signal strength indication, and tentative association. It is also understood that in this embodiment, the reason why the link status indication information indicates that the status of one or more links between the Non-AP MLD and the first AP MLD is Disabled is a tentative association.

[0098] This application embodiment uses link status indication information to inform the first AP MLD that one or more links are disabled due to tentative association, thus preventing the first AP MLD from attempting to request the activation of one or more links due to a large amount of data to be transmitted.

[0099] In one example, before step S105 above, step S107 is included: The Non-AP MLD sends a first request to the first AP MLD, which requests the first AP MLD to provide its neighbor information. The neighbor information here can refer to other AP MLDs around the first AP MLD, or other BSSs around the BSS where the first AP MLD is located. Specifically, the Non-AP MLD can send a BSS Transition Management Query frame to the first AP MLD, which requests the first AP MLD to provide its neighbor information. The first AP MLD sends a BSS Transition Management Request frame to the Non-AP MLD. After receiving the BSS Transition Management Request frame, the Non-AP MLD returns a BSS Transition Management Response frame to the first AP MLD.

[0100] Optionally, the BSS transfer management query frame mentioned above may include a BSS transfer query reason field and a BSS transfer candidate list field. The BSS transfer query reason field can be used to indicate the reason for making the BSS transfer management query; the BSS transfer candidate list field can carry one or more Neighbor Report elements. See also Figure 9a , Figure 9a This is a schematic diagram of part or all of the frame structure of the BSS transfer management query frame provided in the embodiments of this application.

[0101] The BSS transfer management request frame mentioned above may include the following fields: a preferred candidate list included indicator (Bit 0), an abridged indicator (Bit 1), an immediate disassociation indicator (Bit 2), a BSS termination included indicator (Bit 3), an immediate ESS disassociation indicator (Bit 4), a disassociation timer field, and a validity interval field, etc.

[0102] See Figure 9b , Figure 9bThis is a schematic diagram of part or all of the frame structure of the BSS transfer management request frame provided in this application embodiment. When the "Preferred Candidate list included" indicator is at position 0, it indicates that the Non-AP MLD can ignore the information in the BSS Transition Candidate List field; when the "Preferred Candidate list included" indicator is at position 1, it indicates that the AP MLD expects the Non-AP MLD to process the information in the BSS Transition Candidate List field. The "Disassociation Imminent" indicator bit is used to indicate whether the Non-AP MLD will be disassociated. When the "Disassociation Imminent" indicator is at position 1, it indicates that the Non-AP MLD will be immediately disassociated by the AP MLD; when the "Disassociation Imminent" indicator is at position 0, it indicates that disassociation will not occur immediately. When the "BSS Termination Included" indicator is at position 1, it indicates that the BSS will be terminated; when the "BSS Termination Included" indicator is at position 0, it indicates that the BSS Termination Duration field will not be carried. The ESSDisassociation Imminent indicator bit indicates whether the Session Information URL field is carried and whether the Non-AP MLD will be disassociated by the ESS. When the ESS Disassociation Imminent indicator bit is 1, it means that the STA will be disassociated by the ESS, and the Session Information URL field will appear; when the ESS Disassociation Imminent indicator bit is 0, it means that the STA will not be disassociated by the ESS immediately. The Disassociation Timer field indicates how long after the AP MLD will send a disassociation frame to the Non-AP MLD. The Validity Interval field indicates the validity period of the BSS transition candidate list information.

[0103] The aforementioned BSS transfer management response frame may include a BSS transfer management status code field, a BSS termination delay field, a target BSS ID field, and a list of BSS transfer candidates field, etc. See also Figure 9c , Figure 9c This is a schematic diagram of part or all of the frame structure of the BSS transfer management response frame provided in the embodiments of this application. The BTM Status Code field indicates the status information responded to the BSS handover request, such as whether the BSS handover is accepted. The BSS Termination Delay field indicates how long the Non-AP MLD expects the AP MLD to wait before terminating the BSS. The Target BSSID indicates the identifier of the target BSS for the handover. The BSSTransition Candidate List field can carry one or more neighbor report information elements.

[0104] Optionally, the target BSS identifier in the BSS transfer management response frame of this application embodiment may carry the service access point (SAP) MAC address of the target APMLD.

[0105] Optionally, step S107 can also be: The Non-AP MLD actively sends a BSS transfer management query frame to the first AP MLD, requesting the first AP MLD to provide its neighbor information. Optionally, step S107 can also be: The Non-AP MLD switches to other channels (here, other channels can refer to channels different from the channel of the first AP MLD) to perform active or passive scanning to obtain the neighbor information of the first AP MLD.

[0106] In one example, after step S104, step S108 is included: the target AP MLD sends a DS-STA-Notify.request primitive to the distributed system. This DS-STA-Notify.request primitive carries mapping information between the target AP MLD and the Non-AP MLD, or the association relationship between the target AP MLD and the Non-AP MLD. This DS-STA-Notify.request primitive is used to inform the distributed system of STA-AP mapping information. This is because each Non-AP MLD can only be associated with one AP MLD, and the distributed system must know which AP MLD serves that Non-AP MLD, and then deliver packets destined for the MAC address of that Non-AP MLD to the corresponding AP MLD.

[0107] Optionally, before the target AP MLD sends the DS-STA-Notify.request primitive, the Non-AP MLD can negotiate block acknowledgement (BA) with the target AP MLD.

[0108] Optionally, the DS-STA-Notify.request primitive mentioned above can carry the SAP MAC address and update type of the Non-AP MLD. The update type can include three types: ADD, MOVE, and DELETE. ADD is used in the DS-STA-Notify.request primitive sent by the AP MLD when the Non-AP MLD is initially associated with another AP MLD. DELETE is used in the DS-STA-Notify.request primitive sent by the AP MLD when the Non-AP MLD is initially deassociated with another AP MLD. MOVE is used in the DS-STA-Notify.request primitive sent by the AP MLD when the Non-AP MLD switches from one AP MLD to a new AP MLD.

[0109] Therefore, in this embodiment, the update type carried by the DS-STA-Notify.request primitive sent by the target AP MLD is MOVE. When the client is a Non-AP MLD, the MAC Address in the DS-STA-Notify.request primitive sent by the target AP MLD is the SAP MAC Address of that Non-AP MLD. Optionally, the SAP MAC Addresses of both the Non-AP MLD and the AP MLD are also used in the STA-AP Mapping information mentioned above.

[0110] In one example, after step S104, step S109 is included: if the time during which no data transmission occurs between the first AP MLD and the Non-AP MLD in the channel idle state exceeds a certain predetermined time, the Non-AP MLD can proactively send a multi-link deassociation frame to the first AP MLD. Then, the Non-AP MLD can switch one or more second STAs whose remaining links with the first AP MLD are in the enabled state to the channel of the corresponding link of the target AP MLD, and notify the target AP MLD that the link status between the one or more second STAs and the target AP MLD becomes enabled.

[0111] Optionally, after step S104, the Non-AP MLD may immediately send a multi-link deassociation frame to the first AP MLD, switch to the channel of the corresponding link of the target AP MLD, and notify the target AP MLD that the status of the link has become Enabled.

[0112] It is understood that the above steps S108 and S109 can be executed simultaneously, or step S108 can be executed before step S109 or after step S109. The present application embodiment does not limit the execution order between steps S108 and S109.

[0113] In this embodiment, the Non-AP MLD disconnects part of the link with the currently associated AP MLD (i.e., the first AP MLD), and then uses the STA with the link status disconnected to send a multi-link association request frame to one or more second AP MLDs, requesting to establish a multi-link tentative association with the one or more second AP MLDs; the one or more second AP MLDs return a multi-link association response frame to the Non-AP MLD; if the multi-link association response frame indicates agreement to establish a multi-link tentative association, the Non-AP MLD can perform 802.1X authentication and a four-way handshake key exchange process with the one or more second AP MLDs; after the four-way handshake key exchange is completed, the Non-AP MLD selects a target APMLD from the one or more second AP MLDs based on whether the association is successful, the capabilities of each second AP MLD, and the link quality between the Non-AP MLD and each second AP MLD, and triggers the target AP MLD to update the mapping relationship between sites and access points in the distributed system through an indication message. It can reduce data transmission interruption time when multi-link devices are roaming. Ideally, it can make data transmission uninterrupted during roaming, that is, there is always an available link for data transmission at any time.

[0114] To better understand the technical solution of Embodiment 1 of this application, the technical solution of Embodiment 1 is illustrated below with two specific examples. Example 1 shows a specific flow of the multi-link trial association method provided in Embodiment 1; Example 2 shows a signaling interaction flow of the multi-link trial association method provided in Embodiment 1.

[0115] Understandably, the specific examples below assume that the first AP multi-link device is AP MLD1 and the second AP multi-link device is AP MLD2; AP MLD1 includes AP11 and AP12, and AP MLD2 includes AP21 and AP22; the Non-AP multi-link devices include STA1 and STA2. The Non-AP multi-link devices are associated with AP MLD1 before roaming occurs.

[0116] Example 1: See Figure 10 , Figure 10 This is a schematic diagram illustrating the switching of the APMLD during roaming using a Non-AP MLD provided in an embodiment of this application. Figure 10As shown, STA2@Non-AP MLD represents STA 2 of the Non-AP MLD; CH represents channel; CH1@Band 1 represents channel 1 on band 1. The process of switching AP MLDs during roaming for a Non-AP MLD includes, but is not limited to, the following steps: Step 1: The Non-AP MLD sends a link status indication message to AP MLD1. This link status indication message is used to indicate that the status of link 12 is disconnected (or disabled).

[0117] The link status indication information may carry the link identifier (link ID) corresponding to link 12, and the information may also indicate that the status of link 12 is Disabled.

[0118] Optionally, the link status indication information may also carry a Reason Code field to indicate the reason why link 12 is in a Disabled state. Understandably, the reason for the link being disconnected (or Disabled) could be power saving, low received signal strength indication (Low RSSI), or tentative association, etc. It is also understood that in this embodiment, the Reason Code field carried in the link status indication information can be set to tentative association.

[0119] Optionally, the link status indication information can be sent via link 11 or link 12; this embodiment does not limit the transmission. It is understood that the information carried by the link status indication information remains unchanged regardless of which link it is sent via.

[0120] Step 2: STA2 of Non-AP MLD (i.e., STA2@Non-AP MLD) hops to channel 2 of band 4 (i.e., CH2@Band 4) to initiate a multi-link exploratory association with AP MLD2.

[0121] Specifically, STA2@Non-AP MLD switches to link 22 to begin BSS transfer. First, it performs an 802.11 open authentication process with APMLD2, and then sends a multi-link reassociation request frame. This frame can carry tentative reassociation indication information, which can indicate whether the reassociation operation is tentative or whether the requested reassociation operation is tentative. This tentative reassociation indication information can be carried in the common information field of the multi-link aggregation (MLA) element in the multi-link reassociation request frame.

[0122] Optionally, the multi-link reassociation request frame can also indicate that the status of link 21 is Disabled. This is because STA 1 of the Non-AP MLD (i.e., STA1@Non-AP MLD) has not yet disconnected from AP MLD1, meaning that the status of link 21 between STA1 and AP11 is enabled. Further optionally, the multi-link reassociation request frame can also indicate the reason why the status of link 21 is Disabled by carrying a Reason Code field. Here, the Reason Code field can be set to "Association with old AP MLD".

[0123] Optionally, when reassociating with AP MLD2 or in a multi-link exploratory reassociation, the Non-AP MLD can use a new SAP MAC address. Specifically, the Non-AP MLD carries both its new and old SAP MAC addresses in the multi-link reassociation request frame. The old SAP MAC address of the Non-AP MLD can be used by AP MLD2 to retrieve incomplete data packets from AP MLD1.

[0124] Understandably, the old SAP MAC Address of the Non-AP MLD can refer to the SAP MAC Address used when the Non-AP MLD was associated with AP MLD1.

[0125] Understandably, because the Non-AP MLD uses the new SAP MAC Address to perform multi-link exploratory reassociation with AP MLD2, the Non-AP MLD needs to be re-authenticated for 802.1X.

[0126] Step 3: AP MLD2 returns a multi-link association response frame to STA 2 of Non-AP MLD on link 22.

[0127] If the multi-link reassociation response frame indicates that the Non-AP MLD and AP MLD2 are successfully associated, then the Non-AP MLD can perform negotiation and interaction operations with AP MLD2, such as establishing a BA Agreement. However, AP MLD2 cannot send the DS-STA-Notify.request primitive to notify the distributed system to update the STA-AP Mapping information.

[0128] Step 4: At a certain moment, the Non-AP MLD sends a STA-AP Mapping Notify frame to AP MLD 2 to trigger AP MLD 2 to send the DS-STA-Notify.request primitive to notify DS to update the STA-AP Mapping information.

[0129] The timing of when a Non-AP MLD sends a STA-AP Mapping Notify frame can be determined by a combination of factors. For example, a STA-AP Mapping Notify frame may be sent when the association between the Non-AP MLD and AP MLD2 is stronger than the association between the Non-AP MLD and AP MLD1.

[0130] Step 5: AP MLD2 returns an acknowledgment frame to Non-AP MLD and sends the DS-STA-Notify.request primitive to notify DS to update the STA-AP Mapping information.

[0131] In this embodiment, the DS-STA-Notify.request primitive carries the MAC address of the service access point (SAP) of the Non-AP MLD, and the update type carried by the DS-STA-Notify.request primitive is MOVE.

[0132] Optionally, after AP MLD2 sends the DS-STA-Notify.request primitive to notify DS to update the STA-AP Mapping information, it can retrieve the incomplete data transmitted to the Non-AP MLD from AP MLD1.

[0133] Step 6: STA1 of Non-AP MLD (i.e., STA1@Non-AP MLD) sends a multi-link disassociation frame to AP MLD1, and then jumps to channel 1 of band 3 (i.e., CH1@Band 3) to exchange data with AP21 of AP MLD2 (i.e., AP 21@AP MLD 2).

[0134] Specifically, the Non-AP MLD notifies AP MLD2 that link 21 has become enabled in two ways: implicit notification and explicit notification. Implicit notification occurs when the Non-AP MLD has uplink data to transmit; it can directly send uplink data on link 21, implicitly notifying AP MLD2 that link 21 is now enabled. Explicit notification occurs when the Non-AP MLD has no uplink data to transmit; it can send a QoS Null frame to AP MLD2 to notify AP MLD2 that link 21 is now enabled. Alternatively, it can notify AP MLD2 by including the link identifier and status information of link 21 in the A-Control field of the data frame sent on link 22.

[0135] Optionally, STA1 of the Non-AP MLD can be set to a time value. If the time during which no data transmission occurs between AP MLD1 and the Non-AP MLD exceeds this time value while the channel is idle, STA1 of the Non-AP MLD can proactively send a multi-link association frame to AP MLD1.

[0136] Optionally, the Non-AP MLD and AP MLD1 can be associated with a time value. If no data transmission occurs between AP MLD1 and Non-AP MLD for a period exceeding this time value during channel idle, Non-AP MLD can automatically disconnect the link without needing to send a multi-link association frame to AP MLD1.

[0137] Optionally, when the Non-AP MLD receives an acknowledgment frame (ACK frame) returned by AP MLD2 for key message 4, STA1 of the Non-AP MLD can send a multilink deassociation frame to AP MLD1.

[0138] Understandably, in practical applications, the process of switching AP MLDs during roaming using a Non-AP MLD can be less than [number missing]. Figure 10 The steps shown can also be more than [number missing]. Figure 10 The steps shown are not limited in this embodiment.

[0139] In this embodiment, the Non-AP MLD disconnects one or part of the link with the currently associated AP MLD (i.e., AP MLD1); then, the STA with the disconnected link state establishes a multi-link association with the new target AP MLD (i.e., AP MLD2); after the four-way handshake to derive PTK and GTK, the target AP MLD (i.e., AP MLD2) sends the DS-STA-Notify.request primitive to notify DS to update the STA-AP Mapping information, and retrieves the incomplete data transmitted to the Non-AP MLD from the previously associated AP MLD (i.e., APMLD1). This reduces data transmission interruption time; ideally, there is no data transmission interruption, meaning that at any given time, there is always an available link for data transmission.

[0140] Example 2: See Figure 11 , Figure 11 This is a schematic diagram of the signaling interaction of a Non-AP MLD switching APMLD during roaming, provided in an embodiment of this application. Figure 11 The process of switching AP MLDs during roaming in a Non-AP MLD may not include the aforementioned steps. Figure 10 In step 4, STA2 of the Non-AP MLD does not need to send a STA-AP Mapping Notify frame to AP MLD 2 to trigger AP MLD 2 to send the DS-STA-Notify.request primitive. This embodiment of the application restricts AP MLD2 to directly send the DS-STA-Notify.request primitive to DS after receiving Key Message 4, thereby enabling DS to update STA-AP Mapping information.

[0141] Optionally, after receiving the ACK frame returned by AP MLD2 for Key Message 4, the Non-AP MLD can immediately send a multi-link deassociation frame to AP MLD1, then switch to the link channel corresponding to AP MLD2, and notify AP MLD2 that the link status has become enabled. Alternatively, after receiving the ACK frame returned by AP MLD2 for Key Message 4, if there is no data transmission between AP MLD1 and the Non-AP MLD for more than a certain time during channel idle state, the Non-AP MLD can proactively send a multi-link deassociation frame to AP MLD1, then switch to the link channel corresponding to AP MLD2, and notify AP MLD2 that the link status has become enabled.

[0142] Understandable, from Figure 11 As can be seen from the signaling interaction process shown, the data transmission of Non-AP MLD is uninterrupted throughout the entire roaming process, that is, Non-AP MLD always has an available link for data transmission at any time.

[0143] Since Embodiment 1 of this application introduces TentativeAssociation in the association / reassociation process of multi-link devices to achieve uninterrupted data transmission, the frame types allowed to be transmitted between Non-AP MLD and AP MLD under different states also need to be redefined.

[0144] See Figure 12a , Figure 12a This is a schematic diagram illustrating the transition relationships between different states and the frame types allowed to be sent in different states, as provided in the embodiments of this application. Figure 12aAs shown, State 5 is a newly added state in this application embodiment. Under State 5, the frames allowed to be transmitted (or the data services allowed to be provided) include data frames, control frames, or management frames in Frame Class 1, Frame Class 2, Frame Class 3, and Frame Class 4. The various frames under Frame Class 1 and Frame Class 2 are the same as those in existing protocols. Data frames in Frame Class 3 can refer to data frames between STAs with Ethernet_Type notequeal to 0X0800 or 0X86dd in an infrastructure BSS or in an MBSS. Frame Class 4 can refer to data frames with Ethernet_Type=0x0800 or 0X86dd. Another way to define frame class 3 and frame class 4 is as follows: Frame class 3 can refer to a MAC frame header where Address 3 is the BSSID of the currently associated AP; frame class 4 can refer to a MAC frame header where Address 3 is the MAC address of a non-currently associated AP's BSSID. Understandably, before the AP MLD sends the DS-STA-Notify.request primitive, this embodiment only allows the transmission of frames in frame classes 1, 2, and 3. Only after the AP MLD sends the DS-STA-Notify.request primitive or the Non-AP MLD sends the STA-AP Mapping Notify frame is this embodiment allowed to transmit any frame, such as frames in frame classes 1, 2, 3, and 4. In other words, only after the AP MLD sends the DS-STA-Notify.request primitive is direct communication between the Non-AP MLD and the DS permitted; before that, communication with the DS is only permitted through the AP MLD as a proxy.

[0145] See Figure 12b , Figure 12b This is another schematic diagram illustrating the transition relationships between different states and the frame types allowed to be sent in different states, as provided in the embodiments of this application. For example... Figure 12b As shown, this application embodiment does not add any new states. In state 4, data frames, control frames, or management frames from frame class 1, frame class 2, frame class 3, and frame class 4 are allowed to be transmitted. Figure 12bAs can be seen, during the process of changing from state 3 to state 4, STA MLD and AP MLD have successfully performed a four-step handshake to derive PTK and GTK and triggered AP MLD to send the DS-STA-Notify.request primitive. Therefore, this application embodiment adapts to the multi-link trial association method of this application embodiment one by changing the condition of changing from state 3 to state 4.

[0146] Example 2 This application also provides an initial association method for multi-link devices. This initial association method utilizes multiple radios of a Non-AP MLD to simultaneously initiate exploratory associations with multiple AP MLDs (or APs). Then, based on the association results, the optimal AP MLD (or AP) is selected for association. This can improve the association success rate and speed of Non-AP MLDs in the initial association process.

[0147] It is understood that Embodiment 2 of this application can be applied alone in the initial association scenario of Non-AP MLD and AP MLD, or it can be applied in combination with Embodiment 1. This application does not limit this.

[0148] The initial association method provided in this application embodiment will be described below from the perspective of interaction between Non-AP MLD and AP MLD.

[0149] See one example. Figure 13a , Figure 13a This is a schematic diagram illustrating the interaction between Non-APMLD and AP MLD during the initial association process provided in this application embodiment. For example... Figure 13a As shown, taking 3 AP MLDs and 1 Non-AP MLD as examples, the initial association method provided in this application embodiment will be described. Specifically, the initial association method includes: (1) Non-AP MLDs on a link (such as Figure 13a Link 1) to an AP MLD (e.g. Figure 13a (1) Initiate association with AP MLD1 and indicate that other links with AP MLD1 are in a disabled state, and then perform 802.1X authentication to obtain PMK; (2) Non-AP MLD uses the remaining multiple links (such as AP MLD1) to establish association and instruct other links with AP MLD1 to be in a disabled state, and then performs 802.1X authentication to obtain PMK; Figure 13a Links 2 and 3 send Multi-link Re-association Request frames on different channels to initiate multi-link reassociation requests with other APs (such as Link 2 and Link 3). Figure 13a (2) Trial association of AP MLD2 and APMLD3, and indicate that other links are in a Disabled state in the association request frame; (3) Non-AP MLD determines the association success based on whether the association is successful and the individual AP MLDs (e.g., AP MLD2 and APMLD3) are associated, and indicates that other links are in a Disabled state in the association request frame; Figure 13a The capabilities of AP MLD1, AP MLD2, and AP MLD3, as well as the link quality between Non-APMLD and each AP MLD, are used to determine the target AP MLD, i.e., to determine which AP MLD to associate with in the end, and then the key (i.e., PTK and / or GTK) is derived.

[0150] Optionally, the Non-AP MLD can trigger a four-way handshake to derive PTK and GTK with the target AP MLD by sending a newly defined frame.

[0151] Understandable Figure 13a During the interaction between the Non-AP MLD and the AP MLD, as shown, the Non-AP MLD only needs to perform 802.1X authentication once, without having to perform multiple 802.1X authentications with multiple AP MLDs. This can reduce the association latency of the Non-AP MLD in the initial association process and improve the association speed.

[0152] See another example. Figure 13b , Figure 13b This is another interactive diagram of Non-APMLD and AP MLD during the initial association process provided in the embodiments of this application. For example... Figure 13b As shown, taking 3 AP MLDs and 1 Non-AP MLD as an example, the initial association method provided by the embodiments of this application will be described. Specifically, the initial association method includes: (a) Non-AP MLDs on multiple links (such as...) Figure 13b Send Multi-link Association Request (MLD) frames on Link 1, Link 2, and Link 3, and simultaneously with multiple AP MLDs (such as... Figure 13b (a) Initiate a tentative association with AP MLD1, AP MLD2, and AP MLD3, and indicate that other links are in a Disabled state in the association request frame; (b) Non-AP MLD determines the target AP MLD based on whether the association is successful, the capabilities of each AP MLD, and the link quality between Non-AP MLD and each AP MLD, that is, determines which AP MLD to associate with in the end; (c) Non-AP MLD triggers the process of 802.1X authentication, four-way handshake to derive PTK and GTK, etc. with the target AP MLD by sending EAP-Start.

[0153] Understandably, since EAP-Start is optional, the target AP MLD cannot initiate 802.1X authentication in this way.

[0154] Understandable Figure 13bAs shown in the interaction process between Non-AP MLD and AP MLD, the Non-AP MLD directly initiates exploratory associations with multiple AP MLDs simultaneously. After receiving a multi-link association response frame, it selects one AP MLD from these multiple AP MLDs to perform 802.1X authentication, four-way handshake to derive PTK and GTK, and other processes. This can improve the association success rate of the Non-AP MLD in the initial association process and increase the association speed by initiating exploratory associations in parallel (simultaneously).

[0155] See another example. Figure 13c , Figure 13c This is another interactive diagram of Non-APMLD and AP MLD during the initial association process provided in the embodiments of this application. For example... Figure 13c As shown, taking 3 AP MLDs and 1 Non-AP MLD as an example, the initial association method provided in this application embodiment will be described. Specifically, the initial association method includes: (A) Non-AP MLDs on multiple links (such as...) Figure 13c Send multi-link association request frames on links 1, 2, and 3, and simultaneously with multiple APMLDs (such as... Figure 13c (a) Initiate exploratory associations with AP MLD1, AP MLD2, and AP MLD3, and indicate that other links are in a disabled state in the association request frame. Then, perform 802.1X authentication with each AP MLD, and perform a four-way handshake to derive PTK and GTK processes; (b) Non-AP MLD determines the target AP MLD based on whether the association is successful, the capabilities of each AP MLD, and the link quality between the Non-AP MLD and each AP MLD, that is, determines which AP MLD to associate with in the end; (c) Non-AP MLD triggers the target AP MLD to send the DS-STA-Notify.request primitive to notify the distributed system of the corresponding STA-AP mapping information by sending a STA-AP Mapping Notify frame.

[0156] Understandable Figure 13c In the interaction process between the Non-AP MLD and the AP MLD shown, the Non-AP MLD directly initiates exploratory associations with multiple AP MLDs simultaneously, and performs 802.1X authentication with each AP MLD, a four-way handshake to derive PTK and GTK processes, etc. Finally, it selects one AP MLD from the multiple AP MLDs and sends a STA-AP Mapping Notify frame to it to trigger the target AP MLD to send the DS-STA-Notify.request primitive. This can improve the association success rate of the Non-AP MLD in the initial association process.

[0157] Example 3 This application also provides a method for associating non-collocated multi-link devices in a Non-AP MLD roaming scenario. The following description will illustrate the method for associating non-collocated multi-link devices provided in this application, taking into account the optimal association scenario for Non-AP MLDs. For ease of description, it is assumed that the Non-AP MLD includes two STAs, STA1 and STA2, and the AP MLD includes two APs, AP1 and AP2; one link or AP of the AP MLD can operate in the 2.4GHz band, and the other link or AP can operate in the 5GHz band. It is understood that in practical applications, the Non-AP MLD may include more than two STAs, and the AP MLD may include more than two APs. In cases where the Non-AP MLD includes more than two STAs or the AP MLD includes more than two APs, the description of two STAs and two APs in this application can be referred to, and will not be repeated here.

[0158] See Figure 14 , Figure 14 This is a schematic diagram of the optimal association scenario during the Non-AP MLD movement process provided in the embodiments of this application. For example... Figure 14 As shown, when the Non-AP MLD remains in region 1, its two STAs are associated with the two APs in AP MLD1. When the Non-AP MLD moves from region 1 to region 2 and remains there, its two STAs can be associated with the APs operating in the 2.4 GHz band in AP MLD1 and AP MLD2 respectively, establishing a Non-Collocated MLD3, which includes the APs operating in the 2.4 GHz band in both AP MLD1 and AP MLD2. When the Non-AP MLD moves from region 2 to region 3 and remains there, its two STAs are associated with the two APs in AP MLD2.

[0159] In the above Figure 14 For further details on the optimal association scenario shown, please refer to [link / reference]. Figure 15 , Figure 15 This is a schematic flowchart of an association method for non-co-located multi-link devices provided in an embodiment of this application. Figure 15 As shown, the association method for this non-co-located multi-link device includes, but is not limited to, the following steps: S201, Non-AP MLD sends a multi-link association request frame to AP MLD2.

[0160] S202, AP MLD2 sends a multi-link setup request (MLD Setup Request) to AP MLD1.

[0161] S203, AP MLD1 returns a multi-link setup response (MLD Setup Response) to AP MLD2.

[0162] S204, AP MLD2 returns a multi-link association response frame to Non-AP MLD.

[0163] Optionally, to better understand the association method for non-co-located multi-link devices provided in the embodiments of this application, the following explanation focuses on the interaction between the Non-AP MLD and the AP MLD. See [link to relevant documentation]. Figure 16 , Figure 16 This is a schematic diagram illustrating the interaction between a Non-AP MLD and an AP MLD provided in an embodiment of this application. For example... Figure 16 As shown, AP MLD1 includes AP11 and AP12, AP MLD2 includes AP21 and AP22, and Non-AP MLD includes STA1 and STA2. AP11 and AP22 can operate in the 5GHz band, while AP12 and AP22 can operate in the 2.4GHz band. CH1@2.4GHz represents channel 1 in the 2.4GHz band, CH1@5GHz represents channel 1 in the 5GHz band, and similarly, CH2@2.4GHz represents channel 2 in the 2.4GHz band, and CH2@5GHz represents channel 2 in the 5GHz band. Figure 16 As shown, after the Non-AP MLD indicates that the link (link 11) between STA1 and AP11 is disabled, or the Non-AP MLD disconnects the link (link 11) between STA1 and AP11, STA1 of the Non-AP MLD sends a Multi-link Association Request to AP MLD2; AP22 of AP MLD2 sends an MLD Setup Request to AP12 of AP MLD1 to request the establishment of a Non-collocated MLD3; AP12 of AP MLD1 returns an MLD Setup Response to AP22 of AP MLD2 in response to the MLD Setup Request; AP MLD2 returns a Multi-link Association Response to STA1 of the Non-AP MLD in response to the Multi-link Association Request.

[0164] Optionally, the MLD Setup Response can respond to the MLD Setup Request by agreeing or rejecting. If the MLD Setup Response indicates agreement to establish a Non-collocated MLD3, then AP22 and AP12 can share a high MAC layer, or in other words, AP22 and AP12 form a new logical multi-link device (i.e., Non-collocated MLD3). In subsequent configuration processes, AP22 and AP12 can be assigned a unified sequence number, PTK, etc. Understandably, in this scenario, Non-AP MLD can be viewed as a switch from AP MLD1 to Non-collocated MLD3.

[0165] The implementation methods of steps S201 and S204 in this application embodiment can refer to the implementation methods of steps S101 and S102 in embodiment one of this application, and will not be repeated here.

[0166] Optionally, the multi-link establishment request may carry the following information: relevant information about STA1 and relevant information about Non-collocated MLD3 in the Non-AP MLD. The multi-link establishment response may carry the following information: status code and relevant information about Non-collocated MLD3. Understandably, AP22 and AP11 negotiate relevant information about Non-collocated MLD3 through multi-link establishment requests and responses. The relevant information about STA1 may include STA1's SAP MAC Address, STA1's MAC Address indication, and anchor link indication, etc. The relevant information about Non-collocated MLD3 may include the Non-collocated MLD3's SAP MAC Address, the link information corresponding to AP22 in AP MLD2, and the link information corresponding to AP12 in AP MLD1.

[0167] In the multi-link establishment request, the link information corresponding to AP22 of AP MLD2 may include the link identifier (LinkID), operating class, channel number, basic service set identifier (BSSID), and other relevant information for AP22; the link information corresponding to AP12 of AP MLD1 may include Link ID, operating class, channel number, BSSID, etc. In the multi-link establishment response, the link information corresponding to AP22 of AP MLD2 may include Link ID, operating class, channel number, BSSID, etc.; the link information corresponding to AP12 of AP MLD1 may include Link ID, operating class, channel number, BSSID, and other relevant information for AP12.

[0168] In this application embodiment, Non-collocated MLD3 is established through multi-link establishment requests and responses during the exploratory association process between Non-AP MLD and AP MLD2, thereby realizing the association between Non-AP MLD and Non-collocated MLD3, and providing an association method under optimal association scenarios.

[0169] The foregoing details the method provided in this application. In order to facilitate better implementation of the above-described solutions in the embodiments of this application, the embodiments of this application also provide corresponding devices or equipment.

[0170] This application embodiment can divide the site multi-link device or access point multi-link device into functional modules according to the above method examples. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0171] In the case of using integrated units, see Figure 17 , Figure 17 This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device 1 can be a Non-AP MLD or a chip within a Non-AP MLD, such as a Wi-Fi chip. Figure 17 As shown, the communication device 1 includes a processing unit 11 and a transceiver unit 12.

[0172] Processing unit 11 is used to generate a multi-link association request frame; transceiver unit 12 is used to send a multi-link association request frame to one or more second AP MLDs, the multi-link association request frame being used to initiate a multi-link exploratory association between a Non-AP MLD and one or more second AP MLDs; the transceiver unit 12 is also used to send an indication message to a target AP MLD when the multi-link exploratory association between the Non-AP MLD and one or more second AP MLDs is successful, to trigger the target AP MLD to update the mapping relationship between the site and the access point, the target AP MLD being a second AP MLD determined from one or more second AP MLDs.

[0173] In one possible design, the transceiver unit 12 is further configured to: send link status indication information to the first AP MLD, the link status indication information being used to indicate that the link status between one or more first STAs of the Non-AP MLD and the first AP MLD is disconnected.

[0174] The communication device 1 of this application embodiment has any of the functions of the Non-AP MLD in the above method, which will not be described again here.

[0175] See Figure 18 , Figure 18 This is another schematic diagram of the communication device provided in the embodiments of this application. The communication device 2 can be a target AP MLD or a chip within the target AP MLD, such as a Wi-Fi chip. Figure 18 As shown, the communication device 2 includes a transceiver unit 21 and a processing unit 22.

[0176] The transceiver unit 21 is configured to receive a multi-link association request frame from a Non-AP MLD, which requests the Non-AP MLD to perform a multi-link exploratory association with a target AP MLD; the transceiver unit 21 is also configured to receive indication information from the Non-AP MLD when the multi-link association response frame returned by the target AP MLD indicates successful association, which triggers the target AP MLD to update the mapping relationship between the site and the access point; the processing unit 22 is configured to generate mapping information between the site and the access point; the transceiver unit 21 is also configured to send the mapping information between the site and the access point, which indicates that the mapping relationship between the site and the access point is updated from the association between the Non-AP MLD and the first AP MLD to the association between the Non-AP MLD and the target AP MLD.

[0177] The communication device 2 in this embodiment has any of the functions of the target AP MLD in the above method, which will not be described in detail here.

[0178] The above describes the Non-AP MLD and target AP MLD according to embodiments of this application. The following describes the possible product forms of the Non-AP MLD and target AP MLD. It should be understood that any product possessing the above-described features... Figure 17 Any product of any form that possesses the aforementioned Non-AP MLD functionality, and any product that has the above-mentioned Figure 18 Any form of product that embodies the functionality of the target AP MLD falls within the protection scope of this application. It should also be understood that the following description is merely illustrative and does not limit the product form of the Non-APMLD and target AP MLD in this application to these specific examples.

[0179] As a possible product form, the Non-AP MLD and target AP MLD described in the embodiments of this application can be implemented by a general bus architecture.

[0180] The Non-AP MLD includes a processor and a transceiver internally connected to the processor. The processor generates a multi-link association request frame, and the transceiver sends this frame to one or more second AP MLDs to initiate a tentative multi-link association between the Non-AP MLD and the one or more second AP MLDs. The transceiver also sends an indication message to a target AP MLD (which is determined from the one or more second AP MLDs) if the tentative multi-link association between the Non-AP MLD and the one or more second AP MLDs is successful. This triggers the target AP MLD to update the site-to-access point mapping. Optionally, the Non-AP MLD may also include a memory for storing instructions executed by the processor.

[0181] The target AP MLD includes a processor and a transceiver internally connected to the processor. The transceiver is configured to receive multi-link association request frames from a Non-AP MLD, requesting the Non-AP MLD to initiate a multi-link exploratory association with the target AP MLD. The transceiver is also configured to receive indication information from the Non-AP MLD when the target AP MLD returns a multi-link association response frame indicating successful association. This indication information triggers the target AP MLD to update the site-to-access point mapping relationship. The processor generates site-to-access point mapping information, and the transceiver is further configured to send this mapping information, indicating that the site-to-access point mapping relationship has been updated from an association between the Non-AP MLD and a first AP MLD to an association between the Non-AP MLD and the target AP MLD. Optionally, the target AP MLD may also include a memory for storing instructions executed by the processor.

[0182] As a possible product form, the Non-AP MLD and target AP MLD described in the embodiments of this application can be implemented by a general-purpose processor.

[0183] A general-purpose processor implementing a Non-AP MLD includes processing circuitry and an input / output interface internally connected and communicating with the processing circuitry. The processing circuitry generates a multi-link association request frame, and the input / output interface sends this frame to one or more second AP MLDs. This frame initiates a tentative multi-link association between the Non-AP MLD and one or more second AP MLDs. The input / output interface also sends an indication message to a target AP MLD (identified from one or more second AP MLDs) upon successful tentative multi-link association between the Non-AP MLD and the target AP MLD, triggering the target AP MLD to update the site-to-access point mapping. Optionally, the general-purpose processor may further include a storage medium for storing instructions executed by the processing circuitry.

[0184] A general-purpose processor implementing the target AP MLD includes processing circuitry and an input / output interface internally connected and communicating with the processing circuitry. The input / output interface is used to receive a multi-link association request frame from a Non-AP MLD, which requests the Non-AP MLD to initiate a multi-link exploratory association with the target AP MLD. The input / output interface is also used to receive indication information from the Non-AP MLD when the target AP MLD returns a multi-link association response frame indicating successful association. This indication information triggers the target AP MLD to update the site-to-access point mapping relationship. The processing circuitry generates site-to-access point mapping information. The input / output interface is also used to send the site-to-access point mapping information, which indicates that the site-to-access point mapping relationship has been updated from an association between the Non-AP MLD and a first AP MLD to an association between the Non-AP MLD and the target AP MLD. Optionally, the general-purpose processor may further include a storage medium for storing instructions executed by the processing circuitry.

[0185] As a possible product form, the Non-AP MLD and target AP MLD described in the embodiments of this application can also be implemented using the following: one or more FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

[0186] It should be understood that the sequence generation devices of the various product forms described above have any of the functions of the Non-AP MLD in the above method embodiments, which will not be repeated here; the sequence receiving devices of the various product forms described above have any of the functions of the APMLD in the above method embodiments, which will not be repeated here.

[0187] This application also provides a computer-readable storage medium storing computer program code. When the processor executes the computer program code, the electronic device performs the method in any of the foregoing embodiments.

[0188] This application also provides a computer program product that, when run on a computer, causes the computer to perform the methods in any of the foregoing embodiments.

[0189] This application also provides a communication device, which can exist in the form of a chip. The device includes a processor and an interface circuit. The processor is used to communicate with other devices through a receiving circuit, so that the device can execute the method in any of the foregoing embodiments.

[0190] This application also provides a wireless communication system, including at least one site multilink device and at least two access point multilink devices, wherein the site multilink device and the access point multilink device can perform the methods in any of the foregoing embodiments.

[0191] The steps of the methods or algorithms described in this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a core network interface device. Of course, the processor and storage medium can also exist as discrete components in the core network interface device.

[0192] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer-readable storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

[0193] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above description is only a specific embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this application should be included within the scope of protection of this application.

Claims

1. A multi-link trial association method, characterized in that, include: Non-AP MLD sends a request frame to one or more second AP MLDs, the request frame including tentative association indication information, the tentative association indication information being used to indicate whether to perform multi-link tentative association; The Non-AP MLD receives response frames.

2. The method according to claim 1, characterized in that, The tentative association indication information indicates that multi-link tentative association should be performed, including: not updating the mapping relationship between sites and access points.

3. The method according to claim 1, characterized in that, The tentative association indication information indicates that multi-link tentative association should not be performed, including updating the mapping relationship between sites and access points.

4. The method according to claim 2 or 3, characterized in that, The mapping information between the site and the access point includes the SAP Media Access Control MAC address of the Non-AP MLD and the SAP MAC address of the target AP MLD; the target AP MLD is one of the one or more second AP MLDs.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: The Non-AP MLD receives a beacon frame, which includes a simplified neighbor reporting element. The simplified neighbor reporting element includes tentative association capability indication information, which can be used to indicate whether the second APMLD supports tentative association.

6. The method according to any one of claims 1 to 5, characterized in that, The request frame also includes a lifecycle for tentative association.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: The Non-AP MLD sends a Basic Service Set (BSS) transfer management query frame to the first AP MLD. The BSS transfer management query frame is used to request the first AP MLD to provide feedback on the first AP MLD's neighbor information. The Non-AP MLD receives BSS transfer management request frames.

8. A communication device, characterized in that, Includes modules or units for performing the method as described in any one of claims 1 to 7.

9. A communication device, characterized in that, The device includes a processor and a transceiver internally connected to the processor, the processor being configured to support the communication device in performing the method as described in any one of claims 1 to 7, and the transceiver being configured to support communication between the communication devices.

10. A communication device, characterized in that, It includes a processor and an interface circuit, the processor being configured to communicate with other devices via the interface circuit, causing the chip or chip system to perform the method as described in any one of claims 1 to 7.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 7.

12. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1 to 7.

Images