Method and apparatus for information indication in btm

By introducing streamlined fields and streamlined extended fields in the BTM request frame, the BSS conversion information indication between non-AP multi-link devices and AP multi-link devices is improved, and the problem of incomplete information indication in the prior art is solved, and the problem of improved information indication is improved. Coordination efficiency and stability between equipment.

WO2024245376A1PCT designated stage expired Publication Date: 2024-12-05HUAWEI TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/096543
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-31
Filing Date
2024-05-31
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

The information in the existing BTM indicates that the BSS conversion process between the non-AP multi-link device and the AP multi-link device is not perfect enough, making it difficult for non-AP multi-link devices to clarify the attitude and its own behavior of the AP multi-link device.

Method used

By introducing thin fields and thin extension fields in the BTM request frame, it indicates how the BSSID or AP multilink devices are not listed in the BSS conversion candidate list, and the candidate target AP multilink devices listed in the candidate list. There is no way to handle APs in any recommended AP combination, and the behavior of non-AP multi-link devices is clarified.

Benefits of technology

It improves the decision accuracy of non-AP multi-link devices during the BSS conversion process, ensures their effective coordination with AP multi-link devices, and improves the communication efficiency and stability between multi-link devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024096543_05122024_PF_FP_ABST
    Figure CN2024096543_05122024_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to a method and apparatus for information indication in BTM. The method comprises: an AP MLD generates and sends a BTM request frame, the BTM request frame comprising first indication information used for indicating a processing mode of a BSSID or an AP MLD that is not listed in a BSS transition candidate list entry field, and a processing mode of an AP that does not appear in a recommended AP combination in a candidate target AP MLD listed in the BSS transition candidate list entry field. By using the present application, the information indication in BTM can be perfected. The present application is applied to a WLAN system supporting 802.11 series protocols such as a next-generation WiFi protocol of 802.11ax, i.e., 802.11be, WiFi 7 or EHT, and the next generation of 802.11be, i.e., WiFi 8, UHR and WiFi AI, and is also applied to a WPAN system supporting UWB, a sensing system, etc.
Need to check novelty before this filing date? Find Prior Art

Description

Information indication method and device in BTM

[0001] This application claims priority to the Chinese patent application with application number 202310638067.7 filed with the State Intellectual Property Office of China on May 31, 2023, and priority to the Chinese patent application with the invention name “Information Indication Method and Device in BTM”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of wireless communication technologies, and in particular to a method and apparatus for indicating information in basic service set (BSS) transition management (BTM). Background Art

[0003] With the development of wireless communication technology, more and more wireless communication devices support multi-link (ML) communication. For example, they can communicate simultaneously on the 2.4 GHz, 5 GHz, and 6 GHz frequency bands, or on different channels within the same frequency band, thereby increasing the communication rate between devices. Such devices are generally called multi-link devices (MLDs). Multi-link devices typically contain one or more subordinate stations, each of which operates on a frequency band, a channel, or a link. If all stations within an MLD are access points (APs), it can be further referred to as an AP MLD; if all stations within an MLD are non-access point stations (non-AP STAs), it can be further referred to as a non-AP MLD.

[0004] Currently, when a station accesses a local area network (LAN), it must belong to a basic service set (BSS). In some scenarios, such as roaming, a non-AP STA needs to exit the current BSS and join a new one. If the non-AP STA supports the Basic Service Set Transition Management (BTM) function, this function can be used to facilitate BSS transitions. During the BTM process, the AP can send a BSS transition management request (BTM request) frame to the non-AP STA about to disassociate, informing them of the impending disassociation. The BTM request frame can also include information about the APs surrounding the non-AP STA, facilitating the non-AP STA's selection of a new BSS.

[0005] In existing technologies, an AP MLD can also provide information about surrounding AP MLDs to a non-AP MLD via a BTM request frame, allowing the non-AP MLD to select a new AP MLD for association. However, the information provided in existing BTMs regarding BSS transitions between non-AP MLDs and AP MLDs is incomplete.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide a method and apparatus for indicating information in a BTM, which can improve the information indication in the BTM and enable the non-AP MLD to better understand the attitude of the AP MLD and the behavior of the non-AP MLD itself.

[0008] The present application is introduced below from different aspects. It should be understood that the implementation methods and beneficial effects of the following different aspects can be referenced to each other.

[0009] In a first aspect, the present application provides an information indication method in BTM, the method comprising: an AP MLD generates and sends a BTM request frame, the BTM request frame comprising a BSS conversion candidate list entry field and a request mode field, the request mode field comprising first indication information, the first indication information being used to indicate a processing method for a basic service set identifier (BSS identifier, BSSID) or AP MLD that is not listed in the BSS conversion candidate list entry field, and a processing method for an AP that does not appear in any recommended AP combination among the candidate target AP MLDs listed in the BSS conversion candidate list entry field.

[0010] In this application, BSSID can be used to identify a BSS or an AP. The BSS conversion candidate list entry field includes one or more neighbor report elements. A neighbor report element can be used to carry (or describe) the preference of a target BSS candidate or a candidate target AP MLD. Different neighbor report elements can carry preferences for different AP combinations (AP sets) in the same candidate target AP MLD, and different neighbor report elements can also carry preferences for different target BSS candidates or candidate target AP MLDs. Therefore, "the candidate target AP MLD listed in the BSS conversion candidate list entry field" can refer to the candidate target AP MLD corresponding to the neighbor report element of the BSS conversion candidate list entry field.

[0011] The frame formats of the BTM request frame, the BSS transition candidate list entry field, and the neighbor report element, etc., can be found in the following description and are not described in detail here.

[0012] The present application carries first indication information in the request mode field of the BTM request frame, which is used to indicate the processing method of the BSSID or AP MLD that is not listed in the BSS conversion candidate list entry field, and the processing method of the AP that does not appear in any recommended AP combination in the candidate target AP MLD listed in the BSS conversion candidate list entry field. This improves the information indication in the BTM, clarifies the processing method of the AP in the MLD, and makes the non-AP MLD more clear about the attitude of the AP MLD and the behavior of the non-AP MLD itself.

[0013] In a second aspect, the present application provides an information indication method in BTM, the method comprising: a non-AP MLD receiving and parsing a BTM request frame, the BTM request frame comprising a BSS conversion candidate list entry field and a request mode field, the request mode field comprising first indication information, the first indication information being used to indicate a processing method for a BSSID or AP MLD that is not listed in the BSS conversion candidate list entry field, and a processing method for an AP that does not appear in any recommended AP combination among the candidate target AP MLDs listed in the BSS conversion candidate list entry field.

[0014] In a third aspect, the present application provides a communication device, which may be an AP MLD or a chip or functional module configured in the AP MLD, and includes a processing unit and a transceiver unit. The processing unit is configured to generate a BTM request frame; the transceiver unit is configured to send or output the BTM request frame. The BTM request frame includes a BSS conversion candidate list entry field and a request mode field, wherein the request mode field includes first indication information, and the first indication information is used to indicate how to handle BSSIDs or AP MLDs that are not listed in the BSS conversion candidate list entry field, and how to handle APs that do not appear in any recommended AP combination among the candidate target AP MLDs listed in the BSS conversion candidate list entry field.

[0015] In a fourth aspect, the present application provides a communication device, which may be a non-AP MLD or a chip or functional module configured in a non-AP MLD. The communication device includes a transceiver unit and a processing unit. The transceiver unit is configured to receive or input a BTM request frame; the processing unit is configured to parse the 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 indication information. The first indication information is used to indicate how to handle BSSIDs or AP MLDs that are not listed in the BSS transition candidate list entry field, and how to handle APs that do not appear in any recommended AP combination among the candidate target AP MLDs listed in the BSS transition candidate list entry field.

[0016] In a possible implementation manner of any of the above aspects, the first indication information is a bridged field.

[0017] Optionally, the length of the simplified field is 1 bit.

[0018] Optionally, when the simplified field is a first value, it indicates that the sender of the BTM request frame (i.e., the AP MLD) neither recommends nor opposes the receiver of the BTM request frame (i.e., the non-AP MLD) from associating with a BSSID or AP MLD that does not appear in the BSS conversion candidate list entry field, and an AP that does not appear in any recommended AP combination among the candidate target AP MLDs that appear in the BSS conversion candidate list entry field. When the simplified field is a second value, it indicates that the sender of the BTM request frame (i.e., the AP MLD) excludes or opposes the receiver of the BTM request frame (i.e., the non-AP MLD) from associating with a BSSID or AP MLD that does not appear in the BSS conversion candidate list entry field, and an AP that does not appear in any recommended AP combination among the candidate target AP MLDs that appear in the BSS conversion candidate list entry field.

[0019] Exemplarily, the first value is 0 and the second value is 1. Alternatively, the first value is 1 and the second value is 0.

[0020] This application expands the meaning of the simplified field so that it can simultaneously indicate the processing method of the BSSID or AP MLD that is not listed in the BSS conversion candidate list entry field, and the processing method of the AP that does not appear in the candidate target AP MLD listed in the BSS conversion candidate list entry field; the meaning is clear, no additional overhead is added, and the compatibility is good.

[0021] In a possible implementation of any of the above aspects, the BSS conversion candidate preference sub-element of the BSS conversion candidate list entry field includes a preference field. Exemplarily, the meaning of the Preference field may follow the existing meaning, or the meaning of the Preference field may change as the standard evolves, which is not limited in this application. Alternatively, the Preference field may be used to indicate the degree of recommendation of an AP combination. The AP combination may be an AP combination recommended by a neighbor report element to which the Preference field belongs. That is, this AP combination is an AP combination recommended by a candidate target AP MLD listed in the BSS conversion candidate list entry field. The larger the value of the Preference field, the higher the degree of recommendation it represents.

[0022] This application can also change the meaning of the Preference field so that the neighbor report element can indicate the recommendation level of a certain AP combination when recommending an AP MLD combination.

[0023] In one possible implementation of any of the above aspects, the first indication information includes a simplified field and a simplified extension field. The simplified field is used to indicate a handling method for a BSSID or AP MLD that is not listed in the BSS transition candidate list entry field. The simplified extension field is used to indicate a handling method for an AP that is not included in any recommended AP combination among the candidate target AP MLDs listed in the BSS transition candidate list entry field.

[0024] Optionally, the length of the simplified extension field is 1 bit. For example, a reserved bit in the request mode field can be used as the simplified extension field.

[0025] Optionally, when the simplified extension field is a third value, it indicates that the sender of the BTM request frame (i.e., the AP MLD) neither recommends nor opposes the receiver of the BTM request frame (i.e., the non-AP MLD) from associating with an AP that is not included in any recommended AP combination among the candidate target AP MLDs in the BSS transition candidate list entry field. When the simplified extension field is a fourth value, it indicates that the sender of the BTM request frame (i.e., the AP MLD) excludes or opposes the receiver of the BTM request frame (i.e., the non-AP MLD) from associating with an AP that is not included in any recommended AP combination among the candidate target AP MLDs in the BSS transition candidate list entry field.

[0026] Exemplarily, the third value is 0 and the fourth value is 1. Alternatively, the third value is 1 and the fourth value is 0.

[0027] This application adds a simplified extension field to the request mode field to indicate how to handle APs that do not appear in the candidate target AP MLD listed in the BSS transition candidate list entry field. The logic is clear and easy to understand for non-AP MLD. The added bits appear at the same time as the existing simplified field, and the logic is neat.

[0028] In a fifth aspect, the present application provides an information indication method in BTM, the method comprising: AP MLD generates and sends a BTM request frame, the BTM request frame comprising a BSS conversion candidate list entry field and a request mode field, the request mode field comprising a simplified field, the simplified field being used to indicate a processing method for a BSSID or AP MLD that is not listed in the BSS conversion candidate list entry field, and a processing method for an AP combination that is not recommended in the candidate target AP MLD listed in the BSS conversion candidate list entry field.

[0029] An "AP combination" can include one or more APs. That is, a single AP can also be considered an AP combination, as can all APs belonging to an AP MLD. The meaning of "AP combinations not recommended by the candidate target AP MLD listed in the BSS transition candidate list entry field" is described in Example 3 below and is not detailed here.

[0030] This embodiment of the present application expands the meaning of simplified fields to simultaneously indicate how to handle BSSIDs or AP MLDs not listed in the BSS transition candidate list entry field, and how to handle AP combinations not recommended by the candidate target AP MLDs listed in the BSS transition candidate list entry field. This improves the information indication in the BTM, clarifies the handling of non-recommended AP combinations in the MLD, and makes the non-AP MLD more explicit about the AP MLD's attitude and its own behavior. Furthermore, this embodiment provides clear meaning, no additional overhead, and improved compatibility.

[0031] In a sixth aspect, the present application provides an information indication method in BTM, the method comprising: a non-AP MLD receives and parses a BTM request frame, the BTM request frame comprising a BSS conversion candidate list entry field and a request mode field, the request mode field comprising a simplified field, the simplified field being used to indicate a processing method for a BSSID or AP MLD that is not listed in the BSS conversion candidate list entry field, and a processing method for an AP combination that is not recommended in the candidate target AP MLD listed in the BSS conversion candidate list entry field.

[0032] In a seventh aspect, the present application provides a communication device, which may be an AP MLD or a chip or functional module configured in the AP MLD, and includes a processing unit and a transceiver unit. The processing unit is configured to generate a BTM request frame; the transceiver unit is configured to send or output the BTM request frame. The BTM request frame includes a BSS conversion candidate list entry field and a request mode field, wherein the request mode field includes a simplified field, which is used to indicate how to handle BSSIDs or AP MLDs that are not listed in the BSS conversion candidate list entry field, and how to handle AP combinations that are not recommended in the candidate target AP MLDs listed in the BSS conversion candidate list entry field.

[0033] In an eighth aspect, the present application provides a communication device, which may be a non-AP MLD or a chip or functional module configured in a non-AP MLD. The communication device includes a transceiver unit and a processing unit. The transceiver unit is configured to receive or input a BTM request frame; the processing unit is configured to parse the 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 simplified field, which is used to indicate how to handle BSSIDs or AP MLDs not listed in the BSS transition candidate list entry field, and how to handle AP combinations that are not recommended in the candidate target AP MLDs listed in the BSS transition candidate list entry field.

[0034] In combination with any one of the fifth to eighth aspects, in one possible implementation, the length of the simplified field is 1 bit. When the simplified field is a first value, it indicates that the sender of the BTM request frame (i.e., the AP MLD) neither recommends nor opposes the receiver of the BTM request frame (i.e., the non-AP MLD) from associating with a BSSID or AP MLD that does not appear in the BSS conversion candidate list entry field, and an AP combination that is not recommended among the candidate target AP MLDs that appear in the BSS conversion candidate list entry field. When the simplified field is a second value, it indicates that the sender of the BTM request frame (i.e., the AP MLD) excludes or opposes the receiver of the BTM request frame (i.e., the non-AP MLD) from associating with a BSSID or AP MLD that does not appear in the BSS conversion candidate list entry field, and an AP combination that is not recommended among the candidate target AP MLDs that appear in the BSS conversion candidate list entry field.

[0035] Exemplarily, the first value is 0 and the second value is 1. Alternatively, the first value is 1 and the second value is 0.

[0036] In combination with any one of the fifth to eighth aspects, in a possible implementation, the BSS conversion candidate preference sub-element of the above-mentioned BSS conversion candidate list entry field includes a Preference field. Exemplarily, the meaning of the Preference field may follow the existing meaning, or the meaning of the Preference field may change as the standard evolves, which is not limited in this application. Alternatively, the Preference field may be used to indicate the degree of recommendation of an AP combination. The AP combination may be an AP combination recommended by a neighbor report element to which the Preference field belongs. That is, this AP combination is an AP combination recommended by a candidate target AP MLD listed in the BSS conversion candidate list entry field. The larger the value of the Preference field, the higher the degree of recommendation it represents.

[0037] This application can also change the meaning of the Preference field so that the neighbor report element can indicate the recommendation level of a certain AP combination when recommending an AP MLD combination.

[0038] In a ninth aspect, the present application provides an information indication method in a BTM, the method comprising: an AP MLD generates and sends a BTM request frame, the BTM request frame including a BSS conversion candidate list entry field, the BSS conversion candidate list entry field including one or more neighbor report elements, wherein one neighbor report element is used to carry information about a candidate target AP MLD. Each neighbor report element includes a second indication information, the second indication information being used to indicate a handling method for an AP that does not appear in an AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs. Since one neighbor report element corresponds to one candidate target AP MLD, the second indication information can be briefly described as: a handling method for indicating an AP that does not appear in a certain AP combination of a certain candidate target AP MLD.

[0039] It is understood that an "AP group" can include one or more APs. In other words, a single AP can also be considered an AP group, and all APs belonging to an AP MLD can also be considered an AP group.

[0040] This application carries the second indication information in the neighbor report element to indicate the processing method of the AP that does not appear in a certain AP combination in the single candidate target AP MLD, so that each recommended AP combination can have its own processing method, which is flexible to use.

[0041] In a tenth aspect, the present application provides a method for indicating information in a BTM, the method comprising: a non-AP MLD receiving and parsing a BTM request frame, the BTM request frame including a BSS transition candidate list entry field, the BSS transition candidate list entry field including one or more neighbor report elements, wherein one neighbor report element is used to carry information about a candidate target AP MLD. Each neighbor report element includes second indication information, the second indication information being used to indicate a handling method for an AP that does not appear in an AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs.

[0042] In an eleventh aspect, the present application provides a communication device, which may be an AP MLD or a chip or functional module configured in the AP MLD, and the communication device includes a processing unit and a transceiver unit. The processing unit is configured to generate a BTM request frame; the transceiver unit is configured to send or output the BTM request frame. The BTM request frame includes a BSS conversion candidate list entry field, and the BSS conversion candidate list entry field includes one or more neighbor report elements, wherein one neighbor report element is used to carry information about a candidate target AP MLD. The neighbor report element includes second indication information, and the second indication information is used to indicate a handling method for an AP that does not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs.

[0043] In a twelfth aspect, the present application provides a communication device, which may be a non-AP MLD or a chip or functional module configured in a non-AP MLD, and the communication device includes a transceiver unit and a processing unit. The transceiver unit is used to receive or input a BTM request frame; the processing unit is used to parse the BTM request frame. The BTM request frame includes a BSS conversion candidate list entry field, and the BSS conversion candidate list entry field includes one or more neighbor report elements, wherein one neighbor report element is used to carry information of a candidate target AP MLD. The neighbor report element includes second indication information, and the second indication information is used to indicate a handling method for an AP that does not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs.

[0044] In combination with any one of aspects 9 to 12, in one possible implementation, when the second indication information is a first value, it indicates that the sender of the BTM request frame (i.e., the AP MLD) neither recommends nor objects to the receiver of the BTM request frame (i.e., the non-AP MLD) associating with an AP that does not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs. When the second indication information is a second value, it indicates that the sender of the BTM request frame (i.e., the AP MLD) excludes or objects to the receiver of the BTM request frame (i.e., the non-AP MLD) associating with an AP that does not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs.

[0045] Exemplarily, the first value is 0 and the second value is 1. Alternatively, the first value is 1 and the second value is 0.

[0046] In combination with any aspect from the ninth aspect to the twelfth aspect, in a possible implementation, the above-mentioned second indication information is carried in the BSS transition candidate preference sub-element of the neighbor report element.

[0047] For example, since the existing BSS conversion candidate preference sub-element is not extensible, the length of the Preference field can be shortened so that the length of the Preference field is less than or equal to 7 bits, but the meaning of the Preference field is not changed (such as the Preference field is used to indicate the degree of recommendation of the candidate target AP MLD carried by the neighbor report element to which the Preference field belongs); and the one or more bits saved by shortening the Preference field are used to represent the second indication information. In other words, the Preference field in the BSS conversion candidate preference sub-element is less than or equal to 7 bits, the bit length of the second indication information is greater than or equal to 1 bit, and the sum of the length of the Preference field and the bit length of the second indication information is less than or equal to 1 byte (8 bits). It can be understood that this implementation does not limit the meaning of the Preference field, but only changes the length of the Preference field. The meaning of the Preference field can also change as the standard evolves.

[0048] This application includes a second indication in the BSS Transition Candidate Preference sub-element of the Neighbor Report element to indicate how to handle APs that are not included in the AP combination of the Candidate Target AP MLD carried by the Neighbor Report element. This allows for a unique handling method for each AP combination recommended in the Candidate Target AP MLD, providing flexibility. Furthermore, the second indication is used simultaneously with the Preference value; that is, it does not appear when the Neighbor Report element is not used for recommendation.

[0049] In combination with any one of aspects 9 to 12, in one possible implementation, the second indication information is carried in a BSSID information field of a neighbor report element. Exemplarily, a reserved bit in the BSSID information field can be used as the second indication information.

[0050] This application uses a reserved bit in the BSSID information field of the neighbor report element to indicate the processing method for APs that do not appear in the AP combination of the candidate target AP MLD carried by this neighbor report element. Each AP combination recommended in the candidate target AP MLD can have its own processing method, which is flexible to use.

[0051] In the thirteenth aspect, the present application provides an information indication method in BTM, the method comprising: AP MLD generates and sends a BTM request frame, the BTM request frame includes a BSS conversion candidate list entry field, the BSS conversion candidate list entry field includes one or more neighbor report elements, wherein one neighbor report element is used to carry information of a candidate target AP MLD. A neighbor report element includes a per-STA profile subelement (Per-STA Profile subelement) of any non-prohibited AP in a candidate target AP MLD. A Per-STA Profile subelement corresponds to a non-prohibited AP in the candidate target AP MLD. Here, "non-prohibited" can include at least two meanings: "recommended" and "neither recommended nor opposed".

[0052] In addition, this application also defaults to prohibiting association with APs that do not appear in the Neighbor Report element. Here, "APs that do not appear in the Neighbor Report element" can refer to APs other than the AP indicated by the BSSID field in the Candidate Target AP MLD carried by the Neighbor Report element and the AP corresponding to the Per-STA Profile subelement.

[0053] This application modifies the meaning of the AP combination carried in the neighbor report element so that it defaults to prohibiting association with APs that do not appear in the neighbor report element. This improves the information indication in BTM and makes non-AP MLD more clear about the attitude of AP MLD and its own behavior.

[0054] In a fourteenth aspect, the present application provides an information indication method in BTM, the method comprising: a non-AP MLD receives and parses a BTM request frame, the BTM request frame includes a BSS conversion candidate list entry field, the BSS conversion candidate list entry field includes one or more neighbor report elements, wherein one neighbor report element is used to carry information of a candidate target AP MLD. A neighbor report element includes a Per-STA Profile subelement of any non-prohibited AP in a candidate target AP MLD. A Per-STA Profile subelement corresponds to a non-prohibited AP in the candidate target AP MLD. Here, "non-prohibited" can include at least two meanings: "recommended" and "neither recommended nor opposed."

[0055] In the fifteenth aspect, the present application provides a communication device, which can be an AP MLD or a chip or functional module configured in the AP MLD, and the communication device includes a processing unit and a transceiver unit. The processing unit is used to generate a BTM request frame; the transceiver unit is used to send or output the BTM request frame. The BTM request frame includes a BSS conversion candidate list entry field, and the BSS conversion candidate list entry field includes one or more neighbor report elements, wherein one neighbor report element is used to carry information of a candidate target AP MLD. A neighbor report element includes the Per-STA Profile subelement of any non-prohibited AP in a candidate target AP MLD. A Per-STA Profile subelement corresponds to a non-prohibited AP in the candidate target AP MLD. Here, "non-prohibited" can include at least two meanings: "recommended" and "neither recommended nor opposed".

[0056] In the sixteenth aspect, the present application provides a communication device, which may be a non-AP MLD or a chip or functional module configured in a non-AP MLD, and the communication device includes a transceiver unit and a processing unit. The transceiver unit is used to receive or input a BTM request frame; the processing unit is used to parse the BTM request frame. The BTM request frame includes a BSS conversion candidate list entry field, and the BSS conversion candidate list entry field includes one or more neighbor report elements, wherein one neighbor report element is used to carry information of a candidate target AP MLD. A neighbor report element includes a Per-STA Profile subelement of any non-prohibited AP in a candidate target AP MLD. A Per-STA Profile subelement corresponds to a non-prohibited AP in the candidate target AP MLD. Here, "non-prohibited" can include at least two meanings: "recommended" and "neither recommended nor opposed."

[0057] In combination with any aspect from the thirteenth aspect to the sixteenth aspect, in one possible implementation, each Per-STA Profile subelement also includes third indication information, and the third indication information is used to indicate the processing method of the AP corresponding to this per-STA profile subelement.

[0058] Optionally, when the third indication information is a first value, it indicates that the sender of the BTM request frame (i.e., the AP MLD) neither recommends nor opposes the receiver of the BTM request frame (i.e., the non-AP MLD) from associating with the AP corresponding to the per-STA profile sub-element. When the third indication information is a second value, it indicates that the sender of the BTM request frame (i.e., the AP MLD) recommends that the receiver of the BTM request frame (i.e., the non-AP MLD) from associating with the AP corresponding to the per-STA profile sub-element. Exemplarily, the first value is 0 and the second value is 1. Alternatively, the first value is 1 and the second value is 0.

[0059] This application defaults to prohibiting association for APs not appearing in the Neighbor Report element. APs corresponding to the Per-STA Profile subelement that appears indicate whether association is recommended through a third indication. Because association preference information appears in the Per-STA Profile subelement corresponding to each AP, each AP in each AP combination provided by AP MLD can have its own processing method, providing great flexibility.

[0060] In combination with any one of aspects 13 to 16, in one possible implementation, the third indication information is carried in the STA Control field of the per-STA profile subelement. Exemplarily, a reserved bit in the STA Control field of the Per-STA Profile subelement can be used as the third indication information.

[0061] In a seventeenth aspect, the present application provides a communication device, which is an AP MLD, and includes a processor configured to execute the method described in the first aspect, the fifth aspect, the ninth aspect, the thirteenth aspect, or any possible implementation of any one of them. Alternatively, the processor is configured to execute a program stored in a memory, and when the program is executed, the method described in the first aspect, the fifth aspect, the ninth aspect, the thirteenth aspect, or any possible implementation of any one of them is executed.

[0062] In combination with the seventeenth aspect, in a possible implementation, the memory is located outside the above-mentioned communication device.

[0063] In combination with the seventeenth aspect, in one possible implementation, the memory is located within the above-mentioned communication device.

[0064] In the present application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

[0065] In combination with the seventeenth aspect, in a possible implementation, the communication device further includes a transceiver, and the transceiver is used to send a BTM request frame.

[0066] In an eighteenth aspect, the present application provides a communications device, which is a non-AP MLD. The communications device includes a processor configured to execute the method described in the second aspect, the sixth aspect, the tenth aspect, the fourteenth aspect, or any possible implementation of any one of these aspects. Alternatively, the processor is configured to execute a program stored in a memory, and when the program is executed, the method described in the second aspect, the sixth aspect, the tenth aspect, the fourteenth aspect, or any possible implementation of any one of these aspects is executed.

[0067] In combination with the eighteenth aspect, in a possible implementation, the memory is located outside the above-mentioned communication device.

[0068] In combination with the eighteenth aspect, in one possible implementation, the memory is located within the above-mentioned communication device.

[0069] In the present application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

[0070] In combination with the eighteenth aspect, in a possible implementation, the communication device further includes a transceiver, and the transceiver is used to receive a BTM request frame.

[0071] In the nineteenth aspect, an embodiment of the present application provides a communication device, which includes a logic circuit and an interface, and the logic circuit is coupled to the interface; the interface is used to input and / or output information, and the logic circuit is used to execute the method shown in the above-mentioned first aspect, the above-mentioned fifth aspect, the above-mentioned ninth aspect, the above-mentioned thirteenth aspect, or any possible implementation of any aspect therein.

[0072] In the twentieth aspect, an embodiment of the present application provides a communication device, which includes a logic circuit and an interface, and the logic circuit is coupled to the interface; the interface is used to input and / or output information, and the logic circuit is used to execute the method shown in the second aspect, the sixth aspect, the tenth aspect, the fourteenth aspect, or any possible implementation of any aspect therein.

[0073] In the twenty-first aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, which, when run on a computer, enables the method shown in the first aspect, the fifth aspect, the ninth aspect, the thirteenth aspect, or any possible implementation of any one of them to be executed.

[0074] In aspect 22, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, which, when executed on a computer, enables the method shown in any possible implementation of the second aspect, the sixth aspect, the tenth aspect, the fourteenth aspect, or any of them to be executed.

[0075] In aspect 23, an embodiment of the present application provides a computer program product, which includes a computer program or computer code, and when it runs on a computer, it enables the method shown in the above-mentioned first aspect, the above-mentioned fifth aspect, the above-mentioned ninth aspect, the above-mentioned thirteenth aspect, or any possible implementation of any aspect therein to be executed.

[0076] In aspect 24, an embodiment of the present application provides a computer program product, which includes a computer program or computer code, and when it runs on a computer, it enables the method shown in the above-mentioned second aspect, the above-mentioned sixth aspect, the above-mentioned tenth aspect, the above-mentioned fourteenth aspect, or any possible implementation of any aspect therein to be executed.

[0077] In aspect 25, an embodiment of the present application provides a computer program. When the computer program is run on a computer, the method shown in the first aspect, the fifth aspect, the ninth aspect, the thirteenth aspect, or any possible implementation of any one of them is executed.

[0078] In aspect 26, an embodiment of the present application provides a computer program. When the computer program is run on a computer, the method shown in aspect 2, aspect 6, aspect 10, aspect 14, or any possible implementation of any one of them is executed.

[0079] In aspect 27, an embodiment of the present application provides a communication system, which includes an AP MLD and a non-AP MLD, wherein the AP MLD is used to execute the method shown in the first aspect, the fifth aspect, the ninth aspect, the third aspect, or any possible implementation of any one of them, and the non-AP MLD is used to execute the method shown in the second aspect, the sixth aspect, the tenth aspect, the fourteenth aspect, or any possible implementation of any one of them.

[0080] The technical effects achieved in the above-mentioned aspects can be referred to each other or to the beneficial effects in the method embodiments shown below, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0081] FIG1a is a schematic diagram of an architecture of a wireless communication system provided by an embodiment of the present application;

[0082] FIG1b is another schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application;

[0083] FIG2a is a schematic diagram of a multi-link device communicating with other devices according to an embodiment of the present application;

[0084] FIG2 b is another schematic diagram of a multi-link device communicating with other devices according to an embodiment of the present application;

[0085] FIG3 is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0086] FIG4 is a schematic diagram of the frame format of the action field in the BTM request frame provided in an embodiment of the present application;

[0087] FIG5 is a schematic diagram of a frame format of a neighbor report element provided in an embodiment of the present application;

[0088] FIG6 is a schematic diagram of a frame format of a basic multi-link sub-element provided in an embodiment of the present application;

[0089] FIG7 is a schematic diagram of the frame format of a BSS conversion candidate preference sub-element provided in an embodiment of the present application;

[0090] FIG8 is a schematic diagram of the frame format of the request mode field provided in an embodiment of the present application;

[0091] FIG9 is a schematic flow chart of a first method for indicating information in a BTM according to an embodiment of the present application;

[0092] FIG10 is a schematic diagram of a second flow chart of the information indication method in the BTM provided in an embodiment of the present application;

[0093] FIG11 is a schematic diagram of another frame format of a request mode field provided in an embodiment of the present application;

[0094] FIG12 is a schematic diagram of a third flow chart of the information indication method in the BTM provided in an embodiment of the present application;

[0095] FIG13 is a schematic diagram of a fourth flow chart of the information indication method in the BTM provided in an embodiment of the present application;

[0096] FIG14 is a schematic diagram of the frame format of the BSSID information field provided in an embodiment of the present application;

[0097] FIG15 is a schematic diagram of another frame format of a BSS conversion candidate preference sub-element provided in an embodiment of the present application;

[0098] FIG16 is a schematic diagram of a fifth flow chart of the information indication method in the BTM provided in an embodiment of the present application;

[0099] FIG17 is a schematic diagram of the frame format of the STA Control field provided in an embodiment of the present application;

[0100] FIG18 is a sixth flow chart of the information indication method in the BTM provided in an embodiment of the present application;

[0101] FIG19 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0102] FIG20 is another schematic structural diagram of a communication device provided in an embodiment of the present application;

[0103] FIG21 is another structural diagram of the communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0104] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application.

[0105] In the description of this application, unless otherwise specified, " / " means "or", for example, A / B can mean A or B. "And / or" in this article is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, "at least one" means one or more, and "plurality" means two or more. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can mean: a, b, c; a and b; a and c; b and c; or a, b, and c. Among them, a, b, and c can be single or multiple.

[0106] In the description of this application, words such as "first" and "second" do not limit the quantity or order of execution, and words such as "first" and "second" do not necessarily limit differences. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to the process, method, product, or device.

[0107] In this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary," "for example," or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary," "for example," or "for example" is intended to present the relevant concepts in a concrete way.

[0108] Elements used in the singular herein are intended to mean "one or more" rather than "one and only one" unless specifically stated otherwise.

[0109] Continuously improving throughput is an ongoing technical goal in the evolution of cellular networks and wireless local area networks (WLANs). WLAN protocols are primarily discussed within the IEEE 802.11 standards group, and throughput has been continuously improved in previous standards such as 802.11a / b / g / n / ac / ax. The next-generation standard, IEEE 802.11be, known as extremely high throughput (EHT), prioritizes significantly improving peak throughput. To achieve this goal, the next-generation IEEE 802.11be standard includes multi-link (ML) as one of its key technologies. Its core concept is to enable WLAN devices supporting the next-generation IEEE 802.11 standard to transmit and receive data across multiple frequency bands, enabling greater bandwidth for data transmission and significantly improving throughput.

[0110] Multiple frequency bands include, but are not limited to, the 2.4 GHz, 5 GHz, and 6 GHz Wi-Fi bands. Access and transmission on each frequency band is called a link, and access and transmission on multiple bands is called multi-link (ML). Multi-link helps reduce latency and improve robustness.

[0111] A multi-link device includes one or more subordinate sites, and the subordinate sites can be logical sites. In the embodiments of the present application, "a multi-link device includes subordinate sites" is also briefly described as "a multi-link device includes sites." Each subordinate site can operate on a frequency band, a channel, or a link. The subordinate site can be an AP or a non-AP STA. Among them, a multi-link device whose subordinate site is an AP can be called an AP multi-link device (AP multi-link device, AP MLD), and a multi-link device whose subordinate site is a non-AP STA can be called a non-AP multi-link device (non-AP multi-link device, non-AP MLD).

[0112] When transmitting data, a multi-link device (such as an AP MLD) and another multi-link device (non-AP MLD) can use a link identifier to identify a link or a station on a link. Before communicating, the two multi-link devices (such as an AP MLD and a non-AP MLD) can first negotiate or communicate the corresponding relationship between a link identifier (link ID) and a link or a station on a link. Alternatively, the AP MLD can indicate the corresponding relationship between a link identifier and a link or a station on a link through a broadcast management frame, such as a beacon frame. Therefore, during the data transmission process, there is no need to transmit a large amount of signaling information to indicate a link or a station on a link. It is sufficient to carry the link identifier, which reduces signaling overhead and improves transmission efficiency.

[0113] In one possible implementation, a multi-link device can implement wireless communications using the 802.11 family of protocols, such as Extreme Throughput (EHT), or a protocol based on or compatible with 802.11be, thereby enabling communication with other devices. Of course, the other devices may or may not be multi-link devices.

[0114] The technical solutions provided in this application can be applied to WLAN systems, such as Wi-Fi, etc. For example, the method provided in this application can be applied to IEEE 802.11 series protocols, such as 802.11ax next-generation Wi-Fi protocols, such as 802.11be, Wi-Fi 7 or EHT, and the next generation of 802.11be, Wi-Fi 8, ultra-high reliability (UHR), ultra-high reliability and throughput (UHRT) or Wi-Fi AI, etc., which are not listed here one by one. The technical solutions provided in this application can also be applied to wireless personal area networks (WPAN) systems based on ultra-wide band (UWB), sensing systems, etc. For example, the method provided in this application can be applied to IEEE 802.15 series protocols, such as 802.15.4a protocol, 802.15.4z protocol or 802.15.4ab protocol, or a future generation of UWB WPAN protocols, etc., which are not listed one by one. The technical solution provided in this application can also be applied to the following communication systems, for example, the Internet of Things (IoT) system, the Vehicle to X (V2X), the Narrow Band Internet of Things (NB-IoT) system, devices in the Internet of Vehicles, IoT nodes and sensors in the Internet of Things (IoT), smart cameras in smart homes, smart remote controls, smart water and electricity meters, and sensors in smart cities, etc., or it can also be applicable to the Long Term Evolution (LTE) system, the fifth-generation (5G) communication system, and new communication systems that will emerge in the future development of communications.

[0115] Although this application is mainly described using a network deploying IEEE 802.11 as an example, those skilled in the art will readily appreciate that the various aspects of this application can be extended to other networks that adopt various standards or protocols, such as high-performance wireless LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard, primarily used in Europe), wide area networks (WANs), wireless local area networks (WLANs), personal area networks (PANs), or other networks now known or developed in the future.

[0116] Referring to Figure 1a, Figure 1a is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application. As shown in Figure 1a, the wireless communication system includes at least two AP MLDs (such as AP MLD100 and AP MLD200 in Figure 1a) and at least one non-AP MLD (such as non-AP MLD300 in Figure 1a). Optionally, Figure 1a may also include a traditional station that only supports transmission over a single link (such as single-link non-AP STA400 in Figure 1a, also referred to as STA400). The AP MLD is a device that provides services to the non-AP MLD. The non-AP MLD can communicate with the AP MLD using multiple links, thereby achieving the effect of improving throughput. A STA in the non-AP MLD can also communicate with an AP in the AP MLD via a single link. It is understandable that Figure 1a uses a mobile phone as a non-AP MLD and a router as an example, and does not limit the types of AP MLDs and non-AP MLDs in this application. It is also understandable that the number of AP MLDs and non-AP MLDs in FIG1a is merely exemplary, and the number of AP MLDs or non-AP MLDs in the wireless communication system may be greater or lesser, which is not limited in this application.

[0117] In the embodiments of the present 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.

[0118] Refer to Figure 1b, which is another architectural diagram of a wireless communication system provided in an embodiment of the present application. As shown in Figure 1b, an AP MLD includes n stations, namely AP1, AP2, ..., APn; a non-AP MLD also includes n stations, namely STA1, STA2, ..., STAn. Here, n is a positive integer. Communication between MLDs is multi-link communication, and links 1 to n in Figure 1b constitute a multi-link. In other words, the AP MLD and the non-AP MLD can communicate in parallel using links 1, link 2, ..., link n. An AP in the AP MLD can establish a link with a STA in the non-AP MLD. For example, STA1 in the non-AP MLD establishes link 1 with AP1 in the AP MLD, STA2 in the non-AP MLD establishes link 2 with AP2 in the AP MLD, and STAn in the non-AP MLD establishes link n with APn in the AP MLD, and so on. By way of example, the multi-link device in the embodiment of the present application can be a single-antenna device or a multi-antenna device. For example, it can be a device with more than two antennas. The embodiment of the present application does not limit the number of antennas included in the multi-link device.

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

[0120] Referring to Figure 2a, Figure 2a is a schematic diagram of a multi-link device communicating with other devices according to an embodiment of the present application. For example, Figure 2a illustrates a communication scenario between AP MLD 101 and non-AP MLD 102. AP MLD 101 includes subordinate APs 101-1 and 101-2, and non-AP MLD 102 includes subordinate STAs 102-1 and 102-2. AP MLD 101 and non-AP MLD 102 communicate in parallel using Link 1 and Link 2.

[0121] Referring to Figure 2b, Figure 2b is another schematic diagram of a multi-link device communicating with other devices according to an embodiment of the present application. For example, Figure 2b illustrates a scenario in which AP MLD 101 communicates with non-AP MLD 102, non-AP MLD 103, and STA 104. AP MLD 101 includes subordinate APs 101-1 to 101-3; non-AP MLD 102 includes three subordinate stations, namely STA 102-1, STA 102-2, and STA 102-3; non-AP MLD 103 includes two subordinate stations, namely STA 103-1 and STA 103-2; and STA 104 is a single-link device. AP MLD 101 can communicate with non-AP MLD 102 using links 1, 2, and 3, respectively; communicate with non-AP MLD 103 using links 2 and 3; and communicate with STA 104 using link 1. In one example, STA 104 operates in the 2.4 GHz band; in non-AP MLD 103, STA 103-1 operates in the 5 GHz band, and STA 103-2 operates in the 6 GHz band; in non-AP MLD 102, STA 102-1 operates in the 2.4 GHz band, STA 102-2 operates in the 5 GHz band, and STA 102-3 operates in the 6 GHz band. AP 101-1 in AP MLD 101, operating in the 2.4 GHz band, can transmit uplink or downlink data to STA 104 and STA 102-1 in non-AP MLD 102 over link 1. AP 101-2 operating in the 5 GHz band in AP MLD 101 can transmit uplink or downlink data with STA 103-1 operating in the 5 GHz band in non-AP MLD 103 via link 2, and can also transmit uplink or downlink data with STA 102-2 operating in the 5 GHz band in non-AP MLD 102 via link 2. AP 101-3 operating in the 6 GHz band in AP MLD 101 can transmit uplink or downlink data with STA 102-3 operating in the 6 GHz band in non-AP MLD 102 via link 3, and can also transmit uplink or downlink data with STA 103-2 in the non-AP MLD via link 3.

[0122] Figure 2a above only illustrates that the AP MLD supports two frequency bands. Figure 2b above illustrates that AP MLD 101 supports three frequency bands (2.4 GHz, 5 GHz, and 6 GHz), each corresponding to a link. AP MLD 101 can operate on one or more of Link 1, Link 2, or Link 3. In practical applications, the AP MLD and non-AP MLD can also support more or fewer frequency bands, that is, the AP MLD and non-AP MLD can operate on more or fewer links, which is not limited in this embodiment of the present application. Figures 2a and 2b are merely schematic diagrams and do not constitute any limitation on the scope of protection of the embodiments of the present application. It is understood that the description of the 802.11 physical layer (PHY) and medium access control (MAC) layer in a multi-link device can refer to relevant standards or protocols, etc., and will not be described in detail in this embodiment of the present application.

[0123] Exemplarily, a multi-link device (here, either a non-AP MLD or an AP MLD) can be a device with wireless communication capabilities. This device can be a complete device or a chip or processing system installed in the complete device. Devices installed with these chips or processing systems can implement the methods and functions of the embodiments of the present application under the control of these chips or processing systems. For example, the non-AP MLD in the embodiments of the present application has wireless transceiver capabilities, can support the 802.11 series of protocols, and can communicate with AP MLDs, single-link devices, or other non-AP MLDs. For example, a non-AP MLD is any user communication device that allows a user to communicate with an AP and, in turn, with a WLAN. For example, a non-AP MLD can be a tablet computer, desktop, laptop, notebook computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), mobile phone, or other network-capable user device, or an IoT node in the Internet of Things (IoT), or an in-vehicle communication device in the Internet of Vehicles (IoV). A non-AP MLD can also be a chip or processing system in these terminals. The AP MLD can be a device that provides services to non-AP MLDs and can support the 802.11 series of protocols. For example, the AP MLD can be a communication entity such as a communication server, router, switch, or bridge. Alternatively, the AP MLD can include various forms of macro base stations, micro base stations, and relay stations. Of course, the AP MLD can also be a chip or processing system within these various devices to implement the methods and functions of the embodiments of the present application. The 802.11 protocol can be one that supports or is compatible with 802.11be.

[0124] It is understandable that multi-link devices can support high-speed and low-latency transmission. With the continuous evolution of wireless LAN application scenarios, multi-link devices can also be applied to more scenarios, such as sensor nodes in smart cities (for example, smart water meters, smart electricity meters, smart air detection nodes), smart devices in smart homes (for example, smart cameras, projectors, displays, TVs, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment terminals (for example, wearable devices such as AR and VR), smart devices in smart offices (for example, printers, projectors, etc.), Internet of Vehicles devices in the Internet of Vehicles, and some infrastructure in daily life scenarios (for example, vending machines, self-service navigation counters in supermarkets, self-service cash registers, self-service ordering machines, etc.). The specific forms of non-AP MLD and AP MLD are not limited in the embodiments of this application and are only illustrative.

[0125] The following is a brief description of the application scenarios involved in the embodiments of the present application.

[0126] The Basic Service Set (BSS) is the foundational building block of IEEE 802.11 local area networks (LANs), consisting of multiple STAs. Different types of BSSs have member STAs that form different topologies. For example, in an infrastructure BSS, a special STA acts as the access point to the distributed system (DS). This STA is called an access point STA (AP STA), often referred to as an AP. Other STAs are called non-AP STAs. All non-AP STAs associate with this AP to access the DS, and non-AP STAs are not connected to each other. In an independent BSS, all STAs share the same role and can connect to each other. LANs use hierarchical management. When two STAs interact, data transmitted by STA 1 is transmitted from BSS 1 through the DS to BSS 2, and finally to STA 2. Therefore, when a STA accesses a LAN, it must belong to a specific BSS.

[0127] For Infrastructure BSS, in some scenarios, non-AP STAs need to disconnect from the currently associated AP and reassociate with a new AP, that is, the non-AP STA needs to exit the current BSS and join a new BSS. Therefore, the Basic Service Set Transition Management (BSS transition management, BTM) function is proposed, which is applicable to Infrastructure BSS. If the non-AP STA supports the BTM function, this function can be used to help achieve BSS transition. For example, the AP can send a BSS transition management request (BSS transition management request, BTM request) frame to the non-AP STA that is about to be disassociated, informing them of the upcoming disassociation, and can add information about the APs around the non-AP STA in the BTM request frame to facilitate the non-AP STA to select a new BSS.

[0128] The current technical solution has clearly defined the BSS transition process between a non-AP STA that is not affiliated with any MLD and an AP. It is understandable that for a multi-link device (MLD), there are also scenarios where the non-AP MLD needs to disassociate from the currently associated AP MLD and reassociate with a new AP MLD. For example, refer to Figure 3, which is a schematic diagram of an application scenario provided by an embodiment of the present application. As shown in Figure 3, there are four AP MLDs near the non-AP MLD, namely AP MLD1, AP MLD2, AP MLD3, and AP MLD4. Assume that the current non-AP MLD is associated with AP MLD 1, but the non-AP MLD is about to disassociate from AP MLD 1, so the non-AP MLD needs to select one of the remaining three AP MLDs (AP MLD2, AP MLD3, and AP MLD4) for reassociation. When the non-AP MLD makes a selection, the currently associated AP MLD1 can make a recommendation.

[0129] This application mainly focuses on BSS conversion between non-AP MLD and AP MLD.

[0130] In one possible implementation, the AP MLD can provide information about the AP MLDs surrounding the non-AP MLD to the non-AP MLD via a BTM request frame, and provide a recommendation level for these AP MLDs. Referring to Figure 4 , Figure 4 is a schematic diagram of the frame format of the Action field in the BTM request frame provided in an embodiment of the present application. The Action field of the BTM request frame can be used to carry management information for the BTM request frame. As shown in Figure 4 , the Action field of the BTM request frame can include, but is not limited to, a BSS Transition Candidate List Entries field and a Request Mode field. The following focuses on several of these fields.

[0131] The BSS transition candidate list entry field may include one or more Neighbor Report elements, where a Neighbor Report element may be used to describe (or carry) the preference level for a target BSS candidate or a candidate target AP MLD. Typically, one Neighbor Report element corresponds to one target BSS candidate or candidate target AP MLD. Different Neighbor Report elements may correspond to the same candidate target AP MLD or to different candidate target AP MLDs.

[0132] Refer to Figure 5, which is a schematic diagram of the frame format of the neighbor report element provided in an embodiment of the present application. As shown in Figure 5, the neighbor report element may include but is not limited to: a basic service set identifier (BSS identifier, BSSID) field and an optional sub-element (Optional Subelements) field. Among them, the BSSID field is the MAC address of any AP recommended in the candidate target AP MLD. The optional sub-element field can be used to carry information about the candidate target AP MLD and the degree of recommendation. When the neighbor report element in the BSS conversion candidate list entry field is used for recommendation, the Optional Subelements field can contain the following content:

[0133] (1) The Basic Multi-Link subelement corresponding to the candidate target AP MLD. See Figure 6, which is a schematic diagram of the frame format of the Basic Multi-Link subelement provided in an embodiment of the present application. If the Presence Bitmap field in the Basic Multi-Link subelement shown in Figure 6 is all 0, and there is no Link Info field, then this neighbor report element means "recommending this candidate target AP MLD but not specifically which APs are recommended". If the Link Info field of the Basic Multi-Link subelement shown in Figure 6 has one or more Per-STA Profile subelement (each STA profile subelement), then each Per-STA Profile subelement corresponds to a subsidiary AP recommended in this candidate target AP MLD, then this neighbor report element means "recommending a certain AP combination of this candidate target AP MLD".

[0134] (2) The BSS Transition Candidate Preference Subelement corresponding to the candidate target AP MLD is used to indicate the degree of recommendation of this candidate target AP MLD. For details, please refer to the description of the standard and will not be repeated here. See Figure 7, which is a schematic diagram of the frame format of the BSS transition candidate preference subelement provided in an embodiment of the present application. As shown in Figure 7, the BSS transition candidate preference subelement may include but is not limited to: a preference (Preference) field. The length of the Preference field is 1 byte (equal to 8 bits). When the value of the Preference field is 0, it means "exclude this candidate target AP MLD", that is, tell the non-AP MLD not to associate with the mentioned candidate target AP MLD. When the value of the Preference field is 1 to 255, it indicates the degree of recommendation of this candidate target AP MLD. The value from small to large indicates the degree of recommendation from low to high. The value 255 is "most recommended" and the value 1 is "least recommended".

[0135] In short, the BSS Transition Candidate List Entries field carries one or more Neighbor Report elements. Each Neighbor Report element corresponds to a different candidate target AP MLD or a different AP combination of the same candidate target AP MLD, and provides the recommended value / recommendation level for that candidate target AP MLD. Furthermore, the recommended values ​​for different AP combinations of the same candidate target AP MLD may vary, which is not discussed in this application.

[0136] Refer to Figure 8, which is a schematic diagram of the frame format of the request mode field provided in an embodiment of the present application. As shown in Figure 8, the request mode field includes, but is not limited to, an abridged field. The abridged field can be used to indicate to the recipient of the BTM request frame the intended treatment of BSSIDs or AP MLDs not listed in the BSS Transition Candidate List Entries field (the Abridged (bit 1) field indicates to the recipient of the frame the intended treatment of all BSSIDs or AP MLDs not listed in the BSS Transition Candidate List Entries field.). In the BSS Transition Candidate List Entries field of the present application, the BSSID can be used to identify a single-link site or a traditional site, such as an AP.

[0137] For example, when the value of the Abridged field is 1, it means "exclude (associate with) BSSIDs or AP MLDs that do not appear," that is, it tells the non-AP MLD not to associate with BSSIDs or AP MLDs that do not appear in the BSS Transition Candidate List Entries field. When the value of the Abridged field is 0, it means that the non-AP MLD is neither recommended nor opposed to associating with BSSIDs or AP MLDs that do not appear 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.).

[0138] In summary, the AP MLD currently associated with a non-AP MLD can use the BSS Transition Candidate List Entries field to inform the non-AP MLD of the handling method for the surrounding AP MLDs (i.e., whether to prohibit or oppose association). The predetermined handling method for BSSIDs or AP MLDs not listed in the BSS Transition Candidate List Entries field is indicated by the Abridged field, and the recommendation level of the candidate target AP MLDs listed in the BSS Transition Candidate List Entries field is indicated by the Preference field. However, there is no specification for the handling method for APs listed in the BSS Transition Candidate List Entries field that are not part of the recommended AP combination.

[0139] For example, suppose an AP MLD contains four APs, AP1 through AP4. Suppose the BSSID field in the Neighbor Report element corresponding to this AP MLD is the MAC address of AP2 in the AP MLD, and the Link Info field contains a Per-STA Profile subelement corresponding to AP4 in the AP MLD. In this case, the Neighbor Report element indicates "recommended AP combination for this AP MLD (AP2 and AP4)." Therefore, how to handle AP1 and AP3 in this AP MLD is unclear.

[0140] In view of this, an embodiment of the present application provides an information indication method and device in BTM, which can improve the information indication, clarify the predetermined processing method for APs that are not recommended in the candidate target AP MLD listed in the BSS Transition Candidate List Entries field, and enable the non-AP MLD to more clearly understand the attitude of the currently associated AP MLD and its own behavior.

[0141] The technical solution provided in this application will be described in detail below with reference to more drawings.

[0142] In order to facilitate the clear description of the technical solution of the present application, the present application is described through a plurality of embodiments, and the specific embodiments are as follows. In the present application, unless otherwise specified, the same or similar parts between the various embodiments or implementation methods can refer to each other. In the various embodiments of the present application, and the various implementation methods / implementation methods / implementation methods in the various embodiments, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments and the various implementation methods / implementation methods / implementation methods in the various embodiments are consistent and can be referenced to each other. The technical features in the different embodiments and the various implementation methods / implementation methods / implementation methods in the various embodiments can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The implementation methods of the present application described below do not constitute a limitation on the scope of protection of the present application. It will be understood that the order of the following embodiments does not represent the degree of importance.

[0143] Example 1

[0144] Embodiment 1 of the present application mainly introduces a method for improving information indication by modifying the meaning of the Abridged field in the Request Mode field.

[0145] Refer to Figure 9, which is a flowchart of a first method for indicating information in a BTM according to an embodiment of the present application. As shown in Figure 9, the method for indicating information in a BTM includes but is not limited to the following steps:

[0146] S101. The AP MLD generates 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 simplified field. The simplified field is used to indicate how to handle BSSIDs or AP MLDs that are not listed in the BSS transition candidate list entry field, and how to handle APs that do not appear in any recommended AP combination among the candidate target AP MLDs listed in the BSS transition candidate list entry field.

[0147] S102: The AP MLD sends the BTM request frame, and the non-AP MLD receives the BTM request frame.

[0148] S103: The non-AP MLD parses the BTM request frame. Exemplarily, by parsing the simplified fields in the BTM request frame, the non-AP MLD can obtain a handling method for BSSIDs or AP MLDs not listed in the BSS conversion candidate list entry field, as well as a handling method for APs that are not included in any recommended AP combination among the candidate target AP MLDs listed in the BSS conversion candidate list entry field.

[0149] In one possible implementation, the format of the Action field of the above-mentioned BTM request frame can be as shown in Figure 4 above, which will not be described in detail here. 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. Among them, the BSS Transition Candidate List Entries field includes one or more neighbor report elements, which can be used to describe (or carry) the preference level of the target BSS candidate or candidate target AP MLD. Different neighbor report elements can correspond to different AP combinations of the same candidate target AP MLD. Of course, different neighbor report elements can also correspond to different target BSS candidates or candidate target AP MLDs. The frame format of each neighbor report element can be as shown in Figure 5 above, which will not be described in detail here.

[0150] The frame format of the Request Mode field can be as shown in Figure 8 above, which is not described in detail here. The Request Mode field includes a simplified field (Abridged field). The Abridged field can be used to indicate the processing method for (all) BSSIDs or (all) AP MLDs that are not listed in the BSS Transition Candidate List Entries field, as well as the processing method for APs that do not appear in any recommended AP combination among (all) candidate target AP MLDs listed in the BSS Transition Candidate List Entries field. Alternatively, the Abridged field can be used to indicate the processing method for (all) BSSIDs or (all) AP MLDs that are not listed in the BSS Transition Candidate List Entries field, as well as the processing method for APs that do not appear in the AP combination of candidate target AP MLDs listed in the BSS Transition Candidate List Entries field.

[0151] In this application, "(all) BSSIDs" can mean both BSSID and all BSSIDs. Similarly, "(all) AP MLDs" can mean both AP MLD and all AP MLDs. The same expressions below have the same meaning and are not repeated here.

[0152] In one possible implementation, the length of the Abridged field is 1 bit. When the Abridged field is a first value, it indicates that the sender of the BTM request frame neither recommends nor objects to associating the receiver of the BTM request frame with a BSSID or AP MLD that does not appear in the BSS Transition Candidate List Entries field, and an AP that does not appear in any recommended AP combination among the candidate target AP MLDs in the BSS Transition Candidate List Entries field. When the Abridged field is a second value, it indicates that the sender of the BTM request frame objects to or excludes associating the receiver of the BTM request frame with a BSSID or AP MLD that does not appear in the BSS Transition Candidate List Entries field, and an AP that does not appear in any recommended AP combination among the candidate target AP MLDs in the BSS Transition Candidate List Entries field. The first value may be 0, and the second value may be 1. Of course, the first value may also be 1, and the second value may be 0, which is not limited in this embodiment of the present application.

[0153] It can be understood that if the presence bitmap field in the Basic Multi-Link subelement of a Neighbor Report element is all 0 and there is no Link Info field, it means that all affiliated APs of the candidate target AP MLD corresponding to this Neighbor Report element are recommended.

[0154] It can also be understood that "(all) AP MLDs not listed in the BSS Transition Candidate List Entries field" does not include the AP MLD that sent the BTM request frame. For example, take the application scenario shown in Figure 3 above. Suppose that the current non-AP MLD is associated with AP MLD 1, and AP MLD 1 discovers that the non-AP MLD needs to perform a BSS transition, or the non-AP MLD discovers that it needs to perform a BSS transition. AP MLD1 sends a BTM request frame to the non-AP MLD, carrying information and recommendation levels of AP MLD2, AP MLD3, and AP MLD4. Therefore, "(all) AP MLDs not listed in the BSS Transition Candidate List Entries field" refers to all other AP MLDs in the network except AP MLD1, AP MLD2, AP MLD3, and AP MLD4. Assume that AP MLD 2 has three APs: AP2-1, AP2-2, and AP2-3; AP MLD 3 has two APs: AP3-1 and AP3-2; and AP MLD 4 has two APs: AP4-1 and AP4-2. Furthermore, assume that the BSS Transition Candidate List Entries field includes four neighbor report elements: Neighbor Report Element 1 recommends the combination of AP2-1 and AP2-2 for AP MLD 2; Neighbor Report Element 2 recommends the combination of AP2-2 and AP2-3 for AP MLD 2; Neighbor Report Element 3 recommends AP MLD 3 (that is, all APs belonging to AP MLD 3 are recommended); and Neighbor Report Element 4 recommends AP4-2 for AP MLD 4 (the BSSID field contains AP4-2's MAC address, the Presence Bitmap field is not all zeros, and there is no Link Info field). Then, "APs listed in (all) candidate target AP MLDs in the BSS Transition Candidate List Entries field that do not appear in any recommended AP combination" may include AP4-1. Optionally, for the recommended AP combination {AP2-1, AP2-2}, the handling method for AP2-3 may be default, such as defaulting to opposing association with AP2-3. For the recommended AP combination {AP2-2, AP2-3}, the handling method for AP2-1 may also be default, such as defaulting to opposing association with AP2-1. In other words, for each recommended AP combination, the handling method for APs that do not appear in this recommended AP combination but appear in other AP combinations in the same APMLD may be the default rule.

[0155] In another possible implementation, when the Abridged field is a first value, it indicates that the sender of the BTM request frame neither recommends nor objects to the receiver of the BTM request frame being associated with a BSSID or AP MLD that does not appear in the BSS Transition Candidate List Entries field, or an AP that does not appear in the AP combination of the candidate target AP MLD that appears in the BSS Transition Candidate List Entries field. When the Abridged field is a second value, it indicates that the sender of the BTM request frame objects to or excludes the receiver of the BTM request frame from being associated with a BSSID or AP MLD that does not appear in the BSS Transition Candidate List Entries field, or an AP that does not appear in the AP combination of the candidate target AP MLD that appears in the BSS Transition Candidate List Entries field. The first value can be 0, and the second value can be 1. Of course, the first value can also be 1, and the second value can be 0, and this is not limited in the embodiment of the present application.

[0156] For example, consider the application scenario shown in Figure 3. Assume that the current non-AP MLD is associated with AP MLD 1, and AP MLD 1 discovers that the non-AP MLD needs to perform a BSS transition, or that the non-AP MLD itself needs to perform a BSS transition. AP MLD 1 sends a BTM request frame to the non-AP MLD, carrying information about AP MLD 2 and its recommendation level. Assume that AP MLD 2 has three APs: AP2-1, AP2-2, and AP2-3. Furthermore, assume that the BSS Transition Candidate List Entries field includes two neighbor report elements. Neighbor report element 1 recommends the AP MLD 2 combination of AP2-1 and AP2-2, while neighbor report element 2 recommends the AP MLD 2 combination of AP2-2 and AP2-3. If AP2-3 is not in the recommended AP combination {AP2-1, AP2-2}, then when the Abridged field is set to 1, association with BSSIDs or AP MLDs that do not appear in the BSS Transition Candidate List Entries field is excluded. Furthermore, if the non-AP MLD selects the AP combination {AP2-1, AP2-2}, association with AP2-3 is excluded. If the Abridged field is set to 0, association with BSSIDs or AP MLDs that do not appear in the BSS Transition Candidate List Entries field is neither recommended nor opposed. Furthermore, if the non-AP MLD selects the AP combination {AP2-1, AP2-2}, association with AP2-3 is neither recommended nor opposed. If AP2-1 is not in the recommended AP combination {AP2-2, AP2-3}, then when the Abridged field is set to 1, association with BSSIDs or AP MLDs that do not appear in the BSS Transition Candidate List Entries field is excluded. Furthermore, if the non-AP MLD selects the AP combination {AP2-2, AP2-3}, association with AP2-1 is excluded. If the Abridged field is set to 0, association with BSSIDs or AP MLDs that do not appear in the BSS Transition Candidate List Entries field is neither recommended nor opposed. Furthermore, if the non-AP MLD selects the AP combination {AP2-2, AP2-3}, association with AP2-1 is neither recommended nor opposed.

[0157] In one possible implementation, the BSS Transition Candidate Preference subelement of the BSS Transition Candidate List Entries field includes a Preference field. Exemplarily, the meaning of the Preference field may continue to use the existing meaning, or the meaning of the Preference field may change as the standard evolves, which is not limited in the embodiments of the present application. Alternatively, the Preference field may be used to indicate the degree of recommendation of an AP combination. The AP combination may be an AP combination recommended by a neighbor report element to which the Preference field belongs. In other words, this AP combination is an AP combination recommended by a candidate target AP MLD listed in the BSS Transition Candidate List Entries field.

[0158] This embodiment of the present application expands the meaning of the Abridged field to simultaneously indicate how to handle BSSIDs or AP MLDs not listed in the BSS Transition Candidate List Entries field, and how to handle APs that do not appear in the candidate target AP MLDs listed in the BSS Transition Candidate List Entries field. This improves information indication, clarifies how APs are handled in the MLD, and enables the non-AP MLD to more clearly understand the attitude of the currently associated AP MLD and its own behavior. Furthermore, this embodiment of the present application is clear in meaning, does not increase overhead, and has good compatibility.

[0159] Furthermore, the embodiment of the present application also changes the meaning of the Preference field so that the neighbor report element can indicate the recommendation degree of a certain AP combination when recommending the AP MLD.

[0160] Example 2

[0161] The second embodiment of the present application mainly introduces a method for improving information indication by using the reserved bits in the Request Mode field.

[0162] Referring to Figure 10, Figure 10 is a second flow chart of the information indication method in the BTM provided by the embodiment of the present application. As shown in Figure 10, the information indication method in the BTM includes but is not limited to the following steps:

[0163] S201. The AP MLD generates 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 simplified extension field. The simplified extension field is used to indicate how to handle APs that are listed in the BSS transition candidate list entry field but do not appear in any recommended AP combination among the candidate target AP MLDs.

[0164] S202: The AP MLD sends the BTM request frame, and the non-AP MLD receives the BTM request frame.

[0165] S203: The non-AP MLD parses the BTM request frame. Exemplarily, by parsing the simplified extension field in the BTM request frame, the non-AP MLD can obtain a handling method for APs listed in the candidate target AP MLD field in the BSS transition candidate list that are not included in any recommended AP combination. Furthermore, by parsing the simplified field in the BTM request frame, the non-AP MLD can obtain a predetermined handling method for BSSIDs or AP MLDs not listed in the BSS transition candidate list field.

[0166] In one possible implementation, the format of the Action field of the above-mentioned BTM request frame can be as shown in Figure 4 above, which will not be described in detail here. 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. Among them, the BSS Transition Candidate List Entries field includes one or more neighbor report elements, which can be used to describe (or carry) the preference level of the target BSS candidate or candidate target AP MLD. Different neighbor report elements can correspond to different AP combinations of the same candidate target AP MLD. Of course, different neighbor report elements can also correspond to different target BSS candidates or candidate target AP MLDs. The frame format of each neighbor report element can be as shown in Figure 5 above, which will not be described in detail here.

[0167] The Request Mode field can include an Abridged field and an Abridged Extension field. The Abridged field can be used to indicate to the recipient of the BTM request frame the intended treatment of all BSSIDs or AP MLDs not listed in the BSS Transition Candidate List Entries field. The Abridged (bit 1) field indicates to the recipient of the frame the intended treatment of all BSSIDs or AP MLDs not listed in the BSS Transition Candidate List Entries field. The Abridged Extension field can be used to indicate to the recipient of the BTM request frame the treatment of APs that do not appear in any recommended AP combination among (all) candidate target AP MLDs listed in the BSS Transition Candidate List Entries field. Alternatively, the Abridged Extension field can be used to indicate to the recipient of the BTM request frame the treatment of APs that do not appear in the AP combination of candidate target AP MLDs listed in the BSS Transition Candidate List Entries field.

[0168] Among them, the specific meanings of "(all) AP MLDs not listed in the BSS Transition Candidate List Entries field", "APs that do not appear in any recommended AP combination among (all) candidate target AP MLDs listed in the BSS Transition Candidate List Entries field", and "handling method for APs that do not appear in the AP combination of candidate target AP MLDs listed in the BSS Transition Candidate List Entries field" can be found in the description of the aforementioned embodiment 1 and will not be repeated here.

[0169] It can be understood that the "Abridged Extension field" in the embodiment of the present application can also have other names, such as "Extension Abridged field", or the first field, etc., and the embodiment of the present application does not limit this.

[0170] For example, see Figure 11, which is a schematic diagram of another frame format for the Request Mode field provided in an embodiment of the present application. As shown in Figure 11, a reserved bit in the Request Mode field can be used as a simplified extension field. When the Abridged Extension field is a third value, it indicates that the sender of the BTM request frame neither recommends nor objects to the receiver of the BTM request frame associating with an AP that is not included in any recommended AP combination among the candidate target AP MLDs 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 objects to or excludes the receiver of the BTM request frame from associating with an AP that is not included in any recommended AP combination among the candidate target AP MLDs in the BSS Transition Candidate List Entries field. Alternatively, when the Abridged Extension field is a third value, it indicates that the sender of the BTM request frame neither recommends nor objects to the receiver of the BTM request frame associating with an AP that is not included in a particular AP combination among the candidate target AP MLDs in the BSS Transition Candidate List Entries field. When the Abridged Extension field is the fourth value, it indicates that the sender of the BTM request frame objects to or excludes the receiver of the BTM request frame from associating with an AP combination that does not appear in a candidate target AP MLD in the BSS Transition Candidate List Entries field when selecting the AP combination.

[0171] Among them, the third value can be 0 or 1; correspondingly, the fourth value can be 1 or 0; this embodiment of the present application does not limit this.

[0172] It is understood that the value and meaning of the Abridged field in the Request Mode field shown in Figure 11 above can remain unchanged. When the Abridged field is a first value (e.g., 0), it indicates that the sender of the BTM request frame neither recommends nor objects to the association of the receiver of the BTM request frame with a BSSID or AP MLD that does not appear in the BSS Transition Candidate List Entries field. When the Abridged field is a second value (e.g., 1), it indicates that the sender of the BTM request frame objects to or excludes the association of the receiver of the BTM request frame with a BSSID or AP MLD that does not appear in the BSS Transition Candidate List Entries field.

[0173] It can also be understood that the length of the simplified extension field in Figure 11 above can be 1 bit or more bits, which is not limited in the embodiment of the present application.

[0174] This embodiment utilizes reserved bits in the Request Mode field to indicate the handling method for APs that are not listed in the candidate target AP MLDs in the BSS Transition Candidate List Entries field. This improves the information indication and allows the non-AP MLD to more clearly understand the attitude of the currently associated AP MLD and its own behavior. Furthermore, this embodiment does not modify the meaning of the Abridged field, but instead uses additional bits to supplement the explanation, providing clear logic and easier understanding for the non-AP MLD. Furthermore, the additional bits appear simultaneously with the existing Abridged field, maintaining a neat logic.

[0175] Example 3

[0176] Embodiment 3 of the present application mainly introduces the modification of the meaning of the Abridged field so that it can indicate the processing method of the AP combination that is not recommended in the AP MLD appearing in the BSS transition candidate list entry field.

[0177] Refer to Figure 12, which is a schematic diagram of a third flow chart of the information indication method in the BTM provided by the embodiment of the present application. As shown in Figure 12, the information indication method in the BTM includes but is not limited to the following steps:

[0178] S301: The AP MLD generates 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 simplified field. The simplified field is used to indicate how to handle BSSIDs or AP MLDs not listed in the BSS transition candidate list entry field, and how to handle AP combinations that are not recommended in the candidate target AP MLDs listed in the BSS transition candidate list entry field.

[0179] S302: The AP MLD sends the BTM request frame, and the non-AP MLD receives the BTM request frame.

[0180] S303: The non-AP MLD parses the BTM request frame. Exemplarily, by parsing the simplified fields in the BTM request frame, the non-AP MLD can obtain a handling method for BSSIDs or AP MLDs not listed in the BSS transition candidate list entry field, and a handling method for AP combinations not recommended by the candidate target AP MLDs listed in the BSS transition candidate list entry field.

[0181] In one possible implementation, the format of the Action field of the above-mentioned BTM request frame can be as shown in Figure 4 above, which will not be described in detail here. 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. Among them, the BSS Transition Candidate List Entries field includes one or more neighbor report elements, which can be used to describe (or carry) the preference level of the target BSS candidate or candidate target AP MLD. Different neighbor report elements can correspond to different AP combinations of the same candidate target AP MLD. Of course, different neighbor report elements can also correspond to different target BSS candidates or candidate target AP MLDs. The frame format of each neighbor report element can be as shown in Figure 5 above, which will not be described in detail here.

[0182] The frame format of the Request Mode field can be as shown in Figure 8 above and is not further described here. The Request Mode field includes a simplified field (Abridged field). The Abridged field can be used to indicate the handling method for (all) BSSIDs or (all) AP MLDs not listed in the BSS Transition Candidate List Entries field, as well as the handling method for AP combinations that are not recommended among (all) candidate target AP MLDs listed in the BSS Transition Candidate List Entries field.

[0183] It can be understood that the specific meaning of “(all) AP MLDs not listed in the BSS Transition Candidate List Entries field” can be found in the description of the aforementioned embodiment 1, which will not be repeated here.

[0184] The meaning of "no AP combination recommended by (all) candidate AP MLDs listed in the BSS Transition Candidate List Entries field" can be illustrated with an example. An "AP combination" can include one or more APs. In other words, a single AP can also be considered an AP combination, as can all APs belonging to an AP MLD. Taking the application scenario shown in Figure 3 as an example, assume that the current non-AP MLD is associated with AP MLD 1. AP MLD 1 discovers that the non-AP MLD requires a BSS transition, or that the non-AP MLD itself requires a BSS transition. AP MLD 1 sends a BTM request frame to the non-AP MLD, carrying information and recommendation levels for AP MLD 2, AP MLD 3, and AP MLD 4. Assume that AP MLD 2 has three APs: AP2-1, AP2-2, and AP2-3; AP MLD 3 has two APs: AP3-1 and AP3-2; and AP MLD 4 has two APs: AP4-1 and AP4-2. Furthermore, assuming that the BSS Transition Candidate List Entries field includes a total of three neighbor report elements, neighbor report element 1 recommends the combination of AP2-1 and AP2-2 of AP MLD 2, neighbor report element 2 recommends AP MLD 3 (that is, all subordinate APs of AP MLD 3 are recommended), and neighbor report element 3 recommends AP4-2 of AP MLD 4. Then, the "AP combination not recommended among (all) candidate target AP MLDs listed in the BSS Transition Candidate List Entries field" includes: {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}, {AP4-1, AP4-2}. Of course, an "AP combination" may also include two or more APs, and this embodiment of the present application is not limiting.

[0185] In one possible implementation, the length of the Abridged field is 1 bit. When the Abridged field is a first value, it indicates that the sender of the BTM request frame neither recommends nor objects to associating the receiver of the BTM request frame with a BSSID or AP MLD that does not appear in the BSS Transition Candidate List Entries field, or an AP combination that is not recommended in the candidate target AP MLDs that appear in the BSS Transition Candidate List Entries field. When the Abridged field is a second value, it indicates that the sender of the BTM request frame objects to or excludes associating the receiver of the BTM request frame with a BSSID or AP MLD that does not appear in the BSS Transition Candidate List Entries field, or an AP combination that is not recommended in the candidate target AP MLDs that appear in the BSS Transition Candidate List Entries field.

[0186] The first value may be 0, and the second value may be 1. Of course, the first value may also be 1, and the second value may be 0, which is not limited in the embodiment of the present application.

[0187] In one possible implementation, the BSS Transition Candidate Preference subelement of the BSS Transition Candidate List Entries field includes a Preference field. Exemplarily, the meaning of the Preference field may follow the existing meaning, or the meaning of the Preference field may change as the standard evolves; this is not limited in the embodiments of the present application. Alternatively, the Preference field may be used to indicate the degree of recommendation of an AP combination. The AP combination may be an AP combination recommended by a neighbor report element to which the Preference field belongs. That is, this AP combination is an AP combination recommended by a target AP MLD listed in the BSS Transition Candidate List Entries field.

[0188] This embodiment of the present application expands the meaning of the Abridged field to simultaneously indicate how to handle BSSIDs or AP MLDs not listed in the BSS Transition Candidate List Entries field, and how to handle AP combinations that are not recommended by the candidate target AP MLDs listed in the BSS Transition Candidate List Entries field. This improves the information indication, allowing the non-AP MLD to more clearly identify the attitude of the currently associated AP MLD and its own behavior. Furthermore, this embodiment of the present application is clear in meaning, does not increase overhead, and has good compatibility.

[0189] Furthermore, the embodiment of the present application also changes the meaning of the Preference field so that the neighbor report element can indicate the recommendation degree of a certain AP combination when recommending the AP MLD.

[0190] Example 4

[0191] Embodiment 4 of the present application mainly introduces a method for improving information indication by using bits in a neighbor report element.

[0192] See Figure 13, which is a fourth flow chart of the information indication method in the BTM provided by the embodiment of the present application. As shown in Figure 13, the information indication method in the BTM includes but is not limited to the following steps:

[0193] S401, AP MLD generates a BTM request frame, which includes one or more neighbor report elements, where one neighbor report element is used to carry information about a candidate target AP MLD. The neighbor report element includes second indication information, which is used to indicate a processing method for an AP that does not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs.

[0194] S402: The AP MLD sends the BTM request frame, and the non-AP MLD receives the BTM request frame.

[0195] S403: The non-AP MLD parses the BTM request frame. Exemplarily, by parsing the second indication information in the BTM request frame, the non-AP MLD can obtain a processing method for APs that are not included in the AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs.

[0196] In one possible implementation, the format of the Action field of the above-mentioned BTM request frame can be as shown in Figure 4 above, which will not be described in detail here. The Action field of the BTM request frame may include but is not limited to: BSS Transition Candidate List Entries field. Among them, the BSS Transition Candidate List Entries field includes one or more neighbor report elements, and a neighbor report element can be used to describe (or carry) the preference level of a target BSS candidate or candidate target AP MLD. Different neighbor report elements can be used to describe (or carry) the preference level of the same candidate target AP MLD. Of course, different neighbor report elements can also be used to describe (or carry) the preference levels of different target BSS candidates or candidate target AP MLDs. The frame format of each neighbor report element can be as shown in Figure 5 above, which will not be described in detail here.

[0197] In one possible implementation, each neighbor report element includes a second indication information, which can be used to indicate how to handle APs that do not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs. Since each neighbor report element corresponds to one candidate target AP MLD, the second indication information can be briefly described as indicating how to handle APs that do not appear in a certain AP combination of a certain candidate target AP MLD. It is understood that an "AP combination" can include one or more APs. In other words, a single AP can also be considered an AP combination, and all APs belonging to an AP MLD can also be considered an AP combination.

[0198] For example, using the scenario shown in Figure 3, assume that the current non-AP MLD is associated with AP MLD 1. AP MLD 1 discovers that the non-AP MLD requires a BSS transition, or that the non-AP MLD itself requires a BSS transition. AP MLD 1 sends a BTM request frame to the non-AP MLD, carrying information about AP MLD 2 and its recommendation level. Assume that AP MLD 2 has three APs: AP2-1, AP2-2, and AP2-3. The BSS Transition Candidate List Entries field includes a Neighbor Report element. The BSSID field of this Neighbor Report element contains the MAC address of AP2-1 in AP MLD 2, and the Link Info field contains a Per-STA Profile subelement corresponding to AP2-2 in AP MLD 2. Therefore, this Neighbor Report element recommends the combination of AP2-1 and AP2-2 for AP MLD 2. At this time, the second indication information in the neighbor report element is used to indicate a processing method for AP2-3 that does not appear in the combination of AP2-1 and AP2-2 in AP MLD2 carried by the neighbor report element.

[0199] In one possible implementation, when the second indication information is a first value, it indicates that the sender of the BTM request frame neither recommends nor objects to the receiver of the BTM request frame associating with an AP that does not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs. When the second indication information is a second value, it indicates that the sender of the BTM request frame objects to or excludes the receiver of the BTM request frame from associating with an AP that does not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs. The first value may be 1 or 0; correspondingly, the second value may be 0 or 1; this is not limited in the embodiment of the present application.

[0200] In one possible implementation, the above-mentioned second indication information can be carried in the BSSID information field of the neighbor report element. Exemplarily, the second indication information can be represented by a reserved bit in the BSSID information field. Alternatively, the Extremely High Throughput bit in the BSSID information field can be reused to indicate the processing method for APs that do not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element. See Figure 14, which is a schematic diagram of the frame format of the BSSID information field provided in an embodiment of the present application. As shown in Figure 14, a reserved bit in the BSSID information field can be used as the second indication information. When the value of the second indication information is 1, it indicates that the sender of the BTM request frame opposes or excludes the receiver of the BTM request frame from associating with the AP that does not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which this second indication information belongs. When the value of the second indication information is 0, it indicates that the sender of the BTM request frame neither recommends nor objects the receiver of the BTM request frame to associate with an AP that does not appear in the AP combination of the candidate target AP MLD carried in the neighbor report element to which the second indication information belongs.

[0201] It can be understood that Figure 14 is only an example. The embodiment of the present application does not limit the bit length of the second indication information, nor does it limit the correspondence between the value and meaning of the second indication information.

[0202] In an embodiment of the present application, a reserved bit is used in the BSSID information field of the Neighbor Report element to indicate a processing method for APs that do not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element. Each AP combination recommended in the candidate target AP MLD can have its own processing method, which is flexible to use.

[0203] In another possible implementation, the above-mentioned second indication information can be carried in the BSS conversion candidate preference sub-element of the neighbor report element. Exemplarily, since the existing BSS conversion candidate preference sub-element is not extensible, the length of the Preference field can be shortened so that the length of the Preference field is less than or equal to 7 bits, but the meaning of the Preference field is not changed; and the one or more bits saved by shortening the Preference field are used to represent the second indication information. In other words, the Preference field in the BSS conversion candidate preference sub-element is less than or equal to 7 bits, the bit length of the second indication information is greater than or equal to 1 bit, and the sum of the length of the Preference field and the bit length of the second indication information is less than or equal to 1 byte (8 bits). It can be understood that the embodiment of the present application does not limit the meaning of the Preference field, but only changes the length of the Preference field. The meaning of the Preference field can change as the standard evolves.

[0204] Refer to Figure 15, which is a schematic diagram of another frame format of the BSS transition candidate preference sub-element provided in an embodiment of the present application. As shown in Figure 15, the length of the Preference field can be shortened from 1 byte (8 bits in total) to 7 bits, and the saved 1 bit can be used as the second indication information. For example, the least significant bit (LSB) of this 1 byte (B0 to B7), namely B0, can be used as the second indication information. When the value of the second indication information (such as B0) is 0, it indicates that the sender of the BTM request frame opposes or excludes the receiver of the BTM request frame from associating with an AP that does not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which this second indication information belongs. When the value of the second indication information (such as B0) is 1, it indicates that the sender of the BTM request frame neither recommends nor opposes the receiver of the BTM request frame from associating with an AP that does not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which this second indication information belongs. This provides better compatibility with traditional sites (i.e., single-link sites).

[0205] It can be understood that Figure 15 is only an example. The embodiment of the present application does not limit the bit length of the second indication information, nor does it limit the correspondence between the value and meaning of the second indication information.

[0206] In this embodiment of the present application, a second indication is included in the BSS Transition Candidate Preference sub-element of the Neighbor Report element to indicate how to handle APs that are not included in the AP combination of the candidate target AP MLD carried by the Neighbor Report element. This allows for a unique handling method for each AP combination recommended in the candidate target AP MLD, providing flexibility. Furthermore, the second indication is used simultaneously with the Preference value; that is, the second indication will not appear if the Neighbor Report element is not used for recommendation.

[0207] In a possible implementation, the BSS transition candidate preference sub-element of the neighbor report element includes a Preference field. The meaning of the Preference field can be found in the related description in the above embodiment 1, which will not be repeated here.

[0208] In the embodiment of the present application, the neighbor report element carries the second indication information to indicate the processing method of the AP that does not appear in a certain AP combination in the single candidate target AP MLD, so that each recommended AP combination can have its own processing method, which is flexible to use.

[0209] Example 5

[0210] The fifth embodiment of the present application mainly introduces a method for improving information indication by redefining the recommended AP combination in the Link Info field.

[0211] See Figure 16, which is a fifth flow chart of the information indication method in the BTM provided by the embodiment of the present application. As shown in Figure 16, the information indication method in the BTM includes but is not limited to the following steps:

[0212] S501: The AP MLD generates a BTM request frame. The BTM request frame includes one or more neighbor report elements, wherein one neighbor report element is used to carry information about a candidate target AP MLD. The neighbor report element includes a per-STA profile sub-element of any non-barred AP in the candidate target AP MLD. Optionally, the per-STA profile sub-element also includes third indication information, which may be used to indicate a processing method for the AP corresponding to the per-STA profile sub-element.

[0213] S502: The AP MLD sends the BTM request frame, and the non-AP MLD receives the BTM request frame.

[0214] S503: The non-AP MLD parses the BTM request frame. Exemplarily, by parsing the Neighbor Report element in the BTM request frame, the non-AP MLD obtains information about APs that are not prohibited in the candidate AP MLD. Furthermore, by parsing the per-STA profile sub-element in the Neighbor Report element, the non-AP MLD obtains the AP processing method corresponding to the per-STA profile sub-element.

[0215] In one possible implementation, the format of the Action field of the above-mentioned BTM request frame can be as shown in Figure 4 above, which will not be described in detail here. The Action field of the BTM request frame may include but is not limited to: BSS Transition Candidate List Entries field. Among them, the BSS Transition Candidate List Entries field includes one or more neighbor report elements, and a neighbor report element can be used to describe (or carry) the preference level of a target BSS candidate or candidate target AP MLD. Different neighbor report elements can be used to describe (or carry) the preference level of the same candidate target AP MLD. Of course, different neighbor report elements can also be used to describe (or carry) the preference levels of different target BSS candidates or candidate target AP MLDs. The frame format of each neighbor report element can be as shown in Figure 5 above, which will not be described in detail here.

[0216] A neighbor report element may include a basic multi-link subelement (Basic Multi-Link subelement) corresponding to a candidate target AP MLD. The frame format of the Basic Multi-Link subelement may be as shown in Figure 6 above, which will not be repeated here. It can be understood that if the AP MLD wants to recommend a certain AP combination of a candidate target AP MLD to the non-AP MLD, it is necessary to add the Neighbor Report element of any AP in the AP combination to the BSS Transition Candidate List Entries field (that is, the BSSID field of the Neighbor Report element is the MAC address of any AP in the AP combination), and add the Basic Multi-Link subelement to this Neighbor Report element. The Per-STA Profile subelement of other APs in the AP combination will be added to the Link Info field of this Basic Multi-Link subelement. In short, the Link Info field carries the Per-STA Profile subelement of other APs in the recommended AP combination except the AP indicated by the BSSID field.

[0217] In an embodiment of the present application, if the AP MLD is to recommend an AP combination of a candidate target AP MLD to the non-AP MLD, the BSSID field of the Neighbor Report element remains the MAC address of any AP in the AP combination. However, the Link Info field of the Basic Multi-Link subelement includes the Per-STA Profile subelement of any non-prohibited (associated) AP in the candidate target AP MLD. Optionally, each Per-STA Profile subelement also includes third indication information. The third indication information can be used to indicate how to handle the AP corresponding to the Per-STA Profile subelement. A Per-STA Profile subelement corresponds to a non-prohibited AP in the candidate target AP MLD. Here, "non-prohibited" can include at least two meanings: "recommended" and "neither recommended nor opposed." This embodiment of the present application also assumes that APs not appearing in the Neighbor Report element are prohibited from association. Here, "APs not appearing in the Neighbor Report element" can refer to APs in the candidate target AP MLD carried by the Neighbor Report element, excluding the APs indicated by the BSSID field and the APs corresponding to the Per-STA Profile subelement.

[0218] In one possible implementation, when the third indication information in a certain Per-STA Profile subelement is a first value, it indicates that the sender of the above-mentioned BTM request frame neither recommends nor objects to the receiver of the BTM request frame being associated with the AP corresponding to the Per-STA Profile subelement. When the third indication information in a certain Per-STA Profile subelement is a second value, it indicates that the sender of the above-mentioned BTM request frame recommends that the receiver of the BTM request frame be associated with the AP corresponding to the Per-STA Profile subelement. The first value can be 0 or 1; correspondingly, the second value can be 1 or 0; this is not limited in the embodiment of the present application.

[0219] In one possible implementation, the third indication information may be carried in the STA control field of the Per-STA Profile subelement. Exemplarily, a reserved bit in the STA Control field of the Per-STA Profile subelement may be used to represent the third indication information. Referring to FIG. 17 , FIG. 17 is a schematic diagram of the frame format of the STA Control field provided in an embodiment of the present application. For ease of description, FIG. 17 refers to the third indication information as a Recommended field. It is understood that in actual applications, the third indication information may have other field names, which are not limited in the embodiment of the present application. As shown in FIG. 17 , the STA Control field includes, but is not limited to, a Recommended field. For example, the length of the Recommended field is 1 bit. When the value of the Recommended field is 1, it indicates that the AP MLD recommends that the non-AP MLD be associated 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, it indicates that the AP MLD neither recommends nor opposes the non-AP MLD being associated with the AP corresponding to the Per-STA Profile subelement to which the Recommended field belongs. It is understood that the embodiment of the present application does not limit whether the value of the Recommended field is 1 or 0. Figure 17 is only an example, and the embodiment of the present application does not limit the length of the Recommended field.

[0220] In this embodiment of the present application, APs not appearing in the Neighbor Report element are prohibited from association by default. APs corresponding to the Per-STA Profile subelement that appears indicate whether association is recommended through third indication information. Because association preference information appears in the Per-STA Profile subelement corresponding to each AP, each AP in each AP combination provided by AP MLD can have its own processing method, providing great flexibility.

[0221] Example 6

[0222] The sixth embodiment of the present application mainly introduces a default processing method for an AP that does not appear in the candidate target AP MLD listed in the BSS Transition Candidate List Entries field.

[0223] See Figure 18, which is a sixth flow chart of the information indication method in the BTM provided by the embodiment of the present application. As shown in Figure 18, the information indication method in the BTM includes but is not limited to the following steps:

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

[0225] S602: The AP MLD sends the BTM request frame, and the non-AP MLD receives the BTM request frame.

[0226] S603: The non-AP MLD parses the BTM request frame.

[0227] In one possible implementation, the format of the Action field of the BTM request frame may be as shown in FIG4 above, which is not described in detail here. 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. The frame format of the Request Mode field may be as shown in FIG8 above, which is not described in detail here. The Request Mode field includes an Abridged field. The Abridged field may be used to indicate the processing method for (all) BSSIDs or (all) AP MLDs that are not listed in the BSS Transition Candidate List Entries field. The processing method for APs that do not appear in any recommended AP combination among the (all) candidate target AP MLDs listed in the BSS Transition Candidate List Entries field may use the default rule.

[0228] In one possible implementation, the default rule may include any of the following: excluding / opposing association with APs that are not recommended in the candidate target AP MLD that appears in the BSS Transition Candidate List Entries field; neither recommending nor opposing association with APs that are not recommended in the candidate target AP MLD that appears in the BSS Transition Candidate List Entries field; and the non-AP MLD must treat APs that are not recommended in the AP MLD that appears in the BSS Transition Candidate List Entries field as having a specific preference value, such as 1. Here, "non-recommended APs" may refer to "APs that do not appear in any recommended AP combination" or "APs that do not appear in a recommended AP combination."

[0229] This embodiment of the present application improves information indication by designing a default handling method for APs that are not listed in the candidate target AP MLDs in the BSS Transition Candidate List Entries field. This allows the non-AP MLD to better understand the attitude of the currently associated AP MLD and its own behavior. Furthermore, this embodiment of the present application does not modify the fields in the BTM request frame, thus adding no overhead.

[0230] The above content elaborates on the method provided by the present application. In order to facilitate the implementation of the above scheme of the embodiment of the present application, the embodiment of the present application also provides corresponding devices or equipment.

[0231] Based on the above-mentioned method embodiment, this application divides the AP MLD and non-AP MLD into functional modules. For example, each functional module can be divided into corresponding functional modules, or two or more functions can be integrated into a single processing module. The integrated modules can be implemented as either hardware or software functional modules. It should be noted that the module division in this application is illustrative and represents only a logical functional division. In actual implementation, other division methods may be used. The AP MLD and non-AP MLD of the present embodiment are described in detail below with reference to Figures 19 to 21.

[0232] Referring to Figure 19 , Figure 19 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. As shown in Figure 19 , the communication device includes a transceiver unit 10 and a processing unit 20. The transceiver unit 10 can implement corresponding communication functions, and the processing unit 20 is used to process data. For example, the transceiver unit 10 can also be referred to as a communication interface or a communication unit.

[0233] In some embodiments of the present application, the communication device may be the AP MLD described above. Specifically, the communication device shown in Figure 19 may be used to execute the steps or functions performed by the AP MLD in the method embodiments described above. For example, the communication device may be an AP MLD or a chip or functional module configured within the AP MLD, but this is not limited in the present application. The transceiver unit 10 is used to execute the AP MLD's transceiver-related operations described in the method embodiments described above, and the processing unit 20 is used to execute the AP MLD's processing-related operations described in the method embodiments described above.

[0234] Exemplarily, the processing unit 20 is used to generate a BTM request frame, which includes a BSS conversion candidate list entry field and first indication information, wherein the first indication information is used to indicate a processing method for a BSSID or AP MLD that is not listed in the BSS conversion candidate list entry field, and a processing method for an AP that does not appear in any recommended AP combination among the candidate target AP MLD listed in the BSS conversion candidate list entry field; the transceiver unit 10 is used to send or output the BTM request frame.

[0235] It is understood that the transceiver unit 10 can send the BTM request frame to other communication devices, or the transceiver unit 10 can output the BTM request frame from the processing unit 20 to other components or other functional modules in the AP MLD. The description of other information output by the transceiver unit is similar and will not be detailed below.

[0236] It is understandable that for the specific description of the BTM request frame, the BSS conversion candidate list entry field, and the first indication information, reference may be made to the method embodiment 1 or 2 shown above, and will not be described in detail here.

[0237] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiments of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above-mentioned method embodiments one or two (such as Figure 9 or Figure 10), which will not be described in detail here.

[0238] Exemplarily, the processing unit 20 is used to generate a BTM request frame, which includes a BSS conversion candidate list entry field and a request mode field, the request mode field includes a simplified field, and the simplified field is used to indicate the processing method of the BSSID or AP MLD not listed in the BSS conversion candidate list entry field, and the processing method of the AP combination that is not recommended in the candidate target AP MLD listed in the BSS conversion candidate list entry field; the transceiver unit 10 is used to send or output the BTM request frame.

[0239] It is understandable that the specific description of the BTM request frame, the BSS conversion candidate list entry field, the request mode field, and the simplified field, etc. can be referred to the method embodiment 3 shown above, and will not be described in detail here.

[0240] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above-mentioned method embodiment three (such as Figure 12), which will not be described in detail here.

[0241] Exemplarily, the processing unit 20 is used to generate a BTM request frame, which includes one or more neighbor report elements, one of which is used to carry information about a candidate target AP MLD, and the neighbor report element includes second indication information, which is used to indicate a processing method for an AP that does not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs; the transceiver unit 10 is used to send or output the BTM request frame.

[0242] It is understandable that for the specific description of the BTM request frame, the neighbor report element, and the second indication information, reference may be made to the fourth method embodiment shown above, and will not be described in detail here.

[0243] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above-mentioned method embodiment 4 (such as Figure 13), which will not be described in detail here.

[0244] Exemplarily, the processing unit 20 is used to generate a BTM request frame, which includes one or more neighbor report elements, wherein one neighbor report element is used to carry information of a candidate target AP MLD, and the neighbor report element includes a per-STA profile sub-element of any non-prohibited AP in the candidate target AP MLD; the transceiver unit 10 is used to send or output the BTM request frame.

[0245] It is understandable that for the specific description of the BTM request frame, neighbor report element, and per-STA profile sub-element, etc., reference can be made to the method embodiment 5 shown above, and they will not be described in detail here.

[0246] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above-mentioned method embodiment 5 (such as Figure 16), which will not be described in detail here.

[0247] Referring to Figure 19 , in some other embodiments of the present application, the communication device may be the non-AP MLD shown above. Specifically, the communication device shown in Figure 19 may be used to execute the steps or functions performed by the non-AP MLD in the method embodiments described above. Exemplarily, the communication device may be a non-AP MLD or a chip or functional module configured within a non-AP MLD, but this is not limited in the present embodiment. The transceiver unit 10 is used to execute the non-AP MLD's transceiver-related operations described in the method embodiments described above, and the processing unit 20 is used to execute the non-AP MLD's processing-related operations described in the method embodiments described above.

[0248] Exemplarily, the transceiver unit 10 is used to receive or input a BTM request frame, which includes a BSS conversion candidate list entry field and first indication information, wherein the first indication information is used to indicate a processing method for a BSSID or AP MLD that is not listed in the BSS conversion candidate list entry field, and a processing method for an AP that does not appear in any recommended AP combination among the candidate target AP MLDs listed in the BSS conversion candidate list entry field; the processing unit 20 is used to parse the BTM request frame.

[0249] It is understood that the transceiver unit 10 may receive the BTM request frame from other communication devices, or the transceiver unit 10 may input the BTM request frame from other components or other functional modules in the AP MLD. The description of other information input by the transceiver unit is similar and will not be detailed below.

[0250] It is understandable that the specific description of the BTM request frame, the BSS conversion candidate list entry field, and the first indication information, etc. can be referred to the method embodiment 1 or 2 shown above, and will not be described in detail here.

[0251] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiments of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above-mentioned method embodiments one or two (such as Figure 9 or Figure 10), which will not be described in detail here.

[0252] Exemplarily, the transceiver unit 10 is used to receive or input a BTM request frame, which includes a BSS conversion candidate list entry field and a request mode field, the request mode field including a simplified field, the simplified field being used to indicate a processing method for a BSSID or AP MLD that is not listed in the BSS conversion candidate list entry field, and a processing method for an AP combination that is not recommended in the candidate target AP MLD listed in the BSS conversion candidate list entry field; the processing unit 20 is used to parse the BTM request frame.

[0253] It is understandable that the specific description of the BTM request frame, the BSS conversion candidate list entry field, the request mode field, and the simplified field, etc. can be referred to the method embodiment 3 shown above, and will not be described in detail here.

[0254] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above-mentioned method embodiment three (such as Figure 12), which will not be described in detail here.

[0255] Exemplarily, the transceiver unit 10 is used to receive or input a BTM request frame, which includes one or more neighbor report elements, one of which is used to carry information about a candidate target AP MLD, and the neighbor report element includes second indication information, which is used to indicate a processing method for an AP that does not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs; the processing unit 20 is used to parse the BTM request frame.

[0256] It is understandable that for the specific description of the BTM request frame, the neighbor report element, and the second indication information, reference may be made to the fourth method embodiment shown above, and will not be described in detail here.

[0257] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above-mentioned method embodiment 4 (such as Figure 13), which will not be described in detail here.

[0258] Exemplarily, the transceiver unit 10 is used to receive or input a BTM request frame, which includes one or more neighbor report elements, wherein one neighbor report element is used to carry information of a candidate target AP MLD, and the neighbor report element includes a per-STA profile sub-element of any non-prohibited AP in the candidate target AP MLD; the processing unit 20 is used to parse the BTM request frame.

[0259] It is understandable that for the specific description of the BTM request frame, neighbor report element, and per-STA profile sub-element, etc., reference can be made to the method embodiment 5 shown above, and they will not be described in detail here.

[0260] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above-mentioned method embodiment 5 (such as Figure 16), which will not be described in detail here.

[0261] The above describes the non-AP MLD and AP MLD embodiments of the present application. The following describes possible product forms of the non-AP MLD and AP MLD. It should be understood that any product that possesses the functions of the non-AP MLD described in Figure 19 above, or any product that possesses the functions of the AP MLD described in Figure 19 above, falls within the scope of protection of the present application. It should also be understood that the following description is merely illustrative and does not limit the product forms of the non-AP MLD and AP MLD embodiments of the present application to these examples.

[0262] In one possible implementation, in the communication device shown in FIG19 , 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, wherein the transmitting unit may be a transmitter and the receiving unit may be a receiver, and the transmitting unit and receiving unit are integrated into a single device, such as a transceiver. In the embodiments of the present application, the processor and the transceiver may be coupled, etc., and the embodiments of the present application do not limit the connection method between the processor and the transceiver. During the execution of the above-described method, the process of sending information (such as sending a BTM request frame, etc.) in the above-described method can be understood as the process of the processor outputting the above-described information. When outputting the above-described information, the processor outputs the above-described information to the transceiver for transmission by the transceiver. After being output by the processor, the above-described information may also require further processing before reaching the transceiver. Similarly, the process of receiving information (such as receiving a BTM request frame, etc.) in the above-described method can be understood as the process of the processor receiving the input information. When the processor receives the input information, the transceiver receives the above-described information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to be processed further before being input into the processor.

[0263] Referring to Figure 20 , Figure 20 is another schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device may be an AP MLD or a non-AP MLD, or a chip therein. Figure 20 only illustrates the main components of the communication device. In addition to the processor 1001 and the transceiver 1002, the communication device may further include a memory 1003 and input / output devices (not shown).

[0264] Processor 1001 is primarily used to process communication protocols and communication data, control the entire communication device, execute software programs, and process software program data. Memory 1003 is primarily used to store software programs and data. Transceiver 1002 may include control circuitry and an antenna. The control circuitry is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input / output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.

[0265] When the communication device is powered on, the processor 1001 can 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 sent wirelessly, the processor 1001 performs baseband processing on the data to be sent 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 in the form of electromagnetic waves through the antenna. When data is sent 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.

[0266] In another implementation, the RF circuit and antenna may be provided independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna may be remotely arranged independent of the communication device.

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

[0268] Exemplarily, the communication device can be used to perform the functions of the AP MLD in the aforementioned embodiment 1: the processor 1001 can be used to execute step S101 in Figure 9, and / or other processes for executing the technology described in this document; the transceiver 1002 can be used to execute step S102 in Figure 9, and / or other processes for the technology described in this document.

[0269] Exemplarily, the communication device can be used to perform the functions of the non-AP MLD in the aforementioned embodiment 1: the processor 1001 can be used to execute step S103 in Figure 9, and / or to execute other processes of the technology described in this document; the transceiver 1002 can be used to receive a BTM request frame, and / or to perform other processes of the technology described in this document.

[0270] Exemplarily, the communication device can be used to perform the functions of the AP MLD in the aforementioned embodiment 2: the processor 1001 can be used to perform step S201 in Figure 10, and / or other processes for performing the technology described in this document; the transceiver 1002 can be used to perform step S202 in Figure 10, and / or other processes for the technology described in this document.

[0271] Exemplarily, the communication device can be used to perform the functions of the non-AP MLD in the aforementioned embodiment 2: the processor 1001 can be used to execute step S203 in Figure 10, and / or to execute other processes of the technology described in this document; the transceiver 1002 can be used to receive a BTM request frame, and / or to perform other processes of the technology described in this document.

[0272] Exemplarily, the communication device can be used to perform the functions of the AP MLD in the aforementioned embodiment three: the processor 1001 can be used to execute step S301 in Figure 12, and / or to execute other processes of the technology described in this document; the transceiver 1002 can be used to execute step S302 in Figure 12, and / or to execute other processes of the technology described in this document.

[0273] Exemplarily, the communication device can be used to perform the functions of the non-AP MLD in the aforementioned embodiment three: the processor 1001 can be used to execute step S303 in Figure 12, and / or to execute other processes of the technology described in this document; the transceiver 1002 can be used to receive a BTM request frame, and / or to be used for other processes of the technology described in this document.

[0274] Exemplarily, the communication device can be used to perform the functions of the AP MLD in the aforementioned embodiment 4: the processor 1001 can be used to perform step S401 in Figure 13, and / or other processes for performing the technology described in this document; the transceiver 1002 can be used to perform step S402 in Figure 13, and / or other processes for the technology described in this document.

[0275] Exemplarily, the communication device can be used to perform the functions of the non-AP MLD in the aforementioned embodiment three: the processor 1001 can be used to execute step S403 in Figure 13, and / or to execute other processes of the technology described in this document; the transceiver 1002 can be used to receive a BTM request frame, and / or to perform other processes of the technology described in this document.

[0276] Exemplarily, the communication device can be used to perform the functions of the AP MLD in the aforementioned embodiment five: the processor 1001 can be used to perform step S501 in Figure 16, and / or other processes for performing the technology described in this document; the transceiver 1002 can be used to perform step S502 in Figure 16, and / or other processes for the technology described in this document.

[0277] Exemplarily, the communication device can be used to perform the functions of the non-AP MLD in the aforementioned embodiment 5: the processor 1001 can be used to execute step S503 in Figure 16, and / or to execute other processes of the technology described in this document; the transceiver 1002 can be used to receive a BTM request frame, and / or to perform other processes of the technology described in this document.

[0278] Exemplarily, the communication device can be used to perform the functions of the AP MLD in the aforementioned embodiment six: the processor 1001 can be used to perform step S601 in Figure 18, and / or other processes for performing the technology described in this document; the transceiver 1002 can be used to perform step S602 in Figure 18, and / or other processes for the technology described in this document.

[0279] Exemplarily, the communication device can be used to perform the functions of the non-AP MLD in the aforementioned embodiment three: the processor 1001 can be used to execute step S603 in Figure 18, and / or to execute other processes of the technology described in this document; the transceiver 1002 can be used to receive a BTM request frame, and / or to be used for other processes of the technology described in this document.

[0280] In one implementation, processor 1001 may store instructions, which may be computer programs. The computer programs, when executed on processor 1001, may cause the communication device to perform the methods described in the above method embodiments. The computer programs may be embedded in processor 1001, in which case processor 1001 may be implemented by hardware.

[0281] In one implementation, the communication device may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiment. The processor and transceiver described in this application can be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit (RFIC), a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0282] It is understood that the communication device shown in the embodiment of the present application may also have more components than those in Figure 20, and the embodiment of the present application is not limited to this. The method performed by the processor and transceiver shown above is only an example. For the specific steps performed by the processor and transceiver, please refer to the introduction of the method embodiment above.

[0283] In another possible implementation, in the communication device shown in Figure 19, the processing unit 20 can be one or more logic circuits, and the transceiver unit 10 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Or the transceiver unit 10 can also be a sending unit and a receiving unit, the sending unit can be an output interface, and the receiving unit can be an input interface, and the sending unit and the receiving unit are integrated into one unit, such as an input / output interface. Referring to Figure 21, Figure 21 is another structural diagram of a communication device provided in an embodiment of the present 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 above-mentioned processing unit 20 can be implemented with a logic circuit 901, and the transceiver unit 10 can be implemented with an interface 902. Among them, the logic circuit 901 can be a chip, a processing circuit, an integrated circuit or a system on chip (SoC) chip, etc., and the interface 902 can be a communication interface, an input / output interface, a pin, etc. Exemplarily, Figure 21 is shown as an example of the above-mentioned communication device being a chip, and the chip includes a logic circuit 901 and an interface 902.

[0284] In the embodiment of the present application, the logic circuit and the interface may also be coupled to each other. The embodiment of the present application does not limit the specific connection method between the logic circuit and the interface.

[0285] In some embodiments of the present application, the communication device may be used to execute the method, steps, or functions performed by the AP MLD in any of the above method embodiments.

[0286] Exemplarily, the logic circuit 901 is used to generate a BTM request frame; the interface 902 is used to output the BTM request frame.

[0287] In other embodiments of the present application, the communication device may be used to execute the method, steps, or functions performed by the non-AP MLD in any of the above method embodiments.

[0288] Exemplarily, the interface 902 is used to input a BTM request frame; the logic circuit 901 is used to parse the BTM request frame.

[0289] It is understandable that for the specific description of the BTM request frame, etc., reference can be made to the method embodiment shown above, and no further details will be given here.

[0290] It can be understood that the communication device shown in the embodiment of the present application can implement the method provided in the embodiment of the present application in the form of hardware, or can implement the method provided in the embodiment of the present application in the form of software, etc., and the embodiment of the present application is not limited to this.

[0291] For the specific implementation methods of the various embodiments shown in Figure 21, you can also refer to the above embodiments, which will not be described in detail here.

[0292] An embodiment of the present application further provides a wireless communication system, which includes a non-AP MLD and an AP MLD. The non-AP MLD and the AP MLD can be used to execute the method in any of the aforementioned embodiments.

[0293] In addition, the present application also provides a computer program, which is used to implement the operations and / or processing performed by the non-AP MLD in the method provided in the present application.

[0294] The present application also provides a computer program, which is used to implement the operations and / or processing performed by the AP MLD in the method provided in the present application.

[0295] The present application also provides a computer-readable storage medium having computer code stored therein. When the computer code is executed on a computer, the computer executes the operations and / or processing performed by the non-AP MLD in the method provided in the present application.

[0296] The present application also provides a computer-readable storage medium having computer code stored therein. When the computer code is executed on a computer, the computer is enabled to execute the operations and / or processes performed by the AP MLD in the method provided in the present application.

[0297] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program runs on a computer, the operations and / or processing performed by the non-AP MLD device in the method provided in the present application are executed.

[0298] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program runs on a computer, the operations and / or processes performed by the AP MLD in the method provided by the present application are executed.

[0299] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.

[0300] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of the present application.

[0301] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0302] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or partly contributed to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a readable storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned readable storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0303] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for indicating information in basic service set switching management, characterized in that: include: The access point multi-link device AP MLD generates a basic service set transition management BTM request frame, wherein the BTM request frame includes a basic service set BSS transition candidate list entry field and first indication information, wherein the first indication information is used to indicate a processing method for a basic service set identifier BSSID or AP MLD not listed in the BSS transition candidate list entry field, and a processing method for an AP that does not appear in any recommended AP combination among the candidate target AP MLD listed in the BSS transition candidate list entry field; The AP MLD sends the BTM request frame.

2. A method for indicating information in basic service set switching management, characterized in that: include: The non-access point multi-link device non-AP MLD receives a basic service set transition management BTM request frame, wherein the BTM request frame includes a basic service set BSS transition candidate list entry field and first indication information, wherein the first indication information is used to indicate a processing method of a basic service set identifier BSSID or AP MLD not listed in the BSS transition candidate list entry field, and a processing method of an AP that does not appear in any recommended AP combination among the candidate target AP MLD listed in the BSS transition candidate list entry field; The non-AP MLD parses the BTM request frame.

3. The method according to claim 1 or 2, characterized in that: The first indication information is a simplified field.

4. The method according to claim 3, characterized in that The first indication information is used to indicate a processing method for a BSSID or AP MLD not listed in the BSS conversion candidate list entry field, and a processing method for an AP that does not appear in any recommended AP combination in the candidate target AP MLD listed in the BSS conversion candidate list entry field, including: When the simplified field is a first value, it indicates that the AP MLD neither recommends nor opposes association with a BSSID or AP MLD that does not appear in the BSS conversion candidate list entry field, and an AP that does not appear in any recommended AP combination among the candidate target AP MLDs that appear in the BSS conversion candidate list entry field; When the simplified field is a second value, it indicates that the AP MLD excludes BSSIDs or AP MLDs not associated with the BSS conversion candidate list entry field, and APs that do not appear in any recommended AP combination among the candidate target AP MLDs appearing in the BSS conversion candidate list entry field.

5. The method according to claim 3 or 4, characterized in that: The BSS conversion candidate preference sub-element of the BSS conversion candidate list entry field includes a preference Preference field, and the Preference field is used to indicate the recommendation degree of the AP combination of the candidate target AP MLD listed in the BSS conversion candidate list entry field.

6. The method according to claim 1 or 2, characterized in that: The first indication information is a simplified field and a simplified extension field, the simplified field is used to indicate the processing method of the BSSID or AP MLD that is not listed in the BSS conversion candidate list entry field, and the simplified extension field is used to indicate the processing method of the AP that does not appear in any recommended AP combination among the candidate target AP MLD listed in the BSS conversion candidate list entry field.

7. The method according to claim 6, characterized in that The simplified extension field is used to indicate a processing method for an AP that is not included in any recommended AP combination in the candidate target AP MLD listed in the BSS conversion candidate list entry field, including: When the simplified extension field is a third value, it indicates that the AP MLD neither recommends nor opposes association with an AP that does not appear in any recommended AP combination in the candidate target AP MLD that appears in the BSS conversion candidate list entry field; When the simplified extension field is a fourth value, it indicates that the AP MLD excludes APs that are not present in any recommended AP combination among the candidate target AP MLDs present in the BSS conversion candidate list entry field.

8. A method for information indication in basic service set switching management, characterized in that: include: The access point multi-link device AP MLD generates a basic service set transition management BTM request frame, wherein the BTM request frame includes a basic service set BSS transition candidate list entry field and a request mode field, wherein the request mode field includes a simplified field, and the simplified field is used to indicate a processing method for an AP combination that is not recommended in the candidate target AP MLD listed in the BSS transition candidate list entry field; The AP MLD sends the BTM request frame.

9. A method for indicating information in basic service set switching management, characterized in that: include: The non-access point multi-link device non-AP MLD receives a basic service set transition management BTM request frame, wherein the BTM request frame includes a basic service set BSS transition candidate list entry field and a request mode field, wherein the request mode field includes a simplified field, and the simplified field is used to indicate a processing method for an AP combination that is not recommended in the candidate target AP MLD listed in the BSS transition candidate list entry field; The non-AP MLD parses the BTM request frame.

10. The method according to claim 8 or 9, characterized in that: The simplified field is used to indicate a processing method for an AP combination that is not recommended in the candidate target AP MLD listed in the BSS conversion candidate list entry field, including: When the simplified field is a first value, it indicates that the AP MLD neither recommends nor objects to associating with an AP combination that is not recommended in the candidate target AP MLD that appears in the BSS conversion candidate list entry field; When the simplified field is a second value, it indicates that the AP MLD excludes associations with AP combinations that are not recommended in the candidate target AP MLDs that appear in the BSS conversion candidate list entry field.

11. The method according to any one of claims 8 to 10, characterized in that The simplified field is also used to indicate a processing method for a basic service set identifier BSSID or AP MLD that is not listed in the BSS conversion candidate list entry field.

12. The method according to claim 11, characterized in that The simplified field is also used to indicate a processing method for a basic service set identifier BSSID or AP MLD that is not listed in the BSS conversion candidate list entry field, including: When the simplified field is a first value, it indicates that the AP MLD neither recommends nor objects to associating with a BSSID or AP MLD that does not appear in the BSS conversion candidate list entry field; When the simplified field is a second value, it indicates that the AP MLD exclusion is associated with a BSSID or AP MLD that does not appear in the BSS conversion candidate list entry field.

13. The method according to any one of claims 8 to 12, characterized in that The BSS conversion candidate preference sub-element of the BSS conversion candidate list entry field includes a preference Preference field, and the Preference field is used to indicate the recommendation degree of the AP combination of the candidate target AP MLD listed in the BSS conversion candidate list entry field.

14. A method for indicating information in basic service set switching management, characterized in that: include: The access point multi-link device AP MLD generates a basic service set transition management BTM request frame, wherein the BTM request frame includes one or more neighbor report elements, wherein one neighbor report element is used to carry information of a candidate target AP MLD, and the neighbor report element includes second indication information, wherein the second indication information is used to indicate a processing method for an AP that does not appear in an AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs; The AP MLD sends the BTM request frame.

15. A method for indicating information in basic service set switching management, characterized in that: include: The non-access point multi-link device non-AP MLD receives a basic service set transition management BTM request frame, wherein the BTM request frame includes one or more neighbor report elements, wherein one neighbor report element is used to carry information of a candidate target AP MLD, and the neighbor report element includes second indication information, wherein the second indication information is used to indicate a processing method for an AP that does not appear in an AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs; The non-AP MLD parses the BTM request frame.

16. The method according to claim 14 or 15, characterized in that The second indication information is used to indicate a processing method for an AP that does not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs, including: When the second indication information is a first value, it indicates that the AP MLD neither recommends nor opposes an AP that does not appear in the AP combination associated with the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs; When the second indication information is a second value, it indicates that the AP MLD excludes APs that do not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which the second indication information belongs.

17. The method according to any one of claims 14 to 16, characterized in that The second indication information is carried in the BSS switch candidate preference sub-element of the neighbor report element.

18. The method according to claim 17, characterized in that The BSS conversion candidate preference sub-element also includes a preference field, the length of the preference field is less than or equal to 7 bits, and the preference field is used to indicate the recommendation degree of the candidate target AP MLD carried by the neighbor report element to which the preference field belongs.

19. The method according to claim 18, characterized in that The sum of the bit length of the second indication information and the length of the Preference field is less than or equal to 1 byte.

20. The method according to any one of claims 14 to 16, characterized in that The second indication information is carried in the basic service set identifier BSSID information field of the neighbor report element.

21. An information indication method in basic service set switching management, characterized in that: include: The access point multi-link device AP MLD generates a basic service set transition management BTM request frame, wherein the BTM request frame includes one or more neighbor report elements, wherein one neighbor report element is used to carry information of a candidate target AP MLD, and the neighbor report element includes a per-STA profile sub-element of any non-prohibited AP in the candidate target AP MLD; The AP MLD sends the BTM request frame.

22. A method for indicating information in basic service set switching management, characterized in that: include: The non-AP MLD receives a basic service set transition management BTM request frame, wherein the BTM request frame includes one or more neighbor report elements, wherein one neighbor report element is used to carry information of a candidate target AP MLD, and the neighbor report element includes a per-STA profile sub-element of any non-prohibited AP in the candidate target AP MLD; The non-AP MLD parses the BTM request frame.

23. The method according to claim 21 or 22, characterized in that The per-STA profile sub-element also includes third indication information, where the third indication information is used to indicate a processing mode of the AP corresponding to the per-STA profile sub-element.

24. The method according to claim 23, characterized in that The third indication information is used to indicate a processing method of the AP corresponding to the per-STA profile sub-element, including: When the third indication information is a first value, it indicates that the AP MLD neither recommends nor objects to associating with the AP corresponding to the per-STA profile sub-element; When the third indication information is the second value, it indicates that the AP MLD recommends associating with the AP corresponding to the per-STA profile sub-element.

25. The method according to claim 23 or 24, characterized in that The third indication information is carried in the site STA control field of the per-STA profile sub-element.

26. A communication device, characterized in that: The method comprises a unit or a module for executing the method according to any one of claims 1 to 25.

27. A communication device, characterized in that: including a processor and a memory; The memory is used to store instructions; The processor is configured to execute the instructions so that the method according to any one of claims 1 to 25 is performed.

28. A communication device, characterized in that: It comprises a logic circuit and an interface, the logic circuit and the interface are coupled; the interface is used to input and / or output code instructions, and the logic circuit is used to execute the code instructions so that the method described in any one of claims 1 to 25 is executed.

29. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store a computer program, and when the computer program is executed, the method according to any one of claims 1 to 25 is performed.

30. A communication system, characterized in that: The communication system includes an AP MLD and a non-AP MLD, the AP MLD is used to execute the method as described in any one of claims 1, 8, 14, and 21, and the non-AP MLD is used to execute the method as described in any one of claims 2, 9, 15, and 22.

Citation Information

Patent Citations

  • Communication apparatus and communication method for multi-link setup and link maintenance

    CN115280894A

  • Address randomization for mobile access points

    CN115733823A

  • Multi-link communication method and device and readable storage medium

    CN116133043A

  • Multi-link reconfiguration method and apparatus

    WO2022152184A1