Instruction method and apparatus for BTM

Abstract

This application relates to a method and apparatus for providing information in a BTM. The method includes the following: An AP MLD generates and transmits a BTM request frame. The BTM request frame includes first instruction information indicating processing for a BSSID or AP MLD not listed in the BSS transition candidate list entry field, and processing for APs not present in the recommended AP set within the candidate target AP MLD listed in the BSS transition candidate list entry field. According to this application, information instruction in a BTM can be improved. This application is applicable to WLAN systems that support next-generation Wi-Fi protocols of 802.11ax such as 802.11be, Wi-Fi 7, or EHT, next-generation protocols of 802.11be such as Wi-Fi 8 or UHR, or 802.11 series protocols such as Wi-Fi AI. This application is further applicable to WPAN systems, sensing systems, etc. that support UWB.

Description

Technical Field

[0001] [Cross-Reference to Related Applications] This application claims priority to Chinese Patent Application No. 202310638067.7, titled "INFORMATION INDICATION METHOD IN BTM AND APPARATUS", filed with the China National Intellectual Property Administration on May 31, 2023, the entire content of which is incorporated herein by reference.

[0002] [Technical Field] This application relates to the field of wireless communication technologies, and particularly to an information indication method and apparatus in basic service set (BSS) transition management (BTM).

Background Art

[0003] With the development of wireless communication technologies, more wireless communication devices support multi-link (ML) communication, such as simultaneous communication on the 2.4 GHz, 5 GHz, and 6 GHz frequency bands, or simultaneous communication on different channels of the same frequency band. This improves the communication speed between devices. Such devices are usually called multi-link devices (MLDs). An MLD usually includes one or more cooperating stations, and each cooperating station operates on one frequency band, one channel, or one link. If all stations inside an MLD are access points (APs), the MLD may be further called an AP MLD. If all stations inside an MLD are non-access point stations (non-AP STAs), the MLD may be further called a non-AP MLD.

[0004] Currently, when accessing a local area network, a station must belong to a basic service set (BSS). In some scenarios, such as roaming scenarios, a non-AP STA needs to leave its current BSS and join a new one. If a non-AP STA supports Basic Service Set Transition Management (BTM) functionality, this functionality can be used to help achieve BSS transitions. In the BTM process, an AP may send a BSS transition management request (BTM request) frame to the non-AP STA to be disassociated, notifying the non-AP STA that the AP is being disassociated. Furthermore, information about surrounding APs of the non-AP STA may be added to the BTM request frame to help the non-AP STA select a new BSS.

[0005] In conventional technology, an AP MLD may also provide a non-AP MLD with information about surrounding AP MLDs via a BTM request frame to help the non-AP MLD select a new AP MLD for association. However, information guidance in existing BTMs is incomplete regarding BSS transitions between non-AP MLDs and AP MLDs. [Overview of the project]

[0006] Embodiments of this application provide a method and apparatus for information instruction in a BTM to improve information instruction in the BTM, thereby making it clearer to non-AP MLDs the attitude of AP MLDs and the behavior of non-AP MLDs.

[0007] The present invention will be described below in different embodiments. It should be understood that the following implementations and beneficial effects of the different embodiments will be referenced to one another.

[0008] According to a first aspect, the application provides a method for providing information in a BTM. The method includes: an AP MLD generates and transmits a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field and a request mode field, the request mode field including first instruction information, the first instruction information indicating processing for a basic service set identifier (BSS identifier, BSSID) or AP MLD that is not present in the BSS transition candidate list entry field, and processing for an AP that is not present in any of the recommended AP sets in the candidate target AP MLD described in the BSS transition candidate list entry field.

[0009] In this application, BSSID may be used to identify one BSS or one AP. The BSS transition candidate list entry field includes one or more peripheral reporting elements. One peripheral reporting element may be used to carry (or describe) a preference for one target BSS candidate or candidate target AP MLD. Different peripheral reporting elements may carry preferences for different AP sets (AP sets) within the same candidate target AP MLD, and different peripheral reporting elements may, alternatively, carry preferences for different target BSS candidates or candidate target AP MLDs. Thus, “candidate target AP MLD described in the BSS transition candidate list entry field” may refer to a candidate target AP MLD corresponding to a peripheral reporting element in the BSS transition candidate list entry field.

[0010] For details regarding the frame format of the BTM request frame, the BSS transition candidate list entry field, peripheral reporting elements, etc., please refer to the following explanation. Further details are not provided in this specification.

[0011] In this application, the first instruction information is carried in the request mode field of the BTM request frame and indicates the processing for BSSIDs or AP MLDs that are not present in the BSS transition candidate list entry field, and the processing for APs that are not present in any of the recommended AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entry field. This improves the information indication in the BTM, clarifies the processing for APs in the MLD, and allows non-AP MLDs to better recognize the attitude of AP MLDs and the behavior of non-AP MLDs.

[0012] According to a second aspect, the application provides a method for indicating information in a BTM. The method includes: a non-AP MLD receives and parses a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field and a request mode field, the request mode field includes first instruction information, the first instruction information indicating processing for BSSIDs or AP MLDs that are not present in the BSS transition candidate list entry field and processing for APs that are not present in any of the recommended AP sets in the candidate target AP MLDs listed in the BSS transition candidate list entry field.

[0013] According to a third aspect, the application provides a communication device. The communication device may be an AP MLD, or a chip, functional module, etc., configured within the AP MLD. The communication device includes a processing unit and a transceiver unit. The processing unit is configured to generate a BTM request frame, and the transceiver unit is configured to transmit or output a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field and a request mode field, the request mode field includes first instruction information, the first instruction information indicating processing for a BSSID or AP MLD not present in the BSS transition candidate list entry field, and processing for an AP not present in any of the recommended AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entry field.

[0014] According to a fourth aspect, the application provides a communication device. The communication device may be a non-AP MLD, or a chip, functional module, etc., configured within a non-AP MLD. The communication device includes a transceiver unit and a processing unit. The transceiver unit is configured to receive or input BTM request frames, and the processing unit is configured to analyze BTM request frames. The BTM request frame includes a BSS transition candidate list entry field and a request mode field, the request mode field includes first instruction information, the first instruction information indicating processing for BSSIDs or AP MLDs not present in the BSS transition candidate list entry field and processing for APs not present in any of the recommended AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entry field.

[0015] In any one of the possible implementations described above, the first instruction information is an abridged field.

[0016] Optionally, the length of the shortened field is 1 bit.

[0017] Optionally, when the abbreviation field is the first value, the abbreviation field indicates that the sender of the BTM request frame (i.e., the AP MLD) has no recommendation or deprecation for associations between the recipient of the BTM request frame (i.e., a non-AP MLD) and APs that are not present in the BSS transition candidate list entry field (BSSID or AP MLD), and APs that are not present in any of the recommended AP sets within the candidate target AP MLDs present in the BSS transition candidate list entry field. When the abbreviation field is the second value, the abbreviation field indicates that the sender of the BTM request frame (i.e., the AP MLD) excludes or opposes associations between the recipient of the BTM request frame (i.e., a non-AP MLD) and APs that are not present in the BSS transition candidate list entry field (BSSID or AP MLD), and APs that are not present in any of the recommended AP sets within the candidate target AP MLDs present in the BSS transition candidate list entry field.

[0018] For example, the first value is 0 and the second value is 1. Alternatively, the first value is 1 and the second value is 0.

[0019] In this application, the meaning of the abbreviated field is extended so that it can indicate both processing for BSSIDs or AP MLDs that are not present in the BSS transition candidate list entry field, and processing for APs that are not present in the candidate target AP MLDs listed in the BSS transition candidate list entry field. The meaning is clear, there is no additional overhead, and compatibility is good.

[0020] In any one of the possible implementations described above, the BSS transition candidate preference sub-element of the BSS transition candidate list entry field includes a preference field. For example, the existing meaning may continue to be used as the meaning of the preference field, or the meaning of the preference field may change with the evolution of the standard. This is not limited to this application. Alternatively, the preference field may indicate the recommendation level of an AP set. The AP set may be an AP set recommended by the peripheral reporting element to which the preference field belongs. In other words, the AP set is a recommended AP set within the candidate target AP MLD described in the BSS transition candidate list entry field. A larger value in the preference field indicates a higher recommendation level.

[0021] In this application, the meaning of the preference field may be further modified so that the peripheral reporting element can indicate the degree of recommendation of the AP set in the AP MLD when recommending the AP set.

[0022] In any one of the possible implementations of the above embodiments, the first instruction information consists of a shortened field and a shortened extended field. The shortened field indicates the process for a BSSID or AP MLD that is not present in the BSS transition candidate list entry field. The shortened extended field indicates the process for an AP that is not present in any of the recommended AP sets within the candidate target AP MLD listed in the BSS transition candidate list entry field.

[0023] Optionally, the length of the abbreviated extension field is 1 bit. For example, one reserved bit in the request mode field may be used as the abbreviated extension field.

[0024] Optionally, when the Shortened Extension Field is a third value, the Shortened Extension Field indicates that the sender of the BTM Request Frame (i.e., the AP MLD) has no recommendation or non-recommendation for the association of the receiver of the BTM Request Frame (i.e., the non-AP MLD) with an AP that does not exist in any of the recommended AP sets within the candidate target AP MLDs present in the BSS Transition Candidate List Entry Field. When the Shortened Extension Field is a fourth value, the Shortened Extension Field indicates that the sender of the BTM Request Frame (i.e., the AP MLD) excludes or opposes the association of the receiver of the BTM Request Frame (i.e., the non-AP MLD) with an AP that does not exist in any of the recommended AP sets within the candidate target AP MLDs present in the BSS Transition Candidate List Entry Field.

[0025] For example, the third value is 0 and the fourth value is 1. Alternatively, the third value is 1 and the fourth value is 0.

[0026] In this application, the Shortened Extension Field is added to the Request Mode Field to indicate the processing for an AP that does not exist in the candidate target AP MLDs described in the BSS Transition Candidate List Entry Field. For ease of understanding by the non-AP MLD, the logic is clear. Further, the added bits and the existing Shortened Field coexist and the logic is clean.

[0027] According to a fifth aspect, this application provides an information indication method in BTM. The method includes the following. The AP MLD generates and transmits a BTM Request Frame. The BTM Request Frame includes a BSS Transition Candidate List Entry Field and a Request Mode Field. The Request Mode Field includes a Shortened Field. The Shortened Field indicates the processing for a BSSID or AP MLD that does not exist in the BSS Transition Candidate List Entry Field and the processing for an AP set that is not recommended within the candidate target AP MLDs described in the BSS Transition Candidate List Entry Field.

[0028] The "AP set" may include one or more APs. In other words, a single AP may also be used as one AP set, and all APs cooperating with one AP MLD may also be used as one AP set. For the meaning of "AP set not recommended within the candidate target AP MLD described in the BSS transition candidate list entry field", refer to the description in Embodiment 3 below. Details are not described in this specification.

[0029] In this embodiment of this application, the meaning of the shortened field is extended to indicate both the processing for the BSSID or AP MLD that does not exist in the BSS transition candidate list entry field and the processing for the AP set not recommended within the candidate target AP MLD described in the BSS transition candidate list entry field. The information indication in the BTM is improved, and the processing for the AP set not recommended within the MLD is clarified. As a result, the non-AP MLD becomes clearer about the attitude of the AP MLD and the behavior of the non-AP MLD. Furthermore, its meaning is clear, no additional overhead is increased, and compatibility is good.

[0030] According to the sixth aspect, this application provides an information indication method in the BTM. The method includes the following. The non-AP MLD receives and analyzes a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field and a request mode field. The request mode field includes a shortened field, and the shortened field indicates the processing for the BSSID or AP MLD that does not exist in the BSS transition candidate list entry field and the processing for the AP set not recommended within the candidate target AP MLD described in the BSS transition candidate list entry field.

[0031] According to a seventh aspect, the application provides a communication device. The communication device may be an AP MLD, or a chip, functional module, etc., configured within the AP MLD. The communication device includes a processing unit and a transceiver unit. The processing unit is configured to generate a BTM request frame, and the transceiver unit is configured to transmit or output a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field and a request mode field, the request mode field includes an abbreviation field, the abbreviation field indicating processing for a BSSID or AP MLD not present in the BSS transition candidate list entry field and processing for an AP set not recommended within the candidate target AP MLD listed in the BSS transition candidate list entry field.

[0032] According to the eighth aspect, the application provides a communication device. The communication device may be a non-AP MLD, or a chip, functional module, etc., configured within a non-AP MLD. The communication device includes a transceiver unit and a processing unit. The transceiver unit is configured to receive or input BTM request frames, and the processing unit is configured to parse BTM request frames. The BTM request frame includes a BSS transition candidate list entry field and a request mode field, the request mode field includes an abbreviation field, the abbreviation field indicating processing for BSSIDs or AP MLDs not present in the BSS transition candidate list entry field and processing for AP sets not recommended within the candidate target AP MLDs listed in the BSS transition candidate list entry field.

[0033] Referencing any one of the fifth to eighth aspects, in a possible implementation, the length of the abbreviated field is 1 bit. When the abbreviated field is a first value, the abbreviated field indicates that the sender of the BTM request frame (i.e., the AP MLD) has no recommendation or deprecation for the association of the recipient of the BTM request frame (i.e., a non-AP MLD) with BSSIDs or AP MLDs that are not present in the BSS transition candidate list entry field, and with sets of APs that are not recommended in the candidate target AP MLDs present in the BSS transition candidate list entry field. When the abbreviated field is a second value, the abbreviated field indicates that the sender of the BTM request frame (i.e., the AP MLD) excludes or opposes the association of the recipient of the BTM request frame (i.e., a non-AP MLD) with BSSIDs or AP MLDs that are not present in the BSS transition candidate list entry field, and with sets of APs that are not recommended in the candidate target AP MLDs present in the BSS transition candidate list entry field.

[0034] For example, the first value is 0 and the second value is 1. Alternatively, the first value is 1 and the second value is 0.

[0035] Referring to any one of the fifth to eighth aspects, in possible implementations, the BSS transition candidate preference sub-element of the BSS transition candidate list entry field includes a preference field. For example, existing meanings may continue to be used as the meaning of the preference field, or the meaning of the preference field may change with the evolution of the standard. This is not limited to this application. Alternatively, the preference field may indicate the degree of recommendation of an AP set. The AP set may also be the AP set recommended by the peripheral reporting element to which the preference field belongs. In other words, the AP set is the recommended AP set within the candidate target AP MLD described in the BSS transition candidate list entry field. A larger value in the preference field indicates a higher degree of recommendation.

[0036] In this application, the meaning of the preference field may be further modified so that the peripheral reporting element can indicate the degree of recommendation of the AP set in the AP MLD when recommending the AP set.

[0037] According to a ninth aspect, the application provides a method for indicating information in a BTM. The method includes: an AP MLD generates and transmits a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field, which includes one or more peripheral reporting elements, each peripheral reporting element being used to carry information about a candidate target AP MLD. Each peripheral reporting element includes one second instruction information, which indicates processing for APs that are not present in the set of APs in the candidate target AP MLD carried by the peripheral reporting element to which the second instruction information belongs. Since one peripheral reporting element corresponds to one candidate target AP MLD, the second instruction information may be concisely described as indicating processing for APs that are not present in the set of APs in the candidate target AP MLD.

[0038] It can be understood that an "AP set" may contain one or more APs. In other words, a single AP may be used as an AP set, and all APs that work with one AP MLD may also be used as an AP set.

[0039] In this application, the second instruction information is carried in a peripheral reporting element to indicate processing for APs that are not present in the AP set within a single candidate target AP MLD, and as a result, processing can be present for each recommended AP set, which is flexible for use.

[0040] According to a tenth aspect, the application provides a method for indicating information in a BTM. The method includes: a non-AP MLD receives and parses a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field, which includes one or more peripheral reporting elements, each peripheral reporting element being used to carry information about a candidate target AP MLD. Each peripheral reporting element includes one second indication information, which indicates processing for APs that are not present in the set of APs in the candidate target AP MLD carried by the peripheral reporting element to which the second indication information belongs.

[0041] According to an eleventh aspect, the application provides a communication device. The communication device may be an AP MLD, or a chip, functional module, etc., configured within the AP MLD. The communication device includes a processing unit and a transceiver unit. The processing unit is configured to generate a BTM request frame, and the transceiver unit is configured to transmit or output a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field, the BSS transition candidate list entry field includes one or more peripheral reporting elements, one peripheral reporting element used to carry information about one candidate target AP MLD. The peripheral reporting element includes second instruction information, the second instruction information indicating processing for APs that are not present in the set of APs in the candidate target AP MLD carried by the peripheral reporting element to which the second instruction information belongs.

[0042] According to a twelfth aspect, the application provides a communication device. The communication device may be a non-AP MLD, or a chip, functional module, etc., configured within a non-AP MLD. The communication device includes a transceiver unit and a processing unit. The transceiver unit is configured to receive or input BTM request frames, and the processing unit is configured to parse BTM request frames. The BTM request frame includes a BSS transition candidate list entry field, the BSS transition candidate list entry field includes one or more peripheral report elements, one peripheral report element used to carry information about one candidate target AP MLD. The peripheral report element includes second instruction information, the second instruction information indicating processing for APs that are not present in the set of APs in the candidate target AP MLD carried by the peripheral report element to which the second instruction information belongs.

[0043] Referencing any one of the 9th to 12th aspects, in a possible implementation, when the second instruction is a first value, the second instruction indicates that the sender of the BTM request frame (i.e., AP MLD) has no recommendation or deprecation for an association of the recipient of the BTM request frame (i.e., non-AP MLD) with an AP that is not present in the set of APs in the candidate target AP MLD carried in the peripheral reporting element to which the second instruction belongs. When the second instruction is a second value, the second instruction indicates that the sender of the BTM request frame (i.e., AP MLD) excludes or opposes an association of the recipient of the BTM request frame (i.e., non-AP MLD) with an AP that is not present in the set of APs in the candidate target AP MLD carried in the peripheral reporting element to which the second instruction belongs.

[0044] For example, the first value is 0 and the second value is 1. Alternatively, the first value is 1 and the second value is 0.

[0045] Referencing any one of the 9th to 12th embodiments, in a possible implementation, the second instruction information is carried in the BSS transition candidate preference sub-element of the peripheral reporting element.

[0046] For example, since existing BSS transition candidate preference sub-elements are not extensible, the length of the preference field may be shortened, resulting in a preference field length of 7 bits or less, while ensuring that the meaning of the preference field does not change (for example, the preference field indicates the recommendation level of the candidate target AP MLD carried by the peripheral reporting element to which the preference field belongs). One or more bits saved by shortening the preference field represent second instruction information. In other words, the preference field of a BSS transition candidate preference sub-element is 7 bits or less, the bit length of the second instruction information is 1 bit or more, and the sum of the length of the preference field and the bit length of the second instruction information is 1 octet (8 bits) or less. In this implementation, it can be understood that the meaning of the preference field is not limited, and only the length of the preference field is changed. The meaning of the preference field may change further as the standard evolves.

[0047] In this application, the second instruction information is carried in the BSS transition candidate preference sub-element of the peripheral reporting element to indicate processing for APs that are not present in the set of APs within the candidate target AP MLD carried by the peripheral reporting element. Processing can exist for each recommended set of APs within the candidate target AP MLD, which is flexible for use. Furthermore, the second instruction information and preference value are used simultaneously, i.e., the second instruction information is absent when the peripheral reporting element is not used for recommendation.

[0048] Referencing any one of the 9th to 12th embodiments, in possible implementations, the second instruction information is carried in the BSSID information field of the peripheral reporting element. For example, one reserved bit in the BSSID information field may be used as the second instruction information.

[0049] In this application, one reserved bit is used in the BSSID information field of the peripheral reporting element to indicate processing for APs that are not present in the set of APs in the candidate target AP MLD carried by the peripheral reporting element. Processing may exist for each recommended set of APs in the candidate target AP MLD, which is flexible for use.

[0050] According to a thirteenth aspect, the application provides a method for providing information in a BTM. The method includes: an AP MLD generates and transmits a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field, which includes one or more peripheral reporting elements, one of which is used to carry information about a candidate target AP MLD. One peripheral reporting element includes a per-STA profile subelement for any AP that is not excluded in the candidate target AP MLD. One per-STA profile subelement corresponds to one AP that is not excluded in the candidate target AP MLD. Here, “not excluded” may include at least two meanings: “recommended” and “not recommended or not recommended.”

[0051] Furthermore, this application further considers by default that APs not present in the peripheral reporting element are excluded from the association. Here, “APs not present in the peripheral reporting element” may refer to APs that are not in the candidate target AP MLD carried by the peripheral reporting element and that correspond to the APs indicated by the BSSID field and the per-STA profile subelement.

[0052] This application modifies the meaning of AP sets carried in peripheral reporting elements, so that APs not present in peripheral reporting elements are excluded from associations by default in this application. This improves information indication in BTM and clarifies the attitude of AP MLDs and the behavior of non-AP MLDs.

[0053] According to a fourteenth aspect, the application provides a method for providing information in a BTM. The method includes: a non-AP MLD receives and parses a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field, which includes one or more peripheral reporting elements, one of which is used to carry information about one candidate target AP MLD. One peripheral reporting element includes a per-STA profile subelement of any AP that is not excluded in one candidate target AP MLD. One per-STA profile subelement corresponds to one AP that is not excluded in one candidate target AP MLD, where “not excluded” may include at least two meanings: “recommended” and “not recommended or not recommended.”

[0054] According to a 15th aspect, the application provides a communication device. The communication device may be an AP MLD, or a chip, functional module, etc., configured within the AP MLD. The communication device includes a processing unit and a transceiver unit. The processing unit is configured to generate a BTM request frame, and the transceiver unit is configured to transmit or output a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field, the BSS transition candidate list entry field includes one or more peripheral reporting elements, one peripheral reporting element used to carry information about one candidate target AP MLD. One peripheral reporting element includes a per-STA profile subelement of any AP that is not excluded in one candidate target AP MLD. One per-STA profile subelement corresponds to one AP that is not excluded in one candidate target AP MLD. Here, “not excluded” may include at least two meanings: “recommended” and “not recommended or not recommended.”

[0055] According to the sixteenth aspect, the application provides a communication device. The communication device may be a non-AP MLD, or a chip, functional module, etc., configured within a non-AP MLD. The communication device includes a transceiver unit and a processing unit. The transceiver unit is configured to receive or input BTM request frames, and the processing unit is configured to parse BTM request frames. The BTM request frame includes a BSS transition candidate list entry field, the BSS transition candidate list entry field includes one or more peripheral reporting elements, one peripheral reporting element used to carry information about one candidate target AP MLD. One peripheral reporting element includes a per-STA profile subelement of any AP that is not excluded in one candidate target AP MLD. One per-STA profile subelement corresponds to one AP that is not excluded in one candidate target AP MLD. Here, “not excluded” may include at least two meanings: “recommended” and “not recommended or not recommended.”

[0056] Referencing any one of the 13th to 16th aspects, in a possible implementation, each per-STA profile subelement further includes third instruction information, the third instruction information indicating processing for the AP corresponding to the per-STA profile subelement.

[0057] Optionally, when the third instruction is a first value, the third instruction indicates that the sender of the BTM request frame (i.e., AP MLD) has no recommendation or deprecation for the association of the BTM request frame recipient (i.e., non-AP MLD) with the AP corresponding to the per-STA profile subelement. When the third instruction is a second value, the third instruction indicates that the sender of the BTM request frame (i.e., AP MLD) recommends the association of the BTM request frame recipient (i.e., non-AP MLD) with the AP corresponding to the per-STA profile subelement. For example, the first value is 0 and the second value is 1. Alternatively, the first value is 1 and the second value is 0.

[0058] In this application, APs that are not present in the peripheral reporting elements are excluded from the association by default, and third directive information specifies whether APs that exist and correspond to the per-STA profile subelement are recommended for the association. Since the association preference information exists in the per-STA profile subelement corresponding to each AP, there can be processing for each AP within each set of APs provided by the AP MLD, which is very flexible for use.

[0059] Referencing any one of the 13th to 16th embodiments, in possible implementations, the third instruction information is carried in the STA control field of the per-STA profile subelement. For example, one reserved bit in the STA control field of the per-STA profile subelement may be used as the third instruction information.

[0060] According to the 17th aspect, the application provides a communication device, an AP MLD, which includes a processor configured to perform a method according to the first, fifth, ninth, or thirteenth aspect, or any one of the possible implementations of the first, fifth, ninth, or thirteenth aspect. Alternatively, the processor is configured to execute a program stored in memory. When the program is executed, a method according to the first, fifth, ninth, or thirteenth aspect, or any one of the possible implementations of the first, fifth, ninth, or thirteenth aspect is performed.

[0061] Referring to the 17th aspect, in possible implementations, the memory is located outside the communication device.

[0062] Referring to the 17th aspect, in possible implementations, the memory is located inside the communication device.

[0063] In this application, the processor and memory may, as an alternative, be integrated into a single device. In other words, the processor and memory may, as an alternative, be integrated together.

[0064] Referring to the 17th aspect, in possible implementations, the communication device further includes a transceiver, which is configured to transmit BTM request frames.

[0065] According to the 18th aspect, the application provides a communication device. The communication device is a non-AP MLD, and the communication device includes a processor configured to perform a method according to the second, sixth, tenth, or fourteenth aspect, or any possible implementation of the second, sixth, tenth, or fourteenth aspect. Alternatively, the processor is configured to execute a program stored in memory. When the program is executed, a method according to the second, sixth, tenth, or fourteenth aspect, or any possible implementation of the second, sixth, tenth, or fourteenth aspect is performed.

[0066] Referring to the 18th aspect, in possible implementations, the memory is located outside the communication device.

[0067] Referring to the 18th aspect, in possible implementations, the memory is located inside the communication device.

[0068] In this application, the processor and memory may, as an alternative, be integrated into a single device. In other words, the processor and memory may, as an alternative, be integrated together.

[0069] Referring to the 18th aspect, in possible implementations, the communication device further includes a transceiver, which is configured to receive BTM request frames.

[0070] According to the 19th 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 and / or output information. The logic circuit is configured to perform a method according to the first, fifth, ninth, or thirteenth aspect, or any one of the possible implementations of the first, fifth, ninth, or thirteenth aspect.

[0071] According to the 20th 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 and / or output information. The logic circuit is configured to perform a method according to the second, sixth, tenth, or fourteenth aspects, or any one of the possible implementations of the second, sixth, tenth, or fourteenth aspects.

[0072] According to the 21st 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 the first, fifth, ninth, or thirteenth aspect, or any one of the possible implementations of the first, fifth, ninth, or thirteenth aspect, can be executed.

[0073] According to the 22nd 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 the second, sixth, tenth, or fourteenth aspect, or any one of the possible implementations of the second, sixth, tenth, or fourteenth aspect, can be executed.

[0074] According to the 23rd aspect, embodiments of this application provide a computer program product, the computer program product comprising a computer program or computer code, which, when executed on a computer, enables the execution of a method according to the first, fifth, ninth, or thirteenth aspect, or any one of the possible implementations of the first, fifth, ninth, or thirteenth aspect.

[0075] According to the 24th aspect, an embodiment of the present application provides a computer program product, the computer program product comprising a computer program or computer code, which, when executed on a computer, enables the execution of a method according to the second, sixth, tenth, or fourteenth aspect, or any one of the possible implementations of the second, sixth, tenth, or fourteenth aspect.

[0076] According to the 25th aspect, an embodiment of the present application provides a computer program. When the computer program is executed on a computer, it becomes possible to execute a method according to the first, fifth, ninth, or thirteenth aspect, or any one of the possible implementations of the first, fifth, ninth, or thirteenth aspect.

[0077] According to the 26th aspect, an embodiment of the present application provides a computer program. When the computer program is executed on a computer, it becomes possible to perform a method according to the second, sixth, tenth, or fourteenth aspect, or any one of the possible implementations of the second, sixth, tenth, or fourteenth aspect.

[0078] According to the 27th aspect, an embodiment of the present application provides a communication system. The communication system includes an AP MLD and a non-AP MLD. The AP MLD is configured to perform a method according to the first, fifth, ninth, third aspect, or any possible implementation of the first, fifth, ninth, or third aspect. The non-AP MLD is configured to perform a method according to the second, sixth, tenth, or fourteenth aspect, or any possible implementation of the second, sixth, tenth, or fourteenth aspect.

[0079] The technical effects achieved by the above embodiments will be based on the technical effects in the embodiments of the following methods, or on each other. Further details will not be described again in this specification. [Brief explanation of the drawing]

[0080] [Figure 1a] This is a diagram showing the architecture of a wireless communication system according to an embodiment of this application. [Figure 1b] This is a diagram of another architecture of a wireless communication system according to an embodiment of this application. [Figure 2a]This diagram illustrates communication between a multilink device and another device according to an embodiment of this application. [Figure 2b] Another diagram illustrating communication between a multilink device and other devices according to an embodiment of this application. [Figure 3] This is a diagram illustrating an application scenario according to the embodiments of this application. [Figure 4] This is a diagram of the frame format of the action field of a BTM request frame according to an embodiment of this application. [Figure 5] This is a diagram showing the frame format of peripheral reporting elements according to an embodiment of this application. [Figure 6] This is a diagram showing the frame format of a basic multilink sub-element according to an embodiment of this application. [Figure 7] This is a diagram of the frame format of the BSS transition candidate preference sub-element according to an embodiment of this application. [Figure 8] This is a diagram of the frame format of the request mode field according to an embodiment of this application. [Figure 9] This is a first schematic flowchart of the information instruction method in BTM according to an embodiment of this application. [Figure 10] This is a second schematic flowchart of the information instruction method in BTM according to the embodiment of this application. [Figure 11] This is a diagram of another frame format for the requested mode field according to an embodiment of this application. [Figure 12] This is a third schematic flowchart of the information instruction method in BTM according to the embodiment of this application. [Figure 13] This is a fourth schematic flowchart of the information instruction method in BTM according to the embodiment of this application. [Figure 14] This is a diagram of the frame format of the BSSID information field according to an embodiment of this application. [Figure 15] This is a diagram of another frame format for BSS transition candidate preference sub-elements according to an embodiment of this application. [Figure 16] This is a fifth schematic flowchart of the information instruction method in BTM according to the embodiment of this application. [Figure 17] This is a diagram showing the frame format of the STA control field according to an embodiment of this application. [Figure 18] This is a sixth schematic flowchart of the information instruction method in BTM according to the embodiment of this application. [Figure 19] This is a diagram showing the structure of a communication device according to an embodiment of this application. [Figure 20] This is a diagram showing another structure of a communication device according to an embodiment of this application. [Figure 21] This is a diagram showing yet another structure of a communication device according to an embodiment of this application. [Modes for carrying out the invention]

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

[0082] In this description of the application, unless otherwise specified, " / " means "or". For example, A / B may mean A or B. In this specification, the term "and / or" describes only the relationship between related objects and indicates that there may be three relationships. For example, A and / or B may represent the following three cases: that only A exists, that both A and B exist, and that only B exists. Furthermore, "at least one" means one or more, and "plural" means two or more. "At least one of the following items" or a similar expression indicates any combination of these items, including either a single item or a combination of multiple items. For example, at least one of a, b or c may mean a, b, c, a and b, a and c, b and c, or a, b and c. A, b and c may be singular or plural.

[0083] In this description of the application, terms such as “first” and “second” do not limit the number or order of execution, and terms such as “first” and “second” do not indicate a clear distinction. Furthermore, the terms “includes,” “have,” and any other variation thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device comprising a series of steps or units may, at their discretion, further include steps or units not described, or at their discretion, further include other steps or units specific to the process, method, product, or device.

[0084] In this application, terms such as “example,” “for example,” etc., indicate the provision of an example, illustration, or explanation. No embodiment or design method described using “example,” “in example,” or “for example” in this application should be described as being preferable to or having more advantages than other embodiments or design methods. More precisely, the use of terms such as “example,” “in example,” or “for example” is intended to present the relevant concepts in a particular manner.

[0085] In this application, elements expressed in the singular form are intended to represent "one or more," but not "one or only one" unless otherwise specified.

[0086] The technical goal of the development and evolution of cellular networks and wireless local area networks (WLANs) is to continuously increase throughput. WLAN protocols are primarily discussed within the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards group. In previous standards such as 802.11a / b / g / n / ac / ax, throughput has been continuously improved. The next-generation standard of IEEE 802.11be is called extremely high throughput (EHT), and significantly improving peak throughput is the most important technical goal of the next-generation standard IEEE 802.11be. To achieve the technical goal of extremely high throughput, multi-link (ML) will be used as one of the key technologies in the next-generation standard of IEEE 802.11be. The main concept of the next-generation standard of IEEE 802.11 is that WLAN devices supporting the next-generation standard of IEEE 802.11 will have multi-band transmit and receive capabilities. In this way, a larger bandwidth can be used for data transmission, thereby significantly improving throughput.

[0087] Multiple frequency bands include, but are not limited to, the 2.4GHz Wi-Fi frequency band, the 5GHz Wi-Fi frequency band, and the 6GHz Wi-Fi frequency band. A single link means that access and transmission occur on each frequency band. Therefore, multi-link (ML) means that access and transmission occur on multiple frequency bands. Multi-link helps reduce latency and improve robustness.

[0088] A multilink device includes one or more interoperability stations, which may be logical stations. In embodiments of this application, “a multilink device includes interoperability stations” is also briefly described as “a multilink device includes stations.” Each interoperability station may operate on one frequency band, one channel, or one link. Interoperability stations may be APs or non-AP STAs. A multilink device in which the interoperability stations are APs may be called an AP multi-link device (AP MLD), and a multilink device in which the interoperability stations are non-AP STAs may be called a non-AP multi-link device (non-AP MLD).

[0089] During data transmission between a multilink device (e.g., AP MLD) and another multilink device (non-AP MLD), a link identifier may be used to identify a link or a station on a link. Before communication takes place, the two multilink devices (e.g., AP MLD and non-AP MLD) may first negotiate or communicate about the correspondence between the link identifier (link ID) and the link or station on the link. Alternatively, the AP MLD may indicate the correspondence between the link identifier and the link or station on the link via a broadcast management frame, such as a beacon frame. Thus, the link identifier is carried without the need to transmit a large amount of signaling information to identify the link or station on the link during data transmission. This reduces signaling overhead and improves transmission efficiency.

[0090] In possible implementations, a multilink device may implement wireless communication with other devices by complying with the 802.11 series protocols, for example, in the case of ultra-high throughput (EHT) or in the case of 802.11be or a protocol compatible with 802.11be. Obviously, the other devices may or may not be multilink devices.

[0091] The technical solutions provided in this application may be applied to WLAN systems such as Wi-Fi. For example, the methods provided in this application may be applied to IEEE 802.11 series protocols, such as next-generation Wi-Fi protocols of 802.11ax like 802.11be, Wi-Fi 7 or EHT, or next-generation protocols of 802.11be like Wi-Fi 8, ultra-high reliability (UHR), ultra-high reliability and throughput (UHRT), or Wi-Fi AI. Examples are not listed herein. The technical solutions provided in this application may be further applied to ultra-wideband (UWB) based wireless personal area network (WPAN) systems, sensing systems, etc. For example, the methods provided in this application may be applicable to IEEE 802.15.4 series protocols such as 802.15.4a, 802.15.4z, and 802.15.4ab protocols, or to next-generation UWB WPAN protocols. Examples are not listed herein. The technical solutions provided in this application may be further applied to the following communication systems, such as Internet of Things (IoT) systems, vehicle-to-everything (V2X), narrowband Internet of Things (NB-IoT) systems, the Internet of Things in the Internet of Things (IoT), devices used in Internet of Things nodes, sensors, etc., smart cameras in smart homes, smart remote controls, smart water meters and smart electricity meters, sensors in smart cities, etc.Alternatively, this application is more applicable to long-term evolution (LTE) systems, fifth-generation (5G) communication systems, and new communication systems that may emerge in future communication developments.

[0092] While this application is primarily described using a network in which IEEE 802.11 is deployed as an example, those skilled in the art will readily understand that various aspects of this application may be extended to other networks using various standards or protocols, such as high-performance radio LANs (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard and mainly used in Europe), wide area networks (WANs), wireless local area networks (WLANs), personal area networks (PANs), or other known or later developed networks.

[0093] Figure 1a is a diagram of the architecture of a wireless communication system according to an embodiment of the present application. As shown in Figure 1a, the wireless communication system includes at least two AP MLDs (e.g., AP MLD100 and AP MLD200 in Figure 1a) and at least one non-AP MLD (e.g., non-AP MLD300 in Figure 1a). Optionally, Figure 1a may further include a legacy station (e.g., single-link non-AP STA400 in Figure 1a, also called STA400) that supports transmission only over a single link. The AP MLDs are devices that provide services to the non-AP MLDs, and the non-AP MLDs may communicate with the AP MLDs over multiple links to increase throughput. The STAs within the non-AP MLDs may also communicate with the APs within the AP MLDs over the links. The example in Figure 1a where the non-AP MLD is a mobile phone and the AP MLD is a router should be understood as not indicating a limitation to the types of AP MLDs and non-AP MLDs in this application. The number of AP MLDs and non-AP MLDs in Figure 1a is merely an example, and it can be further understood that there may be more or fewer AP MLDs or non-AP MLDs in a wireless communication system. This is not limited to this application.

[0094] In embodiments of this application, the term “communication” may also be described as “data transmission,” “information transmission,” or “transmission.” The term “transmission” may generally refer to sending and receiving.

[0095] Figure 1b is a diagram of another architecture of a wireless communication system according to an embodiment of this application. As shown in Figure 1b, the AP MLD includes n stations, i.e., AP1, AP2, ..., and APn, and the non-AP MLD also includes n stations, i.e., STA1, STA2, ..., and STAn, where n is a positive integer. Communication between MLDs is multilink communication. In Figure 1b, links 1 to n form a multilink. In other words, the AP MLD and the non-AP MLD may perform parallel communication through links 1, 2, ..., and n. An AP in the AP MLD may set up a link with an STA in the non-AP MLD. For example, STA1 in the non-AP MLD sets up link 1 with AP1 in the AP MLD, STA2 in the non-AP MLD sets up link 2 with AP2 in the AP MLD, STAn in the non-AP MLD sets up link n with APn in the AP MLD, and so on. For example, the multilink device in the embodiments of this application may be a single-antenna device or a multi-antenna device. For example, the multilink device may be 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.

[0096] The frequency bands in which the multilink device operates may include, but are not limited to, sub-1GHz, 2.4GHz, 5GHz, 6GHz, and high-frequency 60GHz.

[0097] Figure 2a is a diagram illustrating communication between a multilink device and other devices according to an embodiment of this application. For example, Figure 2a shows a scenario in which AP MLD101 communicates with non-AP MLD102. AP MLD101 includes linked AP101-1 and linked AP101-2, and non-AP MLD102 includes linked STA102-1 and linked STA102-2, and AP MLD101 and non-AP MLD102 perform parallel communication through Link 1 and Link 2.

[0098] Figure 2b is another diagram illustrating communication between a multilink device and other devices according to an embodiment of this application. For example, Figure 2b 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 stations, namely STA102-1, STA102-2, and STA102-3. non-AP MLD103 includes two linked stations, namely STA103-1 and STA103-2. STA104 is a single-link device. 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, and 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 transmit uplink or downlink data to STA104 and STA102-1 in non-AP MLD102 via link 1. AP101-2, operating in the 5GHz frequency band within AP MLD101, may transmit uplink or downlink data to STA103-1, operating in the 5GHz frequency band within non-AP MLD102, via link 2, and may further transmit uplink or downlink data to 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 transmit uplink or downlink data to STA102-3, operating in the 6GHz frequency band within non-AP MLD102, via link 3, and may further transmit uplink or downlink data to STA103-2 within the non-AP MLD via link 3.

[0099] Figure 2a shows that the AP MLD supports only two frequency bands, and Figure 2b shows only an example where the AP MLD 101 supports 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 links, such as link 1, link 2, or link 3. In practical 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 2a and 2b are merely simplified diagrams and do not constitute any limitation on the scope of protection of the embodiments of this application. For descriptions of the 802.11 physical layer (PHY) and medium access control (MAC) layers in multilink devices, it may be understood that relevant standards, protocols, etc., should be referred to. Details are not shown one by one in the embodiments of this application.

[0100] For example, a multilink device (which may be referred to herein as a non-AP MLD or AP MLD) may be a device having wireless communication capabilities. The device may be an integrated device, or a chip, processing system, etc., installed on an integrated device. A device with a chip or processing system installed may implement the methods and functions provided in embodiments of this application under the control of the chip or processing system. For example, in embodiments of this application, a non-AP MLD may have wireless transceiver capabilities, support 802.11 series protocols, and communicate with an AP MLD, a single-link device, or another non-AP MLD. For example, a non-AP MLD is a user communication device that enables a user to communicate with an AP and further with a WLAN. For example, a non-AP MLD may be a user device that can connect to a network, such as a tablet computer, desktop computer, laptop computer, notebook computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), or mobile phone, an Internet of Things node in the Internet of Things, or an in-vehicle communication device in the Internet of Vehicles. Alternatively, a non-AP MLD may be a chip and processing system in the above-mentioned device. An AP MLD may be a device that provides services for a non-AP MLD and may support 802.11 series protocols. For example, an AP MLD may be a communication entity, such as a communication server, router, switch, or bridge, or an AP MLD may include various forms of macro base stations, micro base stations, relay stations, etc. Obviously, an AP MLD may be a chip and processing system in various forms of devices. Thus, the methods and functions of the embodiments of this application are realized. The 802.11 protocol may be one that supports 802.11be or a protocol compatible with 802.11be.

[0101] It can be understood that multilink devices may support high-rate and low-latency transmission. With the continued evolution of application scenarios for wireless local area networks, multilink devices may be used in more scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, or smart air detection 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 AR and VR devices), smart devices in smart offices (e.g., printers or projectors), Internet of Vehicle devices in the Internet of Vehicles, and some infrastructure in everyday life scenarios (e.g., vending machines, self-service navigation stations in supermarkets, self-service cash register devices, or self-service ordering machines). Specific forms of non-AP MLDs and AP MLDs are not limited to the embodiments of this application. The devices described above are merely examples for illustrative purposes.

[0102] The following briefly describes the application scenarios in the embodiments of this application.

[0103] The Basic Service Set (BSS) is the basic module of an IEEE 802.11 local area network and includes multiple STAs. Member STAs of different types of BSSs form different topological structures. For example, a special STA in the infrastructure BSS acts as a role for accessing distributed systems (DSs), and this STA is called an Access Point Station (AP STA), which is usually abbreviated as AP. Other STAs are called non-AP STAs, and all non-AP STAs are associated with APs to access DSs, and non-AP STAs are not connected to each other. In an independent BSS, all STAs have the same role, and STAs may be connected to each other. Local area networks use hierarchical management. Specifically, when two STAs interact with each other, data transmitted by STA1 is transmitted from BSS1 to BSS2 through the DS and finally arrives at STA2. Therefore, when accessing a local area network, STAs must belong to a BSS.

[0104] In infrastructure BSSs, in some scenarios, a non-AP STA needs to disconnect from its currently associated AP and re-associate with a new AP; that is, the non-AP STA needs to leave its current BSS and join a new BSS. Therefore, a Basic Service Set Transition Management (BSS transition management, BTM) function has been proposed and is applicable to infrastructure BSSs. If a non-AP STA supports the BTM function, it can be used to help achieve BSS transitions. For example, an AP may send a BSS transition management request (BTM request) frame to the non-AP STA to be disassociated, notifying the non-AP STA that the AP is being disassociated. Furthermore, information about APs surrounding the non-AP STA may be added to the BTM request frame to help the non-AP STA select a new BSS.

[0105] The BSS transition procedure between an AP and a non-AP STA that is not associated with any MLD is clarified in existing technical solutions. It can be understood that there are also scenarios in which a non-AP MLD needs to disassociate from the AP MLD it is currently associated with and reassociate with a new AP MLD. For example, Figure 3 illustrates an application scenario according to an embodiment of this application. As shown in Figure 3, there are four AP MLDs around a non-AP MLD, namely AP MLD1, AP MLD2, AP MLD3, and AP MLD4. Assume that the current non-AP MLD is associated with AP MLD1. However, the non-AP MLD should be disassociated from AP MLD1. Therefore, the non-AP MLD needs to select one of the remaining three AP MLDs (AP MLD2, AP MLD3, and AP MLD4) for reassociation. When a non-AP MLD makes a selection, the currently associated AP MLD1 may provide a recommendation.

[0106] This application primarily focuses on the BSS transition between non-AP MLD and AP MLD.

[0107] In possible implementations, an AP MLD may provide a non-AP MLD with information about surrounding AP MLDs via a BTM request frame and provide a recommendation level for the AP MLD. Figure 4 shows the frame format of the action field of a BTM request frame according to an embodiment of this application. The action field of the BTM request frame may be used to carry administrative information for the BTM request frame. As shown in Figure 4, the action field of the BTM request frame may include, but is not limited to, a BSS transition candidate list entries field and a request mode field. Some fields are described below in detail.

[0108] The BSS transition candidate list entries field may contain one or more neighbor report elements. Neighbor report elements may be used to describe (or carry) the priority of a target BSS candidate or a candidate target AP MLD. Typically, one neighbor report element may correspond to one target BSS candidate or one candidate target AP MLD. Different neighbor report elements may correspond to the same candidate target AP MLD or to different candidate target AP MLDs.

[0109] Figure 5 is a diagram of the frame format of a peripheral reporting element according to an embodiment of this application. As shown in Figure 5, a peripheral reporting element may include, but is not limited to, a Basic Service Set Identifier (BSS identifier, BSSID) field and an optional subelements field. The BSSID field is the MAC address of any recommended AP in the candidate target AP MLD. The optional subelements field may be used to carry information about the candidate target AP MLD and the recommendation level of the candidate target AP MLD. When a peripheral reporting element in the BSS transition candidate list entries field is used for recommendation, the optional subelements may include the following:

[0110] (1) Basic multi-link subelement corresponding to the candidate target AP MLD. Figure 6 is a diagram of the frame format of the basic multi-link subelement according to an embodiment of this application. If all the presence bitmap fields of the basic multi-link subelement shown in Figure 6 are 0 and there is no link info field, the peripheral reporting element indicates that "the candidate target AP MLD is recommended, but it is not specifically indicated which AP is recommended." If the link info field of the basic multi-link subelement shown in Figure 6 has one or more per-STA profile subelements, each per-STA profile subelement corresponds to one recommended linked AP within the candidate target AP MLD. In this case, the peripheral reporting element indicates that "the set of APs within the candidate target AP MLD is recommended."

[0111] (2) A BSS transition candidate preference subelement corresponding to a candidate target AP MLD, indicating the recommendation level of the candidate target AP MLD. For further details, please refer to the description in the standard, which is not described herein. Figure 7 is a diagram of the frame format of a BSS transition candidate preference subelement according to an embodiment of this application. As shown in Figure 7, the BSS transition candidate preference subelement may, but is not limited to, include a preference field. The length of the preference field is one octet (equal to 8 bits). When the value of the preference field is 0, the preference field indicates that the candidate target AP MLD is excluded, i.e., that the non-AP MLD is notified not to be associated with the mentioned candidate target AP MLD. When the value of the preference field is in the range of 1 to 255, the preference field indicates the recommendation level of the candidate target AP MLD. The ascending order of the values ​​indicates the ascending order of recommendation level. A value of 255 indicates "most recommended", and a value of 1 indicates "least recommended".

[0112] In short, the BSS transition candidate list entries field carries one or more peripheral reporting elements. Each peripheral reporting element corresponds to a different candidate target AP MLD or a different set of APs within the same candidate target AP MLD, and provides a recommendation value / score for the candidate target AP MLD. Furthermore, the recommendation values ​​for different sets of APs within the same candidate target AP MLD may be different. This is not discussed in this application.

[0113] Figure 8 shows a frame format of the request mode field according to an embodiment of this application. As shown in Figure 8, the request mode field includes, but is not limited to, an abridged field. The abridged (bit 1) field indicates to the recipient of the frame the intended treatment of all BSSIDs or AP MLDs not present in the BSS transition candidate list entries field. In the BSS transition candidate list entries field in this application, the BSSID may be used to identify a single link station or a legacy station, such as an AP.

[0114] For example, when the value of the abridged field is 1, the abridged field indicates that "non-existent BSSIDs or AP MLDs are excluded (from association)," meaning that non-AP MLDs are notified not to associate with BSSIDs or AP MLDs that do not exist in the BSS transition candidate list entries field. When the value of the abridged field is 0, the abridged field indicates that there is no recommendation or deprecation for association of non-AP MLDs with BSSIDs or AP MLDs that do not exist in the BSS transition candidate list entries field (the AP MLD sets the Abridged bit in the Request Mode field to 0 when the AP MLD has no recommendation for or against any BSSID or AP MLD not present in the BSS transition candidate list entries field).

[0115] In conclusion, AP MLDs currently associated with non-AP MLDs may notify the non-AP MLDs via the BSS transition candidate list entries field of the actions to be taken for AP MLDs surrounding the non-AP MLD (i.e., whether to exclude or oppose the association). Predetermined actions for BSSIDs or AP MLDs not present in the BSS transition candidate list entries field are indicated by the abridged field, and the recommendation level of candidate target AP MLDs listed in the BSS transition candidate list entries field is indicated by the preference field. However, no action is specified for APs that are within the candidate target AP MLDs listed in the BSS transition candidate list entries field but do not belong to the recommended AP set.

[0116] For example, suppose an AP MLD contains four APs, i.e., AP1 to AP4. Assume the BSSID field of the peripheral reporting element corresponding to the AP MLD is the MAC address of AP2 in the AP MLD, and the link info field has a per-STA profile subelement. The STA profile subelement corresponds to AP4 in the AP MLD. In this case, the peripheral reporting element indicates that "the AP set of APs in the AP MLD (i.e., AP2 and AP4) is recommended." In this case, the processing for AP1 and AP3 in the AP MLD is not clear.

[0117] With this in mind, embodiments of this application provide an information instruction method and apparatus in a BTM for improving information instruction and clarifying predetermined processing for APs that are not recommended within candidate target AP MLDs listed in the BSS transition candidate list entry field, thereby making it clearer to non-AP MLDs the attitude of currently associated AP MLDs and the behavior of non-AP MLDs.

[0118] The technical solutions provided in this application will be described in detail below with reference to more attached drawings.

[0119] To clearly illustrate the technical solutions of this application, this application is described by using multiple embodiments. See the description below for details. In this application, unless otherwise specified, the same or similar parts of the embodiments or implementations refer to one another. In the embodiments and implementations / methods in the embodiments of this application, unless otherwise specified or unless a logical inconsistency arises, the terminology and / or descriptions are consistent and may refer to one another between different embodiments and between implementations / methods in the embodiments. The technical features and implementations / methods in different embodiments may be combined to form new embodiments, implementations or methods based on these internal logical relationships. The following implementations of this application are not intended to limit the scope of protection of this application. It should be understood that the order of the following embodiments does not indicate importance.

[0120] Embodiment 1 Embodiment 1 of this application primarily describes a method for improving information indication by modifying the meaning of the abridged field in the request mode field.

[0121] Figure 9 is a first schematic flowchart of an information instruction method in a BTM according to an embodiment of this application. As shown in Figure 9, the information instruction method in a BTM includes, but is not limited to, the following steps.

[0122] S101: The AP MLD generates a BTM request frame, which includes a BSS transition candidate list entry field and a request mode field. The request mode field includes an abbreviation field, which indicates the processing for BSSIDs or AP MLDs that are not present in the BSS transition candidate list entry field, and the processing for APs that are not present in any of the recommended AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entry field.

[0123] S102: The AP MLD sends a BTM request frame. Correspondingly, the non-AP MLD receives a BTM request frame.

[0124] S103: The non-AP MLD parses the BTM request frame. For example, the non-AP MLD may parse the abbreviated field of the BTM request frame to obtain the processing for BSSIDs or AP MLDs that are not present in the BSS transition candidate list entry field, and the processing for APs that are not present in any of the recommended AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entry field.

[0125] In possible implementations, the format of the action field in the BTM request frame may be as shown in Figure 4. Further details are not provided herein. The action field in the BTM request frame may include, but are not limited to, a BSS transition candidate list entries field and a request mode field. The BSS transition candidate list entries field may include one or more peripheral reporting elements, which may be used to describe (or carry) the priority of the target BSS candidate or the priority of the candidate target AP MLD. Different peripheral reporting elements may correspond to different sets of APs of the same candidate target AP MLD. Obviously, different peripheral reporting elements may, alternatively, correspond to different target BSS candidates or candidate target AP MLDs. The frame format for each peripheral reporting element may be as shown in Figure 5. Further details are not provided herein.

[0126] The frame format of the request mode field may be as shown in Figure 8. Further details will not be described again herein. The request mode field includes an abridged field. The abridged field may indicate the processing for (all) BSSIDs or (all) AP MLDs that are not present in the BSS transition candidate list entries field, and the processing for APs that are not present in any of the recommended AP sets within the (all) candidate target AP MLDs listed in the BSS transition candidate list entries field. Alternatively, the abridged field may indicate the processing for (all) BSSIDs or (all) AP MLDs that are not present in the BSS transition candidate list entries field, and the processing for APs that are not present in the AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entries field.

[0127] In this application, "(all) BSSIDs" may represent two meanings: BSSID and all BSSIDs. Similarly, "(all) AP MLDs" may represent AP MLDs and all AP MLDs. In the following description, the same expression has the same meaning. Further details will not be explained again.

[0128] In possible implementations, the length of the abridged field is 1 bit. When the abridged field is a first value, the abridged field indicates that the sender of the BTM request frame has no recommendation or deprecation for an association of the BTM request frame recipient with an AP that is not present in any of the recommended AP sets within the candidate target AP MLDs present in the BSS transition candidate list entries field. When the abridged field is a second value, the abridged field indicates that the sender of the BTM request frame rejects or excludes an association of the BTM request frame recipient with an AP that is not present in any of the recommended AP sets within the candidate target AP MLDs present in the BSS transition candidate list entries field. The first value may be 0, and the second value may be 1. Obviously, the first value may be 1 as an alternative, and the second value may be 0. This is not limited to this embodiment of the application.

[0129] If the presence bitmap field of the basic multilink sub-element of an peripheral reporting element is all 0 and the link info field is absent, it can be understood that this indicates all affiliated APs of the candidate target AP MLD corresponding to the peripheral reporting element are recommended.

[0130] It can be further understood that "all AP MLDs that are not present in the BSS transition candidate list entries field" does not include AP MLDs that send BTM request frames. The application scenario shown in Figure 3 is used as an example. Assume that the current non-AP MLD is associated with AP MLD1, and AP MLD1 has discovered that the non-AP MLD needs to perform a BSS transition, or that the non-AP MLD has discovered that it needs to perform a BSS transition. AP MLD1 sends a BTM request frame to the non-AP MLD carrying information about AP MLD2, AP MLD3, and AP MLD4 and their recommendation levels. In this case, "all AP MLDs that are not present in the BSS transition candidate list entries field" refers to other AP MLDs in the network other than AP MLD1, AP MLD2, AP MLD3, and AP MLD4. Assume that AP MLD2 has three APs, namely AP2-1, AP2-2, and AP2-3; AP MLD3 has two APs, namely AP3-1 and AP3-2; and AP MLD4 has two APs, namely AP4-1 and AP4-2. Furthermore, assume that the BSS transition candidate list entries field contains a total of four peripheral reporting elements. Peripheral reporting element 1 recommends the set of AP2-1 and AP2-2 of AP MLD2. Peripheral reporting element 2 recommends the set of AP2-2 and AP2-3 of AP MLD2. Peripheral reporting element 3 recommends AP MLD3 (i.e., recommends all of AP MLD3's linked APs). Peripheral reporting element 4 recommends AP4-2 of AP MLD4 (the BSSID field is the MAC address of AP4-2, the presence bitmap field is not all 0s, and the link info field does not exist). In this case, "an AP that is not present in any of the recommended AP sets within the candidate target AP MLD listed in the BSS transition candidate list entries field" may include AP4-1.Optionally, for the recommended AP set {AP2-1, AP2-2}, the processing for AP2-3 may be the default, for example, by default, the association with AP2-3 is opposed. For the recommended AP set {AP2-2, AP2-3}, the processing for AP2-1 may be the default, for example, by default, the association with AP2-1 is opposed. In other words, for each recommended AP set, the processing for APs that are not in the recommended AP set but exist in other AP sets within the same AP MLD may be the default rule.

[0131] In other possible implementations, when the abridged field is a first value, the abridged field indicates that the sender of the BTM request frame has no recommendation or deprecation for an association of the BTM request frame recipient with a BSSID or AP MLD that is not present in the BSS transition candidate list entries field, and with an AP that is not present in the AP set within the candidate target AP MLD present in the BSS transition candidate list entries field. When the abridged field is a second value, the abridged field indicates that the sender of the BTM request frame opposes or excludes an association of the BTM request frame recipient with a BSSID or AP MLD that is not present in the BSS transition candidate list entries field, and with an AP that is not present in the AP set within the candidate target AP MLD present in the BSS transition candidate list entries field. The first value may be 0, and the second value may be 1. Obviously, the first value may be 1 as an alternative, and the second value may be 0. This is not limited to this embodiment of the application.

[0132] The application scenario shown in Figure 3 is used as an example. Assume that the current non-AP MLD is associated with AP MLD1, and AP MLD1 has discovered that the non-AP MLD needs to perform a BSS transition, or that the non-AP MLD has discovered that it needs to perform a BSS transition. AP MLD1 sends a BTM request frame to the non-AP MLD carrying information about AP MLD2 and their recommendation levels. Assume that AP MLD2 has three APs, namely AP2-1, AP2-2, and AP2-3. Furthermore, assume that the BSS transition candidate list entries field contains two peripheral reporting elements. Peripheral reporting element 1 recommends the set of AP2-1 and AP2-2 from AP MLD2. Peripheral reporting element 2 recommends the set of AP2-2 and AP2-3 from AP MLD2. For the recommended AP set {AP2-1, AP2-2}, AP2-3 is not in this set. In this case, when the value of the abridged field is 1, the abridged field excludes associations with BSSIDs or AP MLDs that do not exist in the BSS transition candidate list entries field, and excludes associations with AP2-3 if the non-AP MLD selects the AP set {AP2-1, AP2-2}. When the value of the abridged field is 0, the abridged field has no recommendations or deprecations for associations with BSSIDs or AP MLDs that do not exist in the BSS transition candidate list entries field, and has no recommendations or deprecations for associations with AP2-3 if the non-AP MLD selects the AP set {AP2-1, AP2-2}. For the recommended AP set {AP2-2, AP2-3}, AP2-1 is not in this set.In this case, when the value of the abridged field is 1, the abridged field excludes associations with BSSIDs or AP MLDs that do not exist in the BSS transition candidate list entries field, and excludes the association with AP2-1 if the non-AP MLD selects the AP set {AP2-2, AP2-3}. When the value of the abridged field is 0, the abridged field has no recommendations or deprecations for associations with BSSIDs or AP MLDs that do not exist in the BSS transition candidate list entries field, and has no recommendations or deprecations for associations with AP2-1 if the non-AP MLD selects the AP set {AP2-2, AP2-3}.

[0133] In possible implementations, the BSS transition candidate preference subelement of the BSS transition candidate list entries field includes a preference field. For example, existing meanings may continue to be used as the meaning of the preference field, or the meaning of the preference field may change with the evolution of the standard. This is not limited to the embodiments of this application. Alternatively, the preference field may indicate the degree of recommendation of an AP set. The AP set may also be an AP set recommended by the peripheral reporting element to which the preference field belongs. In other words, the AP set is a recommended AP set within the candidate target AP MLD described in the BSS transition candidate list entries field.

[0134] In this embodiment of the application, the meaning of the abridged field is extended to indicate both processing for BSSIDs or AP MLDs that are not present in the BSS transition candidate list entries field and processing for APs that are not present in the candidate target AP MLDs listed in the BSS transition candidate list entries field. This improves information indication and clarifies processing for APs within MLDs, resulting in greater clarity for non-AP MLDs regarding the attitude of currently associated AP MLDs and the behavior of non-AP MLDs. Furthermore, the meaning of this embodiment of the application is clear, there is no increased overhead, and compatibility is good.

[0135] Furthermore, in this embodiment of the application, the meaning of the preference field may be further modified so that the peripheral reporting element can indicate the degree of recommendation of the AP set in the AP MLD when recommending the set.

[0136] Embodiment 2 Embodiment 2 of this application primarily describes a method for improving information indication by using reserved bits in the request mode field.

[0137] Figure 10 is a second schematic flowchart of the information instruction method in BTM according to an embodiment of this application. As shown in Figure 10, the information instruction method in BTM includes, but is not limited to, the following steps.

[0138] S201: The AP MLD generates a BTM request frame, which includes a BSS transition candidate list entry field and a request mode field, the request mode field includes a shortened extension field, and the shortened extension field indicates the processing for APs that are not present in any of the recommended AP sets in the candidate target AP MLD listed in the BSS transition candidate list entry field.

[0139] S202: The AP MLD sends a BTM request frame. Correspondingly, the non-AP MLD receives a BTM request frame.

[0140] S203: The non-AP MLD parses the BTM request frame. For example, the non-AP MLD may parse the abbreviated extension field of the BTM request frame to obtain processing for APs that are not present in any of the recommended AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entry field. Furthermore, the non-AP MLD may parse the abbreviated extension field of the BTM request frame to obtain predetermined processing for BSSIDs or AP MLDs that are not present in the BSS transition candidate list entry field.

[0141] In possible implementations, the format of the action field in the BTM request frame may be as shown in Figure 4. Further details are not provided herein. The action field in the BTM request frame may include, but are not limited to, a BSS transition candidate list entries field and a request mode field. The BSS transition candidate list entries field may include one or more peripheral reporting elements, which may be used to describe (or carry) the priority of the target BSS candidate or the priority of the candidate target AP MLD. Different peripheral reporting elements may correspond to different sets of APs of the same candidate target AP MLD. Obviously, different peripheral reporting elements may, alternatively, correspond to different target BSS candidates or candidate target AP MLDs. The frame format for each peripheral reporting element may be as shown in Figure 5. Further details are not provided herein.

[0142] The request mode field may include an abridged field and an abridged extension field. The abridged field may indicate to the recipient of the BTM request frame the intended treatment of all BSSIDs or AP MLDs not present in the BSS transition candidate list entries field. The abridged extension field may indicate to the recipient of the BTM request frame the treatment for APs that are not present in any of the recommended AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entries field. Alternatively, the abridged extension field may indicate to the recipient of the BTM request frame the treatment for APs that are not present in any of the AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entries field.

[0143] For specific meanings of "(all) AP MLDs that do not exist in the BSS transition candidate list entries field," "APs that do not exist in any of the recommended AP sets within the (all) candidate target AP MLDs listed in the BSS transition candidate list entries field," and "processing for APs that do not exist in the AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entries field," please refer to the description of Embodiment 1 above. Further details will not be explained again in this specification.

[0144] It can be understood that the “abridged extension field” in embodiments of this application may have alternative names, such as “extension abridged field” or the first field. This is not limited to these embodiments of this application.

[0145] For example, Figure 11 illustrates another frame format of the request mode field according to an embodiment of this application. As shown in Figure 11, one reserved bit in the request mode field may be used as an abridged extension field. When the abridged extension field is a third value, it indicates that the sender of the BTM request frame has no recommendation or deprecation for an association of the BTM request frame recipient with an AP that is not present in any of the recommended AP sets in the candidate target AP MLD present in the BSS transition candidate list entries field. When the abridged extension field is a fourth value, it indicates that the sender of the BTM request frame rejects or excludes an association of the BTM request frame recipient with an AP that is not present in any of the recommended AP sets in the candidate target AP MLD present in the BSS transition candidate list entries field. Alternatively, when the abridged extension field has a third value, it indicates that the sender of the BTM request frame has no recommendation or deprecation for the recipient of the BTM request frame's association with APs that are not present in the AP set when the recipient selects an AP set in the candidate target AP MLD present in the BSS transition candidate list entries field. When the abridged extension field has a fourth value, it indicates that the sender of the BTM request frame opposes or excludes the recipient of the BTM request frame's association with APs that are not present in the AP set when the recipient selects an AP set in the candidate target AP MLD present in the BSS transition candidate list entries field.

[0146] The third value may be 0 or 1. Correspondingly, the fourth value may be 1 or 0. This is not limited to this embodiment of the application.

[0147] It can be understood that the value and meaning of the abridged field in the request mode field shown in Figure 11 may remain unchanged. When the abridged field has a first value (e.g., 0), it indicates that the sender of the BTM request frame has no recommendation or deprecation for the association of the BTM request frame's recipient with a BSSID or AP MLD that is not present in the BSS transition candidate list entries field. When the abridged field has a second value (e.g., 1), it indicates that the sender of the BTM request frame opposes or excludes the association of the BTM request frame's recipient with a BSSID or AP MLD that is not present in the BSS transition candidate list entries field.

[0148] It can be further understood that the length of the shortened extension field in Figure 11 may be one or more bits. This is not limited to the embodiments of this application.

[0149] In this embodiment of the application, the reserved bit in the request mode field indicates processing for APs that are not present in the candidate target AP MLDs listed in the BSS transition candidate list entries field. This improves informational indication, making it clearer to non-AP MLDs the attitude of the currently associated AP MLDs and the behavior of the non-AP MLDs. Furthermore, in this embodiment of the application, the meaning of the abridged field is not changed, but additional bits are used for supplementary explanation. The logic is clear, which facilitates understanding of non-AP MLDs. Moreover, the logic is clean, with the added bits and the existing abridged field existing simultaneously.

[0150] Embodiment 3 Embodiment 3 of this application primarily describes how to modify the meaning of an abridged field so that the abridged field may indicate processing for a set of APs that are not recommended within the AP MLD present in the BSS transition candidate list entry field.

[0151] Figure 12 is a third schematic flowchart of the information instruction method in BTM according to an embodiment of this application. As shown in Figure 12, the information instruction method in BTM includes, but is not limited to, the following steps.

[0152] S301: The AP MLD generates a BTM request frame, which includes a BSS transition candidate list entry field and a request mode field, the request mode field includes an abbreviation field, the abbreviation field indicating the processing for BSSIDs or AP MLDs that are not present in the BSS transition candidate list entry field and the processing for AP sets that are not recommended within the candidate target AP MLDs listed in the BSS transition candidate list entry field.

[0153] S302: An AP MLD sends a BTM request frame. A non-AP MLD receives a BTM request frame in response.

[0154] S303: The non-AP MLD parses the BTM request frame. For example, the non-AP MLD may parse the abbreviated field of the BTM request frame to obtain the processing for BSSIDs or AP MLDs that are not present in the BSS transition candidate list entry field, and the processing for AP sets that are not recommended within the candidate target AP MLDs listed in the BSS transition candidate list entry field.

[0155] In possible implementations, the format of the action field in the BTM request frame may be as shown in Figure 4. Further details are not provided herein. The action field in the BTM request frame may include, but are not limited to, a BSS transition candidate list entries field and a request mode field. The BSS transition candidate list entries field may include one or more peripheral reporting elements, which may be used to describe (or carry) the priority of the target BSS candidate or the priority of the candidate target AP MLD. Different peripheral reporting elements may correspond to different sets of APs of the same candidate target AP MLD. Obviously, different peripheral reporting elements may, alternatively, correspond to different target BSS candidates or candidate target AP MLDs. The frame format for each peripheral reporting element may be as shown in Figure 5. Further details are not provided herein.

[0156] The frame format of the request mode field may be as shown in Figure 8. Further details will not be described again herein. The request mode field includes an abridged field. The abridged field may indicate the processing for (all) BSSIDs or (all) AP MLDs that are not present in the BSS transition candidate list entries field, and the processing for AP sets that are not recommended within (all) candidate target AP MLDs listed in the BSS transition candidate list entries field.

[0157] For a specific meaning of "all AP MLDs that do not exist in the BSS transition candidate list entries field," please refer to the description of Embodiment 1 above. Further details will not be provided herein.

[0158] However, the meaning of "a set of APs that are not recommended within (all) candidate target AP MLDs listed in the BSS transition candidate list entries field" can be illustrated by using an example. An "AP set" may contain one or more APs. In other words, a single AP may be used as an AP set, and all APs that work with a single AP MLD may also be used as an AP set. The application scenario shown in Figure 3 is used as an example. Assume that the current non-AP MLD is associated with AP MLD1, and AP MLD1 has discovered that the non-AP MLD needs to perform a BSS transition, or that the non-AP MLD has discovered that it needs to perform a BSS transition. AP MLD1 sends a BTM request frame to the non-AP MLD carrying information about AP MLD2, AP MLD3, and AP MLD4 and their recommendation levels. Assume that AP MLD2 has three APs, namely AP2-1, AP2-2, and AP2-3; AP MLD3 has two APs, namely AP3-1 and AP3-2; and AP MLD4 has two APs, namely AP4-1 and AP4-2. Furthermore, assume that the BSS transition candidate list entries field contains a total of three peripheral reporting elements. Peripheral reporting element 1 recommends the set of AP2-1 and AP2-2 from AP MLD2. Peripheral reporting element 2 recommends AP MLD3 (i.e., recommends all linked APs from AP MLD3). Peripheral reporting element 3 recommends AP4-2 from AP MLD4. In this case, the "AP sets not recommended within the candidate target AP MLD (all) listed in the BSS transition candidate list entries field" include {AP2-1,AP2-3}, {AP2-2,AP2-3}, {AP2-1,AP2-2,AP2-3}, {AP2-1}, {AP2-2}, {AP2-3}, {AP3-1}, {AP3-2}, {AP4-1}, and {AP4-1,AP4-2}. Clearly, the "AP set" may include two or more APs as alternatives.This is not limited to the embodiments of this application.

[0159] In possible implementations, the length of the abridged field is 1 bit. When the abridged field has a first value, it indicates that the sender of the BTM request frame has no recommendation or deprecation for the BTM request frame recipient's association with BSSIDs or AP MLDs that are not present in the BSS transition candidate list entries field, and with AP sets that are not recommended within the candidate target AP MLDs present in the BSS transition candidate list entries field. When the abridged field has a second value, it indicates that the sender of the BTM request frame opposes or excludes the BTM request frame recipient's association with BSSIDs or AP MLDs that are not present in the BSS transition candidate list entries field, and with AP sets that are not recommended within the candidate target AP MLDs present in the BSS transition candidate list entries field.

[0160] The first value may be 0, and the second value may be 1. Clearly, the first value may be 1 as an alternative, and the second value may be 0. This is not limited to this embodiment of the application.

[0161] In possible implementations, the BSS transition candidate preference subelement of the BSS transition candidate list entries field includes a preference field. For example, existing meanings may continue to be used as the meaning of the preference field, or the meaning of the preference field may change with the evolution of the standard. This is not limited to the embodiments of this application. Alternatively, the preference field may indicate the degree of recommendation of an AP set. The AP set may also be an AP set recommended by the peripheral reporting element to which the preference field belongs. In other words, the AP set is a recommended AP set within the candidate target AP MLD described in the BSS transition candidate list entries field.

[0162] In this embodiment of the application, the meaning of the abridged field is extended to indicate both processing for BSSIDs or AP MLDs that are not present in the BSS transition candidate list entries field and processing for AP sets that are not recommended within the candidate target AP MLDs listed in the BSS transition candidate list entries field. This improves informational indication, and as a result, non-AP MLDs are more clearly informed about the attitude of the currently associated AP MLDs and the behavior of the non-AP MLDs. Furthermore, the meaning of this embodiment of the application is clear, there is no increased overhead, and compatibility is good.

[0163] Furthermore, in this embodiment of the application, the meaning of the preference field may be further modified so that the peripheral reporting element can indicate the degree of recommendation of the AP set in the AP MLD when recommending the set.

[0164] Embodiment 4 Embodiment 4 of this application primarily describes a method for improving information indication by using bits within peripheral reporting elements.

[0165] Figure 13 is a fourth schematic flowchart of the information instruction method in BTM according to an embodiment of this application. As shown in Figure 13, the information instruction method in BTM includes, but is not limited to, the following steps.

[0166] S401: The AP MLD generates a BTM request frame, the BTM request frame includes one or more peripheral report elements, one peripheral report element is used to carry information about one candidate target AP MLD, the peripheral report element includes second instruction information, the second instruction information indicates processing for APs that are not present in the set of APs in the candidate target AP MLD carried by the peripheral report element to which the second instruction information belongs.

[0167] S402: The AP MLD sends a BTM request frame. Correspondingly, the non-AP MLD receives a BTM request frame.

[0168] S403: The non-AP MLD parses the BTM request frame. For example, the non-AP MLD may parse the second instruction information within the BTM request frame to obtain processing for APs that are not present in the set of APs in the candidate target AP MLD carried by the peripheral reporting element to which the second instruction information belongs.

[0169] In possible implementations, the format of the action field in the BTM request frame may be as shown in Figure 4. Further details are not provided herein. The action field in the BTM request frame may include, but is not limited to, a BSS transition candidate list entries field. The BSS transition candidate list entries field may include one or more peripheral reporting elements, one of which may be used to describe (or carry) the priority of one target BSS candidate or one candidate target AP MLD. Different peripheral reporting elements may be used to describe (or carry) the priority of the same candidate target AP MLD. Obviously, different peripheral reporting elements may, alternatively, be used to describe (or carry) the priority of different target BSS candidates or different candidate target AP MLDs. The frame format for each peripheral reporting element may be as shown in Figure 5. Further details are not provided herein.

[0170] In possible implementations, each peripheral reporting element may include one second directive, which may indicate processing for APs that are not present in the AP set within the candidate target AP MLD carried by the peripheral reporting element to which the second directive belongs. Since one peripheral reporting element corresponds to one candidate target AP MLD, the second directive may be concisely described as indicating processing for APs that are not present in the AP set within the candidate target AP MLD. It can be understood that an "AP set" may include one or more APs. In other words, a single AP may be used as an AP set, and all APs interacting with a single AP MLD may also be used as an AP set.

[0171] The application scenario shown in Figure 3 is used as an example. Assume that the current non-AP MLD is associated with AP MLD1, and AP MLD1 has discovered that the non-AP MLD needs to perform a BSS transition, or that the non-AP MLD has discovered that it needs to perform a BSS transition. AP MLD1 sends a BTM request frame to the non-AP MLD that carries information about AP MLD2 and their recommendation levels. Assume that AP MLD2 has three APs, namely AP2-1, AP2-2, and AP2-3, and that the BSS transition candidate list entries field contains one peripheral reporting element, and the BSSID field of the peripheral reporting element is the MAC address of AP2-1 of AP MLD2. The link info field has one per-STA profile subelement, and the per-STA profile subelement corresponds to AP2-2 of AP MLD2. In this case, the peripheral reporting element indicates that the set of AP2-1 and AP2-2 of AP MLD2 is recommended. In this case, the second instruction information within the peripheral reporting element indicates processing for AP2-3, which is not present in the set of AP2-1 and AP2-2 of AP MLD2 being carried by the peripheral reporting element.

[0172] In possible implementations, when the second instruction is a first value, the second instruction indicates that the sender of the BTM request frame does not recommend or discourage an association of the recipient of the BTM request frame with an AP that is not present in the set of APs in the candidate target AP MLD carried in the peripheral reporting element to which the second instruction belongs. When the second instruction is a second value, the second instruction indicates that the sender of the BTM request frame opposes or excludes an association of the recipient of the BTM request frame with an AP that is not present in the set of APs in the candidate target AP MLD carried in the peripheral reporting element to which the second instruction belongs. The first value may be 1 or 0. Correspondingly, the second value may be 0 or 1. This is not limited to this embodiment of the application.

[0173] In possible implementations, the second instruction information may be carried in the BSSID information field of the peripheral reporting element. For example, the second instruction information may be represented by using a reserved bit in the BSSID information field. Alternatively, the extremely high throughput bit in the BSSID information field may be reused to indicate processing for APs that are not present in the set of APs in the candidate target AP MLD carried in the peripheral reporting element. Figure 14 is a diagram of the frame format of the BSSID information field according to an embodiment of this application. As shown in Figure 14, one reserved bit in the BSSID information field may be used as the second instruction information. When the value of the second instruction information is 1, the second instruction information indicates that the sender of the BTM request frame opposes or excludes the association of the recipient of the BTM request frame with APs that are not present in the set of APs in the candidate target AP MLD carried in the peripheral reporting element to which the second instruction information belongs. When the value of the second instruction is 0, the second instruction indicates that the sender of the BTM request frame does not have a recommendation or deprecation for the recipient of the BTM request frame to associate with an AP that is not present in the set of APs in the candidate target AP MLD carried in the peripheral reporting element to which the second instruction belongs.

[0174] It should be understood that Figure 14 is merely an example. In the embodiments of this application, the bit length of the second instruction information is not limited, nor is the correspondence between the value and meaning of the second instruction information.

[0175] In this embodiment of the application, one reserved bit is used in the BSSID information field of the peripheral reporting element to indicate processing for APs that are not present in the set of APs in the candidate target AP MLD carried by the peripheral reporting element. Processing may exist for each recommended set of APs in the candidate target AP MLD, which is flexible for use.

[0176] In other possible implementations, the second instruction information may be carried in a BSS transition candidate preference sub-element of a peripheral reporting element. For example, since existing BSS transition candidate preference sub-elements are not extensible, the length of the preference field may be shortened so that the length of the preference field is 7 bits or less, but the meaning of the preference field does not change. The one or more bits saved by shortening the preference field represent the second instruction information. In other words, the preference field of the BSS transition candidate preference sub-element is 7 bits or less, the bit length of the second instruction information is 1 bit or more, and the sum of the length of the preference field and the bit length of the second instruction information is 1 octet (8 bits) or less. In embodiments of this application, it can be understood that the meaning of the preference field is not limited, and only the length of the preference field is changed. The meaning of the preference field may change with the evolution of the standard.

[0177] Figure 15 shows another frame format of the BSS transition candidate preference sub-element according to an embodiment of this application. As shown in Figure 15, the length of the preference field may be shortened from one octet (8 bits in total) to seven bits, with one saved bit used as second indication information. For example, the least significant bit (LSB) in the octet (B0-B7), i.e., B0, may be used as the second indication information. When the value of the second indication information (e.g., B0) is 0, the second indication information indicates that the sender of the BTM request frame opposes or excludes the receiver of the BTM request frame's association with APs that are not present in the set of APs in the candidate target AP MLD carried in the peripheral reporting element to which the second indication information belongs. When the value of the second instruction information (e.g., B0) is 1, the second instruction information indicates that the sender of the BTM request frame does not have a recommendation or deprecation for the recipient of the BTM request frame to associate with an AP that is not present in the set of APs in the candidate target AP MLD carried in the peripheral reporting element to which the second instruction information belongs. In this way, it can be more compatible with conventional stations (i.e., single-link stations).

[0178] It should be understood that Figure 15 is merely an example. In the embodiments of this application, the bit length of the second instruction information is not limited, nor is the correspondence between the value and meaning of the second instruction information.

[0179] In this embodiment of the application, the second instruction information is carried in the BSS transition candidate preference sub-element of the peripheral reporting element to indicate processing for APs that are not present in the set of APs in the candidate target AP MLD carried by the peripheral reporting element. Processing can exist for each recommended set of APs in the candidate target AP MLD, which is flexible for use. Furthermore, the second instruction information and preference values ​​are used simultaneously, i.e., the second instruction information is absent when the peripheral reporting element is not used for recommendation.

[0180] In possible implementations, the BSS transition candidate preference sub-element of the peripheral reporting element includes a preference field. For the meaning of the preference field, refer to the relevant explanation in Embodiment 1 above. Further details are not described herein.

[0181] In this embodiment of the application, the second instruction information is carried in a peripheral reporting element to indicate processing for APs that are not present in the AP set within a single candidate target AP MLD, thereby allowing processing for each recommended AP set to exist, which is flexible for use.

[0182] Embodiment 5 Embodiment 5 of this application primarily describes a method for improving information instructions by redefining the recommended AP set in the link information field.

[0183] Figure 16 is a fifth schematic flowchart of the information instruction method in BTM according to an embodiment of this application. As shown in Figure 16, the information instruction method in BTM includes, but is not limited to, the following steps.

[0184] S501: The AP MLD generates a BTM request frame, the BTM request frame containing one or more peripheral reporting elements, one peripheral reporting element used to carry information about one candidate target AP MLD, the peripheral reporting element containing an STA per profile sub-element of any AP not excluded in the candidate target AP MLD. Optionally, the STA per profile sub-element may further contain a third instruction information, the third instruction information may indicate processing for the AP corresponding to the STA per profile sub-element.

[0185] S502: The AP MLD sends a BTM request frame. In response, the non-AP MLD receives a BTM request frame.

[0186] S503: The non-AP MLD analyzes the BTM request frame. For example, the non-AP MLD may obtain information about APs that are not excluded in the candidate target AP MLD by analyzing the peripheral reporting elements of the BTM request frame. Furthermore, the non-AP MLD may obtain processing for APs corresponding to the STA-specific profile sub-elements by analyzing the STA-specific profile sub-elements of the peripheral reporting elements.

[0187] In possible implementations, the format of the action field in the BTM request frame may be as shown in Figure 4. Further details are not provided herein. The action field in the BTM request frame may include, but is not limited to, a BSS transition candidate list entries field. The BSS transition candidate list entries field may include one or more peripheral reporting elements, one of which may be used to describe (or carry) the priority of one target BSS candidate or one candidate target AP MLD. Different peripheral reporting elements may be used to describe (or carry) the priority of the same candidate target AP MLD. Obviously, different peripheral reporting elements may, alternatively, be used to describe (or carry) the priority of different target BSS candidates or different candidate target AP MLDs. The frame format for each peripheral reporting element may be as shown in Figure 5. Further details are not provided herein.

[0188] A single peripheral reporting element may include a basic multi-link subelement corresponding to a single candidate target AP MLD. The frame format of the basic multi-link subelement may be as shown in Figure 6. Further details will not be described herein. If an AP MLD needs to recommend a set of APs from a candidate target AP MLD to a non-AP MLD, it can be understood that a peripheral reporting element for any AP in the AP set needs to be added to the BSS transition candidate list entries field (i.e., the BSSID field of the peripheral reporting element is the MAC address of any AP in the AP set). Furthermore, the basic multi-link subelement should be added to the peripheral reporting element, and the per-STA profile subelements of other APs in the AP set should be added to the link info field of the basic multi-link subelement. In short, the link info field carries the per-STA profile subelements of APs other than those in the recommended AP set that are indicated by the BSSID field.

[0189] In this embodiment of the application, if an AP MLD needs to recommend a set of APs in a candidate target AP MLD to a non-AP MLD, the BSSID field of the peripheral reporting element is still the MAC address of any AP in the set of APs. However, the link info field of the basic multi-link subelement includes a per-STA profile subelement of any AP that is in the candidate target AP MLD and is not excluded (from the association). Optionally, each per-STA profile subelement further includes a third directive information, which may indicate processing for the AP corresponding to the per-STA profile subelement. One per-STA profile subelement corresponds to one AP that is not excluded in the candidate target AP MLD, where “not excluded” may include at least two meanings: “recommended” and “not recommended or not recommended.” In this embodiment of the application, it is further considered by default that APs that are not present in the peripheral reporting element are excluded from the association. Here, "APs not present in the surrounding reporting elements" may refer to APs other than those located within the candidate target AP MLD carried by the surrounding reporting elements and corresponding to the APs indicated by the BSSID field and the per-STA profile subelement.

[0190] In possible implementations, when the third instruction information within the per-STA profile subelement is a first value, the third instruction information indicates that the sender of the BTM request frame does not have a recommendation or deprecation for the association of the recipient of the BTM request frame with the AP corresponding to the per-STA profile subelement. When the third instruction information within the per-STA profile subelement is a second value, the third instruction information indicates that the sender of the BTM request frame does have a recommendation for the association of the recipient of the BTM request frame with the AP corresponding to the per-STA profile subelement. The first value may be 0 or 1. Correspondingly, the second value may be 1 or 0. This is not limited to this embodiment of the application.

[0191] In possible implementations, the third instruction information may be carried in the station control (STA control) field of the per-STA profile subelement. For example, one reserved bit in the STA control field of the per-STA profile subelement may represent the third instruction information. Figure 17 is a diagram of the frame format of the STA control field according to an embodiment of this application. For ease of explanation in Figure 17, the third instruction information is referred to as the recommended field. In practical applications, it may be understood that the third instruction information may have other field names. This is not limited to the embodiments of this application. As shown in Figure 17, the STA control field includes, but is not limited to, the recommended field. For example, the length of the recommended field is 1 bit. When the value of the recommended field is 1, the recommended field indicates that the AP MLD has a recommendation for association of a non-AP MLD with the AP corresponding to the per-STA profile subelement to which the recommended field belongs. When the value of the recommended field is 0, the recommended field indicates that the AP MLD does not recommend or discourage association of the non-AP MLD with the AP corresponding to the per-STA profile subelement to which the recommended field belongs. It should be understood that whether a value of 1 or 0 in the recommended field indicates a recommendation is not limited to this embodiment of the application. Figure 17 is merely an example, and the length of the recommended field is not limited to this embodiment of the application.

[0192] In this embodiment of the application, APs that are not present in the peripheral reporting element are excluded from the association by default, and third directive information specifies whether APs that exist and correspond to the per-STA profile subelement are recommended for the association. Since the association preference information exists in the per-STA profile subelement corresponding to each AP, there can be processing for each AP within each set of APs provided by the AP MLD, which is very flexible for use.

[0193] Embodiment 6 Embodiment 6 of this application primarily describes the default processing for APs that are not present in the candidate target AP MLD listed in the BSS transition candidate list entry field.

[0194] Figure 18 is a sixth schematic flowchart of the information instruction method in BTM according to an embodiment of this application. As shown in Figure 18, the information instruction method in BTM includes, but is not limited to, the following steps.

[0195] S601:AP MLD generates a BTM request frame.

[0196] S602: The AP MLD sends a BTM request frame. Correspondingly, the non-AP MLD receives a BTM request frame.

[0197] S603: non-AP MLD analyzes the BTM request frame.

[0198] In possible implementations, the format of the action field in the BTM request frame may be as shown in Figure 4. Further details are not provided herein. The action field in the BTM request frame may include, but is not limited to, the BSS transition candidate list entries field and the request mode field. The frame format of the request mode field may be as shown in Figure 8. Further details are not provided herein. The request mode field includes an abridged field. The abridged field may indicate processing for (all) BSSIDs or (all) AP MLDs that are not present in the BSS transition candidate list entries field. However, processing for APs that are not present in any of the recommended AP sets within the (all) candidate target AP MLDs listed in the BSS transition candidate list entries field may be a default rule.

[0199] In possible implementations, the default rule may include one of the following: excluding / opposing associations with non-recommended APs in the candidate target AP MLD present in the BSS transition candidate list entries field, and having no recommendation or deprecation for associations with non-recommended APs in the candidate target AP MLD present in the BSS transition candidate list entries field. A non-AP MLD should treat non-recommended APs in the AP MLD present in the BSS transition candidate list entries field as APs with a specific preference value, such as value 1. Here, "non-recommended AP" may mean "an AP that does not exist in any recommended AP set" or "an AP that does not exist in any recommended AP set."

[0200] In this embodiment of the application, a default process is designed for APs that are not present in the candidate target AP MLDs listed in the BSS transition candidate list entry field. This improves informational guidance, resulting in a greater clarity for non-AP MLDs regarding the attitude of the currently associated AP MLDs and the behavior of the non-AP MLDs. Furthermore, in this embodiment of the application, no fields in the BTM request frame are modified, and no overhead is increased.

[0201] The above description details the method provided in this application. To facilitate the implementation of the above solution in the embodiments of this application, embodiments of this application further provide corresponding apparatus or devices.

[0202] In this application, the functional modules of AP MLDs and non-AP MLDs are obtained through partitioning according to embodiments of the method described above. For example, functional modules may be obtained through partitioning corresponding to various functions, 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 partitioning is merely an example and represents a logical functional partitioning. Other partitioning methods may be used in actual implementations. The AP MLDs and non-AP MLDs in embodiments of this application will be described in detail below with reference to Figures 19 to 21.

[0203] Figure 19 is a diagram illustrating the structure of a communication device according to an embodiment of this application. As shown in Figure 19, the communication device includes a transceiver unit 10 and a processing unit 20. The transceiver unit 10 may implement corresponding communication functions, and the processing unit 20 is configured to perform data processing. For example, the transceiver unit 10 may also be called a communication interface or communication unit.

[0204] In some embodiments of this application, the communication device may be the AP MLD shown above. In other words, the communication device shown in Figure 19 may be configured to perform steps, functions, etc., performed by the AP MLD in embodiments of the above method. For example, the communication device may be the AP MLD, or a chip, functional module, etc., configured within the AP MLD. This is not limited to embodiments of this application. The transceiver unit 10 is configured to perform the receive / transmit related operations of the AP MLD in embodiments of the above method. The processing unit 20 is configured to perform the processing related operations of the AP MLD in embodiments of the above method.

[0205] For example, processing unit 20 is configured to generate a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field and first instruction information, the first instruction information indicating processing for BSSIDs or AP MLDs that are not present in the BSS transition candidate list entry field, and processing for APs that are not present in any of the recommended AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entry field. Transceiver unit 10 is configured to transmit or output the BTM request frame.

[0206] The transceiver unit 10 may transmit the BTM request frame to other communication devices, or it may be understood that the transceiver unit 10 outputs the BTM request frame from the processing unit 20 to other components of the AP MLD, other functional modules, etc. The relevant explanation for the transceiver unit outputting other information is similar. Further details will not be explained below.

[0207] For a specific description of the BTM request frame, the BSS transition candidate list entry field, the first instruction information, etc., it may be understood that you should refer to Embodiment 1 or 2 of the method described above. Further details will not be described again herein.

[0208] It should be understood that the specific description of the transceiver unit and processing unit in this embodiment of this application is merely illustrative. For specific functions or steps performed by the transceiver unit and processing unit, refer to Embodiment 1 or 2 of the method described above (for example, Figures 9 and 10). Further details are not described herein.

[0209] For example, processing unit 20 is configured to generate a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field and a request mode field, the request mode field includes an abbreviation field, the abbreviation field indicating processing for BSSIDs or AP MLDs not present in the BSS transition candidate list entry field and processing for AP sets not recommended within the candidate target AP MLDs listed in the BSS transition candidate list entry field. Transceiver unit 10 is configured to transmit or output the BTM request frame.

[0210] For a specific description of the BTM request frame, BSS transition candidate list entry field, request mode field, abbreviation field, etc., it may be understood that you should refer to Embodiment 3 of the method described above. Further details will not be described again in this specification.

[0211] It should be understood that the specific description of the transceiver unit and processing unit in this embodiment of this application is merely illustrative. For specific functions or steps performed by the transceiver unit and processing unit, refer to Embodiment 3 of the method described above (for example, Figure 12). Further details are not described herein.

[0212] For example, processing unit 20 is configured to generate a BTM request frame. The BTM request frame includes one or more peripheral reporting elements, one of which is used to carry information about one candidate target AP MLD, the peripheral reporting element includes second instruction information, the second instruction information indicates processing for APs that are not present in the set of APs in the candidate target AP MLD carried by the peripheral reporting element to which the second instruction information belongs. Transceiver unit 10 is configured to transmit or output the BTM request frame.

[0213] For a specific description of the BTM request frame, peripheral reporting elements, second instruction information, etc., it may be understood that you should refer to Embodiment 4 of the method described above. Further details will not be described again in this specification.

[0214] It should be understood that the specific description of the transceiver unit and processing unit in this embodiment of this application is merely illustrative. For specific functions or steps performed by the transceiver unit and processing unit, refer to Embodiment 4 of the method described above (for example, Figure 13). Further details are not described herein.

[0215] For example, processing unit 20 is configured to generate a BTM request frame. The BTM request frame includes one or more peripheral reporting elements, one of which is used to carry information about one candidate target AP MLD, and the peripheral reporting elements include per-STA profile sub-elements of any APs that are not excluded in the candidate target AP MLD. Transceiver unit 10 is configured to transmit or output the BTM request frame.

[0216] For specific descriptions of the BTM request frame, peripheral reporting elements, STA-specific profile sub-elements, etc., it may be understood that you should refer to Embodiment 5 of the method described above. Further details will not be described again in this specification.

[0217] It should be understood that the specific description of the transceiver unit and processing unit in this embodiment of this application is merely illustrative. For specific functions or steps performed by the transceiver unit and processing unit, refer to Embodiment 5 of the method described above (for example, Figure 16). Further details are not described herein.

[0218] Figure 19 is reused. In some other embodiments of this application, the communication device may be a non-AP MLD as shown above. In other words, the communication device shown in Figure 19 may be configured to perform steps, functions, etc., performed by the non-AP MLD in the embodiments of the above method. For example, the communication device may be a non-AP MLD, or a chip, functional module, etc., configured within the non-AP MLD. This is not limited to the embodiments of this application. The transceiver unit 10 is configured to perform the receive / transmit related operations of the non-AP MLD in the embodiments of the above method. The processing unit 20 is configured to perform the processing related operations of the non-AP MLD in the embodiments of the above method.

[0219] For example, the transceiver unit 10 is configured to receive or input a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field and first instruction information, the first instruction information indicating processing for BSSIDs or AP MLDs that are not present in the BSS transition candidate list entry field, and processing for APs that are not present in any of the recommended AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entry field. The processing unit 20 is configured to parse the BTM request frame.

[0220] The transceiver unit 10 may receive BTM request frames from other communication devices, or it may be understood that the transceiver unit 10 may input BTM request frames from other components or other functional modules of the AP MLD. The relevant explanation for inputting other information by the transceiver unit is similar. Further details will not be provided below.

[0221] For a specific description of the BTM request frame, the BSS transition candidate list entry field, the first instruction information, etc., it may be understood that you should refer to Embodiment 1 or 2 of the method described above. Further details will not be described again herein.

[0222] It should be understood that the specific description of the transceiver unit and processing unit in this embodiment of this application is merely illustrative. For specific functions or steps performed by the transceiver unit and processing unit, refer to Embodiment 1 or 2 of the method described above (for example, Figures 9 and 10). Further details are not described herein.

[0223] For example, transceiver unit 10 is configured to receive or input a BTM request frame. The BTM request frame includes a BSS transition candidate list entry field and a request mode field, the request mode field includes an abbreviation field, the abbreviation field indicating the processing for BSSIDs or AP MLDs not present in the BSS transition candidate list entry field and the processing for AP sets that are not recommended within the candidate target AP MLDs listed in the BSS transition candidate list entry field. Processing unit 20 is configured to parse the BTM request frame.

[0224] For a specific description of the BTM request frame, BSS transition candidate list entry field, request mode field, abbreviation field, etc., it may be understood that you should refer to Embodiment 3 of the method described above. Further details will not be described again in this specification.

[0225] It should be understood that the specific description of the transceiver unit and processing unit in this embodiment of this application is merely illustrative. For specific functions or steps performed by the transceiver unit and processing unit, refer to Embodiment 3 of the method described above (for example, Figure 12). Further details are not described herein.

[0226] For example, the transceiver unit 10 is configured to receive or input a BTM request frame. The BTM request frame includes one or more peripheral reporting elements, one of which is used to carry information about one candidate target AP MLD, the peripheral reporting element includes second instruction information, the second instruction information indicates processing for APs that are not present in the set of APs within the candidate target AP MLD carried by the peripheral reporting element to which the second instruction information belongs. The processing unit 20 is configured to parse the BTM request frame.

[0227] For a specific description of the BTM request frame, peripheral reporting elements, second instruction information, etc., it may be understood that you should refer to Embodiment 4 of the method described above. Further details will not be described again in this specification.

[0228] It should be understood that the specific description of the transceiver unit and processing unit in this embodiment of this application is merely illustrative. For specific functions or steps performed by the transceiver unit and processing unit, refer to Embodiment 4 of the method described above (for example, Figure 13). Further details are not described herein.

[0229] For example, the transceiver unit 10 is configured to receive or input a BTM request frame. The BTM request frame includes one or more peripheral reporting elements, one of which is used to carry information about one candidate target AP MLD, and the peripheral reporting elements include STA-specific profile sub-elements of any AP that is not excluded in the candidate target AP MLD. The processing unit 20 is configured to parse the BTM request frame.

[0230] For specific descriptions of the BTM request frame, peripheral reporting elements, STA-specific profile sub-elements, etc., it may be understood that you should refer to Embodiment 5 of the method described above. Further details will not be described again in this specification.

[0231] It should be understood that the specific description of the transceiver unit and processing unit in this embodiment of this application is merely illustrative. For specific functions or steps performed by the transceiver unit and processing unit, refer to Embodiment 5 of the method described above (for example, Figure 16). Further details are not described herein.

[0232] The above describes non-AP MLD and AP MLD in embodiments of this application. The following describes possible product forms of non-AP MLD and AP MLD. It should be understood that any product of any form having the functionality of a non-AP MLD as shown in Figure 19, and any product of any form having the functionality of an AP MLD as shown in Figure 19, fall within the scope of protection of embodiments of this application. It should be further understood that the following description is merely an example, and the product forms of non-AP MLD and AP MLD in embodiments of this application are not limited to these.

[0233] In possible implementations, in the communication device shown in Figure 19, the processing unit 20 may be one or more processors, and the transceiver unit 10 may be a transceiver. Alternatively, the transceiver unit 10 may be a transmitting unit and a receiving unit. The transmitting unit may be a transmitter. The receiving unit may be a receiver. The transmitting unit and the receiving unit are integrated into a single device, for example, a transceiver. In embodiments of this application, the processor and the transceiver may be coupled, and the connection method between the processor and the transceiver is not limited in embodiments of this application. In the process of performing the above method, the process of transmitting information in the above method (e.g., transmitting a BTM request frame) 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 before the information arrives at the transceiver. Similarly, the process of receiving information in the above method (e.g., receiving a BTM request frame) may be understood as the process of receiving input information by the processor. When the processor receives input information, the transceiver receives the above information and inputs it to the processor. Furthermore, after the transceiver receives the above information, other processing may need to be performed on the information before it is input to the processor.

[0234] Figure 20 shows another structure of the communication device according to an embodiment of this application. The communication device may be an AP MLD or a non-AP MLD, or a chip within an AP MLD or a non-AP MLD. Figure 20 shows only the main components of the communication device. In addition to the processor 1001 and transceiver 1002, the communication device may further include a memory 1003 and a power / input / output device (not shown).

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

[0236] After the communication device is powered on, the processor 1001 may read the software program in the memory 1003, 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 1001 performs baseband processing on the data to be transmitted and 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 to the outside through the antenna in the form of electromagnetic waves. 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 1001. The processor 1001 converts the baseband signal into data and processes the data.

[0237] 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 remotely, independently of the communication equipment.

[0238] The processor 1001, transceiver 1002, and memory 1003 may be connected via a communication bus.

[0239] For example, the communication device may be configured to perform the functions of the AP MLD in Embodiment 1. The processor 1001 may be configured to perform step S101 in Figure 9, and / or to perform other processes of the technology described in this specification. The transceiver 1002 may be configured to perform step S102 in Figure 9, and / or to perform other processes of the technology described in this specification.

[0240] For example, the communication device may be configured to perform the functions of the non-AP MLD in Embodiment 1. The processor 1001 may be configured to perform step S103 in Figure 9, and / or to perform other processes of the technology described in this specification. The transceiver 1002 may be configured to receive a BTS request frame, and / or to perform other processes of the technology described in this specification.

[0241] For example, the communication device may be configured to perform the functions of AP MLD in Embodiment 2. The processor 1001 may be configured to perform step S201 in Figure 10, and / or to perform other processes of the technology described in this specification. The transceiver 1002 may be configured to perform step S202 in Figure 10, and / or to perform other processes of the technology described in this specification.

[0242] For example, the communication device may be configured to perform the functions of the non-AP MLD in Embodiment 2. The processor 1001 may be configured to perform step S203 in Figure 10, and / or to perform other processes of the technology described in this specification. The transceiver 1002 may be configured to receive a BTS request frame, and / or to perform other processes of the technology described in this specification.

[0243] For example, the communication device may be configured to perform the functions of the AP MLD in Embodiment 3. The processor 1001 may be configured to perform step S301 in Figure 12, and / or to perform other processes of the technology described in this specification. The transceiver 1002 may be configured to perform step S302 in Figure 12, and / or to perform other processes of the technology described in this specification.

[0244] For example, the communication device may be configured to perform the functions of the non-AP MLD in Embodiment 3. The processor 1001 may be configured to perform step S303 in Figure 12, and / or to perform other processes of the technology described in this specification. The transceiver 1002 may be configured to receive a BTS request frame, and / or to perform other processes of the technology described in this specification.

[0245] For example, the communication device may be configured to perform the functions of the AP MLD in Embodiment 4. The processor 1001 may be configured to perform step S401 in Figure 13, and / or to perform other processes of the technology described in this specification. The transceiver 1002 may be configured to perform step S402 in Figure 13, and / or to perform other processes of the technology described in this specification.

[0246] For example, the communication device may be configured to perform the functions of the non-AP MLD in Embodiment 3. The processor 1001 may be configured to perform step S403 in Figure 13, and / or to perform other processes of the technology described in this specification. The transceiver 1002 may be configured to receive a BTS request frame, and / or to perform other processes of the technology described in this specification.

[0247] For example, the communication device may be configured to perform the functions of the AP MLD in Embodiment 5. The processor 1001 may be configured to perform step S501 in Figure 16, and / or to perform other processes of the technology described in this specification. The transceiver 1002 may be configured to perform step S502 in Figure 16, and / or to perform other processes of the technology described in this specification.

[0248] For example, the communication device may be configured to perform the functions of the non-AP MLD in Embodiment 5. The processor 1001 may be configured to perform step S503 in Figure 16, and / or to perform other processes of the technology described in this specification. The transceiver 1002 may be configured to receive a BTS request frame, and / or to perform other processes of the technology described in this specification.

[0249] For example, the communication device may be configured to perform the functions of AP MLD in Embodiment 6. The processor 1001 may be configured to perform step S601 in Figure 18, and / or to perform other processes of the technology described in this specification. The transceiver 1002 may be configured to perform step S602 in Figure 18, and / or to perform other processes of the technology described in this specification.

[0250] For example, the communication device may be configured to perform the functions of the non-AP MLD in Embodiment 3. The processor 1001 may be configured to perform step S603 in Figure 18, and / or to perform other processes of the technology described in this specification. The transceiver 1002 may be configured to receive a BTS request frame, and / or to perform other processes of the technology described in this specification.

[0251] In this implementation, the processor 1001 may store instructions. These instructions may be computer programs. The computer programs are executed on the processor 1001, causing the communication device to perform the method described in the embodiment of the above method. The computer programs may be fixed to the processor 1001. In this case, the processor 1001 may be implemented by hardware.

[0252] In the implementation, the communication device may include a circuit. The circuit may implement the transmission, reception, or communication functions in the embodiments of the above-described method. The processor and transceiver described in this application may be implemented in an integrated circuit (IC), analog IC, radio frequency integrated circuit (RFIC), mixed-signal IC, application-specific integrated circuit (ASIC), printed circuit board (PCB), electronic device, etc. The processor and transceiver may, as an alternative, be manufactured using various IC technologies, such as complementary metal-oxide-semiconductor (CMOS), N-type metal-oxide-semiconductor (NMOS), P-type metal-oxide-semiconductor (PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), and gallium arsenide (GaAs).

[0253] It can be understood that the communication device shown in this embodiment of this application may have more components than those shown in Figure 20. This is not limited to this embodiment of this application. The above method performed by the processor and transceiver is merely an example. For specific steps performed by the processor and transceiver, refer to the description in the embodiment of the above method.

[0254] In other possible implementations, in the communication device shown in Figure 19, the processing unit 20 may be one or more logic circuits, and the transceiver unit 10 may be an input / output interface, or may be called a communication interface, interface circuit, interface, etc. Alternatively, the transceiver unit 10 may be a transmitting unit and a receiving unit. The transmitting unit may be an output interface, and the receiving unit may be an input interface. The transmitting unit and the receiving unit are integrated into a single unit, for example, an input / output interface. Figure 21 shows yet another structure of the communication device according to an embodiment of this application. As shown in Figure 21, the communication device shown in Figure 21 includes a logic circuit 901 and an interface 902. That is, the processing unit 20 may be implemented through the logic circuit 901, and the transceiver unit 10 may be implemented through the interface 902. The logic circuit 901 may be a chip, processing circuit, integrated circuit, system on chip (SoC) chip, etc. The interface 902 may be a communication interface, input / output interface, pin, etc. For example, Figure 21 shows an example where the above communication device is used as a chip. The chip includes a logic circuit 901 and an interface 902.

[0255] In this embodiment of the application, the logic circuits and interfaces may be further coupled to one another. The specific connection methods of the logic circuits and interfaces are not limited to this embodiment of the application.

[0256] In some embodiments of this application, the communication device may be configured to perform methods, steps, functions, etc., performed by AP MLD in any one of the embodiments of the above method.

[0257] For example, logic circuit 901 is configured to generate a BTM request frame. Interface 902 is configured to output a BTM request frame.

[0258] In some other embodiments of this application, the communication device may be configured to perform methods, steps, functions, etc., performed by the non-AP MLD in any one of the embodiments of the above method.

[0259] For example, interface 902 is configured to receive a BTM request frame. Logic circuit 901 is configured to analyze the BTM request frame.

[0260] For a detailed explanation of the BTM request frame and other related matters, it may be helpful to refer to the embodiments of the method described above. Further details will not be provided again in this specification.

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

[0262] For a specific implementation of the embodiment shown in Figure 21, please refer to the embodiment described above. Further details will not be explained again in this specification.

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

[0264] Furthermore, this application further provides a computer program, which is configured to perform operations and / or processes performed by a non-AP MLD in the manner provided in this application.

[0265] This application further provides a computer program, which is configured to perform operations and / or processes performed by AP MLD in the manner provided in this application.

[0266] 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 a non-AP MLD in the manner provided in this application.

[0267] 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 AP MLD in the manner provided in this application.

[0268] 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, it becomes possible to perform operations and / or processes that are performed by a non-AP MLD device in the manner provided in this application.

[0269] 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, it becomes possible to perform operations and / or processes to be performed by the AP MLD device in the manner provided in this application.

[0270] In some embodiments provided in this application, it should be understood that the disclosed systems, apparatus and methods may be implemented in other ways. For example, the embodiments of the apparatus described are merely examples. For example, the division into units is merely a logical functional division, and other divisions may be used 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 apparatus or units may be implemented in electrical, mechanical or other forms.

[0271] Units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units, may be located in one place, or may be 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.

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

[0273] When an integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored on a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application may be implemented in the form of a software product, either essentially or in part with respect to the prior art. 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, or network device) to perform all or part of the steps of the method described in the embodiments of this application. The above-mentioned computer-readable storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk, read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0274] 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 technical scope 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 method for providing information in basic service set transition management, The steps include: generating a Basic Service Set Transition Management (BTM) request frame using an Access Point Multilink Device (AP MLD), wherein the BTM request frame includes a Basic Service Set (BSS) transition candidate list entry field and first instruction information, the first instruction information indicating processing for Basic Service Set Identifiers (BSSIDs) or AP MLDs that are not present in the BSS transition candidate list entry field, and processing for APs that are not present in any of the recommended AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entry field; The AP MLD transmits the BTM request frame. A method that includes this.

2. A method for providing information in basic service set transition management, The steps include: receiving a Basic Service Set Transition Management (BTM) request frame by a non-access point multilink device (non-AP MLD), wherein the BTM request frame includes a Basic Service Set (BSS) transition candidate list entry field and first instruction information, wherein the first instruction information indicates processing for Basic Service Set Identifiers (BSSIDs) or AP MLDs that are not present in the BSS transition candidate list entry field, and processing for APs that are not present in any of the recommended AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entry field; The steps include: analyzing the BTM request frame using the non-AP MLD; A method that includes this.

3. The method according to claim 1 or 2, wherein the first instruction information is an abbreviated field.

4. The first instruction information indicates processing for a BSSID or AP MLD that does not exist in the BSS transition candidate list entry field, and processing for an AP that does not exist in any of the recommended AP sets within the candidate target AP MLDs listed in the BSS transition candidate list entry field. When the abbreviated field is a first value, the abbreviated field indicates that the AP MLD does not have a recommendation or deprecation for association with the BSSID or AP MLD that is not present in the BSS transition candidate list entry field, and with the AP that is not present in any of the recommended AP sets within the candidate target AP MLD present in the BSS transition candidate list entry field. When the abbreviated field is a second value, the abbreviated field indicates that the AP MLD excludes the association with the BSSID or AP MLD that is not present in the BSS transition candidate list entry field, and the AP that is not present in any of the recommended AP sets within the candidate target AP MLD present in the BSS transition candidate list entry field. The method according to claim 3, including the following:

5. The method according to claim 3 or 4, wherein the BSS transition candidate preference sub-element of the BSS transition candidate list entry field includes a preference field, the preference field indicating the degree of recommendation of the AP set in the candidate target AP MLD described in the BSS transition candidate list entry field.

6. The method according to claim 1 or 2, wherein the first instruction information is an abbreviated field and an abbreviated extension field, the abbreviated field indicating the processing for the BSSID or AP MLD that is not present in the BSS transition candidate list entry field, and the abbreviated extension field indicating the processing for the AP that is not present in any of the recommended AP sets in the candidate target AP MLD described in the BSS transition candidate list entry field.

7. The shortened extension field indicates the processing for the AP that does not exist in any of the recommended AP sets in the candidate target AP MLD described in the BSS transition candidate list entry field. When the abbreviated extension field is a third value, the abbreviated extension field indicates that the AP MLD does not have a recommendation or deprecation for association with the AP that is not present in any of the recommended AP sets in the candidate target AP MLD present in the BSS transition candidate list entry field. When the abbreviated extension field is a fourth value, the abbreviated extension field indicates that the AP MLD excludes the association with the AP that is not present in any of the recommended AP sets in the candidate target AP MLD present in the BSS transition candidate list entry field. The method according to claim 6, including the following:

8. A method for providing information in basic service set transition management, The step of generating a Basic Service Set Transition Management (BTM) request frame by an Access Point Multilink Device (AP MLD), wherein the BTM request frame includes a Basic Service Set (BSS) Transition Candidate List entry field and a Request Mode field, the Request Mode field includes a Shortened field, the Shortened field indicates the processing for AP sets not recommended in the Candidate Target AP MLD listed in the BSS Transition Candidate List entry field, and The AP MLD transmits the BTM request frame. A method that includes this.

9. A method for providing information in basic service set transition management, The steps include: receiving a Basic Service Set Transition Management (BTM) request frame by a non-access point multilink device (non-AP MLD), wherein the BTM request frame includes a Basic Service Set (BSS) transition candidate list entry field and a request mode field, the request mode field includes a shortened field, and the shortened field indicates processing for AP sets not recommended within the candidate target AP MLD listed in the BSS transition candidate list entry field; The steps include: analyzing the BTM request frame using the non-AP MLD; A method that includes this.

10. The abbreviated field indicates processing for a set of APs that are not recommended within the candidate target AP MLD listed in the BSS transition candidate list entry field. When the abbreviated field is a first value, the abbreviated field indicates that the AP MLD does not have a recommendation or deprecation for association with the AP set that is not recommended in the candidate target AP MLD present in the BSS transition candidate list entry field. When the abbreviated field is a second value, the abbreviated field indicates that the AP MLD excludes the association with the AP set that is not recommended in the candidate target AP MLD present in the BSS transition candidate list entry field. The method according to claim 8 or 9, including the action of:

11. The method according to any one of claims 8 to 10, wherein the abbreviated field further indicates processing for a basic service set identifier (BSSID) or AP MLD that is not present in the BSS transition candidate list entry field.

12. The abbreviated field further indicates processing for a basic service set identifier (BSSID) or AP MLD that is not present in the BSS transition candidate list entry field. When the abbreviated field is a first value, the abbreviated field indicates that the AP MLD does not have a recommendation or deprecation for an association with the BSSID or the AP MLD that is not present in the BSS transition candidate list entry field. When the abbreviated field is a second value, the abbreviated field indicates that the AP MLD excludes associations with the BSSID or the AP MLD that are not present in the BSS transition candidate list entry field. The method according to claim 11, including the following:

13. The method according to any one of claims 8 to 12, wherein the BSS transition candidate preference sub-element of the BSS transition candidate list entry field includes a preference field, and the preference field indicates the degree of recommendation of the AP set in the candidate target AP MLD described in the BSS transition candidate list entry field.

14. A method for providing information in basic service set transition management, The steps include: generating a Basic Service Set Transition Management (BTM) request frame by an Access Point Multilink Device (AP MLD), wherein the BTM request frame includes one or more peripheral reporting elements, one peripheral reporting element used to carry information about one candidate target AP MLD, the peripheral reporting element includes second instruction information, the second instruction information indicating processing for APs that are not present in the set of APs within the candidate target AP MLD carried by the peripheral reporting element to which the second instruction information belongs; The AP MLD transmits the BTM request frame. A method that includes this.

15. A method for providing information in basic service set transition management, The steps include: receiving a Basic Service Set Transition Management (BTM) request frame by a non-access point multilink device (non-AP MLD), wherein the BTM request frame includes one or more peripheral reporting elements, one peripheral reporting element used to carry information about one candidate target AP MLD, the peripheral reporting element includes second instruction information, the second instruction information indicates processing for APs that are not present in the set of APs within the candidate target AP MLD carried by the peripheral reporting element to which the second instruction information belongs; The steps include: analyzing the BTM request frame using the non-AP MLD; A method that includes this.

16. The second instruction information indicates processing for an AP that is not present in the set of APs in the candidate target AP MLD carried by the peripheral reporting element to which the second instruction information belongs. When the second instruction information is a first value, the second instruction information indicates that the AP MLD does not have a recommendation or a discouragement for association with the AP that is not present in the AP set in the candidate target AP MLD carried by the peripheral reporting element to which the second instruction information belongs. When the second instruction information is a second value, the second instruction information indicates that the AP MLD excludes the association with APs that are not present in the set of APs in the candidate target AP MLD carried by the peripheral reporting element to which the second instruction information belongs. The method according to claim 14 or 15, including the action of:

17. The method according to any one of claims 14 to 16, wherein the second instruction information is conveyed by the BSS transition candidate preference sub-element of the peripheral reporting element.

18. The method according to claim 17, wherein the BSS transition candidate preference sub-element further includes a preference field, the length of which the preference field is 7 bits or less, and the preference field indicates the degree of recommendation of the candidate target AP MLD carried by the peripheral reporting element to which the preference field belongs.

19. The method according to claim 18, wherein the sum of the bit length of the second instruction information and the length of the preference field is one octet or less.

20. The method according to any one of claims 14 to 16, wherein the second instruction information is carried in the Basic Service Set Identifier (BSSID) information field of the peripheral reporting element.

21. A method for providing information in basic service set transition management, The steps include: generating a Basic Service Set Transition Management (BTM) request frame using an Access Point Multilink Device (AP MLD), wherein the BTM request frame includes one or more peripheral reporting elements, one peripheral reporting element used to carry information about one candidate target AP MLD, and the peripheral reporting element includes STA-specific profile sub-elements for any APs not excluded in the candidate target AP MLD; The AP MLD transmits the BTM request frame. A method that includes this.

22. A method for providing information in basic service set transition management, The steps include: receiving a Basic Service Set Transition Management (BTM) request frame by a non-access point multilink device (non-AP MLD), wherein the BTM request frame includes one or more peripheral reporting elements, one peripheral reporting element used to carry information about one candidate target AP MLD, and the peripheral reporting element includes STA-specific profile sub-elements of any APs not excluded in the candidate target AP MLD; The steps include: analyzing the BTM request frame using the non-AP MLD; A method that includes this.

23. The method according to claim 21 or 22, wherein the STA-specific profile sub-element further includes a third instruction information, the third instruction information indicating a process for the AP corresponding to the STA-specific profile sub-element.

24. The third instruction information indicates the processing for the AP corresponding to the profile sub-element for each STA, When the third instruction information is a first value, the third instruction information indicates that the AP MLD does not have a recommendation or a recommendation for association with the AP corresponding to the STA profile sub-element. When the third instruction information is the second value, the third instruction information indicates that the AP MLD has a recommendation for the association with the AP corresponding to the STA profile sub-element. The method according to claim 23, which includes the following:

25. The method according to claim 23 or 24, wherein the third instruction information is conveyed in the station (STA) control field of each STA profile sub-element.

26. A communication device comprising a unit or module configured to perform the method described in any one of claims 1 to 25.

27. 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, thereby enabling the method according to any one of claims 1 to 25 to be performed.

28. A communication device including logic circuits and interfaces, A communication device wherein the logic circuit is coupled to the interface, the interface is configured to input and / or output code instructions, and the logic circuit is configured to execute the code instructions to enable the method according to any one of claims 1 to 25 to be performed.

29. 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 25 is executed.

30. It is a communication system, The communication system includes an AP MLD and a non-AP MLD, wherein the AP MLD is configured to perform the method described in any one of claims 1, 8, 14, and 21, and the non-AP MLD is configured to perform the method described in any one of claims 2, 9, 15, and 22.

Images