Access point (AP) multi-link device discovery method and related device

Abstract

Provided in an embodiment of the present application are an access point (AP) multilink device discovery method and a related device, for example, applied to a WLAN supporting 802.11 be, the method comprising: a report AP sending a first management frame to a site, the first management frame carrying information of a neighbor AP, the report AP belonging to an AP multilink device, and the neighbor AP belonging to the AP multilink device; the reported AP indicated by the neighbor AP information and the reporting AP belong to the same multi-link device or belong to the same multi-BSSID set with other APs in the multi-link device where the reporting AP is located; therefore, the site receiving the first management frame can know the MLD structure and the multi-BSSID set structure on the AP multi-link equipment, so that the site can better select a proper AP for association.

Description

[0001] This application is a divisional application. The application number of the original application is 202010763205.0, and the original application date is July 31, 2020. The entire contents of the original application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a node AP multi-link device discovery method and related apparatus. Background Art

[0003] In order to significantly improve the service transmission rate of the WLAN system, the Institute of Electrical and Electronics Engineers (IEEE) 802.11ax standard further adopts Orthogonal Frequency Division Multiple Access (OFDMA) technology based on the existing Orthogonal Frequency Division Multiplexing (OFDM) technology. OFDMA technology supports multiple nodes to send and receive data at the same time, thereby achieving multi-site diversity gain. In 2017, when 802.11ax was finalized, the Federal Communications Commission (FCC) opened a new free frequency band of 5925-7125MHz, hereinafter referred to as 6GHz. Therefore, the 802.11ax standard workers expanded the operating range of 802.11ax devices from 2.4GHz and 5GHz to 2.4GHz, 5GHz and 6GHz in the 802.11ax Project Authorization Requests (PAR).

[0004] IEEE 802.11 next generation WiFi protocol (extremely high throughput, EHT) devices need to be forward compatible, so they will also support the working spectrum of 802.11ax devices, that is, they will support 2.4GHz, 5GHz and 6GHz bands. According to the latest free 6GHz band, based on the frequency band for channel division, the supported bandwidth can exceed the maximum bandwidth of 160MHz supported in 5GHz, such as 320MHz. In addition to ultra-large bandwidth, IEEE 802.11ax next generation WiFi-extremely high throughput can also improve peak throughput through more streams, such as increasing the number of streams to 16 streams, and multiple frequency bands (2.4GHz, 5GHz and 6GHz) cooperation. On the same frequency band, peak throughput can also be improved and service transmission latency can be reduced by cooperating with multiple channels. Multi-band or multi-channel is collectively referred to as multi-link below. Although 802.11ax and previous WiFi networks with the same operating frequency band are configured with multiple links, generally speaking, each multi-link establishes a different Basic Service Set (BSS), and at one time only one link can communicate with sites in the BSS to which the link belongs.

[0005] 802.11ax and earlier introduced the Multiple Basic Service Set Identifier (BSSID) technology, whose main function is to virtualize multiple logical APs on a physical AP, that is, to form multiple virtual networks, each of which is used to manage different sites separately, similar to the AP products in the current WIFI scenario, in which one AP can virtualize a home AP (home AP) and a client AP (guest AP).

[0006] How to enable a site to quickly discover an AP multi-link device, thereby helping the site to quickly find a suitable AP for association, is a technical problem being studied by technicians in this field. Summary of the invention

[0007] The embodiment of the present application discloses an AP multi-link device discovery method and related apparatus, which can better perform link discovery.

[0008] In a first aspect, an embodiment of the present application provides an AP multi-link device discovery method, the method comprising:

[0009] The reporting AP sends a first management frame to the station, wherein the first management frame carries information of a neighboring AP, and the reporting AP belongs to an AP multi-link device.

[0010] The neighbor AP information includes one or more of the first information, the second information, and the third information, wherein;

[0011] The first information is used to indicate whether the reported AP is in the same MLD as the reporting AP or whether the reported AP and members of the MLD to which the reporting AP belongs belong to the same multi-BSSID set;

[0012] The second information is used to indicate whether the reported AP and the members of the MLD to which the reporting AP belongs belong to the same multi-BSSID set;

[0013] The third information is used to indicate whether the reported AP and the reporting AP belong to the same MLD.

[0014] In the above method, by carrying the MLD information of the reported AP and the Multiple BSSID set information in the simplified neighbor report element of the first management frame, the station receiving the first management frame can obtain the basic situation of each reported AP in the MLD and the Multiple BSSID set based on this information, so as to better select the appropriate AP from the reporting AP and the reported AP for association.

[0015] In a second aspect, an embodiment of the present application provides an AP multi-link device discovery method, the method comprising:

[0016] The station receives a first management frame sent by a reporting AP, wherein the first management frame carries information of a neighboring AP, and the reporting AP belongs to an AP multi-link device.

[0017] The neighbor AP information includes one or more of the first information, the second information, and the third information, wherein;

[0018] The first information is used to indicate whether the reported AP is in the same MLD as the reporting AP or whether the reported AP and members of the MLD to which the reporting AP belongs belong to the same multi-BSSID set;

[0019] The second information is used to indicate whether the reported AP and the members of the MLD to which the reporting AP belongs belong to the same multi-BSSID set;

[0020] The third information is used to indicate whether the reported AP and the reporting AP belong to the same MLD.

[0021] In the above method, by carrying the MLD information of the reported AP and the Multiple BSSID set information in the simplified neighbor report element of the first management frame, the station receiving the first management frame can obtain the basic situation of each reported AP in the MLD and the Multiple BSSID set based on this information, so as to better select the appropriate AP from the reporting AP and the reported AP for association.

[0022] In a third aspect, an embodiment of the present application provides an AP multi-link device discovery device, the device comprising:

[0023] a sending unit, configured to send a first management frame to a station, wherein the first management frame carries information of a neighbor AP, and the reporting AP belongs to an AP multi-link device,

[0024] The neighbor AP information includes one or more of the first information, the second information, and the third information, wherein;

[0025] The first information is used to indicate whether the reported AP is in the same MLD as the reporting AP or whether the reported AP and members of the MLD to which the reporting AP belongs belong to the same multi-BSSID set;

[0026] The second information is used to indicate whether the reported AP and the members of the MLD to which the reporting AP belongs belong to the same multi-BSSID set;

[0027] The third information is used to indicate whether the reported AP and the reporting AP belong to the same MLD.

[0028] In the above method, by carrying the MLD information of the reported AP and the Multiple BSSID set information in the simplified neighbor report element of the first management frame, the station receiving the first management frame can obtain the basic situation of each reported AP in the MLD and the Multiple BSSID set based on this information, so as to better select the appropriate AP from the reporting AP and the reported AP for association.

[0029] In a fourth aspect, an embodiment of the present application provides an AP multi-link device discovery device, the device comprising:

[0030] a receiving unit, configured to receive a first management frame sent by a reporting AP, wherein the first management frame carries information of a neighboring AP, and the reporting AP belongs to an AP multi-link device;

[0031] The neighbor AP information includes one or more of the first information, the second information, and the third information, wherein;

[0032] The first information is used to indicate whether the reported AP is in the same MLD as the reporting AP or whether the reported AP and members of the MLD to which the reporting AP belongs belong to the same multi-BSSID set;

[0033] The second information is used to indicate whether the reported AP and the members of the MLD to which the reporting AP belongs belong to the same multi-BSSID set;

[0034] The third information is used to indicate whether the reported AP and the reporting AP belong to the same MLD.

[0035] In the above method, by carrying the MLD information of the reported AP and the Multiple BSSID set information in the simplified neighbor report element of the first management frame, the station receiving the first management frame can obtain the basic situation of each reported AP in the MLD and the Multiple BSSID set based on this information, so as to better select the appropriate AP from the reporting AP and the reported AP for association.

[0036] In a possible implementation of the first aspect, the second aspect, the third aspect, or the fourth aspect, the neighbor AP information further includes fourth information, wherein the fourth information is used to indicate whether the reported AP belongs to a multi-BSSID set.

[0037] In a possible implementation manner of the first aspect, the second aspect, the third aspect, or the fourth aspect, the neighbor AP information further includes eighth information, wherein the eighth information includes an MLD sequence number of an MLD to which the reported AP belongs.

[0038] In a possible implementation of the first aspect, the second aspect, the third aspect, or the fourth aspect, if the reported AP and the reporting AP are in the same MLD or belong to the same multi-BSSID set as the members of the MLD to which the reporting AP belongs, the information of the neighbor AP includes the eighth information.

[0039] In a possible implementation manner of the first aspect, the second aspect, the third aspect, or the fourth aspect, if the reported AP and the members of the MLD to which the reporting AP belong belong to the same multi-BSSID set, the neighbor AP information includes the eighth information.

[0040] In a possible implementation of the first aspect, the second aspect, the third aspect, or the fourth aspect, the information of the neighbor AP also includes ninth information, wherein the ninth information includes the multi-BSSID set sequence number of the multi-BSSID set to which the reported AP belongs.

[0041] In a possible implementation of the first aspect, the second aspect, the third aspect, or the fourth aspect,

[0042] If the reported AP belongs to a multi-BSSID set,

[0043] The reported AP and the reporting AP are in the same MLD.

[0044] Then the information of the neighbor AP includes the ninth information.

[0045] In a possible implementation of the first aspect, the second aspect, the third aspect, or the fourth aspect,

[0046] If the reported AP and the members of the MLD to which the reporting AP belongs belong to the same multi-BSSID set,

[0047] Then the information of the neighbor AP includes the ninth information.

[0048] In a possible implementation manner of the first aspect, the second aspect, the third aspect, or the fourth aspect, the neighbor AP information further includes fifth information, and the fifth information is used to indicate a link identifier of the reported AP.

[0049] In a possible implementation manner of the first aspect, the second aspect, the third aspect, or the fourth aspect, the information of the neighbor AP further includes one or more of the sixth information and the seventh information, wherein:

[0050] The sixth information is used to indicate the link identifier of the reporting AP and / or the MAC address of the MLD where the reporting AP is located;

[0051] In one implementation, the sixth information is located in an MLD element of the first management frame;

[0052] In an implementation manner, a reporting AP in the AP MLD sends the first management frame on the link on which it works, and the first management frame carries the MLD element.

[0053] In one implementation, the MLD element includes MLD common information and does not carry sub-element information corresponding to each AP. The MLD common information includes at least one of an MLD MAC address, a link identifier, and an MLD sequence number.

[0054] The MLD sequence number is used to indicate the sequence number of an AP MLD, and is the same as the MLD sequence number indicated by the eighth information in the Reduced Neighbor Report element (RNR element) in the first management frame. In other words, for the same AP MLD, the MLD sequence number carried in the RNR element carried in the first management frame is the same as the MLD sequence number carried in the MLD element carried in the first management frame.

[0055] The seventh information is used to indicate whether the first management frame carries information of all first reported APs, or to indicate whether the management frame carries information of all first reported APs and information of members in the multi-BSSID set where all first reported APs are located. The first reported APs are other AP members in the MLD to which the reporting AP belongs except the reporting AP.

[0056] In a possible implementation manner of the first aspect, the second aspect, the third aspect, or the fourth aspect, the information of the neighbor AP is carried in a simplified neighbor report element or a neighbor report element.

[0057] In a possible implementation manner of the first aspect, the second aspect, the third aspect, or the fourth aspect, the first management frame is a beacon frame or a probe response frame.

[0058] In a fifth aspect, an embodiment of the present application provides an AP multi-link device discovery method, the method comprising:

[0059] The reporting AP sends a second management frame to the station, where the second management frame carries information about a neighboring AP, where the reporting AP belongs to an AP multi-link device, where the information about the neighboring AP includes first information, and where the first information includes one or more of the following:

[0060] Whether the reported AP and the reporting AP belong to the same MLD;

[0061] Whether the reported AP belongs to an AP in an MLD;

[0062] The reported AP and the previously reported AP belong to the same MLD.

[0063] In the above method, by carrying the information of the MLD where the reported AP is located in the neighbor report element of the second management frame, the station receiving the second management frame can obtain the basic situation of each reported AP in the MLD based on this information, so as to better select from the neighbor APs as candidate APs when the station switches BSS.

[0064] In a sixth aspect, an embodiment of the present application provides an AP multi-link device discovery method, the method comprising:

[0065] The station receives a second management frame sent by the reporting AP, where the second management frame carries information about a neighboring AP, where the reporting AP belongs to an AP multi-link device, and where the information about the neighboring AP includes first information, where the first information includes one or more of the following:

[0066] Whether the reported AP and the reporting AP belong to the same MLD;

[0067] Whether the reported AP belongs to an AP in an MLD;

[0068] The reported AP and the previously reported AP belong to the same MLD.

[0069] In the above method, by carrying the information of the MLD where the reported AP is located in the neighbor report element of the second management frame, the station receiving the second management frame can obtain the basic situation of each reported AP in the MLD based on this information, so as to better select from the neighbor APs as candidate APs when the station switches BSS.

[0070] In a seventh aspect, an embodiment of the present application provides an AP multi-link device discovery device, the device comprising:

[0071] A sending unit, configured to send a second management frame to a station, where the second management frame carries information about a neighbor AP, where the reporting AP belongs to an AP multi-link device, and where the information about the neighbor AP includes first information, where the first information includes one or more of the following:

[0072] Whether the reported AP and the reporting AP belong to the same MLD;

[0073] Whether the reported AP belongs to an AP in an MLD;

[0074] The reported AP and the previously reported AP belong to the same MLD.

[0075] In the above method, by carrying the information of the MLD where the reported AP is located in the neighbor report element of the second management frame, the station receiving the second management frame can obtain the basic situation of each reported AP in the MLD based on this information, so as to better select from the neighbor APs as candidate APs when the station switches BSS.

[0076] In an eighth aspect, an embodiment of the present application provides an AP multi-link device discovery device, the device comprising:

[0077] A receiving unit, configured to receive a second management frame sent by a reporting AP, where the second management frame carries information about a neighboring AP, where the reporting AP belongs to an AP multi-link device, where the information about the neighboring AP includes first information, where the first information includes one or more of the following:

[0078] Whether the reported AP and the reporting AP belong to the same MLD;

[0079] Whether the reported AP belongs to an AP in an MLD;

[0080] The reported AP and the previously reported AP belong to the same MLD.

[0081] In the above method, by carrying the information of the MLD where the reported AP is located in the neighbor report element of the second management frame, the station receiving the second management frame can obtain the basic situation of each reported AP in the MLD based on this information, so as to better select from the neighbor APs as candidate APs when the station switches BSS.

[0082] In a possible implementation of the fifth, sixth, seventh, or eighth aspect, the information of the neighbor AP also includes second information, wherein the second information includes one or more of the MAC address of the AP multi-link device MLD where the reported AP is located, the number of APs included in the AP multi-link device MLD where the reported AP is located, the simultaneous sending and receiving STR capability indication between each AP in the AP multi-link device MLD where the reported AP is located, the link identifier corresponding to the reported AP, and information of other APs in the AP multi-link device MLD where the reported AP is located except the reported AP.

[0083] In a possible implementation manner of the fifth aspect, the sixth aspect, the seventh aspect, or the eighth aspect, if the reported AP belongs to an AP in an MLD, the information of the neighbor AP also includes the second information.

[0084] In a possible implementation manner of the fifth aspect, the sixth aspect, the seventh aspect, or the eighth aspect, the second information specifically includes a MAC address of an AP multi-link device MLD where the reported AP is located.

[0085] In a possible implementation manner of the fifth, sixth, seventh, or eighth aspect, information of each AP other than the reported AP in the AP multi-link device where the reported AP is located is carried in a neighbor report element.

[0086] In a possible implementation of the fifth aspect, the sixth aspect, the seventh aspect, or the eighth aspect, the information of the neighbor AP includes an operation set, a channel number, and a BSSID, and the information of the neighbor AP is carried in a neighbor report element.

[0087] In a possible implementation of the fifth aspect, the sixth aspect, the seventh aspect, or the eighth aspect, the information of the neighbor AP includes a link identifier, and the information of the neighbor AP is carried in a neighbor report element.

[0088] In a possible implementation of the fifth, sixth, seventh, or eighth aspect, the first information is specifically carried in a reserved field of the BSSID information field of a neighbor report element or in a simplified neighbor report element.

[0089] In a possible implementation of the fifth aspect, the sixth aspect, the seventh aspect, or the eighth aspect, the second information is specifically carried in an optional sub-element field of a neighbor report element.

[0090] In a possible implementation of the fifth aspect, the sixth aspect, the seventh aspect, or the eighth aspect, the second management frame is a beacon frame, a probe response frame, an association response frame, a reassociation response frame, or an authentication frame.

[0091] In a ninth aspect, an embodiment of the present application provides a fast BSS switching method, the method comprising:

[0092] Sending a fast switching request frame to the associated current access point AP, wherein the fast switching request frame is used to request switching to a target AP, and the target AP belongs to an AP in an AP multi-link device MLD;

[0093] A fast switching response frame sent by the current AP is received, where the fast switching response frame includes the first address information.

[0094] The fast switching request frame and the fast switching response frame include first address information, wherein the first address information includes the MAC address of the MLD where the station sending the fast switching request frame is located and the MAC address of the MLD where the target AP is located.

[0095] The above method can help all sites of the multi-link device to participate in fast switching.

[0096] In a tenth aspect, an embodiment of the present application provides a fast BSS switching method, the method comprising:

[0097] The current access point AP receives a fast switching request frame sent by a station, wherein the fast switching request frame is used to request switching to a target AP, and the target AP belongs to an AP in an AP multi-link device MLD;

[0098] The current AP sends a fast switching response frame to the station, where the fast switching response frame includes the first address information.

[0099] The fast switching request frame and the fast switching response frame include first address information, wherein the first address information includes the MAC address of the MLD where the station sending the fast switching request frame is located and the MAC address of the MLD where the target AP is located.

[0100] The above method can help all sites of the multi-link device to participate in fast switching.

[0101] In an eleventh aspect, an embodiment of the present application provides a fast BSS switching device, the device comprising:

[0102] A sending unit, configured to send a fast switching request frame to an associated current access point AP, wherein the fast switching request frame is used to request switching to a target AP, and the target AP belongs to an AP in an AP multi-link device MLD;

[0103] A receiving unit is used to receive a fast switching response frame sent by the current AP, where the fast switching response frame includes the first address information.

[0104] The fast switching request frame and the fast switching response frame include first address information, wherein the first address information includes the MAC address of the MLD where the station sending the fast switching request frame is located and the MAC address of the MLD where the target AP is located.

[0105] The above method can help all sites of the multi-link device to participate in fast switching.

[0106] In a twelfth aspect, an embodiment of the present application provides a fast BSS switching device, the device comprising:

[0107] A receiving unit, configured to receive a fast switching request frame sent by a station, wherein the fast switching request frame is used to request switching to a target AP, and the target AP belongs to an AP in an AP multi-link device MLD;

[0108] A sending unit is used to send a fast switching response frame to the site, where the fast switching response frame includes the first address information.

[0109] The fast switching request frame and the fast switching response frame include first address information, wherein the first address information includes the MAC address of the MLD where the station sending the fast switching request frame is located and the MAC address of the MLD where the target AP is located.

[0110] The above method can help all sites of the multi-link device to participate in fast switching.

[0111] In a possible implementation of the ninth aspect, the tenth aspect, the eleventh aspect, or the twelfth aspect, the MAC address of the MLD where the site sending the fast switching request frame and the fast switching response frame is located in the first address information is carried in the site address field; the MAC address of the MLD where the target AP is located in the first address information is carried in the target AP address field.

[0112] In the thirteenth aspect of the embodiments of the present application, a computer-readable storage medium is provided, in which a computer program code is stored. When the computer program runs on a processor, the processor executes the method in any one of the above-mentioned first aspect, second aspect, fifth aspect, sixth aspect, ninth aspect, and tenth aspect and the corresponding possible implementation methods.

[0113] In the fourteenth aspect of the embodiments of the present application, a computer program product is provided, which stores a computer program (instructions) executed by the above-mentioned processor. When the computer program runs on the processor, the processor executes the methods in any one of the above-mentioned first aspect, second aspect, fifth aspect, sixth aspect, ninth aspect, and tenth aspect and the corresponding possible implementation methods.

[0114] In the fifteenth aspect of the embodiments of the present application, a communication device is provided, which includes a processor and may also include a transceiver and a memory, wherein the transceiver is used to send and receive information, or to communicate with other network elements; the memory is used to store computer programs (instructions); the processor is used to execute the computer program to support the communication device to implement any one of the above-mentioned first aspect, second aspect, fifth aspect, sixth aspect, ninth aspect, and tenth aspect and the corresponding possible implementation methods.

[0115] In the sixteenth aspect of the embodiments of the present application, a communication device is provided, which may exist in the form of a chip product. The structure of the device includes a processor and may also include a memory, which is used to couple with the processor and store the necessary programs (instructions) and data of the device. The processor is used to execute the computer program stored in the memory to support the communication device to execute the methods in any of the above-mentioned first aspect, second aspect, fifth aspect, sixth aspect, ninth aspect, and tenth aspect and the corresponding possible implementation methods. Optionally, the memory may be located in the processor as internal storage, and the processor may also be located outside the processor and coupled to the processor as external storage.

[0116] In the seventeenth aspect of the embodiments of the present application, a communication device is provided. The device can exist in the form of a chip product. The structure of the device includes a processor and an interface circuit. The processor is used to communicate with other devices through a receiving circuit, so that the device executes any one of the above-mentioned first aspect, second aspect, fifth aspect, sixth aspect, ninth aspect, and tenth aspect and the corresponding possible implementation methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0117] The following is an introduction to the drawings used in the embodiments of the present application.

[0118] Figure 1 A schematic diagram of the structure of a communication system provided in an embodiment of the present application;

[0119] FIG2( a ) is a schematic diagram of the structure of a multi-link device provided in an embodiment of the present application;

[0120] FIG2( b ) is a schematic diagram of the structure of another multi-link device provided in an embodiment of the present application;

[0121] FIG2( c ) is a schematic diagram of the structure of another multi-link device provided in an embodiment of the present application;

[0122] FIG3( a) is a schematic diagram of a multi-link communication provided in an embodiment of the present application;

[0123] FIG3( b) is a schematic diagram of another multi-link communication provided in an embodiment of the present application;

[0124] FIG3( c ) is a schematic diagram of a format of a neighbor report element provided in an embodiment of the present application;

[0125] FIG3( d ) is a schematic diagram of a simplified format of a neighbor report element provided in an embodiment of the present application;

[0126] FIG3( e) is a schematic diagram of the format of a TBTT information field provided in an embodiment of the present application;

[0127] Figure 4 An interactive schematic diagram of an AP multi-link device discovery method provided in an embodiment of the present application;

[0128] Figure 5 A schematic diagram of a Multiple BSSID collection framework based on MLD provided in an embodiment of the present application;

[0129] Figure 6 A schematic diagram of another MLD-based Multiple BSSID collection framework provided in an embodiment of the present application;

[0130] Figure 7A schematic diagram of another MLD-based Multiple BSSID collection framework provided in an embodiment of the present application;

[0131] FIG8( a) is a schematic diagram of the format of another TBTT information field provided in an embodiment of the present application;

[0132] FIG8( b) is a schematic diagram of the format of another TBTT information field provided in an embodiment of the present application;

[0133] FIG8( c ) is a schematic diagram of the format of another TBTT information field provided in an embodiment of the present application;

[0134] Fig. 9 An interactive schematic diagram of another AP multi-link device discovery method provided in an embodiment of the present application;

[0135] Fig.10 A schematic diagram of the format of another neighbor report element provided in an embodiment of the present application;

[0136] Fig.11 It is an interactive schematic diagram of a fast BSS switching method based on a DS system provided in an embodiment of the present application;

[0137] Fig.12 This is an interactive schematic diagram of a fast BSS switching method based on a wireless air interface provided in an embodiment of the present application;

[0138] Fig.13 A schematic diagram of the field format of an FT request action frame is provided for an embodiment of the present application;

[0139] Fig.14 A schematic diagram of another FT request action frame field format is provided for an embodiment of the present application;

[0140] Fig.15 A schematic diagram of the composition of a communication device provided in an embodiment of the present application;

[0141] Fig.16 A schematic diagram of another communication device provided in an embodiment of the present application;

[0142] Fig.17 A schematic diagram of the structure of an MLD element provided in an embodiment of the present application;

[0143] Fig.18 A schematic diagram of the structure of another MLD element provided in an embodiment of the present application. DETAILED DESCRIPTION

[0144] The following first introduces the relevant technologies involved in the present application, and then describes the embodiments of the present application in conjunction with the drawings.

[0145] An embodiment of the present application provides a communication method applied to a wireless communication system. The wireless communication system may be a wireless local area network (WLAN) or a cellular network. The method may be implemented by a communication device in the wireless communication system or a chip or processor in the communication device. The communication device may be a wireless communication device that supports parallel transmission of multiple links, for example, a multi-link device or a multi-band device. For example, in a wireless local area network, the communication device supports communication using the IEEE 802.11 series of protocols, including: 802.11be, 802.11ax, or 802.11a / b / g / n / ac.

[0146] 1. Multi-link device (MLD), also known as multi-band device (multi-band device).

[0147] The multi-link device MLD includes one or more subordinate sites, and the subordinate sites are logical sites. In the embodiments of the present application, "the multi-link device includes subordinate sites" is also briefly described as "the multi-link device includes sites". The subordinate sites can be access points (Access Point, AP) or non-access point stations (non-APSTA). For the convenience of description, the present application refers to a multi-link device whose subordinate site is AP as a multi-link AP or AP multi-link device or AP multi-link device (AP multi-link device), and a multi-link device whose subordinate site is a non-AP STA as a multi-link STA or a multi-link STA device or a STA multi-link device (STA multi-link device).

[0148] The multi-link device MLD can implement wireless communication following the 802.11 series protocols, for example, following Extremely High Throughput (EHT), or following 802.11be-based or compatible support for 802.11be, thereby implementing communication with other devices. Of course, the other devices may be multi-link devices or may not be multi-link devices.

[0149] Each logical site can work on a link, but multiple logical sites are allowed to work on the same link. The link identifier mentioned below represents a site working on a link, that is, if there is more than one logical site on a link, more than one link identifier is required to represent them. The link identifier mentioned below sometimes also represents the site working on the link. When a multi-link device transmits data with another multi-link device, before communication, the multi-link device and the other multi-link device can first negotiate or communicate the correspondence between the link identifier and a link or a site on a link, or the AP multi-link device broadcasts a management frame, such as a beacon frame, to indicate the correspondence between the link identifier and a link or a site on a link. Therefore, in data transmission, there is no need to transmit a large amount of signaling information to indicate the link or the site on the link, and only the link identifier can be carried, which reduces the signaling overhead and improves the transmission efficiency.

[0150] The following is an example of one of the multi-link devices being an AP multi-link device and the other multi-link device being a STA multi-link device. In one example, when the AP multi-link device establishes a BSS, the management frame sent, such as a beacon frame, will carry an element including multiple link identification information fields, and each link identification information field can suggest a corresponding relationship between a link identification and a station working on a link. Each link identification information field includes a link identification, and also includes: one or more of a MAC address, an operation set, and a channel number, wherein one or more of the MAC address, the operation set, and the channel number can indicate a link; in another example, during the multi-link association process, the AP multi-link device and the STA multi-link device negotiate multiple link identification information fields. In subsequent communications, the AP multi-link device or the STA multi-link device will use the link identification to characterize a station in the multi-link device, and the link identification can also characterize the MAC address of the station, the working operation set, and one or more attributes of the channel number. The MAC address can also be replaced with the association identification of the AP multi-link device after association. Optionally, if multiple sites work on one link, the link identifier (a digital ID) represents not only the operation set and channel number of the link, but also the site identifier working on the link, such as the site's MAC address or AID.

[0151] Figure 1Taking a wireless local area network as an example, an application scenario diagram of an embodiment of the present application is introduced. The application scenario includes: a first site 101 and a second site 102, and the first site 101 can communicate with the second site 102 using multiple links, so as to achieve the effect of improving throughput. The first site can be a multi-link device, and the second site can be a single-link device or a multi-link device, etc. In one scenario, the first site 101 is an AP multi-link device, and the second site 102 is a STA multi-link device or site (such as a single-link site); in another scenario, the first site 101 is a STA multi-link device, and the second site 102 is an AP (such as a single-link AP) or an AP multi-link device. In another scenario, the first site 101 is an AP multi-link device, and the second site 102 is an AP multi-link device or AP; in another scenario, the first site 101 is a STA multi-link device, and the second site 102 is a STA multi-link device or STA. Of course, the wireless local area network may also include other devices. Figure 1 The number and types of devices shown are exemplary only.

[0152] Figure 2(a) and Figure 2(b) show the schematic diagrams of the structures of AP multi-link devices and STA multi-link devices participating in the communication. The 802.11 standard focuses on the 802.11 physical layer (PHY) and media access control (MAC) layer in AP multi-link devices and STA multi-link devices (such as mobile phones and laptops).

[0153] As shown in Figure 2(a), the multiple APs included in the AP multi-link device are independent of each other at the low MAC layer and the PHY layer, and are also independent of each other at the high MAC layer; the multiple STAs included in the STA multi-link device are independent of each other at the low MAC layer and the PHY layer, and are also independent of each other at the high MAC layer.

[0154] As shown in Figure 2(b), the multiple APs included in the AP multi-link device are independent of each other in the low MAC layer and the PHY layer, and share the high MAC layer. The multiple STAs included in the STA multi-link device are independent of each other in the low MAC layer and the PHY layer, and share the high MAC layer.

[0155] Of course, the STA multi-link device may adopt a structure in which the high MAC layer is independent of each other, while the AP multi-link device may adopt a structure in which the high MAC layer is shared; or the STA multi-link device may adopt a structure in which the high MAC layer is shared, while the AP multi-link device may adopt a structure in which the high MAC layer is independent of each other. Exemplarily, the high MAC layer or the low MAC layer may be implemented by a processor in a chip system of the multi-link device, or may be implemented by different processing modules in a chip system.

[0156] Exemplarily, the multi-link device in the embodiment of the present application can be a single-antenna device or a multi-antenna device. For example, it can be a device with more than two antennas. The embodiment of the present application does not limit the number of antennas included in the multi-link device. FIG2(c) illustrates an example in which an AP multi-link device has multiple antennas and a STA multi-link device has a single antenna. In the embodiment of the present application, the multi-link device can allow services of the same access type to be transmitted on different links, and even allow the same data packets to be transmitted on different links; it can also not allow services of the same access type to be transmitted on different links, but allow services of different access types to be transmitted on different links.

[0157] The frequency bands in which the multi-link device operates may include but are not limited to: sub 1GHz, 2.4GHz, 5GHz, 6GHz and high frequency 60GHz. Figures 3(a) and 3(b) show two schematic diagrams of a multi-link device communicating with other devices via multiple links in a wireless local area network.

[0158] FIG3( a ) shows a scenario in which an AP multi-link device 101 and a STA multi-link device 102 communicate. The AP multi-link device 101 includes subordinate AP101-1 and AP101-2, the STA multi-link device 102 includes subordinate STA102-1 and STA102-2, and the AP multi-link device 101 and the STA multi-link device 102 communicate using link 1 and link 2 in parallel.

[0159] FIG3( b ) shows a scenario in which an AP multi-link device 101 communicates with a STA multi-link device 102, a STA multi-link device 103, and a STA 104. The AP multi-link device 101 includes subordinate APs 101-1 to 101-3, the STA multi-link device 102 includes two subordinate STAs 102-1 and 102-2, the STA multi-link device 103 includes two subordinate STAs 103-1, STA 103-2, and STA 103-3, and STA 104 is a single-link device. The AP multi-link device can communicate with the STA multi-link device 102 using links 1 and 3, communicate with the multi-link device 103 using links 2 and 3, and communicate with the STA 104 using link 1. In one example, STA104 operates in the 2.4 GHz frequency band; STA multi-link device 103 includes STA103-1 and STA103-2, STA103-1 operates in the 5 GHz frequency band, and STA103-2 operates in the 6 GHz frequency band; STA multi-link device 102 includes STA102-1 and STA102-2, STA102-1 operates in the 2.4 GHz frequency band, and STA102-2 operates in the 6 GHz frequency band. AP101-1 in the AP multi-link device operating in the 2.4 GHz frequency band can transmit uplink or downlink data with STA104 and STA102-2 in the STA multi-link device 102 through link 1. AP101-2 in the AP multi-link device operating in the 5 GHz frequency band can transmit uplink or downlink data with STA103-1 in the STA multi-link device 103 operating in the 5 GHz frequency band through link 2. AP101-3 in the AP multi-link device 101 operating in the 6 GHz frequency band can transmit uplink or downlink data with STA102-2 in the STA multi-link device 102 operating in the 6 GHz frequency band through link 3, and can also transmit uplink or downlink data with STA103-2 in the STA multi-link device through link 3.

[0160] It should be noted that FIG3(a) only shows that the AP multi-link device supports two frequency bands, and FIG3(b) only shows that the AP multi-link device supports three frequency bands (2.4GHz, 5GHz, 6GHz), each frequency band corresponds to a link, and the AP multi-link device 101 can work on one or more links in link 1, link 2 or link 3. On the AP side or the STA side, the link here can also be understood as a station working on the link. In actual applications, the AP multi-link device and the STA multi-link device can also support more or fewer frequency bands, that is, the AP multi-link device and the STA multi-link device can work on more links or fewer links, which is not limited in the embodiments of the present application.

[0161] Exemplarily, the multi-link device is a device with a wireless communication function, which can be a complete device, or a chip or processing system installed in the complete device, etc. The device installed with these chips or processing systems can implement the method and function of the embodiment of the present application under the control of these chips or processing systems. For example, the multi-link STA in the embodiment of the present application has a wireless transceiver function, can support the 802.11 series of protocols, and can communicate with the multi-link AP or other multi-link STA or single-link device. For example, the multi-link STA is any user communication device that allows the user to communicate with the AP and then communicate with the WLAN. For example, the multi-link STA can be a tablet computer, desktop, laptop, notebook computer, ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), handheld computer, netbook, personal digital assistant (Personal Digital Assistant, PDA), mobile phone and other user devices that can be connected to the Internet, or an Internet of Things node in the Internet of Things, or a vehicle-mounted communication device in the Internet of Vehicles, etc. The multi-link STA can also be the chip and processing system in the above-mentioned terminals. The multi-link AP in the embodiment of the present application is a device that provides services for the multi-link STA, and can support the 802.11 series of protocols. For example, the multi-link AP can be a communication entity such as a communication server, a router, a switch, a bridge, or the multi-link AP can include various forms of macro base stations, micro base stations, relay stations, etc. Of course, the multi-link AP can also be a chip and processing system in these various forms of devices, so as to realize the method and function of the embodiment of the present application. In addition, the multi-link device can support high-speed and low-latency transmission. With the continuous evolution of wireless local area network application scenarios, the multi-link device can also be applied to more scenarios, such as sensor nodes in smart cities (such as smart water meters, smart meters, smart air detection nodes), smart devices in smart homes (such as smart cameras, projectors, display screens, TVs, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment terminals (such as wearable devices such as AR and VR), smart devices in smart offices (such as printers, projectors, etc.), Internet of Vehicles devices in Internet of Vehicles, and some infrastructure in daily life scenes (such as vending machines, self-service navigation desks in supermarkets, self-service cash registers, self-service ordering machines, etc.). In the embodiment of the present application, there is no special restriction on the specific form of multi-link STA and multi-link AP, which is only an exemplary description. Among them, the 802.11 series protocols may include: 802.11be, 802.11ax, 802.11a / b / g / n / ac, etc.

[0162] 2. Multiple Basic Service Set Identifier (BSSID) mode.

[0163] The Multiple BSSID set is a combination of some cooperating APs, and all the cooperating APs use the same operation set, channel number, and antenna interface. In the Multiple BSSID set, there is only one TransmittedBSSID AP, and the other APs are Nontransmitted BSSID APs. The information of the Multiple BSSID set (that is, the Multiple BSSID element) is carried in the beacon frame or probe response frame or neighbor report sent by the Transmitted BSSID AP. The BSSID information of the Nontransmitted BSSID AP is derived by receiving the above-mentioned beacon frame or probe response frame, or the Multiple BSSID element in the neighbor report.

[0164] In Multiple BSSID technology, a physical AP can virtualize multiple logical APs. Each virtualized AP manages a BSS. Different virtualized APs generally have different SSIDs and permissions, such as security mechanisms or transmission opportunities. Among the multiple virtualized APs, there is a virtual AP whose BSSID is configured as a transmitted BSSID. This virtual AP can be called a transmitted AP. The BSSIDs of other virtual APs are configured as non-transmitted BSSIDs. This virtual AP can be called a non-transmitted AP. Generally speaking, multiple APs in Multiple BSSID can also be understood as one AP device virtualizing multiple cooperative AP devices. Only APs with a Transmitted BSSID can send beacon frames and probe response frames. If the probe request frame sent by the STA is to an AP with a Nontransmitted BSSID in the Multiple BSSID set, the AP with a Transmitted BSSID needs to help respond to the probe response frame. The beacon frame sent by the AP with the Transmitted BSSID includes the Multiple BSSID element, and other APs with the Nontransmitted BSSID cannot send beacon frames. The association identifiers (AIDassociation identifiers) assigned by multiple virtual APs to the sites they manage share the same space, which means that the AIDs assigned to the sites in multiple virtual BSSs cannot overlap.

[0165] Optionally, the MultipleBSSID element is as shown in Table 1, including element ID, length, maximum BSSID indication, and sub-elements, wherein the maximum BSSID indicates that the maximum number of BSSIDs included in the above-mentioned Multiple BSSID set is n, and the optional sub-elements include information of each non-transmission BSSID. The receiving end can calculate the value of each BSSID in the multiple BSSID set based on the reference BSSID, the maximum BSSID indication and the sequence number of the BSSID. Each BSSID includes 48 bits, wherein the value of the high (48-n) bits of each BSSID in the multiple BSSID set is the same as the value of the high 48-n bits of the reference BSSID, and the value of the low n bits of each BSSID in the multiple BSSID set is the sum of the low n values ​​of the reference BSSID and the sequence number x of the BSSID, and then modulo 2n. The reference BSSID (that is, the Transmitted BSSID) is carried in the BSSID field in the MAC header of the frame (such as the beacon frame) containing the MultipleBSSID element. For the specific calculation method, please refer to the 802.11-2016 standard protocol.

[0166] Table 1 MultipleBSSID elements

[0167] Element ID length Maximum BSSID indication Optional child elements byte 1 1 6 variable

[0168] Among them, the “optional sub-elements” in Table 1 can be as shown in Table 2.

[0169] Table 2 Optional sub-elements

[0170] Sub-element ID name expand 0 Nontransmitted BSSID profile Not scalable 1-220 reserve 221 Manufacturer Proprietary Manufacturer Definition 222-255 reserve

[0171] In Table 2, the Nontransmitted BSSID profile (configuration) includes one or more elements of an AP or DMG STA with a Nontransmitted BSSID. The Nontransmitted BSSID profile (configuration) includes but is not limited to the following elements:

[0172] 1. For each Nontransmitted BSSID, the Nontransmitted BSSID capability element needs to be included, as well as multiple other elements in the beacon.

[0173] 2. SSID element and Multiple BSSID-Index element: The Multiple BSSID-Index element includes a BSSID sequence number field.

[0174] 3. If the MultipleBSSID element is carried in the beacon, the FMSDescriptor (description) element is also included.

[0175] 4. The following elements are not included: The Timestamp and BeaconInterval fields, DSSS Parameter Set, IBSS Parameter Set, Country, Channel Switch Announcement, Extended Channel Switch Announcement, Wide Bandwidth Channel Switch, Transmit Power Envelope, Supported Operating Classes, IBSSDFS, ERP Information, HT Capabilities, HT Operation, VHT Capabilities, VHT Operation, SIG Beacon Compatibility, Short Beacon Interval, S1G Capabilities, and S1G Operation (11ah). These elements are usually the same as the values ​​of the transmitted BSSID AP elements.

[0176] 5. The NonInheriatance element is optional and is the last element in the Nontransmitted BSSIDprofile. The non-inheritance element includes a series of element ID numbers that the Nontransmitted BSSID cannot inherit from the transmitted BSSID and the element ID extension number. It is worth noting that the specific content of the element is omitted here, as shown in Table 3, including element ID, length, element ID extension, element ID list, element ID extension list, where the element ID extension number only appears when the element ID value is 255.

[0177] Table 3 Non-inherited elements

[0178] 1 byte 1 byte 1 byte 1 or more bytes 1 or more bytes Element ID length Element ID Extension Element ID list Element ID extended list

[0179] 3. AP Discovery and Association

[0180] If a station wants to associate with an AP and establish a connection, it must first discover the existence of the AP through scanning. There are two forms of scanning: active scanning and passive scanning.

[0181] Passive scanning is a kind of management frame sent by the AP on the receiving channel, such as beacon frame, association response frame, reassociation response frame, authentication frame, probe response frame, etc. For example, the station jumps on different channels to search for beacon frames sent by the AP. Once the station obtains the control information of the AP through the Beacon frame, it can further obtain other additional information from the AP by exchanging Probe Request frames and Probe Response frames.

[0182] Active scanning means that a station can actively send a broadcast Probe Request frame without hearing a Beacon frame. The AP that receives the Probe Request frame can initiate random channel access to reply to the Probe Response frame if certain conditions are met.

[0183] During the scanning process, in order to assist the station to perform a quick scan, the AP will carry a reduced neighbor report element in management frames, such as beacon frames and probe response frames, to avoid the station from constantly scanning channels and reduce the scanning time of the station. In addition, when the station finds that the received signal strength indication (RSSI) of the currently associated AP drops to a certain level or that the basic service set (BSS) needs to be switched for other reasons, the AP can carry a neighbor report element in a BSS switching management query frame (BSS Transition management Query), or a BSS switching management request frame (BSS Transition management Request), or a BSS switching management response frame (BSS Transition management Response) to tell the station which BSSs are around and related information of the BSSs, so as to assist the station in performing BSS switching. The neighbor report element and the reduced neighbor report element are introduced below.

[0184] Neighbor Report element: AP carries the neighbor report element in management frames, such as beacon frames, association response frames, reassociation response frames, authentication frames, and probe response frames. When a station scans, it receives management frames sent by APs, obtains information about surrounding APs based on the neighbor report elements, and then selects a suitable AP for association.

[0185] Specifically, the Neighbor Report element describes the information of a neighbor AP and the BSS to which it belongs. An AP can indicate the relevant information of multiple neighbor APs by carrying multiple Neighbor Report elements. FIG3(c) illustrates an indication format. As can be seen from FIG3(c), the Neighbor Report element may include the following fields.

[0186] BSSID field: indicates the BSSID corresponding to the reported neighbor AP.

[0187] BSSID info field: indicates the related information of the neighbor BSSID.

[0188] Operating Class field and channel Number field: used to indicate which channel the neighbor BSSID is on.

[0189] PHY Type field: indicates the physical layer type of the AP corresponding to the neighbor BSSID.

[0190] Optional subelements field: carries some optional subelements.

[0191] For the BSSID info field, it carries the following information:

[0192] AP Reachability field: indicates whether the neighbor AP is reachable.

[0193] Security field: Indicates whether the neighboring AP supports the same security configuration as the existing connection.

[0194] Key Scope field: Indicates whether the neighbor AP and the reporting AP are the same authenticator.

[0195] Capabilities field: indicates some optional capability information of the neighbor AP.

[0196] Mobility domain field: indicates whether the neighbor AP and the reporting AP are in the same mobility domain.

[0197] High Throughput field: Indicates that the HT capabilities element of the neighbor AP (carried in the optional subelement field) is the same as the HT capabilities element of the reporting AP.

[0198] Very High Throughput field: indicates that the VHT capabilities element of the neighbor AP is the same as the VHT capabilities element of the reporting AP.

[0199] FTM (fine time measurement) field: indicates whether the neighbor AP supports fine timing measurement.

[0200] High Efficiency field: indicates that the HE capabilities element of the neighbor AP is the same as the HE capabilities element of the reporting AP.

[0201] ER (Extended range) BSS (Extended distance BSS) field: indicates that the Beacon sent by the neighbor AP is sent in HEER SU PPDU mode.

[0202] Collocated AP field: indicates whether the neighbor AP and the reporting AP are co-located APs.

[0203] Unsolicited Probe Response Active field: indicates whether the neighbor AP has enabled active probe response.

[0204] Member of ESS with 2.4 / 5GHz co-located AP (ESS (extended service set)) field: Indicates whether the neighbor AP is co-located with a 2.4 / 5GHz AP and is a member of an extended service set.

[0205] OCT supported with reporting AP field: indicates whether the neighbor AP supports exchanging management frame type MPDUs through the On-channel tunneling (OCT) mechanism.

[0206] Co-located with 6GHz AP field: indicates whether the neighbor AP is co-located with a 6GHZ AP.

[0207] For the Capabilities field, it may also have the following information fields:

[0208] Spectrum management field: indicates whether the neighbor AP supports spectrum management function.

[0209] QoS field: indicates whether the neighbor AP supports the QoS mechanism.

[0210] APSD field: indicates whether the neighbor AP supports the automatic energy-saving transmission mechanism.

[0211] Radio Measurement field: indicates whether the neighbor AP supports the radio measurement function.

[0212] Reduced Neighbor Report Element: AP carries a reduced neighbor report element in management frames, such as beacon frames and probe response frames. When scanning a site, it receives management frames sent by APs, obtains information about surrounding APs based on the reduced neighbor report element, and then selects a suitable AP for association.

[0213] Specifically, a reduced neighbor report element generally carries one or more Neighbor AP info fields, which are used to describe information about one or more neighbor APs and the BSSs to which they belong. FIG3(d) illustrates an indication format. As can be seen from FIG3(d), a reduced neighbor report element may include the following fields.

[0214] The TBTT info Header field carries the following information:

[0215] TBTT info Field Type field: indicates the type of TBTT info. Together with the TBTT info length field, it indicates the format of the TBTT info field.

[0216] Filtered neighbor AP field: indicates whether the SSIDs of all BSSs carried in the Neighbor AP info field match the SSID in the Probe Request frame.

[0217] Reserved field (1 bit).

[0218] TBTT info count field: indicates the number of TBTT info fields contained in the TBTT info set.

[0219] TBTT info Length field: indicates the length of each TBTT info field. The specific information format carried under different lengths is shown in Table 4:

[0220] Table 4

[0221]

[0222] The following is the specific format of the TBTT info field when the TBTT information length is 12 bytes:

[0223] Neighbor AP TBTT offset (Neighbor AP Target Beacon Transmission Time Offset) field: indicates the offset between the Beacon transmission time of the neighbor AP and the reporting AP.

[0224] BSSID (BSS Identifier) ​​field: indicates the BSS identifier corresponding to the neighbor AP.

[0225] Short SSID (Short Service Set Identifier) ​​field: indicates the service set identifier to which the neighboring AP belongs.

[0226] BSS Parameter field: indicates the parameters of the neighbor AP, as shown in Figure 3(e), which contains the following information:

[0227] OCT recommended (recommended to use the channel tunnel mechanism) field: indicates that the neighbor AP expects to exchange management type MPDUs with it through the OCT mechanism.

[0228] Same SSID (Same Service Set Identifier) ​​field: indicates whether the neighbor AP and the reporting AP have the same SSID.

[0229] Multiple BSSID (Multiple Basic Service Set Identifier) ​​field: Indicates whether the neighbor AP is part of a multiple BSSID set.

[0230] Transmitted BSSID (Transmitted Basic Service Set Identifier) ​​field: If the neighbor AP is part of a multiple BSSID set, it further indicates whether the neighbor AP is a Transmitted BSSID or a non-transmitted BSSID.

[0231] Member Of ESS With 2.4 / 5GHz Co-Located AP (co-located with a 2.4 / 5GHz AP and a member of an extended service set) field: indicates whether the neighbor AP is co-located with a 2.4 / 5GHz AP (that is, whether it is a 6GHz only AP) and is a member of an extended service set.

[0232] Unsolicited Probe Response Active field: indicates whether the neighbor AP has enabled the unsolicited probe response.

[0233] Co-located AP field: indicates whether the neighbor AP is co-located with the reporting AP.

[0234] It should be noted that, in the embodiment of the present application, the AP described in the neighbor report element (Neighbor Report element) or the reduced neighbor report element (Reduced Neighbor Report element) is the reported AP (reported access point (AP): An AP that is described in an element such as a Neighbor Report element or a Reduced Neighbor Report element.), and the neighbor AP mentioned subsequently can be understood as the reported AP; the AP that sends the neighbor report element or the reduced neighbor report element is the reporting AP (reporting access point (AP): An AP that is transmitting an element, such as a Neighbor Report element or a Reduced Neighbor Report element, describing areported AP).

[0235] How to enable a station to discover an AP multi-link device (the AP in the AP multi-link device may optionally belong to a Multiple BSSID set) is a technical problem being studied by those skilled in the art.

[0236] See also Figure 4 , Figure 4 This is an AP multi-link device discovery method provided by an embodiment of the present application. The method can be applied between sites, between access points and sites, and between access points and access points. For the convenience of description, the following description is based on the communication between access points and sites. The method includes but is not limited to the following steps:

[0237] Step S401: the access point AP sends a first management frame to a station.

[0238] The first management frame carries information used by the site to discover the AP multi-link device, so that the site that receives the information can establish an association with the corresponding AP. For example, the first management frame can be a beacon frame, a probe response frame, etc. The first management frame can be sent by an AP multi-link device, or a reporting AP in an AP multi-link device. The site that receives the first management frame can be either a site in a site multi-link device or a single-link site. In other types of BSSs (such as mesh BSSs and independent BSSs), the site that sends the first management frame can also be a site that belongs to a multi-link device MLD; the site that receives the first management frame can also be an access point that belongs to an MLD or a single-link access point. The subsequent descriptions are all illustrated by the example of the reporting AP in the AP multi-link device sending the first management frame to the site.

[0239] In an embodiment of the present application, in one example, an AP multi-link device may include one logical AP, which switches to work on multiple links. In another example, an AP multi-link device includes n logical APs, which work on n different links, respectively. Therefore, link identifiers link1, link2, ..., linkn can be used to represent them, and the MAC address of each AP is different. An AP multi-link device is identified by a MAC address of an MLD, or it can be said that the MAC address is used to identify the management entity of the AP multi-link device, wherein the MAC address of the AP multi-link device may be the same as one of the MAC addresses of the n logical APs included in the multi-link AP, or may be different from the MAC addresses of the n logical APs. For example, the MAC address of the AP multi-link device is a public MAC address, which can identify the AP multi-link device.

[0240] In one example, a logical AP or multiple logical APs in an AP multi-link device may belong to one or more multiple Basic Service Set Identifier (BSSID) sets. In one example, the multiple BSSID sets to which each logical AP in an AP multi-link device belongs are different. In another example, multiple logical APs in an AP multi-link device may belong to the same Multiple BSSID set. For example, if there are two logical APs in the AP multi-link device working on one link, in this case, the two logical APs may belong to the same multiple BSSID set.

[0241] For example, if Figure 5 As shown, the MAC address of a multi-link device is MLD1, for example. The multi-link device includes three logical APs, represented as AP1, AP2 and AP3, wherein AP1, AP2 and AP3 work on link 1 (link1), link 2 (link2) and link 3 (link3), respectively. The MAC addresses of AP1, AP2 and AP3 are BSSID_11, BSSID_21 and BSSID_31, respectively (before 802.11ax, the BSSID of the BSS established by the AP is the MAC address of the AP, which may be changed later). AP1 is a member of Multiple BSSID set 1, and Multiple BSSID set 1 also includes AP4 with a MAC address of BSSID_13; AP2 is a member of Multiple BSSID set 2, and Multiple BSSID set 2 also includes AP5 with a MAC address of BSSID_22 and AP6 with a MAC address of BSSID_23; AP3 is a member of Multiple BSSID set 1. Members of BSSID set 3, MultipleBSSID set 3 also include AP7 with a MAC address of BSSID_32 and AP8 with a MAC address of BSSID_33.

[0242] Figure 6The diagram illustrates the architecture of a multi-link device in which the APs in the BSS identified by the Transmitted BSSID in multiple Multiple BSSID sets are not in the same AP. For ease of description, the AP in the BSS identified by the Transmitted BSSID may be referred to as a transmitted AP (TransmittedBSSID AP), and the AP in the BSS identified by the nontransmitted BSSID may be referred to as a nontransmitted AP (nontransmittedBSSID AP). Among them, the AP whose MAC address ends with x is the Transmitted BSSID AP, and the AP whose MAC address ends with y or z is the Non-Transmitted BSSID AP. For example, the Transmitted BSSID AP in Multiple BSSID set 1 is AP1 with a MAC address of BSSID_1x, and the non-Transmitted BSSID AP in Multiple BSSID set 1 is AP4 with a MAC address of BSSID_1y; the Transmitted BSSID AP in Multiple BSSID set 2 is AP5 with a MAC address of BSSID_2x, and the non-Transmitted BSSID APs in Multiple BSSID set 2 include AP2 with an address of BSSID_2y and AP6 with a MAC address of BSSID_2z; the Transmitted BSSID AP in Multiple BSSID set 3 is AP3 with a MAC address of BSSID_3x, and the non-Transmitted BSSID AP in Multiple BSSID set 3 is AP4 with a MAC address of BSSID_1y. BSSIDAP includes AP7 with MAC address BSSID_3y and AP8 with MAC address BSSID_3z. Figure 6 It can be seen that the Transmitted BSSID APs (i.e., transmitting APs) from different Multiple BSSID sets are distributed in different AP multi-link devices. For example, the AP with a MAC address of BSSID-1x and the AP with a MAC address of BSSID-2x are respectively in the AP multi-link device MLD1 and the AP multi-link device MLD2.

[0243] Figure 7It illustrates that the APs in the BSS identified by the Transmitted BSSID in multiple Multiple BSSID sets come from the same AP multi-link device. For the convenience of description, the AP in the BSS identified by the Transmitted BSSID can be called a transmitted AP (TransmittedBSSID AP), and the AP in the BSS identified by the nontransmitted BSSID can be called a non-transmitted AP (nontransmittedBSSID AP). Among them, the AP whose MAC address ends with x is the Transmitted BSSID AP, and the AP whose MAC address ends with y or z is the Non-Transmitted BSSID AP. For example, the Transmitted BSSID AP in Multiple BSSID set 1 is AP1 with a MAC address of BSSID_1x, and the non-Transmitted BSSID AP in Multiple BSSID set 1 is AP4 with a MAC address of BSSID_1y; the Transmitted BSSID AP in Multiple BSSID set 2 is AP2 with a MAC address of BSSID_2x, and the non-Transmitted BSSID APs in Multiple BSSID set 2 include AP5 with a MAC address of BSSID_2y and AP6 with a MAC address of BSSID_2z; the Transmitted BSSID AP in Multiple BSSID set 3 is AP3 with a MAC address of BSSID_3x, and the non-Transmitted BSSID AP in Multiple BSSID set 3 is AP4 with a MAC address of BSSID_1y. BSSIDAP includes AP7 with MAC address BSSID_3y and AP8 with MAC address BSSID_3z. Figure 7 It can be seen that the Transmitted BSSID APs (ie, transmitting APs) from different Multiple BSSID sets are all in the AP multi-link device MLD1.

[0244] In the embodiment of the present application, the first management frame carries information of neighbor APs, for example, the information of the neighbor APs is carried in a neighbor report element, or a reduced neighbor report element (Reduced Neighbor Report element). The reduced neighbor report element is used as an example for explanation below. The reduced neighbor report element needs to carry information of other APs in the AP multi-link device except the reporting AP, such as the operation set, channel number, BSSID, ShortSSID of other APs, information of whether other APs belong to MultipleBSSID, information of whether other APs belong to Transmitted BSSID, and if the other APs belong to the Multiple BSSID set, it also includes information of each AP in the Multiple BSSID set, etc. It can be understood that when the information of the neighbor APs of the reporting AP is reported by the reporting AP, the neighbor AP is also called the reported AP. The reduced neighbor report element is illustrated below.

[0245] The Reduced Neighbor Report element includes one or more of the first information (also called the Co-MLD field), the second information (also called the MLD Multiple BSSID field), and the third information (also called the SameMLD field).

[0246] The first information is used to indicate whether the reported AP and the reporting AP are in the same MLD or whether the reported AP and the member APs of the MLD to which the reporting AP belongs belong to the same Multiple BSSID set.

[0247] The field carrying the first information may be referred to as a first information field. The first information field may also have other names, for example, a co-MLD field.

[0248] Optionally, the first information field may be set in the BSS parameter field of the simplified neighbor report element or in the TBTT information field. In FIG8(a), the Co-MLD field is specifically illustrated as a reserved bit (bit 7) of the BSS parameter field. As shown in FIG8(a), in Example 1, if the reported AP and the reporting AP are in the same MLD or the members of the MLD to which the reported AP and the reporting AP belong belong to the same MultipleBSSID set, the value of an indicator bit of the Co-MLD field is set to 1; if the reported AP and the reporting AP are not in the same MLD and the reported AP does not belong to the same Multiple BSSID set as the members of the MLD to which the reporting AP belongs, the value of the indicator bit is set to 0. Example 2: Whether the reported AP and the reporting AP are in the same MLD can be indicated by an indicator bit. For example, the value of this indicator bit is set to 1 to indicate that the reported AP and the reporting AP are in the same MLD, and the value of this indicator bit is set to 0 to indicate that the reported AP and the reporting AP are not in the same MLD. In addition, whether the reported AP belongs to the same Multiple BSSID set as the members of the MLD to which the reporting AP belongs can be indicated by another indicator bit. For example, the value of this indicator bit is set to 1 to indicate that the reported AP belongs to the same Multiple BSSID set as the members of the MLD to which the reporting AP belongs. The value of this indicator bit is set to 0 to indicate that the reported AP does not belong to the same Multiple BSSID set as the members of the MLD to which the reporting AP belongs. These two indicator bits are carried in the Co-MLD field. In another example, if the reported AP and the reporting AP are in the same MLD or the reported AP and the members of the MLD to which the reporting AP belongs belong to the same Multiple BSSID set, the Co-MLD field is set to 1, indicating that the reported AP and the reporting AP are in the same MLD or the reported AP and the members of the MLD to which the reporting AP belongs belong to the same Multiple BSSID set; conversely, if the reported AP and the reporting AP are not in the same MLD or the reported AP and the members of the MLD to which the reporting AP belongs do not belong to the same Multiple BSSID set, the Co-MLD field is set to 0, indicating that the reported AP and the reporting AP are not in the same MLD or the reported AP and the members of the MLD to which the reporting AP does not belong belong to the same Multiple BSSID set.

[0249] As shown in Figure 8(a), the TBTT information field may also optionally include an MLD-Index field. When the Co-MLD field is set to 1, the MLD-index field carries the index or MAC address of the MLD to which the reporting AP and the reported AP belong, indicating the MLD. For the case where the Co-MLD field is set to 0, the TBTT information field may include an MLD-idex field. The MLD-index field may be set to a reserved or other value, or may not include the MLD-index field. Other examples of the MLD-index field will be further described in subsequent sections.

[0250] The second information is used to indicate whether the reported AP and the members of the MLD to which the reporting AP belongs belong to the same Multiple BSSID set.

[0251] The field carrying the second information may be referred to as the second information field, and the second information field may have other names, for example, the MLD Multiple BSSID field. The second information field may be set in the BSS parameter field of the simplified neighbor report element or the TBTT information field, and the MLD Multiple BSSID field may be a newly added field in the BSS parameter field of the simplified neighbor report element or the TBTT information field.

[0252] The third information is used to indicate whether the reported AP and the reporting AP belong to the same MLD. If they belong to the same MLD, the third information is set to the seventh value. If they do not belong to the same MLD, the third information is set to the eighth value. For example, the third information includes 1 bit, which is set to 1 to indicate that the reported AP and the reporting AP do not belong to the same MLD, and which is set to 0 to indicate that the reported AP and the reporting AP do not belong to the same MLD. The field carrying the third information may be referred to as the third information field, and the third information field may have other names.

[0253] The third information field can be set in the BSS parameter field or the TBTT information field of the simplified neighbor report element. Taking Figure 8 (b) as an example, the third information field can be specifically the same MLD field in the BSS parameter field in the simplified neighbor report element, and the same MLD field can be the reserved bit (B7) in the BSS parameter field. If the reported AP and the reporting AP are in the same MLD, the value of an indicator bit of the same MLD field is set to 1; if the reported AP and the reporting AP are not in the same MLD, the value of the one indicator bit is set to 0. Taking Figure 8 (b) as an example, optionally, the TBTT information field can also include the MLD-Index field. When the same MLD field is set to 1, the MLD-index field carries the index or MAC address of the MLD to which the reporting AP and the reported AP belong, indicating the MLD. In the case where the same MLD field is set to 0, the TBTT information field can include the MLD-idex field, and the MLD-index field can be set to a reserved or other value, or of course, the MLD-index field may not be included. Other examples of the MLD-index field will be further described in subsequent sections.

[0254] The fourth information is used to indicate whether the reported AP belongs to the Multiple BSSID set.

[0255] For example, the fourth information may be specifically a Multiple BSSID indicator bit, the Multiple BSSID indicator bit is set to a specific value, for example, the Multiple BSSID indicator bit includes 1 bit, the 1 bit is set to 1 to indicate that the reported AP belongs to the Multiple BSSID set, and the Multiple BSSID indicator bit is set to another specific value, for example, the Multiple BSSID indicator bit includes 1 bit, the 1 bit is set to 0 to indicate that the reported AP does not belong to the MultipleBSSID set. Exemplarily, the Multiple BSSID indicator bit may be the Multiple BSSID field in the BSS parameter field.

[0256] Among them, the eighth information is used to indicate the MLD index (MLD-Index) of the reported AP (reported AP). The field carrying the above eighth information can be called the eighth information field, and the eighth information field can also have other names, for example, the MLD-index field. The eighth information field can be set in the TBTT info field of the Reduced Neighbor Report element (Reduced NeighborReport element). Optionally, for a reporting AP, when it needs to report multiple reported APs, each of these multiple reported APs corresponds to an MLD index, and different MLDs can be distinguished by the MLD index. Therefore, when the MLD indexes of two reported APs are the same, it indicates that the two reported APs belong to the same MLD. For example, the MLD index of the MLD to which the reported AP with a MAC address of BSSID-2x belongs and the MLD index of the MLD to which the reported AP with a MAC address of BSSID-3y belongs are both 2, which means that the two reported APs belong to MLD 2. Optionally, when the same reported APL is labeled by different reporting APs, the labeled MLD numbers may be the same or different. Optionally, the MLD index field may carry the MLD number, the MLD MAC address, or the MLD identifier.

[0257] Optionally, a special value of the MLD index field can be used to indicate whether the reported AP and the reporting AP belong to the same MLD. For example, if a reported AP and a reporting AP belong to the same MLD, then a special MLD Index value (such as all 0s) can be carried in the eighth information to represent the sequence number of the MLD to indicate that the reported AP and the reporting AP belong to the same MLD. When the receiving end (such as a site) subsequently reads the special MLD index value, although the MLD sequence number of the MLD to which the reported AP belongs cannot be directly obtained, it can be known that the MLD sequence number of the MLD to which the reported AP belongs is the same as the MLD sequence number of the reporting AP, because the receiving end can obtain the MLD sequence number of the MLD to which the reporting AP belongs from the first management frame, and therefore the MLD sequence number of the MLD to which the reported AP belongs can also be known.

[0258] Optionally, if the reported AP does not belong to any MLD, then the reported AP does not have a corresponding MLD sequence number. Therefore, a special MLD index value (for example, set to 255) can be carried in the eighth information to indicate that it has no corresponding MLD sequence number (or expressed as: using a special value of the eighth information (for example, set to 255) to indicate that the reported AP does not belong to any MLD). Of course, in the case where the reported AP does not belong to any MLD, it can also be regarded as belonging to a virtual AP multi-link device MLD, which includes an AP. At this time, the virtual MLD to which the reported AP belongs also has a normal MLD-Index, but the MLD-Index of the MLD to which other APs belong is different from the MLD-Index of the virtual MLD to which the reporting AP belongs.

[0259] In one embodiment, the eighth information may be carried in a Reduced NeighborReport element only when the reported AP and the reporting AP are in the same MLD or the members of the MLD to which the reporting AP belongs belong to the same Multiple BSSID set, as illustrated below.

[0260] Optionally, the first information may be used to indicate whether the reported AP and the reporting AP are in the same MLD or belong to the same Multiple BSSID set as the members of the MLD to which the reporting AP belongs. If so, the first information may carry a third value. If not (i.e., the reported AP and the reporting AP are not in the same MLD, nor do they belong to the same Multiple BSSID set as the members of the MLD to which the reporting AP belongs), the first information may carry a fourth value. For example, the first information includes 1 bit, which is set to 1 to indicate that the condition is met, and which is set to 0 to indicate that the condition is not met. Optionally, the third information may also be used to indicate that the reported AP and the reporting AP belong to the same MLD. Furthermore, the eighth information may be carried in a Reduced Neighbor Report element.

[0261] For example, as shown in Figure 8(a), if the first information of the Co-MLD field indicates that the reported AP and the reporting AP are in the same MLD or the members of the MLD to which the reported AP and the reporting AP belong belong to the same Multiple BSSID set, the eighth information is carried through the MLD-Index field.

[0262] Optionally, as shown in FIG8(b), if the Same-MLD field indicates that the reported AP and the reporting AP are in the same MLD, the eighth information is carried by the MLD-Index field. Figure 6 For example, assuming that the AP with MAC address BSSID-1x is the reporting AP, and the AP with MAC address BSSID-2x and the AP with MAC address BSSID-2y are two reported APs, since the reported AP with MAC address BSSID-2y and the reporting AP with MAC address BSSID-1x are in the same MLD, the first information field of the simplified neighbor report element corresponding to the reported AP with MAC address BSSID-2x carries the third value; in addition, although the reported AP with MAC address BSSID-2x and the reporting AP with MAC address BSSID-1x do not belong to the same MLD, they belong to the same Multiple BSSID set as the AP with MAC address BSSID-2y in the MLD to which the reporting AP with MAC address BSSID-1x belongs, so the first information field of the simplified neighbor report element corresponding to the reported AP with MAC address BSSID-2y carries the third value. When the first information carries the third value, a corresponding field will be added to the simplified neighbor report element to carry the eighth information.

[0263] In another embodiment, the eighth information may be carried in the simplified neighbor report element only when the reported AP and the members of the MLD to which the reporting AP belongs belong to the same MultipleBSSID set, which is described below with an example.

[0264] Optionally, the second information may be used to indicate whether the reported AP and the members of the MLD to which the reporting AP belongs belong to the same Multiple BSSID set. If so, the second information carries the fifth value; if not, the second information carries the sixth value. For example, the first information includes 1 bit, which is set to 1 to indicate that the condition is met, and which is set to 0 to indicate that the condition is not met. When the value carried by the second information is the fifth value, a corresponding field is added to the simplified neighbor report element to carry the eighth information.

[0265] In another example, if the fourth information indicates that the reported AP belongs to a Multiple BSSID set, for example, the Multiple BSSID field in the BSSparameter field indicates that the reported AP belongs to a Multiple BSSID set, the TBTT information field may also carry the MLD-index field.

[0266] In the embodiment of the present application, the member reporting the MLD to which the AP belongs includes two possibilities, as follows: 1. any member of the MLD to which the AP belongs, 2. any other member of the MLD to which the AP belongs except the member reporting the AP. If the present application mentions the member reporting the MLD to which the AP belongs, the above two possibilities are included and will not be repeated elsewhere.

[0267] Among them, the ninth information is used to indicate the Multiple BSSID set serial number (Multiple BSSIDset-index) of the Multiple BSSID set to which the reported AP belongs. The field carrying the above-mentioned ninth information can be called the ninth information field, and the ninth information field can also have other names, for example, the Multiple BSSID set-index field. The ninth information field can be set in the TBTT info field of the Reduced Neighbor Report element. Optionally, the Multiple BSSID set-index field can carry the serial number or ID of the Multiple BSSID set.

[0268] Optionally, method 1: the ninth information may be carried in the simplified neighbor report element only when all of the following conditions are met:

[0269] Condition 1: If the reported AP belongs to the Multiple BSSID set.

[0270] Condition 2: The reported AP and the reporting AP are in the same MLD or belong to the same multi-BSSID set as the members of the MLD to which the reporting AP belongs.

[0271] Optionally, method 2: parse the ninth information above when all the following conditions are met.

[0272] Condition 1: The members of the MLD to which the reporting AP belongs belong to the same multi-BSSID set

[0273] Optionally, method three: parse the ninth information above when all the following conditions are met.

[0274] Condition 1: If the reported AP belongs to the Multiple BSSID set.

[0275] For example, if the reported AP belongs to the Multiple BSSID set, the Multiple BSSID indicator in the BSS parameters field has the first value, such as 1. If the reported AP and the reporting AP are in the same MLD or the members of the MLD to which the reporting AP belongs belong to the same multiple BSSID set, the Co-MLD field value is 1; if both the Multiple BSSID indicator and the Co-MLD field are set to 1, a MultipleBSSID set-index field is added to the TBTT info field. Optionally, when only condition 1 is met, a Multiple BSSID set-index field can also be added to the TBTT info field.

[0276] It can be understood that if the simplified neighbor report elements of multiple reported APs include the same ninth information (such as Multiple BSSID set-index), it means that the multiple reported APs are APs in the same Multiple BSSID set. Optionally, when the reported AP and the reporting AP are in the same Multiple BSSID set, the Multiple BSSID set-index in the simplified neighbor report element of the reported AP can be set to a special value (for example, 0). When the subsequent receiving end reads that the Multiple BSSID set-index in the simplified neighbor report element of the reported AP is the special value, it can be determined that the reported AP and the reporting AP are in the same Multiple BSSID set. In another way, the information of each AP in the same Multiple BSSID set can be obtained based on the Multiple BSSID element carried by the reporting AP in the first management frame.

[0277] Of course, if the above two conditions are not met, the TBTT info field may also include a Multiple BSSID set-index field, which is a reserved value or does not indicate any Multiple BSSID set. The scheme of carrying the Multiple BSSID set-index field only when conditions 1 and 2 are met, and the scheme of carrying the Multiple BSSID set-index field only when condition 1 is met, have smaller signaling overhead.

[0278] Optionally, for members other than the reporting AP in the same Multiple BSSID set as the reporting AP, the information of these other AP members may not be carried in the Reduced neighbor report element, but may be indicated by the Multiple BSSID element carried in the management frame.

[0279] The simplified neighbor report element may include one or more of the eighth information, the ninth information, the first information, the second information, the third information and the fourth information, and may also include one or more of the fifth information, the sixth information and the seventh information.

[0280] Among them, the fifth information is used to indicate the link ID of the reported AP. It can be understood that for the same AP multi-link device MLD, the link IDs occupied by the multiple APs contained therein are unique. Therefore, for a certain MLD, the corresponding AP can be uniquely determined by the link ID. In the embodiment of the present application, the Link ID can be one-to-one corresponding to the operating class, or the channel number, or the MAC address of the reported AP, or a combination of multiple thereof. Therefore, in the first management frame sent by the reporting AP, or other management frames, if it is necessary to carry the BSS parameters of a reported AP, the link ID corresponding to the reported AP can be directly added. The receiving end can determine the corresponding operating class, channel number, MAC address of the reported AP and other information according to the link ID corresponding to the reported AP, without repeatedly indicating these information, thereby achieving the effect of saving overhead.

[0281] For example, as shown in Figure 8(c), if the first information in the Co-MLD field indicates that the reported AP and the reporting AP are in the same MLD or belong to the same Multiple BSSID set as the members of the MLD to which the reporting AP belongs, the eighth information is carried in the MLD-Index field. In addition, the ninth information may be carried in the Multiple BSSIDset-index field, and the fifth information may be carried in the Link ID field. Of course, the TBTT information field shown in Figure 8(b) may also include the Link ID field and the Multiple BSSIDset-index field.

[0282] Among them, the sixth information is used to indicate the link identifier (Link ID) of the reporting AP and / or the MAC address (Address) of the MLD where the reporting AP is located. The use principle of the link identifier (Link ID) of the reporting AP can refer to the description of the use principle of the reported AP in the fifth information above, and will not be repeated here. In addition, the MAC address (Address) of the MLD where the reporting AP is located is used to help determine the MAC address of the MLD where the reported AP is located. It is mentioned in the previous scheme that if the MLD sequence number of the MLD where the reported AP is located is the same as the MLD sequence number of the MLD where the reporting AP is located, the MLD sequence number of the MLD where the reported AP is located can be simply represented by the first value. Therefore, after determining that the MLD sequence numbers of the reported AP and the reporting AP are the same through the first value, the MAC address of the MLD where the reported AP is located can be further determined according to the MAC address of the MLD where the reporting AP is located indicated here (which can be used as the MLD sequence number). In addition, the MAC address of the MLD of the AP can also be used to establish associations between multi-link devices, such as being carried in the interaction process of the probe request frame / probe response frame, the authentication request frame / authentication response frame, and the association request frame / association response frame.

[0283] Optionally, the sixth information may not be in the simplified neighbor report element, but still in the above-mentioned first management frame, such as in the MLD element of the first management frame, where the MLD element is used to indicate the information of multiple APs of the same MLD, or the information of one or more single-link APs.

[0284] like Fig.17 As shown, the MLD element includes: a public control field, an MLD public information field, and one or more optional sub-elements. Optionally, the MLD public information field includes an MLD MAC address field, and optionally includes fields such as an authentication algorithm. The MLD MAC address field is used to indicate the address of the MLD indicated by the MLD element, and the address is used to identify an MLD. Optionally, the address of the MLD is the MAC address of the MLD, or it can be said that the MAC address is used to identify the AP multi-link device management entity, wherein the MAC address of the AP multi-link device may be the same as one of the MAC addresses of the n APs included in the multi-link AP MLD, or may be different from the MAC addresses of the n APs. For example, the MAC address of the AP multi-link device is a public MAC address, which can identify the AP multi-link device.

[0285] Optionally, the public control field includes an MLD address existence field (or called an MLD address occurrence field or an MLD address occurrence identifier), which is used to indicate whether the MLD address field exists in the MLD public information field. Optionally, the public control field also includes an authentication algorithm occurrence field, which is used to indicate whether the authentication algorithm field exists in the MLD public information field. Optionally, the above-mentioned "occurrence field" may include 1 bit, taking a first value to indicate that the corresponding field appears, and taking a second value to indicate that the corresponding field does not appear. For example, the first value is 1 and the second value is 0.

[0286] Optionally, an MLD element also includes one or more sub-elements, and a sub-element describes the information of an AP in the multi-AP multi-link device. The content of each sub-element includes the link identifier of the AP. Optionally, each sub-element also includes fields related to the AP, such as the SSID field, the timestamp field, the beacon interval field, and elements of the AP. The elements of the AP include the BSS load element, the EHT capability element, and the EHT operation element.

[0287] In the AP MLD discovery mechanism, the reporting AP in the AP MLD (any AP except the non-transmitting AP in the multi-BSSID set can serve as a reporting AP) sends the first management frame on its working link, such as a beacon frame, a probe response frame, etc. In addition to sending a reduced neighbor report element (RNR element), it also needs to carry an MLD element. The MLD element can be used to indicate the common information in the AP MLD and the specific information of each AP. In this way, it can help the STA MLD select an optimal AP MLD to establish a multi-link association. In order to avoid the first management frame being too long, the first management frame only carries the MLD public information of the MLD element, and the information of the sub-elements corresponding to each AP does not need to be carried, such as Fig.18 The first half of the MLD element shown includes one or more or all of the MLD MAC address, link identifier, and MLD sequence number, and optionally, an authentication algorithm field. The link identifier is used to indicate the reporting AP, as mentioned in the sixth information above, and will not be repeated here; the MLD sequence number is used to indicate the sequence number of an AP MLD, which is consistent with the MLD sequence number indicated by the eighth information in the RNR element, that is, for the same AP MLD, the MLD sequence number used in the RNR element is the same as the MLD sequence number in the MLD element. For example, Figure 6As shown, assuming that the reporting AP in MLD1 is BSSID-1x, the first management frame sent by the reporting AP carries the RNR element, and the RNR element carries information of APs such as BSSID-2y, BSSID-3x, BSSID-2x, BSSID-3y, BSSID-1y and BSSID-2z, and optionally carries information of BSSID-3z. At this time, the first half of the MLD element of MLD1, the first half of the MLD element of MLD2, and the first half of the MLD element of MLD3 are additionally carried, and optionally include the first half of a special MLD element indicating BSSID-3z, wherein the MLD sequence number of the special MLD element is set to a special value, such as 255, the MLD MAC address is the MAC address of the AP, or does not appear, and the link identifier is the link identifier of the single AP.

[0288] The RNR element sent by the reporting AP must include the following information about the reported AP, including:

[0289] (1) All APs in the same AP MLD as the reporting AP, or all APs in the same AP MLD as the reporting AP;

[0290] (2) All APs in the AP MLD of the non-transmitting AP in the same multi-BSSID set as the reporting AP; or all APs in the AP MLD of the non-transmitting AP in the multi-BSSID set where the reporting AP is located;

[0291] (3) All APs in the AP MLD that meet the following two conditions, where the two conditions are: 1) at least one AP in the AP MLD is in the same multi-BSSID set as an AP in the AP MLD where the reporting AP is located; 2) no AP in the AP MLD works on the same link as the reporting AP. In a special case, the AP MLD includes only one AP. Optionally, the AP MLD includes an AP working at 6 GHz. Optionally, the AP MLD may include only the AP MLD of one AP.

[0292] For AP MLDs that meet conditions 1 and 2, after the STA MLD station obtains the information, it can directly send a probe response frame or receive a beacon frame on the current link, where the probe request frame carries the first half of the MLD element, or also carries the link identifier of one or more APs, to obtain the complete information of the corresponding AP MLD, that is, it also includes the detailed information of each AP in the corresponding AP MLD. Specify the detailed information of multiple APs. Then establish a multi-link association with the AP MLD, or skip scanning and directly establish a multi-link association with the AP MLD. The first half of the MLD MAC address in the MLD element can be a special MAC address, or the MLD sequence number is set to a special MLD sequence number, that is, to obtain the information of all surrounding AP MLDs. After the AP in the AP MLD receives the request from the STA MLD, it sends a probe response frame, including the content of the STA MLD request, such as carrying one or more MLD elements. Optionally, each MLD element includes an MLD sequence number.

[0293] For the AP MLD that meets condition 3, optionally, the AP MLD includes an AP working at 6GHz, and the STA MLD can directly obtain the information of the AP MLD without scanning other links. If the STA MLD is interested in the AP MLD, such as a suitable frequency band, the STA MLD can further send the above-mentioned detection request frame, or receive specific information sent by an AP in the AP MLD on the corresponding link. Then establish a multi-link association with the AP MLD, or skip scanning and directly establish a multi-link association with the AP MLD. After the AP in the AP MLD receives the request from the STA MLD, it sends a detection response frame, including the content of the STA MLD request, such as carrying one or more MLD elements. Optionally, each MLD element includes an MLD sequence number.

[0294] The MLD common information in the first half of the MLD element carried by a STA in the STA MLD sent by the probe request frame may include only one or two fields, and does not need to carry all the fields, such as the MLD sequence number or the MLD MAC address.

[0295] by Figure 6 For example, including

[0296] (1) All APs in the same AP MLD1 as the reporting AP, BSSID-1x, i.e., BSSID-2y, BSSID-3x;

[0297] (2) All APs in AP MLD3 where the non-transmitting AP (i.e., BSSID-1y) in the same multi-BSSID set 1 as the reporting AP, BSSID-1x, are: BSSID-1y, BSSID-2z;

[0298] (3) Figure 6 The AP MLDs that meet the above two conditions are the two APs in AP MLD2, BSSID-2x and BSSID-3y, BSSID-2x in AP MLD2 and AP2y in AP MLD1 are in the same multi-BSSID set 2, and no AP in AP MLD2 is in a link with BSSID-1x. Optionally, a special AP MLD that includes only one AP, namely BSSID-3z, is also included.

[0299] In addition, if Fig.18 The first half of the MLD element shown also includes a public control field, wherein the public control field includes one or more or all of the MLD MAC address appearance field, the Link ID appearance field, the MLD sequence number appearance field, and the sub-element appearance field, and optionally includes the authentication algorithm appearance field. The MLD MAC address appearance is used to indicate whether the MLD public information includes the MLD MAC address field; the Link ID appearance is used to indicate whether the MLD public information includes the Link ID field; the MLD sequence number appearance is used to indicate whether the MLD public information includes the MLD sequence number field; wherein the above fields can be indicated by 1 bit respectively, such as 1 indicates appearance, 0 indicates non-appearance, or respectively by 2 values ​​of 1 field, the first value indicates appearance, and the second value indicates non-appearance.

[0300] It should be understood that Fig.17 The first half of the MLD element shown can also be used Fig.18 The first half of the MLD element shown is replaced to allow the AP MLD to provide further detailed information to the station MLD. For example, it is placed in a probe response frame or an association response frame. Optionally, the public control field includes an MLD public information presence field to indicate whether the MLD public information appears, or whether fields other than the MLD MAC address or MLD sequence number in the MLD public information field appear, to help further reduce duplicate information (at this time, the STAMLD has already learned this part of the information).

[0301] If the reporting AP belongs to a multi-BSSID set, the reporting AP must also send a multi-BSSID element, including a nontransmitted profile, indicating information about one or more non-transmitting APs. If the non-transmitting AP mentioned above comes from an AP MLD, then Fig.18The first half of the MLD element shown or Fig.17 The complete portion of the MLD element shown may also be placed in the information of the non-transmitting AP.

[0302] The seventh information is used to indicate whether the first management frame carries the information of all first reported APs, and the first reported APs are members of the MLD to which the reporting AP belongs. Another way is to indicate whether the management frame carries the information of all first reported APs and the information of the members in the Multiple BSSID set where all first reported APs are located. The seventh information can be located in a simplified neighbor report element, or in other existing elements in the above-mentioned first management frame, or in a newly added element in the above-mentioned first management frame. For ease of understanding, several optional indication examples of the seventh information are listed below.

[0303] Example 1: The seventh information is carried in a specific field (for example, it can be called a "complete field"), which is used to indicate whether the reporting AP carries the information of all first reported APs in the management frame, as well as the member information of the Multiple BSSID set where all first reported APs are located. For example, if yes, the seventh information can specifically take a value, such as 1; if no, the seventh information can specifically take another value, such as 0.

[0304] After acquiring the seventh information, the receiving end can know whether the relevant information corresponding to each reported AP is completely received.

[0305] Example 2: The seventh information is carried in a specific field (for example, it can be called a "complete field"), which is used to indicate how many information cycles the reporting AP needs to send all the information of the first reported APs and the member information of the MultipleBSSID sets to which all the first reported APs are located; wherein, one information cycle can be specifically one beacon frame, or two beacon frames, or other time units that can measure the length of time.

[0306] After acquiring the seventh information, the receiving end can know whether the relevant information corresponding to each reported AP has been completely received. If not, it can also know how many information cycles are needed to complete the reception.

[0307] In the embodiment of the present application, the member reporting the MLD to which the AP belongs includes two possibilities, as follows: 1. any member of the MLD to which the AP belongs; 2. any other member of the MLD to which the AP belongs except the member reporting the AP. If the present application mentions the member reporting the MLD to which the AP belongs, the above two possibilities are included and will not be repeated elsewhere.

[0308] In the embodiment of the present application, the members in the Multiple BSSID set where the first reported AP is located include two possibilities, specifically as follows: 1. Any member in the Multiple BSSID set where the first reporting AP is located; 2. Any other member in the Multiple BSSID set where the first reporting AP is located except the first reporting AP. If the present application mentions the members in the Multiple BSSID set where the first reported AP is located, the above two possibilities are included and will not be repeated elsewhere.

[0309] The information placed in the TBTT information field mentioned in the embodiment of the present application includes one or more of the eighth information, the ninth information, the first information, the second information, the third information, the fourth information, and the fifth information. Among them, one or more of the first information, the second information, the third information, the fourth information, and the fifth information are carried in the BSS parameter field in the TBTT information field. Therefore, the length of the BSS parameter field may be 1 or 2 bytes. If the length of the BSS parameter field becomes 2 bytes, it is equivalent to a 1-byte BSS parameter field and a 1-byte BSS parameter extension field in Table 4. The length of the eighth information is 1 byte and the length of the ninth information is 1 byte.

[0310] Therefore, TBTT info Length (TBTT information length) field: indicates the length of each TBTT info field. The specific information formats carried under different lengths are shown in Table 5, and one or more of 13-byte length, 14-byte length and 15-byte length are added.

[0311] Table 5

[0312]

[0313] Of course, the BSS parameter field length may also be other bytes, such as 3 bytes, 4 bytes, 5 bytes, etc. The eighth information length may also be other bytes, such as 2 to 6 bytes, and the ninth information length may also be other bytes, such as 2 to 6 bytes, etc.

[0314] Step S402: The station receives the first management frame.

[0315] Specifically, after receiving the first management frame, the station parses and obtains information in the first management frame, for example, a reduced neighbor report element in the first management frame, a multiple BSSID element corresponding to the reporting AP, etc. The following focuses on how to interpret the information in the reduced neighbor report element.

[0316] Which of the above-mentioned eighth information, ninth information, first information, second information, third information, fourth information, fifth information, sixth information, and seventh information is carried in the reduced neighbor report element, and which information will be parsed by the site. Generally speaking, if the reduced neighbor report element (Reduced Neighbor Report element) carries one or more Neighbor AP info fields, the corresponding target information of one or more reported APs will be parsed (including at least one of the eighth information, ninth information, first information, second information, third information, fourth information, fifth information, sixth information, and seventh information). If the reduced neighbor report element (Reduced Neighbor Report element) carries one or more Neighbor AP info fields, there are two cases: Case 1. Each Neighbor AP info field corresponds to the information of a reported AP; Case 2. If multiple reported APs have the same operation set and channel number, then one Neighbor AP info field can include the information of multiple reported APs, and each TBTT information field of the Neighbor AP info field includes other information of a reported AP. In case 2, optionally, the TBTT information field corresponding to each reported AP has the same length. If they are different, each reported AP may be indicated by only one Neighbor AP Info field.

[0317] The following is an example of a station receiving target information in the Neighbor AP info field corresponding to one of the reported APs (the principle of target information in the Neighbor AP info field corresponding to other reported APs can be similar), as follows:

[0318] If the first information is parsed, the site can learn through the first information whether the reported AP is in the same MLD as the reporting AP or whether the reported AP belongs to the same Multiple BSSID set as the members of the MLD to which the reporting AP belongs; for example, when the value carried by the first information is the third value (such as 1), the judgment result is yes; when the value carried by the first information is the fourth value (such as 0), the judgment result is no.

[0319] If the second information is parsed, the site can use the second information to learn whether the reported AP belongs to the same Multiple BSSID set as the members of the MLD to which the reporting AP belongs; for example, when the value carried by the second information is the fifth value (such as 1), the judgment result is yes; when the value carried by the second information is the sixth value (such as 0), the judgment result is no.

[0320] Optionally, if the result of the determination based on the first information or the second information is yes, the site further parses the eighth information, that is, parses to obtain the MLD index (MLD-Index) to which the reported AP belongs. Of course, if the first information and the second information do not exist, the site can also directly try to parse the eighth information.

[0321] If the third information is parsed, the site can use the third information to learn whether the reported AP and the reporting AP belong to the same MLD; for example, when the value carried by the third information is the seventh value (such as 1), it is determined that the reported AP and the reporting AP belong to the same MLD; when the value carried by the third information is the eighth value (such as 0), it is determined whether the reported AP and the reporting AP belong to the same MLD.

[0322] If the fourth information is parsed, the site can learn whether the reported AP belongs to the Multiple BSSID set through the fourth information; for example, the fourth information can be specifically a Multiple BSSID indicator bit. When the Multiple BSSID indicator bit is set to a specific value (for example, it can be 1), it indicates that the reported AP belongs to the Multiple BSSID set; when the Multiple BSSID indicator bit is set to another specific value (for example, it can be 0), it indicates that the reported AP does not belong to the Multiple BSSID set.

[0323] Optionally, method one: parse the ninth information when all of the following conditions are met.

[0324] Condition 1: If the reported AP belongs to the Multiple BSSID set.

[0325] Condition 2: The reported AP and the reporting AP are in the same MLD or belong to the same multi-BSSID set as the members of the MLD to which the reporting AP belongs.

[0326] Optionally, method 2: parse the ninth information above when all the following conditions are met.

[0327] Condition 1: The members of the MLD to which the reporting AP belongs belong to the same multi-BSSID set.

[0328] Optionally, method three: parse the ninth information above when all the following conditions are met.

[0329] Condition 1: If the reported AP belongs to the Multiple BSSID set.

[0330] It can be understood that the MultipleBSSID set sequence number of the Multiple BSSID set to which the reported AP belongs can be obtained from the ninth information.

[0331] If the fifth information is parsed, the link ID of the reported AP can be obtained. Because the Link ID has a one-to-one correspondence with the operating class, channel number, MAC address of the reported AP, or a combination of one or more of them, if the site has previously received information such as the operating class, channel number, and MAC address of the reported AP, then this information can be obtained based on the correspondence without having to repeatedly indicate this information, thereby saving overhead.

[0332] If the sixth information is parsed, the link ID of the reporting AP can be obtained. Because the Link ID has a one-to-one correspondence with the operating class, or the channel number, or the MAC address of the reporting AP, or a combination of one or more of them, if the site has previously received the reporting AP operating class, channel number, MAC address of the reporting AP and other information, then this information can be obtained based on the correspondence without having to repeatedly indicate this information, thereby saving overhead.

[0333] If the seventh information is parsed, then it can be known whether the first management frame carries the information of all first reported APs, and the first reported AP is a member of the MLD to which the reporting AP belongs. Optionally, if the seventh information shows that the first management frame does not carry the information of all first reported APs, the station continues to receive new management frames until all the information of the first reported APs is received. If the seventh information shows how many information cycles are left to be received, then the corresponding information cycle can be continued to complete the reception of all the information of the first reported APs.

[0334] In another way, if the seventh information is parsed, then it can be known whether the management frame carries the information of all first reported APs and the information of the members in the Multiple BSSID set where all first reported APs are located based on the seventh information. Optionally, if the seventh information shows that the first management frame does not carry the information of all first reported APs, or does not carry the information of the members in the Multiple BSSID set where all first reported APs are located, the station continues to receive new management frames until the information of all first reported APs and the information of the members in the Multiple BSSID set where all first reported APs are located are received. If the seventh information shows how many information cycles are left to be received, the corresponding information cycle can be continued to receive, thereby completing the reception of the information of all first reported APs and the information of the members in the Multiple BSSID set where all first reported APs are located.

[0335] Taking Figure 8(a) as an example, after the station parses the Co-MLD field, it determines that the Co-MLD field is set to 1, and then it is determined that the reported AP and the reporting AP belong to the same MLD or whether the reported AP and the member APs of the MLD to which the reporting AP belongs belong to the same Multiple BSSID set. The station further determines that the TBTT information field also includes the MLD-index field, and further parses the MLD-index field to obtain the index or MAC address of the MLD to which the reported AP belongs. Taking Figure 8(b) as an example, after the station parses the same-MLD field, it determines that the same-MLD field is set to 1, and then it is determined that the reported AP and the reporting AP belong to the same MLD. The station can also determine whether the reported AP and the member APs of the MLD to which the reporting AP belongs belong to the same Multiple BSSID set based on the MLD Multiple BSSID field. The station further parses the MLD-index field to obtain the index or MAC address of the MLD to which the reported AP belongs.

[0336] Taking Figure 8(c) as an example, after the site parses the Co-MLD field, it determines that the Co-MLD field is set to 1, then it is determined that the reported AP and the reporting AP belong to the same MLD or whether the reported AP and the member APs of the MLD to which the reporting AP belongs belong to the same Multiple BSSID set. The site then further parses the MLD-index field, Link ID field, and MultipleBSSID set index field to obtain the index or MAC address of the MLD to which the reported AP belongs, the link ID, and the Multiple BSSID set index.

[0337] In an embodiment of the present application, optionally, the site can obtain, based on one or more of the eighth information, ninth information, first information, second information, third information, fourth information, fifth information, sixth information and seventh information, which MLD each reported AP belongs to and which Multiple BSSID set each reported AP belongs to, thereby having an overall understanding of the Multiple BSSID set structure based on the AP multi-link device, and then, the site can select a suitable AP from the Multiple BSSID set structure based on the AP multi-link device. In specific implementation, the site can carry a link identifier (Link ID) or a Link ID list in the detection request frame, and optionally carry an MLD-Index or an MLD MAC address, so that after the AP receives the detection request frame, it determines the corresponding AP based on the link ID, or the link ID list, or the MLD-Index, or the MLD MAC, and then replies to the site with more detailed information of the corresponding AP (such as AP capability information, operation information, etc., where the capability information is used to indicate which functions the AP supports, and the operation information can be used to indicate the center frequency, working bandwidth, etc. of the AP), and the site then establishes an association with the corresponding AP based on the more detailed information, as illustrated below with an example.

[0338] Example 1: The station carries the MLD-index and one or more of the link IDs in the probe request frame to request the AP to reply with the information of the AP corresponding to the link ID in the probe response frame. The station then establishes association with the AP according to the information of the AP corresponding to the link ID. Figure 6 As shown, the MLD-index carried in the detection request is MLD2, and the link ID carried is link 2 (link2). Then the AP can determine that the corresponding AP is the AP with a MAC address of BSSID-2x based on MLD2 and link2. Therefore, more detailed information of the AP with a MAC address of BSSID-2x is sent to the station, and the station establishes an association with the AP with a MAC address of BSSID-2x.

[0339] Example 2: The station carries the MLD-index and one or more link IDs in the probe request frame to request the AP to reply with information about the APs corresponding to other link IDs other than the one or more link IDs in the probe response frame. The station then selects one or more of the APs to establish associations based on the information about the APs corresponding to the other link IDs. For example, Figure 6As shown, the MLD-index carried in the detection request is MLD1, and the link IDs carried are link 1 (link1) and link 3 (link3). Then, based on MLD2, link1 and link3, the AP can determine that the AP on link2 other than link1 and link3 in the MLD corresponding to MLD2 is the AP with a MAC address of BSSID-2x. Therefore, more detailed information of the AP with a MAC address of BSSID-2x is sent to the station, and the station establishes an association with the AP with a MAC address of BSSID-2x.

[0340] Optionally, the site may also carry signaling in the detection request frame, such as a special Link ID, to request the AP to reply with the information of all first reported APs in its MLD and the member information of the Multiple BSSID set where all first reported APs are located, or only to request the AP to reply with the information of all first reported APs in its MLD, as the basis for the site to select the associated AP.

[0341] exist Figure 4 In the method shown, by carrying the MLD information of the reported AP and the Multiple BSSID set information in the simplified neighbor report element of the first management frame, the station receiving the first management frame can obtain the basic situation of each reported AP in the MLD and the Multiple BSSID set based on this information, so as to better select the appropriate AP from the reporting AP and the reported AP for association.

[0342] See also Fig. 9 , Fig. 9 This is an AP multi-link device discovery method provided by an embodiment of the present application. The method can be applied between sites, between access points and sites, and between access points and access points. For the convenience of description, the following description is based on the communication between access points and sites. The method includes but is not limited to the following steps:

[0343] Step S901: the access point AP sends a second management frame to a station.

[0344] Specifically, the second management frame carries information about a neighbor AP, and the neighbor AP can be used as a candidate AP when the site switches BSS. The second management frame can help the site obtain information about neighbor APs of the associated AP, which is used for potential candidate APs for roaming. For example, the second management frame can be a beacon frame, a probe response frame, an association response frame, a reassociation response frame, an authentication frame, etc. The second management frame may be sent by an AP multi-link device, or a reporting AP in an AP multi-link device. The site receiving the second management frame may be either a site in a site multi-link device or a single-link site. In other types of BSSs, the site sending the second management frame may also be a site that belongs to a multi-link device MLD; the site receiving the second management frame may also be an access point that belongs to an MLD or a single-link access point. The subsequent descriptions are all illustrated by taking the example of a reporting AP in an AP multi-link device sending a second management frame to a site.

[0345] In an embodiment of the present application, in one example, an AP multi-link device may include one logical AP, which switches to work on multiple links. In another example, an AP multi-link device includes n logical APs, which work on n different links, respectively. Therefore, link identifiers link1, link2, ..., linkn can be used to represent them, and the MAC address of each AP is different. An AP multi-link device is identified by an MLD MAC address, or it can be said that the MAC address is used to identify the AP multi-link device management entity, wherein the MAC address of the AP multi-link device may be the same as one of the MAC addresses of the n logical APs included in the multi-link AP, or may be different from the MAC addresses of the n logical APs. For example, the MAC address of the AP multi-link device is a public MAC address, which can identify the AP multi-link device.

[0346] In one example, a logical AP or multiple logical APs in an AP multi-link device may belong to one or more multiple Basic Service Set Identifier (BSSID) sets. In one example, the multiple BSSID sets to which each logical AP in an AP multi-link device belongs are different. In another example, multiple logical APs in an AP multi-link device may belong to the same Multiple BSSID set. For example, if there are two logical APs in the AP multi-link device working on one link, in this case, the two logical APs may belong to the same multiple BSSID set.

[0347] The Multiple BSSID set architecture based on the AP multi-link device in the embodiment of the present application can be as described in the previous embodiment. Figure 5 , Figure 6 , Figure 7 The relevant statements will not be repeated here.

[0348] In the embodiment of the present application, the second management frame carries a neighbor report element (Neighbor Report element), and the neighbor report element needs to carry information of the neighbor AP of the reporting AP, such as the operation set, channel number, BSSID, etc. of the neighbor AP. If the AP in the AP multi-link device belongs to the Multiple BSSID set, the neighbor report element may also include a corresponding Multiple BSSID element. The neighbor report element is illustrated below.

[0349] A neighbor report element, such as the BSSID information field therein, carries the first information.

[0350] First information:

[0351] The first information is used to indicate one or more of the following information:

[0352] Whether the reported AP belongs to the same MLD as the reporting AP; whether the reported AP belongs to an AP in an MLD; the reported AP and the previously reported reported AP belong to the same MLD.

[0353] Optionally, when the first information indicates multiple items among the three items listed above, these multiple items can be indicated separately, for example, the first information includes 3 bits, each bit indicating whether one of the items satisfies the condition; for example, the first bit is 1 to indicate that the reported AP and the reporting AP belong to the same MLD, and the first bit is 0 to indicate that the reported AP and the reporting AP do not belong to the same MLD; the second bit is 1 to indicate that the reported AP belongs to an AP in an MLD, and the second bit is 0 to indicate that the reported AP does not belong to an AP in an MLD; the third bit is 1 to indicate that the reported AP belongs to the same MLD as the previously reported reported AP, and the third bit is 0 to indicate that the reported AP does not belong to the same MLD as the previously reported reported AP.

[0354] Optionally, a Neighbor Report element, such as an optional sub-element field thereof, carries the second information.

[0355] Second information:

[0356] The first optional scheme: the second information includes one or more of the MAC address (Address) of the AP multi-link device MLD where the reported AP is located, the number of APs included in the AP multi-link device MLD where the AP is located, the simultaneous transmit / receive (STR) capability indication between the APs in the AP multi-link device MLD where the AP is located, the link identifier (Link ID) corresponding to the reported AP, and the information of other APs in the AP multi-link device MLD where the AP is located except the reported AP (for example, LinkID, operating class, channel number, BSSID, capability third information apabilities, operating information Operating Infonation, etc.).

[0357] The second optional scheme: The second information includes one or more of the MAC address (Address) of the AP multi-link device MLD where the reported AP is located, the link identifier (Link ID) corresponding to the reported AP, the third capability information apabilities, and the operating information Operating Infonation. Optionally, in this scheme, the information of other APs in the AP multi-link device MLD where the reported AP is located except for the reported AP (such as Link ID, operating class, channel number, BSSID, etc.) can be indicated in one or more other neighbor report elements. Optionally, one neighbor report element carries one AP information.

[0358] Optionally, an MLD indicator bit is set in the neighbor report element (for example, 1 bit in bits 21-31 is used as an MLD indicator bit) to indicate whether the reported AP belongs to a certain MLD. If the reported AP belongs to an AP of a certain MLD, the value of the MLD indicator bit takes a first value; if the reported AP does not belong to an AP of a certain MLD, the value of the MLD indicator bit takes a second parameter value; for example, the first MLD indicator bit includes 1 bit, which is set to 1 to indicate that the reported AP belongs to an AP of a certain MLD, and which is set to 0 to indicate that the reported AP does not belong to an AP of a certain MLD. Bits 21-31 are as follows in the frame structure: Fig.10 shown.

[0359] Optionally, when the MLD indication bit is set to the first value, the above second information is carried (such as carrying a subelement for describing the MLD where the reported AP is located in optionalsubelements, and then carrying the second information in the subelement).

[0360] Optionally, if the reported AP and the reporting AP belong to the same MLD, since the station has obtained the reporting AP through other fields, the neighbor report element no longer carries the second information.

[0361] Optionally, if the reported AP belongs to the same MLD as the previous reported AP, since the site has obtained the relevant information of the MLD to which the previous reported AP belongs through other fields, the neighbor reporting element no longer carries the MAC address of the MLD to which the reported AP belongs. Of course, you can also choose to carry the MAC address of the MLD to which the reported AP belongs.

[0362] Optionally, if the reported AP belongs to a Multiple BSSID set, the optional subelements field of the NeighborReport element carries the fields of the Multiple BSSID elements of the Multiple BSSIDset to which the reported AP belongs. The reference BSSID (or Transmitted BSSID) of the Multiple BSSID element is carried in the BSSID field of the NeighborReport element.

[0363] Step S902: The station receives the second management frame.

[0364] Specifically, after receiving the second management frame, the station parses and obtains information in the second management frame, for example, a neighbor report element (Neighbor Report element) in the second management frame. The following focuses on how to use the information in the neighbor report element.

[0365] The second information and the first information mentioned above, which ones are carried in the neighbor report element, will be parsed by the site. For example, if the optional subelements field of the neighbor report element carries the second information mentioned above, and / or the reserved field in bits 21 to 31 of the BSSID info field carries the first information, then the second information and / or the first information will be parsed.

[0366] If the first information is parsed, the site can obtain one or more of the following contents through the first information:

[0367] Whether the reported AP and the reporting AP belong to the same MLD.

[0368] Whether the reported AP belongs to an AP in an MLD.

[0369] Whether the reported AP and the previously reported AP belong to the same MLD.

[0370] In the embodiment of the present application, optionally, if the reported AP belongs to an AP in an MLD, the site further parses the second information.

[0371] The first optional scheme: the second information includes one or more of the MAC address (Address) of the AP multi-link device MLD where the reported AP is located, the number of APs included in the AP multi-link device MLD where the AP is located, the simultaneous transmit / receive (STR) capability indication between the APs in the AP multi-link device MLD where the AP is located, the link identifier (Link ID) corresponding to the reported AP, and the information of other APs in the AP multi-link device MLD where the AP is located except the reported AP (for example, LinkID, operating class, channel number, BSSID, capability third information apabilities, operating information Operating Infonation, etc.).

[0372] The second optional scheme: The second information includes the MAC address (Address) of the AP multi-link device MLD where the reported AP is located, the link identifier (Link ID) corresponding to the reported AP, the third capability information apabilities, and one or more of the operating information OperatingInfonation. Optionally, in this scheme, the information of other APs in the AP multi-link device MLD where the reported AP is located except for the reported AP (such as Link ID, operating class, channelnumber, BSSID, etc.) can be indicated in one or more other neighbor report elements. Optionally, one neighbor report element carries one AP information.

[0373] In an embodiment of the present application, the site can learn which MLD the reported AP belongs to based on the second information in the neighbor report element, and by combining the information in the neighbor report elements corresponding to other reported APs, it can have a comprehensive understanding of the structure of the AP multi-link device, and then select an optional AP from it when the site switches BSS.

[0374] In specific implementation, the site sends an association request frame or a reassociation request frame to the AP. After receiving the association request frame or the reassociation request frame, the AP carries a neighbor report element in the replied association response frame or the reassociation response frame. The neighbor element carries information of one or more APs belonging to the MLD, such as the capability information and operation information of the AP, etc., wherein the capability information is used to indicate which functions the AP supports, and the operation information can be used to indicate the center frequency, working bandwidth, etc. of the AP. The site then chooses to establish an association with the corresponding AP based on the more detailed information. The following example is used to illustrate.

[0375] Example 1: A station sends an association request to an AP, and the AP carries a neighbor report element in a reply association response frame or a reassociation response, including information about one or more APs. The station can then choose to establish an association with one or more APs in the MLD. For example, Figure 6 As shown, the station sends an association request frame to the AP, then the AP carries the AP with a MAC address of BSSID-2x in MLD2 in the neighbor element in the association response frame or the reassociation response frame, and then the station chooses whether to establish an association with the AP with a MAC address of BSSID-2x.

[0376] exist Fig. 9 In the method shown, by carrying the information of the MLD where the reported AP is located in the neighbor report element of the second management frame, the station receiving the second management frame can obtain the basic situation of each reported AP in the MLD based on this information, so as to better select from the neighbor APs as candidate APs when the station switches BSS.

[0377] For the neighbor report element in the second management frame, in another implementation, this embodiment proposes adding at least one of the following information to the Neighbor Report element:

[0378] Whether the reported AP belongs to the same MLD as the reporting AP

[0379] Whether the reported AP belongs to a certain MLD,

[0380] If the reported AP belongs to a certain MLD, further indicate part or all of the information corresponding to the MLD, such as the MLD MAC Address and Link ID corresponding to the reported AP, the number of sites contained in the MLD, and one or more of the information of each site.

[0381] In the first implementation, using Fig.10As shown, the B21-B31 in the BSS information field carries a 1-bit MLD indication bit, which is used to indicate whether the BSSID belongs to a certain MLD. If the BSSID belongs to a certain MLD, the MLD indication bit is 1; otherwise, the MLD indication bit is 0;

[0382] When the MLD indication position is 1, a subelement describing the MLD to which the reporting AP belongs is carried in the optional subelements, and one or more of the following indication information is carried in the subelement:

[0383] MLD MAC Address

[0384] The number of APs included in the MLD

[0385] STR (simutaneous transmit / receive) capability indication between APs

[0386] Link ID corresponding to the reported AP

[0387] Information about other member APs in the MLD, such as the member AP’s Link ID, operating class, channel number, BSSID, etc.

[0388] In the second implementation, for example Fig.10 As shown, the B21-B31 in the BSS information field carries a 1-bit MLD indication bit, which is used to indicate whether the BSSID belongs to a certain MLD. If the BSSID belongs to a part of a certain MLD, the MLD indication bit is 1; otherwise, the MLD indication bit is 0;

[0389] When the MLD indication position is 1, a subelement describing the MLD to which the reported AP belongs is carried in the optional subelements. The subelement carries the following indication information:

[0390] MLD MAC Address

[0391] The information of other APs of the MLD, such as operating class, channel number, BSSID, etc., can be indicated using another Neighbor Report elements, and the same subelement used to describe the corresponding MLD can be carried in the optional subelements.

[0392] Optionally, in the second implementation, the neighbor report element may also include an indication method to indicate whether the reported AP indicated by the previous neighbor report element in the management frame and the reported AP indicated by the next neighbor packet element belong to the same MLD: for example, a 1-bit previous MLD indication bit carried in B21-B31 in the BSS information field is used to indicate whether the reported AP belongs to the same MLD as the previous reported AP.

[0393] In a third implementation, a 1-bit MLD indication bit may be carried in B21-B31 in the BSS information field to indicate whether the reported AP and the reporting AP belong to the same MLD. If they belong to the same MLD, the information of the MLD to which the reported AP and the reporting AP belong may be optionally not included in the neighbor report element, because the management frame sent by the reporting AP will carry the information of the MLD to which the reporting AP belongs.

[0394] By adopting the method of the embodiment of the present application, the site can obtain the MLD information of the reported AP in the neighbor report element, so that the site can learn the basic situation of each reported AP in the MLD based on this information, so as to better select from the neighbor APs as candidate APs when the site switches BSS.

[0395] See also Fig.11 , Fig.11 A fast BSS switching method based on a DS system is provided in an embodiment of the present application. The method involves a station (non-AP), a current AP (current AP) associated with the station, and a target AP (Target AP) to be switched by the station. The method for switching the station from the associated current AP to the target AP includes:

[0396] Step S1101: The station sends a fast transition (FT) request frame to the current AP.

[0397] Optionally, after receiving the FT request frame, the current AP replies with an Ack frame.

[0398] Step S1102: The current AP sends an FT response frame to the station.

[0399] Optionally, after receiving the FT response frame or the authentication response frame, the station replies with an Ack frame.

[0400] In an embodiment of the present application, the site specifically acts as a fast transition originator (FTO), which initiates a BSS switch based on a distributed system (DS) by sending the FT request frame. The sending address of the FT request frame is the MAC address of the site, the receiving address is the MAC address of the current AP, and it also carries first address information, wherein the first address information includes the MAC address of the MLD where the site is located, the MAC address of the MLD where the target AP is located, and the MAC address of the target AP; or, the first address information includes the MAC address of the MLD where the site is located, and the MAC address of the MLD where the target AP is located.

[0401] For example, Fig.13 and Fig.14 The figure shows a TF request action field and a TF response frame action field, wherein the TF request action field includes a classification, a FT action, a STA address, a target AP address, and a FT request frame body subfield, such as Fig.13 The FT response frame action field includes the FT confirmation action field, and the FT request action field includes the classification, FT action, STA address, target AP address, status codeword and FT response frame body subfield, as shown in FIG. Fig.14 The TF request frame action field and the TF response action field are respectively carried in the TF request frame and the TF response frame, wherein the MAC headers of the TF request frame and the TF response frame carry the receiving address and the sending address.

[0402] Optionally, if the site belongs to a site in a site MLD, the target AP is an AP in an AP multi-link device, and the MAC address of the MLD where the site is located in the first address information is carried in Fig.13 or Fig.14 The MAC address of the MLD where the target AP is located in the first address information is carried in Fig.13 or Fig.14 It is worth noting that if the station sending the FT request frame does not belong to MLD, the MAC address field of the station is still used to carry the MAC address of the station sending the FT request frame. If the target AP to which the station sending the FT request frame is to be switched does not belong to MLD, the target AP address field is still used to carry the MAC address of the target AP to which the station is to be switched.

[0403] Alternatively, the station MAC address field in the FT request frame action field is still used to carry the MAC address of the station sending the FT request frame, and the target AP address field is still used to carry the MAC address of the target AP to which the station sending the FT request frame is to switch. The MAC address of the MLD where the station is located and the MAC address of the MLD where the target AP is located are carried in Fig.13 or Fig.14 It is worth noting that if the station sending the FT request frame does not belong to the MLD, the MAC address of the MLD where the station is located does not exist. If the target AP to which the station sending the FT request frame is to be switched does not belong to the MLD, the MAC address of the MLD where the target AP is located does not exist.

[0404] Specifically, after receiving the FT action frame, the current AP parses the frame to obtain the first address information carried therein, and sends the parsed first address information to the target AP (Target AP).

[0405] Step S1103: The station sends a reassociation request frame to the target AP.

[0406] The current AP address field in the reassociation request frame carries the MAC address of the MLD where the current AP is located.

[0407] Optionally, after receiving the reassociation request frame, the target station responds with an Ack frame

[0408] Step S1104: the target AP replies with a reassociation response frame to the current station.

[0409] Optionally, after receiving the reassociation response frame, the station replies with an Ack frame

[0410] Optionally, both the above-mentioned reassociation request frame and the reassociation response frame carry the above-mentioned first address information. The MAC address of the MLD where the target AP is located in the first address information is carried in the MAC address field of the target AP, or in a newly added field. Optionally, the MAC address of the MLD where the site is located in the first address information is carried in the MAC address field of the site, or in a newly added field. In addition, if the site sending the reassociation request frame does not belong to the MLD, the MAC address field of the site is still used to carry the MAC address of the site sending the reassociation request frame.

[0411] In addition to the FT protocol mentioned above, the embodiment of the present application is also applicable to the FT resource request protocol. In addition to the above steps S1101, S1102, S1103 and S1104, the FT resource request protocol based on the DS system also includes the following steps between step S1102 and step S1103:

[0412] Step S1105: The station sends an FT confirmation frame to the current AP.

[0413] Optionally, after receiving the FT confirmation frame, the current AP replies with an Ack frame.

[0414] Step S1106: the current AP sends a FT ACK frame to the station.

[0415] Optionally, after receiving the FTAck frame, the station replies with an Ack frame.

[0416] The FT confirm frame includes an FT confirm action field, which includes a classification, FT action, STA address, target AP address, and FT confirm frame body subfield, having the following information: Fig.13 The FTAck frame includes an FTACK action field, which includes a classification, FT action, STA address, target AP address, status codeword, and FT Ack frame body subfield, with the following structure: Fig.14 Similar structure. The FTconfirm frame and FT Ack frame carry the first address information. The specific carrying method is as described in the FT request frame and FT response frame above, which will not be repeated here. The MAC address of the MLD where the site is located and the MAC address of the MLD where the target AP is located may also not exist. The specific description is as described in the FT request frame and FT response, which will not be repeated here.

[0417] exist Fig.11 In the method shown, the method provides a method for quickly switching a site multi-link device to an AP multi-link device, or a method for quickly switching a site to an AP multi-link device, or a method for quickly switching a site multi-link device to an AP, which can help all sites of the multi-link device participate in the fast switching.

[0418] See also Fig.12 , Fig.12 A fast BSS switching method based on a wireless air interface is provided in an embodiment of the present application. The method involves a site (non-AP), a current AP (current AP) associated with the site, and a target AP (Target AP) to be switched by the site. If the site belongs to a site in a site MLD, the target AP is an AP in an AP multi-link device. When the site switches from the associated current AP to the target AP, the method includes:

[0419] Step S1201: The station sends an authentication request frame to the target AP.

[0420] Optionally, after receiving the authentication request frame, the target AP replies with an Ack frame.

[0421] Step S1202: The target AP sends an authentication response frame to the station.

[0422] Optionally, after receiving the authentication response frame, the station replies with an Ack frame.

[0423] In an embodiment of the present application, the authentication request frame and the authentication response frame also carry the first address information, such as carried in the frame body, wherein the first address information includes the MAC address of the MLD where the site is located, the MAC address of the MLD where the target AP is located, and the MAC address of the target AP; or, the first address information includes the MAC address of the MLD where the site is located, and the MAC address of the MLD where the target AP is located. Another way: the authentication request frame carries the first address information. Specifically, the SA address field of the authentication request frame carries the MAC address of the MLD where the STA is located, and the DA field carries the MAC address of the MLD where the target AP is located. The authentication response frame carries the first address information. Specifically, the SA address field in the authentication response frame carries the MAC address of the MLD where the target AP is located, and the DA field carries the MLD address where the STA is located. The MAC address of the MLD where the site is located and the MAC address of the MLD where the target AP is located may also be one or more non-existent, as described in the FT request frame and the FT response, and will not be repeated here.

[0424] Step S1203: The station sends a reassociation request frame to the target AP.

[0425] The current AP address field in the reassociation request frame carries the MAC address of the MLD where the current AP is located.

[0426] Optionally, after receiving the reassociation request frame, the target station responds with an Ack frame

[0427] Step S1204: The target AP replies with a reassociation response frame to the current station.

[0428] Optionally, after receiving the reassociation response frame, the station replies with an Ack frame.

[0429] Optionally, both the above-mentioned reassociation request frame and the reassociation response frame carry the above-mentioned first address information. The MAC address of the MLD where the target AP is located in the first address information is carried in the MAC address field of the target AP, or in a newly added field. Optionally, the MAC address of the MLD where the site is located in the first address information is carried in the MAC address field of the site, or in a newly added field. In addition, if the site sending the reassociation request frame does not belong to the MLD, the MAC address field of the site is still used to carry the MAC address of the site sending the reassociation request frame.

[0430] In addition to the FT protocol mentioned above, the embodiment of the present application is also applicable to the FT resource request protocol. In addition to the above steps S1201, S1202, S1203 and S1204, the FT resource request protocol based on the wireless air interface also includes between steps S1202 and S1203:

[0431] Step S1205: The station sends an authentication confirmation frame to the current AP.

[0432] Step S1206: The current AP sends an authentication ACK frame to the station.

[0433] Among them, the authentication confirmation frame and the authentication ACK frame also carry one or more of the MAC address of the MLD where the site is located and the MAC address of the MLD where the target AP is located, for example, carried in the frame body. Another way: the authentication confirmation frame carries the first address information. Specifically, the SA address field of the authentication confirmation frame carries the MLD address where the STA is located, and the DA field carries the MAC address of the MLD where the target AP is located. The authentication Ack frame carries the first address information. Specifically, the SA address field in the authentication Ack frame carries the MAC address of the MLD where the target AP is located, and the DA field carries the MLD address where the STA is located. The MAC address of the MLD where the site is located and the MAC address of the MLD where the target AP is located may also be one or more non-existent, as described in the FT request frame and the FT response, which will not be repeated here.

[0434] For the case where non-AP MLD switches to AP MLD, in an example, the STA Address and Target AP Address fields in the corresponding FT Request / Response / confirm / ACK frames should carry the corresponding SAP Address of non-AP MLD and SAP Address of AP MLD, respectively.

[0435] exist Fig.12 In the method shown, the method provides a method for quickly switching a site multi-link device to an AP multi-link device, or a method for quickly switching a site to an AP multi-link device, or a method for quickly switching a site multi-link device to an AP, which can help all sites of the multi-link device participate in the fast switching.

[0436] The following is a detailed description of the device provided in the embodiment of the present application, which can improve the efficiency of discovering APs.

[0437] Fig.15A communication device 1500 provided in an embodiment of the present application is shown. The device may be an access point AP (e.g., a reporting AP in an AP multi-link device) or a station (e.g., a station that receives a first management frame, or a station that receives a second management frame, or a station in the above-mentioned BSS switching process) in the above-mentioned embodiment, or a chip or processing system in an access point AP (e.g., a reporting AP in an AP multi-link device) or a station (e.g., a station that receives a first management frame, or a station that receives a second management frame, or a station in the above-mentioned BSS switching process), which may implement the above-mentioned Figure 4 The methods and functions of the embodiments shown, or the implementation of the above Fig. 9 The methods and functions of the embodiments shown, or the implementation of the above Fig.11 The methods and functions of the embodiments shown, or the implementation of the above Fig.12 Due to the difference in integration, the communication device may include: Fig.15 One or more of the components shown. Fig.15 The components shown may include at least one processor 1501 , a memory 1502 , a transceiver 1503 , and a communication bus 1504 .

[0438] Combine the following Fig.15 The components of the communication device 1500 are described in detail:

[0439] Processor 1501 is the control center of communication device 1500, which can be a processor or a general term for multiple processing elements. For example, processor 1501 is a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as: one or more microprocessors (digital signal processors, DSP), or, one or more field programmable gate arrays (Field Programmable Gate Array, FPGA). Among them, processor 1501 can perform various functions of the communication device by running or executing software programs stored in memory 1502, and calling data stored in memory 1502. In a specific implementation, as an embodiment, processor 1501 may include one or more CPUs, such as Fig.15 CPU0 and CPU1 are shown in the figure.

[0440] In a specific implementation, as an embodiment, the communication device 1500 may include multiple processors, such as Fig.151501 and processor 1505 are shown in FIG. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). The processor here may refer to one or more communication devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0441] The memory 1502 may be a read-only memory (ROM) or other types of static storage communication devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage communication devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage communication device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1502 may exist independently and be connected to the processor 1501 via the communication bus 1504. The memory 1502 may also be integrated with the processor 1501. The memory 1502 is used to store the software program for executing the solution of the present application, and the execution is controlled by the processor 1501 .

[0442] The transceiver 1503 is used for communication with other devices (e.g., the second device). Of course, the transceiver 1503 can also be used to communicate with a communication network, such as Ethernet, a radio access network (RAN), a wireless local area network (WLAN), etc. The transceiver 1503 may include a receiving unit to implement a receiving function, and a sending unit to implement a sending function.

[0443] The communication bus 1504 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.15 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0444] In one example, the communication device 1500 is a complete device, which may include: a processor 1501, a memory 1502, a transceiver 1503, and a communication bus 1504. Optionally, it may also include other components, such as a display frequency.

[0445] Optionally, the communication device 1500 is an access point AP (eg, a reporting AP in an AP multi-link device), which can be used to implement the aforementioned Figure 4 Methods and functions in the illustrated embodiments. For example, a computer program (instructions) is stored in a memory, and when a processor calls the computer program, the above methods and functions are implemented, for example, the processor is used to generate a first management frame (carrying a simplified neighbor report element), and the transceiver is used to send a second management frame (carrying a neighbor report element). For example, the processor is used to control the transceiver to execute step S401. Of course, the generation process of the first management frame involved in step S401 can also be completed by the processor.

[0446] Optionally, the communication device 1500 is a station, which can be used to implement the above Fig. 9 The illustrated embodiments relate to methods and functions of a site. For example, a computer program is stored in a memory, and when a processor calls the computer program, the above methods and functions are implemented, for example, the processor is used to generate signaling or frames (such as an FT request frame, or an authentication request frame), and the transceiver is used to send signaling or frames (such as receiving an FT response frame, or an authentication response frame). For example, the processor is used to generate a control transceiver to receive the FT request frame or the authentication request frame in step S901, and then the processor determines whether it is necessary to reply to the FT response frame or the authentication response frame according to relevant conditions, and if a reply is required, the FT response frame or the authentication response frame is sent through the transceiver. In another example, the communication device 1500 is a chip system or a processing system in an access point AP (such as a reporting AP in an AP multi-link device) or a site (such as a site that receives a first management frame, or a site that receives a second management frame, or a site in the above BSS switching process), so that the device installed with the chip system or the processing system implements the above Figure 4or Fig. 9 or Fig.11 or Fig.12 The communication device 1500 may include the following: Fig.15 Some components shown in the figure, such as the communication device 1500, include a processor, which can be coupled to a memory, call and execute instructions in the memory, thereby configuring the device in which the chip system or processing system is installed to implement the aforementioned Figure 4 or Fig. 9 or Fig.11 or Fig.12 The methods and functions shown. Optionally, the memory may be a component in a chip system or a processing system, or may be a component coupled externally to the chip system or the processing system. In one example, the chip system or the processing system is installed in an access point AP (e.g., a reporting AP in an AP multi-link device) or a site (e.g., a site that receives a first management frame, or a site that receives a second management frame, or a site in the above-mentioned BSS switching process), so that the access point AP (e.g., a reporting AP in an AP multi-link device) or a site (e.g., a site that receives a first management frame, or a site that receives a second management frame, or a site in the above-mentioned BSS switching process) can implement the corresponding methods and functions in the aforementioned embodiments.

[0447] The chip system or processing system can support 802.11 series protocols for communication, such as 802.11be, 802.11ax, 802.11ac, etc. The chip system can be installed in various devices in scenarios supporting WLAN transmission. The devices in the WLAN transmission scenario have been introduced at the beginning of this specification and will not be repeated here.

[0448] The embodiments of the present application can divide the functional modules of the access point AP (such as the reporting AP in the AP multi-link device) or the site (such as the site receiving the first management frame, or the site receiving the second management frame, or the site in the above-mentioned BSS switching process) according to the above-mentioned method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiments of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0449] In the case of an integrated unit, Fig.16A possible structural diagram of a communication device 1600 is shown, and the communication device 1600 may be a chip or a processing system in a link device or a multi-link device, and the communication device 1600 may perform the operations of the multi-link device in the above method embodiment. The communication device 1600 includes: a processing unit 1601 and a transceiver unit 1602.

[0450] In one example, the communication device 1600 is the above-mentioned access point AP (such as a reporting AP in an AP multi-link device) or a station (such as a station receiving a first management frame, or a station receiving a second management frame, or a station in the above-mentioned BSS switching process).

[0451] The processing unit 1601 may be used to control and manage the actions of the communication device 1600. For example, to generate a first management frame or a second management frame. For another example, to control the operation of the transceiver unit 1602. Optionally, if the communication device 1600 includes a storage unit, the processing unit 1601 may also execute a program or instruction stored in the storage unit, so that the communication device 1600 implements the method and function involved in any of the above embodiments.

[0452] Exemplarily, the processing unit 1601 may control the transceiver unit to execute, for example Figure 4 Step S401 in , or Fig. 9 Step S901 in, or, Fig.11 Steps S1101-S1104, or, Fig.12 Steps S1201-S1204 in the method, and / or other processes for the technology described herein. All relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here.

[0453] Exemplarily, the transceiver unit 1602 can transmit and receive data or signaling transmitted on one link, or transmit and receive data or signaling transmitted on multiple links. Optionally, the transceiver unit 1602 can be a transceiver module, or can include multiple transceiver modules. When the transceiver unit 1602 is a transceiver module, the transceiver module can transmit and receive data on multiple links. For example, if the first multi-link device works on two links, then when the transceiver unit 1602 includes two transceiver modules, one of the transceiver modules works on one link, and the other transceiver module works on the other link. Exemplarily, the transceiver unit 1602 can be used to perform, for example Figure 4 Step S401 in, or, Fig. 9 Step S901 in, or, Fig.11 Steps S1101-S1104, or, Fig.12Steps S1201-S1204 in the method, and / or other processes for the technology described herein. All relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here.

[0454] Exemplarily, the communication device 1600 may be Fig.15 The communication device shown in FIG. 1 may include a processing unit 1601. Fig.15 The processor 1501 and the transceiver unit 1602 in the embodiment can be Fig.15 Optionally, the communication device 1600 may further include a memory, the memory being used to store program codes and data corresponding to the communication device 1600 executing any of the multi-link device communication methods provided above. Fig.15 The description of all relevant contents of each component involved can be referred to the functional description of the corresponding components of the communication device 1600, and will not be repeated here.

[0455] Exemplarily, the communication device 1600 may also be a chip or a processor, wherein the processing unit 1601 is a processing circuit in the chip or processor, and the transceiver unit 1602 may be an input / output circuit in the chip or processor. The input / output circuit is an interface for the chip or processor to communicate with other coupled components or exchange data, which can ensure that signaling or data information or program instructions are input into the chip or processor for processing, and the processed data or signaling is output to other coupled components, and the first multi-link device on which the chip or processor is installed is controlled to implement functions.

[0456] In another example, the communication apparatus 1600 is a second device or a chip in the second device.

[0457] Exemplarily, the processing unit 1601 may be used to generate a first management frame or a second management frame, for example, Figure 4 The first management frame in step S401 is generated by the processing unit 1601, or Fig. 9 The second management frame in S901 is generated by the processing unit 1601, or Fig.11 The FT request frame in step S1101 is generated by processing unit 1601, or Fig.12 The authentication request frame in step S1201 is generated by the processing unit 1601 and / or used in other processes of the technology described herein. All relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here.

[0458] Exemplarily, the transceiver unit 1602 can transmit and receive data or signaling transmitted on one link, or transmit and receive data or signaling transmitted on multiple links. Optionally, the transceiver unit 1602 can be a transceiver module, or can include multiple transceiver modules. When the transceiver unit 1602 is a transceiver module, the transceiver module can transmit and receive data on multiple links. For example, if the site works on two links, then when the transceiver unit 1602 includes two transceiver modules, one of the transceiver modules works on one link, and the other transceiver module works on the other link. Exemplarily, the transceiver unit 1602 can be used to perform, for example Figure 4 Step S401 in, or, Fig. 9 Steps S901 and S902 in, or Fig.11 Steps S1101-S1104 shown, or, Fig.12 Steps S1201-S1204 shown, and / or other processes for the technology described herein. All relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here.

[0459] Exemplarily, the communication device 1600 may be Fig.15 The communication device shown in FIG. 1 may include a processing unit 1601. Fig.15 The processor 1501 and the transceiver unit 1602 in the embodiment can be Fig.15 Optionally, the communication device 1600 may further include a memory, the memory being used to store program codes and data corresponding to the communication device 1600 executing any of the methods provided above. Fig.15 The description of all relevant contents of each component involved can be referred to the functional description of the corresponding components of the communication device 1600, and will not be repeated here.

[0460] Exemplarily, the communication device 1600 may also be a chip or a processor, wherein the processing unit 1601 is a processing circuit in the chip or processor, and the transceiver unit 1602 may be an input / output circuit in the chip or processor. The input / output circuit is an interface for the chip or processor to communicate with other coupled components or exchange data, which can ensure that signaling or data information or program instructions are input into the chip or processor for processing, and the processed data or signaling is output to other coupled components, and the device on which the chip or processor is installed is controlled to implement functions.

[0461] The embodiment of the present application also provides a computer-readable storage medium, in which a computer program code is stored. When the above-mentioned processor executes the computer program code, the electronic device (such as an AP, a station) where the processor is located executes Figure 4 ,or Fig. 9,or Fig.11 ,or Fig.12 The method of any one of the embodiments.

[0462] The embodiment of the present application also provides a computer program product, which, when executed on a computer, enables the computer (such as an AP or a station) to execute Figure 4 ,or Fig. 9 ,or Fig.11 ,or Fig.12 The method of any one of the embodiments.

[0463] The embodiment of the present application also provides a communication device, which can exist in the form of a chip product. The structure of the device includes a processor and an interface circuit. The processor is used to communicate with other devices through a receiving circuit, so that the device executes the above Figure 4 , Fig. 9 ,or Fig.11 ,or Fig.12 The method of any one of the embodiments.

[0464] The embodiment of the present application also provides a communication system, which includes the above-mentioned access point AP (for example, the reporting AP in the AP multi-link device) and a station, and the access point AP (for example, the reporting AP in the AP multi-link device) and the station can perform the above-mentioned Figure 4 or Fig. 9 or Fig.11 or Fig.12 The method in the embodiment. Or the communication system includes the above-mentioned site, which can execute the above-mentioned Fig.11 Method in the embodiment. The steps of the method or algorithm described in conjunction with the disclosure of the present application can be implemented in hardware or by executing software instructions by a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory (RAM), a flash memory, an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a mobile hard disk, a read-only compact disk (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a core network interface device. Of course, the processor and the storage medium can also exist in a core network interface device as discrete components.

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

[0466] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of the present application in detail. It should be understood that the above description is only the specific implementation methods of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the present application should be included in the scope of protection of the present application.

Claims

1. A method for discovering an access point multi-link device (APMLD), characterized in that: include: Reporting that the AP generates a management frame, wherein the management frame includes a simplified neighbor RNR element, the RNR element includes an MLDindex field, and the MLDindex field carries an MLD identifier; The MLDindex field is used to indicate whether the reported AP and the reporting AP belong to the same APMLD; The reporting AP sends the management frame.

2. The method of claim 1, wherein: The reported AP and the reporting AP belong to the same APMLD, or, The reported AP is an AP in the AP MLD where the non-transmitting AP in the same multi-BSSID set as the reporting AP is located.

3. The method according to claim 1 or 2, wherein: The MLDindex field is set to 0 to indicate that the reported AP and the reporting AP belong to the same APMLD.

4. The method according to claim 1 or 2, wherein: The MLDindex field is set to 255 to indicate that the reported AP does not belong to any APMLD.

5. The method according to any one of claims 1 to 4, wherein: The management frame also includes link identification information of the reported AP.

6. The method of claim 5, wherein: The link identifier of the reported AP corresponds to an operation set, a channel number or a media access control MAC address of the reported AP.

7. The method according to claim 5 or 6, wherein: The link identifier of the reported AP is unique in the AP MLD to which the reported AP belongs.

8. The method according to any one of claims 1 to 7, wherein: The management frame also includes link identification information of the reporting AP.

9. The method of claim 8, wherein: The link identification information of the reporting AP is carried in the MLD common information field of the MLD element.

10. The method according to any one of claims 1 to 9, wherein: The management frame further includes an MLD element, and the MLD element carries an MLDMAC address occurrence field or a link identifier occurrence field.

11. The method according to any one of claims 1 to 10, wherein: The management frame includes a beacon frame or a probe response frame.

12. A communication device, characterized in that: The device is a reporting access point AP or is applied to a reporting AP, and includes at least one processor, wherein the at least one processor is used to couple with at least one memory, read and execute instructions in the at least one memory, so as to implement: Generate a management frame, wherein the management frame includes a reduced neighbor RNR element, the RNR element includes an MLDindex field, and the MLDindex field carries an identifier of the MLD; The MLDindex field is used to indicate whether the reported access point AP and the reporting AP belong to the same access point multi-link device APMLD; The management frame is sent.

13. The communication device according to claim 12, wherein: The reported AP and the reporting AP belong to the same APMLD, or, The reported AP is an AP in the AP MLD where the non-transmitting AP in the same multi-BSSID set as the reporting AP is located.

14. The communication device according to claim 12 or 13, wherein: The MLDindex field is set to 0 to indicate that the reported AP and the reporting AP belong to the same APMLD.

15. The communication device according to claim 12 or 13, wherein: The MLDindex field is set to 255 to indicate that the reported AP does not belong to any APMLD.

16. The communication device according to any one of claims 12 to 15, wherein: The management frame also includes link identification information of the reported AP.

17. The communication device according to claim 16, wherein: The link identifier of the reported AP corresponds to an operation set, a channel number or a media access control MAC address of the reported AP.

18. The communication device according to claim 16 or 17, wherein: The link identifier of the reported AP is unique in the AP MLD to which the reported AP belongs.

19. The communication device according to any one of claims 12 to 18, wherein: The management frame also includes link identification information of the reporting AP.

20. The communication device according to claim 19, wherein: The link identification information of the reporting AP is carried in the MLD common information field of the MLD element.

21. The communication device according to any one of claims 12 to 20, wherein: The management frame further includes an MLD element, and the MLD element carries an MLDMAC address occurrence field or a link identifier occurrence field.

22. The communication device according to any one of claims 12 to 21, wherein: The management frame includes a beacon frame or a probe response frame.

23. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed on a processor, implements the method described in any one of claims 1 to 11.

24. A communication system, characterized in that: Comprising the communication device as claimed in claim 12.

Images