Multilink communication method, communication device, and communication system

Abstract

A multilink communication method, communication device, and communication system are provided and are applicable to wireless local area network systems that support 802.11 series protocols, such as IEEE 802.11ax next-generation Wi-Fi protocols like 802.11be, Wi-Fi 7, or EHT, and in other examples, next-generation 802.11be protocols like Wi-Fi 8, UHR, or Wi-Fi AI, and may also be applicable to wireless personal area network systems based on ultra-wideband (UWB) or sensing systems. The method includes the following: an AP transmits a first communication frame, and correspondingly an STA receives the first communication frame, the first communication frame including identification information of a first access point multilink device AP MLD and first instruction information, the first instruction information indicating the termination time of the first AP MLD. This enables the termination of the first AP MLD.

Description

Technical Field

[0001] [Cross-Reference to Related Applications] This application claims the priority of Chinese Patent Application No. 202310305592.7, titled "MULTI-LINK COMMUNICATION METHOD, COMMUNICATION APPARATUS, AND COMMUNICATION SYSTEM", filed with the China National Intellectual Property Administration on March 24, 2023, the entire content of which is incorporated herein by reference.

[0002] [Technical Field] This application relates to the field of communication technologies, and particularly to multi-link communication methods, communication apparatuses, and communication systems.

Background Art

[0003] A multi-link device (MLD) is a device having a plurality of stations that operate simultaneously on different frequency bands or channels. By performing a multi-link establishment operation on one link, a non-access point (AP) multi-link device (non-AP MLD) can achieve association with an AP multi-link device (AP MLD) and may establish multiple links simultaneously.

[0004] For example, an AP MLD may include collocated AP MLDs and non-collocated AP MLDs. A collocated AP MLD can be understood as an AP MLD where the MAC layer and PHY layer are located on the same physical device. A non-collocated AP MLD can be understood as an AP MLD where the upper medium access control (MAC), lower MAC, and physical layer (PHY) are not located on the same physical device, and the upper MAC and lower MAC of the AP MLD are connected via a wired or wireless interface.

[0005] In some scenarios (such as software upgrades and maintenance, and device failures), coexisting or non-coexisting AP MLDs need to be terminated. Therefore, how to terminate coexisting or non-coexisting AP MLDs is an issue that urgently needs to be resolved. [Overview of the project]

[0006] Embodiments of this application disclose a multilink communication method, communication device, and communication system for terminating a coexisting AP MLD or a non-coexisting AP MLD such that a non-AP MLD associated with a coexisting AP MLD or a non-coexisting AP MLD performs a basic service set (BSS) transition in a timely manner.

[0007] According to a first aspect, an embodiment of this application provides a multilink communication method. The method is applied to a first communication device. The method is The steps include determining a first communication frame, wherein the first communication frame includes identification information of a first access point multilink device (AP MLD) and first instruction information, the first instruction information indicating the end time of the first AP MLD, and transmitting the first communication frame.

[0008] In this embodiment of the application, the first communication device may be an AP, the AP may cooperate with a first AP MLD, and the AP may be called an affiliated AP. The first AP MLD may be a coexisting AP MLD or a non-coexisting AP MLD. The first communication frame may be a beacon frame, and when the first AP MLD needs to terminate, the first communication frame may be transmitted using the affiliated AP to indicate that the first AP MLD should terminate and to indicate the termination time of the first AP MLD, so that a non-AP MLD associated with the first AP MLD can perform a BSS transition in a timely manner, enabling the first AP MLD to be terminated or removed, thereby achieving the termination of the first AP MLD.

[0009] According to a second aspect, an embodiment of this application provides a multilink communication method. The method is applied to a second communication device. The method is The steps include receiving a first communication frame, the first communication frame comprising identification information of a first access point multilink device AP MLD and first instruction information, the first instruction information indicating the end time of the first AP MLD, and analyzing the first communication frame.

[0010] In this embodiment of the application, the second communication device may be an STA, which cooperates with a non-AP MLD. The first AP MLD may be a coexisting AP MLD or a non-coexisting AP MLD. When the first AP MLD needs to terminate, the first communication frame may be transmitted using a coexisting AP to indicate that the first AP MLD should terminate and to indicate the termination time of the first AP MLD, so that a non-AP MLD associated with the first AP MLD can perform a BSS transition in a timely manner, enabling the first AP MLD to be terminated or removed, thereby achieving the termination of the first AP MLD.

[0011] In possible implementations, referring to the first or second embodiment, the first communication frame further includes a sixth instruction information, the sixth instruction information indicating a candidate peripheral node to perform a BSS transition.

[0012] In this embodiment of the application, the sixth instruction information may include information about peripheral AP MLDs of the first AP MLD or peripheral APs of the first AP MLD's affiliated APs. When the first AP MLD needs to terminate, the first communication frame may be transmitted by using the first AP MLD's affiliated APs to indicate the termination time of the first AP MLD and candidate peripheral nodes to perform the BSS transition, so that a non-AP MLD associated with the first AP MLD performs the BSS transition. It should be noted that the first communication frames transmitted by all affiliated APs of the first AP MLD may carry the sixth instruction information, though not exactly the same.

[0013] Referring to the first or second embodiment, in a possible implementation, the first AP MLD is a non-coexistent AP MLD.

[0014] In this embodiment of the application, the first AP MLD is a non-coexistent AP MLD, i.e., the first instruction information in the first communication frame indicates the termination time of the non-coexistent AP MLD, thereby achieving the termination of the non-coexistent AP MLD.

[0015] Referring to the first or second embodiment, in a possible implementation, the first AP MLD is a coexisting AP MLD, and the first communication frame further includes identification information of a non-coexisting AP MLD with which the coexisting AP MLD cooperates.

[0016] In this embodiment of the application, the first AP MLD is a coexisting AP MLD, i.e., the first instruction information in the first communication frame indicates the termination time of the coexisting AP MLD, thereby terminating the coexisting AP MLD. The identification information of a non-coexisting AP MLD may include the MAC address of the non-coexisting AP MLD, and the first communication frame carries the identification information of the non-coexisting AP MLD to indicate whether the coexisting AP MLD will cooperate with the non-coexisting AP MLD, so that the non-AP MLD that receives the first communication frame determines which non-coexisting AP MLD the coexisting AP MLD will cooperate with, and so that the non-AP MLD can transition to another coexisting AP MLD within the non-coexisting AP MLD.

[0017] In a possible implementation, referring to the first or second embodiment, the first instruction information includes a first duration, the first duration indicating that the first AP MLD terminates after the first duration.

[0018] In this embodiment of the application, the first unit of duration may be a time unit (TU), i.e., the first instruction information indicates the number of time units after which the first AP MLD will end.

[0019] In possible implementations, referring to the first or second embodiment, the identification information of the first AP MLD and the first instruction information are included in the reconstructed multilink element of the first communication frame.

[0020] In this embodiment of the application, the first communication frame may be a beacon frame, the beacon frame carrying a reconfigured multilink element, the identification information and first instruction information of the first AP MLD included in the reconfigured multilink element. When the first AP MLD is a non-coexistent AP MLD, to indicate that the non-coexistent AP MLD should terminate, the non-coexistent AP MLD includes a reconfigured multilink element in a beacon frame transmitted on the link where each cooperating AP of each coexistent AP MLD that interacts with the non-coexistent AP MLD is located. When the first AP MLD is a coexistent AP MLD, to indicate that the coexistent AP MLD should terminate, the coexistent AP MLD includes a reconfigured multilink element in a beacon frame transmitted on the link where each cooperating AP of the coexistent AP MLD is located.

[0021] In a possible implementation, referring to the first or second embodiment, the first communication frame further includes, namely, instructional information indicating the reason for termination of the first AP MLD and at least one of one or more peripheral report elements, the one or more peripheral report elements including information about peripheral access point APs of APs that cooperate with the first AP MLD.

[0022] In this embodiment of the application, the first communication frame may also be a functional frame defined to indicate that the first AP MLD is terminating. For example, the first communication frame may be an AP MLD termination announcement frame. The communication frame may include a reason code and one or more peripheral report elements, the reason code indicating the reason for the termination of the first AP MLD. When the first AP MLD needs to terminate, the first AP MLD may include a reason code and one or more peripheral report elements in the first communication frame transmitted by the allied APs to indicate that a non-AP MLD associated with the first AP MLD will perform a BSS transition based on one or more peripheral report elements. It can be understood that the peripheral report elements carried in the first communication frame transmitted by all allied APs of the first AP MLD do not have to be exactly the same.

[0023] According to a third aspect, embodiments of this application provide a multilink communication method, which is applied to a first non-coexistent AP MLD. The method includes the following:

[0024] The first non-coexistent AP MLD generates a BSS transition management (BTM) request frame, the BTM request frame contains the identification information of the second non-coexistent AP MLD, and the first non-coexistent AP MLD sends the BTM request frame by using the cooperating AP.

[0025] In this embodiment of this application, when the first non - co - existent AP MLD needs to end, in order to indicate that the non - AP MLD associated with the first non - co - existent AP MLD can transition to the second non - co - existent AP MLD, the first non - co - existent AP MLD may include the identification information of the second non - co - existent AP MLD in the generated BTM request frame, so that as a result, the first non - co - existent AP MLD can be ended or removed. The BTM request frame may be generated by the first non - co - existent AP MLD, or the BTM request frame may be generated by a co - existent AP MLD that cooperates with the first non - co - existent AP MLD, or the BTM request frame may be generated by an associated AP of the first non - co - existent AP MLD. It is understood that this is not limited in this application.

[0026] According to a fourth aspect, an embodiment of this application provides a multi - link communication method. The method is applied to a non - AP MLD. The method includes the step of receiving a BTM request frame from an associated AP, where the associated AP cooperates with the first non - co - existent AP MLD, and the BTM request frame includes an identifier of the second non - co - existent AP MLD, and the step of analyzing the BTM request frame.

[0027] In this embodiment of this application, when the first non - co - existent AP MLD needs to end, in order to indicate that the non - AP MLD associated with the first non - co - existent AP MLD can transition to the second non - co - existent AP MLD, the first non - co - existent AP MLD may include the identification information of the second non - co - existent AP MLD in the generated BTM request frame, so that as a result, the first non - co - existent AP MLD can be ended or removed.

[0028] Referring to the third aspect or the fourth aspect, in a possible implementation manner, the address information field of the BTM request frame includes the identification information of the first non - co - existent AP MLD.

[0029] In this embodiment of the application, the address information field of the BTM request frame may include an address 1 field, an address 2 field, and an address 3 field, where address 1 of the BTM request frame may be set to a broadcast address, and address 3 of the BTM frame may be set to the MAC address of a first non-coexistent AP MLD. For a non-AP MLD associated with the first non-coexistent AP MLD (e.g., a UHR non-AP MLD), after receiving the BTM request frame, the UHR non-AP MLD performs a BSS transition based on the BTM request frame. For pre-EHT STAs and EHT non-AP MLDs, since address 3 of the BTM frame is not an identifier for the corresponding BSS, pre-EHT STAs and EHT non-AP MLDs discard the BTM request frame after receiving the broadcast BTM request frame. To indicate that a UHR non-AP MLD associated with the first non-coexistent AP MLD will perform a BSS transition, the first non-coexistent AP MLD includes its identification information at address 3 of the BTM request frame.

[0030] Referring to the third or fourth aspect, in a possible implementation, the BTM request frame further includes at least one of the following: BSS termination inclusion information, link removal information, and link transition information, the BSS termination inclusion information indicating whether a BSS associated with the first non-coexistent AP MLD is terminated; the link removal information indicating whether a link associated with the first non-coexistent AP MLD is removed; and the link transition information indicating whether a transition is performed between different coexistent AP MLDs that cooperate with the first non-coexistent AP MLD.

[0031] Referring to the third aspect, in a possible implementation, the method is The step is to transmit a second communication frame, the second communication frame including a reduced neighbor report (RNR) element, the reduced neighbor report element including information about at least one cooperating AP of a coexisting AP MLD that interacts with the first non-coexisting AP MLD.

[0032] In this embodiment of the application, the second communication frame may be a beacon frame or a newly defined broadcast frame used to broadcast an RNR. The first non-coexistent AP MLD may include in the second communication frame broadcast by the first non-coexistent AP MLD's associated AP information about at least one associated AP of the first non-coexistent AP MLD's coexistent AP MLD, so that a non-AP MLD associated with the first non-coexistent AP MLD can obtain information about surrounding coexistent AP MLDs without performing a channel scan.

[0033] Referring to the fourth aspect, in possible implementations, the method is The step of receiving a second communication frame, the second communication frame comprising a reduced peripheral report element, the reduced peripheral report element comprising information about at least one cooperating AP of a coexisting AP MLD that cooperates with the first non-coexisting AP MLD.

[0034] In this embodiment of the application, the second communication frame may be a beacon frame or a newly defined broadcast frame used to broadcast an RNR. The first non-coexistent AP MLD may include in the second communication frame broadcast by the first non-coexistent AP MLD's associated AP information about at least one associated AP of the first non-coexistent AP MLD's coexistent AP MLD, so that a non-AP MLD associated with the first non-coexistent AP MLD can obtain information about surrounding coexistent AP MLDs without performing a channel scan.

[0035] According to a fifth aspect, an embodiment of this application provides a multilink communication method. The method is applied to a first communication device. The method is The steps include receiving a probe request frame, the probe request frame comprising identification information of a first coexisting AP MLD and second instruction information, wherein the first coexisting AP MLD cooperates with a third non-coexisting AP MLD, the second instruction information indicates to probe the first coexisting AP MLD, or the second instruction information indicates to probe a coexisting AP MLD that cooperates with a third non-coexisting AP MLD and is in the vicinity of the first coexisting AP MLD, or the second instruction information indicates to probe the first coexisting AP MLD and a coexisting AP MLD that cooperates with a third non-coexisting AP MLD and is in the vicinity of the first coexisting AP MLD, or the second instruction information indicates to probe a coexisting AP MLD that cooperates with a third non-coexisting AP MLD, and transmitting a probe response frame.

[0036] In this embodiment of the application, the first communication device may be an AP, which either cooperates with a first coexisting AP MLD or cooperates with a coexisting AP MLD of a third non-coexisting AP MLD. After receiving a probe request frame, the third non-coexisting AP MLD may respond with a probe response frame by using a cooperating AP. The non-AP MLD includes in the probe request frame transmitted by the STA second directive information indicating the probe range of the probe request frame, so that the non-AP MLD can use the second directive information to probe information about coexisting AP MLDs in the vicinity of the first coexisting AP MLD.

[0037] According to a sixth aspect, an embodiment of this application provides a multilink communication method. The method is applied to a second communication device. The method is The steps include: sending a probe request frame, the probe request frame comprising identification information of a first coexisting AP MLD and second instruction information, wherein the first AP MLD cooperates with a third non-coexisting AP MLD, the second instruction information indicates to probe the first coexisting AP MLD, or the second instruction information indicates to probe a coexisting AP MLD that cooperates with a third non-coexisting AP MLD and is in the vicinity of the first coexisting AP MLD, or the second instruction information indicates to probe the first coexisting AP MLD and a coexisting AP MLD that cooperates with a third non-coexisting AP MLD and is in the vicinity of the first coexisting AP MLD, or the second instruction information indicates to probe a coexisting AP MLD that cooperates with a third non-coexisting AP MLD; and receiving a probe response frame.

[0038] In this embodiment of the application, the second communication device may be an STA, which works in conjunction with a non-AP MLD. The non-AP MLD includes in the probe request frame transmitted by the STA second directive information indicating the probe range of the probe request frame, so that the non-AP MLD can use the second directive information to probe information about coexisting AP MLDs in the vicinity of the first coexisting AP MLD.

[0039] Referring to the fifth or sixth aspect, in a possible implementation, when the second instruction information indicates that a coexisting AP MLD is being probed in conjunction with a third non-coexisting AP MLD, the probe response frame includes the third instruction information, which indicates the number of coexisting AP MLDs that are in conjunction with the third non-coexisting AP MLD.

[0040] In this embodiment of the application, when a third non-coexistent AP MLD includes many coexisting AP MLDs, the signaling overhead is high if the probe response frame includes information about all coexisting AP MLDs that coexist with the third non-coexistent AP MLD. In this case, the probe response frame may include statistical information about the third non-coexistent AP MLD, and it is not necessary to carry information about all coexisting AP MLDs that coexist with the third non-coexistent AP MLD, thereby reducing the signaling overhead. For example, the probe response frame may include the number of coexisting AP MLDs that coexist with the third non-coexistent AP MLD.

[0041] Referring to the fifth or sixth aspect, in a possible implementation, the probe request frame further includes identification information of a third non-coexistent AP MLD.

[0042] Referring to the fifth or sixth aspect, in possible implementations, the probe request frame further includes a service set identifier (SSID).

[0043] According to a seventh aspect, an embodiment of this application provides a multilink communication method. The method is applied to a first communication device. The method is The steps include determining a third communication frame, the third communication frame including a fourth instruction information, the fourth instruction information indicating that a second coexisting AP MLD is removed from a fourth non-coexisting AP MLD, or the fourth instruction information indicating that a second coexisting AP MLD transitions from a fourth non-coexisting AP MLD to a fifth non-coexisting AP MLD, and transmitting the third communication frame.

[0044] In this embodiment of the application, the first communication device may be an AP, the AP may cooperate with a second coexisting AP MLD, and the second coexisting AP MLD may cooperate with a fourth non-coexisting AP MLD. The fifth non-coexisting AP MLD and the fourth non-coexisting AP MLD are two different non-coexisting AP MLDs. For example, the fifth non-coexisting AP MLD may be a non-coexisting AP MLD in the vicinity of the fourth AP MLD. The third communication frame may be a beacon frame, and the third communication frame may be generated by the AP or by the second coexisting AP MLD. When a second coexisting AP MLD needs to be removed from a fourth non-coexisting AP MLD, or when a second coexisting AP MLD needs to transition from a fourth non-coexisting AP MLD to a fifth non-coexisting AP MLD, the second coexisting AP MLD may include the fourth instruction information in the communication frame transmitted by using the coexisting AP, in order to indicate that the second coexisting AP MLD is being removed from the fourth non-coexisting AP MLD, or that the second coexisting AP MLD is transitioning from a fourth non-coexisting AP MLD to a fifth non-coexisting AP MLD, thereby enabling a non-AP MLD associated with the second coexisting AP MLD or the fourth non-coexisting AP MLD to perform a BSS transition or link transition in a timely manner.

[0045] According to the eighth aspect, an embodiment of this application provides a multilink communication method. The method is applied to a second communication device. The method is The steps include receiving a third communication frame, the third communication frame containing a fourth instruction information, the fourth instruction information indicating that a second coexisting AP MLD is removed from a fourth non-coexisting AP MLD, or the fourth instruction information indicating that a second coexisting AP MLD transitions from a fourth non-coexisting AP MLD to a fifth non-coexisting AP MLD, and analyzing the third communication frame.

[0046] In this embodiment of the application, the second communication device may be an STA, which cooperates with a non-AP MLD. The second coexisting AP MLD cooperates with a fourth non-coexisting AP MLD. The fifth non-coexisting AP MLD and the fourth non-coexisting AP MLD are two different non-coexisting AP MLDs. For example, the fifth non-coexisting AP MLD may be a non-coexisting AP MLD in the vicinity of the fourth AP MLD. The third communication frame may be a beacon frame, which may be generated by an AP or by the second coexisting AP MLD. When a second coexisting AP MLD needs to be removed from a fourth non-coexisting AP MLD, or when a second coexisting AP MLD needs to transition from a fourth non-coexisting AP MLD to a fifth non-coexisting AP MLD, the second coexisting AP MLD may include the fourth instruction information in the third communication frame transmitted by using the cooperating AP in order to indicate that the second coexisting AP MLD is to be removed from the fourth non-coexisting AP MLD, or to indicate that the second coexisting AP MLD is to transition from a fourth non-coexisting AP MLD to a fifth non-coexisting AP MLD, thereby enabling a non-AP MLD associated with the second coexisting AP MLD or the fourth non-coexisting AP MLD to perform a BSS transition or link transition in a timely manner.

[0047] Referring to the seventh or eighth aspect, in a possible implementation, the third communication frame further includes fifth instruction information, the fifth instruction information indicating the time to remove the second coexisting AP MLD from the fourth non-coexisting AP MLD, or the fifth instruction information indicating the time to transition the second coexisting AP MLD from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD.

[0048] In this embodiment of the application, the second coexisting AP MLD may include a fifth instruction information in the third communication frame to indicate the time to remove the second coexisting AP MLD from the fourth non-coexisting AP MLD, or to indicate the time to transition the second coexisting AP MLD from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD, thereby enabling a non-AP MLD associated with the second coexisting AP MLD or the fourth non-coexisting AP MLD to perform a BSS transition or link transition in a timely manner.

[0049] In possible implementations, referring to the seventh or eighth aspect, the fifth instruction information includes a second duration, the second duration indicating that the second coexisting AP MLD is removed from the fourth non-coexisting AP MLD after the second duration, or the second duration indicating that the second coexisting AP MLD transitions from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD after the second duration.

[0050] Referring to the seventh or eighth aspect, in a possible implementation, the third communication frame further includes identification information for a second coexisting AP MLD and identification information for a fourth non-coexisting AP MLD.

[0051] According to the ninth aspect, an embodiment of this application provides a multilink communication method. The method is applied to a first communication device. The method is The steps include determining a second communication frame, the second communication frame including a reduced peripheral report element, the reduced peripheral report element including information about at least one cooperating AP of a coexisting AP MLD that cooperates with a non-coexisting AP MLD, and transmitting the second communication frame.

[0052] In this embodiment of the application, the first communication device may be an AP, the AP cooperates with a co-existing AP MLD, and the co-existing AP MLD cooperates with a non-co-existing AP MLD. The co-existing AP MLD includes in a second communication frame broadcast by the co-existing AP information about a co-existing AP MLD that is in the vicinity of the co-existing AP MLD and cooperates with the same non-co-existing AP MLD, so that the non-AP MLD can obtain information about surrounding co-existing AP MLDs without performing a channel scan.

[0053] According to a tenth aspect, an embodiment of this application provides a multilink communication method. The method is applied to a second communication device. The method is The process includes the steps of receiving a second communication frame, the second communication frame including a reduced peripheral report element, the reduced peripheral report element including information about at least one cooperating AP of a coexisting AP MLD that is cooperating with a non-coexisting AP MLD, and analyzing the second communication frame.

[0054] In this embodiment of the application, the second communication device may be an STA, which cooperates with a non-AP MLD. The coexisting AP MLD includes in the second communication frame broadcast by the cooperating AP information about coexisting AP MLDs that are in the vicinity of the coexisting AP MLD and cooperate with the same non-coexisting AP MLD, thereby enabling the non-AP MLD to obtain information about surrounding coexisting AP MLDs without performing a channel scan.

[0055] According to the eleventh aspect, an embodiment of the present application provides a communication device configured to perform a method according to the first aspect or a possible implementation of either the first aspect. The communication device includes a unit for performing a method according to the first aspect or a possible implementation of either the first aspect.

[0056] According to a twelfth aspect, an embodiment of the present application provides a communication device configured to perform a method according to a possible implementation of the second aspect or either of the second aspect. The communication device includes a unit for performing a method according to a possible implementation of the second aspect or either of the second aspect.

[0057] According to the thirteenth aspect, an embodiment of the present application provides a communication device configured to perform a method according to a possible implementation of the third aspect or either of the third aspect. The communication device includes a unit for performing a method according to a possible implementation of the third aspect or either of the third aspect.

[0058] According to a fourteenth aspect, an embodiment of the present application provides a communication device configured to perform a method according to a possible implementation of the fourth aspect or either of the fourth aspects. The communication device includes a unit for performing a method according to a possible implementation of the fourth aspect or either of the fourth aspects.

[0059] According to the fifteenth aspect, an embodiment of the present application provides a communication device configured to perform a method according to a possible implementation of the fifth aspect or either of the fifth aspect. The communication device includes a unit for performing a method according to a possible implementation of the fifth aspect or either of the fifth aspect.

[0060] According to the sixteenth aspect, an embodiment of the present application provides a communication device configured to perform a method according to the sixth aspect or a possible implementation of either aspect. The communication device includes a unit for performing a method according to the sixth aspect or a possible implementation of either aspect.

[0061] According to the 17th aspect, an embodiment of the present application provides a communication device configured to perform a method according to either the 7th aspect or a possible implementation of either the 7th aspect. The communication device includes a unit for performing a method according to either the 7th aspect or a possible implementation of either the 7th aspect.

[0062] According to the 18th aspect, an embodiment of the present application provides a communication device configured to perform a method according to the 8th aspect or a possible implementation of either the 8th aspect. The communication device includes a unit for performing a method according to the 8th aspect or a possible implementation of either the 8th aspect.

[0063] According to the 19th aspect, an embodiment of the present application provides a communication device configured to perform a method according to either the 9th aspect or a possible implementation of either aspect. The communication device includes a unit for performing a method according to either the 9th aspect or a possible implementation of either aspect.

[0064] According to the 20th aspect, an embodiment of the present application provides a communication device configured to perform a method according to either the 10th aspect or a possible implementation of either the 10th aspect. The communication device includes a unit for performing a method according to either the 10th aspect or a possible implementation of either the 10th aspect.

[0065] In the 11th to 20th embodiments, the communication device may include a transceiver unit and a processing unit. For a specific description of the transceiver unit and the processing unit, refer to the embodiments of the device provided below.

[0066] According to the 21st aspect, an embodiment of the present application provides a communication device. The communication device includes a processor configured to perform a method according to one or any possible implementation of any of the first to tenth aspects. Alternatively, the processor is configured to execute a program stored in memory. Once the program is executed, a method according to one or any possible implementation of any of the first to tenth aspects is performed.

[0067] In a possible implementation, the memory is located outside the communication device.

[0068] In a possible implementation, the memory is located inside the communication device.

[0069] In this embodiment of the application, the processor and memory may, alternatively, be integrated into a single device, that is, the processor and memory may, alternatively, be integrated together.

[0070] In possible implementations, the communication device further includes a transceiver, which is configured to receive or transmit signals.

[0071] According to a 22nd aspect, an embodiment of the present application provides a communication device, the communication device comprising a logic circuit and an interface, wherein the logic circuit is coupled to the interface and configured to determine a first communication frame, and the interface is configured to output the first communication frame.

[0072] With respect to the communication device according to the 22nd aspect, it may be understood that the first aspect or the following specific implementation methods should be referenced.

[0073] According to a 23rd aspect, an embodiment of the present application provides a communication device. The communication device includes a logic circuit and an interface, the logic circuit being coupled to the interface, the interface being configured to receive a first communication frame, and the logic circuit being configured to analyze the first communication frame.

[0074] With respect to the communication device according to the 23rd aspect, it may be understood that the second aspect or the following specific implementation methods should be referenced.

[0075] According to a 24th aspect, an embodiment of the present application provides a communication device. The communication device includes a logic circuit and an interface, the logic circuit being coupled to the interface and configured to generate BTM request frames, and the interface being configured to output BTM request frames.

[0076] According to the 25th aspect, an embodiment of the present application provides a communication device. The communication device includes a logic circuit and an interface, the logic circuit being coupled to the interface, the interface being configured to input BTM request frames, and the logic circuit being configured to parse BTM request frames.

[0077] With respect to the communication devices according to the 24th and 25th embodiments, it may be understood that reference may be made to the third embodiment, the fourth embodiment, or the following specific implementation methods.

[0078] According to the 26th aspect, an embodiment of the present application provides a communication device. The communication device includes a logic circuit and an interface, the logic circuit being coupled to the interface, and the interface being configured to input probe request frames and output probe response frames.

[0079] According to the 27th aspect, an embodiment of the present application provides a communication device. The communication device includes a logic circuit and an interface, the logic circuit being coupled to the interface, and the interface being configured to output probe request frames and input probe response frames.

[0080] With respect to the communication devices according to the 26th and 27th embodiments, it may be understood that reference is made to the 5th embodiment, the 6th embodiment, or the following specific implementation methods.

[0081] According to the 28th aspect, an embodiment of the present application provides a communication device. The communication device includes a logic circuit and an interface, the logic circuit being coupled to the interface and configured to determine a third communication frame, and the interface being configured to output the third communication frame.

[0082] According to the 29th aspect, an embodiment of the present application provides a communication device. The communication device includes a logic circuit and an interface, the logic circuit being coupled to the interface, the interface being configured to receive a third communication frame, and the logic circuit being configured to analyze the third communication frame.

[0083] With respect to the communication devices according to the 28th and 29th embodiments, it may be understood that reference is made to the 7th embodiment, the 8th embodiment, or the following specific implementation methods.

[0084] According to a 30th aspect, an embodiment of the present application provides a communication device, the communication device comprising a logic circuit and an interface, the logic circuit being coupled to the interface and configured to determine a second communication frame, and the interface being configured to output the second communication frame.

[0085] According to the 31st aspect, an embodiment of the present application provides a communication device. The communication device includes a logic circuit and an interface, the logic circuit being coupled to the interface, the interface being configured to receive a second communication frame, and the logic circuit being configured to analyze the second communication frame.

[0086] With respect to the communication devices according to the 30th and 31st embodiments, it may be understood that reference may be made to the 9th embodiment, the 10th embodiment, or the following specific implementation methods.

[0087] According to the 32nd aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium is configured to store a computer program, and when the computer program is executed on a computer, a method according to one or any possible implementation of the first to tenth aspects is performed.

[0088] According to the 33rd aspect, an embodiment of the present application provides a computer program product, the computer program product comprising a computer program, which, when the computer program is executed on a computer, is performed by a method according to one or any possible implementation of any of the first to tenth aspects.

[0089] According to the 34th aspect, an embodiment of the present application provides a computer program. When the computer program is executed on a computer, a method according to one or any possible implementation of the first to tenth aspects is performed.

[0090] According to the 35th aspect, an embodiment of the present application provides a communication system. The communication system includes a first communication device and a second communication device. The first communication device is configured to perform a method according to a possible implementation of the first aspect or either of the first aspects, and the second communication device is configured to perform a method according to Alternatively, the first communication device is configured to perform a method according to the seventh aspect or any possible implementation of the seventh aspect, and the second communication device is configured to perform a method according to the eighth aspect or any possible implementation of the eighth aspect. Alternatively, the first communication device is configured to perform a method according to the ninth aspect or any possible implementation of the ninth aspect, and the second communication device is configured to perform a method according to the tenth aspect or any possible implementation of the tenth aspect. [Brief explanation of the drawing]

[0091] The accompanying drawings in the embodiments of this application are described below. [Figure 1] This is a diagram showing the architecture of a communication system according to an embodiment of this application. [Figure 2] This is a diagram illustrating the connection method between a multilink AP and a multilink STA according to an embodiment of this application. [Figure 3a] This invention illustrates a scenario in which an AP MLD communicates with a non-AP MLD. [Figure 3b] This invention illustrates a scenario in which an AP MLD communicates with a non-AP MLD. [Figure 4] This is a diagram showing the architecture of a communication system according to an embodiment of this application. [Figure 5] This is a diagram illustrating the interaction of a multilink communication method according to an embodiment of this application. [Figure 6a] This is a diagram of a reconfigured multilink element according to an embodiment of this application. [Figure 6b] This is a diagram of another reconfigured multilink element according to an embodiment of this application. [Figure 7a] This is a diagram of a first communication frame according to an embodiment of this application. [Figure 7b] This is a diagram of another first communication frame according to an embodiment of this application. [Figure 8] This is a diagram of peripheral report elements according to an embodiment of this application. [Figure 9] This is a diagram of the frame format according to an embodiment of this application. [Figure 10] This is a diagram illustrating the interaction of other multilink communication methods according to embodiments of this application. [Figure 11] This is a diagram of a BTM request frame according to an embodiment of this application. [Figure 12] This is a diagram illustrating the interaction of yet another multilink communication method according to an embodiment of this application. [Figure 13] This is a diagram of the probe-required multilink element according to an embodiment of this application. [Figure 14] This is a diagram illustrating the interaction of yet another multilink communication method according to an embodiment of this application. [Figure 15] This is a diagram illustrating the interaction of yet another multilink communication method according to an embodiment of this application. [Figure 16] This is a diagram showing the structure of a communication device according to an embodiment of this application. [Figure 17] This is a diagram showing the structure of a communication device according to an embodiment of this application. [Figure 18] This is a diagram showing the structure of a communication device according to an embodiment of this application. [Modes for carrying out the invention]

[0092] To facilitate understanding of the technical solutions in this application, the application will be further described below with reference to the attached drawings.

[0093] In this specification, claims, and accompanying drawings of this application, terms such as “first,” “second,” etc. (but not limited to “first” and “second”) are intended merely to distinguish different objects and not to indicate a particular order. Furthermore, terms such as “includes” and “have,” and any other variation thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device comprising a set of steps or units is not limited to the listed steps or units, but instead may optionally include further steps or units not listed, or may optionally include other steps or units specific to those processes, methods, products, or devices.

[0094] As used in this specification, “embodiments” means that certain features, structures, or characteristics described in conjunction with the embodiments may be included in at least one embodiment of this application. The terms used in various parts of this specification do not necessarily mean the same embodiment, nor are they exclusive, independent, or optional embodiments. Those skilled in the art will understand, both explicitly and implicitly, that the embodiments described in this specification may be combined with other embodiments.

[0095] In this application, “at least one” means one or more, “multiple” means two or more, “at least two” means two, three or more, and “and / or” is used to describe an association between related objects and indicates that three relationships may exist. For example, “A and / or B” may indicate the following three cases: that only A exists, that only B exists, and that both A and B exist, where A and B may be singular or plural. Furthermore, “or” indicates that two relationships may exist, e.g., that only A exists and that only B exists. When A and B are not mutually exclusive, this may indicate that three relationships exist, e.g., that only A exists, that only B exists, and that both A and B exist. The letter “ / ” generally indicates an “or” relationship between related objects. Furthermore, “at least one of the following items” or similar expressions means any combination of these items. For example, at least one of a, b, or c may represent a, b, c, "a and b", "a and c", "b and c", or "a, b and c".

[0096] The technical solutions provided in embodiments of this application may be applied to WLAN systems, such as Wi-Fi. For example, the methods provided in embodiments of this application are applicable to wireless local area network systems for IEEE 802.11 series protocols, such as 802.11a / b / g protocols, 802.11n protocols, 802.11ac protocols, 802.11ax protocols, 802.11be protocols, or Wi-Fi 7 or EHT protocols, as well as next-generation protocols such as Wi-Fi 8, UHR, and Wi-Fi AI. The technical solutions provided in embodiments of this application may be further applied to wireless personal area networks (WPANs) based on UWB technology, sensing systems, etc. For example, the methods provided in embodiments of this application are further applicable to IEEE 802.15.4 series protocols such as 802.15a protocols, 802.15.4z protocols, 802.15.4ab protocols, and next-generation UWB WPAN protocols. Examples are not listed herein. The technical solutions provided in embodiments of this application may be further applied to the following communication systems, for example, Internet of Things (IoT) systems, Vehicle to X (V2X) systems and Narrow Band Internet of Things (NB-IoT) systems, or to devices in the Internet of Things (IoT), Internet of Things nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls or smart water / electricity meters in smart homes, sensors in smart cities, or to long-term evolution (LTE) systems, 5th-generation (5G) communication systems, new communication systems emerging in future communication developments, etc.

[0097] WLAN systems can provide high-rate and low-latency transmission. With the continuous evolution of WLAN application scenarios, WLAN systems will be used in a wider range of scenarios and industries, such as the Internet of Things industry, the Internet of Vehicles industry, the banking industry, corporate offices, stadiums, exhibition halls, concert halls, hotel rooms, dormitories, hospital wards, classrooms, supermarkets, squares, streets, production plants, and warehouses. Clearly, devices that support WLAN communication or sensing (e.g., access points or stations) may also be sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, or smart air sensing nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, stereos, refrigerators, or washing machines), nodes in the Internet of Things, entertainment terminals (e.g., wearable devices such as augmented reality (AR) or virtual reality (VR) devices), smart devices in smart offices (e.g., printers, projectors, speakers, or stereos), Internet of Vehicles devices in the Internet of Vehicles, infrastructure in everyday life scenarios (e.g., vending machines, self-service navigation consoles in supermarkets, self-service cashiers, or self-service ordering machines), devices in large-scale sports or music venues, etc. For example, access points and stations may also be devices used in the Internet of Vehicles, Internet of Things nodes in the Internet of Things, sensors, etc., smart cameras in smart homes, smart remote controls, smart water / electricity meters, or sensors in smart cities.

[0098] The embodiments of this application primarily use WLANs as an example, and in particular use networks applicable to the IEEE 802.11 series standards, such as systems supporting Wi-Fi 7, also known as extremely high throughput (EHT), or systems supporting Wi-Fi 8, also known as ultra high reliability (UHR) or ultra high reliability and throughput (UHRT). However, those skilled in the art will readily understand that various aspects of the embodiments of this application may be extended to other networks using various standards or protocols, such as Bluetooth, high performance radio LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard and primarily used in Europe), wide area networks (WANs), or other known or future-developed networks.

[0099] A multi-link device (MLD) is a device having multiple stations (APs or non-AP STAs, etc.) operating simultaneously on different frequency bands or channels. When the channel spacing between two stations in a single multi-link device is sufficiently large, the two stations may operate independently without interfering with each other. If one of any two stations can transmit and the other can simultaneously receive, this is said to support simultaneous transmitting and receiving (STR) capability between the two stations; otherwise, this is said to have non-simultaneous transmitting and receiving (NSTR) capability between the two stations. A multi-link device includes multiple coordinating stations. Coordinating stations may be physical stations or logical stations. Each station may operate on one link, one frequency band, one channel, etc. Coordinating stations may be APs or non-AP STAs. For the sake of clarity, in embodiments of this application, a multilink device whose connecting station is an AP may be called a multilink AP, a multilink AP device, or an AP multi-link device (AP MLD), a multilink device whose connecting station is a non-AP STA may be called a multilink STA, a multilink STA device, or an STA multi-link device (STA multi-link device), or a multilink device whose connecting station is a non-AP STA may be called a multilink non-AP, a multilink non-AP device, or a non-AP multi-link device (non-AP MLD). A multilink device (which may also be called a non-AP MLD or AP MLD herein) is a communication device having wireless communication capabilities.The communication device may be the entire device, or it may be a chip, processing system, etc., installed in the entire device. The device on which the chip or processing system is installed may implement the methods and functions of the embodiments of this application under the control of the chip or processing system.

[0100] A multilink device (MLD) may conform to the 802.11 series protocols to enable wireless communication, for example, it may conform to Extremely High Throughput (EHT), or it may conform to and be based on 802.11be to enable communication with other devices, or it may be compatible with and support 802.11be. Obviously, the other devices may or may not be multilink devices.

[0101] Figure 1 is a diagram of the architecture of a communication system according to an embodiment of this application. As shown in Figure 1, the AP MLD includes AP1, AP2, ... and APn, and the non-AP MLD includes STA1, STA2, ... and STAn, where n is a positive integer. The AP MLD and non-AP MLD may perform parallel communication through links 1, 2, ... and n. STA1 in the non-AP MLD establishes an association relationship with AP1 in the AP MLD. STA2 in the non-AP MLD establishes an association relationship with AP2 in the AP MLD. STAn in the non-AP MLD establishes an association relationship with APn in the AP MLD. Thus, one or more STAs in the non-AP MLD and one or more APs in the AP MLD may communicate after establishing an association relationship. The frequency bands in which the multilink devices (including AP MLDs and non-AP MLDs) operate may include, but are not limited to, sub 1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and high frequency 60 GHz. For example, the methods provided in embodiments of this application are applicable to, but are not limited to, single-user uplink / downlink transmission, multi-user uplink / downlink transmission, vehicle-to-everything (V2X, where X may represent everything), and device-to-device (D2D). For example, V2X may include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), or vehicle-to-network (V2N) communications.

[0102] Figure 2 is a diagram illustrating the connection method between a multilink AP and a multilink STA according to an embodiment of this application. The 802.11 standard focuses on the 802.11 physical layer (PHY) and medium access control (MAC) layers in a multilink device. Therefore, Figure 2 shows only examples of the PHY and MAC layers.

[0103] As shown in Figure 2, a multilink device (e.g., multilink AP and multilink STA) may include a physical layer (PHY) (PHY#1, PHY#2, and PHY#n shown in Figure 2) and a medium access control (MAC) layer. The physical layer may be used to process physical layer signals, and the MAC layer may be used to process MAC layer signals. The MAC layer may be further divided into one high-MAC layer (high-MAC shown in Figure 2) and multiple low-MAC layers (low-MAC#1, low-MAC#2 to low-MAC#n shown in Figure 2). As shown in Figure 2, multiple APs included in a multilink AP are independent of each other in the low-MAC and PHY layers and share the high-MAC layer, and multiple STAs included in a multilink STA are independent of each other in the low-MAC and PHY layers and share the high-MAC layer. The high-MAC layer is connected separately to multiple low-MAC layers, i.e., the high-MAC layer is shared by multiple links. For example, the upper MAC layer primarily completes operations such as assigning sequence numbers (SN) and packet numbers (PN) to MAC service data units (MSDUs), encryption, and decryption. For example, the lower MAC layer primarily completes operations such as assembling MAC protocol data units (MPDUs) for each link, channel access, packet transmission, and acknowledgment.

[0104] In Figure 2, PHY#1, lower MAC#1, and upper MAC within a multilink AP may be considered as AP#1, PHY#2, lower MAC#2, and upper MAC may be considered as AP#2, ..., PHY#n, lower MAC#n, and upper MAC may be considered as AP#n. In other words, a multilink AP can be understood as containing n AP entities. A similar situation exists in a multilink STA. Specifically, the upper MAC within a multilink STA is also shared by multiple links, and PHY#1, lower MAC#1, and upper MAC can be considered as STA#1, PHY#2, lower MAC#2, and upper MAC can be considered as STA#2, ..., PHY#n, lower MAC#n, and upper MAC can be considered as STA#n. In other words, a multilink STA can be understood as containing n STA entities. As shown in Figure 2, PHY#1 of AP#1 in a multilink AP and PHY#1 of STA#1 in a multilink STA operate on the same channel, enabling communication between AP#1 in the multilink AP and STA#1 in the multilink STA via a link (for example, link #1 shown in Figure 2). PHY#2 of AP#2 in a multilink AP and PHY#2 of STA#2 in a multilink STA operate on other identical channels, enabling communication between AP#2 in the multilink AP and STA#2 in the multilink STA via a link (link #2 shown in Figure 2). PHY#n of AP#n in a multilink AP and PHY#n of STA#n in a multilink STA operate on other identical channels, enabling communication between AP#n in the multilink AP and STA#n in the multilink STA via a link (link #n shown in Figure 2).

[0105] For example, both the upper MAC layer and the lower MAC layer may be implemented by a single processor within the chip system of the multilink device, or by different software processing modules within a single chip system. Examples are not enumerated in the embodiments of this application. Figure 2 may be understood as the multilink device being divided into functional modules, and the modules shown in Figure 2 may be implemented in hardware form, or in the form of software functional modules, etc. The PHY layer and MAC layer shown in Figure 2 may be understood as a logical functional division. Other division methods may exist in actual implementations. In Figure 2, n may be equal to 1, or n may be an integer greater than 1, etc.

[0106] The upper MAC layer may also be called the MLD upper MAC sublayer, and the lower MAC layer may also be called the MLD lower MAC sublayer. In addition to the respective MAC addresses on each link, each multilink device has one additional MLD MAC address. The architecture shown in Figure 2 is used as an example. The upper MAC layer may be uniquely identified by using the corresponding MLD MAC address. The lower MAC layer may be uniquely identified by using the MAC address of the corresponding link. For example, lower MAC#1 and lower MAC#2 may correspond to the MAC addresses of their respective links.

[0107] For example, the multilink device in the embodiments of this application may be a single-antenna device or a multi-antenna device, for example, a device having more than two antennas. The number of antennas included in the multilink device is not limited in the embodiments of this application.

[0108] The frequency bands in which the multilink device operates may include, but are not limited to, sub 1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and high frequency 60 GHz. Figures 3a and 3b are two diagrams illustrating communication between a multilink device and other devices in a wireless local area network over multiple links.

[0109] Figure 3a shows a scenario in which AP MLD101 communicates with non-AP MLD102. AP MLD101 includes cooperative AP101-1 and AP101-2, and non-AP MLD102 includes cooperative STA102-1 and STA102-2. AP MLD101 and non-AP MLD102 perform parallel communication through Link 1 and Link 2.

[0110] For example, Figure 3b shows a scenario in which AP MLD101 communicates with non-AP MLD102, non-AP MLD103, and STA104. AP MLD101 includes linked AP101-1 to linked AP101-3, non-AP MLD102 includes three linked STAs, namely STA102-1, STA102-2, and STA102-3, non-AP MLD103 includes two linked STAs, namely STA103-1 and STA103-2, and STA104 is a single-link device, including STA104-1. AP MLD101 may communicate separately with non-AP MLD102 via links 1, 2, and 3, with non-AP MLD103 via links 2 and 3, and with STA104 via link 1. In one example, STA104 operates on the 2.4GHz frequency band, in non-AP MLD103, STA103-1 operates on the 5GHz frequency band, STA103-2 operates on the 6GHz frequency band, in non-AP MLD102, STA102-1 operates on the 2.4GHz frequency band, STA102-2 operates on the 5GHz frequency band, and STA102-3 operates on the 6GHz frequency band. AP101-1, operating on the 2.4GHz frequency band within AP MLD101, may communicate uplink or downlink data with STA104 and STA102-1 in non-AP MLD102 via link 1. AP101-2, operating in the 5GHz frequency band within AP MLD101, may communicate uplink or downlink data with STA103-1, operating in the 5GHz frequency band within non-AP MLD102, via link 2, and may also communicate uplink or downlink data with STA102-2, operating in the 5GHz frequency band within non-AP MLD103, via link 2. AP101-3, operating in the 6GHz frequency band within AP MLD101, may communicate uplink or downlink data with STA102-3, operating in the 6GHz frequency band within non-AP MLD102, via link 3, and may also communicate uplink or downlink data with STA103-2, located within non-AP MLD, via link 3.

[0111] Figure 3a shows that the AP MLD supports only two frequency bands. Figure 3b is used for illustrative purposes to show an example where the AP MLD 101 supports only three frequency bands (2.4 GHz, 5 GHz, and 6 GHz), each frequency band corresponding to one link, and the AP MLD 101 may operate on one or more of links 1, 2, or 3. On the AP side or STA side, a link can also be understood as a station operating on the link. In actual applications, the AP MLD and non-AP MLD may further support more or fewer frequency bands, i.e., the AP MLD and non-AP MLD may operate on more or fewer links. This is not limited to the embodiments of this application. Figures 3a and 3b are for illustrative purposes only and do not constitute any limitation to the scope of protection of the embodiments of this application.

[0112] Figure 4 is a diagram of the architecture of a communication system according to an embodiment of this application. The architecture shown in Figure 4 includes a UHR system, an EHT system, and a pre-EHT system (e.g., called pre-EHT). It can be understood that the lines of different thicknesses, dashed lines, etc., shown in Figure 4 are used to represent different transmission paths. Generally, the interface between a distributed system and the MAC layer may be called a distributed system service access point (DS SAP), a distributed system access function (DSAF), or a MAC service access point (SAP) (abbreviated as MAC SAP, e.g., MAC SAP1 to MAC SAP7, shown by the seven black dots in Figure 4). A MAC address can uniquely identify a MAC SAP. It can be understood that the representation of MAC SAPs shown in Figure 4 (e.g., representation using black dots) and the location of the representation (e.g., the location of the black dots) are merely examples and should not be interpreted as limitations to the embodiments of this application. The interface between the upper MAC layer (e.g., the radio resource control (RRC) layer) and the lower MAC layer is shown by a thick solid line in Figure 4.

[0113] A non-collocated AP MLD may also be called a logical AP MLD. A collocated AP MLD may also be called a physical AP MLD. For ease of explanation, a non-collocated AP MLD and a collocated AP MLD are used below as examples to illustrate the methods provided in embodiments of this application.

[0114] In one example, since data from a pre-EHT STA is associated with a linked AP, all data related to the pre-EHT STA must be received and transmitted using the MAC SAP of the corresponding linked AP (e.g., MAC SAP1, MAC SAP3, MAC SAP4, and MAC SAP6 shown in Figure 4). As shown in Figure 4, for data from or transmitted to a pre-EHT STA, the AP may process the data using the non-multilink device (non-MLD) upper MAC layer (e.g., MAC SAP1, MAC SAP3, MAC SAP4, and MAC SAP6 shown in Figure 4).

[0115] In another example, since data from an EHT non-AP MLD is associated with a coexisting AP MLD, all data related to the EHT non-AP MLD must be received and transmitted using the MAC SAP of the corresponding coexisting AP MLD (e.g., MAC SAP2 and MAC SAP5 shown in Figure 4). As shown in Figure 4, for data from or transmitted to an EHT non-AP MLD, the coexisting AP MLD may perform data processing using the AP MLD upper MAC sublayer (e.g., MAC SAP2 and MAC SAP5 shown in Figure 4), and then perform data processing using the AP MLD lower MAC sublayer. Each AP MLD lower MAC sublayer may correspond to one PHY. For example, for coexisting AP MLD A, the AP MLD lower MAC sublayers may sequentially correspond to PHY1 (which may also be called Link 1 or the PHY corresponding to Link 1), ... and PHY N (which may also be called Link N or the PHY corresponding to Link N), and for coexisting AP MLD B, the AP MLD lower MAC sublayers may sequentially correspond to PHY1 (which may also be called Link 1 or the PHY corresponding to Link 1), ... and PHY M (which may also be called Link M or the PHY corresponding to Link M), where A and B are used to distinguish between different coexisting AP MLDs, and M and N are both positive integers.

[0116] In another example, since data from a UHR non-AP MLD is associated with a non-coexistent AP MLD, all data related to the UHR non-AP MLD must be received and transmitted using the MAC SAP of the corresponding non-coexistent AP MLD (for example, MAC SAP7 shown in Figure 4). As shown in Figure 4, for data from or transmitted to a UHR non-AP MLD, the non-coexistent AP MLD processes the data using the AP MLD upper MAC sublayer and then distributes the data to the relevant modules of TID and link mapping or link merging through the interface between the upper and lower MAC sublayers.

[0117] For example, the functional partitioning of the upper and lower MAC sublayers of a non-coexistent AP MLD may depend on whether or not traffic identifiers (TIDs) are permitted to be mapped to links of different coexistent AP MLDs. For example, when it is permitted for traffic identifiers (TIDs) to be mapped to links of different coexistent AP MLDs, the block acknowledgment (block ACK, BA) session for the TID must be maintained in the upper MAC sublayer of the non-coexistent AP MLD, and the session may be refreshed based on BA information fed back by the corresponding coexistent AP MLD.

[0118] It can be understood that the AP MLD upper MAC sublayer functional block may be located in a coexisting AP MLD, or in an access point controller, or in a portal (also called a gateway), etc. The method for configuring the upper MAC sublayer of a non-coexisting AP MLD is not limited to the embodiments of this application. The AP MLD upper MAC sublayer and the AP MLD lower MAC sublayer may communicate with each other using network cables or other technologies. For example, multiple coexisting AP MLDs interacting with a non-coexisting AP MLD do not have to be located in the same device.

[0119] For example, a non-coexistent AP MLD can be understood as an AP MLD containing multiple coexistent AP MLDs. Alternatively, a non-coexistent AP MLD can be understood as a device configured to centrally or uniformly manage (or control) multiple coexistent AP MLDs.

[0120] The relationship between the MAC address of an MLD and the MAC address of the link that interacts with the MLD, as shown in Figure 2, is used as an example. In this case, a similar relationship exists between non-coexistent AP MLDs and coexistent AP MLDs. For example, each non-coexistent AP MLD has a non-coexistent MLD MAC address (e.g., the upper MAC sublayer of the non-coexistent AP MLD shown in Figure 4), the MLD MAC address of the coexistent AP MLD that interacts with the non-coexistent AP MLD, and the MAC address of the link that interacts with the coexistent AP MLD. It can be understood that the non-coexistent MLD MAC address may be understood as the MAC address of the upper MAC sublayer of the AP MLD shown in Figure 4 (for example, the MAC address of the upper MAC sublayer of the AP MLD may identify MAC SAP7). Furthermore, the n coexistent AP MLDs that interact with a non-coexistent AP MLD may also be referred to as the non-coexistent AP MLD containing n coexistent AP MLDs, or the non-coexistent AP MLD corresponding to n coexistent AP MLDs, etc.

[0121] It can be understood that the relationship between non-coexisting AP MLDs and coexisting AP MLDs may be described differently as standards evolve. Therefore, the description of the relationship between non-coexisting AP MLDs and coexisting AP MLDs is not limited to the embodiments of this application.

[0122] In embodiments of this application, the first communication device may be an AP, and the second communication device may be an STA. Alternatively, in possible implementations, the first communication device may be a non-coexisting AP MLD, and the second communication device may be a non-AP MLD associated with the non-coexisting AP MLD.

[0123] In the communication system shown in Figure 4, the AP MLD may include both coexisting and non-coexisting AP MLDs. The EHT non-AP MLD may be associated with the coexisting AP MLD, and the UHR non-AP MLD may be associated with the non-coexisting AP MLD. However, in some scenarios (software upgrades and maintenance, device failures, etc.), the coexisting or non-coexisting AP MLD may need to be terminated. Therefore, how to terminate the coexisting or non-coexisting AP MLD is an urgent issue that needs to be resolved.

[0124] With this in mind, embodiments of this application provide a multilink communication method for terminating a coexisting AP MLD or a non-coexisting AP MLD, such that a non-AP MLD associated with a coexisting AP MLD or a non-coexisting AP MLD can perform a BSS transition in a timely manner.

[0125] Figure 5 is a diagram illustrating the interaction of a multilink communication method according to an embodiment of this application. As shown in Figure 5, refer to the above description for explanations of non-coexistent AP MLDs, coexistent AP MLDs, non-AP MLDs, etc., in the method. Details of the method shown in Figure 5 will not be described. Relay nodes are not included in the method described below, but it can be understood that when the receiver and the transmitter communicate with each other, the forwarding operation may be performed by using relay nodes. As shown in Figure 5, the method includes the following steps.

[0126] 501: The AP determines a first communication frame, which includes identification information and first instruction information for the first AP MLD, the first instruction information indicating the end time of the first AP MLD.

[0127] For example, AP may be an AP that cooperates with a coexisting AP MLD that cooperates with a non-coexisting AP MLD, or AP may be an AP that cooperates with a coexisting AP MLD, and AP may also be called an affiliated AP. The first AP MLD may be a non-coexisting AP MLD or a coexisting AP MLD. When the first AP MLD is a coexisting AP MLD, the first communication frame further includes identification information of the non-coexisting AP MLD that the coexisting AP MLD cooperates with.

[0128] For example, the identification information of the first AP MLD may include the MAC address of the first AP MLD or the ID of the first AP MLD.

[0129] Optionally, the first communication frame further includes sixth instruction information, which indicates a candidate peripheral node to perform the BSS transition. For example, the sixth instruction information may include information about peripheral AP MLDs of the first AP MLD or peripheral APs of the first AP MLD's allied APs. When the first AP MLD needs to terminate, the first communication frame may be transmitted using the first AP MLD's allied APs to indicate the termination time of the first AP MLD and the candidate peripheral node to perform the BSS transition, thereby causing a non-AP MLD associated with the first AP MLD to perform the BSS transition. It should be noted that the first communication frames transmitted by all allied APs of the first AP MLD may carry sixth instruction information that is not exactly the same.

[0130] In possible implementations, the first instruction information includes a first duration, which indicates that the first AP MLD will terminate after the first duration. For example, the unit of the first duration is a time unit (TU), i.e., the first instruction information indicates the number of time units after which the first AP MLD will terminate.

[0131] Optionally, before transmitting the first communication frame, the AP may acquire further communication frames. The method by which the AP acquires the first communication frame may be by the AP generating the first communication frame, or by the AP acquiring the first communication frame from a coexisting AP MLD or a non-coexisting AP MLD. For example, if the first AP MLD is a non-coexisting AP MLD and the non-coexisting AP MLD needs to terminate, the non-coexisting AP MLD may send a command to a coexisting AP MLD that is cooperating with the non-coexisting AP MLD, resulting in the coexisting AP MLD cooperating with the non-coexisting AP MLD generating the first communication frame, or the non-coexisting AP MLD may use the coexisting AP MLD that is cooperating with the non-coexisting AP MLD to send a command to a cooperating AP that is cooperating with the coexisting AP MLD, resulting in the cooperating AP generating the first communication frame.

[0132] Based on the system architecture shown in Figure 4, it can be understood that different coexisting AP MLDs may have different software / hardware / software-hardware combination modules (e.g., MAC layer and PHY layer), and different APs within the same coexisting AP MLD may also have different software / hardware / software-hardware combination modules (e.g., different MAC layer and PHY layer). In this case, the first communication frame can be understood to be generated by the module. Alternatively, in a specific implementation, different APs within a coexisting AP MLD may share the same processor. In this case, the first communication frame can be understood to be generated by the processor. Alternatively, when the upper MAC sublayer of a non-coexisting AP MLD is located independently within the controller, the controller may generate the first communication frame. Furthermore, after generating the first communication frame, the controller may transmit the first communication frame to the AP.

[0133] 502: The AP transmits the first communication frame, and in response, the STA receives the first communication frame.

[0134] 503:STA analyzes the first communication frame.

[0135] For example, STA interacts with non-AP MLD. The non-AP MLD may decide whether or not to associate with the first AP MLD based on the identification information of the first AP MLD. When the non-AP MLD is associated with the first AP MLD, it performs a BSS transition. For example, the non-AP MLD may transition to a candidate peripheral node indicated by the sixth instruction information.

[0136] In this embodiment of the application, in order to achieve termination of a coexisting AP MLD or a non-coexisting AP MLD, the first instruction information may indicate that the coexisting AP MLD or the non-coexisting AP MLD should be terminated, thereby enabling a non-AP MLD associated with the coexisting AP MLD or the non-coexisting AP MLD to perform a BSS transition in a timely manner.

[0137] For example, with respect to the first communication frame, this embodiment of the application further provides several implementations.

[0138] Implementation method 1: The first communication frame may be a beacon frame, and the identification information of the first AP MLD, the first instruction information, and the sixth instruction information are included in the reconfiguration multi-link element of the first communication frame.

[0139] For example, when a non-coexistent AP MLD determines that it needs to terminate, the non-coexistent AP MLD may transmit a beacon frame on the link where each co-operating AP of each co-operating AP MLD is located to indicate that the non-AP MLD associated with the non-coexistent AP MLD will perform a BSS transition, and the beacon frame carries a reconfigured multilink element. Alternatively, when a co-operating AP MLD needs to terminate, the co-operating AP MLD may include a reconfigured multilink element in the beacon frame transmitted on the link where each co-operating AP of the co-operating AP MLD is located to indicate that the non-AP MLD associated with the co-operating AP MLD will perform a BSS transition.

[0140] For example, Figures 6a and 6b show examples of reconfigured multilink elements according to embodiments of this application, respectively. As shown in Figure 6a, when the first AP MLD is a non-collocated AP MLD, the reconfigured multilink element may include a non-collocated AP MLD MAC address field, a non-collocated AP MLD termination timer field, and one or more optional peripheral report sub-elements. Identification information for the non-collocated AP MLD is carried in the non-collocated AP MLD MAC address field. First instruction information is carried in the non-collocated AP MLD termination timer field. Sixth instruction information is carried in the peripheral report sub-elements.

[0141] Optionally, the reconfigured multilink element may further include a coexisting AP MLD MAC address field, which carries identification information of the current coexisting AP MLD interacting with the non-coexisting AP MLD.

[0142] For example, a reconstructed multilink element may further include a presence bitmap, which indicates whether the reconstructed multilink element includes the following fields: a coexisting AP MLD MAC address field, a non-coexisting AP MLD MAC address field, and a non-coexisting AP MLD termination timer field. For example, the presence bitmap may include a non-collocated AP MLD MAC address present field and a non-collocated AP MLD termination timer present field, the non-coexisting AP MLD MAC address present field indicating whether the reconstructed multilink element includes a non-coexisting AP MLD MAC address field, and the non-coexisting AP MLD termination timer present field indicating whether the reconstructed multilink element includes a non-coexisting AP MLD termination timer field.

[0143] As shown in Figure 6b, when the first AP MLD is a coexisting AP MLD, the reconfigured multilink element further includes identification information for the non-coexisting AP MLD with which the coexisting AP MLD interacts. In other words, the reconfigured multilink element may include a coexisting AP MLD MAC address field, a non-coexisting AP MLD MAC address field, and a collocated AP MLD termination timer field. The identification information for the coexisting AP MLD is carried in the coexisting AP MLD MAC address field. The identification information for the non-coexisting AP MLD with which the coexisting AP MLD interacts is carried in the non-coexisting AP MLD MAC address field. The first instruction information is carried in the coexisting AP MLD termination timer. The sixth instruction information is carried in the peripheral report sub-element.

[0144] For example, a reconfigured multilink element may further include an existence bitmap, which indicates whether the reconfigured multilink element includes the following fields: a co-located AP MLD MAC address field, a non-co-located AP MLD MAC address field, a non-co-located AP MLD termination timer field, and a co-located AP MLD termination timer field. For example, the existence bitmap may include a collocated AP MLD termination timer present field, and the co-located AP MLD termination timer field may indicate whether the reconfigured multilink device includes a co-located AP MLD termination timer field.

[0145] In some implementations, it may be understood that the reconfigured multilink element may include a non-coexisting AP MLD termination timer field and a coexisting AP MLD termination timer field. The reconfigured multilink element may use the non-coexisting AP MLD termination timer field to indicate that the non-coexisting AP MLD is terminating, and the coexisting AP MLD termination timer field to indicate that the coexisting AP MLD is terminating.

[0146] For example, the reconfigured multilink elements listed above may further include fields specifically included in the reconfigured multilink elements defined by the protocol. For example, as shown in Figure 6a or Figure 6b, the reconfigured multilink element may include an element ID (e.g., element ID=255), length, element ID extension (e.g., element ID extension=107), a multilink control field, a common info field, and a link info field. For example, the multilink control field may include a type (e.g., type=2), a reserved field, and an existence bitmap, the existence bitmap indicating whether the relevant information in the common info field exists or not. For example, the common information field may include a common info length field and at least one of the following: MLD MAC address field (MAC address of the MLD that transmits the reconfigured multilink element), coexisting AP MLD MAC address field, coexisting AP MLD termination timer field, non-coexisting AP MLD MAC address field, and non-coexisting AP MLD termination timer field. Optionally, the reconfigured multilink element may further include one or more per-STA profile fields, the per-STA profile field may include a sub-element ID (e.g., sub-element ID=0), length, STA control field, and STA info field.

[0147] For example, the STA control field includes one or more of the following: link ID field, complete profile field, STA MAC address present field, AP removal timer present field, operation update type field, operation parameters present field, and reserved field. The link ID field indicates the identifier of the corresponding link. The complete profile field indicates whether a complete profile is requested. The STA MAC address present field indicates whether the STA information field includes the MAC address of the corresponding STA. The AP removal timer present field indicates whether the STA information field includes the AP removal timer field. The operation update type field (4 bits) indicates the multilink operation update type, where 1 indicates an operation parameter update and values ​​from 1 to 15 are reserved. The operation parameters present field indicates whether the STA information field includes the operation parameters field.

[0148] For example, the STA information field includes one or more of the following: STA info length field, STA MAC address field, AP removal timer field, and operation parameter field. The STA info length field indicates the length of the STA information field. The STA MAC address field indicates the MAC address of the corresponding STA. The AP removal timer field indicates the number of target beacon transmission times (TBTT) after which the corresponding AP will be removed. The operation parameter field includes a presence indication field and an operation parameter info field. The presence indication field indicates whether the operation parameter field contains the corresponding field. For example, the presence indicator field includes a Maximum MPDU Length Present field (indicating whether the operation parameter field includes the Maximum MPDU Length field) and a Maximum A-MSDU Length Present field (indicating whether the operation parameter field includes the Maximum A-MSDU Length field). The operation parameter information field includes a Maximum MPDU Length field (indicating the maximum MPDU length), an A-MSDU Length field (indicating the maximum A-MSDU length), and a padding field (used to carry padding bit 0).

[0149] It should be understood that the order of fields shown in Figure 6a or Figure 6b is not limited to the embodiments of this application. It should be understood that the field, sub-element, or element division scheme in this embodiment of this application is merely an example. Other division schemes may exist for different information within a communication frame in specific implementations, and this is not limited to the embodiments of this application.

[0150] Implementation Method 2: The first communication frame is a functional frame defined to indicate that the first AP MLD is terminating. For example, the first communication frame may be an AP MLD termination announcement frame.

[0151] In this implementation, the first communication frame does not need to include identification information of the first AP MLD. For example, when the first AP MLD is a non-collocated AP MLD, the first communication frame may be a non-collocated AP MLD termination announcement frame indicating that the non-collocated AP MLD is terminating. The first communication frame is transmitted by the cooperating AP of the co-located AP MLD that is cooperating with the non-collocated AP MLD, and the non-AP MLD that receives the first communication frame may determine which co-located AP MLD the cooperating AP is cooperating with and which non-collocated AP MLD the co-located AP MLD is cooperating with in order to determine that the non-collocated AP MLD is terminating, by using the cooperating AP corresponding to the transmitter address of the first communication frame. For example, if the non-AP MLD that receives the first communication frame is associated with a non-collocated AP MLD (e.g., a UHR non-AP MLD), the non-AP MLD performs a BSS transition.

[0152] For example, when the first AP MLD is a collocated AP MLD, the first communication frame may also be a collocated AP MLD termination announcement frame indicating that the collocated AP MLD is terminating. The first communication frame is transmitted by the cooperating AP that is cooperating with the collocated AP MLD, and the non-AP MLD that receives the first communication frame may determine which collocated AP MLD the cooperating AP is cooperating with by using the cooperating AP corresponding to the transmitter address of the first communication frame in order to determine that the collocated AP MLD is terminating. For example, if the non-AP MLD that receives the first communication frame is associated with a collocated AP MLD (e.g., an EHT non-AP MLD), the non-AP MLD performs a BSS transition.

[0153] For example, the first communication frame may further include, or separately, instruction information (also called a reason code) indicating the reason for the termination of the first AP MLD, and at least one of one or more peripheral report elements. The one or more peripheral report elements include information about peripheral access point APs of the APs that interact with the first AP MLD. In other words, the first communication frame may include identification information for the first AP MLD, the first instruction information, instruction information indicating the reason for the termination of the first AP MLD, and at least one of one or more peripheral report elements.

[0154] For example, as shown in Figure 7a, when the first AP MLD is a non-coexistent AP MLD, the first communication frame may include one or more of the following: category, action, reason code, non-coexistent AP MLD termination containment field, termination time, one or more peripheral report elements, and non-coexistent AP MLD MAC address. The reason code may indicate the reason for the termination of the non-coexistent AP MLD. For example, the reason code may be set to a newly defined reason code to indicate non-coexistent AP MLD termination or non-coexistent AP MLD maintenance. For example, when the reason code is set to a first value, the reason code indicates non-coexistent AP MLD termination. When the reason code is set to a second value, the reason code indicates non-coexistent AP MLD maintenance. The non-coexistent AP MLD termination containment indicates whether the non-coexistent AP MLD is terminating or not. The termination time indicates the termination time of the non-coexistent AP MLD. One or more peripheral report elements include information about peripheral APs of co-existing AP MLDs that work with non-co-existing AP MLDs, in order to recommend optional peripherals for BSS transitions to non-AP MLDs associated with non-co-existing AP MLDs.

[0155] For example, as shown in Figure 8, the peripheral report element includes the following elements: element ID, length, BSS identifier (BSSID), BSSID information (info), operating class, channel number, physical layer type (PHY type), and optional sub-elements, such as the basic multi-link sub-element.

[0156] The BSSID field indicates the BSSID corresponding to the reported surrounding AP. The BSSID information field indicates related information for the reported BSSID. The operation class field and channel number field indicate the channel to which the reported BSSID belongs. The PHY type field indicates the physical layer type of the AP corresponding to the reported BSSID.

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

[0158] For example, as shown in Figure 7b, when the first AP MLD is a coexisting AP MLD, the first communication frame may include one or more of the following: category, action, reason code, coexisting AP MLD termination containment field, termination time, one or more neighbor report elements, and coexisting AP MLD MAC address. The reason code may indicate the reason for the termination of the coexisting AP MLD. For example, the reason code may be set to a newly defined reason code to indicate coexisting AP MLD termination or coexisting AP MLD maintenance. For example, when the reason code is set to the third value, the reason code indicates coexisting AP MLD termination. When the reason code is set to the fourth value, the reason code indicates coexisting AP MLD maintenance. The coexisting AP MLD termination containment indicates whether the coexisting AP MLD is terminating or not. The termination time indicates the termination time of the coexisting AP MLD. One or more peripheral report elements include information about peripheral APs of the collaborating APs that work with the coexisting AP MLD in order to recommend optional peripherals for BSS transitions to non-AP MLDs associated with the coexisting AP MLD.

[0159] Figure 9 is a diagram of a frame format according to an embodiment of this application. As shown in Figure 9, the MPDU may include one or more of the following fields: frame control, duration, address1, address2, address3, sequence control, Quality of Service (QoS) control, high throughput control (HT Control), frame body, and frame check sequence (FCS). The address1 field indicates the receiver address (RA). Address2 indicates the transmitter address (TA). Address3 indicates the BSSID of the current BSS, i.e., the address of the cooperating AP (which is an AP in the AP MLD). For management frames, address3 may be used for frame filtering. For example, address3 of a frame transmitted by an AP is set to the BSSID corresponding to the AP. Based on address 3, the STA can determine whether the frame belongs to this BSS, and if not, it may discard the frame.

[0160] Termination of a non-coexisting AP MLD causes a non-AP MLD associated with the non-coexisting AP MLD to perform a BSS transition. Thus, embodiments of this application further provide a multilink communication method for indicating that a non-AP MLD associated with a non-coexisting AP MLD performs a BSS transition.

[0161] Figure 10 is a diagram illustrating the interaction of another multilink communication method according to an embodiment of this application. As shown in Figure 10, refer to the above description for explanations of non-coexistent AP MLDs, coexistent AP MLDs, non-AP MLDs, etc., in the method. Details of the method shown in Figure 10 will not be described. Relay nodes are not included in the method described below, but it can be understood that when the receiver and the transmitter communicate with each other, the forwarding operation may be performed by using relay nodes. As shown in Figure 10, the method includes the following steps.

[0162] 1001: The first non-coexistent AP MLD generates a BTM request frame, which contains the identification information of the second AP MLD.

[0163] For example, the second AP MLD and the first non-coexistent AP MLD are different AP MLDs. For example, the second AP MLD may be a non-coexistent AP MLD or a coexistent AP MLD in the vicinity of the first non-coexistent AP MLD. When the first non-coexistent AP MLD needs to terminate, the first non-coexistent AP MLD generates a BTM request frame to indicate that a non-AP MLD associated with the first non-coexistent AP MLD (e.g., a UHR non-AP MLD) will transition to the second AP MLD, and the BTM request frame includes identification information for the second AP MLD. It should be noted that BTM request frames sent by different cooperating APs may carry different information about the second AP MLD.

[0164] It can be understood that the BTM request frame may, alternatively, be generated by a coexisting AP MLD in conjunction with a first non-coexisting AP MLD, or by a co-operating AP of a coexisting AP MLD in conjunction with a first non-coexisting AP MLD. This is not limited to this application.

[0165] It should be understood that the BTM request frame shown in this embodiment of this application is merely an example. In other possible implementations, a new UHR action frame is defined to indicate that a UHR non-AP MLD performs a BSS transition. For the sake of ease of explanation, in this embodiment of this application, the BTM request frame is used as an example to illustrate the method provided in this embodiment of this application.

[0166] In possible implementations, the address information field of the BTM request frame includes the identifier of the first non-coexistent AP MLD. For example, the identifier of the first non-coexistent AP MLD may include the MAC address of the first non-coexistent AP MLD, and the address information field of the BTM request frame may include the address 1 field, the address 2 field, and the address 3 field. Address 1 of the BTM request frame may be set to the broadcast address, and address 3 of the BTM frame may be set to the MAC address of the first non-coexistent AP MLD. For a non-AP MLD associated with the first non-coexistent AP MLD (e.g., a UHR non-AP MLD), after receiving the BTM request frame, the UHR non-AP MLD performs a BSS transition based on the BTM request frame. For pre-EHT STAs and EHT non-AP MLDs, since address 3 of the BTM frame is not the identifier of the corresponding BSS, pre-EHT STAs and EHT non-AP MLDs discard the BTM request frame after receiving the broadcast BTM request frame.

[0167] In this embodiment of the application, it can be understood that a UHR non-AP MLD associated with a non-coexistent AP MLD may receive a management frame in which address 3 is set to the BSSID of the corresponding link, or may receive a management frame in which address 3 is set to the MAC address of the non-coexistent AP MLD.

[0168] In this implementation, the first non-coexistent AP MLD includes its identification information at address 3 of the BTM request frame to indicate that the UHR non-AP MLD associated with the first non-coexistent AP MLD will perform a BSS transition.

[0169] When a coexisting AP MLD terminates but the collaborating AP does not, it can be understood that the coexisting AP MLD may also set address 3 of the BTM request frame in its identification information and broadcast the BTM request frame by using the collaborating AP of the coexisting AP MLD to indicate that a non-AP MLD associated with the coexisting AP MLD (e.g., an EHT non-AP MLD) should perform a BSS transition. In this case, the EHT non-AP MLD performs a BSS transition after receiving the BTM request frame, and the pre-EHT STA and UHR non-AP MLDs discard the BTM request frame after receiving it.

[0170] For example, a BTM request frame further includes at least one of the following: BSS termination information, link removal information, and link transition information, the BSS termination information indicating whether a BSS associated with the first non-coexistent AP MLD is terminated; the link removal information indicating whether a link associated with the first non-coexistent AP MLD (i.e., the link on which the BTM frame was received) is removed; and the link transition information indicating whether a transition is performed between different coexistent AP MLDs that cooperate with the first non-coexistent AP MLD.

[0171] Figure 11 shows a BTM request frame according to an embodiment of this application. The BTM frame may include at least one of the following: category, wireless network management operation, dialog token, request mode, disassociation timer, validity interval, BSS termination duration, session info, and BSS transition candidate list. The BSS transition candidate list is optional. The request mode may include at least one of the following: preferred candidate list included, abridge, disassociation imminent, BSS termination included, extended service set (ESS) disassociation imminent, link removal, and link transition. The BSS termination included field indicates whether the BSS is invalid or not. For a single UHR non-AP MLD, the BSS termination inclusion field has the following meanings, for example, indicating whether the BSS of a cooperating AP (e.g., the AP that sends the BTM request frame) is terminated, or whether all BSS of a coexisting AP MLD is terminated, or whether all BSS of a non-coexisting AP MLD is terminated. The link removal information indicates whether a link (e.g., the link on which the BTM request frame was received) is removed. Therefore, in a UHR system, the link transition information, BSS termination inclusion information, and link removal information may indicate whether a BSS transition is performed between different non-coexisting AP MLDs, or whether a link transition is performed between different coexisting AP MLDs within the same non-coexisting AP MLD.

[0172] For example, when the first non-coexistent AP MLD terminates, it must broadcast a BTM request frame over all links of all coexistent AP MLDs that interact with it. In this case, the BSS termination containment field is set to 1, the link removal field is set to 0, and the link transition field is set to 0. After receiving the BTM frame, the UHR non-AP MLD performs a BSS transition. After receiving the BTM request frame, the pre-EHT STA and EHT non-AP MLD discard the BTM request frame and do not perform a BSS transition.

[0173] 1002: The first non-coexistent AP MLD sends a BTM request frame by using the cooperating AP, and in response, the non-AP MLD receives the BTM request frame.

[0174] In this embodiment of the application, the BTM request frame may, alternatively, be generated by a cooperating AP, or it may be understood that the BTM request frame is generated by a coexisting AP MLD cooperating with a first non-coexisting AP MLD. For example, when the first non-coexisting AP MLD needs to terminate, the first non-coexisting AP MLD may send a command to a coexisting AP MLD or cooperating AP cooperating with the first non-coexisting AP MLD, causing the coexisting AP MLD or cooperating AP to generate a BTM request frame.

[0175] 1003: non-AP MLD analyzes the BTM request frame.

[0176] For example, a non-AP MLD may perform a BSS transition based on a BTM request frame. For example, a non-AP MLD may transition to a second non-coexistent AP MLD based on a BTM request frame.

[0177] For example, a non-AP MLD may further transmit a BTM response frame by using a non-AP MLD-cooperative STA. The BTM response frame may be generated by the STA, or by a non-AP MLD with which the STA is cooperative.

[0178] In the implementation method, the multilink communication method shown in Figure 10 may further include step 1004.

[0179] 1004: The first non-coexistent AP MLD transmits a second communication frame by using a cooperating AP, and in response, the non-AP MLD receives the second communication frame by using an STA. The second communication frame includes a reduced neighbor report (RNR) element, which includes information about at least one cooperating AP of a neighboring coexisting AP MLD that interacts with the first non-coexistent AP MLD.

[0180] For example, the second communication frame may be a beacon frame or a newly defined broadcast frame. The cooperative AP may cooperate with a third coexisting AP MLD, and the third coexisting AP MLD cooperates with the first non-coexisting AP MLD. At least one cooperative AP cooperates with a coexisting AP MLD that is in the first non-coexisting AP MLD and in the vicinity of the third coexisting AP MLD, that is, the cooperative AP that transmits the second communication frame and at least one cooperative AP cooperate with different coexisting AP MLDs in the same non-coexisting AP MLD. The first non-coexisting AP MLD may indicate that all cooperative APs in the third coexisting AP MLD broadcast the second communication frame, and the second communication frame includes an RNR element, which carries information about at least one cooperative AP in a coexisting AP MLD that is in the vicinity of the third coexisting AP MLD and cooperates with the first non-coexisting AP MLD.

[0181] After receiving the second communication frame, the non-AP MLD may obtain information about surrounding coexisting AP MLDs based on the second communication frame.

[0182] It can be understood that the method shown in Figure 5 may be combined with the method shown in Figure 10. For example, when a non-coexistent AP MLD needs to terminate, the non-coexistent AP MLD may use a first communication frame to indicate the termination time of the non-coexistent AP MLD and an optional peripheral report sub-element, and / or send a BTM request frame to indicate that a non-AP MLD associated with the non-coexistent AP MLD should perform a BSS transition.

[0183] A single UHR non-AP MLD may be selected to be associated with a coexisting AP MLD or a non-coexisting AP MLD. When the non-coexisting AP MLD or coexisting AP MLD associated with the UHR non-AP MLD terminates, the UHR non-AP MLD may transition to a peripheral non-coexisting AP MLD or a peripheral coexisting AP MLD. Generally, in order for a non-AP MLD to choose to transition to a peripheral coexisting AP MLD, it is necessary to query the current non-coexisting AP MLD or coexisting AP MLD to obtain relevant information about the peripheral coexisting AP MLD, or to perform a channel scan. Thus, embodiments of this application further provide a multilink communication method for providing relevant information about peripheral coexisting AP MLDs for a UHR non-AP MLD.

[0184] Figure 12 is a diagram illustrating the interaction of yet another multilink communication method according to an embodiment of this application. As shown in Figure 12, refer to the above description for explanations of non-coexistent AP MLDs, coexistent AP MLDs, non-AP MLDs, etc., in the method. Details of the method shown in Figure 12 will not be described. Relay nodes are not included in the method described below, but it can be understood that when the receiver and the transmitter communicate with each other, the forwarding operation may be performed by using relay nodes. As shown in Figure 12, the method includes the following steps.

[0185] 1201: The STA sends a probe request frame, and in response, the AP receives the probe request frame.

[0186] A probe request frame includes identification information for a first coexisting AP MLD and second instruction information, where the first coexisting AP MLD interacts with a third non-coexisting AP MLD. The second instruction information indicates the probe range of the probe request. For example, the second instruction information indicates that the first coexisting AP MLD should be probed. Alternatively, the second instruction information indicates that a coexisting AP MLD that interacts with the third non-coexisting AP MLD and is located near the first coexisting AP MLD should be probed. Alternatively, the second instruction information indicates that the first coexisting AP MLD and a coexisting AP MLD that interacts with the third non-coexisting AP MLD and is located near the first coexisting AP MLD should be probed. Alternatively, the second instruction information indicates that a coexisting AP MLD that interacts with the third non-coexisting AP MLD should be probed.

[0187] For example, STA is an STA that interacts with a non-AP MLD. For example, a UHR non-AP MLD sends a probe request frame by using an STA. AP interacts with a first coexisting AP MLD, or AP interacts with a coexisting AP MLD of a third non-coexisting AP MLD.

[0188] For example, a probe request frame may be a newly defined probe request frame. For example, a probe request frame may also be called a protected probe action frame and is used to probe information about a given coexisting AP MLD and a coexisting AP MLD that is in the vicinity of the given coexisting AP MLD and interacts with the same non-coexisting AP MLD.

[0189] For example, the probe request frame may further include at least one of the following: the identification information of a third non-coexistent AP MLD and a service set identifier (SSID).

[0190] For example, a probe request frame includes a category, an action, an SSID, and at least one of the following: a probe request multi-link element.

[0191] For example, a probe request multilink element may include a probe scope field, which carries second directive information indicating the probe scope of the probe request frame. For example, if the probe scope field is set to x1, this indicates that the probe request frame is to be used to probe information about a first coexisting AP MLD. In another example, if the probe scope field is set to x2, this indicates that the probe request frame is to be used to probe information about a first coexisting AP MLD and a coexisting AP MLD that is in the vicinity of the first coexisting AP MLD and interacts with the same non-coexisting AP MLD (i.e., a third non-coexisting AP MLD). In yet another example, if the probe scope field is set to x3, this indicates that the probe request frame is to be used to probe information about a coexisting AP MLD that is in the vicinity of the first coexisting AP MLD and interacts with a third non-coexisting AP MLD. In another example, if the probe range field is set to x4, this indicates that the probe request frame will be used to probe for information about the entire third non-coexistent AP MLD (i.e., probe all AP MLDs that interact with the third non-coexistent AP MLD).

[0192] It can be understood that x1, x2, x3, and x4 represent different values ​​in the probe range field; that is, x1, x2, x3, and x4 can be understood as different values. For example, x1 may be 0, x2 may be 1, x3 may be 2, x4 may be 3, or x1, x2, x3, and x4 may be other values. The values ​​of x1, x2, x3, and x4 are not limited in this application.

[0193] For example, the probe request multilink element further includes a non-coexistent AP MLD MAC address field, and the identification information of the third non-coexistent AP MLD is carried in the non-coexistent AP MLD MAC address field.

[0194] Figure 13 shows a probe request multilink element according to an embodiment of this application. As shown in Figure 13, the probe request multilink element includes at least one of the following: element ID (e.g., element ID=255), length, element ID extension (e.g., element ID extension=107), multilink control field, common info field, and link info field. For example, the multilink control field may include type (e.g., type=1), reserved field, and existence bitmap. For example, type may include 3 bits and reserved field may include 1 bit. The existence bitmap may include 12 bits and indicate whether the relevant information in the common info field exists or not. For example, one bit in the existence bitmap indicates whether the AP MLD ID field exists or not, one bit in the existence bitmap indicates whether the non-coexistent AP MLD MAC address field exists or not, and one bit in the existence bitmap indicates whether the probe range field exists or not.

[0195] For example, the common information field may include a common info length field and at least one of the following: an MLD MAC address field (used to carry the MAC address of the first coexisting AP MLD), a non-coexisting AP MLD MAC address field, and a probe range field. For example, the link information field may further include one or more per-STA profile fields, each of which may include a sub-element ID (e.g., sub-element ID=0), length, an STA control field, and an STA info field. The STA control field may include a link ID field, a complete profile requested field, and a reserved field. For example, the link ID field may contain 4 bits, the complete profile requested field may contain 1 bit, and the reserved field may contain 11 bits.

[0196] 1202: The AP sends a probe response frame, and in response, the STA receives the probe response frame.

[0197] For example, after receiving a probe request frame, a third non-coexistent AP MLD may send a probe response frame by using one of the cooperating APs of one cooperating coexistent AP MLD.

[0198] For example, a probe response frame includes the probe result of a probe request frame. For example, when the second instruction indicates to probe a first coexisting AP MLD, the probe response frame includes information about the first coexisting AP MLD. When the second instruction indicates to probe a coexisting AP MLD that is in conjunction with a third non-coexisting AP MLD and is located near the first coexisting AP MLD, the probe response frame includes information about one or more coexisting AP MLDs that are located near the first coexisting AP MLD and are in conjunction with the third non-coexisting AP MLD. When the second instruction indicates to probe the first coexisting AP MLD and a coexisting AP MLD that is in conjunction with a third non-coexisting AP MLD and is located near the first coexisting AP MLD, the probe response frame includes information about the first coexisting AP MLD and information about one or more coexisting AP MLDs that are located near the first coexisting AP MLD and are in conjunction with the third non-coexisting AP MLD. When the second instruction indicates that a coexisting AP MLD is being probed in conjunction with the third non-coexisting AP MLD, the probe response frame may include information about one or more coexisting AP MLDs that are cooperating with the third non-coexisting AP MLD.

[0199] In a possible implementation, when the second instruction indicates that a coexisting AP MLD is being probed in conjunction with a third non-coexisting AP MLD, the probe response frame includes the third instruction, which indicates the number of coexisting AP MLDs that are in conjunction with the third non-coexisting AP MLD.

[0200] When a third non-coexistent AP MLD includes many coexisting AP MLDs, the signaling overhead is high if the probe response frame includes information about all coexisting AP MLDs that coexist with the third non-coexistent AP MLD. In this case, the probe response frame may include statistical information about the third non-coexistent AP MLD, and it is not necessary to carry information about all coexisting AP MLDs that coexist with the third non-coexistent AP MLD, thereby reducing the signaling overhead. For example, the probe response frame may include the number of coexisting AP MLDs that coexist with the third non-coexistent AP MLD.

[0201] In this embodiment of the application, the non-AP MLD includes second instruction information indicating a probe range in a probe request frame transmitted by the STA, so that the non-AP MLD can use the second instruction information to probe information about coexisting AP MLDs in the vicinity of the first coexisting AP MLD.

[0202] In possible implementations, the probe request frame may include an SSID but may not include identification information for a first coexisting AP MLD and instruction information for a second AP. In this implementation, a non-AP MLD may receive a probe response frame that has the same SSID as the probe request frame and is returned by the AP, by using the SSID included in the probe request frame broadcast by the STA. The probe response frame includes information about the AP and information about the coexisting AP MLDs with which the AP collaborates. The non-AP MLD may obtain information about one or more surrounding coexisting AP MLDs by using one or more received probe response frames.

[0203] In this implementation, the probe request frame transmitted by the non-AP MLD only needs to carry the SSID, thereby reducing signaling overhead.

[0204] Figure 14 is a diagram illustrating the interaction of yet another multilink communication method according to an embodiment of this application. As shown in Figure 14, refer to the above description for explanations of non-coexistent AP MLDs, coexistent AP MLDs, non-AP MLDs, etc., in the method. Details of the method shown in Figure 14 will not be described. Relay nodes are not included in the method described below, but it can be understood that a forwarding operation may be performed by using relay nodes when the receiver and transmitter communicate with each other. As shown in Figure 14, the method includes the following steps.

[0205] 1401: AP transmits a third communication frame, and STA receives the third communication frame in response. The third communication frame may include fourth instruction information, which indicates that the second coexisting AP MLD is removed from the fourth non-coexisting AP MLD, or that the second coexisting AP MLD transitions from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD.

[0206] For example, AP cooperates with a second coexisting AP MLD, and the second coexisting AP MLD cooperates with a fourth non-coexisting AP MLD. The fifth non-coexisting AP MLD and the fourth non-coexisting AP MLD are two different non-coexisting AP MLDs. For example, the fifth non-coexisting AP MLD may be a non-coexisting AP MLD in the vicinity of the fourth AP MLD.

[0207] For example, the third communication frame may be generated by the AP or by the second coexisting AP MLD. When the second coexisting AP MLD needs to be removed from the fourth non-coexisting AP MLD, or when the second coexisting AP MLD needs to transition from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD, the AP sends the third communication frame to indicate that the non-AP MLD associated with the second coexisting AP MLD is performing a BSS transition, or that the non-AP MLD associated with the fourth non-coexisting AP MLD is performing a link transition.

[0208] For example, the third communication frame may further include, or separately include, a fifth instruction information which indicates the time to remove the second coexisting AP MLD from the fourth non-coexisting AP MLD, or the fifth instruction information which indicates the time to transition the second coexisting AP MLD from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD. In other words, the fourth and fifth instruction information in the third communication frame indicate that the second coexisting AP MLD is removed from the fourth non-coexisting AP MLD, and indicate the time to remove the second coexisting AP MLD from the fourth non-coexisting AP MLD. Alternatively, the fourth and fifth instruction information within the third communication frame indicates that the second coexisting AP MLD transitions from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD, and indicates the time required to transition the second coexisting AP MLD from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD.

[0209] For example, the fifth instruction includes a second duration, which indicates that the second coexisting AP MLD is removed from the fourth non-coexisting AP MLD after the second duration. Alternatively, the second duration indicates that the second coexisting AP MLD transitions from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD after the second duration. For example, the unit of the second duration is TU.

[0210] 1402:STA analyzes the third communication frame.

[0211] For example, STA cooperates with non-AP MLD. After receiving the third communication frame, the UHR non-AP MLD associated with the fourth non-coexistent AP MLD may perform a link transition. For example, the UHR non-AP MLD may transition the link between the UHR non-AP MLD and the second coexistent AP MLD to another surrounding coexistent AP MLD that is cooperating with the fourth non-coexistent AP MLD. Alternatively, after receiving the third communication frame, the UHR non-AP MLD may perform a BSS transition. For example, the UHR non-AP MLD may transition the BSS to a surrounding AP MLD.

[0212] In possible implementations, the non-AP MLD may determine the AP that transmits the third communication frame based on the transmitter address of the third communication frame, and then determine a second coexisting AP MLD with which the AP cooperates, and a fourth non-coexisting AP MLD with which the second coexisting AP MLD cooperates.

[0213] In other possible implementations, the third communication frame further includes identification information for the second coexisting AP MLD and identification information for the fourth non-coexisting AP MLD. The non-AP MLD may determine the second coexisting AP MLD and the fourth non-coexisting AP MLD based on the identification information for the second coexisting AP MLD and the identification information for the fourth non-coexisting AP MLD.

[0214] In this embodiment of the application, the fourth instruction information may indicate that the second coexisting AP MLD is removed from the fourth non-coexisting AP MLD, or that the second coexisting AP MLD transitions from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD, thereby enabling a non-AP MLD associated with the second coexisting AP MLD or the fourth non-coexisting AP MLD to perform a BSS transition or link transition in a timely manner.

[0215] In possible implementations, the fourth instruction indicates that the second coexisting AP MLD is terminating, and the fifth instruction indicates the termination time of the second coexisting AP MLD. Alternatively, the fourth instruction indicates that the fourth non-coexisting AP MLD is terminating, and the fifth instruction indicates the termination time of the fourth non-coexisting AP MLD. Alternatively, the fourth instruction indicates that the second coexisting AP MLD is being removed from the fourth non-coexisting AP MLD, and the fifth instruction indicates the time to remove the second coexisting AP MLD from the fourth non-coexisting AP MLD. Alternatively, the fourth instruction indicates that the second coexisting AP MLD is transitioning from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD, and the fifth instruction indicates the time to transition the second coexisting AP MLD from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD.

[0216] For example, the third communication frame may be a beacon frame, and the fourth and fifth instruction information may be included in the reconfiguration multilink element of the third communication frame. For example, the reconfiguration multilink element may include a reconfiguration type field and a reconfiguration timer field. The reconfiguration type field indicates the reconfiguration type, which includes one of the following: termination of a non-coexistent AP MLD, termination of a coexistent AP MLD, removal of a coexistent AP MLD from a non-coexistent AP MLD, and transition of a coexistent AP MLD from the current non-coexistent AP MLD to a new non-coexistent AP MLD. The reconfiguration timer field indicates how much time has elapsed since the event corresponding to the reconfiguration type occurred. In other words, the fourth instruction information is carried in the reconfiguration type field, and the fifth instruction information is carried in the reconfiguration timer field.

[0217] For example, if the reconfiguration type field is set to y1, this indicates that the coexisting AP MLD is terminating; if the reconfiguration type field is set to y2, this indicates that the non-coexisting AP MLD is terminating; if the reconfiguration type field is set to y3, this indicates that the coexisting AP MLD is removed from the current non-coexisting AP MLD, i.e., the coexisting AP MLD will no longer interact with any non-coexisting AP MLDs; and if the reconfiguration type field is set to y4, this indicates that the coexisting AP MLD is transitioning from the current non-coexisting AP MLD to a new non-coexisting AP MLD.

[0218] It can be understood that y1, y2, y3, and y4 represent different values ​​of the reconstruction type field, i.e., y1, y2, y3, and y4 can be understood as different values. For example, the reconstruction type field contains 2 bits, where y1 may be 0, y2 may be 1, y3 may be 2, y4 may be 3, or y1, y2, y3, and y4 may be other values. The values ​​of y1, y2, y3, and y4 are not limited in this application.

[0219] It can be understood that both the removal of a coexisting AP MLD from a non-coexisting AP MLD and the transition of a coexisting AP MLD from the current non-coexisting AP MLD to a new non-coexisting AP MLD cause a non-AP MLD associated with the current non-coexisting AP MLD to perform a BSS transition. Therefore, y3 and y4 may have the same value, that is, when a coexisting AP MLD should be removed from the current non-coexisting AP MLD, or when a coexisting AP MLD should transition from the current non-coexisting AP MLD to a new non-coexisting AP MLD, the reconfiguration type field may be set to y3 to indicate that a non-AP MLD associated with the current non-coexisting AP MLD will perform a BSS transition.

[0220] It should be understood that the fields included in the reconfigured multilink element may be those shown in Figure 6a or Figure 6b. For a specific description of the reconfigured multilink element, refer to the relevant description above or the relevant standards or protocols. Further details are not described again in this specification.

[0221] Figure 15 is a diagram illustrating the interaction of yet another multilink communication method according to an embodiment of this application. As shown in Figure 15, refer to the above description for explanations of non-coexistent AP MLDs, coexistent AP MLDs, non-AP MLDs, etc., in the method. Details of the method shown in Figure 15 will not be described. Relay nodes are not included in the method described below, but it can be understood that when the receiver and the transmitter communicate with each other, the forwarding operation may be performed by using relay nodes. As shown in Figure 15, the method includes the following steps.

[0222] 1501: The AP transmits a second communication frame, and in response, the STA receives the second communication frame. The second communication frame includes a reduced peripheral report element, which contains information about at least one cooperating AP of a coexisting AP MLD that is working with a non-coexisting AP MLD.

[0223] For example, AP is a collaborative AP of a coexisting AP MLD that interacts with a non-coexisting AP MLD. The second communication frame may be a beacon frame or a newly defined broadcast frame. Each collaborative AP of a coexisting AP MLD includes a reduced peripheral report element in the second communication frame, and the reduced peripheral report element includes information about at least one collaborative AP of a coexisting AP MLD that is in the vicinity of the coexisting AP MLD and interacts with the same non-coexisting AP MLD as the coexisting AP MLD.

[0224] 1502:STA analyzes the second communication frame.

[0225] For example, STA collaborates with non-AP MLD. After receiving a second communication frame, the non-AP MLD may determine, based on the second communication frame, information about at least one collaborating AP and information about coexisting AP MLDs with which at least one collaborating AP collaborates.

[0226] In this embodiment of the application, the coexisting AP MLD includes in a second communication frame broadcast by the cooperating AP information about a coexisting AP MLD that is in the vicinity of the coexisting AP MLD and is cooperating with the same non-coexisting AP MLD, thereby enabling the non-AP MLD to obtain information about surrounding coexisting AP MLDs without performing a channel scan.

[0227] It can be understood that the methods provided in embodiments of this application may be combined with each other, and the order of combination may be determined based on a particular implementation. Embodiments of this application are not enumerated. For example, the methods shown in Figures 5, 10, 12, 14, and 15 may be combined. Specifically, when a non-coexistent AP MLD needs to terminate, the method shown in Figure 5 may be used to indicate that the non-coexistent AP MLD should terminate, the method shown in Figure 10 may be used to indicate that a non-AP MLD associated with the non-coexistent AP MLD performs a BSS transition, and the non-AP MLD may obtain information about surrounding coexistent AP MLDs by using the method shown in Figure 12 or 15 and perform a BSS transition based on the information about the surrounding coexistent AP MLDs.

[0228] The communication device provided in the embodiments of this application will be described below.

[0229] In this application, the communication device is divided into functional modules based on embodiments of the method described above. For example, each functional module corresponding to each function may be obtained through division, or two or more functions may be integrated into a single processing module. The integrated module may be implemented in hardware form or in the form of a software functional module. It should be noted that in this application, module division is merely an example and is simply a logical functional division. Other division methods may exist in actual implementations. The communication device in embodiments of this application will be described in detail below with reference to Figures 16 to 18.

[0230] Figure 16 is a diagram showing the structure of a communication device according to an embodiment of this application. As shown in Figure 16, the communication device includes a processing unit 1601 and a transceiver unit 1602. The transceiver unit 1602 may implement corresponding communication functions, and the processing unit 1601 is configured to perform data processing. For example, the transceiver unit 1602 may also be called a communication interface, a communication unit, etc.

[0231] In some embodiments of this application, the communication device may be configured to perform actions performed by the AP in the embodiments of the above method. In this case, the communication device may be the AP or a component (such as a chip or system) that can be configured within the AP, the transceiver unit 1602 is configured to perform operations related to receiving and transmitting of the AP in the embodiments of the above method, and the processing unit 1601 is configured to perform operations related to processing of the AP in the embodiments of the above method.

[0232] For example, the processing unit 1601 is configured to determine a first communication frame, and the transceiver unit 1602 is configured to output the first communication frame.

[0233] The transceiver unit 1602 may transmit the first communication frame to the STA, or it may be understood that the transceiver unit 1602 outputs the first communication frame from the processing unit 1601 to other components within the AP. The relevant explanation for the transceiver unit outputting other frames is similar. Further details will not be explained below.

[0234] In some other embodiments of this application, the communication device may be configured to perform actions performed by the STA in the embodiments of the above method. In this case, the communication device may be the STA or a component (such as a chip or system) that can be configured within the STA, the transceiver unit 1602 is configured to perform operations related to receiving and transmitting of the STA in the embodiments of the above method, and the processing unit 1601 is configured to perform operations related to processing of the STA in the embodiments of the above method.

[0235] The transceiver unit 1602 is configured to receive a first communication frame, and the processing unit 1601 is configured to analyze the first communication frame.

[0236] For a specific explanation of how the processing unit 1601 analyzes the communication frame, it may be understood that one should refer to the embodiments of the method described above. Further details will not be described again in this specification.

[0237] In some further embodiments of this application, the communication device may be configured to perform actions performed by the first non-coexistent AP MLD in embodiments of the above method. In this case, the communication device may be the first non-coexistent AP MLD or a component (such as a chip or system) that can be configured within the first non-coexistent AP MLD, the transceiver unit 1602 is configured to perform operations related to receiving and transmitting of the first non-coexistent AP MLD in embodiments of the above method, and the processing unit 1601 is configured to perform operations related to processing of the first non-coexistent AP MLD in embodiments of the above method.

[0238] For example, the processing unit 1601 is configured to generate a BTM request frame, and the transceiver unit 1602 is configured to output a BTM request frame.

[0239] The transceiver unit 1602 may send the BTM request frame to the non-AP MLD, or it may be understood that the transceiver unit 1602 outputs the BTM request frame from the processing unit 1601 to the AP MLD's cooperating AP.

[0240] For example, the transceiver unit 1602 is further configured to output a second communication frame.

[0241] In some further embodiments of this application, the communication device may be configured to perform actions performed by the non-AP MLD in embodiments of the above method. In this case, the communication device may be the non-AP MLD or a component that can be configured within the non-AP MLD, where the transceiver unit 1602 is configured to perform operations related to receiving and transmitting of the non-AP MLD in embodiments of the above method, and the processing unit 1601 is configured to perform operations related to processing of the non-AP MLD in embodiments of the above method.

[0242] The transceiver unit 1602 is configured to receive BTM request frames, and the processing unit 1601 is configured to analyze the BTM request frames.

[0243] For example, the transceiver unit 1602 is further configured to input a second communication frame.

[0244] In some further embodiments of this application, the communication device may be configured to perform actions performed by the AP in the embodiments of the above method. In this case, the communication device may be the AP or a component (such as a chip or system) that can be configured within the AP, the transceiver unit 1602 is configured to perform operations related to receiving and transmitting of the AP in the embodiments of the above method, and the processing unit 1601 is configured to perform operations related to processing of the AP in the embodiments of the above method.

[0245] For example, the transceiver unit 1602 is configured to receive a probe request frame and output a probe response frame.

[0246] The transceiver unit 1602 may transmit the probe response frame to the STA, or it may be understood that the transceiver unit 1602 outputs the probe response frame from the processing unit 1601 to other components in the AP. The relevant explanation for the transceiver unit outputting other frames is similar. Further details will not be explained below.

[0247] In some further embodiments of this application, the communication device may be configured to perform actions performed by the STA in the embodiments of the above method. In this case, the communication device may be the STA or a component (such as a chip or system) that can be configured within the STA, the transceiver unit 1602 is configured to perform operations related to receiving and transmitting of the STA in the embodiments of the above method, and the processing unit 1601 is configured to perform operations related to processing of the STA in the embodiments of the above method.

[0248] The transceiver unit 1602 is configured to output probe request frames and input probe response frames.

[0249] In some further embodiments of this application, the communication device may be configured to perform actions performed by the AP in the embodiments of the above method. In this case, the communication device may be the AP or a component (such as a chip or system) that can be configured within the AP, the transceiver unit 1602 is configured to perform operations related to receiving and transmitting of the AP in the embodiments of the above method, and the processing unit 1601 is configured to perform operations related to processing of the AP in the embodiments of the above method.

[0250] For example, the processing unit 1601 is configured to determine a third communication frame, and the transceiver unit 1602 is configured to output the third communication frame.

[0251] The transceiver unit 1602 may transmit a third communication frame to the STA, or it may be understood that the transceiver unit 1602 outputs a third communication frame from the processing unit 1601 to other components within the AP. The relevant explanation for the transceiver unit outputting other frames is similar. Further details will not be explained below.

[0252] In some further embodiments of this application, the communication device may be configured to perform actions performed by the STA in the embodiments of the above method. In this case, the communication device may be the STA or a component (such as a chip or system) that can be configured within the STA, the transceiver unit 1602 is configured to perform operations related to receiving and transmitting of the STA in the embodiments of the above method, and the processing unit 1601 is configured to perform operations related to processing of the STA in the embodiments of the above method.

[0253] The transceiver unit 1602 is configured to receive a third communication frame, and the processing unit 1601 is configured to analyze the third communication frame.

[0254] In some further embodiments of this application, the communication device may be configured to perform actions performed by the AP in the embodiments of the above method. In this case, the communication device may be the AP or a component (such as a chip or system) that can be configured within the AP, the transceiver unit 1602 is configured to perform operations related to receiving and transmitting of the AP in the embodiments of the above method, and the processing unit 1601 is configured to perform operations related to processing of the AP in the embodiments of the above method.

[0255] For example, the processing unit 1601 is configured to determine a second communication frame, and the transceiver unit 1602 is configured to output the second communication frame.

[0256] The transceiver unit 1602 may transmit a second communication frame to the STA, or it may be understood that the transceiver unit 1602 outputs a second communication frame from the processing unit 1601 to other components within the AP. The relevant explanation for the transceiver unit outputting other frames is similar. Further details will not be provided below.

[0257] In some further embodiments of this application, the communication device may be configured to perform actions performed by the STA in the embodiments of the above method. In this case, the communication device may be the STA or a component (such as a chip or system) that can be configured within the STA, the transceiver unit 1602 is configured to perform operations related to receiving and transmitting of the STA in the embodiments of the above method, and the processing unit 1601 is configured to perform operations related to processing of the STA in the embodiments of the above method.

[0258] The transceiver unit 1602 is configured to receive a second communication frame, and the processing unit 1601 is configured to analyze the second communication frame.

[0259] Optionally, the communication device may further include a storage unit. The storage unit may be configured to store instructions and / or data, and the processing unit 1601 may read instructions and / or data from the storage unit, thereby enabling the communication device to implement an embodiment of the above method.

[0260] It should be understood that the specific descriptions of the transceiver unit and processing unit described in the embodiments of this application are merely examples. For specific functions, execution steps, etc., of the transceiver unit and processing unit, please refer to the embodiments of the method described above. Further details will not be described again herein.

[0261] In the embodiments described above, the first communication frame, BTM request frame, probe request frame, probe response frame, second communication frame, third communication frame, etc., are described in the description of the embodiments of the method described above. Further details will not be described again in this specification.

[0262] The above describes the communication device in this embodiment of the application. The possible product forms of the communication device are described below. It should be understood that any form of product having the functions of the communication device shown in Figure 16 falls within the scope of protection of the embodiments of this application. It should be further understood that the following description is merely illustrative and does not limit the product forms of the communication device in the embodiments of this application.

[0263] In possible implementations, in the communication device shown in Figure 16, the processing unit 1601 may be one or more processors, the transceiver unit 1602 may be a transceiver, or the transceiver unit 1602 may be a transmitting unit and a receiving unit, the transmitting unit may be a transmitter, the receiving unit may be a receiver, and the transmitting unit and the receiving unit may be integrated into a single device, for example, a transceiver. In this embodiment of the application, the processor and the transceiver may be coupled, etc. The method of connecting the processor and the transceiver is not limited to the embodiments of the application. In the process of performing the above method, the process of transmitting information in the above method may be understood as the process of outputting information by the processor. When outputting information, the processor outputs the information to the transceiver so that the transceiver transmits the information. After the information has been output by the processor, further processing may need to be performed on the information, and then the information arrives at the transceiver. Similarly, the process of receiving information in the above method may be understood as the process of receiving input information by the processor. When the processor receives input information, the transceiver receives the information and inputs it to the processor. Furthermore, after the transceiver receives the information, other processing may need to be performed on the information, and then the information is received by the processor.

[0264] As shown in Figure 17, the communication device 170 includes one or more processors 1720 and a transceiver 1710.

[0265] In some embodiments of this application, the communication device may be configured to perform steps, functions, etc., that are performed by the AP in the embodiments of the above method.

[0266] The processor 1720 is configured to determine the first communication frame, and the transceiver 1710 is configured to transmit the first communication frame.

[0267] In some other embodiments of this application, the communication device may be configured to perform steps, functions, etc., that are performed by the STA in the embodiments of the method described above.

[0268] The transceiver 1710 is configured to receive a first communication frame, and the processor 1720 is configured to analyze the first communication frame.

[0269] It should be understood that the specific descriptions of the transceivers and processors described in the embodiments of this application are merely examples. For specific functions, execution steps, etc., of the transceivers and processors, please refer to the embodiments of the method described above. Further details will not be described again herein.

[0270] In some further embodiments of this application, the communication device may be a non-coexistent AP MLD or a component that can be configured within a non-coexistent AP MLD. For example, the processor 1720 may be configured to generate BTM request frames, and the transceiver 1710 may be configured to transmit BTM request frames (e.g., to transmit BTM request frames to the AP).

[0271] In some further embodiments of this application, the communication device may be a non-AP MLD or a component that can be configured within a non-AP MLD. For example, the transceiver 1710 may be configured to receive BTM request frames (e.g., to receive BTM request frames from an STA), and the processor 1720 may be configured to parse BTM request frames.

[0272] In some further embodiments of this application, the communication device may be configured to perform steps, functions, etc., that are performed by the AP in the embodiments of the above method.

[0273] The transceiver 1710 is configured to receive a probe request frame and transmit a probe response frame.

[0274] In some further embodiments of this application, the communication device may be configured to execute the steps, functions, etc. executed by the STA in the embodiments of the above method.

[0275] The transceiver 1710 is configured to transmit a probe request frame and receive a probe response frame.

[0276] In some further embodiments of this application, the communication device may be configured to execute the steps, functions, etc. executed by the AP in the embodiments of the above method.

[0277] The processor 1720 is configured to determine a third communication frame, and the transceiver 1710 is configured to transmit the third communication frame.

[0278] In some further embodiments of this application, the communication device may be configured to execute the steps, functions, etc. executed by the STA in the embodiments of the above method.

[0279] The transceiver 1710 is configured to receive a third communication frame, and the processor 1720 is configured to analyze the third communication frame.

[0280] In some further embodiments of this application, the communication device may be configured to execute the steps, functions, etc. executed by the AP in the embodiments of the above method.

[0281] The processor 1720 is configured to determine a second communication frame, and the transceiver 1710 is configured to transmit the second communication frame.

[0282] In some further embodiments of this application, the communication device may be configured to execute the steps, functions, etc. executed by the STA in the embodiments of the above method.

[0283] The transceiver 1710 is configured to receive a second communication frame, and the processor 1720 is configured to analyze the second communication frame.

[0284] In the embodiments described above, the first communication frame, BTM request frame, probe request frame, probe response frame, second communication frame, third communication frame, etc., are described in the description of the embodiments of the method described above. Further details will not be described again in this specification.

[0285] In the various implementations of the communication device shown in Figure 17, the transceiver may include a receiver and a transmitter, the receiver being configured to perform a receiving function (or operation), and the transmitter being configured to perform a transmitting function (or operation). Furthermore, the transceiver is configured to communicate with other devices / devices through a transmission medium.

[0286] Optionally, the communication device 170 may further include one or more memories 1730 configured to store program instructions and / or data. The memories 1730 are coupled to the processor 1720. The coupling in this embodiment of the application may be an indirect coupling or communication connection between electronic, mechanical or other types of devices, units or modules used for information exchange between devices, units or modules. The processor 1720 may cooperate with the memories 1730. The processor 1720 may execute program instructions stored in the memories 1730. Optionally, at least one of the one or more memories may be included in the processor.

[0287] The specific connecting medium between the transceiver 1710, the processor 1720, and the memory 1730 is not limited to this embodiment of the application. In this embodiment of the application, the memory 1730, the processor 1720, and the transceiver 1710 are connected through a bus 1740 in Figure 17. In Figure 17, the bus is indicated by the use of a thick line. The methods of connection between other components are merely illustrative examples and are not limited thereto. Buses may be classified as address buses, data buses, control buses, etc. For ease of representation, only one thick line represents a bus in Figure 17, but this does not mean that there is only one bus or only one type of bus.

[0288] In this embodiment of the application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. The processor can implement or execute the methods, steps and logic block diagrams disclosed in embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed with reference to embodiments of this application may be performed directly by the hardware processor or by using a combination of hardware and software modules within the processor, etc.

[0289] In embodiments of this application, memory may include, but is not limited to, a hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable ROM (EPROM), read-only memory (ROM), or compact disc read-only memory (CD-ROM). Memory is any storage medium that can be used to carry or store program code in the form of instructions or data structures and that can be read and / or written to by a computer (e.g., a communication device as described in this application). However, this application is not limited thereto. Memory in embodiments of this application may, alternatively, be a circuit or any other device capable of implementing a storage function and configured to store program instructions and / or data.

[0290] For example, the processor 1720 is configured primarily to process communication protocols and data, control the entire communication device, execute software programs, and process data from the software programs. The memory 1730 is configured primarily to store software programs and data. The transceiver 1710 may include a control circuit and an antenna. The control circuit is configured primarily to perform conversions between baseband signals and radio frequency signals and to process radio frequency signals. The antenna is configured primarily to receive and transmit radio frequency signals in the form of electromagnetic waves. Input / output devices such as touchscreens, displays, or keyboards are configured primarily to receive data entered by the user and output data to the user.

[0291] After the communication device is powered on, the processor 1720 may read the software program in the memory 1730, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1720 performs baseband processing on the data to be transmitted and then outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal in the form of electromagnetic waves through the antenna. When data is transmitted to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 1720. The processor 1720 converts the baseband signal into data and processes the data.

[0292] In other implementations, the radio frequency circuit and antenna may be located independently of the processor that performs baseband processing. For example, in a distributed scenario, the radio frequency circuit and antenna may be located independently of the communication equipment.

[0293] It can be understood that the communication device shown in this embodiment of this application may, alternatively, include more components than those shown in Figure 17. This is not limited to this embodiment of this application. The methods performed by the processor and transceiver described above are merely examples. For specific steps performed by the processor and transceiver, refer to the methods described above.

[0294] In other possible implementations, in the communication device shown in Figure 16, the processing unit 1601 may be one or more logic circuits, and the transceiver unit 1602 may be an input / output interface, or may be called a communication interface, interface circuit, interface, etc. Alternatively, the transceiver unit 1602 may include a transmit unit and a receive unit. The transmit unit may be an output interface, and the receive unit may be an input interface. The transmit unit and the receive unit are integrated into a single unit, for example, an input / output interface. As shown in Figure 18, the communication device shown in Figure 18 includes a logic circuit 1801 and an interface 1802. In other words, the processing unit 1601 may be implemented using the logic circuit 1801, and the transceiver unit 1602 may be implemented using the interface 1802. The logic circuit 1801 may be a chip, processing circuit, integrated circuit, system on chip (SoC), etc. The interface 1802 may be a communication interface, input / output interface, pin, etc. For example, Figure 18 shows an example where the communication device is a chip. The chip includes a logic circuit 1801 and an interface 1802.

[0295] In this embodiment of the application, the logic circuits and interfaces may be coupled to each other as an alternative. The specific method of connection between the logic circuits and interfaces is not limited to this embodiment of the application.

[0296] In some embodiments of this application, the communication device may be configured to perform steps, functions, etc., that are performed by the AP in the embodiments of the above method.

[0297] For example, logic circuit 1801 is configured to determine a first communication frame, and interface 1802 is configured to output the first communication frame.

[0298] In some other embodiments of this application, the communication device may be configured to execute the steps, functions, etc. executed by the STA in the above method embodiments.

[0299] For example, interface 1802 is configured to input a first communication frame, and logic circuit 1801 is configured to analyze the first communication frame.

[0300] In some further embodiments of this application, the communication device may be configured to execute the steps, functions, etc. executed by the first non-coexistence AP MLD in the above method embodiments.

[0301] For example, logic circuit 1801 is configured to generate a BTM request frame, and interface 1802 is configured to output the BTM request frame.

[0302] In some further embodiments of this application, the communication device may be configured to execute the steps, functions, etc. executed by the non-AP MLD in the above method embodiments.

[0303] For example, interface 1802 is configured to input a BTM request frame, and logic circuit 1801 is configured to analyze the BTM request frame.

[0304] In some further embodiments of this application, the communication device may be configured to execute the steps, functions, etc. executed by the AP in the above method embodiments.

[0305] For example, interface 1802 is configured to input a probe request frame and output a probe response frame.

[0306] In some further embodiments of this application, the communication device may be configured to execute the steps, functions, etc. executed by the STA in the above method embodiments.

[0307] For example, interface 1802 is configured to output probe request frames and input probe response frames.

[0308] In some further embodiments of this application, the communication device may be configured to perform steps, functions, etc., that are performed by the AP in the embodiments of the above method.

[0309] For example, logic circuit 1801 is configured to determine a third communication frame, and interface 1802 is configured to output the third communication frame.

[0310] In some further embodiments of this application, the communication device may be configured to perform steps, functions, etc., that are performed by the STA in the embodiments of the above method.

[0311] For example, interface 1802 is configured to receive a third communication frame, and logic circuit 1801 is configured to analyze the third communication frame.

[0312] In some further embodiments of this application, the communication device may be configured to perform steps, functions, etc., that are performed by the AP in the embodiments of the above method.

[0313] For example, logic circuit 1801 is configured to determine a second communication frame, and interface 1802 is configured to output the second communication frame.

[0314] In some other embodiments of this application, the communication device may be configured to perform steps, functions, etc., that are performed by the STA in the embodiments of the method described above.

[0315] For example, interface 1802 is configured to receive a second communication frame, and logic circuit 1801 is configured to analyze the second communication frame.

[0316] It should be understood that the specific description of the logic circuits and interfaces in this embodiment of this application is merely illustrative. For specific functions, execution steps, etc., of the logic circuits and interfaces, please refer to the embodiments of the method described above. Further details will not be described again herein.

[0317] In the embodiments described above, the first communication frame, BTM request frame, probe request frame, probe response frame, third communication frame, second communication frame, etc., are described by referring to the description of the embodiments of the method above. Further details will not be described again in this specification.

[0318] It can be understood that the communication device shown in this embodiment of the application may implement the method provided in the embodiment of the application in hardware form, or in software form. This is not limited to the embodiments of the application.

[0319] Embodiments of this application further provide a wireless communication system. The wireless communication system includes an AP and an STA, the AP and STA may be configured to perform the method according to any one of the embodiments described above. Alternatively, the wireless communication system includes a non-coexisting AP MLD and a non-AP MLD, the non-coexisting AP MLD and the non-AP MLD may be configured to perform the method according to any one of the embodiments described above.

[0320] Furthermore, this application further provides a computer program used to implement operations and / or processes performed by the AP in the manner provided in this application.

[0321] This application further provides a computer program, which is used to implement operations and / or processes performed by the STA in the manner provided in this application.

[0322] This application further provides a computer-readable storage medium for storing computer code. When the computer code is executed on a computer, the computer becomes capable of performing operations and / or processes performed by the AP in the manner provided in this application.

[0323] This application further provides a computer-readable storage medium for storing computer code. When the computer code is executed on a computer, the computer becomes capable of performing operations and / or processes performed by the STA in the manner provided in this application.

[0324] This application further provides a computer program product, which includes computer code or a computer program. When the computer code or computer program is executed on a computer, the operations and / or processes performed by the AP in the manner provided in this application are executed.

[0325] This application further provides a computer program product, which includes computer code or a computer program. When the computer code or computer program is executed on a computer, the operations and / or processes performed by the STA in the manner provided in this application are executed.

[0326] In some embodiments provided in this application, it should be understood that the disclosed systems, apparatuses and methods may be implemented in other ways. For example, the embodiments of the described apparatus are merely examples. For example, the division into units is merely a logical functional division, and other divisions may exist in actual implementations. For example, multiple units or components may be combined or integrated into other systems, or some features may be ignored or not performed. Furthermore, the mutual coupling, direct coupling or communication connection indicated or discussed may be implemented through some interfaces. Indirect coupling or communication connection between apparatuses or units may be implemented electronically, mechanically or in other forms.

[0327] Units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected based on the actual requirements for realizing the technical effects of the solution provided in the embodiments of this application.

[0328] Furthermore, the functional units in the embodiments of this application may be integrated into a single processing unit, or each unit may exist physically independently, or two or more units may be integrated into a single unit. The integrated unit may be implemented in hardware form or in the form of a software functional unit.

[0329] When an integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the unit may be stored on a computer-readable storage medium. Based on this understanding, the technical solution of this application may be implemented essentially, or in part, of the prior art, or all or part of the technical solution may be implemented in the form of a software product. A computer software product is stored on a computer-readable storage medium and includes several instructions for instructing a computer device (which may be a personal computer, server, network device, etc.) to perform all or part of the steps of the method described in embodiments of this application. The computer-readable storage medium includes any medium capable of storing program code, such as a USB flash drive, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0330] The above description is merely a specific way of realizing this application and is not intended to limit the scope of protection of this application. Any modification or substitution that is readily conceivable by a person skilled in the art within the scope of the art disclosed in this application shall fall within the scope of protection of this application. Accordingly, the scope of protection of this application shall be subject to the scope of protection of the claims.

Claims

1. A multilink communication method, The steps include determining a first communication frame, wherein the first communication frame includes identification information of a first access point multilink device (AP MLD) and first instruction information, and the first instruction information indicates the end time of the first AP MLD. The steps of transmitting the first communication frame and A method that includes this.

2. A multilink communication method, The steps include receiving a first communication frame, wherein the first communication frame includes identification information of a first access point multilink device (AP MLD) and first instruction information, and the first instruction information indicates the end time of the first AP MLD, and The steps include: analyzing the first communication frame and A method that includes this.

3. The method according to claim 1 or 2, wherein the first AP MLD is a non-coexisting AP MLD.

4. The method according to claim 1 or 2, wherein the first AP MLD is a coexisting AP MLD, and the first communication frame further includes identification information of a non-coexisting AP MLD with which the coexisting AP MLD cooperates.

5. The method according to any one of claims 1 to 4, wherein the first instruction information includes a first duration, the first duration indicating that the first AP MLD terminates after the first duration.

6. The method according to any one of claims 1 to 5, wherein the identification information and the first instruction information of the first AP MLD are included in the reconstructed multilink element of the first communication frame.

7. The method according to any one of claims 1 to 5, wherein the first communication frame further includes, namely, instruction information indicating the reason for termination of the first AP MLD and at least one of one or more peripheral report elements, the one or more peripheral report elements including information about peripheral access points (APs) of the AP that cooperate with the first AP MLD.

8. A multilink communication method, The first non-coexistent AP MLD generates a Basic Service Set (BSS) Transition Management (BTM) request frame, wherein the BTM request frame includes identification information of the second non-coexistent AP MLD. The first non-coexistent AP MLD transmits the BTM request frame by using the cooperating AP, and A method that includes this.

9. A multilink communication method applicable to non-access point multilink devices (non-AP MLDs), The steps include: receiving a Basic Service Set (BSS) Transition Management (BTM) request frame from a linked AP, wherein the linked AP cooperates with a first non-coexistent AP MLD, and the BTM request frame includes identification information of a second non-coexistent AP MLD; The steps include: analyzing the BTM request frame and A method that includes this.

10. The method according to claim 8 or 9, wherein the address information field of the BTM request frame includes identification information of the first non-coexistent AP MLD.

11. The method according to any one of claims 8 to 10, wherein the BTM request frame further includes at least one of the following: BSS termination inclusion information, link removal information, and link transition information, the BSS termination inclusion information indicating whether or not a BSS associated with the first non-coexistent AP MLD is terminated, the link removal information indicating whether or not a link associated with the first non-coexistent AP MLD is removed, and the link transition information indicating whether or not a transition is performed between different coexistent AP MLDs that cooperate with the first non-coexistent AP MLD.

12. The method according to any one of claims 8, 10, and 11, further comprising the step of transmitting a second communication frame, the second communication frame comprising a reduced peripheral report element, the reduced peripheral report element comprising information relating to at least one cooperating AP of a coexisting AP MLD that cooperates with the first non-coexisting AP MLD.

13. The method according to any one of claims 9 to 11, further comprising the step of receiving a second communication frame, the second communication frame comprising a reduced peripheral report element, the reduced peripheral report element comprising information relating to at least one cooperating AP of a coexisting AP MLD that cooperates with the first non-coexisting AP MLD.

14. A multilink communication method, The steps include: receiving a probe request frame, wherein the probe request frame includes identification information of a first coexisting AP MLD and second instruction information, wherein the first coexisting AP MLD cooperates with a third non-coexisting AP MLD, the second instruction information indicates to probe the first coexisting AP MLD, or the second instruction information indicates to probe a coexisting AP MLD that cooperates with the third non-coexisting AP MLD and is in the vicinity of the first coexisting AP MLD, or the second instruction information indicates to probe the first coexisting AP MLD and a coexisting AP MLD that cooperates with the third non-coexisting AP MLD and is in the vicinity of the first coexisting AP MLD, or the second instruction information indicates to probe a coexisting AP MLD that cooperates with the third non-coexisting AP MLD; The steps include sending a probe response frame and A method that includes this.

15. A multilink communication method, The step of transmitting a probe request frame, wherein the probe request frame includes identification information of a first coexisting AP MLD and second instruction information, wherein the first AP MLD cooperates with a third non-coexisting AP MLD, the second instruction information indicates to probe the first coexisting AP MLD, or the second instruction information indicates to probe a coexisting AP MLD that cooperates with the third non-coexisting AP MLD and is in the vicinity of the first coexisting AP MLD, or the second instruction information indicates to probe the first coexisting AP MLD and a coexisting AP MLD that cooperates with the third non-coexisting AP MLD and is in the vicinity of the first coexisting AP MLD, or the second instruction information indicates to probe a coexisting AP MLD that cooperates with the third non-coexisting AP MLD. The step of receiving the probe response frame and A method that includes this.

16. The method according to claim 14 or 15, wherein when the second instruction information indicates that a coexisting AP MLD is being probed in conjunction with the third non-coexisting AP MLD, the probe response frame includes the third instruction information, the third instruction information indicates the number of coexisting AP MLDs that are in conjunction with the third non-coexisting AP MLD.

17. The method according to any one of claims 14 to 16, wherein the probe request frame further includes identification information of the third non-coexistent AP MLD.

18. The method according to any one of claims 14 to 17, wherein the probe request frame further includes a service set identifier (SSID).

19. A multilink communication method, A step of determining a third communication frame, wherein the third communication frame includes fourth instruction information, the fourth instruction information indicating that the second coexisting AP MLD is removed from the fourth non-coexisting AP MLD, or the fourth instruction information indicating that the second coexisting AP MLD transitions from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD. The steps of transmitting the third communication frame and A method that includes this.

20. A multilink communication method, The steps include receiving a third communication frame, the third communication frame including a fourth instruction information, the fourth instruction information indicating that the second coexisting AP MLD is removed from the fourth non-coexisting AP MLD, or the fourth instruction information indicating that the second coexisting AP MLD transitions from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD, The steps include analyzing the third communication frame and A method that includes this.

21. The method according to claim 19 or 20, wherein the third communication frame further includes a fifth instruction information, the fifth instruction information indicating a time to remove the second coexisting AP MLD from the fourth non-coexisting AP MLD, or the fifth instruction information indicating a time to transition the second coexisting AP MLD from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD.

22. The method according to claim 21, wherein the fifth instruction information includes a second duration, the second duration indicating that the second coexisting AP MLD is removed from the fourth non-coexisting AP MLD after the second duration, or the second duration indicating that the second coexisting AP MLD transitions from the fourth non-coexisting AP MLD to the fifth non-coexisting AP MLD after the second duration.

23. The method according to any one of claims 19 to 22, wherein the third communication frame further includes identification information for the second coexisting AP MLD and identification information for the fourth non-coexisting AP MLD.

24. A communication device comprising a unit configured to perform the method described in any one of claims 1 to 23.

25. A communication device including a processor and memory, The memory is configured to store instructions, A communication device wherein the processor is configured to execute the instructions, so that the method according to any one of claims 1 to 23 is performed.

26. A communication device including logic circuits and interfaces, The logic circuit is coupled to the interface, A communication device wherein the interface is configured to input and / or output code instructions, and the logic circuit is configured to execute the code instructions, so that the method according to any one of claims 1 to 23 is performed.

27. A computer-readable storage medium, The computer-readable storage medium is configured to store a computer program, and when the computer program is executed, the method according to any one of claims 1 to 23 is executed.

28. It is a computer program, A computer program wherein, when the computer program is executed, the method described in any one of claims 1 to 23 is executed.

29. It is a communication system, The communication system includes a first communication device and a second communication device, The first communication device is configured to perform the method described in any one of claims 1 and 3 to 7, and the second communication device is configured to perform the method described in any one of claims 2 to 7, or The first communication device is configured to perform the method described in any one of claims 8 and 10 to 12, and the second communication device is configured to perform the method described in any one of claims 9 to 11 and 13, or The first communication device is configured to perform the method described in any one of claims 14 and 16 to 18, and the second communication device is configured to perform the method described in any one of claims 15 to 18, or A communication system in which the first communication device is configured to perform the method described in any one of claims 19 and 21 to 23, and the second communication device is configured to perform the method described in any one of claims 20 to 23.

Images