Information indication method and device in BTM

Abstract

The application relates to a method and device for indicating information in a BTM, the method comprising: an AP MLD generating and sending a BTM request frame, the BTM request frame comprising first indication information, which is used for indicating a processing mode of an AP MLD or a BSSID not listed in a BSS transition candidate list entry field and a processing mode of an AP not appearing in a recommended AP combination in a candidate target AP MLD listed in the BSS transition candidate list entry field. The application can improve the indication of information in the BTM. The application is applied to a WLAN system of an 802.11ax next-generation Wi-Fi protocol, such as 802.11be, Wi-Fi 7 or EHT, an 802.11 series protocol such as 802.11be next-generation, Wi-Fi 8, UHR, Wi-Fi AI, and a WPAN system supporting UWB, a sensing system and the like.

Description

[0001] This application is a divisional application. The original application has the application number 202310638067.7 and the original application date is May 31, 2023. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication technology, and in particular to an information indication method and apparatus in basic service set (BSS) transition management (BTM). Background Technology

[0003] With the development of wireless communication technology, more and more wireless communication devices support multi-link (ML) communication, such as communicating simultaneously on 2.4GHz, 5GHz, and 6GHz frequency bands, or simultaneously communicating on different channels within the same frequency band, thereby improving the communication rate between devices. Such devices are commonly called multi-link devices (MLDs). A multi-link device typically contains one or more affiliated stations, each operating on one frequency band, one channel, or one link. If all stations within an MLD are access points (APs), it can be further called an AP MLD; if all stations within an MLD are non-access point stations (non-AP STAs), it can be further called a non-AP MLD.

[0004] Currently, when a site 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 leave its current BSS and join a new one. If this non-AP STA supports Basic Service Set Transition Management (BTM), this function can be used to facilitate BSS transition. During BTM, the AP can send a BSS transition management request (BTM request) frame to the non-AP STA it is about to disassociate with, informing them of the impending disassociation. The AP can also include information about surrounding APs in the BTM request frame, making it easier for the non-AP STA to select a new BSS.

[0005] In existing technologies, AP MLDs can also provide information about surrounding AP MLDs to non-AP MLDs via BTM request frames, facilitating the non-AP MLD to select a new AP MLD for association. However, the information indication in existing BTMs for BSS transitions between non-AP MLDs and AP MLDs is not yet perfect. Summary of the Invention

[0006] This application provides an information indication method and apparatus in a BTM, which can improve the information indication in a BTM and make the non-AP MLD more aware of the AP MLD's attitude and the non-AP MLD's own behavior.

[0007] The present application is described below from different aspects. It should be understood that the different implementation methods and beneficial effects described below can be referenced from each other.

[0008] In a first aspect, this application provides an information indication method in BTM, the method comprising: an AP MLD generating and sending a BTM request frame, the BTM request frame including a BSS conversion candidate list entry field and a request mode field, the request mode field including first indication information, the first indication information being used to indicate the processing method for a Basic Service Set Identifier (BSS Identifier, BSSID) or AP MLD not listed in the BSS conversion candidate list entry field, and the processing method for an AP listed in the BSS conversion candidate list entry field that does not appear in any recommended AP combination.

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

[0010] The frame formats for BTM request frames, BSS transition candidate list entry fields, and neighbor report elements are described below and will not be detailed here.

[0011] This application carries first indication information in the request mode field of the BTM request frame to indicate the processing method for BSSIDs or AP MLDs not listed in the BSS transition candidate list entry field, and the processing method for APs that do not appear in any recommended AP combinations among the candidate target AP MLDs listed in the BSS transition candidate list entry field. This improves the information indication in BTM, clarifies the processing method for APs in MLDs, and makes the attitude of non-AP MLDs clearer as well as the behavior of non-AP MLDs themselves.

[0012] Secondly, this 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 including a BSS conversion candidate list entry field and a request mode field, the request mode field including first indication information, the first indication information being used to indicate the processing method for BSSIDs or AP MLDs not listed in the BSS conversion candidate list entry field, and the processing method for APs listed in the BSS conversion candidate list entry field that do not appear in any recommended AP combinations.

[0013] Thirdly, this application provides a communication device, which may be an AP MLD or a chip or functional module configured in the AP MLD, etc. 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 a request mode field. The request mode field includes first indication information, which is used to indicate the processing method for BSSIDs or AP MLDs not listed in the BSS conversion candidate list entry field, and the processing method for APs listed in the BSS conversion candidate list entry field that do not appear in any recommended AP combinations.

[0014] Fourthly, this application provides a communication device, which may be a non-AP MLD or a chip or functional module configured in a non-AP MLD, etc. The communication device includes a transceiver unit and a processing unit. The transceiver unit is used to receive or input BTM request frames; the processing unit is used to parse the BTM request frame. The BTM request frame includes a BSS conversion candidate list entry field and a request mode field. The request mode field includes first indication information, which is used to indicate the processing method for BSSIDs or AP MLDs not listed in the BSS conversion candidate list entry field, and the processing method for APs listed in the BSS conversion candidate list entry field that do not appear in any recommended AP combinations.

[0015] In any of the above-mentioned possible implementations, the first indication information is an abridged field.

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

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

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

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

[0020] In one 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. For example, the meaning of the preference field can retain its existing meaning, or the meaning of the preference field can change as the standard evolves; this application is not limited to this. Alternatively, the preference field can be used to indicate the degree of recommendation of an AP combination. This AP combination can be an AP combination recommended by the neighbor reporting element to which the preference field belongs. That is, this AP combination is a recommended AP combination of 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.

[0021] This application can also modify the meaning of the Preference field so that when recommending a certain AP combination in AP MLD, the neighbor report element can indicate the degree of recommendation for that AP combination.

[0022] In one possible implementation of any of the above aspects, the first indication information consists of a simplified field and a simplified extended field. The simplified field indicates the processing method for BSSIDs or AP MLDs not listed in the BSS transformation candidate list entry field. The simplified extended field indicates the processing method for APs listed in the candidate target AP MLDs in the BSS transformation candidate list entry field that do not appear in any recommended AP combinations.

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

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

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

[0026] This application adds a simplified extended field to the request mode field to indicate the processing method for APs that do not appear in the candidate target AP MLD listed in the BSS conversion candidate list field. The logic is clear and easy for non-AP MLDs to understand; moreover, the added bits appear simultaneously with the existing simplified field, making the logic neat.

[0027] Fifthly, this application provides an information indication method in BTM, the method comprising: an AP MLD generating and sending a BTM request frame, the BTM request frame including a BSS conversion candidate list entry field and a request mode field, the request mode field including a simplification field, the simplification field being used to indicate the processing method for BSSIDs or AP MLDs not listed in the BSS conversion candidate list entry field, and the processing method for AP combinations not recommended in the candidate target AP MLDs listed in the BSS conversion candidate list entry field.

[0028] The term "AP combination" can include one or more APs. That is, a single AP can also be considered an AP combination, and all APs belonging to a single AP MLD can also be considered an AP combination. The meaning of "no recommended AP combination in the candidate target AP MLD listed in the BSS conversion candidate list entry field" is described in Example 3 below and will not be elaborated here.

[0029] This application's embodiments, by expanding the meaning of simplified fields, simultaneously indicate the processing methods for BSSIDs or AP MLDs not listed in the BSS conversion candidate list field, and the processing methods for AP combinations not recommended among the candidate target AP MLDs listed in the BSS conversion candidate list field. This improves the information indication in the BTM, clarifies the processing methods for non-recommended AP combinations in the MLD, makes the attitude of non-AP MLDs clearer, and defines the behavior of non-AP MLDs themselves; furthermore, the meaning is clear, without adding additional overhead, and has good compatibility.

[0030] Sixthly, this application provides an information indication method in a BTM, the method comprising: a non-AP MLD receiving and parsing a BTM request frame, the BTM request frame including a BSS conversion candidate list entry field and a request mode field, the request mode field including a simplification field, the simplification field being used to indicate the processing method for BSSIDs or AP MLDs not listed in the BSS conversion candidate list entry field, and the processing method for AP combinations not recommended in the candidate target AP MLDs listed in the BSS conversion candidate list entry field.

[0031] Seventhly, this application provides a communication device, which may be an AP MLD or a chip or functional module configured in an AP MLD, etc. 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 a request mode field. The request mode field includes a simplified field, which is used to indicate the processing method for BSSIDs or AP MLDs not listed in the BSS conversion candidate list entry field, and the processing method for AP combinations not recommended among the candidate target AP MLDs listed in the BSS conversion candidate list entry field.

[0032] Eighthly, this application provides a communication device, which may be a non-AP MLD or a chip or functional module configured in a non-AP MLD, etc. The communication device includes a transceiver unit and a processing unit. The transceiver unit is used to receive or input BTM request frames; the processing unit is used to parse the BTM request frame. The BTM request frame includes a BSS conversion candidate list entry field and a request mode field. The request mode field includes a simplified field, which is used to indicate the processing method for BSSIDs or AP MLDs not listed in the BSS conversion candidate list entry field, and the processing method for AP combinations not recommended among the candidate target AP MLDs listed in the BSS conversion candidate list entry field.

[0033] In conjunction with any of aspects five through eight, in one possible implementation, the length of the aforementioned simplified field is 1 bit. When the simplified field has 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) associating with BSSIDs or AP MLDs not appearing in the BSS transition candidate list entry field, nor with AP combinations not recommended among the candidate target AP MLDs appearing in the BSS transition candidate list entry field. When the simplified field has a second value, it indicates that the sender of the BTM request frame (i.e., the APMLD) excludes or opposes the receiver of the BTM request frame (i.e., the non-AP MLD) associating with BSSIDs or AP MLDs not appearing in the BSS transition candidate list entry field, nor with AP combinations not recommended among the candidate target AP MLDs appearing in the BSS transition candidate list entry field.

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

[0035] In conjunction with any of aspects five through eight, in one possible implementation, the BSS conversion candidate preference sub-element of the aforementioned BSS conversion candidate list entry field includes a Preference field. For example, the meaning of the Preference field can retain its existing meaning, or the meaning of the Preference field can change as the standard evolves; this application is not limited to this. Alternatively, the Preference field can be used to indicate the degree of recommendation for an AP combination. This AP combination can be an AP combination recommended by the neighbor reporting element to which the Preference field belongs. That is, this AP combination is a recommended AP combination of 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.

[0036] This application can also modify the meaning of the Preference field so that when recommending a certain AP combination in AP MLD, the neighbor report element can indicate the degree of recommendation for that AP combination.

[0037] Ninthly, this application provides an information indication method in BTM, the method comprising: an AP MLD generating and sending 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 of a candidate target AP MLD. Each neighbor report element includes second indication information, the second indication information being used 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 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: indicating the processing method for APs that do not appear in a certain AP combination of a certain candidate target AP MLD.

[0038] It is understandable that an "AP combination" can include one or more APs. That is, a single AP can also be considered as an AP combination, and all APs belonging to an AP MLD can also be considered as an AP combination.

[0039] This application carries a second indication information in the neighbor report element to indicate how to handle APs that do not appear in a certain AP combination in a single candidate target AP MLD, so that each recommended AP combination can have its own handling method, making it flexible to use.

[0040] Tenthly, this 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 including a BSS transition candidate list entry field, the BSS transition candidate list entry field including one or more neighbor report elements, one of which is used to carry information of a candidate target AP MLD. Each neighbor report element includes a second indication information, the second indication information being used 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 to which the second indication information belongs.

[0041] Eleventhly, this application provides a communication device, which may be an AP MLD or a chip or functional module configured in the AP MLD, etc. 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 transition candidate list entry field, which includes one or more neighbor report elements, one of which carries information about a candidate target AP MLD. The neighbor report element includes second indication information, which indicates 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 to which the second indication information belongs.

[0042] In a twelfth aspect, this application provides a communication device, which may be a non-AP MLD or a chip or functional module configured in a non-AP MLD, etc. The communication device includes a transceiver unit and a processing unit. The transceiver unit is used to receive or input BTM request frames; the processing unit is used to parse the BTM request frame. The BTM request frame includes a BSS transition candidate list entry field, which includes one or more neighbor report elements, one of which carries information about a candidate target AP MLD. The neighbor report element includes second indication information, which indicates the processing method for APs not appearing 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 conjunction with any of aspects nine through twelfth, in one possible implementation, when the aforementioned second indication information is a first value, it indicates that the sender of the aforementioned BTM request frame (i.e., AP MLD) neither recommends nor opposes the receiver of the BTM request frame (i.e., non-AP MLD) associating with APs not appearing in the AP combinations of candidate target AP MLDs carried by the neighbor report element to which this second indication information belongs. When the aforementioned second indication information is a second value, it indicates that the sender of the aforementioned BTM request frame (i.e., AP MLD) excludes or opposes the receiver of the BTM request frame (i.e., non-AP MLD) associating with APs not appearing in the AP combinations of candidate target AP MLDs carried by the neighbor report element to which this second indication information belongs.

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

[0045] In conjunction with any of aspects nine through twelfth, in one possible implementation, the aforementioned second indication information is carried in the BSS transition candidate preference sub-element of the neighbor report element.

[0046] For example, since the existing BSS transition candidate preference sub-element is not scalable, the length of the Preference field can be shortened to less than or equal to 7 bits, without changing the meaning of the Preference field (e.g., the Preference field is used to indicate the recommendation level of the candidate target APMLD 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 transition 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, only changes the length of the Preference field. The meaning of the Preference field can also change as the standard evolves.

[0047] This application carries a second indication information in the BSS transformation candidate preference sub-element of the neighbor report element to indicate how to handle APs that do not appear in the AP combinations 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 handling method, offering flexibility. Furthermore, the second indication information is used simultaneously with the Preference value; that is, the second indication information will not appear when the neighbor report element is not used for recommendation.

[0048] In conjunction with any of aspects nine through twelfth, in one possible implementation, the aforementioned second indication information is carried in the BSSID information field of the neighbor report element. For example, a reserved bit in the BSSID information field can be used as the second indication information.

[0049] This application uses a reserved bit in the BSSID information field of the neighbor report element to indicate how to handle APs that do not appear in the AP combinations 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 handling method, which is flexible.

[0050] In a thirteenth aspect, this application provides an information indication method in BTM, the method comprising: an AP MLD generating and sending 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, one of which carries information about a candidate target AP MLD. A neighbor report element includes a per-STA profile subelement of any non-banned AP in the candidate target AP MLD. A per-STA profile subelement corresponds to a non-banned AP in the candidate target AP MLD. Here, "non-banned" can include at least two meanings: "recommended" and "neither recommended nor opposed".

[0051] Furthermore, this application also prohibits the association of APs that do not appear in the neighbor report element by default. Here, "APs that do not appear in the neighbor report element" can refer to APs other than the APs indicated by the BSSID field and the APs corresponding to the Per-STA Profile subelement in the candidate target AP MLD carried by this neighbor report element.

[0052] This application improves the information indication in BTM by modifying the meaning of AP combinations carried in the neighbor report element, so that APs not appearing in the neighbor report element are prohibited from association by default, making the non-AP MLD more clear about the attitude of the AP MLD and the behavior of the non-AP MLD itself.

[0053] In a fourteenth aspect, this application provides an information indication method in a BTM (Browser Transition Manager), the method comprising: a non-AP MLD receiving and parsing a BTM request frame, the BTM request frame including a BSS (Browser Switching Candidate List) entry field, the BSS transition candidate list entry field including one or more neighbor report elements, one of which carries information about a candidate target AP MLD. A neighbor report element includes a Per-STA Profile subelement for any non-banned AP in the candidate target AP MLD. A Per-STA Profile subelement corresponds to a non-banned AP in the candidate target AP MLD. Here, "non-banned" can include at least two meanings: "recommended" and "neither recommended nor opposed".

[0054] In a fifteenth aspect, this application provides a communication device, which may be an AP MLD or a chip or functional module configured in the AP MLD, etc. 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 transition candidate list entry field, which includes one or more neighbor report elements, one of which carries information about a candidate target AP MLD. A neighbor report element includes a Per-STA Profile subelement for any non-banned AP in the candidate target AP MLD. A Per-STA Profile subelement corresponds to a non-banned AP in the candidate target AP MLD. Here, "non-banned" can include at least two meanings: "recommended" and "neither recommended nor opposed".

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

[0056] In conjunction with any one of aspects thirteen through sixteen, in one possible implementation, each Per-STA Profile subelement also includes third instruction information, which indicates how the AP corresponding to this Per-STA Profile subelement should be processed.

[0057] Optionally, when the third indication information is a first value, it indicates that the sender of the aforementioned 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) associating with the AP corresponding to this per-STA profile sub-element. When the third indication information is a second value, it indicates that the sender of the aforementioned BTM request frame (i.e., the AP MLD) recommends the receiver of the BTM request frame (i.e., the non-AP MLD) associating with the AP corresponding to this per-STA profile sub-element. For example, the first value is 0 and the second value is 1. Or, the first value is 1 and the second value is 0.

[0058] This application prohibits APs from being associated with any APs not appearing in the neighbor report element by default. For APs that do appear in the Per-STA Profile subelement, a third-party instruction indicates whether association is recommended. Since 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, making it very flexible.

[0059] In conjunction with any of aspects thirteen through sixteen, in one possible implementation, the aforementioned third indication information is carried in the STA Control field of the aforementioned per-STA profile subelement. For example, a reserved bit in the STA Control field of the per-STA Profile subelement can be used as the third indication information.

[0060] In a seventeenth aspect, this application provides a communication device, which is an AP MLD, comprising a processor for executing the methods shown in any possible implementation of the first aspect, the fifth aspect, the ninth aspect, the thirteenth aspect, or any of the above-described aspects. Alternatively, the processor is configured to execute a program stored in a memory, wherein when the program is executed, the methods shown in any possible implementation of the first aspect, the fifth aspect, the ninth aspect, the thirteenth aspect, or any of the above-described aspects are executed.

[0061] In conjunction with the seventeenth aspect, in one possible implementation, the memory is located outside the aforementioned communication device.

[0062] In conjunction with the seventeenth aspect, in one possible implementation, the memory is located within the aforementioned communication device.

[0063] In this application, the processor and memory can also be integrated into a single device, that is, the processor and memory can be integrated together.

[0064] In conjunction with the seventeenth aspect, in one possible implementation, the communication device further includes a transceiver for transmitting BTM request frames.

[0065] In an eighteenth aspect, this application provides a communication device, which is a non-AP MLD, comprising a processor for executing the methods shown in any possible implementation of the second, sixth, tenth, fourteenth, or any of these aspects. Alternatively, the processor is configured to execute a program stored in a memory, wherein when the program is executed, the methods shown in any possible implementation of the second, sixth, tenth, fourteenth, or any of these aspects are executed.

[0066] In conjunction with aspect eighteen, in one possible implementation, the memory is located outside the aforementioned communication device.

[0067] In conjunction with aspect eighteen, in one possible implementation, the memory is located within the aforementioned communication device.

[0068] In this application, the processor and memory can also be integrated into a single device, that is, the processor and memory can be integrated together.

[0069] In conjunction with aspect eighteen, in one possible implementation, the communication device further includes a transceiver for receiving BTM request frames.

[0070] In a nineteenth aspect, embodiments of this application provide a communication device including a logic circuit and an interface, the logic circuit and the interface being coupled; the interface is used for inputting and / or outputting information, and the logic circuit is used for performing the methods shown in any possible implementation of the first aspect, the fifth aspect, the ninth aspect, the thirteenth aspect, or any of the aspects described above.

[0071] In a twentieth aspect, embodiments of this application provide a communication device, which includes a logic circuit and an interface, the logic circuit and the interface being coupled; the interface is used for inputting and / or outputting information, and the logic circuit is used for performing the methods shown in any possible implementation of the second aspect, the sixth aspect, the tenth aspect, the fourteenth aspect, or any of the aspects described above.

[0072] In a twentieth aspect, embodiments of this application provide a computer-readable storage medium for storing a computer program that, when run on a computer, causes the methods shown in any possible implementation of the first aspect, the fifth aspect, the ninth aspect, the thirteenth aspect, or any of the aspects to be executed.

[0073] In a twentieth aspect, embodiments of this application provide a computer-readable storage medium for storing a computer program that, when run on a computer, causes the methods shown in any possible implementation of the second aspect, the sixth aspect, the tenth aspect, the fourteenth aspect, or any of the aspects to be performed.

[0074] In a twentieth aspect, embodiments of this application provide a computer program product comprising a computer program or computer code that, when run on a computer, causes the methods shown in any possible implementation of the first aspect, the fifth aspect, the ninth aspect, the thirteenth aspect, or any of the aspects to be executed.

[0075] In a twentieth aspect, embodiments of this application provide a computer program product comprising a computer program or computer code that, when run on a computer, causes the methods shown in any possible implementation of the second aspect, the sixth aspect, the tenth aspect, the fourteenth aspect, or any of the aspects described above to be executed.

[0076] In a twentieth aspect, embodiments of this application provide a computer program that, when run on a computer, executes the methods shown in any possible implementation of the first aspect, the fifth aspect, the ninth aspect, the thirteenth aspect, or any of the aspects described above.

[0077] In a twentieth aspect, embodiments of this application provide a computer program that, when run on a computer, executes the methods shown in any possible implementation of the second aspect, the sixth aspect, the tenth aspect, the fourteenth aspect, or any of the aspects described above.

[0078] In a twentieth aspect, embodiments of this application provide a communication system comprising an AP MLD and a non-AP MLD. The AP MLD is used to perform the methods shown in any possible implementation of the first aspect, the fifth aspect, the ninth aspect, the third aspect, or any of the above-described aspects. The non-AP MLD is used to perform the methods shown in any possible implementation of the second aspect, the sixth aspect, the tenth aspect, the fourteenth aspect, or any of the above-described aspects.

[0079] The technical effects achieved in the above aspects can be referred to each other or to the beneficial effects in the method embodiments shown below, and will not be repeated here. Attached Figure Description

[0080] Figure 1a This is a schematic diagram of an architecture of a wireless communication system provided in an embodiment of this application;

[0081] Figure 1b This is a schematic diagram of another architecture of the wireless communication system provided in the embodiments of this application;

[0082] Figure 2a This is a schematic diagram illustrating communication between a multi-link device and other devices provided in an embodiment of this application;

[0083] Figure 2b This is another schematic diagram illustrating the communication between a multi-link device and other devices provided in an embodiment of this application;

[0084] Figure 3 This is a schematic diagram of an application scenario provided by an embodiment of this application;

[0085] Figure 4 This is a schematic diagram of the frame format of the action field in the BTM request frame provided in the embodiments of this application;

[0086] Figure 5 This is a schematic diagram of the frame format of the neighbor report element provided in an embodiment of this application;

[0087] Figure 6 This is a schematic diagram of the frame format of the basic multi-link sub-element provided in the embodiments of this application;

[0088] Figure 7 This is a schematic diagram of the frame format of the BSS conversion candidate preference sub-element provided in the embodiments of this application;

[0089] Figure 8 This is a schematic diagram of the frame format of the request mode field provided in an embodiment of this application;

[0090] Figure 9 This is a schematic flowchart of the first type of information indication method in BTM provided in the embodiments of this application;

[0091] Figure 10 This is a schematic diagram of the second type of information indication method in BTM provided in the embodiments of this application;

[0092] Figure 11 This is a schematic diagram of another frame format for the request mode field provided in an embodiment of this application;

[0093] Figure 12 This is a schematic diagram of the third type of information indication method in BTM provided in the embodiments of this application;

[0094] Figure 13 This is a schematic diagram of the fourth type of information indication method in BTM provided in the embodiments of this application;

[0095] Figure 14 This is a schematic diagram of the frame format of the BSSID information field provided in the embodiments of this application;

[0096] Figure 15 This is a schematic diagram of another frame format for BSS conversion candidate preference sub-elements provided in the embodiments of this application;

[0097] Figure 16 This is a fifth flowchart illustrating the information indication method in the BTM provided in this application embodiment;

[0098] Figure 17 This is a schematic diagram of the frame format of the STA Control field provided in the embodiments of this application;

[0099] Figure 18 This is a sixth flowchart illustrating the information indication method in the BTM provided in this application embodiment;

[0100] Figure 19 This is a schematic diagram of the structure of the communication device provided in an embodiment of this application;

[0101] Figure 20 This is another structural schematic diagram of the communication device provided in the embodiments of this application;

[0102] Figure 21 This is another structural schematic diagram of the communication device provided in the embodiments of this application. Detailed Implementation

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

[0104] In the description of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, and c can be single or multiple.

[0105] In the description of this application, the words "first," "second," etc., do not limit the quantity or order of execution, nor do they necessarily imply that they are different. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0106] In this application, the words "exemplary" or "for example" are used to indicate that something is an example, illustration, or illustration. Any embodiment or design described as "exemplary," "for example," or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of the words "exemplary," "for example," or "for example" is intended to present the relevant concepts in a specific manner.

[0107] In this application, the use of singular designations for elements is intended to represent "one or more" rather than "one and only one," unless otherwise specified.

[0108] Continuously improving throughput is a persistent 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 previous standards such as 802.11a / b / g / n / ac / ax have consistently improved throughput. The next-generation standard, IEEE 802.11be, is known as Extremely High Throughput (EHT), with significantly increasing peak throughput as its most important technical objective. To achieve this goal, IEEE 802.11be incorporates multi-link (ML) as a key technology. Its core idea includes enabling WLAN devices supporting the next-generation IEEE 802.11 standard to transmit and receive across multiple frequency bands, allowing for data transmission using greater bandwidth and thus significantly improving throughput.

[0109] Multi-band Wi-Fi includes, but is not limited to, the 2.4GHz Wi-Fi band, the 5GHz Wi-Fi band, and the 6GHz Wi-Fi band. Access and transmission on each band are called a link, and access and transmission across multiple bands are called multi-link (ML). Multi-link technology is helpful in reducing latency and improving robustness.

[0110] A multi-link device includes one or more affiliated sites, which can be logical sites. In this embodiment, "a multi-link device includes affiliated sites" is also briefly described as "a multi-link device includes sites." Each affiliated site can operate on one frequency band, one channel, or one link. The affiliated site can be an AP or a non-APSTA. A multi-link device whose affiliated site is an AP can be called an AP multi-link device (AP MLD), and a multi-link device whose affiliated site is a non-AP STA can be called a non-AP multi-link device (non-AP MLD).

[0111] When a multi-link device (such as an AP MLD) and another multi-link device (non-AP MLD) transmit data, they can use link identifiers to identify a link or a station on a link. Before communication, the two multi-link devices (such as the AP MLD and the non-AP MLD) can negotiate or communicate the mapping between the link identifier (link ID) and a link or a station on a link. Alternatively, the AP MLD can indicate the mapping between the link identifier and a link or a station on a link through broadcast management frames, such as beacon frames. Therefore, during data transmission, it is not necessary to transmit a large amount of signaling information to indicate the link or the station on the link; carrying the link identifier is sufficient, reducing signaling overhead and improving transmission efficiency.

[0112] In one possible implementation, the multi-link device can implement wireless communication by following the 802.11 family of protocols, for example, following Extremely High Throughput (EHT) or following 802.11be-based or compatible protocols, thereby enabling communication with other devices. Of course, the other devices may or may not be multi-link devices.

[0113] The technical solutions provided in this application can be applied to WLAN systems, such as Wi-Fi. For example, the methods provided in this application can be applied to IEEE 802.11 series protocols, such as the next-generation Wi-Fi protocols of 802.11ax, such as 802.11be, Wi-Fi 7, or EHT; further examples include 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. The technical solutions provided in this application can also be applied to wireless personal area network (WPAN) systems based on ultra-wide bandgap (UWB), sensing systems, etc. For example, the methods provided in this application can be applied to IEEE 802.15 series protocols, such as 802.15.4a, 802.15.4z, or 802.15.4ab, or a future generation of UWB WPAN protocols, etc., which are not listed here. The technical solutions provided in this application can also be applied to the following communication systems, such as Internet of Things (IoT) systems, vehicle-to-X (V2X) systems, narrowband Internet of Things (NB-IoT) systems, devices used in vehicle-to-vehicle systems, IoT nodes and sensors in IoT, smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities. Alternatively, they can also be applied to long-term evolution (LTE) systems, 5th-generation (5G) communication systems, and new communication systems that will emerge in the future development of communication.

[0114] Although this application primarily uses the deployment of IEEE 802.11 networks as an example, those skilled in the art will readily understand that the various aspects covered in this application can be extended to other networks employing various standards or protocols, such as high-performance radio LANs (HIPERLANs) (a wireless standard similar to IEEE 802.11, primarily used in Europe), wide area networks (WANs), wireless local area networks (WLANs), personal area networks (PANs), or other networks now known or to be developed in the future.

[0115] See Figure 1a , Figure 1a This is a schematic diagram of an architecture of a wireless communication system provided in an embodiment of this application. Figure 1a As shown, the wireless communication system includes at least two AP MLDs (such as...). Figure 1a AP MLD100 and AP MLD200) and at least one non-AP MLD (such as Figure 1a (non-AP MLD300). Optional, Figure 1a It can also include traditional sites that only support transmission over a single link (such as...). Figure 1a The single-link non-AP STA400 (also known as STA400) is used in this context. The AP MLD provides services to the non-AP MLD, and the non-AP MLD can communicate with the AP MLD using multiple links to improve throughput. A STA within a non-AP MLD can also communicate with an AP within an AP MLD via a single link. Understandably... Figure 1a The use of non-AP MLD as a mobile phone and AP MLD as a router in this application is merely an example and does not imply any limitation on the types of AP MLD and non-AP MLD used in this application. It is also understood that... Figure 1a The number of AP MLDs and non-AP MLDs is merely exemplary. The number of AP MLDs or non-AP MLDs in the wireless communication system may be more or less, and this application does not limit this.

[0116] In the embodiments of this application, the term "communication" can also be described as "data transmission," "information transmission," or "transmission." The term "transmission" can refer to sending and receiving in general.

[0117] See Figure 1b , Figure 1b This is a schematic diagram of another architecture of the wireless communication system provided in the embodiments of this application. For example... Figure 1b As shown, the AP MLD includes n stations, namely AP1, AP2, ..., APn; the non-AP MLD also includes n stations, namely STA1, STA2, ..., STAn. Here, n is a positive integer. Communication between MLDs is multi-link communication. Figure 1bLinks 1 to n in the network constitute a multi-link system. In other words, the AP MLD and non-AP MLD can communicate in parallel using links 1, 2, ..., n. One AP in the AP MLD can establish a link with one 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, STAn in the non-AP MLD establishes link n with APn in the AP MLD, and so on. Exemplarily, the multi-link device in this application embodiment can be a single-antenna device or a multi-antenna device. For example, it can be a device with two or more antennas. This application embodiment does not limit the number of antennas included in the multi-link device.

[0118] The frequency bands in which multi-link devices can operate may include, but are not limited to: sub 1GHz, 2.4GHz, 5GHz, 6GHz and high frequency 60GHz.

[0119] See Figure 2a , Figure 2a This is a schematic diagram illustrating communication between a multi-link device and other devices according to an embodiment of this application. For example, Figure 2a This paper illustrates a scenario of communication between AP MLD 101 and non-AP MLD 102. AP MLD 101 includes AP101-1 and AP101-2, and non-AP MLD 102 includes STA102-1 and STA102-2. AP MLD 101 and non-AP MLD 102 communicate in parallel using link 1 and link 2.

[0120] See Figure 2b , Figure 2b This is another schematic diagram illustrating communication between a multi-link device and other devices provided in this application embodiment. For example, Figure 2bThis diagram illustrates a scenario where AP MLD 101 communicates with non-AP MLD 102, non-AP MLD 103, and STA 104. AP MLD 101 includes its subordinate APs 101-1 to 101-3; non-AP MLD 102 includes its subordinate three sites: STA 102-1, STA 102-2, and STA 102-3; non-AP MLD 103 includes its subordinate two sites: 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, with non-AP MLD 103 using links 2 and 3, and 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 with STA 104 and STA 102-1 in non-AP MLD 102 via Link 1. AP 101-2, operating in the 5GHz band within AP MLD 101, can transmit uplink or downlink data with STA 103-1, operating in the 5GHz band within non-AP MLD 103, via link 2. It can also transmit uplink or downlink data with STA 102-2, operating in the 5GHz band within non-AP MLD 102, via link 2. Similarly, AP 101-3, operating in the 6GHz band within AP MLD 101, can transmit uplink or downlink data with STA 102-3, operating in the 6GHz band within non-AP MLD 102, via link 3. It can also transmit uplink or downlink data with STA 103-2 within the non-AP MLD via link 3.

[0121] The above Figure 2a Only two frequency bands are shown for AP MLD support, as mentioned above. Figure 2bThis illustration only takes the AP MLD 101, which supports three frequency bands (2.4GHz, 5GHz, and 6GHz), with each band corresponding to one link. The AP MLD 101 can operate on one or more links from link 1, link 2, or link 3. In practical applications, AP MLDs and non-AP MLDs can support more or fewer frequency bands, meaning they can operate on more or fewer links. This embodiment does not limit this. Figure 2a and Figure 2b This is merely a simplified illustration and does not constitute any limitation on the scope of protection of the embodiments of this application. It is understood that descriptions of the 802.11 physical layer (PHY) and medium access control (MAC) layer in multi-link devices can be found in relevant standards or protocols, and will not be shown in detail in the embodiments of this application.

[0122] For example, a multi-link device (which can be 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 a complete device. Devices with these chips or processing systems installed can implement the methods and functions of the embodiments of this application under the control of these chips or processing systems. For example, the non-AP MLD in the embodiments of this application has wireless transceiver capabilities, can support the 802.11 series 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 users to communicate with an AP and thus with a WLAN. For example, a non-AP MLD can be a tablet computer, desktop computer, laptop computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), mobile phone, or other network-connected user devices, or an IoT node in the Internet of Things, or an in-vehicle communication device in the Internet of Vehicles; a non-AP MLD can also be a chip and processing system in the above-mentioned terminals. An AP MLD is a device that can provide services to a non-AP MLD and can support the 802.11 series of protocols. For example, an AP MLD can be a communication server, router, switch, bridge, or other communication entity. Alternatively, an AP MLD can include various forms of macro base stations, micro base stations, relay stations, etc. Of course, an AP MLD can also be the chip and processing system within these various types of devices, thereby implementing the methods and functions of the embodiments of this application. The 802.11 protocol can be a protocol that supports or is compatible with 802.11be.

[0123] Understandably, multi-link devices can support high-speed, low-latency transmission. With the continuous evolution of wireless LAN application scenarios, multi-link devices can be applied to even more scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air quality monitoring nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things (IoT), entertainment terminals (e.g., AR, VR wearable devices), smart devices in smart offices (e.g., printers, projectors, etc.), vehicle-to-everything (V2X) devices, and some infrastructure in daily life scenarios (e.g., vending machines, supermarket self-service navigation kiosks, self-checkout machines, self-ordering machines, etc.). In this application embodiment, the specific forms of non-AP MLD and AP MLD are not limited; they are merely illustrative examples.

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

[0125] A Basic Service Set (BSS) is a fundamental module of an IEEE 802.11 local area network (LAN) and consists of multiple Stations (STAs). Different types of BSSs result in different topologies for their member STAs. For example, in an Infrastructure BSS, one special STA acts as an access point to the distributed system (DS); this STA is called the Access Point Station (AP STA), often simply referred to as AP. Other STAs are called non-AP STAs, and all non-AP STAs are associated with this AP to access the DS; non-AP STAs are not connected to each other. In an Independent BSS, all STAs have the same role and can be connected to each other. The LAN uses hierarchical management; when two STAs interact, data transmitted by STA1 travels from BSS1 through the DS to BSS2 and finally reaches STA2. Therefore, an STA must belong to a specific BSS to access the LAN.

[0126] In some scenarios, for Infrastructure BSSs, non-AP STAs need to disconnect from their currently associated APs and re-associate with new APs; that is, non-AP STAs need to leave the current BSS and join a new BSS. Therefore, the Basic Service Set Transition Management (BTM) function is proposed, applicable to Infrastructure BSSs. If a non-AP STA supports BTM, it can use this function to facilitate BSS transition. For example, an AP can send a BSS transition management request (BTMrequest) frame to the non-AP STA it is about to disassociate with, informing it of the impending disassociation. The AP can also include information about surrounding APs in the non-AP STA's BTMrequest frame, making it easier for the non-AP STA to select a new BSS.

[0127] Current technical solutions have clearly defined the BSS conversion process between non-AP STAs (Standard Access Servers) and APs that are not attached to any MLD (Multi-Link Device). It's understandable that for multi-link devices (MLDs), there are also scenarios where a non-AP MLD needs to disassociate from its currently associated AP MLD and reassociate with a new AP MLD. For example, see... Figure 3 , Figure 3This is a schematic diagram illustrating an application scenario provided in an embodiment of this application. For example... Figure 3 As shown, there are four APMLDs near the non-AP MLD: APMLD1, AP MLD2, AP MLD3, and AP MLD4. Assume the current non-AP MLD is associated with AP MLD1, but it will soon be unassociated with AP MLD1. Therefore, the non-AP MLD needs to choose one of the remaining three AP MLDs (AP MLD2, AP MLD3, and AP MLD4) for reassociation. When making this selection, the currently associated AP MLD1 can be recommended.

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

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

[0130] The BSS transformation candidate list entry field can include one or more Neighbor Report elements, which can be used to describe (or carry) the degree of preference for target BSS candidates or target AP MLDs. Typically, one Neighbor Report element corresponds to one target BSS candidate or target AP MLD. Different Neighbor Report elements can correspond to the same target AP MLD or different target AP MLDs.

[0131] See Figure 5 , Figure 5 This is a schematic diagram of the frame format of the neighbor report element provided in an embodiment of this application. For example... Figure 5As shown, the neighbor report element may include, but is not limited to, a Basic Service Set Identifier (BSSID) field and an Optional Subelements field. The BSSID field contains the MAC address of any AP recommended in the candidate target AP MLD. The Optional Subelements field can be used to carry information about the candidate target AP MLD and its recommendation level. When the neighbor report element in the BSS transition candidate list entry field is used for recommendation, the Optional Subelements field may contain the following:

[0132] (1) The basic multi-link subelement corresponding to the candidate target AP MLD. See also Figure 6 , Figure 6 This is a schematic diagram of the frame format of a basic multi-link sub-element provided in an embodiment of this application. Wherein, if Figure 6 If the Presence Bitmap field in the Basic Multi-Link subelement is all 0 and there is no Link Info field, then this neighbor report element indicates "Recommended candidate AP MLD, but does not specify which APs are recommended." If... Figure 6 If the Link Info field of the Basic Multi-Link subelement has one or more Per-STA Profile subelements, then each Per-STA Profile subelement corresponds to a recommended affiliated AP in this candidate target AP MLD. In this case, the neighbor report element means "a certain AP combination recommended for this candidate target AP MLD".

[0133] (2) The BSS Transition Candidate Preference Subelement corresponding to the candidate target AP MLD is used to represent the recommendation level of this candidate target AP MLD. See the standard description for details, which will not be repeated here. Figure 7 , Figure 7 This is a schematic diagram of the frame format of the BSS conversion candidate preference sub-element provided in an embodiment of this application. For example... Figure 7As shown, the BSS transformation candidate preference sub-element may include, but is not limited to, the Preference field. The Preference field is 1 byte long (equal to 8 bits). When the Preference field value is 0, it indicates "exclude this candidate AP MLD," meaning that non-AP MLDs should not be associated with this candidate AP MLD. When the Preference field value is between 1 and 255, it indicates the recommendation level of this candidate AP MLD, with values ​​increasing from low to high, 255 being "most recommended" and 1 being "least recommended."

[0134] 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 different AP combinations of the same candidate target AP MLD, and provides the recommended value / degree of recommendation for that candidate target AP MLD. Furthermore, the recommended values ​​for different AP combinations of the same candidate target AP MLD may differ, which will not be discussed in this application.

[0135] See Figure 8 , Figure 8 This is a schematic diagram of the frame format of the request mode field provided in an embodiment of this application. For example... Figure 8 As shown, the Request Mode field includes, but is not limited to, the Abridged 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. In the BSSTransition Candidate List Entries field of this application, the BSSID can be used to identify single-link sites or legacy sites, such as APs.

[0136] For example, a value of 1 for the Abridged field indicates "exclude (associating) BSSIDs or AP MLDs that do not appear," meaning that non-AP MLDs are not advised to associate with BSSIDs or AP MLDs that do not appear in the BSS Transition Candidate List Entries field. A value of 0 for the Abridged field indicates that associating non-AP MLDs with BSSIDs or AP MLDs that do not appear in the BSS Transition Candidate List Entries field is neither recommended nor discouraged (the APMLD 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 BSSTransition Candidate List Entries field).

[0137] In summary, the BSS Transition CandidateList Entries field can indicate the handling of surrounding AP MLDs (i.e., whether association is prohibited / opposed) for AP MLDs currently associated with a non-AP MLD. The pre-defined handling of BSSIDs or AP MLDs not listed in the BSS Transition Candidate List Entries field is indicated by the Abridged field, while the recommendation level of candidate target AP MLDs listed in the BSS Transition Candidate List Entries field is indicated by the Preference field. However, the handling of APs listed in the BSS Transition Candidate List Entries field that are not part of the recommended AP combination is not specified.

[0138] For example, suppose an AP MLD contains four APs, AP1 to AP4; suppose the BSSID field in the Neighbor Report element corresponding to this AP MLD is the MAC address of AP2 in this AP MLD, and the Link Info field has a Per-STA Profile subelement, which corresponds to AP4 in this AP MLD. In this case, the Neighbor Report element indicates "Recommended AP combination for this AP MLD (i.e., AP2 and AP4)". However, the handling of AP1 and AP3 in this AP MLD is unclear.

[0139] In view of this, embodiments of this application provide an information indication method and apparatus in BTM, which can improve information indication, clarify the predetermined processing method of APs that are not recommended in the candidate target AP MLDs listed in the BSS Transition Candidate List Entries field, and make non-AP MLDs more aware of the attitude of the currently associated AP MLD and their own behavior.

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

[0141] To facilitate a clear description of the technical solutions of this application, multiple embodiments are described below. Unless otherwise specified, the same or similar parts between different embodiments or implementations can be referenced interchangeably. In the various embodiments and implementation methods / methods within those embodiments, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between different implementation methods / methods within those embodiments are consistent and can be mutually referenced. The technical features in different embodiments and between different implementation methods / methods within those embodiments can be combined to form new embodiments, implementation methods, or methods of implementation based on their inherent logical relationships. The embodiments described below do not constitute a limitation on the scope of protection of this application. It is understood that the order of the embodiments below does not represent their importance.

[0142] Example 1

[0143] This application's first embodiment mainly introduces a method to improve information indication by modifying the meaning of the Abridged field in the Request Mode field.

[0144] See Figure 9 , Figure 9This is a schematic flowchart of the first type of information indication method in BTM provided in this application embodiment. For example... Figure 9 As shown, the information indication method in this BTM includes, but is not limited to, the following steps:

[0145] S101, the AP MLD generates 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, which is used to indicate the processing method for BSSIDs or AP MLDs not listed in the BSS conversion candidate list entry field, and the processing method for APs listed in the BSS conversion candidate list entry field that do not appear in any recommended AP combinations.

[0146] S102, the AP MLD sends the BTM request frame. Correspondingly, the non-AP MLD receives the BTM request frame.

[0147] S103, the non-AP MLD parses the BTM request frame. For example, by parsing the simplified fields in the BTM request frame, the non-AP MLD can obtain the processing method for BSSIDs or AP MLDs not listed in the BSS conversion candidate list entry field, as well as the processing method for APs that do not appear in any recommended AP combinations among the candidate target AP MLDs listed in the BSS conversion candidate list entry field.

[0148] In one possible implementation, the format of the Action field in the BTM request frame can be as described above. Figure 4 As shown, this will not be repeated here. The Action field of this BTM request frame may include, but is not limited to, the BSS Transition Candidate List Entries field and the Request Mode field. 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 the target AP MLD. Different neighbor report elements can correspond to different AP combinations of the same target AP MLD. Of course, different neighbor report elements can also correspond to different target BSS candidates or target AP MLDs. The frame format of each neighbor report element can be as described above. Figure 5 As shown, I will not go into details here.

[0149] The frame format of the Request Mode field can be as described above. Figure 8As shown, details are omitted here. The Request Mode field includes an Abridged field. This Abridged field can be used to indicate the processing method for (all) BSSIDs or (all) AP MLDs not listed in the BSSTransition Candidate List Entries field, as well as the processing method for APs that do not appear in any recommended AP combinations 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 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 combinations among candidate target AP MLDs listed in the BSS Transition Candidate List Entries field.

[0150] In this application, "(all) BSSIDs" can mean both BSSID and all BSSIDs. Similarly, "(all) AP MLDs" can mean both AP MLDs and all AP MLDs. The same expressions will have the same meaning in the following text and will not be repeated.

[0151] In one possible implementation, the Abridged field has a length of 1 bit. When the Abridged field is a first value, it indicates that the sender of the BTM request frame neither recommends nor opposes the receiver associating the BSSID or AP MLD that does not appear in the BSS Transition Candidate List Entries field, nor the 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 opposes or excludes the receiver associating the BSSID or AP MLD that does not appear in the BSS Transition Candidate List Entries field, nor the 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 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; this embodiment of the application does not impose any limitations.

[0152] It is understandable that if a Basic Multi-Link subelement of a Neighbor Report element has all Presence Bitmap fields set to 0 and no Link Info field, then all affiliated APs of the candidate target AP MLD corresponding to this Neighbor Report element are recommended.

[0153] It can also be understood that "(all) AP MLDs not listed in the BSS Transition Candidate List Entries field" does not include AP MLDs that sent BTM request frames. For example, as mentioned above... Figure 3The following is an example of an application scenario. Assume 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 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. Then, "(all) AP MLDs not listed in the BSSTransition Candidate List Entries field" refers to other AP MLDs in the network besides AP MLD 1, AP MLD 2, AP MLD 3, and AP MLD 4. Assume AP MLD 2 has 3 APs: AP2-1, AP2-2, and AP2-3; AP MLD 3 has 2 APs: AP3-1 and AP3-2; and AP MLD 4 has 2 APs: AP4-1 and AP4-2. Furthermore, assuming the BSS Transition Candidate List Entries field includes a total of four neighbor report elements: Neighbor report element 1 recommends the combination of AP2-1 and AP2-2 for AP MLD2; Neighbor report element 2 recommends the combination of AP2-2 and AP2-3 for AP MLD2; Neighbor report element 3 recommends AP MLD 3 (meaning all APs belonging to AP MLD3 are recommended); and Neighbor report element 4 recommends AP4-2 for AP MLD 4 (the BSSID field is the MAC address of AP4-2, and the Presence Bitmap field is not all zeros but has no Link Info field). Therefore, "APs listed in the (all) candidate target APs in the BSS Transition Candidate List Entries field that do not appear in any recommended AP combinations" can include AP4-1. Optionally, for the recommended AP combination {AP2-1, AP2-2}, the handling of AP2-3 can be defaulted, such as defaulting to opposing the association with AP2-3. For the recommended AP combination {AP2-2, AP2-3}, the handling of AP2-1 can also be defaulted, such as defaulting to disassociating AP2-1. In other words, for each recommended AP combination, the handling of APs that do not appear in this recommended AP combination but appear in other AP combinations within the same APMLD can be the default rule.

[0154] In another possible implementation, when the Abridged field is a first value, it indicates that the sender of the aforementioned BTM request frame neither recommends nor opposes the recipient of the BTM request frame associating with an AP that does not appear in the BSSID or AP MLD that does not appear in the BSS Transition Candidate List Entries field, nor with any AP that does appear in the candidate target AP MLD combination 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 opposes or excludes the recipient of the BTM request frame associating with an AP that does not appear in the BSSID or AP MLD that does not appear in the BSS Transition Candidate List Entries field, nor with any AP that does appear in the candidate target AP MLD combination 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; this embodiment of the application does not impose any limitations.

[0155] For example, as mentioned above Figure 3The following is an example of an application scenario. Assume the current non-AP MLD is associated with AP MLD 1, and AP MLD 1 discovers that the non-AP MLD needs a BSS transition, or the non-AP MLD discovers that it needs 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 AP MLD 2 has three APs: AP2-1, AP2-2, and AP2-3. Further assume the BSS Transition Candidate ListEntries field includes two neighbor report elements: neighbor report element 1 recommends the combination of AP2-1 and AP2-2 for AP MLD 2, and neighbor report element 2 recommends the combination of AP2-2 and AP2-3 for AP MLD 2. For the recommended AP combination {AP2-1, AP2-2}, AP2-3 is not in this combination. Therefore, when the Abridged field value is 1, it means excluding associations with BSSIDs or AP MLDs not appearing in the BSS Transition Candidate List Entries field. Furthermore, if a non-AP MLD selects the AP combination {AP2-1, AP2-2}, then association with AP2-3 is excluded. When the Abridged field value is 0, it means neither recommending nor opposing associations with BSSIDs or APMLDs not appearing in the BSS Transition Candidate List Entries field. Furthermore, if a non-AP MLD selects the AP combination {AP2-1, AP2-2}, then association with AP2-3 is neither recommended nor opposed. For the recommended AP combination {AP2-2, AP2-3}, AP2-1 is not in this combination. Therefore, when the Abridged field value is 1, it means excluding associations with BSSIDs or AP MLDs not appearing in the BSS Transition Candidate List Entries field. Furthermore, if a non-AP MLD selects the AP combination {AP2-2, AP2-3}, then association with AP2-1 is excluded. When the Abridged field value is 0, it means neither recommending nor opposing associations with BSSIDs or AP MLDs not appearing in the BSS Transition Candidate List Entries field. Furthermore, if a non-AP MLD selects the AP combination {AP2-2, AP2-3}, then association with AP2-1 is neither recommended nor opposed.

[0156] In one possible implementation, the BSS Transition Candidate List Entries field's BSS Transition Candidate Preference subelement includes a Preference field. For example, the meaning of this Preference field can retain its existing meaning, or its meaning can change as the standard evolves; this application embodiment is not limited by this. Alternatively, the Preference field can be used to indicate the degree of recommendation for an AP combination. This AP combination can be an AP combination recommended by the neighbor reporting element to which the Preference field belongs. That is, this AP combination is a recommended AP combination for a candidate target APMLD listed in the BSS Transition Candidate List Entries field.

[0157] This application's embodiments expand the meaning of the Abridged field to simultaneously indicate the processing method for BSSIDs or AP MLDs not listed in the BSSTransition Candidate List Entries field, and the processing method for APs not appearing in the candidate target AP MLDs listed in the BSSTransition Candidate List Entries field. This improves information indication, clarifies the processing method for APs in MLDs, and makes non-AP MLDs more aware of the attitude and behavior of the currently associated AP MLD. Furthermore, the meaning of this application's embodiments is clear, without adding overhead, and has good compatibility.

[0158] Furthermore, embodiments of this application also modify the meaning of the Preference field so that when recommending a certain AP combination of AP MLD, the neighbor report element can indicate the degree of recommendation for that combination.

[0159] Example 2

[0160] Embodiment 2 of this application mainly introduces a method for improving information indication by using reserved bits in the Request Mode field.

[0161] See Figure 10 , Figure 10 This is a schematic diagram of the second type of information indication method in BTM provided in the embodiments of this application. For example... Figure 10 As shown, the information indication method in this BTM includes, but is not limited to, the following steps:

[0162] S201, AP MLD generates BTM request frame, which includes BSS conversion candidate list entry field and request mode field. The request mode field includes a simplified extension field, which is used to indicate the processing method for APs listed in the BSS conversion candidate list entry field that do not appear in any recommended AP combination in the AP MLD.

[0163] S202, the AP MLD sends the BTM request frame. Correspondingly, the non-AP MLD receives the BTM request frame.

[0164] S203, the non-AP MLD parses the BTM request frame. For example, by parsing the simplified extended fields in the BTM request frame, the non-AP MLD can determine the processing method for APs listed in the BSS transition candidate list entry field that do not appear in any recommended AP combinations. Furthermore, by parsing the simplified fields in the BTM request frame, the non-AP MLD can determine the predetermined processing method for BSSIDs or AP MLDs that are not listed in the BSS transition candidate list entry field.

[0165] In one possible implementation, the format of the Action field in the BTM request frame can be as described above. Figure 4 As shown, this will not be repeated here. The Action field of this BTM request frame may include, but is not limited to, the BSS Transition Candidate List Entries field and the Request Mode field. 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 the target AP MLD. Different neighbor report elements can correspond to different AP combinations of the same target AP MLD. Of course, different neighbor report elements can also correspond to different target BSS candidates or target AP MLDs. The frame format of each neighbor report element can be as described above. Figure 5 As shown, I will not go into details here.

[0166] 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 Extension field can be used to indicate to the recipient of the BTM request frame the treatment of APs listed in the BSS Transition Candidate List Entries field that do not appear in any recommended AP combination. Alternatively, the Abridged Extension field can be used to indicate to the recipient of the BTM request frame the treatment of APs listed in the BSS Transition Candidate List Entries field that do not appear in any AP combination of candidate target AP MLDs.

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

[0168] It is understood that the “Abridged Extension field” in the embodiments of this application may have other names, such as “Extension Abridged field”, or the first field, etc., and the embodiments of this application do not impose any restrictions.

[0169] For example, see Figure 11 , Figure 11 This is a schematic diagram of another frame format for the request mode field provided in an embodiment of this application. For example... Figure 11 As shown, a reserved bit in the Request Mode field can be used as a simplified extension field. When the Abridged Extension field is the third value, it indicates that the sender of the aforementioned BTM request frame neither recommends nor opposes the receiver of the BTM request frame associating 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 Extension field is the fourth value, it indicates that the sender of the BTM request frame opposes or excludes the receiver of the BTM request frame associating 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. Alternatively, when the Abridged Extension field is the third value, it indicates that the sender of the aforementioned BTM request frame neither recommends nor opposes the receiver of the BTM request frame associating an AP that does not appear in a certain AP combination when selecting a candidate target AP MLD that does appear 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 an AP that does not appear in a certain AP combination when selecting a candidate target AP MLD that appears in the BSS TransitionCandidate List Entries field.

[0170] The third value can be 0 or 1; correspondingly, the fourth value can be 1 or 0; this application embodiment does not impose any restrictions.

[0171] It is understandable that the above Figure 11The value and meaning of the Abridged field in the Request Mode field can remain unchanged. When the Abridged field is the first value (e.g., 0), it means that the sender of the BTM request frame neither recommends nor opposes the receiver association of the BTM request frame not appearing in the BSS Transition Candidate List Entries field with a BSSID or AP MLD. When the Abridged field is the second value (e.g., 1), it means that the sender of the BTM request frame opposes or excludes the receiver association of the BTM request frame not appearing in the BSS Transition Candidate List Entries field with a BSSID or AP MLD.

[0172] It is understandable that the above Figure 11 The length of the simplified extended field can be 1 bit or more bits, and this application embodiment does not limit it.

[0173] This application embodiment utilizes reserved bits in the Request Mode field to indicate the processing method for APs that do not appear in the candidate target AP MLDs listed in the BSS TransitionCandidate List Entries field. This improves the information indication, making it clearer for non-AP MLDs the attitude of the currently associated AP MLD and their own behavior. Furthermore, this application embodiment does not modify the meaning of the Abridged field, but uses additional bits for supplementary explanation, making the logic clear and easy for non-AP MLDs to understand; and the added bits appear simultaneously with the existing Abridged field, resulting in a neat and tidy logic.

[0174] Example 3

[0175] Embodiment 3 of this application mainly introduces the modification of the meaning of the Abridged field so that it can indicate the processing method for AP combinations that are not recommended in the AP MLD that appear in the BSS conversion candidate list entry field.

[0176] See Figure 12 , Figure 12 This is a schematic diagram of the third type of information indication method in BTM provided in the embodiments of this application. For example... Figure 12 As shown, the information indication method in this BTM includes, but is not limited to, the following steps:

[0177] S301, the AP MLD generates a BTM request frame, which includes a BSS conversion candidate list entry field and a request mode field. The request mode field includes a simplification field, which indicates the processing method for BSSIDs or AP MLDs not listed in the BSS conversion candidate list entry field, as well as the processing method for AP combinations not recommended among the candidate target AP MLDs listed in the BSS conversion candidate list entry field.

[0178] S302, the AP MLD sends the BTM request frame. Correspondingly, the non-AP MLD receives the BTM request frame.

[0179] S303, the non-AP MLD parses the BTM request frame. For example, by parsing the simplified fields in the BTM request frame, the non-AP MLD can obtain the processing method for BSSIDs or AP MLDs not listed in the BSS conversion candidate list entry field, and the processing method for AP combinations not recommended in the candidate target AP MLDs listed in the BSS conversion candidate list entry field.

[0180] In one possible implementation, the format of the Action field in the BTM request frame can be as described above. Figure 4 As shown, this will not be repeated here. The Action field of this BTM request frame may include, but is not limited to, the BSS Transition Candidate List Entries field and the Request Mode field. 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 the target AP MLD. Different neighbor report elements can correspond to different AP combinations of the same target AP MLD. Of course, different neighbor report elements can also correspond to different target BSS candidates or target AP MLDs. The frame format of each neighbor report element can be as described above. Figure 5 As shown, I will not go into details here.

[0181] The frame format of the Request Mode field can be as described above. Figure 8As shown, details will not be repeated here. The Request Mode field includes an Abridged field. This Abridged field can be used to indicate the processing method for (all) BSSIDs or (all) AP MLDs not listed in the BSSTransition Candidate List Entries field, as well as the processing method for AP combinations that are not recommended among (all) candidate target AP MLDs listed in the BSS Transition Candidate List Entries field.

[0182] It is understandable that the specific meaning of "(all) AP MLDs not listed in the BSS Transition Candidate List Entries field" can be found in the description in the aforementioned Example 1, and will not be repeated here.

[0183] The meaning of "AP combinations not recommended in (all) candidate APMLDs listed in the BSS Transition Candidate List Entries field" can be illustrated with an example. Here, "AP combination" can include one or more APs. That is, 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. As mentioned above... Figure 3Taking the illustrated application scenario as an example, 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 the non-AP MLD discovers that it needs to perform a BSS transition. AP MLD 1 sends a BTM request frame to the non-AP MLD, carrying information and recommendation levels of AP MLD2, AP MLD3, and AP MLD4. Assume that AP MLD2 has 3 APs, namely AP2-1, AP2-2, and AP2-3; AP MLD 3 has 2 APs, namely AP3-1 and AP3-2; and AP MLD 4 has 2 APs, namely AP4-1 and AP4-2. Furthermore, assume that the BSS Transition CandidateList Entries field includes a total of 3 neighbor report elements. Neighbor report element 1 recommends the combination of AP2-1 and AP2-2 of AP MLD2, neighbor report element 2 recommends AP MLD 3 (that is, all APs belonging to AP MLD3 are recommended), and neighbor report element 3 recommends AP4-2 of AP MLD 4. The phrase "AP combinations not recommended in the (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" can also include two or more APs; this embodiment of the application does not impose any limitations.

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

[0185] In this context, 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; this embodiment of the application does not impose any restrictions.

[0186] In one possible implementation, the BSS Transition Candidate List Entries field's BSS Transition Candidate Preference subelement includes a Preference field. For example, the meaning of this Preference field can retain its existing meaning, or the meaning of this Preference field can change as the standard evolves; this application embodiment is not limited to this. Alternatively, the Preference field can be used to indicate the degree of recommendation for an AP combination. This AP combination can be an AP combination recommended by the neighbor reporting element to which the Preference field belongs. That is, this AP combination is a specific AP combination recommended by a target AP MLD listed in the BSS Transition Candidate List Entries field.

[0187] This application's embodiments expand the meaning of the Abridged field to simultaneously indicate the processing method for BSSIDs or AP MLDs not listed in the BSSTransition Candidate List Entries field, and the processing method for AP combinations not recommended among the candidate target AP MLDs listed in the BSSTransition Candidate List Entries field. This improves the information indication, making it clearer for non-AP MLDs the attitude and behavior of the currently associated AP MLD. Furthermore, the meaning of this application's embodiments is clear, without adding overhead, and has good compatibility.

[0188] Furthermore, embodiments of this application also modify the meaning of the Preference field so that when recommending a certain AP combination of AP MLD, the neighbor report element can indicate the degree of recommendation for that combination.

[0189] Example 4

[0190] Embodiment 4 of this application mainly introduces a method for improving information indication by using bits in neighbor report elements.

[0191] See Figure 13 , Figure 13 This is a schematic diagram of the fourth type of information indication method in BTM provided in the embodiments of this application. For example... Figure 13 As shown, the information indication method in this BTM includes, but is not limited to, the following steps:

[0192] S401, the AP MLD generates a BTM request frame, which includes one or more neighbor report elements. One of the neighbor report elements is used to carry information about a candidate target AP MLD. The neighbor report element includes second indication information, which is used 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 to which the second indication information belongs.

[0193] S402, the AP MLD sends the BTM request frame. Correspondingly, the non-AP MLD receives the BTM request frame.

[0194] S403, the non-AP MLD parses the BTM request frame. For example, by parsing the second indication information in the BTM request frame, the non-AP MLD can obtain the processing method for APs that do not appear in the AP combination of the candidate target AP carried by the neighbor report element to which this second indication information belongs.

[0195] In one possible implementation, the format of the Action field in the BTM request frame can be as described above. Figure 4 As shown, this will not be repeated here. The Action field of this BTM request frame may include, but is not limited to, the BSS Transition Candidate List Entries field. The BSS Transition Candidate List Entries field includes one or more neighbor report elements. 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 level of different target BSS candidates or candidate target AP MLDs. The frame format of each neighbor report element can be as described above. Figure 5 As shown, I will not go into details here.

[0196] In one possible implementation, each neighbor report element includes a second indication information. This second indication information can be used to indicate the handling method for APs that do 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. Since one neighbor report element corresponds to one candidate target AP MLD, the second indication information can be briefly described as: indicating the handling method for APs that do not appear in a certain AP combination of a certain candidate target AP MLD. It can be understood that an "AP combination" can contain one or more APs. That is, a single AP can also be considered as an AP combination, and all APs belonging to an AP MLD can also be considered as an AP combination.

[0197] For example, as mentioned above Figure 3Taking the illustrated application scenario as an example, 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 the non-AP MLD discovers that it 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, and the BSS Transition Candidate ListEntries field includes one neighbor report element. The BSSID field of this neighbor report element is the MAC address of AP2-1 in AP MLD 2, and the Link Info field has a Per-STAProfile subelement, which corresponds to AP2-2 in AP MLD 2. Therefore, this neighbor report element indicates that the combination of AP2-1 and AP2-2 in AP MLD 2 is recommended. At this point, the second indication information in this neighbor report element is used to indicate how to handle AP2-3, which does not appear in the combination of AP2-1 and AP2-2 carried by this neighbor report element MLD2.

[0198] 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 opposes the receiver associating 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. When the second indication information is a second value, it indicates that the sender of the BTM request frame opposes or excludes the receiver associating 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. The first value can be 1 or 0; correspondingly, the second value can be 0 or 1; this embodiment does not impose any limitations.

[0199] In one possible implementation, the aforementioned second indication information can be carried in the BSSID information field of the neighbor report element. For example, the second indication information can be characterized using reserved bits in the BSSID information field. Alternatively, the Extremely High Throughput bits in the BSSID information field can be reused to indicate the processing method for APs not appearing in the AP combination of the candidate target AP MLD carried by the neighbor report element. See also Figure 14 , Figure 14This is a schematic diagram of the frame format of the BSSID information field provided in an embodiment of this application. For example... Figure 14 As shown, a reserved bit in the BSSID information field can be used as the second indication information. When the second indication information is 1, it indicates that the sender of the BTM request frame objects to or excludes APs not appearing 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 second indication information is 0, it indicates that the sender of the BTM request frame neither recommends nor objects to APs not appearing in the AP combination of the candidate target AP MLD carried by the neighbor report element to which this second indication information belongs.

[0200] Understandable. Figure 14 This is merely an example; the embodiments of this application do not limit the bit length of the second indication information, nor do they limit the correspondence between the value and meaning of the second indication information.

[0201] In this embodiment of the application, a reserved bit is used in the BSSID information field of the Neighbor Report element to indicate the handling method for APs that do not appear in the AP combinations 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 handling method, which is flexible.

[0202] In another possible implementation, the aforementioned second indication information can be carried in the BSS transition candidate preference sub-element of the neighbor report element. For example, since the existing BSS transition candidate preference sub-element is not scalable, the length of the Preference field can be shortened to less than or equal to 7 bits, without changing the meaning of the Preference field; and the one or more bits saved by shortening the Preference field can be used to represent the second indication information. In other words, the Preference field in the BSS transition 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 is understood that the embodiments of this application do not limit the meaning of the Preference field, only change the length of the Preference field; the meaning of the Preference field can change with the evolution of the standard.

[0203] See Figure 15 , Figure 15This is a schematic diagram of another frame format for BSS conversion candidate preference sub-elements provided in an embodiment of this application. For example... Figure 15 As shown, the length of the Preference field can be shortened from 1 byte (8 bits) to 7 bits, with the saved 1 bit used as secondary indication information. For example, the least significant bit (LSB) of this 1 byte (B0 to B7), i.e., B0, can be used as the secondary indication information. When the value of the secondary indication information (such as B0) is 0, it indicates that the sender of the BTM request frame opposes or excludes APs that do not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which this secondary indication information belongs, associated with the receiver of the BTM request frame. When the value of the secondary 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 associating APs that do not appear in the AP combination of the candidate target AP MLD carried by the neighbor report element to which this secondary indication information belongs, associated with the receiver of the BTM request frame. This provides better compatibility with traditional sites (i.e., single-link sites).

[0204] Understandable. Figure 15 This is merely an example; the embodiments of this application do not limit the bit length of the second indication information, nor do they limit the correspondence between the value and meaning of the second indication information.

[0205] This application embodiment carries a second indication information in the BSS transformation candidate preference sub-element of the Neighbor Report element to indicate how to handle APs that do not appear in the AP combinations 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 handling method, offering flexibility. Furthermore, the second indication information is used simultaneously with the Preference value; that is, the second indication information will not appear when the Neighbor Report element is not used for recommendation.

[0206] In one possible implementation, the BSS transformation candidate preference sub-element of the neighbor report element includes a Preference field. The meaning of this Preference field can be found in the relevant description in the aforementioned Embodiment 1, and will not be repeated here.

[0207] In this embodiment, the neighbor report element carries a second indication information to indicate how to handle APs that do not appear in a certain AP combination in a single candidate target AP MLD, so that each recommended AP combination can have its own handling method, making it flexible to use.

[0208] Example 5

[0209] Embodiment 5 of this application mainly introduces a method to improve information indication by redefining the recommended AP combination in the Link Info field.

[0210] See Figure 16 , Figure 16 This is a schematic diagram of the fifth type of information indication method in BTM provided in the embodiments of this application. For example... Figure 16 As shown, the information indication method in this BTM includes, but is not limited to, the following steps:

[0211] S501, the AP MLD generates a BTM request frame. This BTM request frame includes one or more neighbor report elements, one of which carries information about a candidate target AP MLD. This neighbor report element includes a per-STA profile sub-element for any AP that is not banned among the candidate target AP MLDs. Optionally, this per-STA profile sub-element also includes third indication information, which can be used to indicate the processing method for the AP corresponding to this per-STA profile sub-element.

[0212] S502, the AP MLD sends the BTM request frame. Correspondingly, the non-AP MLD receives the BTM request frame.

[0213] S503, the non-AP MLD parses the BTM request frame. For example, by parsing the neighbor report element in the BTM request frame, the non-AP MLD can obtain information about APs that are not blocked in the candidate target AP MLD. Furthermore, by parsing the per-STA profile sub-element in the neighbor report element, the non-AP MLD can obtain the processing method for the AP corresponding to that per-STA profile sub-element.

[0214] In one possible implementation, the format of the Action field in the BTM request frame can be as described above. Figure 4As shown, this will not be repeated here. The Action field of this BTM request frame may include, but is not limited to, the BSS Transition Candidate List Entries field. The BSS Transition Candidate List Entries field includes one or more neighbor report elements. 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 level of different target BSS candidates or candidate target AP MLDs. The frame format of each neighbor report element can be as described above. Figure 5 As shown, I will not go into details here.

[0215] A neighbor report element can include a basic multi-link subelement corresponding to a candidate target AP MLD. The frame format of this basic multi-link subelement can be as described above. Figure 6 As shown, this will not be elaborated further. It can be understood that if an AP MLD wants to recommend a specific AP combination from a candidate AP MLD to a non-AP MLD, it needs to add the Neighbor Report element of any AP in that AP combination to the BSS Transition Candidate List Entries field (i.e., the BSSID field of the Neighbor Report element is the MAC address of any AP in that AP combination), and add a Basic Multi-Link subelement to this Neighbor Report element. The Per-STAProfile subelements of other APs in this AP combination will be added to the Link Info field of this BasicMulti-Link subelement. In short, the Link Info field carries the Per-STAProfile subelements of the other APs in the recommended AP combination besides the AP indicated by the BSSID field.

[0216] In this embodiment, if the AP MLD recommends a combination of APs from 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 that AP combination. However, the Link Info field of the Basic Multi-Link subelement includes the Per-STA Profile subelement of any AP in the candidate target AP MLD that is not banned (associated). Optionally, each Per-STA Profile subelement also includes third indication information. This third indication information can be used to indicate the processing method for the AP corresponding to the Per-STA Profile subelement. One Per-STA Profile subelement corresponds to one unbanned AP in the candidate target AP MLD. Here, "unbanned" can include at least two meanings: "recommended" and "neither recommended nor opposed." This embodiment also defaults to prohibiting association with APs not appearing in the Neighbor Report element. Here, "APs not appearing in the NeighborReport element" can refer to APs other than those indicated by the BSSID field and those corresponding to the Per-STAProfile subelement in the candidate target APMLD carried by this Neighbor Report element.

[0217] In one possible implementation, when the third indication information in a Per-STA Profile subelement is a first value, it indicates that the sender of the aforementioned BTM request frame neither recommends nor opposes the receiver of the BTM request frame associating with the AP corresponding to this 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 aforementioned BTM request frame recommends the receiver of the BTM request frame associating with the AP corresponding to this Per-STA Profile subelement. The first value can be 0 or 1; correspondingly, the second value can be 1 or 0; this embodiment of the application does not impose any limitations.

[0218] In one possible implementation, the aforementioned third indication information can be carried in the STA control field of the Per-STA Profilesubelement. For example, a reserved bit in the STA Control field of the Per-STA Profilesubelement can be used to characterize the third indication information. See also Figure 17 , Figure 17 This is a schematic diagram of the frame format of the STAControl field provided in the embodiments of this application. Figure 17 For ease of description, the third instruction information is referred to as the recommended field. It is understood that in practical applications, the third instruction information may have other field names, and this application embodiment does not impose any restrictions. For example... Figure 17 As shown, the STAControl field includes, but is not limited to, a Recommended field. For example, the Recommended field is one bit long. When the Recommended field value is 1, it indicates that the AP MLD recommends that the non-AP MLD associate with the AP corresponding to the Per-STA Profile subelement to which the Recommended field belongs. When the Recommended field value is 0, it indicates that the AP MLD neither recommends nor opposes the non-AP MLD associating with the AP corresponding to the Per-STA Profile subelement to which the Recommended field belongs. It can be understood that whether a Recommended field value of 1 or 0 indicates a recommendation is not limited in this embodiment. Figure 17 This is merely an example, and the embodiments of this application do not limit the length of the Recommended field.

[0219] In this embodiment, APs not appearing in the Neighbor Report element are prohibited from association by default. APs corresponding to the Per-STA Profile subelements that do appear are indicated by third-party information as to whether association is recommended. Since 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, making it very flexible to use.

[0220] Example 6

[0221] Embodiment Six of this application mainly introduces the default handling method for APs that do not appear in the candidate target AP MLD listed in the BSS Transition Candidate List Entries field.

[0222] See Figure 18 , Figure 18 This is a schematic diagram of the sixth type of information indication method in BTM provided in the embodiments of this application. For example... Figure 18 As shown, the information indication method in this BTM includes, but is not limited to, the following steps:

[0223] S601, AP MLD generates BTM request frame.

[0224] S602, the AP MLD sends the BTM request frame. Correspondingly, the non-AP MLD receives the BTM request frame.

[0225] S603, non-AP MLD parses the BTM request frame.

[0226] In one possible implementation, the format of the Action field in the BTM request frame can be as described above. Figure 4 As shown, this will not be repeated here. The Action field of this BTM request frame may include, but is not limited to, the BSS Transition Candidate List Entries field and the Request Mode field. The frame format of the Request Mode field can be as described above. Figure 8 As shown, details will not be repeated here. The Request Mode field includes an Abridged field. This 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. For APs listed in the BSS Transition Candidate List Entries field that do not appear in any recommended AP combinations, the default rules can be used for processing.

[0227] In one possible implementation, the default rule mentioned above may include any of the following: exclude / oppose APs that are not recommended in the candidate target AP MLD appearing in the BSS Transition Candidate List Entries field; neither recommend nor oppose APs that are not recommended in the candidate target AP MLD appearing in the BSS Transition Candidate List Entries field; and require non-AP MLDs to treat APs that are not recommended in the AP MLD appearing in the BSS Transition Candidate List Entries field as having a specific preference value, such as 1. Here, "not recommended AP" can mean either "AP that does not appear in any recommended AP combination" or "AP that does not appear in any recommended AP combination".

[0228] This application embodiment improves information indication by designing a default handling method for APs that do not appear in the candidate target AP MLDs listed in the BSS Transition Candidate List Entries field. This allows non-AP MLDs to more clearly understand the attitude and behavior of the currently associated AP MLD. Furthermore, this application embodiment does not modify any fields in the BTM request frame and does not increase overhead.

[0229] The foregoing details the method provided in this application. To facilitate the implementation of the above-described solutions in the embodiments of this application, corresponding apparatus or devices are also provided in the embodiments of this application.

[0230] This application divides AP MLD and non-AP MLD into functional modules based on the above method embodiments. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The following will combine... Figures 19 to 21 The AP MLD and non-APMLD of embodiments of this application are described in detail.

[0231] See Figure 19 , Figure 19 This is a schematic diagram of the communication device provided in an embodiment of this application, as shown below. Figure 19As shown, 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 for data processing. The transceiver unit 10 can also be called a communication interface or a communication unit, etc.

[0232] In some embodiments of this application, the communication device may be the AP MLD shown above. That is... Figure 19 The communication device shown can be used to perform the steps or functions executed by the AP MLD in the above method embodiments. For example, the communication device can be the AP MLD or a chip or functional module configured in the AP MLD, etc., and this application embodiment does not limit this. The transceiver unit 10 is used to perform transceiver-related operations of the AP MLD in the above method embodiments, and the processing unit 20 is used to perform AP MLD processing-related operations in the above method embodiments.

[0233] For example, processing unit 20 is used to generate a BTM request frame, which includes a BSS conversion candidate list entry field and first indication information. The first indication information is used to indicate the processing method for BSSIDs or AP MLDs that are not listed in the BSS conversion candidate list entry field, and the processing method for APs that do not appear in any recommended AP combinations among the candidate target AP MLDs listed in the BSS conversion candidate list entry field. Transceiver unit 10 is used to send or output the BTM request frame.

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

[0235] It is understood that specific descriptions of the BTM request frame, the BSS conversion candidate list entry field, and the first indication information can be found in the method embodiment one or two shown above, and will not be detailed here.

[0236] It is understood that the specific descriptions of the transceiver unit and processing unit shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver unit and processing unit, please refer to the above method embodiments one or two (e.g., ...). Figure 9 or Figure 10 (This will not be elaborated on here.)

[0237] For example, 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, which is used to indicate the processing method for BSSIDs or AP MLDs not listed in the BSS conversion candidate list entry field, and the processing method for AP combinations not recommended in the candidate target AP MLDs listed in the BSS conversion candidate list entry field. Transceiver unit 10 is used to send or output the BTM request frame.

[0238] It is understood that for specific explanations of the BTM request frame, BSS conversion candidate list entry field, request mode field, and simplified field, please refer to the method embodiment three shown above, which will not be detailed here.

[0239] It is understood that the specific descriptions of the transceiver unit and processing unit shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver unit and processing unit, please refer to the above-described method embodiment three (e.g., Figure 12 (This will not be elaborated on here.)

[0240] For example, 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. The neighbor report element includes second indication information, which is used 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 to which the second indication information belongs; transceiver unit 10 is used to send or output the BTM request frame.

[0241] It is understood that specific descriptions of the BTM request frame, neighbor report element, and second indication information can be found in the method embodiment four shown above, and will not be detailed here.

[0242] It is understood that the specific descriptions of the transceiver unit and processing unit shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver unit and processing unit, please refer to the above-described method embodiment four (e.g., Figure 13 (This will not be elaborated on here.)

[0243] For example, 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 a per-STA profile sub-element of any AP that is not banned in the candidate target AP MLD; transceiver unit 10 is used to send or output the BTM request frame.

[0244] It is understood that for specific explanations of BTM request frames, neighbor report elements, and per-STA configuration file sub-elements, please refer to the method embodiment five shown above, which will not be detailed here.

[0245] It is understood that the specific descriptions of the transceiver unit and processing unit shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver unit and processing unit, please refer to the above-described method embodiment five (e.g., Figure 16 (This will not be elaborated on here.)

[0246] Reuse Figure 19 In other embodiments of this application, the communication device may be the non-APMLD shown above. That is... Figure 19 The communication device shown can be used to perform the steps or functions executed by the non-AP MLD in the above method embodiments. For example, the communication device can be a non-AP MLD or a chip or functional module configured in the non-AP MLD, etc., and this application embodiment does not limit this. The transceiver unit 10 is used to perform transceiver-related operations of the non-AP MLD in the above method embodiments, and the processing unit 20 is used to perform non-AP MLD processing-related operations in the above method embodiments.

[0247] For example, 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. The first indication information is used to indicate the processing method for BSSIDs or AP MLDs that are not listed in the BSS conversion candidate list entry field, and the processing method for APs that do not appear in any recommended AP combinations 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.

[0248] It is understood that transceiver unit 10 can receive BTM request frames from other communication devices, or it can input the BTM request frame from other components or other functional modules in the AP MLD. The explanations regarding other information input by the transceiver unit are similar and will not be detailed below.

[0249] It is understood that specific descriptions of the BTM request frame, the BSS conversion candidate list entry field, and the first indication information can be found in the method embodiment one or two shown above, and will not be detailed here.

[0250] It is understood that the specific descriptions of the transceiver unit and processing unit shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver unit and processing unit, please refer to the above method embodiments one or two (e.g., ...). Figure 9 or Figure 10(This will not be elaborated on here.)

[0251] For example, 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 includes a simplified field, which is used to indicate the processing method for BSSIDs or AP MLDs not listed in the BSS conversion candidate list entry field, and the processing method for AP combinations not recommended in 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.

[0252] It is understood that for specific explanations of the BTM request frame, BSS conversion candidate list entry field, request mode field, and simplified field, please refer to the method embodiment three shown above, which will not be detailed here.

[0253] It is understood that the specific descriptions of the transceiver unit and processing unit shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver unit and processing unit, please refer to the above-described method embodiment three (e.g., Figure 12 (This will not be elaborated on here.)

[0254] For example, 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. The neighbor report element includes second indication information, which is used 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 to which the second indication information belongs; the processing unit 20 is used to parse the BTM request frame.

[0255] It is understood that specific descriptions of the BTM request frame, neighbor report element, and second indication information can be found in the method embodiment four shown above, and will not be detailed here.

[0256] It is understood that the specific descriptions of the transceiver unit and processing unit shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver unit and processing unit, please refer to the above-described method embodiment four (e.g., Figure 13 (This will not be elaborated on here.)

[0257] For example, 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. The neighbor report element includes a per-STA profile sub-element of any AP that is not banned in the candidate target AP MLD; the processing unit 20 is used to parse the BTM request frame.

[0258] It is understood that for specific explanations of BTM request frames, neighbor report elements, and per-STA configuration file sub-elements, please refer to the method embodiment five shown above, which will not be detailed here.

[0259] It is understood that the specific descriptions of the transceiver unit and processing unit shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver unit and processing unit, please refer to the above-described method embodiment five (e.g., Figure 16 (This will not be elaborated on here.)

[0260] The above describes the non-AP MLD and AP MLD of embodiments of this application. The following describes the possible product forms of the non-AP MLD and AP MLD. It should be understood that any product possessing the above-described features... Figure 19 Any product of any form that possesses the aforementioned non-AP MLD functionality, or any product that has the above-mentioned features. Figure 19 Any form of product that incorporates the functions of the described AP MLD falls within the protection scope of the embodiments of this application. It should also be understood that the following description is merely illustrative and does not limit the product forms of non-AP MLDs and AP MLDs in the embodiments of this application to these examples.

[0261] In one possible implementation, Figure 19 In the communication device shown, the processing unit 20 can be one or more processors, and the transceiver unit 10 can be a transceiver, or the transceiver unit 10 can also be a transmitting unit and a receiving unit. The transmitting unit can be a transmitter, and the receiving unit can be a receiver. The transmitting unit and the receiving unit are integrated into one device, such as a transceiver. In the embodiments of this application, the processor and the transceiver can be coupled, etc., and the connection method between the processor and the transceiver is not limited in the embodiments of this application. In the process of executing the above method, the process of sending information (such as sending a BTM request frame, etc.) in the above method can be understood as the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After the above information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information (such as receiving a BTM request frame, etc.) in the above method can be understood as the process of the processor receiving the input above information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the aforementioned information, the information may need to undergo further processing before being input into the processor.

[0262] See Figure 20 , Figure 20This is another schematic diagram of the communication device provided in the embodiments of this application. The communication device can be an AP MLD or a non-AP MLD, or a chip therein. Figure 20 Only the main components of the communication device are shown. In addition to the processor 1001 and transceiver 1002, the communication device may further include a memory 1003 and input / output devices (not shown).

[0263] The processor 1001 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs. The memory 1003 is mainly used to store software programs and data. The transceiver 1002 may include control circuitry and an antenna. The control circuitry is mainly used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0264] 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 transmitted wirelessly, the processor 1001 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF 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.

[0265] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

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

[0267] For example, the communication device can be used to perform the functions of the AP MLD in the aforementioned embodiment one: the processor 1001 can be used to perform... Figure 9 Step S101, and / or other processes for performing the techniques described herein; transceiver 1002 can be used to perform Figure 9 Step S102 in the document, and / or other processes used in the techniques described herein.

[0268] For example, the communication device can be used to perform the functions of the non-AP MLD in the aforementioned embodiment one: the processor 1001 can be used to perform... Figure 9 The transceiver 1002 may be used to receive BTM request frames and / or other processes for performing the techniques described herein.

[0269] For example, the communication device can be used to perform the functions of the AP MLD in the aforementioned embodiment two: the processor 1001 can be used to perform... Figure 10 Step S201, and / or other processes used to perform the techniques described herein; transceiver 1002 can be used to perform Figure 10 Step S202 in the document, and / or other processes used in the techniques described herein.

[0270] For example, the communication device can be used to perform the functions of the non-AP MLD in the aforementioned embodiment two: the processor 1001 can be used to perform... Figure 10 The transceiver 1002 may be used to receive BTM request frames and / or other processes for performing the techniques described herein.

[0271] For example, 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 perform... Figure 12 Step S301, and / or other processes for performing the techniques described herein; transceiver 1002 can be used to perform Figure 12 Step S302 in the document, and / or other processes used in the techniques described herein.

[0272] For example, 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 perform... Figure 12 The transceiver 1002 may be used to receive BTM request frames and / or other processes for performing the techniques described herein.

[0273] For example, the communication device can be used to perform the functions of the AP MLD in the aforementioned embodiment four: the processor 1001 can be used to perform... Figure 13 Step S401, and / or other processes for performing the techniques described herein; transceiver 1002 can be used to perform Figure 13 Step S402 in the document, and / or other processes used in the techniques described herein.

[0274] For example, 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 perform... Figure 13 The transceiver 1002 may be used to receive BTM request frames and / or other processes for performing the techniques described herein.

[0275] For example, 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... Figure 16 Step S501, and / or other processes for performing the techniques described herein; transceiver 1002 can be used to perform Figure 16 Step S502 in the document, and / or other processes used in the techniques described herein.

[0276] For example, the communication device can be used to perform the functions of the non-AP MLD in the aforementioned embodiment five: the processor 1001 can be used to perform... Figure 16 The transceiver 1002 may be used to receive BTM request frames and / or other processes for performing the techniques described herein.

[0277] For example, 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... Figure 18 Step S601, and / or other processes for performing the techniques described herein; transceiver 1002 can be used to perform Figure 18 Step S602 in the document, and / or other processes used in the techniques described herein.

[0278] For example, 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 perform... Figure 18 The transceiver 1002 may be used to receive BTM request frames and / or other processes for performing the techniques described herein.

[0279] In one implementation, the processor 1001 may store instructions, which may be a computer program. The computer program runs on the processor 1001 and causes the communication device to execute the methods described in the above method embodiments. The computer program may be embedded in the processor 1001; in this case, the processor 1001 may be implemented in hardware.

[0280] In one implementation, the communication device may include a circuit that can perform the functions of transmitting, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal-oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0281] It is understood that the communication device shown in the embodiments of this application may also have more than Figure 20 This application does not limit the use of other components or other related elements. The methods performed by the processor and transceiver shown above are merely examples; for the specific steps performed by the processor and transceiver, please refer to the description of the method embodiments above.

[0282] In another possible implementation, Figure 19 In the communication device shown, 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. Alternatively, the transceiver unit 10 can also be a transmitting unit and a receiving unit. The transmitting unit can be an output interface, and the receiving unit can be an input interface. The transmitting unit and the receiving unit are integrated into one unit, such as an input / output interface. See also Figure 21 , Figure 21 This is another structural schematic diagram of the communication device provided in the embodiments of this application. For example... Figure 21 As shown, Figure 21The communication device shown includes logic circuitry 901 and interface 902. That is, the processing unit 20 can be implemented using logic circuitry 901, and the transceiver unit 10 can be implemented using interface 902. The logic circuitry 901 can be a chip, processing circuit, integrated circuit, or system-on-chip (SoC) chip, etc., and the interface 902 can be a communication interface, input / output interface, pins, etc. For example, Figure 21 The above-mentioned communication device is used as an example of a chip, which includes a logic circuit 901 and an interface 902.

[0283] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method between the logic circuit and the interface is not limited in this embodiment.

[0284] In some embodiments of this application, the communication device can be used to perform the methods, steps, or functions executed by APMLD in any of the above method embodiments.

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

[0286] In other embodiments of this application, the communication device can be used to perform methods, steps, or functions performed by non-AP MLD in any of the above method embodiments.

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

[0288] It is understood that specific details regarding BTM request frames, etc., can be found in the method implementation examples shown above, and will not be elaborated upon here.

[0289] It is understood that the communication device shown in the embodiments of this application can implement the method provided in the embodiments of this application in hardware form or in software form, etc., and the embodiments of this application do not limit it in this way.

[0290] for Figure 21 For specific implementations of the various embodiments shown, please refer to the above embodiments, which will not be described in detail here.

[0291] This application also provides a wireless communication system including a non-AP MLD and an AP MLD, which can be used to perform the methods in any of the foregoing embodiments.

[0292] In addition, this application also provides a computer program for implementing the operations and / or processes performed by the non-AP MLD in the method provided in this application.

[0293] This application also provides a computer program for implementing the operations and / or processes performed by APMLD in the method provided in this application.

[0294] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform operations and / or processes performed by non-APMLD in the method provided in this application.

[0295] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform the operations and / or processes performed by the AP MLD in the method provided in this application.

[0296] This application also provides a computer program product comprising computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by a non-AP MLD device in the method provided in this application to be executed.

[0297] This application also provides a computer program product comprising computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by APMLD in the method provided in this application to be executed.

[0298] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, or it may be an electrical, mechanical, or other form of connection.

[0299] The units described as separate components may or may not be physically separate. 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 can be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of this application.

[0300] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0301] If the integrated unit is implemented as 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 this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned readable storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0302] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An information indication method in basic service set conversion management, characterized in that, include: Access point multi-link device (AP MLD) generates Basic Service Set Transformation Management (BTM) request frame. The BTM request frame includes a Basic Service Set (BSS) transformation candidate list entry field and a request mode field. The request mode field includes a simplified field, which is used to indicate the processing method for AP combinations that are not recommended in the candidate target AP MLD listed in the BSS transformation candidate list entry field. The AP MLD sends the BTM request frame.

2. The method according to claim 1, characterized in that, The simplified field is used to indicate the processing method for AP combinations that are not recommended in the candidate target AP MLDs listed in the BSS transformation candidate list field, including: When the simplified field is the first value, it means that the AP MLD neither recommends nor opposes associating with AP combinations that are not recommended in the candidate target AP MLD that appear in the BSS conversion candidate list entry field; When the simplified field is the second value, it means that the AP MLD excludes AP combinations that are not recommended in the candidate target AP MLDs that appear in the BSS conversion candidate list entry field.

3. The method according to claim 1, characterized in that, The simplified field is also used to indicate the processing method for Basic Service Set Identifier (BSSID) or AP MLD that is not listed in the BSS conversion candidate list entry field.

4. The method according to claim 3, characterized in that, The simplified field is also used to indicate the processing method for Basic Service Set Identifier (BSSID) or AP MLD that is not listed in the BSS transformation candidate list entry field, including: When the simplified field is the first value, it means that the AP MLD neither recommends nor opposes associating with a BSSID or AP MLD that does not appear in the BSS conversion candidate list entry field; When the simplified field is the second value, it means that the AP MLD exclusion association does not appear in the BSSID or AP MLD in the BSS conversion candidate list entry field.

5. The method according to any one of claims 1 to 4, characterized in that, The BSS conversion candidate preference sub-element of the BSS conversion candidate list entry field includes a preference field, which indicates the degree of recommendation of the AP combination of the candidate target AP MLD listed in the BSS conversion candidate list entry field.

6. An access point multi-link device (AP MLD), characterized in that, include: The processing unit is used to generate a Basic Service Set Transformation Management (BTM) request frame. The BTM request frame includes a Basic Service Set (BSS) Transformation Candidate List Entry Field and a Request Mode Field. The Request Mode Field includes a Simplification Field, which is used to indicate the processing method for AP combinations that are not recommended in the candidate target AP MLDs listed in the BSS Transformation Candidate List Entry Field. The transceiver unit is used to send the BTM request frame.

7. The Access Point Multi-Link Device (AP MLD) according to claim 6, characterized in that, The simplified field is used to indicate the processing method for AP combinations that are not recommended in the candidate target AP MLDs listed in the BSS transformation candidate list field, including: When the simplified field is the first value, it means that the AP MLD neither recommends nor opposes associating with AP combinations that are not recommended in the candidate target AP MLD that appear in the BSS conversion candidate list entry field; When the simplified field is the second value, it means that the AP MLD excludes AP combinations that are not recommended in the candidate target AP MLDs that appear in the BSS conversion candidate list entry field.

8. The Access Point Multi-Link Device (AP MLD) according to claim 6, characterized in that, The simplified field is also used to indicate the processing method for Basic Service Set Identifier (BSSID) or AP MLD that is not listed in the BSS conversion candidate list entry field.

9. The Access Point Multi-Link Device (AP MLD) according to claim 8, characterized in that, The simplified field is also used to indicate the processing method for Basic Service Set Identifier (BSSID) or AP MLD that is not listed in the BSS transformation candidate list entry field, including: When the simplified field is the first value, it means that the AP MLD neither recommends nor opposes associating with a BSSID or AP MLD that does not appear in the BSS conversion candidate list entry field; When the simplified field is the second value, it means that the AP MLD exclusion association does not appear in the BSSID or AP MLD in the BSS conversion candidate list entry field.

10. The Access Point Multilink Device (AP MLD) according to any one of claims 6 to 9, characterized in that, The BSS conversion candidate preference sub-element of the BSS conversion candidate list entry field includes a preference field, which indicates the degree of recommendation of the AP combination of the candidate target AP MLD listed in the BSS conversion candidate list entry field.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, which, when executed, performs the method as described in any one of claims 1 to 5.

Images